Field | Description |
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 | Select 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. The available templates are: Broker, UM, filesystem, LDAP, JBoss, WebLogic, Qpid-AMQP (0-x) |
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. API Gateway displays the initial context factory for the provider depending on the predefined JNDI template selected. |
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 are using Software AG 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: ![]() ![]() If you are using the filesystem you have to provide the filepath of the location of the file to be used. If you are using Qpid-AMQP option you have to provide the file path location where the amqp.properties file is saved. |
Provider URL failover list | A 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, API Gateway automatically attempts a connection to a JNDI provider specified in this list. Specify one URL per line. Keep the following points in mind when adding JNDI provider URLs to the failover list: ![]() ![]() ![]() ![]() ![]() ![]() |
Security principal | The principal name, or user name supplied by API Gateway 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 API Gateway 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, API Gateway 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. |