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
.For the z/OS® platform, specifies the location of the JTA Partner Log.
In a high availability (HA) environment, both the transaction log and the compensation log directory for each server in a cluster must be unique.
On z/OS, this log is used for recovery of XA resources. When the application that runs on the WebSphere® product accesses XA resources, the WebSphere product stores information about the resource to enable XA transaction recovery. Use the following syntax:
The default is dir://app_server_root/tranlog/server name.
To specify the size of transaction log files, include a file size setting. Use one of the following formats, where directory_name is the name of the transaction log directory and file_size is the new disk space allocation for the transaction log files, specified in KB (nK) or MB (nM). The minimum transaction log file size that you can specify is 64K. If you specify a value that is less than 64K, or you do not specify a value for the file size, the default value of 1M is used.
dir://directory_name/directory_name;file_sizeK
/directory_name/directory_name;file_sizeK
;file_sizeK <!-- This keeps the default directory -->
If you migrate a WebSphere Application Server Version 5 node to Version 6, the stored location of this configuration property is moved from the server level to the node (server index) level. If you specified a non-default log directory for a Version 5 application server, you are prompted to save the transaction service settings again, to confirm that you want the log directory saved to the node level.
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 | 0 to 2 147 040 |
Specifies the amount of time, in seconds, that the server waits for an inbound Web Services Atomic Transaction (WS-AT) protocol response before resending the previous WS-AT protocol message.
Data type | Integer |
Units | Seconds |
Default | 30 |
Range | 0 to 2 147 483 647 |
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, in seconds, the upper limit of the transaction timeout for transactions that run in this server. This value should be greater than or equal to the value specified for the total transaction timeout.
Timeout setting | Transactions affected |
---|---|
Maximum transaction timeout | All transactions running in this server that are not affected by the total transaction lifetime timeout or an application component timeout. These transactions include transactions imported from outside this server, such as those imported from a client. |
Total transaction lifetime timeout | All transactions that originated in this server that are not affected by an application component timeout, in other words, the associated application component does not set its own timeout. |
Application component timeout | Transactions that are specific to an application
component. You cannot set this transaction timeout using the administrative console. If the component is a container-managed bean, set this timeout in the deployment descriptor for the component. For example, you can use an assembly tool, such as the Rational® Application Developer. If the component is a bean-managed bean, set this timeout programmatically by using the UserTransaction.setTransactionTimeout method. |
If you set a timeout to 0, that timeout does not apply, and is effectively disabled. If you set all timeouts to 0, transactions never time out.
Timeout setting | Value |
---|---|
Maximum transaction timeout | 360 |
Total transaction lifetime timeout | 240 |
Application component timeout | 60 |
To determine the occurrence of a timeout quickly, and to prevent further resource locking, the application server prevents further transactional work on the transactional path where the timeout condition has taken place. This applies equally to attempting to undertake work under the current transaction context and to attempting to perform work under a different transactional context.
Data type | Integer |
Units | Seconds |
Default | 300 |
Range | 0 to 2 147 040 |
Specifies the number of times that the application server retries a completion signal, such as commit or rollback. Retries occur after a transient exception from a resource manager or remote partner, or if the configured asynchronous response timeout expires before all Web Services Atomic Transaction (WS-AT) partners have responded.
If the application server abandons the retries, the resource manager or remote partner is responsible for ensuring that the resource or partner branch of the transaction is completed appropriately. The application server raises (on behalf of the resource or partner) an exception that indicates a heuristic hazard. If a commit request was made, the transaction originator receives an exception on the commit operation; if the transaction is container-initiated, the container returns a remote exception or Enterprise JavaBeans™ (EJB) exception to the EJB client.
During recovery of a subordinate server in a distributed transaction, when the number of heuristic retries is exceeded, the heuristic completion direction property specifies how the transaction is completed.
Data type | Integer |
Default | 0 |
Range | 0 to 2 147 483 647 A value of 0 (the default) means try again indefinitely. |
Specifies the number of seconds that the application server waits before retrying a completion signal, such as commit or rollback, after a transient exception from a resource manager or remote partner.
Data type | Integer |
Default | 0 |
Range | 0 to 2 147 483 647 If you leave this value at 0, the application server still makes subsequent attempts to complete the transaction. It incrementally lengthens the wait time before each attempt, to improve system throughput. |
Specifies the direction that is used to complete a transaction that has a heuristic outcome; either the application server commits or rolls back the transaction, or depends on manual completion by the administrator.
This property applies only to transactions that are in the situations just described.
Data type | Drop-down list |
Default | ROLLBACK |
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 default WS-Transaction specification level to use for outbound requests that include a Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) coordination context.
You can choose from WS-Transaction 1.0 or WS-Transaction 1.1. For details of these specifications, see the topics about WS-AT support or WS-BA support in the application server.
The default WS-Transaction specification level is used if the specification level that the server requires cannot be determined from the provider policy (the WS-Transaction WS-Policy assertion). For example, the policy assertion is not available, either from the WSDL of the target Web service or from the WS-Transaction policy type of the client, or the policy assertion is available but both specification levels are applicable.
Data type | Drop-down list |
Default | 1.0 |
Select or specify the external WS-Transaction HTTP(S) URL prefix.
Select or specify one of these fields if you are using an intermediary node, such as an HTTP server or Proxy Server for WebSphere, to send requests that comply with the Web Services Atomic Transaction (WS-AT) or Web Services Business Activity (WS-BA) protocols.
If WebSphere Application Server security is enabled and transaction coordination authorization is enabled, the HTTPS prefix is used. Otherwise, the HTTP prefix is used.
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.
Select this option to select the external endpoint URL information to use for WS-AT and WS-BA service endpoints from the list.
Data type | Drop-down list |
Default | None |
Select this option to specify the external endpoint URL information to use for WS-AT and WS-BA service endpoints in the field.
http://host_name:port
https://host_name:port
Data type | String |
Default | None |
Specifies the number of transactions that await manual completion by an administrator.
If there are transactions awaiting manual completion, you can click the Review link to display a list of those transactions on the Transactions needing manual completion panel.
Data type | Integer |
Default | 0 |
Specifies the number of transactions with some resources being retried.
If there are transactions with resources being retried, you can click the Review link to display a list of those transactions on the Transactions retrying resources panel.
Data type | Integer |
Default | 0 |
Specifies the number of transactions that have completed heuristically.
If there are transactions that have completed heuristically, you can click the Review link to display a list of those transactions on the Transactions with heuristic outcome panel.
Data type | Integer |
Default | 0 |
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 |