The work performer you build can be based on either a Java™ or Java Message Service (JMS) component queue. For either of these types of work performers, you need to do some preparatory work. To develop a Component Integrator-based work performer, do the following:
Note: See Starting and Stopping the Component Manager for instructions in stopping the Component Manager using the Process Task Manager UI. See also Starting and Stopping a Component Manager Instance.
Refer to the following table for JNDI InitialContextFactory information:
JNDI Configuration |
||
---|---|---|
Application |
Package Pathname of InitialContextFactory |
Required Libraries |
BEA WebLogic® |
weblogic.jndi.WLInitialContextFactory | weblogic_install_dir/server/lib/weblogic.jar |
IBM® WebSphere® with MQSeries® | com.ibm.websphere.naming.WsnInitialContextFactory |
websphere_install_dir/lib/naming.jar |
Tomcat (Sun Java 2 Enterprise Edition (J2EE) Reference Implementation) |
(default, leave blank) |
$J2EE_HOME/lib/j2ee.jar |
JBOSS |
org.jnp.interfaces.NamingContextFactory |
jboss_install_dir/client/jbossall-client.jar jboss_install_dir/client/jnp-client.jar |
Note: If you are using IBM® WebSphere® or JBoss there are Process Task Manager settings necessary, for proper JMS operations. For WebSphere, see Configuration for WebSphere and JMS.
Refer to Authentication and JAAS.
For an example of a login module used by the Process Engine, see Component Authentication Example.
Note: See Starting and Stopping the Component Manager for instructions in stopping the Component Manager using the Process Task Manager UI. See also Starting and Stopping a Component Manager Instance.
If your Java class has dependent modules not included in the JAR file, nor in the existing, specified required libraries (such as, weblogic.jar), you also need to specify as required libraries the JAR file(s) containing the dependent modules.
The polling rate setting determines the rate at which the Component Manager polls component queues for work items requesting services. This rate is normally set to a few seconds (specified in milliseconds). A faster rate may provide a quicker response for an item placed in an empty queue, but too fast a rate can waste computer cycles checking the queue for items, particularly if the queue is empty. To turn off polling, set the polling rate to 0.
You can also configure the Component Manager (not through the Process Configuration Console, but through executing the routercmd script) to use an event-driven mechanism. This causes the Component Integrator to respond to items in a component queue as events (as they arrive). The event-driven mechanism is normally used in place of polling for items, but the Component Integrator can also use events concurrently with polling. For information on configuring your system for event driven Component Queue processing, see the Event Port description in the Component Manager Advanced Properties.
The number of concurrent threads determines the number of service adapter instances configured for each component queue. Setting this value to one (1) is appropriate on single processing platforms. On a multiprocessing platform, setting this to more than one concurrent thread can reduce idle CPU time and exploit symmetric multiprocessing (SMP).
An attempt to import an incorrect parameter type for a component method will cause the import to fail. For specific type mapping information, see Component Operation Parameter Types.
Note: Changes made through the Process Configuration Console while the Component Manager is running are not picked up until the configuration is refreshed. See Components for information on refreshing component configurations.
For an example, see the Content-Extended Operations example.
Note: See Starting and Stopping the Component Manager for instructions in stopping the Component Manager using the Process Task Manager UI. See also Starting and Stopping a Component Manager Instance.
The Component Manager starts the connections for your Java or JMS component queues and manages the processing between the Process Engine and the Java or JMS service adapters. Component authentication takes place when the service adapter initializes.
When a work item is passed to a step that uses a Java component queue, the Java service adapter does the following:
The Java service adapter passes the values of the operation parameters into the method associated with the operation. The values of the operation parameters are defined by:
When a work item is passed to a step that uses a JMS component queue, the JMS service adapter does the following:
Note: Refer to the StepElement XML schema definition to see how JMS component step values are represented by formatted XML String elements.