Creating a JNDI Provider Alias

In this field...

Specify...

JNDI Alias Name

The alias name that you want to assign to this JNDI provider.

Description

A description for this JNDI alias.

Predefined JNDI Templates

The JNDI template that you want to use.

The JNDI templates provide information that you can use to complete alias configuration for a specific provider.

Note:

After you create a JNDI provider, Integration Server Administrator displays Current Settings as the value of the Predefined JNDI Templates field. This indicates that Integration Server uses the currently specified settings for the JNDI provider alias.

Initial Context Factory

The class name of the JNDI provider. The JNDI provider uses the initial context as the starting point for resolving names for naming and directory operations.

If you selected a predefined JNDI template, Integration Server displays the initial context factory for the provider.

Provider URL

The primary URL of the initial context for sessions with the JNDI provider. The URL specifies the JNDI directory in which the JNDI provider stores JMS administered objects.

If you selected a predefined JNDI template, replace the placeholder information in brackets << >> with information specific to your configuration.

If you are using webMethods Universal Messaging, this is the Universal Messaging realm server in the format nsp://UM_host:UM_port (for example, nsp://127.0.0.1:9000).

If you are using a cluster of Universal Messaging realm servers, supply a list of the URLs to each realm server in the cluster. Use a colon or semi-colon to separate each URL:

Separate the URLs using a comma if Integration Server always attempts to connect to the first Universal Messaging server in the list, only trying the second Universal Messaging server in the list if the first server becomes unavailable

Separate the URLs using a semicolon if Integration Server connects to a randomly chosen URL from the list. This may result in better distribution of clients across the servers in the cluster.

Note:

You must specify a URL for every Universal Messaging server in the cluster. Integration Server connects only to the Universal Messaging servers for which you specify a URL. Consequently, Integration Server creates resources such as destinations or durable subscribers on the specified Universal Messaging servers. If you specify only one Universal Messaging server in a cluster, the resources will be local to that server only.

Note:

If the JMS connection alias uses this JNDI provider alias to connect to Universal Messaging cluster and the JMS connection alias is configured to follow the master, Integration Server always connects to the master realm server in the cluster. By default, Integration Server is configured to follow the master realm server in a cluster. Software AG recommends using a comma-separated list of URLs if the JMS connection alias follows the master. For more information about the Enable Follow the Master option for a JMS connection alias, see Creating a JMS Connection Alias

Provider URL Failover List

The comma-separated list of the failover URLs of the initial context for sessions with the JNDI provider. If the connection to the primary JNDI provider becomes unavailable, Integration Server automatically attempts a connection to a JNDI provider specified in this list.

For more information about setting up a JNDI provider failover list, see Creating a JNDI Provider Failover List.

Security Principal

The principal name, or user name supplied by Integration Server to the JNDI provider, if the provider requires one for accessing the JNDI directory.

For information about whether or not the JNDI provider requires security principal information, consult the product documentation for the JNDI provider.

Security Credentials

The credentials, or password, that Integration Server provides to the JNDI provider, if the provider requires security credentials to access the JNDI directory.

For information about whether or not the JNDI provider requires security credentials, consult the product documentation for the JNDI provider.

Other Properties

Any additional properties the JNDI provider requires for configuration. For example, you might need to specify the classpath for any additional .jar or class files that the JNDI provider needs to connect to the JNDI.

When you select a predefined JNDI template, Integration Server populates this field with any additional properties and placeholder information required by the JNDI provider.

For more information about additional properties or classes required by a JNDI provider and the location of those files, see the product documentation for the JNDI provider.