Create a component queue

Use the options on the Add Component Queue Wizard pages to associate a Java™ application or (Workplace or Workplace XT) Java Message Service (JMS) queue with a workflow queue.

NOTE  Workplace supports both Java applications and JMS queues; IBM FileNet Web Services and Open Client support only Java application for components.

See Configure component queues and About Component Integrator for additional configuration information. See the Help for Process Development for information about Component Integrator.

To create a new component queue

  1. In Process Configuration Console, open the isolated region.
  2. Select the Component Queues folder icon and click New on the toolbar.
  3. Enter a name for the queue in the Queue name box. See Naming conventions for information regarding valid names. The name will appear in the list of component queues in Process Designer.
  4. In the Description box, you can optionally enter a brief description of the queue.
  5. Click Next to continue.

Adaptor configuration

  1. Do one of the following:
  2. In the Adaptor drop-down menu, choose the appropriate adaptor—Java Component or (Workplaceor Workplace XT) JMS component.
  3. Click Configure. This displays either the Java configuration dialog box or (Workplace or Workplace XT) the JMS configuration dialog box, depending on the adaptor.

    On return from the Java or JMS configuration dialog box...

  4. Enter 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.
  5. Enter the polling rate; 1000 is equivalent to polling once per second. 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. 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.

    NOTE  If your system has been configured to automatically check for new events, 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), Component Manager automatically queries the associated component queue every 10 seconds. If after 3 seconds an event comes in, Component Manager again queries the component queue and processes any additional work found there.

  6. Select the exception handling submap to be used by this component. The default is Malfunction. See About System Maps for more information on submaps.

    NOTE  If your component has an error during execution, the work item will contain a summary of the exception text. Therefore, it is advantageous to know where to look for the work object. If you retain the Malfunction submap, the work object will go to the Conductor queue. If you define a custom exception handling submap for the component adaptor, the work item will be where you specify.

  7. Specify Automatic or Manual startup mode. If you select Automatic, the adaptor starts when Component Manager starts.

    NOTE   If you are using a WebLogic application server, the JMS adaptor cannot be started until the WebLogic application server has completed its startup sequence. Any JMS adaptors must be started manually after the application server has completed its startup sequence and Component Manager is running.

  8. Set Java™ Authentication and Authorization Service (JAAS) credentials by entering a user name and password that will be used for identification and permissions for both Process Engine (PE) and potentially any external systems that will be accessed.

    For Workplace to use CE Operations, you need appropriate access to the potential targets in the object store.

    CAUTION  In order for the JMS adapter to establish a connection with the queue connection factory, the JAAS credentials (user name and password) specified here for the JMS adapter must exist in the security list of the application server.

  9. Enter the configuration context. The context you enter must be defined in taskman.login.config. (The taskman.login.config file is located in ...\FileNet\router.)
  10. Click Finish when done.

Adding operations

  1. To complete the configuration, select the new component queue and click Properties on the toolbar.
  2. Select the Operations tab to import the operations from the Java class or (Workplace or Workplace XT) specify the JMS event list.

    NOTE  On the Component Properties dialog box, you can specify exposed fields, indexes, and security for this component, as well as change the adaptor and operation properties.

  3. Click Commit to apply these changes to your isolated region. You can commit the changes immediately, or you can wait until you have finished all your changes.