Chapter 6. Scenario: WebSphere Message Broker acting as a transaction manager 129
6.4.4 Configuring the JMS administered objects
We created a bindings file to hold the JMS administered objects. There are two
options to create these objects:
򐂰 Use the new WebSphere MQ Explorer option in WebSphere MQ V6.0.2.2 to
configure the JMS administered objects using a GUI. We used this method in
this scenario to create the bindings.
򐂰 Use the JMSAdmin.bat utility provided with WebSphere MQ installation.
The bindings file is configured so that a JMS client can connect to and access
administered objects in the WebSphere MQ JNDI namespace.
We performed the tasks in the following sections in WebSphere MQ Explorer on
the broker’s WebSphere MQ queue manager, which acts as the syncpoint
transaction coordinator.
130 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
Adding the initial context and connecting to the JNDI
namespace
To create and configure JMS objects in WebSphere MQ Explorer, we added an
initial context to define the root of the JNDI namespace in which the JMS objects
are stored in the naming and directory service. For more information, see
“Adding an initial context” in WebSphere MQ Help.
1. From WebSphere MQ Explorer, select JMS Administered Objects Add
Initial Context.
2. In the Connection details window (Figure 6-7), select a file system to hold the
administered objects.
3. Click Finish to add the context and connect to the JNDI namespace.
Figure 6-7 Adding the initial context
Chapter 6. Scenario: WebSphere Message Broker acting as a transaction manager 131
Creating the queue connection factories
We created the following connection factories for this scenario. With the
exception of the parameters specified, accept the default options.
From WebSphere MQ Explorer, follow these steps:
1. Select JMS Administered Objects bindings directory Connection
Factories New Connection Factory.
2. Type the name jms_JMSPROV1, and select WebSphere MQ as the messaging
provider. Click Next.
3. In the next window (Figure 6-8), select Queue Connection Factory as the
type and make sure that Support XA transactions is selected. Click Next.
Figure 6-8 Creating an XA queue connection factory for queue manager JMSPROV1
132 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
4. In the next window (Figure 6-9), for Transport, select
Bindings
and click
Next
.
Figure 6-9 Select Transport option - Bindings
5. On the next page, accept the defaults and click Next.
Important: The JMSInput node is always on the same machine as the
broker queue manager and always uses the Bindings transport. However,
the queue managers for the JMSOutput nodes (JMSPROV1 and
JMSPROV2) might be on a system that is remote to the message flow. For
the connection factories for these providers, select MQ Client. This means
that the connection uses TCP/IP.
If you select MQ Client as the transport and you selected the Support XA
transactions check box on the previous page of the wizard (Figure 6-8 on
page 131), you must install the WebSphere MQ Extended Transactional
Client on the WebSphere Message broker system. Refer to the following
resources for instructions about installing this component:
򐂰 “Installing the WebSphere MQ client” topic in the WebSphere MQ
Information Center
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?t
opic=/com.ibm.mq.csqzaf.doc/amq2512.htm
򐂰 WebSphere MQ Extended Transactional Client Web page
http://www.ibm.com/software/integration/wmq/transclient.html
򐂰 “Units of work and transactions” in WebSphere MQ V6 Fundamentals,
SG24-7128
Chapter 6. Scenario: WebSphere Message Broker acting as a transaction manager 133
6. In the Properties window (Figure 6-10), click Connection on the left, and for
Base queue manager, type JMSPROV1. Then click OK.
Figure 6-10 Specifying the base queue manager
7. On the next window (not shown), click Finish.
8. Repeat the process as explained in step 1 on page 131 through step 7 to add
the following connection factories.
a. Name: jms_PROV2:
Transport: Bindings
Base queue manager: JMSPROV2
b. Name: jms_ESBQCF:
Transport: Bindings
Base queue manager: TEST.QUEUE.MANAGER
c. Name: recoverXAQCF:
Transport: Bindings
Base queue manager: JMSPROV1
z/OS: The only JMS provider that is supported on z/OS is WebSphere MQ
JMS. The only transport option that is supported for WebSphere MQ JMS
on z/OS is the Bind option.

Get Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.