Use this task to configure the transaction properties for an application server; for example, to define the location of the directory that contains the transaction log or to change default timeouts associated with transactions.
Why and when to perform this task
To configure the transaction properties for an application server, complete the following steps:
Steps for this task
You can also specify a size for the transaction logs, as described in the following step.
Note: If you change the transaction log directory, you should apply the change and restart the application server as soon as possible, to minimize the risk of problems caused that might occur before the application server is restarted. 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.
directory_name;file_size
Where
For example, c:\tranlogs;2M indicates the files are to be created with 2M bytes size and stored in the directory c:\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.
If you change the transaction log directory configuration property to an incorrect directory name, the application server will restart but be unable to open the transaction logs. You should change the configuration property to a valid directory name, then restart the application server.