WS-Transaction policy settings
Use this page to specify the policies for the WS-AtomicTransaction (WS-AT) and WS-BusinessActivity (WS-BA) protocols. WS-AT supports coordination of activities so that either all the activities occur, or none of them occur. WS-BA supports coordination of activities that are more loosely coupled than atomic transactions, and that therefore, require a compensation process if an error occurs.
To view this page in the console, click the following path: , when the policy set includes the WS-Transaction policy type.
You can configure the WS-Transaction policy type for both client and provider policy sets.
WS-AtomicTransaction
- Mandatory
- For a client, the client always propagates a WS-AT context on
an outbound request. If there is no transaction on the thread when
the request is made, the attempt to make the request fails.
For a server, any request that is received must include a WS-AT context, otherwise the request is rejected. If any Web Services Description Language (WSDL) is generated for the web service with which the policy type is associated, a policy assertion is included that indicates that an operation must be invoked with an atomic transaction context.
- Supports
- For a client, the client can propagate a WS-AT context on an outbound
request when it is available. For example, a transaction is associated
with the thread that makes the request, and the policy of the provider
requires WS-AT context.
For a server, if a request includes a WS-AT context, the context is imported and established on the thread before the request is processed. If a request does not include a WS-AT context, the request is processed as usual. If any WSDL is generated for the web service with which the policy type is associated, a policy assertion is included that indicates that an operation supports invocation with an atomic transaction context when that context is available.
- Never
- For a client, the client never propagates a WS-AT context on an
outbound request.
For a server, any request that is received must not include a WS-AT context, otherwise the request is rejected with a MustUnderstand error. If any WSDL is generated for the web service with which the policy type is associated, that WSDL does not include a policy assertion for an atomic transaction context.
WS-BusinessActivity
- Mandatory
- For a client, the client always propagates a WS-BA context on
an outbound request. If there is no business activity scope on the
thread when the request is made, the attempt to make the request fails.
For a server, any request that is received must include a WS-BA context, otherwise the request is rejected. If any WSDL is generated for the web service with which the policy type is associated, a policy assertion is included that indicates that an operation must be invoked with a business activity context.
- Supports
- For a client, the client can propagate a WS-BA context on an outbound
request when it is available. For example, a business activity scope
is associated with the thread that makes the request, and the policy
of the provider requires a WS-BA context.
For a server, if a request includes a WS-BA context, the context is imported and established on the thread before the request is processed. If a request does not include a WS-BA context, the request is processed as usual. If any WSDL is generated for the web service with which the policy type is associated, a policy assertion is included that indicates that an operation supports invocation with a business activity context when that context is available.
- Never
- For a client, the client never propagates a WS-BA context on an
outbound request.
For a server, any request that is received must not include a WS-BA context, otherwise the request is rejected with a MustUnderstand error. If any WSDL is generated for the web service with which the policy type is associated, that WSDL does not include a policy assertion for a business activity context.