| Author |
Message
|
| beth_carlin |
 Posted: Mon Jul 02, 2007 4:54 pm Post subject: wmqi 2.1 to WMB V6 |
 |
|
Acolyte
Joined: 08 Jun 2004
Posts: 64
|
Hi Gurus,
Please tell me if there is any migration utility available in WMB V6 to migrate WMQI 2.1 message flows (xml files) to WMB V6 message flows.
Thanks you
Beth |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Jul 02, 2007 5:25 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes.
There is.
It's called...
"Message Broker Toolkit, v6.0".
Or... perhaps... "mqsimigrateflows".
Maybe Vitor knows for sure?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jul 02, 2007 11:55 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
Yes.
There is.
It's called...
"Message Broker Toolkit, v6.0".
Or... perhaps... "mqsimigrateflows".
Maybe Vitor knows for sure? |
Oh yes. Works a treat. I now bathe in the golden glow of v6 
(The command is actually mqsimigratemsgflows but who's counting?)
Seriously, we've just moved the whole rack of v2.1 to v6 with nothing but the inbuilt tools. Started 2 months ago and hits production next Tuesday. We're like cats in a dog show because we were expecting all sorts of issues but nothing's gone wrong yet.
But I don't do callout!
I commend the Message Broker Migration manual to your attention, which contains a step by step guide to leaving the pain, misery and darkness of v2.1 for the promised land of v6. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Jul 03, 2007 2:35 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Vitor wrote: |
| We're like cats in a dog show because we were expecting all sorts of issues but nothing's gone wrong yet. |
That is an amazing quote.
Vitor, are you looking to get your face on the marketing materials?  |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jul 03, 2007 2:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqmatt wrote: |
| Vitor wrote: |
| We're like cats in a dog show because we were expecting all sorts of issues but nothing's gone wrong yet. |
That is an amazing quote.
Vitor, are you looking to get your face on the marketing materials? |
It's unwise. Remember the photo I used to have on in here? That wasn't edited....... 
Seriously, we moved wads of stuff, it's gone through all the test processes and there's still been nothing that you wouldn't expect from a large release. The only migration-related problems we've had have been from our pet aggrigation flow (known locally as the agrovation flow) and some problems with message sets.
Tribute must be paid not only to the IBM tools and the support offered, but also to Bernard's dad who put much effort into this! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| beth_carlin |
| Posted: Thu Jul 05, 2007 1:51 pm Post subject: please explain more |
|
|
Acolyte
Joined: 08 Jun 2004
Posts: 64
|
This link
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp?
says
Use the mqsimigratemsgflows command to create new flows in the WebSphere Message Broker Version 6.0 format, based on existing exported flows from a WebSphere MQ Integrator Broker Version 2.1 Configuration Manager.
Please explain to me if I must also migrate the 2.1 Configuration Manager to MB6 ?
I plan to install MB6 and create everything new except the 2.1 message flows.
Can I then use mqsimigratemsgflows to import 2.1 xml message flows into MB6 ?
THANK YOU
Beth |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 05, 2007 2:38 pm Post subject: Re: please explain more |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| beth_carlin wrote: |
Please explain to me if I must also migrate the 2.1 Configuration Manager to MB6 ?
I plan to install MB6 and create everything new except the 2.1 message flows.
Can I then use mqsimigratemsgflows to import 2.1 xml message flows into MB6 ?
|
If you examine the syntax of the command (in the section "Migrating message flows from Version 2.1") you'll notice it requires a workspace and a project name.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqdev |
| Posted: Wed Aug 08, 2007 2:29 pm Post subject: Much needed information regarding v2.1 -> v6.0 migration |
|
|
Centurion
Joined: 21 Jan 2003
Posts: 136
|
Hello,
It is good to know someone has already threaded this path and can hopefully guide us too...
Here is our situation:
Present:
MQSI v2.1 with DB2 v7.1 on Win2000
Future (hoping to get here):
WMB v6.0 with DB2 v8.3 on Win2003
We have been trying the migration on a test box (once this procedure is bullet-proof, will use it to migrate Production which is super-critical and we MUST get it right - no excuses accepted whatsoever).
We were able to get the v2.1 Message-flows (mqsimigratemsgflows), Message-sets (mqsimigratesets) and ConfigMgr out to Win2003 box. However we are failing when we try to migrate the v2.1 Broker (mqsimigratecomponents <BrokerName> is failing with some Database related error). There are a ton (literally) of Subscriptions on a bunch of Topics - I can see these on the migrated ConfigMgr on my Win2003 box - would we just be able to create a Broker (with same name as v2.1 Broker) and somehow have the Subscriptions dumped onto the Broker from the ConfigMgr? Getting the Subscription info from v2.1 Broker onto v6.0 Broker (either migrated or created anew on Win2003) is the issue we are facing since we are unable to migrate the Broker using mqsimigratecomponents command. We already have a Sev-1 PMR with IBM - just wanted to touch base in case you have faced something similar....
We have already written scripts for the following:
1. Creation of the Broker
2. Creation of the Execution Groups(EGs) as they exist on v2.1 Broker
3. Creation of BARs for each of the EG for the MessageFlows as they on v2.1 Broker
In addition, we have already imported v2.1 Topics into the v6.0 ConfigMgr. In the Broker Domain under this ConfigMgr, I can see the v2.1 Broker and when I query the Subscriptions for this Broker, I see the subscriptions(only the Broker doesn't exist nor do the underlying DB tables - these would have come over had the mqsimigratecomponents <BrokerName> command been successfull)..we need a way to push these subscriptions onto a newly created v6.0 Broker.
Thanks
-mqdev |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Aug 09, 2007 2:49 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
I suggest you sort out why the mqsimigratecomponents failed, rather than trying to move subscriptions by hand.
You can't recreate subscriptions from the information the Config Manager has, because not all of the required information is there.
Cheers
-Matt |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Aug 09, 2007 8:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I think the "some Database related issue" is the cause of your problems, and a few more details on that may help us help you.
I echo the comments of mqmatt. Where we hit problems we resolved them and continued, if necessary rolling back to before the failure if necessary.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqdev |
| Posted: Thu Aug 09, 2007 3:29 pm Post subject: Thanks for your responses....PMR resolved.. |
|
|
Centurion
Joined: 21 Jan 2003
Posts: 136
|
IBM found that there were a few "orphaned" subscriptions in the BSUBSCRIPTIONS table. We cleaned up those and mqsimigratecomponents worked. We are now engaged in re-creating the Broker using the migrated components on the Win2003 box...will keep updating the details as we progress...
Thanks,
-mqdev |
|
| Back to top |
|
|
|
|
