WS-AT

The two-phase commit protocol is driven by the caller's WS-AT coordinator when it is ready to commit the transaction.

Last but not the least, we'll test the BPEL process in a failing situation to make sure WS-AT works as expected.

As discussed earlier in the article, there is no additional programming effort to use WS-AT, but some configuration may be required.

With the help of WS-AT, all updates are coordinated by a global transaction.

In this example, application SOAP messages and WS-AT transaction message exchanges use different endpoint URLs and TCP ports.

The SOAP message shows the WS-AT headers, which demonstrate the propagation of transaction to the WS interface.

Optionally, enable WebSphere Web services message tracing to verify that WS-AT is working properly.

MSDTC is responsible for transaction management and the handling of WS-AT messages.

In order to show WS-AT in action, we'll use a scenario involving a corporate human resource department.

Figure 12 shows the simple setting you need to enable for WS-AT.

To enable WS-AT, the deployment descriptors for Web and EJB modules must be configured as follows

Step 4: Set up WebSphere security, SSL certificates and transaction service for WS-AT message exchange

Step 5: Import SSL certificates and configure WS-AT in Windows XP