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:
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.
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. |
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.
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. |