Interoperating transactionally between application servers

This topic describes some considerations and actions that you can take to interoperate transactionally between different types of application servers.

Overview

WebSphere Application Server is a transaction manager that supports transactional interoperation with other transaction managers through either the CORBA Object Transaction Service (OTS) protocol or, for JSR-109 compliant requests, Web Service Atomic Transaction (WS-AtomicTransaction) protocol. This is in addition to its ability to coordinate XA resource managers and to be coordinated by J2EE Connector 1.5 resource adapters.

Procedure

• To interoperate transactionally, using the OTS protocol, to send requests from application servers that are WebSphere Application Server V5.0.2 or earlier to application servers that are V6 or later, you need to set the following system properties on application servers 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 application servers that are WebSphere Application Server V4.0.n to application servers that are WebSphere Application Server V6, you need to set the system properties on the V4.0.n application servers.

  You do not need to set these properties to receive requests on application servers that are WebSphere Application Server V5.0.2 or earlier from application servers that are V6 or later.

• If you have enabled WebSphere Application Server security, you need to disable protocol security on servers at version 6.0.2 or later to be able to interoperate transactionally with servers at earlier versions.

  To disable protocol security on a server, complete the following steps:

  1. In the administrative console, click Servers > Application Servers > server_name > [Container Settings] Container Services > Transaction Service

  2. Clear the Enable protocol security check box.

  3. Click Apply or OK.

  4. Save your changes to the master configuration.

  5. Restart the server.

Related tasks

Related information