| Author |
Message
|
| maxis |
 Posted: Tue Jan 06, 2004 10:53 am Post subject: migration 2.1 -> 5.0 |
 |
|
Centurion
Joined: 25 Jun 2002
Posts: 144
|
has anybody successfully migrated from 2.1 -> 5 ( where did version 3 & 4 go  ) If so then will you please share your experience ?
thanks
M |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jan 06, 2004 11:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm working on it.
There's no direct path. You have to export, and then migrate and import all of your flows and message sets. Which means another round of testing.
Granted, the migrate/import is somewhat easy - there's a script that does a lot of the hard work for you.
There is no version 3 or 4. v5 is the next version after 2.1 - it's a renumbering along with a rebranding - from "Websphere MQSeries Integrator" to "Websphere Business Integration Message Broker" - in various flavors.
There's a whole PDF manual describing the migration path.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Tue Jan 06, 2004 12:49 pm Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
|
| Back to top |
|
|
| fcotait |
| Posted: Wed Jan 07, 2004 6:10 am Post subject: |
|
|
Acolyte
Joined: 28 Feb 2002
Posts: 63
Location: Sao Paulo - Brazil
|
|
| Back to top |
|
|
| maxis |
| Posted: Wed Jan 07, 2004 8:00 am Post subject: |
|
|
Centurion
Joined: 25 Jun 2002
Posts: 144
|
thanks everyone for the response. I have been reading those pdf .. and preparing own handy manual for migration process.
What exactly I was/is looking for is real world experience, if someone has already done the migration.
thanks
M |
|
| Back to top |
|
|
| Nick Lethbridge |
| Posted: Thu Jan 08, 2004 4:32 am Post subject: |
|
|
Voyager
Joined: 13 Aug 2001
Posts: 88
Location: Santander, UK
|
I have migrated part of our Production WMQI 2.1 environment to a Development WBI MB 5.0 environment (with Rules & Formatter Extension).
By using the migration utilities the process was not overly difficult, but I did encounter some problems with one of our message flows that uses NEON nodes.
When I deployed the flow to the broker and tested it, the test message that was transformed successfully with 2.1 could not be parsed by 5.0.
(In the end I had to modify the NEON Format slightly and then it worked - perhaps our original format did not define the message correctly and the 5.0 parser identified a problem that the 2.1 parser overlooked ?)
Encountered a few quirks with the Message Brokers Toolkit - it looks as though you can no longer 'Zoom - Fit to Window' a message flow (like you could with the WMQI Control Center), so there is now a lot of scrolling if you need to look at all of a complex message flow. Also, if you update a message flow, there does not seem to be an easy way to regenerate a .bar (broker archive) file that contains it - but this could just be due to my lack of knowledge !
Regards,
Nick |
|
| Back to top |
|
|
| maxis |
| Posted: Thu Jan 08, 2004 6:22 am Post subject: |
|
|
Centurion
Joined: 25 Jun 2002
Posts: 144
|
thanks Nick. This is exactly what I was looking for. However is my migration process going to be .. definitely I'll share with the board.
if anyone else would like share .. pl |
|
| Back to top |
|
|
| solomita |
| Posted: Thu Jul 29, 2004 7:54 am Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
| We are in the process of migrating from 2.1 as well. Does anyone have a document which explains things more specifically than the manuals which I have read already? Also info as to how you proceeded in migrating from dev through prod for V5 as well as backup/recovery in the event of an outage. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jul 29, 2004 1:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I never actually completed the migration at my last job, but the way I planned it was to migrate the development system, and then use that to migrate all the flows and sets and etc.
Then convert the UAT environment (delete and rebuild), and promote the migrated flows and sets.
And again, when UAT had been validated, convert production and promote.
Or if one had new hardware, rather than converting environments, one could build the v5 environment, and do a switchover rather than a production outage.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
