Use WS-Transaction policy to coordinate transactions or business activities for web services
We can use WS-Transaction policy to configure how a JAX-WS service or client handles Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) context.
The Web Services Atomic Transaction (WS-AT) support in the application server provides transactional quality of service to the web services environment. Distributed web services applications, and the resources they use, can take part in distributed global transactions. With Web Services Business Activity (WS-BA) support in the application server, web services on different systems can coordinate activities that are more loosely coupled than atomic transactions. Such activities can be difficult or impossible to roll back atomically, and therefore require a compensation process if an error occurs.
- Configure a JAX-WS client for WS-Transaction context.
- Configure a JAX-WS web service for WS-Transaction context.
- Configure the WS-Transaction policy.
- Configure a WS-Transaction policy set by .
- Configure transaction properties for an application server.
- Configure the WS-Transaction specification level by .
- Configure WS-Transaction support in a secure environment.
- Configure an intermediary node for web services transactions.
- Enable WebSphere Application Server to use an intermediary node for web services transactions.
- Configure a server to use business activity support.
Subtopics
- WS-Transaction
WS-Transaction is an interoperability standard that includes the WS-AtomicTransaction, WS-BusinessActivity, and WS-Coordination specifications. Use these topics to learn more about WS-Transaction.
- Use WS-Transaction policy to coordinate transactions or business activities for web services
We can use WS-Transaction policy to configure how a JAX-WS service or client handles Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) context.
- Create an application that uses the Web Services Business Activity support
To create an application component that uses the business activity support, set Run EJB methods under a Business Activity scope in the deployment descriptor of the relevant application component, and if required, create and specify a compensation handler for the application to use if there is an error. You then build the component into the application and deploy the application onto a server that has the business activity support enabled. The application component can be either an enterprise bean or a web service that is implemented as an enterprise bean.
- 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.
- Configure a JAX-WS web service for WS-Transaction context
We can configure the way that a JAX-WS service 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 web service must receive context, can receive context if it is available, or must not receive context.
- Configure a WS-Transaction policy set by
We can configure the way that a JAX-WS client or web service 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 or service must use context, can use context if it is available, or must not use context. Use command scripts to configure a policy set for web services transactions.
- Configure Web Services Transaction support in a secure environment
If we use Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) support when administrative security is enabled, we might have to change the default transaction service configuration. We can disable the transaction coordination authorization setting, create a new web container transport chain, or do both.
- Configure an intermediary node for web services transactions
Intermediary nodes allow the exchange of Web Services Atomic Transaction (WS-AT) and Web Services Business Activity (WS-BA) protocol messages across firewalls and outside the WAS domain. You configure an intermediary node to specify which WebSphere Application servers the node routes requests to.
- Enable WebSphere Application Server to use an intermediary node for web services transactions
We can use intermediary nodes with Web Services Atomic Transactions (WS-AT) or Web Services Business Activities (WS-BA) to support the exchange of associated requests across firewalls and outside the WAS domain. You configure WebSphere Application Server to use an intermediary node by specifying the external endpoint URL information for the intermediary node in each server that is accessed through the intermediary.
- Configure a server to use business activity support
Business activity support provides compensation for activities such as sending an email, which can be difficult or impossible to roll back atomically. With this compensation, applications on disparate systems can coordinate activities that are more loosely coupled than atomic transactions. To use the business activity support, first enable it on each server to use.
Related tasks
WS-Transaction Configure the WS-Transaction policy Configure transaction properties for an application server Configure the WS-Transaction specification level by Create an application that uses the Web Services Business Activity support
WS-Transaction policy settings Transaction service settings