Configure a JAX-WS client for WS-Transaction context
We can configure the way that a JAX-WS client handles Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) context by configuring the Web Services Transaction (WS-Transaction) policy type. We can specify that the client must send context, can send context if it is available, or must not send context.
A JAX-WS client must be installed.
We can configure a WS-Transaction policy set using the administrative console, as described in this task, or we can configure a WS-Transaction policy set using wsadmin.sh.
To configure a JAX-WS client for WS-Transaction context using the administrative console.
Tasks
- Create a new policy set, or copy and rename an existing policy set. We can copy an existing user-defined policy set, or one of the WS-Transaction default policy sets (WSTransaction or SSL WSTransaction). See Create policy sets .
- Check that your policy set includes the WS-Transaction policy type. If necessary, add the WS-Transaction policy type. See Add policies to policy sets .
- Configure the WS-Transaction policy.
- Associate the policy set with the JAX-WS client. See Manage policy sets and bindings for service clients.
- Choose a WS-Policy application rule that includes the configured policy of the client, that is, client only or client and provider. See Configure the client policy to use a service provider policy.
- Save changes to the master configuration.
The JAX-WS client is configured to use WS-Transaction context in the way specified.
Related:
WSTransaction default policy sets Web Services Atomic Transaction support in the application server Web Services Business Activity support in the application server Configure a JAX-WS web service for WS-Transaction context Configure a WS-Transaction policy set by Create policy sets Add policies to policy sets Configure the WS-Transaction policy Manage policy sets and bindings for service clients at the application level Configure the client policy to use a service provider policy