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
  Configuring the Component Manager
    General properties
    Required libraries
  Starting and stopping the Component Manager
  Components
    Starting and stopping components
    Configuring components
      General properties
      Advanced properties
Process Simulator
Routers
Administrative tasks
   

Component Manager general properties

Use the General tab to specify the connection information for the Component Manager.

The General tab includes these fields:

Name Description

Router URL

Enter the URL of the Process Router to be used for authentication. Enter the information in the following format:
<Application-Engine-or-web-server-name>:<port>/<router-name>.

For Workplace, your entry must match the Process Router specified in the site preference for Tasks/Router. See Router for further details.

User Name

A valid user name.

NOTE Process Task Manager displays the components to which the user has read access. To manage all of the components, the user must have Query access to all component queues.

Password The password associated with the user name specified in the User Name property.
JNDI Initial Context Factory

(JMS-based components only; note that JMS components are supported for Workplace only.) Identifies the class responsible for managing the connection to the J2EE JNDI server through which the JMS adaptor connects to the JMS queue. This is usually a vendor-specific class depending on the application server. The table below lists some common application server types:

For this application server type... use this value...
WebLogic weblogic.jndi.WLInitialContextFactory
WebSphere com.ibm.websphere.naming.WsnInitialContextFactory
Sun Microsystems J2EE Reference Implementation None. The Component Manager uses the default for J2EE.
Registry Port

The RMI port the Component Manager uses. The default port is 32771.

NOTE On Solaris-based systems, you must take additional steps in order to use port 32771. See Eliminating port 32771 conflicts for instructions.

Event Port

The port that the Component Manager listens to for incoming events. The default is 6003.

By entering an event port you configure the Component Manager to automatically respond to new events as they occur. When you specify an event port, the Component Manager responds to both the component's polling rate and to the incoming events. For example, if a component's polling rate is 10000 (10 seconds), the Component Manager automatically queries the associated component queue every 10 seconds. If after 3 seconds an event comes in, the Component Manager again queries the component queue and processes any additional work found there.

Alternatively, if you set the event port to 0, the Component Manager does not automatically respond to new events as they occur; instead, the Component Manager polls periodically for new events, based on the polling rate you set for each component.

Enable automatic startup Enables automatic startup of the associated process when Process Task Manager is started from a script. See Enabling automatic startup for more information.