Component queues make it possible to process a workflow step by using an external entity, such as a Java™ object or Java Message Service (JMS).
You can configure a component queue with an adapter, such as Java or JMS. Use the Java adapter to expose public methods from a Java class as operations on a queue. Use the JMS adapter to publish workflow data to a JMS queue by using operations. By using Process Designer, the workflow author can add a component step to a map and select operations for that step from the list of component queues. The workflow author also specifies the appropriate expression for each operation parameter.
If you have custom legacy component queues that you created with FileNet® P8 versions earlier than 5.2.0, you can still work with those components. Migrate your component queues to the current version.
For information about migrating existing component queues to the new Component Manager framework, see Migrating component queues from a legacy Component Manager.
In the latest version of Component Manager, by default, component queues are started automatically as soon as they are created and updates are applied as soon as the changes are saved. Component Manager does not need to be stopped and restarted to incorporate the change.