Understand the process to integrate IBM WebSphere MQ on Tomcat
We are trying to integrate Tomcat with IBM WebSphere MQ.
In the following PDN link, Pega has provided the process to integrate Tomcat with IBM WebSphere MQ. Need to understand the actions to be done in details as the steps are mentioned in High level.
In the following article, under Resolution, it mentions about the following steps to be performed –
Define MQ JMS (Java Message Service) Administered objects such as Queue Connection Factory, Queue, etc. The MQ Explorer is the tool provided by IBM.
- Does this mean we need to define the instances of QueueConnectionFactory, and Queue, respectively, in context.xml.
Copy the resulting .bindings file to a location on the Tomcat server.
How can we get the bindings file, and is there any alternative way instead of using bindings file.
***Edited by Moderator Marissa to update SR Details; update platform capability tags***
1.Create QueueManager, Queue and Channel on IBM MQ Server.
2.When configuring a Java Message Services connector or service, there are two ways to identify the JMS resources (connection factories, destinations, and so on) the service or connector interacts with: Through resource references in the Process Commander deployment descriptor file (either ejb-jar.xml or web.xml).By direct JNDI name lookup through a JNDI server data object (instance of Data-Admin-Connect-JNDIServer).
Thank you Abhinav. We can able to configure the following modification in the Tomcat application server by modifying the context.xml and web.xml. But Tomcat does not support JMS connection pooling mechanisms, which creates numerous connection when the traffic is high. Can we implement the connection pooling on Tomcat to make the performance better when there are too many messages in the queue.