IBM FileNet P8, Version 5.2.1            

Process Routers (eProcess)

In the Routers folder, you can configure and run Process Routers on Content Platform Engine. (On other server types, use Process Task Manager to manage Process Routers.) The folder displays information about all Process Routers that are currently running locally.

Use a Process Router on Content Platform Engine to:

To add a Process Router:

  1. Select New/New Router from the context menu.
  2. As appropriate, add, edit, or retain the information displayed in the New Router window.
    Property What It Does
    Router Name The name of the Process Router to start. The name you enter cannot contain spaces.

    For Workplace, your entry must match the Process Router name that is specified in the Process Router site preference on Application Engine.

    Router Port The RMI registry port to use. The default port is 32771.
    PPM Server The TCP/IP name of the primary Content Platform Engine on which the PPM is running.
    Important: RMI requests to a server with an underscore (_) in the DNS name fail due to a limitation in JRE 1.4 and greater. If your server has a name containing an underscore, you must use the IP address or localhost if appropriate.

    For Workplace, your entry must match the Process Router name that is specified in the Process Router site preference on Application Engine.

    PPM Port The RMI port that the PPM on the Content Platform Engine (specified in the Process Engine parameter) is using. The default port is 32771; it is necessary to specify this parameter only if the PPM is running on a different port.
    Important: On Solaris-based systems, you must take additional steps in order to use port 32771.
    Isolated Region The number of the isolated region you want this Process Router to access; the number must be 1 - 1000. A Process Router supports only one isolated region.
    Username A valid user name. Administrative authority is not required to run a Process Router.
    Password The password associated with the username specified in the Username parameter.
    RMI Backlog The maximum queue length for incoming RMI connection indications (requests to connect). If a connection indication arrives when the queue is full, the connection is refused. The default value is 100. It is necessary to specify this parameter only if you want to change the value.
    Local Host The fully qualified name of the Application Engine or web server where the Process Router is running. This parameter is optional unless the Content Platform Engine or Application Engine or web server resides behind a firewall or Network Address Translator (NAT). In such configurations, you might be denied access when you start the Process Router, receiving the error Failed to find Service Router. To resolve this error, you must enter the value of Local Host when you start the Process Router.
    Important: RMI requests to a server with an underscore (_) in the DNS name fail due to a limitation in JRE 1.4 and greater. If your server has a name containing an underscore, you must use the IP address or localhost if appropriate.
    Debug Level Indicates whether debugging information is provided. Valid entries are 0 (the default, which turns off debugging) - 4. Do not turn on debugging unless you are directed to do so by your IBM support representative.

    When debugging is on, each level (1-4) provides progressively more information. The output is stored in the Process Router trace file, vwrouter.trc (default).

    Connection Retry The amount of time (in seconds) that the Process Router waits before timing out when attempting to connect to the workflow system.
    Automatically started Whether the Process Router automatically starts when the system is started.
    Tip: To set the Process Router to automatically start, make sure the Process Services Manager service is configured to log on with the local fnsw account rather than the Local System account. Use the Windows Services utility to configure Process Services Manager.
    Automatically restarted Whether the Process Router automatically restarts if an error occurs that causes the process to stop.

To start, stop, or delete a Process Router:

You cannot mix the use of Process Services Administrator and Process Task Manager for starting and stopping a Process Router. You must use the same method to start and stop a Process Router; for example, to stop a Process Router you started in Process Task Manager, you must again use Process Task Manager.
  1. Select the item in the folder, and click Start, Stop, or Delete on the toolbar.


Last updated: October 2015
routers.htm

© Copyright IBM Corporation 2015.