Use this page to specify settings for the transaction service. The transaction service is a server runtime component that can coordinate updates to multiple resource managers to ensure atomic updates of data. Transactions are started and ended by applications or the container in which the applications are deployed.
To view this administrative console page, click
.The default maximum time, in seconds, allowed for a transaction that is started on this server before the transaction service initiates timeout completion. Any transaction that does not begin completion processing before this timeout occurs is rolled back.
This timeout is used only if the application component does not set its own transaction timeout.
The upper limit of this timeout is constrained by the maximum transaction timeout. For example, if you set a value of 500 for the total transaction lifetime timeout, and a value of 300 for the maximum transaction timeout, transactions will time out after 300 seconds.
If you set this timeout to 0, the timeout does not apply and the value of the maximum transaction timeout is used instead.
Data type | Integer |
Units | Seconds |
Default | 120 |
Range |
|
Range |
|
Specifies the maximum duration, in seconds, between transactional requests from a remote client. Any period of client inactivity that exceeds this timeout results in the transaction being rolled back in this application server.
If you set this value to 0, there is no timeout limit.
Data type | Integer |
Units | Seconds |
Default | 60 |
Range | 0 to 2 147 483 647 |
Specifies whether the application server logs about-to-commit-one-phase-resource events from transactions that involve both a one-phase commit resource and two-phase commit resources.
This property enables logging for heuristic reporting. If applications are configured to allow one-phase commit resources to participate in two-phase commit transactions, reporting of heuristic outcomes that occur at application server failure requires extra information to be written to the transaction log. If enabled, one additional log write is performed for any transaction that involves both one-phase and two-phase commit resources. No additional records are written for transactions that do not involve a one-phase commit resource.
Data type | Check box |
Default | Cleared |
Range |
|
Specifies whether all applications on this server accept the possibility of a heuristic hazard occurring in a two-phase transaction that contains a one-phase resource. This setting configures last participant support (LPS) for the server. Last participant support is an extension to the transaction service that enables a single one-phase resource to participate in a two-phase transaction with one or more two-phase resources.
If the Accept heuristic hazard option is not selected, you must configure applications individually to accept the heuristic hazard. You can configure applications either when they are assembled, or following deployment by using the Last participant support extension pane.
Data type | Check box |
Default | Cleared |
Range |
|
Specifies whether the use of file locks is enabled when opening the transaction service recovery log.
Data type | Check box |
Default | Selected |
Specifies whether the secure exchange of transaction service protocol messages is enabled.
This setting has no effect unless you enable WebSphere Application Server security on the server.
Data type | Check box |
Default | Selected |
Specifies the external endpoint URL information that should be used for WS-AtomicTransaction and WS-BusinessActivity service endpoints. This should be in the form http://hostname[:port] where hostname may be the hostname of an HTTP proxy to this server.
http://host_name:portwhere
If the intermediary node is not a Proxy Server, the prefix must be unique for each server. If you are using a Proxy Server, prefixes can be the same for each server in a cluster, because the Proxy Server determines dynamically which server to forward the request to.
The HTTPS prefix will be used if WebSphere Application Server security is enabled and protocol security is enabled for the transaction service, otherwise the HTTP prefix will be used.
Data type | String |
Default | None |
Specifies the external endpoint URL information that should be used for WS-AtomicTransaction and WS-BusinessActivity service endpoints. This should be in the form https://hostname[:port] where hostname may be the hostname of an HTTPS proxy to this server.
https://host_name:portwhere
If the intermediary node is not a Proxy Server, the prefix must be unique for each server. If you are using a Proxy Server, prefixes can be the same for each server in a cluster, because the Proxy Server determines dynamically which server to forward the request to.
The HTTPS prefix will be used if WebSphere Application Server security is enabled and protocol security is enabled for the transaction service, otherwise the HTTP prefix will be used.
Data type | String |
Default | None |
The default maximum time, in seconds, allowed for a transaction that is started on this server before the transaction service initiates timeout completion. Any transaction that does not begin completion processing before this timeout occurs is rolled back.
This timeout is used only if the application component does not set its own transaction timeout.
The upper limit of this timeout is constrained by the maximum transaction timeout. For example, if you set a value of 500 for the total transaction lifetime timeout, and a value of 300 for the maximum transaction timeout, transactions will time out after 300 seconds.
If you set this timeout to 0, the timeout does not apply and the value of the maximum transaction timeout is used instead.
Data type | Integer |
Units | Seconds |
Default | 120 |
Range |
|
Range |
|
Specifies the maximum duration, in seconds, between transactional requests from a remote client. Any period of client inactivity that exceeds this timeout results in the transaction being rolled back in this application server.
If you set this value to 0, there is no timeout limit.
Data type | Integer |
Units | Seconds |
Default | 60 |
Range | 0 to 2 147 483 647 |
Specifies the number of transactions that are imported and prepared but not yet committed.
If there are transactions that have been imported and prepared but not yet committed, you can click the Review link to display a list of those transactions on the Transactions imported and prepared panel.
Data type | Integer |
Default | 0 |