Setting log file size and rotation for JVM log files

You can specify the maximum size and number of log files to be stored on the server.

1. In the WebSphere® Integrated Solutions Console for the server where the logs will be stored click Servers > Server Types > WebSphere application servers > Server_Name.
   Tip: For the Sametime® Media Manager, if you installed the components on separate computers or as separate cell profiles, you must adjust the log file information on all Conference Manager servers.
2. In the "Server Infrastructure" section, click Java and Process management > Process Definition.
3. In the "Additional Properties" section, click Logging and Tracing > JVM Logs.
4. In the "General Properties" section, update the following fields both for System.out and System.err sections:

   Table 1. General properties settings for logging and tracing

   Field	Value
   Log File Rotation	Make sure this is managed by file size rather than file age.
   Maximum size	Set this value to at least 20 MB.
   Maximum Number of Historical Log File	Set this to a value that, when multiplied by the file size, gives you at least 2 GB of history in your logs. In this example you would use 50 files as the maximum.

5. Click OK.
6. Return to the "Additional Properties" section and click Logging and Tracing > Diagnostic Trace.
7. Click File and update the following fields in the "Trace" section:

   Table 2. Additional properties settings for diagnostic traces

   Field	Value
   Maximum size	Set this value to at least 20 MB.
   Maximum Number of Historical Log File	Set this to a value that, when multiplied by the file size, gives you at least 2 GB of history in your logs. In this example you would use 50 files as the maximum.

8. Click OK.
9. Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page.
10. In a clustered environment, repeat these steps for each node within the cluster.