| Author |
Message
|
| manishpnp |
 Posted: Fri Jan 13, 2012 7:16 am Post subject: migratation of WMB6.0 to WMB7.0 |
 |
|
Apprentice
Joined: 21 Feb 2008
Posts: 46
|
Hi,
I'm planning migrate the WebSphere Message Broker v6.1.0.8 to version 7.0.0.3.
WMB6.0 - Broker Details
Broker Name - BRKIKONOB
File Systems
Install Path = /opt/IBM/mqsi/6.1
Working Path = /var/mqsi
data path - /MQHA/BRKIKONOB/data/mqsi
AIX HACMP - MC91 scripts (Presently Broker-BRKIKONOB are under High Availability between two nodes).
I went through the infocenter links and mqseries forum to cover all the details required for the WMB migration to version 7.0.
I have tried to make the plan for this WMB migration and as per my understanding the below steps involved in migration as follows :-
1) stop and backup WMB 6.0 broker (copy this folder - /MQHA/BRKIKONOB/data/mqsi) and its database.
2) Install WMB 7.0 binaries (different than WMB6.0 install path - e.g. /opt/IBM/mqsi/7.0)..I'm right!
3) Apply 7.0.0.3 fix pack (while applying I have to choose WMB 7.0 installation path)
4) pre-migration check of the specified component. (mqsimigratecomponents -c BRKIKONOB)
5) We are using ODBC.ini to connect our database. Do I need to change anything here? upgrade the lib????
5) Migrate the "BRKIKONOB" broker from WMB V7.0 command - mqsimigratecomponents BRKIKONOB....(hope command is correct!!!)
6) start BRKIKONOB broker in WMB 7.0. No need to deploy bar files again.
6) Review the post-migration tasks
 Once WMB7.0 - broker running fine. We will remove the config manager/database/old binaries etc.
9) Using same MC91-HACMP Scripts. I will configure the Broker failover...
Hope there won't be any problem after migrating to WMB7 using mqsimigratecomponents -c BRKIKONOB command. Broker will be start smoothly in WMB7.
Have anyone done this yet and is there any shortage(s) in my steps?
Rollout Plan :-
1) Restore broker to previous version of WMB6 using - mqsimigratecomponents Broker -t 6.1.0.3 - I am not too sure it will smoothly works!!!!
Tried to search rollback to WMB6 in mqseries.forum - but not find any success rollback response using above command.
2) 2nd option - Delete WMB6 components (config manager/user name/broker etc.) and recreate the broker from scratch in WMB6. Then redeploy all the flows, message sets etc.
Looking your advise at this point will be appreciated. Kindly let me know if any steps missing in the migration steps!!!!
manish |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Jan 13, 2012 7:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
mc91/ic91 is out of date.
Review the doc in the infocenter on using an existing HA manager. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Jan 13, 2012 7:44 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It's all very well saying MC/IC91 is out of date, but existing brokers can be upgraded in place and it still works exactly the same way.
The good news is that they will work exactly as before. You can of course get rid of the config manager in the HA startup.
Some observations.
Don't backout the WMB 7003 install even if the migrate check fails. WMB 7003 software coexists perfectly well with WMB 6108. Leave both versions installed.
In fact I would separate the WMB software installation from the broker migration entirely.
I would upgrade/downgrade the broker in place. A lot easier then broker recreation especially with HA.
You need to update your broker .profile to use WMB 7 libaries etc.
You need to update ODBC.ini files to use the later drivers - personally I set up two versions and point to the correct one in the profile script.
What version of DB2 do you have?
There are a few other caveats around this process which I can share later. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 13, 2012 7:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| zpat wrote: |
It's all very well saying MC/IC91 is out of date, but existing brokers can be upgraded in place and it still works exactly the same way.
The good news is that they will work exactly as before. You can of course get rid of the config manager in the HA startup. |
MC91/IC91 doesn't usually provide failover monitoring/etc for the disk that needs to hold the file system repository that replaces the broker database.
i.e. When you stop using the database, you need to make sure that you have put the broker repository on shared disk and that this disk gets moved during failover.
This is additional config that is not, obviously, covered by MC/IC 91 since that was in the database in v6.1 |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Jan 13, 2012 8:24 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
But the registry directory exists in WMB 6.1 as well - there is just more in it.
MC/IC91 moves the WMB broker registry and components directories to the HA storage location specified (usually the queue manager data directory).
These are therefore already on SAN storage. No changes are needed.
There is a slight issue with the mqsirestorebroker command - which I have PMRed and IBM are changing the documentation to include how to use this when these directories have been symlinked elsewhere.
The HA aspects that relate to the config manager and DB2 can, of course, be removed once any fall back to the old version is no longer contemplated. |
|
| Back to top |
|
|
|
|
