| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Any easy way of creating a copy of flow+subflows? |
« View previous topic :: View next topic » |
| Author |
Message
|
| marko |
 Posted: Thu Apr 03, 2003 1:12 pm Post subject: Any easy way of creating a copy of flow+subflows? |
 |
|
Apprentice
Joined: 28 Feb 2002
Posts: 27
|
I would like to create a new set of message flows (for a new project) based on an existing set of message flows (from an existing project).
In this case I do not want to share any flows, but I want to create new copies (with new names).
Control Center allows me to copy a single flow, but does not seem to allow me to recursively copy a flow and all subflows.
So if I simply copy each required flow individually, any referenced subflows and links still refer to old flows rather than the new copies.
I have managed to figure out how to edit the export of the new copy to fix all of the invalid references, but it is very tedious and error prone.
Does anyone have a script to do this? Or is there any other easier way?
Thanks. |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Apr 03, 2003 1:49 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I don't think there is any easier way to do this. You can try following:
1. First make a copy of all subflows and check-in them into Control center.
2. Make a copy of main message flow and then delete the reference to all old sub-flows.
3. Drag the new sub-flows into the newly created main message flows.
4. Check-in the new main message flows.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| yaakovd |
| Posted: Thu Apr 03, 2003 2:19 pm Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
I don't sure if it is correct way, but it working:
Export main flow (with sub-flows). If you can use some prefix or suffix (marko_) for all flows it will help, becouse in export xml file you need to replace "marko_" with "markoA_".
Then you need change all refrences and uid:
| Code: |
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE XMI SYSTEM "mqsi.dtd" >
<XMI xmi.version="1.0">
<XMI.header>
<XMI.documentation>
<XMI.owner>db2inst1</XMI.owner>
MessageProcessingNodeType/f2747755-f400-1111-0080-ff46af7b32d8
MessageProcessingNodeType/5cc067c9-f000-1111-0080-c5b07eb1e2f1
</XMI.documentation>
</XMI.header>
<XMI.content>
<MessageProcessingNodeType icon="images/MessageProcessingNodeType.gif" package="" creator="" version="" useDefaults="true" collectionPath="" scaleableIcon="" versionTimestamp="" isPrimitive="false" longDescription="" versionCreator="" creationTimestamp="" shortDescription="" xmi.uuid="f2747755-f400-1111-0080-ff46af7b32d8" xmi.id="f2747755-f400-1111-0080-ff46af7b32d8" xmi.label="RosettaNetA_TEST">
<Connection icon="images/Connection.gif" creator="" versionTimestamp="" longDescription="" target="4bf05705-e800-1111-0080-c5b07eb1e2f1.in" bendPoints="" versionCreator="" creationTimestamp="" shortDescription="" source="42267955-f400-1111-0080-ff46af7b32d8.OUT" xmi.label="Connection6">
<ConnectionTypeRef icon="images/ConnectionType.gif" xml:link="simple" xmi.label="ConnectionType" type="ConnectionType" refT |
Element 1111-0080 is the same for all flows in current configuration.
You can use 1111 as version label and change it to 1122, 1133 etc.
In this example I changed "RosettaNet" to "RosettaNetA" and "0000" to "1111" and it was successfully imported into DB.
Again, it is working, but... Kiran described the correct way.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
| marko |
| Posted: Fri Apr 04, 2003 6:07 am Post subject: |
|
|
Apprentice
Joined: 28 Feb 2002
Posts: 27
|
Thanks Yaakov.
I will try this. Kirani's suggestion is not easy in my case since I have many flows and subflows, with nesting several layers deep in some cases. I would very likely have errors if I tried to manual edit the flows through Control Center.
Previously I was doing a hybrid between you and Kirani. I was creating copy of all flows, exporting all flows, open each subflow export so I could record the new uuid's. Then edit the root flow and change the old names to new flow names (based off the prefix), then change all old uuid's to new uuid's. Then re-import the editted root flow.
Your technique may not be as safe, but it is a lot less work:-)
Thanks all. |
|
| 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
|
|
|
|
