Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Claudio Rainoldi (ClaudioR)
Corner

Corner
CH
ClaudioR Member since 2014 8 posts
Corner
Posted: Feb 12, 2021
Last activity: Aug 7, 2023
Posted: 12 Feb 2021 8:57 EST
Last activity: 7 Aug 2023 10:34 EDT
Closed

Mq on K8s environment with Tomcat

We are going to evaluate the possibility of upgrading our Pega 7.3 platform, currently hosted on an on premise infrastructure based on WebSphere 8.5, to version Pega 8.x hosted on K8s environment with tomcat application server. We would like to leverage standard Pega 8.x docker image provided by Pega System.

Our main concern regards the integration (both for writing and reading) with external systems using IBM MQ.  According to different articles we found on the community (MQ question related to WAS to Tomcat migration | Collaboration Center (pega.com)) it seems that this should be possible.

What I would like to know is how this could be applied on a K8s environment. I suppose we should in some way customize standard Pega image in order to load the IBM client jars in the tomcat lib.

***Edited by Moderator Marissa to update Content Type from Discussion to Question***
To see attachments, please log in.
Pega Platform 8.6
Client-managed Cloud
Updates
Financial Services
Lead System Architect

Posted: 4 years ago
Posted: 18 Feb 2021 7:38 EST
Kaviya Ravichandran (ravik2) Service Assurance Advisor
Pegasystems Inc.
IN

@ClaudioR

Download the standard docker image, add required jars to lib folder, you can create own new image or do this everytime docker is initialized. 

Then add DSS

     compiler/defaultPaths 

     value: all MQ jars you have in above step separated by comma.

 

Regards,

Kaviya

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice