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
  About the Process Router
  Starting and stopping a router
  Command line options
  Process Router property descriptions
  Configuring router defaults
Administrative tasks
   

About the Process Router

The Process Router routes workflow-related requests to the Process Engine.

  • On the Application Engine or web server

A router on the Application Engine or web server routes requests from a workflow application to a specified VWService and isolated region on a Process Engine. A router can only reference one isolated region; if a VWService includes multiple isolated regions, there must be one router pointing to each isolated region that Process Engine users need to access. A router connects to the Pooled Process Manager (PPM) on the specified VWService. Upon connection, the router retrieves the VWService's configuration map. Based on the configuration map, the router then directs each application request to the PPM on the appropriate Process Engine. On Windows servers, you can configure a router to run automatically as a service through the Process Service Administrator.

  • On the Content Engine or Content Services server

A router on the Content Engine or Content Services server enables you to automatically launch workflows from workflow subscriptions within the system. A router can only reference one isolated region; therefore, automatic launching only applies to one region within a VWService. You can configure a router to run automatically as a service through the Process Service Administrator.

The router acts as an RMI server. For more information about the use of the RMI registry, see About the RMI registry.

The use of a firewall and/or a Network Address Translator (NAT) can prevent the necessary communication between the Process Engine, the Application Engine or web server, and the client by hiding the fully qualified name of the web server host.