PQ69903, 5.0.0: MQ settings not saved on the
administrative console
Downloadable files
Abstract
IBM® WebSphere® Application Server 5.0 MQ® settings not
saved on the administrative console
Download Description
PQ69903 resolves the following problem:
PROBLEM DESCRIPTION:
This error pertains to setting WebSphere MQ JMS Provider. When setting a
WebSphere MQ Queue Destination Target Client, the settings are not saved
correctly and the default value of "JMS" is always shown to the user.
ERROR DESCRIPTION:
Administrative console is not displaying the MQ properties correctly. The
problem was recreated using the following steps:
1. Logon to WebSphere Application Server V5.0 administrative console
2. Under Resources on the left pane, click WebSphere MQ JMS Provider.
3. Scroll down to the bottom and click WebSphere MQ Queue destinations.
4. Click New. Enter Name and JNDI Name, e.g. JMSOutboundQueue.
5. Under Base Queue Name, enter a MQ queue name that will be used on the
remote/local MQ Server. Under Target Client, picked "MQ" instead of "JMS".
6. Click Apply and Save the configuration. The information should have
saved into the WebSphere Application Server V5.0 repository.
7. Bring up a DOS prompt and go to <WAS 5>/bin directory.
8. Type wsadmin. You should see: WASX7209I: Connected to process "server1"
on node xxx (For example, your machine's node name) using SOAP connector;
The type of process: UnManagedProcess WASX7029I: For help, enter: "$Help
help"
9. Type "$AdminfConfig list MQQueue". You should see a list of queues that
you've defined through using WebSphere Application Server V5.0
administrative console. One of them (probably the only one) should be
JMSOutboundQueue (as what you used in step #4.
10. Type "$AdminConfig showall [$AdminConfig getid
You should see whole lot of attributes related to the MQ Queue. Please
note that even though you might have picked "MQ" for your targetclient
when you did the JMS setup through the GUI, you still see targetclient
being the JMS.
LOCAL FIX:
Using wsadmin to change the MQ properties.
Prerequisites
None
Installation Instructions
Please review the readme for detailed installation instructions