Question
Softdel
IN
Last activity: 24 Apr 2018 20:44 EDT
Two phase commit in pega
What is two phase commit in pega and how it is supported?
Accepted Solution
EPAM Systems, Inc.
ES
Hi Sanjeev,
Thanks for posting on PSC.
A two-phase commit capability is a Java Transaction API (JTA) feature supporting distributed transactions.
When PRPC 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.
For example, a flow may update tables in the external relational database such as a customer master file, and also update assignments and properties in the work item. If when the Commit method occurs either the PegaRULES database or the customer master database operation fails, a rollback occurs automatically.
For more information, see Distributed Transactions and PegaRULES Process Commander, a document on the PDN.
Refer this:-https://community.pega.com/sites/default/files/help_v71/procomhelpmain.htm
For ex in Pega, Two-phase could be demonstrated as work object/transactions aren't persisted immediately to the database by methods like saved by Obj-Save or Obj-Delete/Obj-Delete-By-Handle.
Though, if you have the configuration, it will persist immediately.
Hi Sanjeev,
Thanks for posting on PSC.
A two-phase commit capability is a Java Transaction API (JTA) feature supporting distributed transactions.
When PRPC 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.
For example, a flow may update tables in the external relational database such as a customer master file, and also update assignments and properties in the work item. If when the Commit method occurs either the PegaRULES database or the customer master database operation fails, a rollback occurs automatically.
For more information, see Distributed Transactions and PegaRULES Process Commander, a document on the PDN.
Refer this:-https://community.pega.com/sites/default/files/help_v71/procomhelpmain.htm
For ex in Pega, Two-phase could be demonstrated as work object/transactions aren't persisted immediately to the database by methods like saved by Obj-Save or Obj-Delete/Obj-Delete-By-Handle.
Though, if you have the configuration, it will persist immediately.
Obj-Save-Tick the WriteNow option
Obj-Delete & Obj-Delete-By-Handle- Tick the Immediate option
Hope it answers your query, kindly notify it by marking this post as answered.
Regards,
Asif
Pegasystems Inc.
IN
Hi Sanjeev,
Two phase commit is generic term and not specific to pega.
Some more info can be seen here https://collaborate.pega.com/question/two-phase-commit-pega
Thanks,
Ujjwal
Accepted Solution
EPAM Systems, Inc.
ES
Hi Sanjeev,
Thanks for posting on PSC.
A two-phase commit capability is a Java Transaction API (JTA) feature supporting distributed transactions.
When PRPC 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.
For example, a flow may update tables in the external relational database such as a customer master file, and also update assignments and properties in the work item. If when the Commit method occurs either the PegaRULES database or the customer master database operation fails, a rollback occurs automatically.
For more information, see Distributed Transactions and PegaRULES Process Commander, a document on the PDN.
Refer this:-https://community.pega.com/sites/default/files/help_v71/procomhelpmain.htm
For ex in Pega, Two-phase could be demonstrated as work object/transactions aren't persisted immediately to the database by methods like saved by Obj-Save or Obj-Delete/Obj-Delete-By-Handle.
Though, if you have the configuration, it will persist immediately.
Hi Sanjeev,
Thanks for posting on PSC.
A two-phase commit capability is a Java Transaction API (JTA) feature supporting distributed transactions.
When PRPC 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.
For example, a flow may update tables in the external relational database such as a customer master file, and also update assignments and properties in the work item. If when the Commit method occurs either the PegaRULES database or the customer master database operation fails, a rollback occurs automatically.
For more information, see Distributed Transactions and PegaRULES Process Commander, a document on the PDN.
Refer this:-https://community.pega.com/sites/default/files/help_v71/procomhelpmain.htm
For ex in Pega, Two-phase could be demonstrated as work object/transactions aren't persisted immediately to the database by methods like saved by Obj-Save or Obj-Delete/Obj-Delete-By-Handle.
Though, if you have the configuration, it will persist immediately.
Obj-Save-Tick the WriteNow option
Obj-Delete & Obj-Delete-By-Handle- Tick the Immediate option
Hope it answers your query, kindly notify it by marking this post as answered.
Regards,
Asif