| Author |
Message
|
| bennchy |
 Posted: Thu Oct 10, 2013 9:51 am Post subject: Difficulties Configuring Cluster with MQ Explorer |
 |
|
Newbie
Joined: 10 Oct 2013
Posts: 6
|
Hi,
I am new to WebSphere MQ and am trying to set-up clustering following the examples from the IBM documentation but using MQ Explorer.
Working through the examples I had no issue creating a cluster and adding the LONDON and NEWYORK qmgr’s to it, as Full Repository, where the qmgr’s reside on the same physical server.
My problems began when trying to add a third qmgr (PARIS) to the INVENTORY cluster from a MQ Server residing on a different physical machine.
I defined the CLUSRCVR and CLUSNDR channels for NEWYORK and PARIS on their respective servers and they started successfully.
However under Queue Managers on the PARIS server the NEWYORK Queue Manager was displayed but greyed out and with a status of disconnected.
On the PARIS server I then right clicked on the INVENTORY cluster (under Queue Manager Cluster) and opened the Add Queue Manager wizard.
I completed the connection details field specifying the correct Host Name and Port Number but noted that the default server-connection channel had defaulted to SYSTEM.ADMIN.SVRCONN.
On clicking the Finish button I got an error code – reason 2538
An MQCONN call was issued from a client to connect to a queue manager but the attempt to allocate a conversation to the remote system failed. Common causes of this reason code are:
• The listener has not been started on the remote system.
• The connection name in the client channel definition is ncorrect.
• The network is currently unavailable.
I then tried changing the Server-connection channel to the name of the CLUSNDR channel (INVENTORY.PARIS) and got error code 2539
An MQCONN call was issued from a client to connect to a queue manager but the attempt to establish communication failed. Common causes of this reason code are:
• The server and client cannot agree on the channel attributes to use.
• There are errors in one or both of the QM.INI or MQCLIENT.INI configuration files.
• The server machine does not support the code page used by the client.
So now I am really confused. I don’t understand why when connecting to a cluster from another physical server the cluster connection wizard is asking for a server-connection channel. I thought that once the CLUSRCVR and CLUSNDR channels were up and running then that would be all that’s required.
Any advice would be greatly appreciated. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Oct 10, 2013 10:40 am Post subject: Re: Difficulties Configuring Cluster with MQ Explorer |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
| bennchy wrote: |
Hi,
I am new to WebSphere MQ and am trying to set-up clustering following the examples from the IBM documentation but using MQ Explorer. |
If you are new to WMQ, you have picked an advanced task. Have you successfully done the basics first?
Have you put messages to a local queue?
Have you successfully connected two qmgrs with SDR and RCVR channels? Have messages successfully flowed between the qmgrs?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Oct 10, 2013 11:43 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1230
Location: Gold Coast of Florida, USA
|
Wow, you want to rely on a wizard to build these channels for you?
No. You need to understand clustering such that you can do this without the wizard which will pick all kinds of names that will not make sense to you.
First, always create the (cluster) receiver channel first so *this* Qmgr can receive any updates it may be sent (and anybody who needs to talk to this Qmgr knows how to talk to it).
Second, create the (cluster) sender channel. The act of doing this inserts this Qmgr to the cluster and will populate the FRs with connection data and the PR with FR connection data.
At this point, let me suggest a sensible naming convention. Name the cluster channels with the <ClusterName>.<QmgrName> where the QmgrName is the the TARGET Qmgr to receive the data (this works whether it is a sender or receiver channel being created (think about it)).
Note that channel names can only be 20 characters long so keep your cluster and Qmgr names to nine (9) characters or less. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Oct 10, 2013 11:48 am Post subject: Re: Difficulties Configuring Cluster with MQ Explorer |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
| bennchy wrote: |
| I don’t understand why when connecting to a cluster from another physical server the cluster connection wizard is asking for a server-connection channel. |
First, you don't connect to a cluster; rather, you connect to a qmgr, which may or may not be a member of a cluster.
From your post, it seems you are attempting to connect the WMQExplorer to a remote qmgr. Doing so requires a SVRCONN channel on the qmgr to be administered. On the WMQExplorer, you must provide the SVRCONN channel name, ipaddress and port number.
CLUSSDR and CLUSRCVR channels are used solely by clustering software, and not by the WMQExplorer.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Oct 10, 2013 11:51 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
| JosephGramig wrote: |
| Wow, you want to rely on a wizard to build these channels for you? |
The WMQExplorer wizard creates channels and other object just fine.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Oct 10, 2013 12:07 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1230
Location: Gold Coast of Florida, USA
|
| bruce2359 wrote: |
| JosephGramig wrote: |
| Wow, you want to rely on a wizard to build these channels for you? |
The WMQExplorer wizard creates channels and other object just fine. |
I didn't say it wouldn't create a working set of objects. I did say the names only make sense to the person that wrote that wizard and implied I hate those names. What is more, I implied the names would not make sense (well, not as much sense as the names I suggest).
Last, my naming convention will prevent instances where a receiver channel can belong to more than one cluster (which works fine but is more complex to debug what is actually going on if there is a problem). |
|
| Back to top |
|
|
| bennchy |
| Posted: Thu Oct 10, 2013 2:01 pm Post subject: Re: Difficulties Configuring Cluster with MQ Explorer |
|
|
Newbie
Joined: 10 Oct 2013
Posts: 6
|
| bruce2359 wrote: |
If you are new to WMQ, you have picked an advanced task. Have you successfully done the basics first?
|
Apologies in advance if I get some to terminology wrong - I am just a humble beginner.
Yes I have done some basic stuff first before looking at clustering. In my UAT environment, I set up a distributed queuing network to send SWIFT messages from an MQ client via an MQ Server (running on Windows) to an MQ Server running on I-Series.
When following the clustering example from the manual I did test I could put a message on the local queue.
| bruce2359 wrote: |
First, you don't connect to a cluster; rather, you connect to a qmgr, which may or may not be a member of a cluster.
From your post, it seems you are attempting to connect the WMQExplorer to a remote qmgr. Doing so requires a SVRCONN channel on the qmgr to be administered. On the WMQExplorer, you must provide the SVRCONN channel name, ipaddress and port number.
|
I agree it does look that way which is why I am confused as to why that config screen is invoked using the INVENTORY cluster object under Queue Managers Cluster?
| JosephGramig wrote: |
First, always create the (cluster) receiver channel first so *this* Qmgr can receive any updates it may be sent (and anybody who needs to talk to this Qmgr knows how to talk to it).
Second, create the (cluster) sender channel. The act of doing this inserts this Qmgr to the cluster and will populate the FRs with connection data and the PR with FR connection data.
At this point, let me suggest a sensible naming convention. Name the cluster channels with the <ClusterName>.<QmgrName> where the QmgrName is the the TARGET Qmgr to receive the data (this works whether it is a sender or receiver channel being created (think about it)).
|
Thanks Joseph. I did follow the naming convention as you have suggested, not quite sure if I got the creation order the same though.
But from what you are saying, am I right in thinking that even if the Qmgr resides on a different physical node, as long as the CLUSSDR and CLUSRCVR channels are configured and running then the Qmgr should be able to 'join' the cluster?
Thanks for the advice everyone.
Tomorrow I am going to re-install MQ Server on both my test servers and start from scratch - hopefully it will work this time round. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Oct 10, 2013 3:02 pm Post subject: Re: Difficulties Configuring Cluster with MQ Explorer |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
| bennchy wrote: |
| I agree it does look that way which is why I am confused as to why that config screen is invoked using the INVENTORY cluster object under Queue Managers Cluster? |
Terminology is important.
A cluster is not an object; rather, it is a collection of object definitions (including CLUSSDR and CLUSRCVR channels) that have the CLUSTER(cluster name goes here) attribute.
The WMQExplorer displays qmgr information in a variety of ways, including objects with the CLUSTER attribute.
| bennchy wrote: |
| But from what you are saying, am I right in thinking that even if the Qmgr resides on a different physical node, as long as the CLUSSDR and CLUSRCVR channels are configured and running then the Qmgr should be able to 'join' the cluster? |
Yes, provided objects that you expect to be visible in the cluster have the CLUSTER attribute.
And, yes, qmgrs in the cluster may be in the same o/s image, on different o/s images in the same physical server box, or in an o/s visible in your network.
To validate, use the MQSC command DIS CLUSQMGR(*) as described here http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.csqzah.doc%2Fqc11160_.htm
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bennchy |
| Posted: Fri Oct 18, 2013 1:57 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2013
Posts: 6
|
Hi,
Subsequent to my previous post, I have re-installed MQ Server on my test servers and started from scratch.
Unfortunately I am still not making much progress 
On server A I set up a cluster called INVENTORY, in accordance with the IBM documentation, and sent messages to the INVENTQ from the NEWYORK and LONDON qmgrs. Both qmgrs have been defined as full repositories.
On server B I set up the PARIS qmgr and defined the CLUSSDR and CLUSRCVR channels which then started successfully.
As soon as I defined the channels, the INVENTORY cluster appeared under the QUEUE MANAGERS CLUSTER folder in WMQExplorer . The cluster icon denoted ‘Cluster without source provider’.
Having never done this before I am not sure what is supposed to happen, but I am guessing if all was working properly the PARIS qmgr would be displayed under the Partial Repositories folder?
On server A (full repository) I opened up the QUEUE MANAGERS CLUSTER folder and under PARTIAL REPOSITORIES could see the PARIS qmgr displayed but greyed out?
Working through the IBM trouble shooting guide I ran the DISPLAY CLUSQMGR(*) ALL command .
As mentioned in the trouble shooting guide I did NOT find any occurrences of “SYSTEM.TEMPUUID” but noticed the attribute “SSLCAUTH” is set to REQUIRED.
I have not attempted to set up SSL authentication and therefore no cert exists in SSL Cert Repository.
Could this be the cause of the issue? If so is it possible to set SSLCAUTH to be not required?
Any help would really appreciated as I seem to have run into a brick wall! |
|
| Back to top |
|
|
| hughson |
| Posted: Fri Oct 18, 2013 2:59 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| bennchy wrote: |
noticed the attribute “SSLCAUTH” is set to REQUIRED.
I have not attempted to set up SSL authentication and therefore no cert exists in SSL Cert Repository.
Could this be the cause of the issue? If so is it possible to set SSLCAUTH to be not required? |
The attribute SSLCAUTH is ignored until you put something in the SSLCIPH attribute of a channel. Thus this attribute being set to REQUIRED is not having any effect on your set up at all.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| hughson |
| Posted: Fri Oct 18, 2013 3:04 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| bennchy wrote: |
On server A I set up a cluster called INVENTORY... NEWYORK and LONDON qmgrs...
On server B I set up the PARIS qmgr ...
As soon as I defined the channels, the INVENTORY cluster appeared under the QUEUE MANAGERS CLUSTER folder in WMQExplorer . The cluster icon denoted ‘Cluster without source provider’.
Having never done this before I am not sure what is supposed to happen, but I am guessing if all was working properly the PARIS qmgr would be displayed under the Partial Repositories folder? |
Have you added the PARIS queue manager to the MQ Explorer? I see that the PARIS queue manager is on server B which is different from server A. Since you say that the MQ Explorer noticed the INVENTORY cluster, I'm guessing that either you already added the LONDON and NEWYORK queue managers to the MQ Explorer, or the MQ Explorer is running on Server A and so automatically picked up the local queue managers. MQ Explorer will not automatically pick up remote queue managers. You should add it as a remote queue manager to the MQ Explorer.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| bennchy |
| Posted: Fri Oct 18, 2013 4:24 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2013
Posts: 6
|
Hi Morag,
This is where I appear to be going round in circles. As I put in my original post, if on the PARIS server I right click on the INVENTORY cluster (under Queue Manager Cluster) and open the Add Queue Manager wizard, the default server-connection channel refers to SYSTEM.ADMIN.SVRCONN. When I click Finish I get an error message stating the channel name is not recognised.
I get the same result if I use the Add Remote Queue Manager wizard by right clicking on the PARIS queue manager. The server-connection channel defaults to SYSTEM.ADMIN.SVRCONN and the channel name is again not recognised.
Even if I specify my own server-conection channel for PARIS the wizard, still reports the channel name is not recogised?
Cheers
Chris. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Oct 18, 2013 5:26 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Create your own SVRCONN Channels and try to use them.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Oct 18, 2013 5:50 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
| bennchy wrote: |
| When I click Finish I get an error message stating the channel name is not recognised. |
Please post the exact error you received, including the error message number (AMQnnnn) and the exact error text.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| hughson |
| Posted: Fri Oct 18, 2013 5:52 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| bennchy wrote: |
| The server-connection channel defaults to SYSTEM.ADMIN.SVRCONN and the channel name is again not recognised |
Have you defined the SVRCONN of this name on the queue manager you are adding? If not, of course it will fail with an unrecognised channel name. Try defining it first, then adding the queue manager to MQ Explorer.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
|
|
