| Author |
Message
|
| zpat |
 Posted: Mon Oct 27, 2008 8:01 am Post subject: Deploying flows into a stopped state |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Is there any way to deploy a message flow (using a bar file) in a stopped state?
If you stop all the execution group flows, then remove all deployed children, then deploy the bar file - the EG is started automatically.
I would like to stop the EG, remove the existing flows, deploy the bar file but not have it start until I chose to do so. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Mon Oct 27, 2008 8:19 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
A good idea I think. I don't there is a way though. Would the deploy work if you GET inhibited the input queues, assuming the flow uses the MQInput node?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Oct 27, 2008 8:23 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Yes, that would probably be the next best option. |
|
| Back to top |
|
|
| jonasb |
| Posted: Tue Oct 28, 2008 12:10 am Post subject: |
|
|
Apprentice
Joined: 20 Dec 2006
Posts: 49
Location: Sweden
|
Hi,
In previous version of the broker, Message flows did start to execute
before the entire bar was deployed. ( i do not know if this is the case still)
This was very bad if you replaced the entire content of an execution group in one deploy.
e.g.
If the matching MessageSet to a flow was not present before the flow started to execute, you obviously get an error..
I solved the problem with 2 bars for each execution group, one with all the message sets and one with all the message flows.
By deploying the messageset-bar first I can guarantee that they will be present when flow execution starts.
Maybe this can be of some help to you?
_________________
contact admin |
|
| Back to top |
|
|
| mlafleur |
| Posted: Tue Oct 28, 2008 6:38 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2004
Posts: 73
|
| Quote: |
| I would like to stop the EG, remove the existing flows, deploy the bar file but not have it start until I chose to do so. |
This may not help you, but if you stop the existing flows and then deploy a new version over them (same flows) then the new version of the flows will be stopped initially. |
|
| Back to top |
|
|
| rajn27 |
| Posted: Wed Oct 29, 2008 7:50 am Post subject: |
|
|
Newbie
Joined: 28 Oct 2008
Posts: 7
|
1. Stop the sender and reciever on both sides (config mgr and Broker)
2. Deploy the bar
3. Start the Sender Channel on config manager
4. Start the reciever on broker when yo see messages in transmission queue
5. stop the sender channel on config mgr side
6. stop the reciever channel on broker side
7. start the sender channel on broker side and recieve on config mgr side
8. stop the message flow and start all channels |
|
| Back to top |
|
|
|
|
