| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSI Message Flow Duplication |
« View previous topic :: View next topic » |
| Author |
Message
|
| rahoor |
 Posted: Mon Jul 21, 2003 11:54 am Post subject: MQSI Message Flow Duplication |
 |
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
| I have an outstanding issue with having to duplicate message flows in the same broker. The only thing different in the flow is the input and output queue names. All the processing within the code remains the same. Is there an automated fashion whereby this can be accomplished? We currently have a need to routinely create and verify several hundred flows based on just a dozen unique flows. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jul 21, 2003 12:28 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Why do you need to deploy them to different queues?
What can't you achieve with aliases or remote queue definitions?
As to automatically duplicating a message flow, this could be accomplished in the following way: - Export each of your unique message flows to an xml file
- Write a program in some language or another to modify the queue name attributes and the object UUIDs (there have been a couple of messages on this forum that discuss modifying UUIDs - it can be done in a simpliefied manner)
- Script the message flow import and assign utilities from IC01 to import and deploy the modified message flow files
However, I don't know that IBM will be very sympathetic if you run into issues using message flows based on modified exported XML.
Another thing to do is to promote the Input Queue and Output queue names as properties, and then treat each of your unique message flows as a subflow, and create a new message flow containing just that subflow and set the properties. This is manual, but relatively quick. |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Jul 22, 2003 9:05 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
A variation on Jeff's last suggestion would be to create a Subflow containing everything except the Input and Output nodes. Then build the flows you need, each of these with the required Queue names, pulling in the Subflow. But, again, that is manual and tedious.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| 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
|
|
|
|
