| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Config Manager... |
« View previous topic :: View next topic » |
| Author |
Message
|
| niraj |
 Posted: Tue May 06, 2008 10:03 pm Post subject: Config Manager... |
 |
|
Newbie
Joined: 30 Apr 2008
Posts: 6
Location: Bangalore
|
All,
We have are using WMB 6.0.2 on AIX and are using the "mqsistartmsgflow" and "mqsistopmshflow" to start and stop message flows.
Additionally we are using the "ConfigManagerProxy" to check if the flows are running.
We do not have an option of doing the same from the Toolkit in our LIVE environment.
The START / STOP and STATUS commands will be run multiple times in a day for multiple message flows. Since these all use the "ConfigManagerProxy" - questions I have are:
1) Is this going to STRESS the Config Manager?
2) Has anyone experienced performance / any other problems with calling using the "mqsistartmsgflow", "mqsistopmshflow" and the "ConfigManagerProxy" API calls multiple times in a day?
Any pointers on this will be greatly appreciated. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue May 06, 2008 10:10 pm Post subject: Re: Config Manager... |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| niraj wrote: |
We do not have an option of doing the same from the Toolkit in our LIVE environment.
|
Why, Dont you have permission/authorization to do so?
| niraj wrote: |
The START / STOP and STATUS commands will be run multiple times in a day for multiple message flows.
|
Why this is happening, any reason?
| niraj wrote: |
Since these all use the "ConfigManagerProxy" - questions I have are:
1) Is this going to STRESS the Config Manager?
|
No, it not going to give any stress to Config Mgr
| niraj wrote: |
2) Has anyone experienced performance / any other problems with calling using the "mqsistartmsgflow", "mqsistopmshflow" and the "ConfigManagerProxy" API calls multiple times in a day?
Any pointers on this will be greatly appreciated. |
No, AFIK the performance issue doesnt come here at all.
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| niraj |
| Posted: Tue May 06, 2008 10:22 pm Post subject: |
|
|
Newbie
Joined: 30 Apr 2008
Posts: 6
Location: Bangalore
|
Gayathri,
Thanks for the quick response. TO answer your questions..
1) For security reasone we dont want to use the Toolkit in the LIVE environment. The BAR's are prepared and deployed using the command line. Also message flows are started and stopped from the command line.
2) Some flows depend on external triggers to start ( Eg files ) - since there is no way in 6.0.2 to do this ( we will move to 6.1 shortly ), they need to start at various times in a day.
Our main concern was : Since the Config manager is a single UNIX process - would multiple calls to it in a day stress it out / have an impact on the other tasks that it is set to do?
We did notice that on a few occasions the default 60 second timeout interval for MQSISTART/STOP was not enough. This was resolved by increasing the timeout. But with more and more flows using the same mechanism - would we at some point run into problems?
~Niraj |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue May 06, 2008 10:33 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| niraj wrote: |
1) For security reasone we dont want to use the Toolkit in the LIVE environment. The BAR's are prepared and deployed using the command line. Also message flows are started and stopped from the command line.
|
I can understand this,
| niraj wrote: |
2) Some flows depend on external triggers to start ( Eg files ) - since there is no way in 6.0.2 to do this ( we will move to 6.1 shortly ), they need to start at various times in a day.
|
There are some options to do this...you can employ TIME nodes to do so.
| niraj wrote: |
Our main concern was : Since the Config manager is a single UNIX process - would multiple calls to it in a day stress it out / have an impact on the other tasks that it is set to do?
We did notice that on a few occasions the default 60 second timeout interval for MQSISTART/STOP was not enough. This was resolved by increasing the timeout. But with more and more flows using the same mechanism - would we at some point run into problems?
|
Stopping and starting of message flows frequently in Live Production is not a good option, AFAI concerned.
the handshaking between database, broker and configuration managers are happening here heavily, It takes bit of time to update all the necessary details.
if you can find out the bottleneck flows and consolidate that could be the better option.
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
