,             

Migrating component queues from legacy Component Manager

If you have existing component queues from earlier version of FileNet® P8 Component Manager (legacy Component Manager), you should migrate the component queues to the current version of FileNet P8 Component Manager.

You can migrate Java™ and JMS component queues from legacy Component Manager by using Process Configuration Console.

To migrate component queues from legacy Component Manager, complete the following steps:

  1. In Process Configuration Console, right-click a component queue to open the Component Queue Properties window, and then open the Adapter tab.
  2. From the Adapter list, select Java Component, or JMS Component. Note that there is also a Java Component that is listed as deprecated. The deprecated Java component is for use with queues that you do not want to migrate.

    If you are migrating a JMS component, configure the component with the option parameter to specify the JNDI URL where the queue is located. If you do not specify the JNDI URL, it is assumed that the queue information is defined in the application server where the workflow system is located.

  3. Click Configure… to configure the code module for the component queue.
  4. Click ... to select the code module JAR files.
  5. Click Browse/Add to add the jar files for the component queue, and then click OK. When you click OK, you are requested to save the code module to an object store. It is recommended that you store the code module in the object store that shares the same database as the workflow system connection point.
  6. Specify the following adapter properties:
    Table 1. Table of field names and description for the Adapter Properties
    Name Description
    Batch Size The amount of step elements to query per batch at runtime. The suggested minimum is 10.
    Polling Rate The amount of time, in milliseconds, between polls of the associated component queue 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.
    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.
    Processing Timeout The amount of time, in milliseconds, for processing each step in the component method.
    Auto Recovery Timeout The amount of time after which a locked work object in the component queue will be dispatched to the exception submap. This is the recovery behavior to handle work objects that have been locked due to server crashes or adaptor classes that are not working properly.
  7. Specify the JAAS credentials.

    If the component code does not need a login module, other than the out of the box login modules (VWLoginModule, FileNet P8), you do not need to specify the JAAS Configuration context.

    If you specify a JAAS context, you should use the administrative tools provided by the application server hosting the Content Platform Engine server to configure the JAAS context with the appropriate login modules. Note that the login modules can be included in the Code Module for the component.

    If the CELogin was used for the compatibility of the Java API (3.5 Content Engine Java API), you must specify the JAAS credentials. However, it is recommended that you rewrite the component to use the current API.

    Table 2. Table of field names and description for the JAAS Credentials
    Name Description
    User name A valid user name. The user name serves as Java Authentication and Authorization Services (JAAS) credentials for identification and permissions for both the workflow system and any external systems that are accessed. .

    The user must have Query and Process access to the component queue, as defined in Process Configuration Console. 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. For further information, see Developing Component Integrator-Based Workflow Applications.
  8. Click Finish.
  9. Right-click on the component, and then click Properties to reopen the component and configure its operations.
  10. In the Operations section, click on the import button to import each operation that you want to add to the queue.
  11. When you are done adding operations, click OK to commit your changes in Process Configuration Console.


Feedback

Last updated: October 2013
bpfc112.htm

© Copyright IBM Corporation 2014.
This information center is powered by Eclipse technology. (http://www.eclipse.org)