Question
Ford Motor Private Limited
IN
Last activity: 7 Feb 2024 12:46 EST
Distributed transaction support in Pega cloud migration
Dear Team,
We have an application which saves and commits data simultaneously in 2 databases - PegaRULES DB and application DB. As of now both these DB are in on prem environment. Going forward there is a plan to migrate to Pega cloud by which one of the DB will be hosted in Pega cloud and the other in GCP. In this scenario, kindly let us know how the 2 phase commit (distributed transaction) will be handled by Pega.
Pega application version - Pega 8.8
Application deployment file - WAR
Please advise.
Thanks,
Vignesh.
***Edited by Moderator Rupashree to add Capability tags***
Accepted Solution
Updated: 22 Feb 2024 5:00 EST
Pegasystems Inc.
GB
@Vignesh Amarnathan In a distributed environment, Pega supports two-phase commit (distributed transaction) through Java Transaction API (JTA). This feature is available when Pega is installed as an Enterprise tier application and the XA version of JDBC database drivers are installed. The Commit and Rollback methods apply to both internal and external classes, implementing a Java EE distributed transaction.
However, the specifics of how this would work in a hybrid cloud environment, with one database in Pega Cloud and the other in GCP, may depend on the specific configurations and capabilities of these platforms. It's recommended to consult with Pega Cloud services and GCP for detailed guidance.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Commit method > Java EE two-phase Commit support { .section}
Support for Distributed Transaction in Pega 8.7
If you need further help, please log a cloud ticket.
Ford Motor Private Limited
IN
@MarijeSchillern, Thank you for the response.