| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Migrating procedure question... |
« View previous topic :: View next topic » |
| Author |
Message
|
| Maximus |
 Posted: Mon Nov 23, 2009 7:45 am Post subject: Migrating procedure question... |
 |
|
Acolyte
Joined: 14 Jun 2004
Posts: 57
|
Hi Guys,
I have to migration a MQ V6 cluster to MQ V7 and looking at the suggested procedure from IBM at:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzao.doc/mi10790_.htm
And don't understand why I would first test the applications (step 11 and 12) and then do a resume (step 13) to join back the cluster.
Don't I have to resume the QMGR first and then do my testing? If I don't resume the QMGR, how can I test my applications with the newly migrated QMGR?
Also, is this procedure the one used by most of you or is there a better more detailed procedure used by you guys?
To finish, is there any other advise to share when migrating a QMGR in a cluster that is not documented? |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Nov 23, 2009 8:03 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Ideally, your applications would already have been tested against the newer version of WMQ before doing any migrations.
Being out of a cluster should make no difference to checking the application-to-WMQ interface, and as you will be doing one queue manager at a time (presumably) you wouldn't want a flood of inbound messages to that queue manager if the application has issues. Leaving it suspended signals to the cluster an 'unavailability'* for inbound messages.
* normal caveat of last available queue etc.
_________________
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 |
|
|
| Maximus |
| Posted: Mon Nov 23, 2009 8:22 am Post subject: |
|
|
Acolyte
Joined: 14 Jun 2004
Posts: 57
|
| exerk wrote: |
Ideally, your applications would already have been tested against the newer version of WMQ before doing any migrations.
Being out of a cluster should make no difference to checking the application-to-WMQ interface, and as you will be doing one queue manager at a time (presumably) you wouldn't want a flood of inbound messages to that queue manager if the application has issues. Leaving it suspended signals to the cluster an 'unavailability'* for inbound messages.
* normal caveat of last available queue etc. |
All the applications are being tested with WMQ 7.0 on a separate server and only once I am sure they all work I start the migration of existing QMGR one by one.
I am wondering why the procedure says to test the applications before doing the resume on the migrated QMGR. If I want to test the migrated QMGR with the applications, I need to join the cluster so maybe those steps where reversed? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Nov 23, 2009 8:48 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Step 12 is for apps that are connected to the QM directly, so it doesn't matter if the QM is suspended or not.
Step 11 assumes the apps on the other QMs will send messages to your migrated / suspended QM by directly addressing the messages to that QM. A suspended QM is still fully functional. By testing with it suspended you prevent general work from going to it, but can still see how the messages you specifically send to it are handled.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Maximus |
| Posted: Mon Nov 23, 2009 9:42 am Post subject: |
|
|
Acolyte
Joined: 14 Jun 2004
Posts: 57
|
| PeterPotkay wrote: |
Step 12 is for apps that are connected to the QM directly, so it doesn't matter if the QM is suspended or not.
Step 11 assumes the apps on the other QMs will send messages to your migrated / suspended QM by directly addressing the messages to that QM. A suspended QM is still fully functional. By testing with it suspended you prevent general work from going to it, but can still see how the messages you specifically send to it are handled. |
Thanks for the clarifications... now I fully agree with the steps. |
|
| 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
|
|
|
|
