Configuring the Optimize Engines to Communicate with a Secured Broker Server
Important:
webMethods Broker has been deprecated.
In the same way a Broker identity needed to be created in My webMethods Server to communicate with an SSL enabled Broker Server, the Optimize Engines need to be configured to trust the Broker Server certificate and to present their own Certificate(s) for authentication. This configuration can be performed using the My webMethods Define Environments page.
To configure Optimize Engines to communicate with a Secured Broker Server:
1. In My webMethods, navigate the following path: Applications > Administration > System-Wide > Environments > Define Environments
2. Select the environment that was created in the initial installation of the webMethods Optimize platform and select the Configure Servers tab. The SSL properties to use when connecting to the Broker Server are contained in the JNDI Configuration settings. If a single key and trust store is required for the environment you can configure the JNDI settings under Default Settings.
If you are using individual certificates (keystores) for each webMethods component, you must configure a JNDI configuration for each Optimizee engine. Expand the logical server "Analytic Engine" and clear the "Use Default" indicator for the JNDI Configuration. The JNDI properties should now be displayed on the right hand pane. Check the Enable SSL and Encryption flags. Enter the location of the key store that identifies the Analytic Engine. Set the type to PKCS12 and enter the appropriate Distinguished Name. Enter the location of the trust store and the trust stores type. Finally enter the master password used when creating the key and trust stores. Save the configuration.
3. Repeat the process for the Web Service Data Collector and the Infrastructure Data Collector. Use the appropriate keystore and distinguished name for each server.
4. Deploy the changes to the environment and restart the various Optimize components. The restart is required to establish the secured connection to the Broker Servers. Refer to Configuring BAM for information about deploying and environment.