MQ question related to WAS to Tomcat migration
Hi - we are on 7.2.1 and are in the process of migrating from WAS to Tomcat. We are using mq to make service calls to other applications in our company. We are using Bindings mode for MQ (local queue manager on each server) and are using native Websphere MQ and not JMS. We really didn't need to do much in WAS related to the mq configuration (set the native mq path in the "Websphere MQ Messaging provider" definition) to get native mq to work. What configurations do I need to do within the TomCat configuration files to make use of native mq? Or, does Tomcat only work with jms? We brought up the Tomcat jvm without any mq definitions; the application is working fine other than mq. I am brand new to Tomcat.
THanks.
***Moderator Edit: Vidyaranjan | Updated Categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Updated: 27 Jul 2017 9:28 EDT
Pegasystems Inc.
IN
Hi Mark,
We always need client jars for tomcat to talk with MQ. Take the client jars from MQ of whatever version you are using and place them at Tomcat level /lib folder. Your catalina.properties setting will see to it they are picked up by the "common" classloader. You might also want to edit catalina.properties so that these jars are not scanned for config info at startup (although they are not that big).
Please note that you should keep MQ client jars at the tomcat level (/lib directory - use the client jars for your version of the MQ server). Importing jars to database can cause classloading conflict with the OOTB pega jars.
After this you need to create following DSS:
compiler/defaultPaths
value: all MQ jars you have in above step separated by comma.
After that Create MQ server in PRPC app and Configure Connect-MQ in PRPC app.
Hi Mark,
We always need client jars for tomcat to talk with MQ. Take the client jars from MQ of whatever version you are using and place them at Tomcat level /lib folder. Your catalina.properties setting will see to it they are picked up by the "common" classloader. You might also want to edit catalina.properties so that these jars are not scanned for config info at startup (although they are not that big).
Please note that you should keep MQ client jars at the tomcat level (/lib directory - use the client jars for your version of the MQ server). Importing jars to database can cause classloading conflict with the OOTB pega jars.
After this you need to create following DSS:
compiler/defaultPaths
value: all MQ jars you have in above step separated by comma.
After that Create MQ server in PRPC app and Configure Connect-MQ in PRPC app.
Hope this will help you
-Abhishek
Pegasystems Inc.
IN
Hi Have look at below PDN article
https://collaborate.pega.com/question/pega-719-migrating-websphere-tomcat
PEG
PL
Hi,
As far as i know, with respect to PRPC, you dont need to do anything in tomcat. What you can do is to use PRPC to connect directly to MQ server. Records->Integration-Resources-> MQ Server.
After creating the instance, Connect MQ has MQ server name. Give this name and mostly thats all you need to do.
Accepted Solution
Updated: 27 Jul 2017 9:28 EDT
Pegasystems Inc.
IN
Hi Mark,
We always need client jars for tomcat to talk with MQ. Take the client jars from MQ of whatever version you are using and place them at Tomcat level /lib folder. Your catalina.properties setting will see to it they are picked up by the "common" classloader. You might also want to edit catalina.properties so that these jars are not scanned for config info at startup (although they are not that big).
Please note that you should keep MQ client jars at the tomcat level (/lib directory - use the client jars for your version of the MQ server). Importing jars to database can cause classloading conflict with the OOTB pega jars.
After this you need to create following DSS:
compiler/defaultPaths
value: all MQ jars you have in above step separated by comma.
After that Create MQ server in PRPC app and Configure Connect-MQ in PRPC app.
Hi Mark,
We always need client jars for tomcat to talk with MQ. Take the client jars from MQ of whatever version you are using and place them at Tomcat level /lib folder. Your catalina.properties setting will see to it they are picked up by the "common" classloader. You might also want to edit catalina.properties so that these jars are not scanned for config info at startup (although they are not that big).
Please note that you should keep MQ client jars at the tomcat level (/lib directory - use the client jars for your version of the MQ server). Importing jars to database can cause classloading conflict with the OOTB pega jars.
After this you need to create following DSS:
compiler/defaultPaths
value: all MQ jars you have in above step separated by comma.
After that Create MQ server in PRPC app and Configure Connect-MQ in PRPC app.
Hope this will help you
-Abhishek
Pegasystems Inc.
IN
Also in addition to that, with respect to DSS please refer below pdn link for more information:
Hope this will help you in setting those DSS required.
-Abhishek
JPMorgan Chase & Company
US
Hi,
if you are migrating to Websphere to tomcat server, so recommended to use JMS listener instead of MQ listener.
Please refer below pdn articles
https://pdn.pega.com/troubleshooting-mq-listeners-do-not-start
https://community.pega.com/sites/default/files/help_v63sp1/Default.htm
Ameriprise Financial
US
Hi - thanks for all of the replies and information. We were able to get mq running using the information provided by Abhishek. We are using bindings mode, so we needed to do one additional step to finally get it working. We needed to get the java.library.path updated with /opt/mqm/java/lib64 path so that libmqjbnd.so could be found.
Pegasystems Inc.
IN
Hi Mark,
https://stackoverflow.com/questions/22677896/tomcat-to-mq-server-connectivity-using-ccdt-64-bit
Please have a look on the above stack-overflow, seems to be helpful for your scenario.
Thank you
-Abhishek