Configure Web service atomic transactions

Before you begin

You must install a Web service before you can configure atomic transactions. See Install a Web service.

Note: This section applies to JAX-WS Web services only.

WebLogic Web services enable interoperability with other external transaction processing systems, such as Websphere, JBoss, Microsoft .NET, and so on, through the support of the following specifications: WS-AtomicTransaction Version 1.2 and WS-Coordination Version 1.2.

These specifications define an extensible framework for coordinating distributed activities among a set of participants. The coordinator is the central component, managing the transactional state (coordination context) and enabling Web services and clients to register as participants.

At development time, you can enable Web services atomic transactions using the @weblogic.wsee.wstx.wsat.Transactional annotation in the JWS file or client application, or by passing the weblogic.wsee.wstx.wsat.TransactionalFeature as a parameter when creating the Web service client. For more information about these annotations, see "Using Web Service Atomic Transactions" in Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server.

At deployment time, you can configure Web service atomic transaction properties at the domain, Web service endpoint, and Web service operation levels.

At the domain level, you set properties to configure the atomic transaction coordinator and participant, including:

Flag specifying whether two-way SSL is used for the message exchange between coordinator and participant. If enabled, WebLogic Server must support SSL and use certificates.
Flag specifying whether to use issuedtoken to enable mutual authentication between the WS-AT coordinator and participant.

At the Web service endpoint or operation level, you can enable Web service atomic transactions, and configure the following information:

Version: Version of the Web service atomic transaction coordination context that is used for Web services and clients. For clients, it specifies the version used for outbound messages only. The value specified must be consistent across the entire transaction.
Valid values include WSAT 10, WSAT 11, and WSAT 12, and Default. The Default value for Web services is all three versions (driven by the inbound request); the Default value for Web service clients is WSAT 10.

Flow type: Flag that specifies whether the coordination context is passed with the transaction flow.

The following table summarizes the valid values and their meaning on the Web service and client. The table also summarizes the valid value combinations when configuring Web service atomic transactions for an EJB-style web service that uses the @TransacationAttribute annotation.

Value	Web Service Client	Web Service	Valid EJB @TransacdtionAttribute Values
`Never`	JTA Transaction: Do not export transaction coordination context. No JTA Transaction: Do not export transaction coordination context.	Transaction flow exists: Do not import transaction coordination context. If the CoordinationContext header contains `mustunderstand="true"`, a SOAP fault is thrown. No JTA Transaction: Do not import transaction coordination context.	`NEVER`, `NOT_SUPPORTED`, `REQUIRED` `REQUIRES_NEW, SUPPORTS`
`Supports` (Default)	JTA Transaction: Export transaction coordination context. No JTA Transaction: Do not export transaction coordination context.	Transaction flow exists: Import transaction context. No JTA Transaction: Do not import transaction coordination context.	`SUPPORTS`, `REQUIRED`
`Mandatory`	JTA Transaction: Export transaction coordination context. No JTA Transaction: An exception is thrown.	Transaction flow exists: Import transaction context. No JTA Transaction: Service-side exception is thrown.	`MANDATORY`, `REQUIRED, SUPPORTS`

For more information about Web service atomic transactions, see "Using Web Service Atomic Transactions" in Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server.

The following steps describe how to configure Web services atomic transactions:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
To secure messages exchanged between the coordinator and participant (at the domain level):
1. In the left pane of the Administration Console, select the name of the domain that you want to configure.
2. In the right pane, select the JTA tab.
3. Expand the Advanced properties.
4. Set the following flags to configure the atomic transaction coordinator and participant, as desired:
  - Web Service Transactions Transport Security Mode
  - Web Service Transactions Issued Token Enabled
5. Click Save.
To enable and configure Web service atomic transactions (at the Web service or client endpoint or operation level):
1. In the left pane of the Administration Console, select Deployments.
2. In the right pane, navigate within the Deployments table until you find the Web service or client for which you want to view the configuration.
  Note: Web services are deployed as part of an Enterprise application, Web application, or EJB. To understand how Web services are displayed in the Administration Console, see View installed Web services.
3. In the Deployments table, click the name of the Web service or client.
4. Select Configuration > Ports, and then click the name of the endpoint or operation for the Web service or client that you want to configure.
5. (Web service or client endpoint page only) Select the Atomic Transaction tab.
6. Click Customize Atomic Transactions Configuration.
7. Click Enabled to enable Web services atomic transactions.
8. Set the Flow Type and Version properties, as required.
9. Click Save.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).

Administration Console Online Help

Configure Web service atomic transactions