Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Task Manager
  Search  |  Index
Process Reference  
Process Task Manager
Getting started
Process Service
PPM (Pooled Process Manager)
Rules Engine
Component Manager
Process Simulator
Routers
Administrative tasks
  Monitoring Process Task Manager
  Managing the log files
    Enabling automatic startup
    FileNet event log files
    VWJs log files
    VWJs debugging trace files
    PPM debugging trace files
    RMI registry log file
    Router trace file
   

FileNet event log files

The Process Service and other FileNet products log messages in the event logs on the Process Engine. Process Service writes a message to the event log when:

  • A user is not available to handle an error, or
  • An unrecoverable error is encountered.

For example, if an error occurs while the Process Engine is processing a work item in a system queue, the only option is to save the error in the event log because there is no user associated with a system queue.

Note that some processes write only one message in the daily current event log, even if an error has occurred multiple times since the current event log was created. This is done to avoid redundant error messages in the event log.

Event logs on Windows platforms

Process Service events are logged in the Windows Application Log and are accessible from the Windows Event Viewer. Process Service events have IS or VWServices as their source. In addition, related database errors appear under the associated database source. For details on the Event Viewer, refer to a Windows 2000 Server System Guide.

NOTE A Process Engine with Image Services (IS) fully installed (FileNet Web Services Client or Open Client interface) is an exception to using the Windows Event Viewer. To view an event log in this case, refer to Event logs on UNIX platforms below.

The Windows Event Viewer monitors various types of events in the system, such as errors, warnings, informational events, and successful and unsuccessful security access attempts. Events are recorded in logs and may be generated by the Windows system, services, and applications, or through audited user activity.

When you start Windows, event logging starts automatically. Process Service events have IS or VWServices as their source. In addition, related database errors appear under the associated database source. For details on the Event Viewer, refer to the Windows NT Server System Guide.

Event logs on UNIX platforms

On UNIX platforms, a new event log is generated each day. To view an event log, enter the vl command at the command prompt.

UNIX Event Log Information

File name

elog.yyyymmdd, where yyyymmdd indicates the date.

Created on:

The Process Engine.

Located in:

The \fnsw\local\logs\elogs folder (the same folder where you installed the Process Servicesoftware).

Can be turned off:

No.

To archive:

Use standard operating system commands to copy the files you want to archive to permanent storage media, then delete the copied files from the current location. You cannot copy the current day’s event log while Process Service is running. You can copy and delete all of the remaining files, if desired, or leave the most recent files online for reference and future archiving.