Use the Advanced tab to specify advanced properties for legacy Component Manager.
The Advanced tab includes these fields:
Field | Description |
---|---|
Registry Port | The Java Remote Method Invocation (RMI) port legacy Component Manager uses. The default port is 32771. |
Event Port | The port that legacy Component Manager listens to for incoming
events. The default is 32773. By entering an event port you configure this legacy Component Manager to automatically respond to new events as they occur. (The workflow system communicates with only one legacy Component Manager. If you have multiple legacy Component Managers running, specify the Event Port for only one of them.) When you specify an event port, legacy Component Manager responds to both the component's polling rate and to the incoming events. For example, if a component's polling rate is 10000 (10 seconds), legacy Component Manager automatically queries the associated component queue every 10 seconds. If after 3 seconds an event comes in, legacy Component Manager again queries the component queue and processes any additional work found there. Alternatively, if you set the event port to 0, legacy Component Manager does not automatically respond to new events as they occur; instead, legacy Component Manager polls periodically for new events, based on the polling rate you set for each component. |
JNDI Initial Context Factory | (For Java™ Message Service- (JMS) or Enterprise Java™Bean-
(EJB) based components only) Identifies the class responsible for managing the connection to the Java™ Platform, Enterprise Edition (JEE) Java™ Naming and Directory Interface (JNDI) server. This is usually a vendor-specific class depending on the application server. See Configuring Component Integrator for details. |
JRE Parameters | Extra parameters that are passed to legacy Component Manager
when it is started. This must be used if you are using the JMS adapter with Component Integrator. See Configuring Component Integrator for details. |
Preferred JRE Bin Path | Specifies an alternate Java™ Runtime Environment (JRE) for
this legacy Component Manager. Use this option if the JRE versions
must match (for example, a Java™ adaptor calling an EJB container).
If you leave this blank, the system uses the JRE that was installed
with legacy Component Manager. This is required under certain conditions if you are using the JMS adapter with Component Integrator. See Configuring Component Integrator for details. |