In Many Projects,wherever you have IBM Websphere MQ Series ,you have definitely come across whether the high availability can be done from PI that if one MQ Server goes down whether PI would be able to connect to other MQ Server and transfer messages..
The answer is YES ,using MQ Series CCDT Techniques..
CCDT is nothing but Client Channel Definition Table is created when you create the queue manager on the WebSphere MQ server. This table contains the details of all the client-connection channels defined at the WebSphere MQ server.
The more information about CCDT can be found on
In our Project ,Landscape is given below Server 1 -> Queue1 on Queue Manager1 on channel 1 can be connected to Port1
Server 2 -> Queue2 on Queue Manager2 on channel 2 can be connected to Port2
Here Queue 1 and Queue 2 has the same name..
Our requirement is that if Server 1 goes down the message needs to be sent to Queue 2 and the same time if Server 2 goes down the message needs to be sent to Queue 1.
CCDT has been prepared in such a way that it has the information about how to connect to Queue1/Queue2 (the both shares same name )
(Here IP Address ,Server Port ,Queue Manager Name ,Channel name have been left blank)
You have to place this CCDT configuration file in any location on the PI Server..that location needs to be mentioned in the advanced configuration
Parameter name = JMS.QueueConnectionFactoryImpl.method.setCCDTURL
value = java.net.URL file:///<file location>
<file location> would be the place where you have kept CCDT file on the PI Server
Once all the required configuration done ,PI will use CCDT table entry details like, Hostname , Queue Manager,Channel name and Port details ..If Server 1 goes down ,then PI –JMS Adapter will establish the
Connection to Server 2 and vice –versa
Thanks to Kishore Narapureddy for pointing me in the right direction and also helping me to understand the CCDT Techniques with his MQ Series expertise