Using CCDT in an Activation Specification for a Queue Manager Group of separate queue managers in WAS V7, V8.0 and V8.5
This technical document describes the steps for configuring an Activation Specification in WebSphere Application Server V7, V8 and V8.5 that uses a Client Channel Definition Table (CCDT) file for a Queue Manager Group in WebSphere MQ V7 that use separate queue managers.
This document explains the usage of the sample MDB (SampleMDBEJBEA)
+++ Related techdocs
a) If you want to use a Connection Factory, consult the following related techdoc:
Using CCDT in a Connection Factory for a Queue Manager Group of separate queue managers in WAS V7 and V8.x
b) The sample MDB (SampleMDBEJBEAR) is available from the following techdoc.
It also has the steps on how to create the JMS administrative objects and how to deploy the MDB.
Using WebSphere MQ V7 as JMS Provider for WebSphere Application Server V7, V8.0 and V8.5
c) For the case of a Queue Manager Group that is composed of a multi-instance queue manager, see the techdoc:
Using a CCDT file to connect to WebSphere MQ multi-instance queue managers from WebSphere Application Server V7
+++ Update on 26-Sep-2013
Added Note and explanation: XA is NOT supported for separate queue managers using CCDT.
File: Using CCDT in Activation Specification for a Queue Manager Group in WAS V7 and V8.x.pdf
|Application Servers||WebSphere Application Server||Java Message Service (JMS)||AIX, HP-UX, Linux, Solaris, Windows||8.5, 8.0, 7.0|
|Business Integration||WebSphere MQ||Clients||AIX, HP-UX, Linux, Solaris, Windows||7.5, 7.1, 7.0|
WebSphere MQ WMQ