| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Migrating the WorkBench from 5 Toolkit to 6.1 Toolkit |
« View previous topic :: View next topic » |
| Author |
Message
|
| sri_csee1983 |
 Posted: Thu Jul 03, 2008 7:22 pm Post subject: Migrating the WorkBench from 5 Toolkit to 6.1 Toolkit |
 |
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear friends,
We are in the process of migrating the broker from Version 5 to 6.1 and hence the toolkit also. So to migrate the flows and messagesets that were developed in 5 toolkit will not open in 6.1 (I suppose). So before opening I need to migrate my workbench to 6.1. In the help I found that we need to migrate each message flow project and message set project. Since we have n number of message flows and message set projects, is there any command so that if we run, the entire workbench gets migrated? Sorry if this answered early. Need your expertise comment on this
_________________
With Cheers,
Sri |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Thu Jul 03, 2008 8:54 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
from the infocenter
Migrate Version 5.0 mappings and data definitions using the mqsimigratemfmaps command.
When you start the Message Broker Toolkit Version 6.1 for the first time, you are prompted to enter a workspace location. Enter the directory where the Message Broker Toolkit Version 5.0 workspace that you want to migrate is located. In Version 5.0, the default location is install_dir/eclipse/workspace.
Version 5.0 message flows are converted to the Version 6.1 format automatically when you save them for the first time. Message Broker Toolkit Version 5.0 cannot read message flows that have been saved in Version 6.1 format.
If your message flows use WebSphere MQ Everyplace® (MQe) nodes, follow the instructions in Migrating a message flow that contains WebSphere MQ Everyplace nodes.
If your message flows use XML style sheets, follow the instructions in Migrating style sheets and XML files from Version 5.0.
Version 5.0 message sets are converted automatically to Version 6.1 format when you save them for the first time. Message Broker Toolkit Version 5.0 cannot read message sets that have been saved in Version 6.1 format.
Clean and rebuild your workspace.
To migrate user-defined nodes from Version 5.0, import the user-defined node project into the Version 6.1 workbench and rebuild the project. If you are migrating user-defined nodes from Version 5.0, perform the following additional steps:
Modify the <requires> element in the plugin.xml file in the user-defined node project root to match the following example. Ensure that you delete all extraneous entries from the Version 5.0 plugin.xml file so that it matches the following example exactly:
<requires>
<import match="greaterOrEqual" plugin="com.ibm.etools.mft.api" version="6.0.0"/>
</requires>
Modify the "org.eclipse.help.contexts" extension in the same plugin.xml file to match the following example:
<extension point="org.eclipse.help.contexts">
<contexts file="HelpContexts.xml"/>
</extension>
_________________
Cheers |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Thu Jul 03, 2008 9:40 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear AkankshA,
Many thanks for your reply. Before posting this in the forum I went through the help of MB6.o and I think u too have posted from the same. My Workbench contains only message flow projects and Message Set Projects. Now what do you mean by Message mapping. Is that necessary for me to execute the command mqsimigratemfmaps?
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| AkankshA |
| Posted: Thu Jul 03, 2008 9:51 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
i request you to please go through the documentation and get an understanding of message broker first.. or get some training..
message mapping is done if you are using mapping node in your flow...
so if u have these nodes then execute else skip it...
_________________
Cheers |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Thu Jul 03, 2008 10:08 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
I ell sure take it up. But I thought taking training after a live experience will make me easy to learn. Thats y, such basic quetions. Dont mistake me. And also I saw this again in the help tht mqsimigratemfmaps is to migrate message mappings (as u told if use Mapping Node). I shud have read that and then replied to ur query. Any how thanks for ur replies. And also we are not using any mapping nodes, So I ell skip the same.
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Jul 07, 2008 1:46 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Why do you need to migrate all your message flows in one go? Whenever a flow happens to need changing, just load it up in the 6.1 toolkit and the first time you save it will be migrated.
If you use the mqsimigratecomponents command on the runtime, you don't need to redeploy your flow logic, so you don't need to load up your flows in order to migrate them.
(Of course, if you're creating a new 6.1 broker and moving each flow across individually, then you will need to load up everything, but that's the price you pay for having a mirrored environment.) |
|
| 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
|
|
|
|
