Pega Application migration to Container
We are migrating our Pega Application(V 8.6.1) which is currently running as a Weblogic on Oracle DB setup to Openshift Container(on same Oracle DB). We are planning to use the Pega Helm Chart approach to deploy the same. So we are in process of creating the Pega and backingservices yaml files. For pega yaml, we are pulling the latest 8.6.1 image (pegasystems/pega:8.6.1) and for backingservices we are pulling the latest search image(pegasystems/search:latest) from Docker Hub. Need clarification on below questions. Any help here is appreciated.
- I see the instruction given in the link(https://github.com/thomasgpeters/pega-deploy/blob/main/docs/Deploying-Pega-on-openshift.md) installs both backingservices.yaml and pega.yaml with same namespace which means that each environment(DEV/STAGING/PROD) is going to have its own backingservices yaml installation. Please correct me if I’m wrong.
- How does pega.yaml install links to SRS? Is it by the pegasearch attribute in pega.yaml? Got below questions on the same.
- externalURL here is the SRS URL obtained from backingservices yaml deployment? Do we need to update the url after the backingservices yaml install?
- What is the purpose of charts/srs under backingservices?
pegasearch: |
We are migrating our Pega Application(V 8.6.1) which is currently running as a Weblogic on Oracle DB setup to Openshift Container(on same Oracle DB). We are planning to use the Pega Helm Chart approach to deploy the same. So we are in process of creating the Pega and backingservices yaml files. For pega yaml, we are pulling the latest 8.6.1 image (pegasystems/pega:8.6.1) and for backingservices we are pulling the latest search image(pegasystems/search:latest) from Docker Hub. Need clarification on below questions. Any help here is appreciated.
- I see the instruction given in the link(https://github.com/thomasgpeters/pega-deploy/blob/main/docs/Deploying-Pega-on-openshift.md) installs both backingservices.yaml and pega.yaml with same namespace which means that each environment(DEV/STAGING/PROD) is going to have its own backingservices yaml installation. Please correct me if I’m wrong.
- How does pega.yaml install links to SRS? Is it by the pegasearch attribute in pega.yaml? Got below questions on the same.
- externalURL here is the SRS URL obtained from backingservices yaml deployment? Do we need to update the url after the backingservices yaml install?
- What is the purpose of charts/srs under backingservices?
pegasearch: |
For Pega Platform 8.6 and later, Pega recommends using the chart 'backingservices' to enable Pega SRS. To deploy this service, you must configure your SRS cluster using the backingservices Helm charts and provide the SRS URL for your Pega Infinity deployment. |
|
- How does the Pega Search Indices of Rules/Data/Work will be written in Container setup? Today for Weblogic, we specify the -Dindex.directory argument on the server to direct a node to host and write the Pega Search Indices. How does it work with Container? How do we specify the -Dindex.directory? Do we need to set bind mount using Environment Variable and set the JVM Args in pega.yaml?
- Can we copy the currently built indices from Weblogic directory(PegaSearchIndex) to Container volume/bindmount? Will it start building only new Indices or do we need to clean up and start from scratch?
- Also if we need to go without a separate SRS(no backingservices yaml install), what is the option to be given in pega.yaml to consider embedded elastic search functionality? Is it supported in 8.6.1?
***Edited by Moderator Marije to add Capability tags***