You can configure your system to enable propagation of Web Services Atomic Transactions (WS-AT) message contexts and Web Service Business Activities (WS-BA) message contexts across firewalls or outside the WebSphere Application Server domain. With these configurations, you can distribute Web service applications that use WS-AT or WS-BA across disparate systems.
No intermediary node exists in this topology. The client communicates directly with the specific WebSphere Application Server on which the target service resides.
In this topology, the client communicates with an HTTP server, which always routes the client requests and Web services transaction protocol messages to a specific WebSphere Application Server. As for any HTTP proxy configuration, you must provide HTTP endpoint URL information, that is, configure the HTTP server URL prefix for the target Web service module. Also, typically you need to configure the HTTP server for Web services transactions, that is, configure it to deliver Web services transaction protocol messages to the appropriate WebSphere Application Server. To do this, configure the transaction service HTTP proxy prefix, which is described in the topic about enabling WebSphere Application Server to use an intermediary node for Web services transactions.
Transactional integrity is assured, because recovery processing occurs after the failed server restarts.