Server Factories

This parameter specifies the server factories to use when using the Remote Method Invocation (RMI). (This parameter is only applicable for the Java Action Processor.)

The TIBCO iProcess Workspace (Browser) installer asks for server factory information if the interface type is RMI. It then writes that information into the <ServerFactories> element in the apConfig.xml file.

You can modify the server factory information, or add additional <ServerFactory> elements if multiple server factories are used.

To configure the server factories to use:

1.

Locate the <ServerFactories> element in the apConfig.xml file:

2.

Enter values in these elements to specify information about the server factory:

—

<UniqueId>: Used to uniquely identify the server factory.

—

<Name>: The name of the server factory.

—

<IsJRMP>: This specifies the protocol used to marshall objects. Setting this to “true” causes the Java Remote Method Protocol (JRMP) to be used; setting this to “false” causes Internet Inter-ORB Protocol (IIOP) to be used. (Note that the protocol specified here must be the same protocol used when constructing xSession objects.)

—

<LoadFactor>: This specifies how the load should be dispersed among the server factories when using multiple server factories. The number specified here is viewed as a percentage of the total of the load factors specified for all server factories. For ease of use, the total of all load factors should total 100 (although it’s not required). For example, if three server factories are used, their load factors might be set to 50, 30, and 20 — the first one will get 50% of the load, the second 30%, and the third 20%.

This defaults to 100. You can can modify this value if you use multiple server factories.

—

<JNDIEnv>: Multiple JNDI environment settings can be specified to use when creating the context used to locate the server factory. Each of these will contain a <Name> and <Value> element to provide specifics about the environment setting.

The installer asks for a “Java naming provider URL” (which specifies the location of the registry when the registry is being used as the initial context). The installer adds this value to one set of JNDI environment <Name> / <Value> element pairs (see the example above).

Another set of <Name> / <Value> element pairs is provided that specifies the initial context factory to use (see java.naming.factory.initial in the example above).