Using advanced HTTPS options when trending remotely

If you want to use HTTPS for communications with a remote OpenEdge Management Trend Database, you can also use the following advanced options:

A Trust Keystore other than the demo provided by OpenEdge Management

A proxy server

To use the advanced options:

1. From the OpenEdge Management Trend Database Configuration page, click Advanced Options. The expanded OpenEdge Management Trend Database Configuration page appears.

Under HTTPS Configuration, the full path name to the demo keystore (demoTrendTrustKeystore.zip) appears in the Keystore path name field.

Note: Although the demo keystore is a .zip file, the .zip file format is not a requirement for a keystore. You can also use a .cer file or a .pem file as the keystore.

2. Type the keystore name in the Keystore path name field to use a keystore other than the demo keystore.

3. Set the Enabled protocols options to change the default cryptographic protocols. By default, remote trending databases support SSLv3, TLSv1, TLSv1.1, and TLSv1.2.

4. Enter comma-separated cipher suite values in the Enabled cipher suites field to manually set cipher suites. By default, OpenEdge Management and OpenEdge Explorer supports all the cipher suites that are provided by the SSL implementation of the Java Secure Socket Extension (JSSE).

5. If you want to use a proxy server, do the following:

a. Select the Use a Proxy server option.

b. Type the host name in the Proxy host name field.

c. Type the server port number in the Proxy server port field.

6. Click Submit. A message appears confirming that the configuration has been successfully updated.

7. Click OK.

Note: The changes that you make to the configuration might require you to reconnect (log in again) to OpenEdge Management.