| Author |
Message
|
| k9i |
 Posted: Thu Oct 28, 2004 10:28 am Post subject: Broker vs. ConfigMgrs |
 |
|
Newbie
Joined: 11 Jul 2004
Posts: 8
|
WBIMB V5
Can a broker be moved to a new configuration manager under a different queue manager without deleting and recreating the broker?
We attempted this and it seems to "work" (create new EG, deploy BAR files, start/stop run flows etc.) except there are messages from the broker trying to contact the SYSTEM.BROKER.ADMIN.REPLY queue for the previous and now defunct configuration manager.
Also, can a broker be configured into more than one domain/configuration manager at a time (for failure mode operation)? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Oct 28, 2004 10:49 am Post subject: Re: Broker vs. ConfigMgrs |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| k9i wrote: |
| Can a broker be moved to a new configuration manager under a different queue manager without deleting and recreating the broker? |
No.
| k9i wrote: |
| Also, can a broker be configured into more than one domain/configuration manager at a time (for failure mode operation)? |
No.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Oct 28, 2004 11:06 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| k9i wrote: |
We attempted this and it seems to "work" (create new EG, deploy BAR files, start/stop run flows etc.) except there are messages from the broker trying to contact the SYSTEM.BROKER.ADMIN.REPLY queue for the previous and now defunct configuration manager.
|
So you are saying that every time you deploy something to this Broker, it's sending message to "old Config Managers" SYSTEM.BROKER.ADMIN.REPLY queue?
What are your requirements for Failure mode operation?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| k9i |
| Posted: Fri Oct 29, 2004 6:34 am Post subject: |
|
|
Newbie
Joined: 11 Jul 2004
Posts: 8
|
The DataFlowEngine is evidently attempting to send updates to the first config manager based on error messages indicating that admin reply queue does not exist (on what was the previous queue manager which was shared with the broker instance) Evidently the queue was removed when we did the mqsideleteconfigmgr on the original).
Our basic requirement is to have a backup server configured ("warm standby") with MQ and broker/configuration manager installed and ready to go in case of failure on the primary node hosting the configuration manager. The configuration manager would be run against another queue manager on the secondary node.
Broker failover and everything else (DB2 and MQ) are already working (using the IC71 support pac instructions + minor tweaks for V5).
Right now, the only known problem is the error message and the concern is that there is something that we have not done that will be a problem.
We do not want to have to configure a new broker upon failover and redeploy everything just because the configuration manager has "moved" (which how I read jefflowrey's reply). The outdated support pac documentation does not address high availability of the configuration manager and we are simply trying to address it (without having to reconfigure anything upon fail-over.) Because it was not documented in IC71, we did not attempt to run the configmgr against an MSCS clustered queue manager as we did the broker.
Also - does the WBIMB documentation state that a broker may only be configured into a single domain/configuration manager for its life? I could not find it and the product does not prevent users from doing it.
Thanks for the replies! |
|
| Back to top |
|
|
| ourtown |
| Posted: Fri Oct 29, 2004 7:20 am Post subject: |
|
|
Acolyte
Joined: 05 Feb 2002
Posts: 67
Location: Somerset, NJ
|
For documentation search for
Removing a broker from a broker domain
For a resilient config manager the simplest solution seems to be using a VMWare image
Otherwise you need your config manager to be highly available - putting it under MSCS works fine but for D/R you would need backup and restore of the config manager components
_________________
Brian S. Crabtree
WBI Consultant |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Wed Sep 14, 2005 7:49 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
| Quote: |
Otherwise you need your config manager to be highly available - putting it under MSCS works fine but for D/R you would need backup and restore of the config manager components
|
We know the configuration Manager is considered to be less critical than the broker & UNS.
Any one run the configuration manager under MSCS? or Run as a HA resource?
Looks like IBM support pack supports for Broksr & UNS only.
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24006261&loc=en_US&cs=utf-8&lang=en
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
|
|
