| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ with Win2K hot standby |
« View previous topic :: View next topic » |
| Author |
Message
|
| scott9 |
 Posted: Wed Dec 10, 2003 4:50 pm Post subject: MQ with Win2K hot standby |
 |
|
Acolyte
Joined: 11 Jul 2002
Posts: 62
Location: Sacramento,CA
|
We have two Win2K systems. One is primary & the other is a hot standby. If the primary drops, the user application (not MQ) is manually brought up on the hot standby. There is no virtual IP address or disk that is shared between the systems. We must incorporate MQ into this design to transmit messages from MVS to the HOT Win2K system. I want to limit the amount of (MQ) manual intervention required.
We have two dilemmas:
1. The QMGR on MVS basically needs to "find" the Win2K QMGR (wherever it is).
2. Additionally, we need the MQ resources (qmgr, queues, channels) to follow the application.
QUESTIONS:
Does anybody have a similar configuration? If so, how do you manage the channels between the two MQ systems. I'm concerned about dynamically "flipping" channels. I expect we may run into sequence errors, etc.
Anybody familiar with an (W2K) exit or subroutine that checks the presence of a resource and starts MQ accordingly?
Thanks in advance. |
|
| Back to top |
|
 |
| JasonE |
| Posted: Thu Dec 11, 2003 2:23 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
You requirements match exactly what an MSCS (Microsoft cluster) setup would give you for free (shared disk, virtual ip, qmgr data moves from machine to machine and you can configure your apps to go along with it).
Trying to achieve this without such hardware support will be difficult as you will suffer from sequence number errors even if you find a way of routing the channels.
The only thought I would give is use of MQ clustering - have the hot and backup w2k systems running all the time, and a workload balanacing exit on the mainframe to always pick the hot w2k system unless the channel state is in retry. |
|
| Back to top |
|
|
| scott9 |
| Posted: Fri Dec 12, 2003 4:13 pm Post subject: |
|
|
Acolyte
Joined: 11 Jul 2002
Posts: 62
Location: Sacramento,CA
|
Unfortunately, MSCS is not an option. We didn't go with the Workload Blancing Exit, because there is no "key" on MVS to identify which system is active. The application is manually moved to the secondary box. The QMGR and QUEUE objects must be identical on both boxes.
Here's my plan (I'd appreciate any comments).
* Both Windows systems will run an identically named QMGR (req'd by application)
* Both Windows QMGRS will have identically named RCVR channels.
* The MVS QMGR will have a single SDR channel that will point (CONNAME) to the active system. It will be redirected (either through virtual IP or changing CONNAME) to the secondary system.
* We will have to perform a RESET CHANNEL whenever switching from primary to backup.
* Each Windows QMGR will have a uniquely named SDR channel to MVS.
* Likewise, MVS will have unique RCVR channels from each Windows box. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Fri Dec 12, 2003 8:16 pm Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well you could still use a virtual IP Address and move it when moving to the hot standby, and this will allow mainframe to find the box, also the mainframe sdr channel will need to be stopped and started, so that it will
start a new TCP/IP Connection
You will have sequence errors, but you can resolve them and restart the channels
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| 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
|
|
|
|
