| Author |
Message
|
| muralihegde |
 Posted: Thu Nov 12, 2015 10:36 am Post subject: Changing additional instances without redeploying |
 |
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
| We have WMB 8.0.0.5 on AIX. Is it possible to increase or decrease the additional instance of the flow, during run time, without redeploying the bar file? If possible, are there any mqsi broker commands that can be used to achieve the same? Also in order to increasing or decreasing the additional instances of the flow, is it needed for the message flows or execution group or the broker to be restarted for this to take effect? We have few long running message flows, hence we have to decide if the increase/decrease can be done without interrupting the running flows? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Nov 12, 2015 10:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Not on your version. Workload policies were introduced in IIBv9 and do exactly what you describe; increasing or decreasing the additional instances (among other possible functions) without redeploying the flow.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 12, 2015 1:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
At V 8 have you tried to use the CMP API to change that value? What happens when you do?
@Vitor I know there you go java again... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 12, 2015 1:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| @Vitor I know there you go java again... |
Humph.
Commands.
XML.
Humph.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Nov 12, 2015 11:32 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Vitor wrote: |
| fjb_saper wrote: |
| @Vitor I know there you go java again... |
Humph.
Commands.
XML.
Humph. |
JSON
Humph
Cobol
Humph
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| maurito |
| Posted: Fri Nov 13, 2015 3:29 am Post subject: Re: Changing additional instances without redeploying |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| muralihegde wrote: |
| We have WMB 8.0.0.5 on AIX. Is it possible to increase or decrease the additional instance of the flow, during run time, without redeploying the bar file? If possible, are there any mqsi broker commands that can be used to achieve the same? Also in order to increasing or decreasing the additional instances of the flow, is it needed for the message flows or execution group or the broker to be restarted for this to take effect? We have few long running message flows, hence we have to decide if the increase/decrease can be done without interrupting the running flows? |
Yes you can.
Use the MQExplorer. right click on the message flow, then properties, that will show you the additional instances |
|
| Back to top |
|
|
| muralihegde |
| Posted: Fri Nov 13, 2015 6:11 am Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
| Thank you maurito. As you suggested, we tried using the Broker/WMQ Explorer. We are able to change the additional instances using that option. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 13, 2015 7:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| muralihegde wrote: |
| Thank you maurito. As you suggested, we tried using the Broker/WMQ Explorer. We are able to change the additional instances using that option. |
If anyone needs me, I'll be over here with my scripted commands, my XML workload policies and a copy of "Learn Java in 21 Days".
(It's exactly the right thickness to stop my desk wobbling. Most use it's been since I bought it 3 years ago.)
Automation. It's not that I don't trust our support area with a GUI, it's just that I don't trust our support area with a GUI.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| maurito |
| Posted: Fri Nov 13, 2015 7:23 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| Vitor wrote: |
| muralihegde wrote: |
| Thank you maurito. As you suggested, we tried using the Broker/WMQ Explorer. We are able to change the additional instances using that option. |
If anyone needs me, I'll be over here with my scripted commands, my XML workload policies and a copy of "Learn Java in 21 Days".
(It's exactly the right thickness to stop my desk wobbling. Most use it's been since I bought it 3 years ago.)
Automation. It's not that I don't trust our support area with a GUI, it's just that I don't trust our support area with a GUI. |
I am all for that.
The MQ Explorer will change the add inst. property, and it will persist restarts. But it will not persist redeployments. |
|
| Back to top |
|
|
|
|
