Administrators can facilitate solution recovery processes by following a first steps checklist of general practices.
The transaction (tranlog) log file stores critical transactional data that is written to databases. It is an internal file that WebSphere Application Server uses to manage in-flight transactions and attempt to recover them should the server crash.
Put the transaction logs on a shared drive. This is the only way to allow peer recovery, which helps minimize the downtime during recovery.
You should only uninstall applications with the direction from the IBM® support organization.
Too much trace will cause a slowdown in system throughput and might cause transaction time-outs. Too much trace can often add to the problems that need to be addressed, rather than providing insight as to how to solve the original problems.
Get immediate assistance from IBM support to define the correct trace specification.
Enabling the Run in development mode option may reduce the startup time of an application server. This may include JVM settings such as disabling bytecode verification and reducing JIT compilation costs.
The following list describes the recommended actions when it comes to recovery.
Logs may be overwriting themselves depending on the configuration. Capturing a set early and often is an important step for postmortem analysis. See the topic on IBM Support Assistant (ISA) for details on the IBM Support Assistant, which helps with this type of activity.