Configuring Web Services Transaction support in a secure environment
If you use Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) support when administrative security is enabled, you might have to change the default transaction service configuration. You can disable the transaction coordination authorization setting, create a new web container transport chain, or do both.
About this task
You might disable transaction coordination authorization if you want to interoperate with other servers, but you do not want to use the transaction manager in the Common Criteria EAL4 evaluated configuration (the default when administrative security is set). When transaction coordination authorization is disabled, WebSphere® Application Server does not automatically reject secure WS-Transactions protocol messages.
You might disable transaction coordination authorization if you want to interoperate with other servers and you do not want to set up security for the transaction manager to support the Common Criteria EAL4 evaluated configuration. When transaction coordination authorization is disabled, WebSphere Application Server does not automatically reject secure WS-Transactions protocol messages.
- You want to use an alternative port number for WS-AT or WS-BA protocol messages.
- You want to interoperate with a non-WebSphere Application Server that requires client certificate authentication on the Secure Sockets Layer (SSL) connection that is used for protocol messages.