Author |
Message
|
gpklos |
Posted: Wed Mar 31, 2010 5:57 am Post subject: MQ 7.0.1 PUB SUB Migration |
|
|
Centurion
Joined: 24 May 2002 Posts: 108
|
We are currently running Websphere MQ for windows version 6. We have some critical applications that are using the MQ PUB SUB Broker that
comes with MQ 6. We are going to be moving to Websphere MQ version 7.0.1. I have been reading the migration guide and several documents
related to upgrading to version 7.0.1 of MQ. However I find myself
getting confused over what exactly, if anything, needs done to the
applications to work with MQ version 7 and the new integrated MQ broker.
Now first let me say we have a few JMS applications that talk PUB SUB to
MQ and some regular Java applications that talk PUB SUB. What I'm trying
to figure out is how the following switches/modes/commands work with
each other. According to the migration manual when you upgrade the queue manager to version 7 the pub/sub function is not automatically migrated. You must run the "strmqbrk" to migrate the STATE information. Do you run this if you are running the PSMODE of "Enabled"? Do the JMS/Java apps need to change if the PSMODE is "enabled" but the strmqbrk command hasn't been run. I'm confused as to how these relate and what happens in the different combinations. When do I run strmqbrk? Once it is run do the apps need changed or even just recompiled.
Also there is a "websphere mq messaging provider" which has two modes of "normal" and "migration". These work with JMS apparently. How do these options fit into the picture?
Sorry for so many questions, and confusing ones possibly, but I'm real
confused. Especially since I'm not a programmer, so it is hard to understand some of this. (or just not so smart
Thanks,
Gary |
|
Back to top |
|
 |
mvic |
Posted: Wed Mar 31, 2010 7:07 am Post subject: Re: MQ 7.0.1 PUB SUB Migration |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
Would you mind editing your post so it can be read more easily? The word wrap has gone pretty badly wrong, which makes it difficult to follow. |
|
Back to top |
|
 |
gpklos |
Posted: Wed Mar 31, 2010 7:21 am Post subject: |
|
|
Centurion
Joined: 24 May 2002 Posts: 108
|
We are currently running Websphere MQ for windows version 6. We have some critical applications that are using the MQ PUB SUB Broker that comes with MQ 6. We are going to be moving to Websphere MQ version 7.0.1. I have been reading the migration guide and several documents related to upgrading to version 7.0.1 of MQ. However I find myself getting confused over what exactly, if anything, needs done to the applications to work with MQ version 7 and the new integrated MQ broker.
Now first let me say we have a few JMS applications that talk PUB SUB to MQ and some regular Java applications that talk PUB SUB. What I'm trying to figure out is how the following switches/modes/commands work with each other. According to the migration manual when you upgrade the queue manager to version 7 the pub/sub function is not automatically migrated. You must run the "strmqbrk" to migrate the STATE information. Do you run this if you are running the PSMODE of "Enabled"? Do the JMS/Java apps need to change if the PSMODE is "enabled" but the strmqbrk command hasn't been run. I'm confused as to how these relate and what happens in the different combinations. When do I run strmqbrk? Once it is run do the apps need changed or even just recompiled.
Also there is a "websphere mq messaging provider" which has two modes of "normal" and "migration". These work with JMS apparently. How do these options fit into the picture?
Sorry for so many questions, and confusing ones possibly, but I'm real confused. Especially since I'm not a programmer, so it is hard to understand some of the programming issues. (or just not so smart )
I hope this looks better. |
|
Back to top |
|
 |
mvic |
Posted: Wed Mar 31, 2010 7:37 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
Quote: |
I hope this looks better. |
Much better, thank you
gpklos wrote: |
What I'm trying to figure out is how the following switches/modes/commands work with each other. According to the migration manual when you upgrade the queue manager to version 7 the pub/sub function is not automatically migrated. You must run the "strmqbrk" to migrate the STATE information. |
Correct. This is the same with V6 too, in that with V6 you did not get a running broker unless you typed strmqbrk. When the broker runs for the first time in V7 it migrates your state - well it should do, but you would be well advised to test it all out in a QA environment.
Quote: |
Do you run this if you are running the PSMODE of "Enabled"? Do the JMS/Java apps need to change if the PSMODE is "enabled" but the strmqbrk command hasn't been run. |
Are you planning on NOT running strmqbrk? Why?
Quote: |
I'm confused as to how these relate and what happens in the different combinations. When do I run strmqbrk? Once it is run do the apps need changed or even just recompiled. |
Run it after starting the queue manager. The apps should not need to change. But make sure this is tested..
Quote: |
Also there is a "websphere mq messaging provider" which has two modes of "normal" and "migration". These work with JMS apparently. How do these options fit into the picture? |
Please post a link.. not sure what you're referring to. |
|
Back to top |
|
 |
gpklos |
Posted: Wed Mar 31, 2010 9:12 am Post subject: |
|
|
Centurion
Joined: 24 May 2002 Posts: 108
|
|
Back to top |
|
 |
