Syntax:
com.ibi.agents.XDTxAgent
iIT Service Object:
operations: Transaction Completion Registration
Description:
This service registers process flows to be executed at commit or rollback instances of the local transaction. These process flows can include compensating logic when an application interacts with non-transactional systems. Input to the process flow will be a copy of input to this service. Any user-defined parameters will be available to the process flow as Special Registers (SREGs) in the process flow scope.
Parameters:
|
Parameter |
Description |
|---|---|
|
Rollback Flow |
Process flow to execute if the local transaction is rolled back. This process flow must be published to the system level of the current configuration. |
|
Commit Flow |
Process flow to execute if the local transaction is committed. This process flow must be published to the system level of the current configuration. |
Services capable of supporting transaction commit/rollback in a process flow automatically respond the success of failure of the process flow as a whole by issuing a commit or rollback accordingly. Examples of such services are the SQL service, MQ Read service, and the MQ Emit service. Other services do not so respond to commit or rollback, either because the underlying service (for example, a Siebel system) does not support transactionality or the operation required must rely on application logic. In such a situation, your flow can register a process flow to be run at transaction commit/rollback (end of the process flow) appropriate to the transactional status. For the most common case (handling a failure by rolling back activity) this is usually referred to as a compensating transaction.
You can register one or more compensating or committing transactions by using the XDTxAgent. Each use will register an event process flow for rollback and/or commit handling. The process flow must be deployed as a system process flow to the configuration/application.
On entry, the process flow will be given the input document that was in effect when the registration service registered the event flow.
You can also enter user variables (Special Registers) to the service, which will be available as flow-level registers when the commit or rollback event flow is invoked. The value seen by the process flow will be the current set that is defined during the registration for that flow.
Edges:
The following table lists the available line edges for the Transaction Completion Registration Service (com.ibi.agents.XDTxAgent).
|
Line Edge |
Description |
|---|---|
|
OnError |
Error |
|
OnSuccess |
Success |
|
OnFailure |
Failure |
|
OnCustom |
|