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
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:
At the Web service endpoint or operation level, you can enable Web service atomic transactions, and configure the ffollowing information:
Valid values include
WSAT 12, and
Default value for Web
services is all three versions (driven by the inbound request); the
Default value for Web service clients is
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
|Value||Web Service||Web Service Client||Valid EJB @TransacdtionAttribute Values|
||Do not export coordination context.||Do not import coordination context.||
||Export coordination context.||Import coordination context.||
||Export coordination context. An exception is thrown if there is no active transaction.||Import coordination context.||
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:
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.