Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Engine Administration
  Search  |  Index
Process Reference  
Process Engine Administration
Workflow administration tasks
System administration tasks
  Configuring the Process Engine
  Configuring users and groups (Workplace)
  Configuring users and groups (Open Client/FileNet Web Services Client)
  Configuring optional features
  Running the Process Engine
    Running the system
    System maintenance tasks
    Administrative tools
  Improving system performance
  Troubleshooting
   

Running the system

Managing the Process Engine involves managing the various workflow processes required for running the Process Engine. Related processes on the Application Engine or web server are discussed here as well.

When a workflow application or step processor makes a request, the Process Router on the Application Engine or web server receives the request and determines the appropriate Process Engine to fulfill it. The Pooled Process Manager (PPM) on that server receives the request and allocates it to one of several VWJs server processes in an attempt to balance the load of incoming requests. After the request is fulfilled, the Process Engine returns the result via the PPM to the Process Router and then to the workflow application or step processor.

The table below describes the processes involved.

Process Name Description Runs on the...

Process Service

The software processes and utilities that enable workflow activity.

Process Engine

Process Router

Acts as an RMI server to determine which Process Engine receives a request from a workflow application.

Application Engine or web server

Pooled Process Manager (PPM)

The link between the Process Router and the Process Engine VWJs server process.

Process Engine

Process Service

The Process Service software can be configured to start automatically when the Process Engine is booted, or to allow you to manually start the Process Service software. In addition, occasionally you may need to start, restart, or stop the Process Engine manually. Note that the Process Engine documentation always indicates when you must restart the Process Engine software as part of a procedure.

Use the Process Task Manager to start, restart, and stop the Process Service software on the Process Engine.

The Process Router

You must start a Process Router on the Application Engine or web server in order for users to access the Process Engine. You can start the Process Router before or after you have started the PPM on the Process Engine. If the Process Router fails to connect to a PPM process or receives a connection error while running, the Process Router tries to reconnect to the PPM the next time the Process Router is accessed. If successful, it resets its connection information to the current PPM process. This capability allows the Process Router to recover from errors that might occur if a Process Engine is restarted at some point.

Use the Process Task Manager or the Process Service Administrator to manage the Process Router. (The Process Service Administrator is not available on the Application Engine.)

TIP Use the Process Service Administrator (FileNet Web Services Client or Open Client) if you want to configure the Process Router to start automatically when the web server is booted.

The Pooled Process Manager (PPM)

You must start the PPM in order for users to access the Process Engine. In a multi-server configuration, the PPM must be running on each server.

Use the Process Task Manager or the Process Service Administrator to manage the PPM on the Process Engine.

TIP Use the Process Service Administrator if you want to configure the PPM to start automatically when the Process Engine is booted.