IBM FileNet P8, Version 5.2.1            

Content Federation Services for Image Services log files

Image Services and Content Platform Engine have several ways to track system activity in log files. You can use these files to troubleshoot problems that occur when you install, configure, or use Content Federation Services for Image Services.

Image Services

Image Services activity logging
Successful operations are logged in the following five categories. Failure cases are not logged.
  • Annotation Logging
  • Security Logging (User and Group Maintenance)
  • Index Services Logging (Indexing and Foldering)
  • Workflow Queue Logging
  • Document Table Logging (Deletion and Insertion)
Image Services syslog and subsystem logging
Errors, warnings, and informational messages are recorded in the standard system log. Use the vl command to view the log file.
Image Services performance monitoring (perf_mon)

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.

For more information about using the perf_mon tool, see the Image Services System Tools Guide .

Quick logging

Use FileNet® System Configuration Editor (fn_edit) to enable quick logging (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.

Content Platform Engine

Windows event logs
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
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, enable it only for troubleshooting.
System monitoring
The Content Federation Services for Image Services Connection Monitor tool displays status and activity information for a local Content Platform Engine host that has one or more Image Services Domain servers configured. The information enables you to diagnose system problems and track the number and speed of documents that move between Image Services and Content Platform Engine.
System monitor

The IBM® Enterprise Content Management 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, ECM System Monitor can help you track import agent status, document committal and retrieval flow, and Image Services index transfer.

ECM System Monitor has a web-based operator console that you can customize by setting performance thresholds and alerts. You can tailor the standard suite of reports to your Content Federation Services for Image Services configuration.

Windows Performance Monitor

On Windows servers, Content Platform Engine provides counters that enable you to monitor system performance by using any performance monitoring utility that is compatible with Windows.

Packaged with the Windows server, the Performance Monitoring utility enables you to choose counters for the Content Platform Engine components that you want to monitor. This utility enables you to view activity on your Content Platform Engine server in real time. It also generates log files that you can later view and analyze by using printable graphs, histograms, or reports.

Auditing
The system administrator can monitor the activity of the Content Platform Engine system by configuring auditing at the class level. Auditing can be enabled or disabled at the object store level.


Last updated: October 2015
cfs_activity_logging.htm

© Copyright IBM Corporation 2015.