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)
  About the PPM
  Starting and stopping the PPM
  Command line options
  PPM property descriptions
Rules Engine
Component Manager
Process Simulator
Routers
Administrative tasks
   

Starting and stopping the PPM

Use the PPM node in Process Task Manager to start and stop the PPM on the Process Engine. In a multi-server configuration, the PPM must be running on each Process Engine.

TIP On a Windows-based Process Engine, you can alternatively start and stop the PPM from Process Service Administrator; via this tool, you can configure the PPM to start automatically when you start Windows. Whichever method you choose to start the PPM, you must use the same method to stop the PPM; for example, to stop the PPM you started in Process Task Manager, you must again use Process Task Manager. (For the purposes of this discussion, Process Task Manager and the command line option are considered to be the same method.)

To start the PPM

  1. Select the PPM node in the feature pane.
  2. Make changes, if desired, to the PPM properties. If the Process Engine and Application Engine are on opposite sides of a firewall, you must specify the Return Port property.
  3. Click the Start button on the toolbar.

To stop the PPM

  1. Select the PPM node in the feature pane.
  2. Click the Stop button on the toolbar.

    NOTE Stopping the PPM also shuts down any VWJs processes that the PPM has started.

   

CAUTION If your Windows Process Engine is configured as a cluster, you must use the appropriate cluster administration tool (the Microsoft Cluster Administrator or the Oracle Fail Safe Manager) rather than the Process Task Manager or other Process Service tools to:

  • Start, stop, and restart the Process Service software.
  • Start and stop the PPM service.

Failure to stop the Process Engine or the PPM service using the cluster administration tools will initiate a fail-over reaction from the cluster service.