2 phase commit and Rollback using EAI Transaction Service
(Doc ID 480926.1)
Last updated on MARCH 01, 2018
Applies to:Siebel System Software - Version 7.5.2 SIA  and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2  Fin Svcs
Database: Oracle 18.104.22.168
Application Server OS: Microsoft Windows 2000 Advanced Server SP 2
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-952439851.
***Checked for relevance on 28-OCT-2013***
Customer is using business service EAI Transaction Service. When a record is being updated or inserted by user at the Siebel end, BeginTransaction will be invoked during BusComp_PreWriteRecord event. BusComp_WriteRecord event will fire a custom workflow to query Siebel table for the changed data and construct a XML to be sent to the backend to update the legacy system. When the reply from the backend is received, depending on the reply status, the system will have to be committed or rollback accordingly by invoking EndTransaction.
Customer had few questions about implementation:
1) By using EAI Transaction Service, is the data actually being committed to the database at the point of BusComp_WriteRecord (before EndTransaction is executed)?
2) Can we assume that the changes is only committed at that particular session only until we call EndTransaction?
3) Customer had further question of updating few fields in Siebel received from the external system
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document