Component queues

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.

Stopping and Starting a Component Queue

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.

To stop a component queue:
  1. In Process Configuration Console, clear the Enable Queue Processing in Server check box on the Component Properties > Adapter tab.
  2. Commit your changes.
Before Content Cortex Version 5.2.1, Process Configuration Console is started from either Workplace or IBM® FileNet® Workplace XT. Starting in Content Cortex Version 5.2.1, Process Configuration Console can also be started from the Content Platform Engine administration console in the following way:
  1. Expand the object store node, then expand the Administrative > Workflow System node.
  2. Select Actions > Configure Workflow Settings.