White Papers
Abstract
The objective of this technical document is to describe in detail how to exploit from the WebSphere Application Server the connection to Multi-Instance Queue Managers in IBM MQ, by using an MQ "Client Channel Definition Table" (CCDT).
The MQ 7.0.1 JMS client introduced also the feature "automatic client reconnection", which is used on JMS standalone applications, but it is not used when running a JMS application within an application server. Instead, the automatic retry mechanisms for Listener Ports and Activation Specifications are used.
One way to configure the WebSphere Application Server to work with multi-instance queue managers is by using an MQ "Client Channel Definition Table" (CCDT).
Note: XA is not supported during automatic client reconnect
Content
Chapter 1: Prerequisites (Sample MDB, userid with proper authority, CCDT file)
Chapter 2: Creating a Client Channel Definition Table (CCDT)
Chapter 3: Defining a Connection Factory that uses the CCDT
Chapter 4: Switchover testing of the Sample MDB - Listener Port
- Test 1: Messages are passed to the MDB, from host-1 "veracruz"
- Test 2: Doing a switchover of the Queue Manager from host-1 "veracruz" to host-2 "cbeech"
- Test 3: MDB gets message that is put into the other instance of the queue manager (host-2 "cbeech")
- Similar steps as in Chapter 4
It is highly recommended that you review the details described in the following technote:
Using WebSphere MQ automatic client reconnection with the WebSphere MQ classes for JMS
++ Section added on 19-Jun-2012:
Using CCDTURL custom property in WAS 6.1
Was this topic helpful?
Document Information
Modified date:
02 March 2024
UID
swg27020701