Create a JNDI Server data instance to the record information used to log into a Java-EE-compliant application server to obtain Java Naming & Directory Interface® information.
The following tabs are available on this form:
JNDI is used in Connect EJB rules, Connect JMS rules, Service JMS rules, and Authentication Services data instances.
You can use the Records Explorer to review or create JNDI Servers.
The Data-Admin-Connect-JNDIServer class contains JNDI Server data instances. This class is part of the Integration-Resources category.
- JNDI Server data instances - Completing the New or Save As form
Create a new JNDI Server data instance by selecting JNDI Server from the Integration-Resources category.
- JNDI Server form - Completing the Environment tab
Use the Environment tab to find and log into an external Java EE application server to retrieve the JNDI context. If your goal is to connect to an EJB through its local interface or to a remote EJB through an EJB reference rather than its JNDI name, leave this tab blank.
- JNDI Server form - Completing the Custom Properties tab
Use the Custom Properties tab to define additional properties necessary for creating a JNDI Server connection. While the available properties that can be set depend partly on the application server, there are some general ones defined as part of the JNDI spec. See http://docs.oracle.com/javase/jndi/tutorial/.
- More about JNDI Server data instances
Before attempting to access the JNDI server defined by this instance, update the server CLASSPATH Environment variable to include the Java class for the JNDI Initial Context Factory. This change takes effect the next time your system starts. See the Pega Community article About the Process Commander class paths.