Configure transaction properties for an appserver
To configure the transaction properties for an appserver, go to:Console | Servers | Manage Local Server | Transaction Service
Configuration The values of properties defined in the configuration file. If you change these properties, the new values are applied when the appserver next starts.
Runtime The runtime values of properties. If you change these properties, the new values are applied immediately, but are overwritten with the Configuration values when the appserver next starts.
Select the Configuration tab, to display the transaction-related configuration properties.
To change the directory in which transaction logs are written, type the full pathname of the directory in the Transaction log directory field. You can check the current runtime value of Transaction log directory, by clicking the Runtime tab.
You can also specify a size for the transaction logs, as described in the following step.
If you change the transaction log directory, apply the change and restart the appserver as soon as possible, to minimize the risk of problems caused that might occur before the appserver is cycled. For example, if a problem causes the server to fail (with in-flight transactions), the server next starts with the new log directory and is unable to automatically resolve in-flight transactions that were recorded in the old log directory.
If you want to change the default file size of transaction log files, modify the Transaction log directory field to include a file size setting, in the following format...directory_name;file_size
- directory_name is the name of the transaction log directory
- file_size is the new default size specified in bytes. The nK or nM suffix can be used to indicate kilobytes or megabytes. If you do not specify a file size value, the default value of 1M is used.
For example, /path/to/tranlogs;2M indicates the files are to be created with 2M bytes size and stored in the directory /path/to/tranlogs.
In a non-production environment, you can use the transaction log directory value of ;0 to disable transaction logging. (There must be no directory name element before the size element of 0.) You should not disable transaction logging in a production environment, because this prevents recovery after a system failure and, therefore, data integrity cannot be guaranteed.
In the Total transaction lifetime timeout field, type the number of seconds a transaction can remain inactive before it is ended by the transaction service. A value of 0 (zero) indicates that there is no timeout limit.
In the Client inactivity timeout field, type the number of seconds after which a client is considered inactive and the transaction service ends any transactions associated with that client. A value of 0 (zero) indicates that there is no timeout limit.
Stop then restart the appserver.
If you change the transaction log directory configuration property to an incorrect directory name, the appserver will restart but be unable to open the transaction logs. You should change the configuration property to a valid directory name, then restart the appserver.