You can configure application servers so that transaction messages are sent and received between application servers at different versions of WebSphere® Application Server. Depending on the version of the application server, you can set system properties, or use the transaction coordination authorization setting.
The transaction manager in WebSphere Application Server 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.
When administrative security is enabled, the transaction manager is configured by default for use in the Common Criteria EAL4 evaluated configuration.
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.
In this information ...Related concepts
Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |