Configuring the MDEX Engine for SSL in Oracle Endeca Workbench

In Oracle Endeca Workbench, you use the EAC Admin Console to configure the MDEX Engine (and Aggregated MDEX Engine) for SSL.

The EAC Admin Console page will let you specify the location of the SSL certificate files and the SSL cipher for the MDEX Engine. By clicking the Show Advanced Options of the MDEX Engine component, you will see three SSL-related fields: SSL Cert File, SSL CA File, and SSL Cipher. The following table lists the meanings of the SSL fields.

SSL Field	Description
SSL Cert File	The path of the eneCert.pem certificate that the MDEX Engine presents to any client. This is also the certificate that the Application Controller Agent should present to the MDEX Engine when trying to communicate with the MDEX Engine. The file name can be a path relative to the component’s working directory.
SSL CA File	The path of the eneCA.pem Certificate Authority file that the MDEX Engine uses to authenticate communications with other Endeca components. The file name can be a path relative to the component’s working directory.
SSL Cipher	An optional cipher string (such as `RC4-SHA`) that specifies the minimum cryptographic algorithm that the MDEX Engine will use during the SSL negotiation. If you leave this field blank, the SSL software will try to obtain a working cryptographic algorithm from its internal list of ciphers, beginning with `AES256-SHA`.

To configure SSL for the Oracle Endeca Workbench:

Log in to Endeca Workbench with the application that you want to administer.
Click the EAC Administration link.
Expand the MDEX Engine component and click Show Advanced Options.
In the SSL Cert File field, enter the full path of the SSL certificate file.
In the SSL CA File field, enter the full path of the SSL certificate authority file.
In the SSL Cipher field, either leave it empty or enter an SSL cipher string.
To save the configuration, click Update.
Note: If the MDEX Engine is running, you must stop it before you can save your changes.