Running a PAPI Client in a J2EE Distributed Environment

If your PAPI Java client and the J2EE Process Engines it connects to run in different locations then you must provide the PAPI client the information to connect to the remote Process Engine. You must provide this information using standard JNDI properties.
You must configure JNDI process when the J2EE Process Execution Engine is running in an application server, and the Java PAPI client is running in:

The Java PAPI client needs information to locate a J2EE Engine that is running in a different location. You must provide the PAPI client this information using JNDI properties. The PAPI client uses these JNDI properties to create a Context and connect to the application server where the J2EE Engine is running.

PAPI requires you to specify the following properties:

These are standard JNDI properties. For information about these properties, see your application server documentation. For WebLogic Server, see the Programming WebLogic JNDI document

If your PAPI client connects to a single Process Engine you can specify this properties using system properties, or using a file. To specify this properties using a file follow the procedures described in Configuring JNDI for a Single J2EE Process Execution Engine.

If your PAPI client needs to connect to multiple Process Engines then you have to provide it the information to connect to them using a properties file for each of the engines. To do this follow the procedures described in Configuring JNDI for Multiple J2EE Engines.

If your application server requires that you specify other properties then you can specify them in the same properties file. The PAPI client uses all the properties defined in the properties file to create a Context to connect to the application server.