WAS v8.5 > End-to-end paths > Web services - Transaction support (WS-Transaction) > Use WS-Transaction policy to coordinate transactions or business activities for web services > WS-Transaction
Web services transactions, high availability, firewalls and intermediary nodes
We 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, we can distribute web service applications that use WS-AT or WS-BA across disparate systems.
The topologies available to you are as follows:
- Direct connection
-
No intermediary node exists in this topology. The client communicates directly with the specificWAS on which the target service is hosted.
- HTTP server, such as IBM HTTP Server
-
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 WAS. 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 WAS.
Transactional integrity is assured, because recovery processing occurs after the failed server restarts.
Related concepts:
Use WS-Transaction policy to coordinate transactions or business activities for web services
Related
Configure an intermediary node for web services transactions
Enable WAS to use an intermediary node for web services transactions
Install and configure web server plug-ins
Configure transaction properties for an application server
Reference:
Provide HTTP endpoint URL information