| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSI Upgrading on a failover cluster to 5.3 |
« View previous topic :: View next topic » |
| Author |
Message
|
| martinatkins |
 Posted: Sat Aug 14, 2004 10:56 pm Post subject: MQSI Upgrading on a failover cluster to 5.3 |
 |
|
Novice
Joined: 11 Jan 2004
Posts: 10
|
| I need to upgrade mqsi 2.01 to mqsi 5, We have mqsi installed on a failover cluster ( windows environment ) .I will have updated the mqseries platform to 5.3 from 5.21 , Where can I find any information about upgrading on a failover cluster to 5.3 |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sun Aug 15, 2004 4:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is this a question about setting up WBIMB version 5 in a failover cluster?
Or setting up WebSphere MQ version 5.3 in a failover cluster?
Either way, the failover clustering (and I assume you mean MSCS - right?) is separate from the product upgrade process.
You should read the WBIMB Migration PDF document to understand what needs to be done to upgrade WBIMB. Then you should just be able to register the necessary resources in the MSCS clustering the same way you did version 2.1.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| k9i |
| Posted: Thu Aug 19, 2004 4:24 am Post subject: |
|
|
Newbie
Joined: 11 Jul 2004
Posts: 8
|
We found that there is a name change to the HKLM registry key vs. the instructions in support pac IC71 (which is based on 2.1). MSCS needs this to replicate the broker's registry data.
\SOFTWARE\IBM\WebSphereMQIntegrator
That said, we've not fully tested our MSCS based configuration yet. |
|
| Back to top |
|
|
| k9i |
| Posted: Sat Sep 25, 2004 3:49 am Post subject: |
|
|
Newbie
Joined: 11 Jul 2004
Posts: 8
|
We've also discovered an issue with the way MSCS handles the broker resource registry data vs. the fact that mqsisetdbparms requires the broker to be stopped when the command is run. When the broker generic service resource is brought back online under MSCS, it restores the specified registry data to its previous online state - overwriting the database user/password information stored under <broker-name>/DSN key.
Ideally, mqsisetdbparms would be allowed to run while the broker is running, (but require a restart to pick up changes.)
For now, our work-around is to remove the key from the cluster resource for one restart while setting the DSN/user/password, then restore it in a subsequent restart. |
|
| 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
|
|
|
|
