In the Metadata Exchange Enabled field, select True from the menu to enable the

Administering Web Services 6-21 Configuring Web Services Atomic Transactions WebLogic Web services support the WS-Coordination and WS-AtomicTransaction WS-AT specifications. Therefore, you can configure Web services atomic transactions to enable interoperability between Oracle WebLogic Server and other vendor’s transaction processing systems, such as WebSphere, JBoss, Microsoft .NET, and so on. Web services atomic transactions are supported for WebLogic JAX-WS Web services and SOA Web services and references. You can enable and configure Web services atomic transactions at design time as described in the following topics: ■ Using Web Services Atomic Transactions in Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server ■ WS-Atomic Transaction Support in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite For WebLogic JAX-WS Web services, you can configure Web services atomic transactions at deployment time using the WebLogic Server Administration Console. For more information, see Configure Web service atomic transactions in the Oracle WebLogic Server Administration Console Help. For SOA Web services and references, you can configure Web services atomic transactions at deployment time, on the service or reference endpoint, using Oracle Enterprise Manager Fusion Middleware Control or WLST. Refer to the following sections for detailed procedures using both interfaces. For information about configuring Web service atomic transactions for SOA references, see Configuring the Web Service Client on page 6-27. Using Fusion Middleware Control To configure atomic transactions for a SOA Web service:

1. Navigate to the SOA composite home page as described in

Viewing the Web Services and References in a SOA Composite on page 6-6.

2. In the Services and References section of the page, select the service to be

configured.

3. In the Service Home page, click the Properties tab.

4. In the Atomic Transaction Version field, select the version of the Web service

atomic transaction coordination context that is supported for the SOA service. The value specified must be consistent across the entire transaction. Valid values are: ■ WSAT10 ■ WSAT11 ■ WSAT12 Note: You need to wait approximately 30 seconds or the equivalent of the configured Graceful Shutdown Timeout time between stopping and restarting the application. During this time, the server is allowing all global transactions to complete before shutting down the application. If you do not wait the configured Graceful Shutdown Timeout time, then the application will not be restarted appropriately and you will not be able to access it. To avoid waiting the graceful shutdown timeout period, you can restart the application twice.