| Author |
Message
|
| iibmate |
 Posted: Wed May 27, 2015 1:30 am Post subject: issue mqsichangeflowmonitoring for new deployment |
 |
|
Apprentice
Joined: 17 Mar 2015
Posts: 38
Location: Perth, WA
|
Folks,
In our project, we are configuring our threads to emit events based on monitoring profile. We are ample of developers testing our threads on a single integration node instance.
Good thing... events are emitted and we are able to see those getting logged in datacapture store and able to see them in webadmin ui.
bad thing.. Whenever a developer deploys his thread, emission of events is not done by other threads and we have to enable events emitting by mqsichangeflowmonitoring command. Is this the case ?
Any alternate solution for this ?
Environment : IIB V 9002 on linux.
Thanks in advance ! |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 27, 2015 4:48 am Post subject: Re: issue mqsichangeflowmonitoring for new deployment |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| iibmate wrote: |
| Whenever a developer deploys his thread, emission of events is not done by other threads and we have to enable events emitting by mqsichangeflowmonitoring command. Is this the case ? |
Yes.
| iibmate wrote: |
| Any alternate solution for this ? |
Include the mqsichangeflowmonitoring command in your deploy script / MAVEN / JENKINS / CI solution.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| iibmate |
| Posted: Wed May 27, 2015 5:31 pm Post subject: Re: issue mqsichangeflowmonitoring for new deployment |
|
|
Apprentice
Joined: 17 Mar 2015
Posts: 38
Location: Perth, WA
|
| Vitor wrote: |
| Include the mqsichangeflowmonitoring command in your deploy script / MAVEN / JENKINS / CI solution. |
This solution is proposed in higer environments.
In dev, since developer will right click and deploy compiled contents onto DFE processes, dont think so this will work. |
|
| Back to top |
|
|
| iibmate |
| Posted: Wed May 27, 2015 5:38 pm Post subject: Re: issue mqsichangeflowmonitoring for new deployment |
|
|
Apprentice
Joined: 17 Mar 2015
Posts: 38
Location: Perth, WA
|
| Vitor wrote: |
| iibmate wrote: |
| Whenever a developer deploys his thread, emission of events is not done by other threads and we have to enable events emitting by mqsichangeflowmonitoring command. Is this the case ? |
Yes.
|
Just because of change in one thread, emitting of events by other threads should not stop. Does not make sence. For me, IBM have to come with fix for this. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 28, 2015 4:45 am Post subject: Re: issue mqsichangeflowmonitoring for new deployment |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| iibmate wrote: |
| For me, IBM have to come with fix for this. |
Then raise a PMR, especially if you can find it documented someplace that it doesn't work like this (the PMR will therefore result in a change to the code or a change to the documentation).
Or raise an RFE and post the link here; I'm sure you'd get some votes.
What you should not do is just leave it. Despite the number of IBMers loose in here, change comes through official channels.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Thu May 28, 2015 5:27 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
I understand your problem. In our DEV environment, developers can deploy message flows and then the monitoring configs are lost (every time a deploy is done, by default, monitoring is set to inactive).
We have created a script executed by windows scheduler once a day that enables monitoring on all execution groups of DEV environment (other urgent monitoring requests we have the development teams calling the sysAdmin team to enable monitoring).
Maybe you can built such a script and schedule it to run every hour (maybe not a good choice  ) , or you can build such script and allows developers to run it, or you can allow your developers to run the mqischangeflowmonitoring (Danger here). It all comes down to how much control you are willing to deliver to your development team 
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| vishnurajnr |
| Posted: Thu May 28, 2015 9:32 pm Post subject: |
|
|
Centurion
Joined: 08 Aug 2011
Posts: 134
Location: Trivandrum
|
|
| Back to top |
|
|
| iibmate |
| Posted: Thu May 28, 2015 11:05 pm Post subject: Re: issue mqsichangeflowmonitoring for new deployment |
|
|
Apprentice
Joined: 17 Mar 2015
Posts: 38
Location: Perth, WA
|
| Vitor wrote: |
What you should not do is just leave it. Despite the number of IBMers loose in here, change comes through official channels. |
That is what I am doing now, since I dont have an option to raise a PMR.
getting below error..
http://www.ibm.com/developerworks/error/error-500.html |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 29, 2015 4:27 am Post subject: Re: issue mqsichangeflowmonitoring for new deployment |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| iibmate wrote: |
| Vitor wrote: |
What you should not do is just leave it. Despite the number of IBMers loose in here, change comes through official channels. |
That is what I am doing now, since I dont have an option to raise a PMR. |
The option comes with the license. You personally may not, but someone on your site does and they can nominate you as an additional person.
It's the inalienable right of all IBM customers to complain about IBM products. Don't let them deny you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
