| Author |
Message
|
| LMD |
 Posted: Mon Jul 17, 2006 8:21 am Post subject: Administering MQ with WAS 6.1 console |
 |
|
Acolyte
Joined: 30 Oct 2002
Posts: 56
Location: Paris - France
|
Hello all,
With WAS 6.1 there is a new admin console, named "Integrated Solution Console".
On the "Servers" tab, there is an option labelled "WebSphere MQ servers", who let you configure an client connection to an external Queue Manager (not the WAS 6.x Messaging Engine).
You can spécify :
- WebSphere MQ server name
- WebSphere MQ host
- WebSphere MQ port
- WebSphere MQ port
- Reply-to queue
There is also un button nammed "Test Connection" ....
When clicked :
"Error WebSphere MQ server PETWMQ4 connection test failed for WebSphere MQ queue manager PETWMQ4. : An attempt to connect to WebSphere MQ using the information that is provided by the WebSphere MQ Server bus member PETWMQ4 resulted in a connection to a WebSphere MQ queue manager running on version MQCMDL_LEVEL_600 on platform MQPL_WINDOWS_NT. This configuration is not supported. Destinations that are assigned to the WebSphere MQ Server bus member are not accessible.."
My Queue Manager PETWMQ4 is a 6.0 one running on a W2K3 server. So all seems OK.
There is no any messages in AMQERRxx.LOG files.
I this configuration limited to a z/OS Queue Manager ?
Thanks in advance.
_________________
lmd_at_demey-consulting.fr - http://demey-consulting.fr - Paris, France.
WMQ, WAS & IIB Certified.
#IBMChampion |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Jul 17, 2006 9:03 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Maybe the command server is not running |
|
| Back to top |
|
|
| LMD |
| Posted: Mon Jul 17, 2006 9:11 am Post subject: |
|
|
Acolyte
Joined: 30 Oct 2002
Posts: 56
Location: Paris - France
|
the command server IS running, I am able to admin this QM with same parms via MO71 ....
_________________
lmd_at_demey-consulting.fr - http://demey-consulting.fr - Paris, France.
WMQ, WAS & IIB Certified.
#IBMChampion |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 17, 2006 11:12 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Then the question remains as to how you configured it. As a foreign Bus on the SIBus ==> qmgr to qmgr channels from the SIBus to the MQ and back?
Or as an MQ QMGR on the WAS instance.(server or client?)
Thanks for giving us more info...
A tout a l'heure... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| LMD |
| Posted: Mon Jul 17, 2006 12:27 pm Post subject: |
|
|
Acolyte
Joined: 30 Oct 2002
Posts: 56
Location: Paris - France
|
The PETWMQ4 QM is configured with qmgr to qmgr channels from and back the SIBus, and I was able to exchange messages from an to.
(the Messaging Engine seems to be a good option to provide an HA soltuion between MQ and WAS, as the ME restart automatically on any running WAS 6.1 node)
I also have defined a SVRCONN channel on the PETWMQ4 QM, to administrate it remotly (with the MCAUSER set to the right value !)
What I am looking for is information about how to configure this, the InfoCenter is very poor, and Redbooks on 6.1 are very hard to find 
_________________
lmd_at_demey-consulting.fr - http://demey-consulting.fr - Paris, France.
WMQ, WAS & IIB Certified.
#IBMChampion |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 17, 2006 2:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Careful with the WAS SIBus JMSEngine. You can configure it seemlessly so that one APP server takes over if the primary dies. However I don't belive the MQ channel will simply switch over to the new host. You should have a channel defined to each of the hosts supporting the JMSEngine so that in case of failover there is at least one route open. The problem will arise when you need to switch which route is being used to get back to the SIBus...
Now I don't know if you can cluster with the "QMGRS" representing the SIBus... That would take care of switching...
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| LMD |
| Posted: Mon Jul 17, 2006 11:43 pm Post subject: |
|
|
Acolyte
Joined: 30 Oct 2002
Posts: 56
Location: Paris - France
|
| fjb_saper wrote: |
| Careful with the WAS SIBus JMSEngine. You can configure it seemlessly so that one APP server takes over if the primary dies. However I don't belive the MQ channel will simply switch over to the new host. You should have a channel defined to each of the hosts supporting the JMSEngine so that in case of failover there is at least one route open. The problem will arise when you need to switch which route is being used to get back to the SIBus... |
I have solved this 2 months ago, using WAS Edge Components. Site Selector (SS) take care of the host used by ME, and my MQ sender channel point to the SS IP. So the ME can move around nodes, MQ can always communicate with ME, using the same floating IP.
| fjb_saper wrote: |
Now I don't know if you can cluster with the "QMGRS" representing the SIBus... That would take care of switching...
Enjoy |
With WAS V6, it was said that MQ and ME cannot cluster at this time, but "could be possible at later release". I have not tried with WAS 6.1, as we plan to use an HACMP/MSCS cluster on the MQ side.
_________________
lmd_at_demey-consulting.fr - http://demey-consulting.fr - Paris, France.
WMQ, WAS & IIB Certified.
#IBMChampion |
|
| Back to top |
|
|
|
|
