JNDI Server form
Completing the Environment tab

Field

Description

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

Optional. 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 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.

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 pySecurityPrincipal. For more information, see Using the Global Resource Settings feature.

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.

Click this button at any time after you have completed the information on this tab to confirm that Process Commander can connect to the JNDI server identified.

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 you system uses OpenJMS, this button assumes that OpenJMS facilities are installed on the same server as Process Commander. The button fails when OpenJMS is installed elsewhere.)

Click this button at any time 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 + sign next to each node to view additional information about the associated JNDI entry.

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

In the JMS Explorer, choose a Connection Factory using the SmartPrompt. The Destination field is automatically populated. Click Browse Messages to view all messages in the queue.

If your production level is both lower than 5, and the logged in user has the proper Role/Privilege, you can:

• You can add messages to the queue by clicking the Put Messages button and filling out the corresponding form.
• You can remove messages from the queue by clicking the Remove Messages button.