| Author |
Message
|
| niraj |
 Posted: Wed Apr 30, 2008 2:14 am Post subject: Deploy a message flow without starting it... |
 |
|
Newbie
Joined: 30 Apr 2008
Posts: 6
Location: Bangalore
|
All,
We are using WMB 6.0.2. Is there a way to deploy a messaeg flow but NOT start it? We want to deploy the flows but start them at a specified time only...
Regards,
~Niraj |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Apr 30, 2008 2:21 am Post subject: Re: Deploy a message flow without starting it... |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| niraj wrote: |
We are using WMB 6.0.2. Is there a way to deploy a messaeg flow but NOT start it?
|
Inhibit the input queue and deploy the bar file
| niraj wrote: |
We want to deploy the flows but start them at a specified time only...
|
user time nodes to employ this.
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| niraj |
| Posted: Wed Apr 30, 2008 2:25 am Post subject: Still a problem.. |
|
|
Newbie
Joined: 30 Apr 2008
Posts: 6
Location: Bangalore
|
All,
We have multiple input sources - so inhibiting a Inptu MQ will not solve the problem.
TImer nodes will not work as I have a TimeoutNotificatio node in "Automatic" operation as the start node. When the MF is deployed - it'll start immediately. This is the problem I want to avoid.
~Niraj |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 30, 2008 2:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
|
| Back to top |
|
|
| sankritya |
| Posted: Wed Apr 30, 2008 2:40 am Post subject: |
|
|
Centurion
Joined: 14 Feb 2008
Posts: 100
|
| After deploying all the flows just right click on the message flow you want to stop in the execution group and stop it.I think this should work for you. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 30, 2008 2:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sankritya wrote: |
| After deploying all the flows just right click on the message flow you want to stop in the execution group and stop it.I think this should work for you. |
The flow will of course finish processing any messages picked up between deployment and the stop command.
The same effect can of course be achieved with the command line if you're doing a scripted build & deployment.
As in the previous thread I referenced, there's a question of why you'd deploy a flow you don't want to run, at a design level.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
