Transaction service settingsUse this page to modify transaction service settings.
To view this administrative console page, click Servers > Application Servers > server > Transaction Service.
Configuration tab
A blank value in the server configuration is expanded by the transaction log at startup as the directory (install_root)/tranlog/(server_name).
When the application running on the WebSphere product accesses more than one resource, the WebSphere product stores transaction information 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, move the transaction log files to a storage device with more physical disk drives, or preferably RAID disk drives. When the log files are moved to the file systems on such disks, the task of writing data to the physical media is shared across the multiple disk drives. This allows more concurrent access to persist transaction information and faster access to that data from the logs. Depending upon the design of the application and storage subsystem, performance gains can range from 10% to 100%, or even more in some cases.
Consider setting this property when the application server shows one or more of following signs:
| 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. |
Any transaction that is not requested to complete before this time-out is rolled back. If set to 0, there is no time-out limit.
| Data type | Integer |
| Units | Seconds |
| Default | 120 |
| Range | 0 to 2 147 483 647 |
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 |
Runtime tab
A blank value in the server configuration is expanded by the transaction log at startup as the directory (install_root)/tranlog/(server_name).
When the application running on the WebSphere product accesses more than one resource, the WebSphere product stores transaction information 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, move the transaction log files to a storage device with more physical disk drives, or preferably RAID disk drives. When the log files are moved to the file systems on such disks, the task of writing data to the physical media is shared across the multiple disk drives. This allows more concurrent access to persist transaction information and faster access to that data from the logs. Depending upon the design of the application and storage subsystem, performance gains can range from 10% to 100%, or even more in some cases.
Consider setting this property when the application server shows one or more of following signs:
| 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. |
Any transaction that is not requested to complete before this time-out is rolled back. If set to 0, there is no time-out limit.
| Data type | Integer |
| Units | Seconds |
| Default | 120 |
| Range | 0 to 2 147 483 647 |
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 |