Transaction service settings

Use this page to modify transaction service settings.

To view this administrative console page, click Servers > Application Servers > server > Transaction Service.

Transaction log directory

Specifies the name of a directory for this server where the transaction service stores log files for recovery.

A blank value in the server configuration is expanded by the transaction log at startup as the directory (install_root)/tranlog/(server_name).

When an application running on WebSphere Application Server accesses more than one resource, Application Server stores transaction information within the product directory to properly coordinate and manage the distributed transaction. In a higher transaction load, this persistence slows down performance of the application server due to its dependency on the operating system and the underlying storage systems. To achieve better performance, designate a new directory for the log files on a separate, physically larger storage system.

Set this property to change your log file directory when the application server shows one or more of following signs:

File system recommendations:

Data type String
Default Initial value is the %WAS_HOME%/tranlog/(server_name) directory and a default size of 1MB.
Recommended Create a file system with at least 3-4 disk drives raided together in a RAID-0 configuration. Then, create the transaction log on this file system with the default size. When the server is running under load, check the disk input and output. If disk input and output time is more then 5%, consider adding more physical disks to lower the value. If disk input and output is low, but the server is still high, consider increasing the size of the log files.

Total transaction lifetime timeout

Specifies the maximum duration, in seconds, for transactions on this application server.

Any transaction that is not requested to complete before this time-out is rolled back. If set to 0, transactions never time out.

Data type Integer
Units Seconds
Default 120
Range 0 to 2 147 483 647

Client inactivity timeout

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 rolling back in this application server. If set to 0, there is no timeout limit.

Data type Integer
Units Seconds
Default 60
Range 0 to 2 147 483 647

Enable logging for heuristic reporting

Select this property to enable the application server to log "about to commit one-phase resource" events from transactions that involve 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- and two-phase commit resources. No additional records are written for transactions that do not involve a one-phase commit resource.

Data type String
Default Cleared
Range
Cleared
The application server does not log "about to commit one-phase resource" events from transactions that involve a one-phase commit resource and two-phase commit resources.
Selected
The application server does log "about to commit one-phase resource" events from transactions that involve a one-phase commit resource and two-phase commit resources.

Related tasks
Tuning performance parameter index
Related reference
Administrative console buttons
Administrative console page features



Searchable topic ID:   Transaction_service
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/udat_contranserv.html

Library | Support | Terms of Use | Feedback