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

WS-Transaction and mixed-version cells

You must consider WS-Transaction policy type enablement and behavior, and the WS-Transaction specification level to use, when a cell contains servers at different versions; for example, WebSphere Application Server v7.0 or later and WAS v6.1 Feature Pack for Web Services.


WS-Transaction policy type enablement

For a v6.1 Feature Pack for Web Services server, we can enable the WS-Transaction policy type by including it in a policy set, but we cannot configure it. For a v7.0 or later server, we can both enable and configure the WS-Transaction policy type. Configuration information is written to the WS-Transaction policy type file.

In a cell with both v6.1 Feature Pack for Web Services and v7.0 or later servers, the following behavior occurs:


WS-Transaction specification level

WAS supports the WS-Transaction 1.0, WS-Transaction 1.1 and WS-Transaction 1.2 specifications. In practice, version 1.2 of the WS-Transaction standard is functionally equivalent to version 1.1, so within WAS, wherever WS-Transaction 1.1 is supported, WS-Transaction 1.2 is also.

A WAS v6.x server supports WS-Transaction 1.0. A v7.0 or later server supports WS-Transaction 1.0, 1.1 and 1.2.

No special restrictions apply to a cell with both v6.x and v7.0 or later servers.


Related concepts:

Use WS-Transaction policy to coordinate transactions or business activities for web services


Reference:

WS-Transaction policy settings
Transaction service settings


+

Search Tips   |   Advanced Search