| Author |
Message
|
| manishpnp |
 Posted: Thu Jan 05, 2012 5:28 am Post subject: WMQ migration from version 6 to version 7 |
 |
|
Apprentice
Joined: 21 Feb 2008
Posts: 46
|
Hello All,
Need help on migrating WMQ running on v6.0.2.6 to WMQ7.0.1.1.
WMQ 6.0 are running out of support from IBM. We have planned to migrate WMQ 6.0.2.10 to WMQ 7.0.1.4 version in AIX 5.3
Queue Manager - IKONOB
File Systems - /MQHA/IKONOB/data and /MQHA/IKONOB/logs
AIX HACMP - MC91 scripts (Presently queue managers are under High Availability between two nodes)
I went through the infocenter links and mqseries forum to cover all the details required for WMQ migration to version 7.0.
As we are running out of service/support from IBM for the WMQ and WMB 6.x versions, we have planned to migrate them to V7 version.
I am preparing the plan for this migration and as per my understanding the task involved in migration as follows :-
1) Take the backup of exsing WMQ 6.0 queue managers from - /MQHA/IKONOB/data and /MQHA/IKONOB/logs
2) Login using mqm user
3) Copy all the mq definitions and OAM authorties using saveqmgr and amqoamd
4) Remove Queue Managers from Cluster
5) Stop all MQ components (queue managers, brokers, configuration manager). Make sure no processes listed related to amq or runmq.
6) Stop Broker database if any
7) Install WMQ V7 with fixpack (Do not have to uninstall current version before installing WMQ 7.0 because the installation process does it for you.)
 Hope queue manager files systems and log directory will same as "/MQHA/IKONOB/data" and MQHA/IKONOB/logs
9) Start queue managers
10) - check the all queue definitions/channels/OAM etc.
11) Configure MQ7.0 Queue Manager with MC91 for High Availability
My assumtion is once queue manager migrated to WMQ7.0. Linear log size will be change from 1024(WMQ6) to 4026(WMQ7.0)..I'm right?
If anything goes wrong here :- Rollback plan
1) Uninstall WMQ 7.0
2) Install WMQ 6.0
3) Restore backup queue managers in the same file systems
Have anyone done this yet and is there any missing steps in above plan? Appreciate your inputs!
Do I need to do anything extra steps after Installing WMQ 7.0 or starting queue manager?
Any configuration/script difference in MC91 for WMQ7.0?
Thanks,
manish |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Jan 05, 2012 5:36 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Start by reading the migration guide in the V7.0 Info Centre, correlate that with what you have put above, refine, then repost if necessary.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jan 05, 2012 6:06 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I have recently done this. The obvious points I would raise from your list are:
MC91 - our QM didn't need any HA reconfiguration (as far as I know), but the more recent support pac files can be loaded into /MQHA/bin - the main change I noticed was the list of MQ processes that exist. However we don't use the application monitor part of this support pac.
No need to stop the broker database.
You can get MQ 7013 as a base install and then add fixpack 7017. If you rollback you will have to install MQ 6 base then 6026 fixpack.
I don't see why the log file size would change by itself - but then we use circular logs.
One tip - if you rollback - delete the qmgr data directory contents before restoring the v6 data - otherwise you will leave the newly created v7 system objects behind, which will cause problems when you later upgrade again.
Check these filesets are installed on AIX : bos.iconv.ucs.com, bos.iconv.ucs.ebcdic, bos.iconv.ucs.pc
If you have externally signed SSL certs add this to qm.ini files to stop OCSP checking certificate revocation (at least until you know this works!).
SSL: ; SSL parms
OCSPCheckExtensions=No ; Do not try to contact OCSP server
OCSPAuthentication=WARN
Expect differences in the way locally hosted java applications may handle data conversion or connection ids. Remote MQ client apps won't change until their MQ client is upgraded.
This java problem is especially the case if you upgrade to v7 earlier than 7017 (at which point most of the changed default behaviour was put back the way it used to be under v6).
For that reason alone I don't think v7014 is a good choice. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Jan 06, 2012 8:01 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| If you found this useful - some sort of acknowledgement of that might be appropriate. |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Jan 06, 2012 8:07 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| zpat wrote: |
| If you found this useful - some sort of acknowledgement of that might be appropriate. |
Do it for the love, not the karma 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| manishpnp |
| Posted: Fri Jan 13, 2012 7:10 am Post subject: Re : WMQ migration from version 6 to version 7 |
|
|
Apprentice
Joined: 21 Feb 2008
Posts: 46
|
Hi everyone..
Appreciate your valuable inputs. I would definately consider this scenarios in migration plan.
I apologies to respond very late as I was busy to shifting my apartment and internet connection also start very late....
Thanks a lot...
manish |
|
| Back to top |
|
|
|
|
