Component Integrator Preparation and Processing Task Flow

This topic describes the user preparations, processing task flow, and module and server connections of the Component Integrator architecture and components. The fundamental logical modules of the Component Integrator itself are shown in the regions labelled 6, 7, and 8 in the Component Integrator task flow diagram (below), consisting of the following kinds of modules:

The Component Integrator task flow diagram includes other components in order to emphasize the connections and interactions with other FileNet workflow-related components. For further description of content of the task flow diagram, see the following:

    Component Integrator task flow diagram

    Component Integrator Flow flow step 1 flow step 2 flow step 3 flow step 4 flow step 5 flow step 6 flow step 7 flow step 6 flow step 8            

Steps in the Flow of Component Integrator Processing Tasks

  1. Deploying a custom Java class.
  2. Configuring a Java Component Queue for deployed custom Java component integration is the same as configuring a queue for any work performer — Employ the Configuration Console to configure a Process Engine Java Component Queue with Operations. Defining a Java Component Queue with operations consists of the following activities:

    Note Only one Java class can be associated with one Java Component Queue, and the class must have a constructor that has no parameters.

  3. Refer to defining Component Queue operations for detailed information about defining Java Component Queue Operations. For additional information about creating Component Queues, refer to Creating and configuring a component queue in the Setting Up the Component Integrator section of this document.

  4. Configuring a JMS Queue — Employ the Configuration Console to configure a JMS Queue with Operations, which hold message information. Refer to defining Component Queue operations for detailed information about defining JMS Queue Operations. JMS queue operations are defined with the JMS operations dialog to have the following properties:

    Refer to defining Component Queue operations for detailed information about defining JMS Queue Operations.

  5. Authoring a workflow — You employ the Designer tool to perform the following tasks:

    Note Refer to Component step - general properties in the Help for Process Designer online help for specific information on workflow authoring with components that you have set up to work with the Component Integrator.

  6. Configuring the Component Manager — You employ the Task Manager tool on your Process Engine server to access the Component Manager. Configure the Component Manager to manage the processing connections between the Process Engine and the service adapter for the Java or JMS component that is to be integrated with the following procedure:
    1. Specifying the connection information for the Component Manager by configuring the Component Manager general properties and the Component advanced properties.
    2. Specifying the location of the JAR files that contain any needed classes associated with each Component Queue by configuring the Component Manager required libraries. The location of the required libraries is associated with the Component Queue (and service adapter) type as follows:
      • For a Java Component Queue, the required library is the JAR file that contains the Java class for the component that is to be integrated. Additional required libraries would be JAR files that that provide the Java class with any dependent modules it may need.
      • For a JMS Component Queue, refer to the table of JNDI Initial Context Factories in this document to determine your application server's required libraries for a JMS component.
      • If a required library JAR file is altered or added when the Component Manager is running, the Component Manager must be stopped and re-started before it can be used.
    3. Starting the Component Manager is described in the following references:
  7. Managing runtime connectivity— The Component Manager starts the connections for your components and manages the processing connections between the Process Engine and the service adapters (Java or JMS) for each integrated component. There is one instance of a service adapter for each instance of an integrated component, and component authentication takes place when the service adapter initializes. For an example and information on authenticating a component for the Process and Content Engines, see the Component Authentication Example in this document.

    Note You can adjust previously set configuration properties with component advanced properties at runtime with the Component Manager, but changes made to these settings will affect only the current instance of the component.

  8. Processing a work item in a Java Component step — When a work item is passed to a step that uses a Java Component Queue, the Java Adapter performs the following tasks:
  9. Processing a work item in a JMS Component step — When a work item is passed to a step that uses a JMS Component Queue, the JMS Adapter performs the following tasks: