IBM FileNet P8, Version 5.2.1            

Configure the legacy Component Manager

The legacy Component Manager uses a connection point to access the workflow system. Connection points are stored on the Content Platform Engine server; before legacy Component Manager can access a connection point, you must specify the information that Process Task Manager uses to connect to Content Platform Engine. The legacy Component Manager displays the default connection information that it uses in the Component Managers property pane. When you create a new Component Manager, Process Task Manager uses this connection information to generate a list of available connection points. See Component Manager general properties for a description of the connection information.

To create a Component Manager:

  1. Select New from the Action menu.
  2. Select the desired Connection Point. (The workflow system and isolated region that it references is displayed below.)
  3. Click OK. Process Task Manager creates a legacy Component Manager named <connection point>.ALL. (ALL is the default suffix, and indicates that this legacy Component Manager polls all component queues that are accessible through the selected connection point. You can restrict this by listing specific queues in the legacy Component Manager general properties.)
  4. Process Task Manager automatically fills in general properties for the new Component Manager. You can update the general properties as needed. Select each tab, listed in the table below, to specify additional legacy Component Manager properties.
    Property Group Description
    General Specify the connection information and the queues to be managed by this Component Manager.
    Required libraries Specify the location of the jar files that contain the class associated with each component queue. Process Task Manager appends the jar file locations to the class path when starting this Component Manager.
    Advanced Specify advanced properties for this Component Manager.
    Java security Specify the location of Java security files.


Last updated: October 2015
cm_config.htm

© Copyright IBM Corporation 2015.