Optionally, you can capture messages for the eDiscovery Manager
web client and the eDiscovery Manager work manager that can help with
troubleshooting.
Important: Your ability to
perform tasks depends on the roles that were assigned to you. Only
icons and menu options for tasks that are associated with your roles
are visible to you. Be aware that this topic might include information
that is not relevant to your roles.
To configure logging for the
eDiscovery Manager web client, the
eDiscovery Manager work manager (server), or both:
- On the Administration page, click Logging
Configuration in the Navigation pane.
- Enter the absolute path and a file name for the log file.
You must enter an absolute path and a file name with the extension .log, for
example, /opt/IBM/eDM/logs/edm.log on an AIX® system or C:\Program Files\IBM\eDM\logs\edm.log on a Windows system.
- Select the optimal logging level for your site.
- Off
- Logs no messages.
- Severe
- Logs only extremely important messages, such as those for events that indicate that the
application cannot continue to function. This is the default value.
- Warning
- Logs all messages at the Severe level plus warning messages, such as those about errors that
prevent completion of a requested action.
- Informational
- Logs all messages at the Warning level plus informational runtime messages, such as status
information.
- Fine
- Logs all tracing information at a fine level of detail. Because this level of logging can
consume a lot of system resources, specify this level only when diagnosing problems and only long
enough to capture the necessary information for fixing the problems.
- Finer
- Logs all tracing information at an even finer level of detail. Because this level of logging can
consume a lot of system resources, specify this level only when diagnosing problems and only long
enough to capture the necessary information for fixing the problems.
- Finest
- Logs all tracing information at the highest level of detail. Because this level of logging can
consume a lot of system resources, specify this level only when diagnosing problems and only long
enough to capture the necessary information for fixing the problems.
Recommendation: To maximize performance, do not configure a more
detailed logging level than you need.
- Enter the maximum number of log files to create and enter the maximum size, in MB, of
each log file. Be mindful of your disk space constraints and the logging level that you specified.
The more messages you choose to log, the faster the log files will fill up and the more log files
will be needed.
When a log file reaches the specified size, eDiscovery Manager creates a
new log file. When the specified number of log files is reached, eDiscovery Manager begins overwriting the existing log files, starting with the first
log file that it created.
Entering a value of 0 (zero) for the
Size limit of each log file
(MB) field has two implications:
- The log file size is unlimited. The log file will continue to grow with no restrictions on its
size.
- Regardless of the value that you enter for the Number of rotating log
files field, only one log file will be created. With no limit on the log file size,
there is no need to roll over the first log file and create another one.
Recommendation: Never set the value of the Size limit
of each log file (MB) field to 0 (zero). For performance and disk space reasons, it is
better to configure multiple log files that are smaller than to configure a single large log
file.
- Click Apply.
Your changes are immediately visible to you and they take effect immediately. Both new and
existing eDiscovery Manager sessions begin to operate
under the new configuration settings as soon as you click Apply.