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 advanced properties

Use the Advanced tab to fine-tune the settings for a component at runtime.

Changes made to these settings affect only the current instance of the component. If you stop the Component Manager or run the Refresh All Configurations command, the component settings revert to the values entered via the Process Configuration Console.

The Advanced tab includes these fields:

Name Description

User Name

A valid user name. The user name serves as JAAS credentials for identification and permissions on both the Process Engine and any external systems that are accessed. See Java Authentication and Authorization Service (JAAS).

The user must have Query & Process access to the component queue, as defined in the Process Configuration Console. The Component Manager reports an error when starting the component if the user does not have sufficient access rights.

Password The password associated with the user name.
Configuration Context The name of the set of login modules JAAS uses for this component. The context you enter must be defined in taskman.login.config. For further information, see Developing Component Integrator-Based Workflow Applications in the Help for Process Java API.
Concurrent Threads

The number of concurrent threads to execute for this component. Use 1 for a system with a single CPU. This number can be increased for a system with multiple CPUs.

Polling Rate

If the component is inactive, this is the amount of time in milliseconds between polls of the queue by this component to look for work; 1000 is equivalent to polling once per second. Frequent polling can impact system performance if the queue tends to be empty. As long as there is work in the queue the component never goes inactive and polling does not occur.

If you have specified an event port, the Component Manager responds to both the component's polling rate and to new events as they occur. 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.

Exception Submap The submap to be used when this component encounters exceptions. The default is Malfunction. See About system maps for more information on submaps.