Optional: If you want to change
the directory in which transaction logs are written, type the full path name
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.If you leave this
field unset, the application server assumes a default location within the
appropriate profile directory.
When
using WebSphere Application Server without high availability support, you
do not need to set the recovery log configuration for persistent services
(such as the transactions service). The application server assumes a default
location in the appropriate profile directory. When high availability support
is enabled, this default may not be visible from all servers in the cluster
(for example, if they are in different profiles or physical nodes.) Because
of this behavior, configure the recovery log location for each server in the
cluster before enabling high availability. You must also ensure that each
server in the cluster has a unique log directory, to avoid attempts by multiple
servers to access the same log file.
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 occurring 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.
Optional: To change the size
of transaction log files, modify the Transaction log directory field
to include a file size setting. Use the following format, where directory_name is
the name of the transaction log directory and file_size is
the disk space allocation for the transaction log files, specified in kilobytes
(nK) or megabytes (nM). If you do not
specify a value for the file size, the default value of 1M is used.
directory_name;file_size
![[AIX HP-UX Linux Solaris Windows]](../../dist.gif)
For example, for a Windows system, the following entry specifies
that transaction log files are created in the directory c:\tranlogs with a
size of 2 megabytes.
c:\tranlogs;2M
In a non-production
environment, you can turn transaction logging off by entering ;0 in
the Transaction log directory field (do not enter a
directory name). Do not turn transaction logging off in a production environment
because this prevents recovery after a system failure, and therefore data
integrity cannot be guaranteed.
For more information about transaction
log sizes, see Managing transaction logging for optimum server availability.
Stop then restart the application server. 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.
If you are running
the application server as non-root, modify the permissions on the new transaction
log location. If you want to use peer recovery of transactions on a shared
device with non-root users, make sure that your non-root users and groups
have matching identification numbers across machines