| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cluster Setup Question |
« View previous topic :: View next topic » |
| Author |
Message
|
| paul52 |
 Posted: Sun Jul 28, 2002 2:37 pm Post subject: Cluster Setup Question |
 |
|
Novice
Joined: 01 Jul 2002
Posts: 22
|
Hello Everyone
I just want to see if i messed any stepse in setting cluster of 2 QM in AIX. I installed MQ in two separate physical machine (Different IP address) but left the same default port (1414)
Here are the steps i will be executing in the AIX box.
1. Create 2 Queue Mangers (QM1 & QM2) in 2 physical Machine with deault port (1414).
At Host A: crtmqm - SYSTEM.DEAD.LETTER.QUEUE QM1
At Host B: crtmqm - SYSTEM.DEAD.LETTER.QUEUE QM2
3. Created Both Qeue Manager as REpository by MQSC command and the name of the cluster is TEST_CLUTER
RUNMQSC At QM1: ALTER QMGR RESPO (TEST_CLUSTER)
RUNMQSC At QM2: ALTER QMGR RESPO (TEST_CLUSTER)
3. Define CL-Q as custer queue in both QM1 & QM2
RUNMQSC at QM1:
DEFINE QLOCAL (CL-Q) CLUSTER (TEST_CLUSTER)
RUNMQSC at QM2:
DEFINE QLOCAL (CL-Q) CLUSTER (TEST_CLUSTER)
3. Setup the Sender/Receiver channel
In QM1:
Receiver: TO.QM1
Sender: TO.QM2
IN QM2:
Receiver: TO.QM2
Sender: TO.QM1
3. Channel listerner program
At command prompt at Host of QM1 : RUNMQLSR –t tcp [-n QMANME] [-p 1414]
AT command prompt at Host of QM2 : RUNMQLSR –t tcp [-n QMANME] [-p 1414]
How do i verify my cluster configuration is working fine.
What is the different between START channel & Channel Listner program.
Thank you very much for your help.
..Paul |
|
| Back to top |
|
 |
| bduncan |
| Posted: Sun Jul 28, 2002 5:30 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
A few things.
You mention in step 3, "Setup the Sender/Receiver channel". You probably know the difference, but just to make sure we are using the same terminology, you should call these "cluster sender" and "cluster receiver" channels since they are inherently different.
The difference between the channel listener and the "start channel" command is that "start channel" is usually issued on a sender channel (though can be issued on a properly configured receiver channel as well) and basically tells the channel to do whatever it takes to get the channel's status to "RUNNING". The channel listener program simply tells the queue manager to listen for incoming information on the given port (1414). Notice that you don't specify a channel name here. The listener applies to the entire queue manager. Now, if you try to issue "start channel" and the appropriate channel listener(s) aren't running, it won't be able to start. On the other hand, if you start the channel listener, it doesn't necessarily mean all affected channels will immediately start running. It depends of course on your particular configuration.
As far as verifying your cluster is working, there are tons of things to check:
1) check the channels between the two repositories by issuing the "PING CHANNEL" command. Note: the channels must be stopped in order to issue this command correctly. So the correct sequence is "stop channel(x)", "ping channel(x)", "start channel(x)". Of course, if the channel is already running, you probably don't need to test the ping since the ping should always work if the channels are able to start.
2) verify which queue managers each repository "thinks" is in the cluster by issuing "display clusqmgr(*)". Make sure all the queue managers in the cluster are represented here.
3) verify each queue manager sees the clustered queues. Since you called your clustered queue "CL-Q" you should type "DIS QCLUSTER(CL-Q)" on each of the full repositories. I say full because other queue managers in the cluster won't know about CL-Q unless they host an instance of it, or have put a message to it within the last 90 days.
4) Finally, try putting some messages to CL-Q from each queue manager. Note, if you use amqsput to do this, it uses MQOO_BIND_ON_OPEN which means that it will always send messages to the same instance (local) of CL-Q. For this reason you should either use a program that uses MQOO_BIND_NOT_FIXED, or make clustered queues with different names and then try to put messages to them from the queue manager(s) not hosting them...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| paul52 |
| Posted: Mon Jul 29, 2002 6:09 pm Post subject: Client (JMS) connection to Cluster. |
|
|
Novice
Joined: 01 Jul 2002
Posts: 22
|
Hello Brandon
Thanks you very much for the information. Now My Channel works great.
1. Would you please let me know what are the detail steps to setup JMS (client) communication to Server. I am using MQSeries 5.3 in Cluster environment. My client is running in Window 2000 and Server (Queue Manager) running in AIX. Cluster name is CLUSTR_TEST and Cluster Queue is Cl_Q
2. Are there any sample test program to test cluster environment.
3. Do I need to install MA88 ( I heard MQSeries 5.3 comes with MA88, Is it true.)
Thank you very much again.
...Pauls |
|
| 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
|
|
|
|
