Optimize 10.7 | webMethods Optimize Documentation | Configuring BAM | Managing webMethods Optimize Environments | Configuring Logical Servers | Defining Logical Server Subcomponents for the Infrastructure Data Collector | Defining JNDI Configuration Settings
 
Defining JNDI Configuration Settings
Important:
webMethods Broker has been deprecated.
By default the Infrastructure Data Collector uses the JNDI configuration settings defined for the Default Settings configuration on the Configure Servers tab. If you want to use custom settings for the Infrastructure Data Collector, un-check the Use Default check box and the complete JNDI Configuration settings will be displayed in an editable form.
If a single key and trust store are desired for the environment you can configure the JNDI Configuration under the Default Settings node in the configuration tree (on the Configure Servers tab). If you have individual certificates (Keystores) for each Optimize component you may override the default JNDI configuration by clearing the Use Default check box for JNDI Configuration under the appropriate component in the configuration tree and updating the setting as appropriate.
*To edit JNDI configuration settings for Infrastructure Data Collector
1. Under the Infrastructure Data Collector node in the configuration tree (on the Configure Servers tab), click JNDI Configuration.
2. Clear the Use Default check box to display the JNDI Configuration settings in an editable format.
3. In the JNDI configuration area of the JNDI Configuration for Environment Default Settings area, the first two settings, Broker Name and Naming Factory Type are required for all systems, and the remaining settings are applicable based on your SSL needs.
The following table describes the JNDI Configuration settings.
Field
Description
Broker Name
If you choose “Software AG Universal Messaging” (the default value) as the JMS server in the Naming Factory Type field, this field should be empty. If you select "Broker (deprecated)" as the JMS server in the Naming Factory Type field, this field should display the appropriate Broker name.
Naming Factory Type
Select the appropriate JMS server, either “Broker (deprecated)” or “Universal Messaging”. If you choose “Universal Messaging”, then Broker Name field should be empty. If you choose “Broker (deprecated)”, then the Broker Name field must list the appropriate broker server name.
Enable SSL
Select this check box to enable a secure connection. The check box is unchecked by default and is not required.
Encryption
Select this check box to enable an encrypted connection. The check box is unchecked by default and is not required.
Key Store File
Type the absolute path to the private key file that is located on a server accessible by the component. This field is required only if you enable SSL.
Key Store Type
Click the drop down to select the Key Store Type (PKCS12 or JKS). This field is required only if you enable SSL.
Distinguished Name
Type the name of the appropriate certificate identifier. This field is required only if you enable SSL.
Trust Store File
Type the absolute path to the CA certificate file on a server location accessible by Analytic Engine. This field is required only if you enable SSL.
Trust Store Type
Click the drop down to select the Trust Store Type (PKCS12 or JKS). This field is required only if you enable SSL.
Key and Trust Store Password
Type the pass phrase to access the specified Key and Trust Stores. This field is required only if you enable SSL.
JMS Cluster URL
If your system uses a Universal Messaging cluster as the JMS provider, type the appropriate URL to identify the cluster. Note that, if provided, this setting overrides the JMS Provider URL generated from the JMS Endpoint and the information in the Broker Name field. This field should be coordinated with the value specified in the Naming Factory Type field. The format for this URL is <protocol>://<host>:port, <protocol>://<host>:port, etc. Valid protocols are nsp, nsps, nhp, and nhps. Also, note that you must configure your Universal Messaging cluster in an appropriate manner for your needs and system configuration. Refer to the webMethods Universal Messaging Clustering Guide for more information about configuring and managing Universal Messaging clusters.
Note:
Refer to Defining JNDI Configuration Settings in the section on Configuring Default Settings for Logical Servers for more information about specific JNDI Configuration settings.
4. Click Save to save changes you have made in the JNDI configuration area, or click Reset to discard any changes.
If you click Finish without first clicking Save, any changes made to these settings will be lost.
5. Click Finish to close the Configure Servers tab and return to the Define Environments page.