Using MQ connector in Pega 7.1.8
Hi Pega Support Team,
We have Pega Platform 7.1.8 and IBM WebSphere Application Server Proprietary information hidden.
When we trying to connect to external MQ server, we create MQ server instance, MQ connector in Pega to enable the connection.
Af first, we always have "MQException cannot be resolved" error. To solve it, we place the "com.ibm.mq.jmqi.jar" file on the disk of the application server and update the dynamic system settings of "compiler/defaultPaths" to point to that jar file. Then the problem got solved.
However, it is more like a workaround instead of a formal solution, especially for production environment.
And per our understanding, for IBM WAS Proprietary information hidden, it is not necessary to include any additional jar file outside Pega.
Could you please advise us which is a formal way or best practise for solving this problem? Or do we need to open a SR to apply for a hotfix for this problem?
Thanks and Regards,
Yang
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Pegasystems Inc.
IN
Add "com.ibm.mq.MQException " in the pegarules/compiler/defaultclasses dynamic setting instance and restart server.
Thanks,
Narasimha
Incessant Technologies
IN
Hi ,
To connect to MQ Queue / Queue manager you need following jar files to be present in PRPC classloader path so that MQ Rules could reference them on compile /run time. you can do this by importing the jars by
Designer Studio - > Application - > Distribution - > Import
Jar file list -
com.ibm.mq.jar ,
com.ibm.mq.jmqi.jar,
com.ibm.mq.headers.jar,
com.ibm.mq.commonservices.jar,
connector.jar
By changing the default path to server directory you did the same thing but it is not the correct way to do it if jar file is going to be part of your product feature.
Let me know if you have any further question on this.
MBMT
CN
I tried to import the jars before but it brought class conflict problem and broke the env down.
So it is risky to import external jars for our environment.
Anyway, thank you for your kindly help.
Best Regards,
Yang
Accepted Solution
Pegasystems Inc.
IN
Add "com.ibm.mq.MQException " in the pegarules/compiler/defaultclasses dynamic setting instance and restart server.
Thanks,
Narasimha
MBMT
CN
It seems this solution works for me. Thank you so much!
One more thing is, when I add "com.ibm.mq.MQException" in the compiler/defaultclasses, it works; when I removed it from compiler/defaultclasses and restart the web application server, I found the MQ connection still works. It seems the configuration has been cached. Do you know the exact way Pega cache it?
Thanks a lot!
Best Regards,
Yang
Pegasystems Inc.
IN
Hi Refer the below PDN article.
https://collaborate.pega.com/question/problem-enable-mq-client-support-pega-7
Thanks