| Author |
Message
|
| madrox |
 Posted: Mon Jun 01, 2015 9:16 am Post subject: Starting execution groups in a desired order |
 |
|
Acolyte
Joined: 11 Mar 2015
Posts: 71
|
Is it possible to start the execution groups in a desired order when the broker is started?
I would to start one of our eg's after all the others have come up because of dependencies.
Thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jun 01, 2015 10:09 am Post subject: Re: Starting execution groups in a desired order |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| madrox wrote: |
| Is it possible to start the execution groups in a desired order when the broker is started? |
Or at least not out of the box. On IIBv9 or later you can set the dependent EG to a start mode of "Manual" with the others left as "Automatic", then script the manual start of the remaining EG after the others confirm they're successfully started.
It would be much better to tweak the design a little to remove the dependency. This kind of hard link is very anti-pattern.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 01, 2015 10:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You could take better aim at your foot with a larger calibre bullet by implementing a global cache variable that tells you when the rest of the dependent flows are up and running, and then cause the flows with the dependencies to wait until that variable is set...
 |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 01, 2015 10:13 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Just out of morbid curiosity, what exactly is the dependency here?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| madrox |
| Posted: Mon Jun 01, 2015 10:14 am Post subject: |
|
|
Acolyte
Joined: 11 Mar 2015
Posts: 71
|
| We have adapter flows that are deployed on one of the eg's that call the flows on another |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Mon Jun 01, 2015 10:20 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
| Message Broker is supposed to be stateless. The orchestration of the process needs to be done outside of the broker. IMO. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 01, 2015 10:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Is there a solid reason for putting the flows in a separate EG? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 01, 2015 10:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| madrox wrote: |
| We have adapter flows that are deployed on one of the eg's that call the flows on another |
If the calling flow will time out waiting for the called flow to start then your SLA is so tight you need to rethink your design or the EG start delay is so long you need to rethink your EG layout.
Either way, you sound like you're fixing a symptom not the problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| madrox |
| Posted: Mon Jun 01, 2015 10:35 am Post subject: |
|
|
Acolyte
Joined: 11 Mar 2015
Posts: 71
|
| Quote: |
| On IIBv9 or later you can set the dependent EG to a start mode of "Manual" with the others left as "Automatic", then script the manual start of the remaining EG after the others confirm they're successfully started. |
Where can i set this to manual? |
|
| Back to top |
|
|
| madrox |
| Posted: Mon Jun 01, 2015 10:38 am Post subject: |
|
|
Acolyte
Joined: 11 Mar 2015
Posts: 71
|
| Quote: |
Is there a solid reason for putting the flows in a separate EG?
|
We have kept WS call flows separate from adapter flows |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 01, 2015 10:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| madrox wrote: |
| Quote: |
| On IIBv9 or later you can set the dependent EG to a start mode of "Manual" with the others left as "Automatic", then script the manual start of the remaining EG after the others confirm they're successfully started. |
Where can i set this to manual? |
If you type "start mode" into the search bar of the IIBv9 InfoCenter, this is the first hit!
 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jun 01, 2015 10:52 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You can add a compute node with a ESQL sleep to the flows that need the other services up and running. Set a flag in a shared variable so that you don't do the sleep other than the first time.
Or just code a script to start the EGs in a given order (assuming they are all stopped before the broker is stopped).
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| madrox |
| Posted: Mon Jun 01, 2015 10:55 am Post subject: |
|
|
Acolyte
Joined: 11 Mar 2015
Posts: 71
|
Thank you all..
Since its just one flow that needs to started manually this should resolve the issue. |
|
| Back to top |
|
|
|
|
