Parshant Sharma (ParshantS)
Cognizant Technology Solutions pvt. ltd.

Cognizant Technology Solutions pvt. ltd.
ParshantS Member since 2013 10 posts
Cognizant Technology Solutions pvt. ltd.
Posted: March 23, 2016
Last activity: September 15, 2017
Posted: 23 Mar 2016 5:29 EDT
Last activity: 15 Sep 2017 5:55 EDT

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!

System Administration Installation and Deployment Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.