Chapter 12. Configuring WebSphere 243
Figure 12-6 Embedded JMS Server configuration window
7. You might also want to change the initial state to Started in order to start the
embedded JMS server the next time you start the application server.
OK, then save the configuration.
12.3 Using WebSphere MQ V5.3
WebSphere Application V5 can also use WebSphere MQ as a JMS provider. The
WebSphere administrative console gives an interface similar to the one provided
for the embedded JMS provider to define WebSphere MQ resources.
Before an external WebSphere MQ JMS provider can be used, we must verify
that the MQJMS_LIB_ROOT variable is set in the environment. This can be done
in the WebSphere Variables configuration window.
12.3.1 Defining a queue connection factory
To configure the WebSphere MQ JMS provider, click Resources -> WebSphere
MQ JMS Provider
. This will take you to the window shown in Figure 12-7 on
244 Self-Service Applications using IBM WebSphere V5.0 and IBM MQSeries Integrator
Figure 12-7 WebSphere MQ JMS Provider configuration window
To create a queue connection factory, we can follow a procedure similar to the
one used with the embedded JMS provider.
Once we get to the queue connection factory configuration window, we have to
specify some additional WebSphere MQ parameters for the JMS provider, as
shown in Figure 12-8 on page 245.
Chapter 12. Configuring WebSphere 245
Figure 12-8 WebSphere MQ Queue Connection Factory configuration window
246 Self-Service Applications using IBM WebSphere V5.0 and IBM MQSeries Integrator
In the Queue Connection Factory configuration window, we specify the following
Scope: The scope of the Queue Connection Factory identifies the location for
the configuration file. This value is static and depends on the server selection
made in the WebSphere JMS Provider window.
Name: This is the required display name for the connection factory.
JNDI Name: This is the resource name, which will be used to locate the
queue connection factory in the JNDI context.
Description: An optional description for the resource.
Category: An optional category string that can be used to classify or group
Component-managed Authentication Alias: References authentication
data for component-managed sign-on to the resource.
Container-managed Authentication Alias: References authentication data
for container-managed sign-on to the resource.
Queue Manager: The name of the WebSphere MQ queue manager for this
connection factory. Connections created using this connection factory
connect to that queue manager. The queue manager must be previously
defined using the WebSphere MQ Explorer.
Host: The name of the host on which the WebSphere MQ queue manager
runs. This is required only for client connections as defined using the
Transport Type properties.
Port: The TCP/IP port number used to connect to the WebSphere MQ queue
manager as defined in the queue manager creation process. This is required
only for client connections.
Channel: The name of the channel used to connect to the WebSphere MQ
queue manager. This is required only for client connections.
Transport Type: Connections to WebSphere MQ can be accomplished using
either client or inter-process bindings connection. For the client connection
the host, port and channel properties must be properly set. Inter-process
binding connection can only be used if the WebSphere MQ resides in the
same physical machine as the WebSphere Application Server.
Model Queue Definition: The name of the model queue used by the queue
manager to create temporary queues.
Client ID: The JMS client used for connections to the WebSphere MQ queue
CCSID: The coded character set identifier for use with the WebSphere MQ
Chapter 12. Configuring WebSphere 247
Message Retention: This property makes unwanted messages stay in the
queue. Otherwise, the messages will be dealt with according to their
XA Enable: This attribute indicates whether the JMS provider is XA-compliant
Additionally, we can configure the connection and session pools for the
WebSphere Application Server.
Once configuration is done for the Connection Factory properties, click
make the changes take effect and then save the configuration.
12.3.2 Define a queue destination
To create queue destinations for WebSphere MQ, we can use the WebSphere
MQ Queue Destinations link from the WebSphere MQ JMS Provider window. In
the Queue Destinations list window, you can create, modify, or delete queue
destination configurations. To add a new queue destination, click
New, and it will
take you to the following window.