Interoperating transactionally between appservers

Configure appservers so that transaction messages are sent and received between appservers at different versions of WAS. Depending on the version of the appserver, we can set system properties, or use the transaction coordination authorization setting.

The transaction manager in WAS supports transactional interoperation with other transaction managers through either the CORBA Object Transaction Service (OTS) protocol, or, for JSR-109 compliant requests, the Web Services Atomic Transaction (WS-AT) protocol. Also, the transaction manager can coordinate XA resource managers and be coordinated by Java EE Connector Architecture 1.5 resource adapters.

 

• To interoperate transactionally, using the OTS protocol to send requests from appservers that are WAS V5.0.2 or earlier to appservers that are V6 or later, set the following system properties on appservers that are V5.0.2 or earlier.

  com.ibm.ejs.jts.jts.ControlSet.nativeOnly=false com.ibm.ejs.jts.jts.ControlSet.interoperabilityOnly=true
  

  For example, to send requests from appservers that are WAS V4.0.n to appservers that are WAS V 6, set the system properties on the V4.0.n application servers.

  You do not have to set these properties to receive requests on appservers that are WAS V 5.0.2 or earlier from appservers that are V6 or later.

• When administrative security is enabled, the transaction manager is configured by default for use in the Common Criteria EAL4 evaluated configuration. When administrative security is enabled for appservers at WAS V6.0.2 or later, for such servers to interoperate transactionally with appservers at earlier versions, or with non-WAS servers, disable transaction coordination authorization on the server. The transaction coordination authorization setting controls only the transaction protocol messages between servers that are used to coordinate the completion of a transaction. It does not affect application messages or the security of the server. When transaction coordination authorization is enabled, the server verifies that the sending server is authorized to handle prepare, commit, rollback, and one-phase commit messages.

  To disable transaction coordination authorization on a server, use the following steps.

  1. In the admin console ...

     Servers > Server Types > WebSphere application servers > server_name > [Container Settings] Container Services > Transaction Service .

  2. Clear the Enable transaction coordination authorization check box.

  3. Click Apply or OK.

  4. Save the changes to the master configuration.

  5. Restart the server.

 

Related concepts

Web Services Atomic Transaction support in the appserver

 

Related tasks

Moving a transaction log from one server to another
Restarting an appserver on a different host
Use the transaction service

 

Related

Common Criteria (EAL4) support

 

Related information

CORBA Object Transaction Service Java EE Connector Architecture The Java transaction service (JTS) The Java transaction API (JTA)