| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| I have been asked to evaluate environments inside of a flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| jrsetters |
 Posted: Tue Jun 11, 2013 12:08 pm Post subject: I have been asked to evaluate environments inside of a flow |
 |
|
Acolyte
Joined: 24 Aug 2011
Posts: 72
Location: Cincinnati, OH
|
By 'environment' here I mean the organization's view of what is 'TEST or 'PROD' and so forth.
My organization wants me to investigate a couple of things:
1) Evaluate an environment indicator in each message and either publish it if it matches the required environment or discard and notify the analysts by email.
2) Find some way to allow the message flows to be dynamically 'flipped' from operating as production feeds to test or QA or whatever.
The first one seems like a pretty straight forward Compute and Email node task. The second one though, seems fraught with peril, and I am not really sure how to approach this. Their preference is that I design it so they can drop a file in a directory that simply has 'PROD' or 'TEST' and that I can then pass that down to the workflows to evaluate against the incoming message environment indicators until it is changed.
I don't really like this idea, there has to be a better way to do this. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jun 11, 2013 12:25 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Database
User Defined Property
SHARED variable and any other Input node
GlobalCache and any other Input node
User Defined Configurable Service
I'd go with User Defined Property, myself. Easy to change as needed, particularly as part of deployments. |
|
| Back to top |
|
|
| goffinf |
| Posted: Tue Jun 11, 2013 12:52 pm Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
Not sure if this is also part of the use case you have been asked to consider, but sometimes there is a desire to be able to change the configuration of a deployed flow without having to start, stop, or redeploy. For example you may have a flow that sends messages to a Dev instance of an external service and you might want to point it somewhere else for a variety of possible reasons.
I wouldn't expect that most people would consider doing something like this for Prod, since typically deployment and administration of Prod is a much more controlled activity, but for lower environments it can be pretty useful.
For those cases, all of the options which mqjeff suggested still apply, and possibly the CM API also.
HTHs
Fraser. |
|
| 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
|
|
|
|
