|
Problem |
When configuring a queue connection factory (QCF) under
the WebSphere® MQ JMS provider in the WebSphere Application Server V5
administrative console, the parameters listed in this document must be
specified. |
|
Solution |
To configure the QCF, in the administrative console,
select Resources > WebSphere MQ JMS Provider > WebSphere MQ Queue
Connection Factories > New, or select the QCF Name if it is already
configured. The Name and JNDI name are the only required parameters
listed.
- Name
This name is for administrative purposes only. It can be any name.
- JNDI Name
This is the name used by the lookup() in the application to instantiate
the QCF. The standard is to prepend the JNDI name with jms/.
- Transport Type
Select BINDINGS or CLIENT. BINDINGS works only for queue managers on the
same physical machine as the application server being configured. CLIENT
works for both local and remote queue managers. If the queue manager is
remote, the MQ Client must be installed on the application server machine.
If CLIENT is selected, Host and Port are also required.
- Host
This is the host name or IP address on which the queue manager runs.
- Port
This is the port number of the queue manager used by this QCF. The default
is 1414. If it is changed from the default, and the port number is not
known, it can be determined as follows.
To determine the port of the queue manager in Windows, open the MQ
Services GUI (Start Menu > Programs > IBM WebSphere MQ >
WebSphere MQ Services). Select the queue manager. Right-click on Listener.
Select Properties > Parameters. The port number is displayed.
To determine the port of the queue manager in AIX®, Solaris Operating
System™, HP-UX, or Linux®, there are two possibilities, depending on how
MQ was configured to listen on the network.
The first way is to run ps -ef | grep runmqlsr to see if any MQ
listener programs are running. These will have the qmgr name and port
number on the command line (1414 if no number is given).
The second way is to run grep amqcrsta /etc/inetd.conf to see if
there are entries there that relate to MQ (amqcrsta is the name of the
program that inetd starts if a connection comes in on the port). If there
is an entry that matches, it looks like:
MQ-QMGR1 stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m QMGR1.
In this case, MQ-QMGR1 is the service name, so grep MQ-QMGR1
/etc/services shows what port it is associated with.
- Queue Manager
This is the queue manager name that the QCF connects to. It is not
required, but is suggested. With the BINDINGS transport type, this
specifies a local queue manager to connect to. If not specified, the
default queue manager is used. If there is no default queue manager, then
the connection fails. With the CLIENT transport type, the queue manager
name is compared against the name of the queue manager connected to
through the specified port. If the names do not match, the connection
fails. If no queue manager name is specified, then no comparison is done,
and the connection is made to the queue manager listening on the specified
port.
Complete details on all of the QCF parameters is located in the information center. |
|
|
|
|
|
|