Is it Possible to Convert JMS MDB Listeners to JMS Listeners ?
Hi @MarijeSchillern - Can you please remove “Pega Smart Investigate for Payments 8.8” tag as this is general query not specific to Smart Investigate for Payments product ?
Thanks,
@kumas10 Could you please help me on the query …
@Ganta I will try to locate the relevant SME for your question (which is not Smart Investigate specific)
I was not able to find any previous question about this apart from this.
Can you confirm that you read the available documentation:
About JMS MDB Listener data instances (Data-Admin-Connect-JMSMDBListener)
More about JMS MDB Listener data instances
JMS MDB Listener form - Completing the JMS Properties tab
For more information on the alternatives for EAR-related rules, see Deprecation of EAR deployments in Pega Platform 8.6.
@Ganta , there is no automated conversion tool, but it is certainly possible to manually convert a JMS MDB listener configuration to a standard JMS listener configuration. The major difference between the two is that the JMS MDB listener configuration must be exported as a deployment descriptor file and deployed to the J2EE application container where the Pega platform is running. Regular JMS listeners are managed within Pega Admin studio, just like email and file listeners. The JMS listener documentation describes a number of configuration options which may or may not be applicable to the JMS provider implementation being used.