Question
Nordea
SE
Last activity: 23 Sep 2022 2:17 EDT
Support for Distributed Transaction in Pega 8.7
Hi,
As per the article - https://community.pega.com/node/2309446, Pega 8.7 will stop supporting rules that require EAR deployments. This means when we upgrade to Pega 8.7, we would need to deploy the application as a web application (WAR deployment). There are a couple of questions that need to be answered to get some clarification on Pega's future vision. I have already asked these questions to Pega and waiting for their response:--
1) If an application architecture must require distributed transaction which follows 2 phase commit protocol, how will we move to Pega 8.7 which will no longer support Enterprise deployment?
Hi,
As per the article - https://community.pega.com/node/2309446, Pega 8.7 will stop supporting rules that require EAR deployments. This means when we upgrade to Pega 8.7, we would need to deploy the application as a web application (WAR deployment). There are a couple of questions that need to be answered to get some clarification on Pega's future vision. I have already asked these questions to Pega and waiting for their response:--
1) If an application architecture must require distributed transaction which follows 2 phase commit protocol, how will we move to Pega 8.7 which will no longer support Enterprise deployment?
2) From the article I understand that the JMS MDB listener must be converted to a JMS listener. Let's say if we make the required changes and then move to the cloud later, will JMS listener still be supported because as per the article - (https://community.pega.com/knowledgebase/articles/migrating-pega-cloud-services/remediating-migrating-pega-cloud-services-environments), JMS connectors and services are currently not supported on the cloud because they require provider-specific software to be installed. In that case what are the alternatives to support java messaging services? As per the article, we need to replace these connectors with supported connector types. What are those connector types? Are we referring to MQ listeners? Today we are using JMS MDB listener to process plain text messages where WebSphere MQ as a JMS service provider is used so I think we can go for MQ listener but what if the connected system expects only JMS messages to be sent? What is the support available on Pega cloud to support Java Messaging Services?
Accepted Solution
Updated: 26 Jul 2021 6:29 EDT
Nordea
SE
on the 2nd point - https://community.pega.com/knowledgebase/articles/migrating-pega-cloud-services/remediating-migrating-pega-cloud-services-environments was updated and the section on “Java Message Service (JMS),” was removed because it was out of date (FDBK-80441 and BUG-665138) so now we can say for sure JMS listener will also work for Cloud
On 1st point- we/Pega SME do not have clarity on how Pega 8.7 will support the distributed transaction or provide support to XA driver. We probably need to wait for the product to be released as there is no enough documentation available that can answer this question.