You can specify the maximum size and number of log files
to be stored on the server.
Before you begin
Before performing this procedure, make sure you have the required
disk space. IBM® recommends that
the server retain a history at least 2 GB in size, to assist with
troubleshooting. If you can spare more disk space than that, you can
set the file maximum size to more than 20 MB.
Procedure
- In the WebSphere® Integrated
Solutions Console for the server where the logs will be stored click .
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.
- In the "Server Infrastructure" section, click .
- In the "Additional Properties" section, click .
- 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. |
- Click OK.
- Return to the "Additional Properties" section and click .
- 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. |
- Click OK.
- Save the change to the master configuration by clicking
the Save link in the "Messages" box at the
beginning of the page.
- In a clustered environment, repeat these steps for each
node within the cluster.