1.3.3.1 Configuring Incoming Transactions

Oracle Tuxedo services exposed as Web services do not require any specific configuration other than creating a transaction log file and adding it to the GWWS deploy configuration file in order to initiate a local transaction associated with an incoming WS-AT transaction request.

To ensure a transaction can be propagated into an Oracle Tuxedo domain, do the following steps:

  1. Ensure that the Oracle Tuxedo service called supports transactions
  2. Configure a transaction log g file in the GWWS deployment file. For more information, see Configuring Transaction Log Device
  3. Configure a policy file containing a WS-AT Assertion corresponding to the desired behavior with respect to the external Web Service called. For more information, see Configuring Policy Assertions
  4. Incoming calls containing a CoordinationContext element creates an Oracle Tuxedo global transaction.