Image Services and Content Engine have several ways to keep track of system activity.
Successful operations are logged in the following five categories. Failure cases are not logged.
Errors, warnings, and informational messages are recorded in the standard system log. Use the vl command to view the log file.
The perf_mon tool gathers statistical data from the following areas: cpu usage for kernel and non-kernel activities; overall file system activities; kernel file system activities; network I/O statistics; database server counts; document services counts, RPC statistics, and security statistics.
See the Image Services System Tools Guide for more information on using the perf_mon tool.
Use the FileNet System Configuration Editor (fn_edit) to enable this feature (Collect Statistics) on the System Application Services tab.
Quick logging collects statistics for committals, retrievals, and deletions during system image processing. These statistics are kept in the /fnsw/local/tmp/qlogs/1 directory.
When a Content Federation Services for Image Services library encounters an
error, it generates an entry in the system log (sys_log). Sys_log messages generated
from the libraries are sent to the standard error output device, stderr, which
is usually the monitor screen, and also to a file. By default, this file is
named
<CFS-IS directory>\client\logs\walYYYYMMDD
The location, but not the name, of this file can be changed by setting the environment variable WAL_LOG_DIR to specify a different directory.
Output to stderr can be turned off by creating the file <CFS-IS directory>\client\tmp\nocons. If this file exists, sys_log entries will be written only to the walYYYYMMDD file.
Event logs provide historical information that can help you track down system and security problems. The event-logging service controls whether events are tracked on Windows systems. When this service is started, you can track user actions and system resource usage events with the following event logs.
Trace logging is a diagnostic tool that generates detailed information for tracing server and client activities. However, it provides no security or audit trail information. Because trace logging creates a drain on system performance, it should be enabled only for troubleshooting.
The Content Federation Services for Image Services Connection Monitor tool displays status and activity information for a local Content Engine host that has one or more Image Services Domain servers configured. The information provided enables you to diagnose system problems and track the number and speed of documents moving among Image Services and Content Engine systems.
SSI Trace Logging lets you monitor the flow of Content Federation Services for Image Services documents entered on the Content Engine server. To enable this feature, enter the following command at a command prompt:
SSI_trace -on -t
The trace information is then included in the system log located in the <CFS-IS
Directory>\client\logs\wal<yyyymmdd> file
The “-t” option causes the SSI_trace program to continue running indefinitely.
That guarantees that shared memory is not lost, so the value of the trace flag
is preserved. If shared memory is reinitialized, the trace flag will be off
when shared memory is created again later.
When you want to turn the trace off, first, stop the SSI_trace program if it’s
still running, then enter the following command at a command prompt:
SSI_trace -off
The FileNet System Monitor is a functional expansion that provides system monitoring capabilities for the entire FileNet product family. In a Content Federation Services for Image Services environment, FileNet System Monitor can help you keep track of import agent status, document commital and retrieval flow, and Image Services index transfer.
FileNet System Monitor has a web-based operator console that you can customize by setting performance thresholds and alerts. And you can tailor the standard suite of reports to your Content Federation Services for Image Services configuration.
On Windows servers, the Content Engine provides counters that enable you to monitor system performance using any Windows-compatible third-party performance monitoring utility.
Packaged with the Windows server, the Performance Monitoring utility lets you choose counters for the Content Engine components that you want to monitor. This enables you to view activity on your Content Engine server in real time. It also generates log files which you can later view and analyze using printable graphs, histograms, or reports.
The system administrator can monitor the activity of the Content Engine system
by configuring auditing at the class level. Auditing can be enabled or disabled
at the object store level.