Skip to main content

JNDI Server form - Completing the Environment tab

Suggest edit Updated on January 29, 2021

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.

FieldDescription
Initial Context Factory

Enter the fully qualified Java class name of the factory class that creates the initial context. Enter a class that is included in the Pega Platform class paths.

VendorFormat
JBoss
org.jboss.naming.remote.client.InitialContextFactory
IBM WebSphere
com.ibm.websphere.naming.WsnInitialContextFactory
Oracle WebLogic
weblogic.jndi.WLInitialContextFactory

Leave blank if the key to this JNDI Server instance is one of the reserved values localEJBs or remoteEJBrefs.
Provider URL Enter a URL for the JNDI service provider, for example:
ldap://somehost:389

The format for this value depends on the application server supporting the service:

VendorFormat
JBoss
remote://hostname:portnumber
IBM WebSphere
iiop://hostname:portnumber
Oracle WebLogic
t3://hostname:portnumber

This field supports the Global Resource Settings syntax (= PageName.PropertyName ). The default property name for this field is pyProviderURL. For more information, see Using the Global Resource Settings feature.

Leave blank if the key to this JNDI Server instance is one of the reserved values localEJBs or remoteEJBrefs.

Security PrincipalOptional. Identify the principal for authenticating the caller to the service. The format of the principal depends on the authentication scheme. If you leave this field blank, the service provider determines the behavior.

This field supports the Global Resource Settings syntax (= PageName.PropertyName ). The default property name for this field is pySecurityPrincipal. For more information, see Using the Global Resource Settings feature.

Security Credentials Optional. Specify the credentials of the principal for authenticating the caller to the service. The value you enter depends on the authentication scheme. It may be a hashed password, clear-text password, key, certificate, and so on. If you leave this field blank, the service provider determines the behavior.

This field supports the Global Resource Settings syntax (= PageName.PropertyName ). The default property name for this field is pySecurityCredentials. For more information, see Using the Global Resource Settings feature.

Test ConnectivityClick this button at any time after you have completed the information on this tab to confirm that your system can connect to the JNDI server.

The system presents test results in a separate window, identifying the parameters used in the test, the steps attempted, and the outcome of each step.

If your system uses OpenJMS, this option assumes that OpenJMS facilities are installed on the same server as Pega Platform. This option fails when OpenJMS is installed elsewhere.

Browse TreeClick this button after you complete this tab to view the JNDI tree for this server. This feature is supported on WebLogic and WebSphere servers only.

The system presents the tree in a separate window. Click the plus sign next to each node to view additional information about the associated JNDI entry.

JMS ExplorerClick to display the JMS Connection Details in a separate window.

n the JMS Explorer, choose a Connection Factory using the SmartPrompt. Similarly, select a Destination. Click Browse Messages to view all messages in the queue.

If your system's production level is both lower than 5, and you have the proper Role/Privilege, you can:

  • To add messages to the queue, click Put Messages and fill out the corresponding form.
  • To remove messages from the queue, click Remove Messages.
  • Previous topic JNDI Server data instances - Completing the New or Save As form
  • Next topic JNDI Server form - Completing the Custom Properties tab
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us