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.
Field |
Description |
||||||||
| 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.
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:
This field supports the Global Resource Settings syntax (=PageName.PropertyName). The default property name for this field is Leave blank if the key to this JNDI Server instance is one of the reserved values |
||||||||
| Security Principal |
Optional. 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 |
||||||||
| 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 |
||||||||
| Test Connectivity |
Click 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 Tree |
Click 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 Explorer |
Click to display the JMS Connection Details in a separate window. In 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:
|