Use the options on the Add Component Queue Wizard pages to associate
a Java application or (Workplace
only) JMS queue with a workflow queue.
NOTE Workplace
supports both Java applications and JMS queues; FileNet Web Services Client
and Open Client
support only Java application for components.
In the Process Configuration Console,
open the isolated region and server.
Select the Component Queues folder
icon and click New on the toolbar.
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.
In the Description box, you can
optionally enter a brief description of the queue.
Click Next to continue.
Adaptor configuration
Do one of the following:
To configure a new component queue, continue with step 2 below.
To modify the configuration of an existing component queue, be sure
that the .jar file containing the classes is available on the local
computer, then make the desired changes.
In Workplace, to modify CE_Operations, copy p8ciops.jar
to C:\Temp, then make the desired
changes. (The p8ciops.jar file
is installed on the Application Engine at ...\FileNet\Workplace\WEB-INF\lib.)
In the Adaptor drop-down menu, choose
the appropriate adaptorJava Component
or (Workplace
only) JMS component.
On return from the Java or JMS configuration dialog....
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.
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, the 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), the Component Manager automatically
queries the associated component queue every 10 seconds. If after 3
seconds an event comes in, the Component Manager again queries the component
queue and processes any additional work found there.
Select the exception handling submap to be used by this component.
The default is Malfunction. See About
System Maps for more information on submaps.
Specify Automatic or Manual
startup mode. If you select Automatic, the adaptor starts when the Component
Manager starts.
Set JAAS credentials by entering a user
name and password that will
be used for identification and permissions on both the Process Engine
and potentially any external systems that will be accessed. See Java
Authentication and Authorization Service (JAAS) on the Sun site.
For Workplace
to use CE Operations, you need appropriate access to the potential
targets in the object store.
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.)
Click Finish when done.
Adding operations
To complete the configuration, select the new component queue and
click Properties on the toolbar.
Click the Operations
tab to import the operations from the Java class or (Workplace
only) specify the JMS event list.
NOTE
On the Component Properties dialog, you can specify exposed fields,
indexes, and security for this component, as well as change the adaptor
and operation properties.
Click Commit on the toolbar
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.