| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBI Deploy |
« View previous topic :: View next topic » |
| Author |
Message
|
| mward |
 Posted: Tue Feb 19, 2008 7:44 am Post subject: WBI Deploy |
 |
|
Newbie
Joined: 24 Jun 2007
Posts: 6
|
| Hello all, I need some expert advice. What is the best practice way to do a deploy. We have an MQ-Broker developer that tries to deploy his flows in test and development any time he/she wants. This causes DB access errors and deploy timeouts on the z/os system. Then he/she complains that z/os is having all kinds of db and MQ-b problems, I think it's because the flows are being used when they are trying to deploy. When the deploy is done when no one is working all is well. Can I get some expert opinions on how the changes to flows should be deployed? Thanks in advance. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Feb 19, 2008 8:14 am Post subject: Re: WBI Deploy |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mward wrote: |
| Can I get some expert opinions on how the changes to flows should be deployed? |
Same as you'd deploy a new version of an application, or apply a patch/upgrade to software.
IMHO flows fit better into an application release cycle, partly because that's geared to more frequent change and usually incorporates business level testing which is applicable to the flows, but mostly because changes to applications typically cause changes to flow and changes to flows cause changes to applications. So considering flows to be applications in terms of releases, source code control, etc makes for neat packages of deliverable.
My 2 cents, other views are equally valid, etc, etc.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Feb 19, 2008 9:07 am Post subject: Re: WBI Deploy |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mward wrote: |
| We have an MQ-Broker developer that tries to deploy his flows in test and development any time he/she wants. |
How much you tightly control test and development environments varies, but in general the point here is that they are development environments.
They should a) be isolated from each other and from production, b) be geared to meet the needs of test and development and not the needs of production or infrastructure.
It's not clear from what you've said why a flow deployment would cause "db access errors and deploy timeouts". The former would certainly cause the later.
Granted, if a flow is in a stuck state, because of an error in the flow, then it may not stop gracefully during a deploy. But that's not a problem with the "deploy" procedure.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mward |
| Posted: Tue Feb 19, 2008 12:11 pm Post subject: |
|
|
Newbie
Joined: 24 Jun 2007
Posts: 6
|
| Is there a specific way you would do the deploy? I.E. stop the execution group first, or would you deploy the flow while it's being used(tested)? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Feb 19, 2008 12:15 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| mward wrote: |
| deploy the flow while it's being used(tested)? |
Deployments are transparent to message proccesing, in that a deployment will not occur "mid-flow". The flow will stop processing messages, shut itself down, and start up the newly deployed code to process messages again.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