mvic |
Posted: Wed Mar 31, 2010 9:35 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
Thanks, I followed the link and searched the page for "normal" and "migration" which were what you mentioned. No hits on that page for those two words: are you sure that was the page?
Did the rest of my answers make sense? |
|
Back to top |
|
 |
gpklos |
Posted: Wed Mar 31, 2010 9:49 am Post subject: |
|
|
Centurion
Joined: 24 May 2002 Posts: 108
|
|
Back to top |
|
 |
mvic |
Posted: Wed Mar 31, 2010 10:01 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
Much better, thanks.
I suppose it is not that clear, but that page is all about the choice of value for PROVIDERVERSION in the connection factory. (If only the first paragraph had said eg. "this page describes the PROVIDERVERSION setting and what it controls.")
Or the value of com.ibm.msg.client.wmq.overrideProviderVersion, which is said on that page to override any setting on the connection factory.
The difference seems to be that, if you choose 6, then the V6 methods of pub sub programming will be used under the covers. And if you choose 7, then.. etc.
As far as JMS application programming is concerned, no changes ought to be necessary to the app source code because the JMS spec has not changed with the change in MQ version from 6 to 7.
I hope this helps  |
|
Back to top |
|
 |
gpklos |
Posted: Wed Mar 31, 2010 10:37 am Post subject: |
|
|
Centurion
Joined: 24 May 2002 Posts: 108
|
Thanks for your quick responses. Hopefully I will be upgrading soon. It depends, but when I do I will run the STRMQBRK immediately and then go from there. Obviously the apps will have to test to be sure.
Thanks again,
Gary |
|
Back to top |
|
 |
mvic |
Posted: Wed Mar 31, 2010 12:08 pm Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
I just re-read one of your posts and you said you have apps using pub/sub with the MQ java classes. These should not need to be changed in any way. The MQ folks always try to ensure old apps will continue to work, and on the rare occasion this was not possible they should document it in the migration guide.
As always, test to be sure, but your old MQ java classes apps should continue to work at V7, whether they be pub/sub or queueing apps. Yes there is now a PSMODE, and this has to be set correctly. but when it is, your old apps that put commands to command/stream queues should work. |
|
Back to top |
|
 |
nallabalu |
Posted: Wed Mar 31, 2010 8:38 pm Post subject: Have the same issue - need steps to migrate pub/sub |
|
|
Novice
Joined: 29 Mar 2005 Posts: 19 Location: Long Island, NY
|
Can you please elaborate the steps how to migrate pub/sub after migrating the queue managers from v6.0.2.5 to v7.0.1.1 on win2003. I also tried to run the command strmqbrk to migrate, but migration of some of the subscriptions error ed with RC 2035. Also found error messages in the qmgr-error log -
AMQ5944: Migration has completed with errors. The Queued Publish/Subscribe
Interface will need to be started manually
EXPLANATION:
The migration command has completed but not all data could be migrated. Details
of the error(s) can be found in earlier error messages and the migration log.
ACTION:
Examine earlier error messages and review the migration log, then manually
perform migration of any remaining data that is still required (or if the
problem was transitory by re-running the migration command). Once migration has
been completed, the Queued Publish/Subscribe Interface can be started by
issuing the following MQSC command: alter qmgr psmode(enabled)
------------------------------------------------------------------------------------
AMQ5029: The Server 'SYSTEM.BROKER' has ended. ProcessId(4696). |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Mar 31, 2010 9:24 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Quote: |
but migration of some of the subscriptions errored with RC 2035 |
RC 2035 points to an authorization problem... You need to resolve it.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
nallabalu |
Posted: Thu Apr 01, 2010 7:53 am Post subject: |
|
|
Novice
Joined: 29 Mar 2005 Posts: 19 Location: Long Island, NY
|
I added the right user ID that have authority to the topic and re run the migration command, but still have the same error put to the psmigr.log. seen below :
Migration starting.
2010-04-01 11:34:33.257: Skipping migration of relations as it has already been performed
2010-04-01 11:34:34.288: About to set PSSYNCPT to IFPER
2010-04-01 11:34:34.288: About to set PSRTYCNT to 5
2010-04-01 11:34:34.288: About to set PSNPMSG to DISCARD
2010-04-01 11:34:34.288: About to set PSNPRES to NORMAL
2010-04-01 11:34:34.320: Completed migration of PUBSUB Queue Manager attributes
2010-04-01 11:34:34.351: Altered the SYSTEM.BROKER service to MANUAL starting
2010-04-01 11:34:34.351: Prior to update, QPUBSUB namelist was: SYSTEM.BROKER.DEFAULT.STREAM SYSTEM.BROKER.ADMIN.STREAM
2010-04-01 11:34:34.382: Stream SYSTEM.BROKER.DEFAULT.STREAM not added to namelist: It's already present
2010-04-01 11:34:34.382: Stream SYSTEM.BROKER.ADMIN.STREAM not added to namelist: It's already present
2010-04-01 11:34:34.382: Migration Completed with Errors (for details see earlier messages) |
|
Back to top |
|
 |
|