+

Search Tips   |   Advanced Search

Configure the WS-Transaction specification level using wsadmin.sh

We can configure the default WS-Transaction specification level to use for outbound requests that include a Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) coordination context.

The product supports the WS-Transaction 1.0, the WS-Transaction 1.1 and the WS-Transaction 1.2 specifications, but when an outbound request is sent, only one specification level can be used. The default WS-Transaction specification level is used if the specification level that the server requires cannot be determined from the provider policy (the WS-Transaction WS-Policy assertion). This situation might occur when the policy assertion is not available either from the WS-Transaction policy type of the client or from the WSDL of the target web service. Also, this situation might occur when the policy assertion is available, but the client and the target web service support both specification levels.

For details of the specifications, see the topics about Web Services Atomic Transaction support and Web Services Business Activity support in the application server.

We can set the default WS-Transaction specification level using wsadmin.sh, as described in this task, or using the administrative console and configuring the relevant transaction property for the application server.


Tasks

  1. Start the wsadmin scripting client if it is not already running.

  2. Retrieve the configuration ID of the transaction service. In Jacl, use the following code example: 
    set txService $AdminConfig list TransactionService
    In Jython, use the following code example: 
    txService = AdminConfig.list("TransactionService")

  3. Modify the WSTransactionSpecificationLevel attribute to the value you require. In Jacl, to configure the server to use WS-Transaction 1.1, use the following code example: 
    $AdminConfig modify $txService {{WSTransactionSpecificationLevel WSTX_11}}
    In Jython, to configure the server to use WS-Transaction 1.0, use the following code example: 
    AdminConfig.modify ($txService,[["WSTransactionSpecificationLevel", "WSTX_10"]])

  4. Save the configuration changes with the wsadmin tool.

  5. Optional: In a network deployment environment only, synchronize the node using the wsadmin tool.

We have configured the default WS-Transaction specification level for the server.


Related:

  • Web Services Atomic Transaction support in the application server
  • Web Services Business Activity support in the application server
  • Save wsadmin configuration changes
  • Synchronize nodes
  • Configure transaction properties for an application server
  • Use WS-Transaction policy to coordinate transactions or business activities for web services