Question
Deploying/promoting a JMS MDB Listener changes to Non-Dev(SIT/UAT/PROD) environments
As i understand from the article Deploying a JMS message-driven bean (MDB) that represents a JMS MDB listener in Pega 7, that we need to update the application on websphere to add the generated MDB module and bind the listener with the correct target and destination JNDI.
However, the article does not mention how to promote the changes to non-Dev environment like SIT/UAT/PROD etc. Do we have to follow the same steps in each environment. Also if I have multiple listeners do I have to do the same steps for each listener individually?
I am just trying to ease out or simplify the promotion steps as the dev team does not do these deployments in higher environments and just want to avoid any missed configuration/issues due to the steps involved.
Any thoughts/suggestions would be helpful. Thanks!
You would only need to generate the module once and then update the existing prpc_ear with this module in higher environments. The listener module will match the JMS Pega Data records you'll be migrating to these environments as well. Make sure the JNDI references in websphere match as you migrate the module to these servers.
Accenture
IN
Can a single Pega instance have multiple MDB Listener instances mapped? I have 3 applications built on a single pega instance and each application should be able to listen to individual listeners. App server is WAS. Is that possible ?
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread
We have also sent you a private message opening up a communication channel in case you have any further questions.