When you initially configure OpenEdge Management or OpenEdge Explorer, you specify the Web server port you want to use. You cannot select the HTTPS protocol for the Web server at this stage, but you can update the configuration options after the installation is complete. You can change the port number and specify whether to use HTTP only, HTTPS only, or both HTTP and HTTPS.
If you select both the HTTP and HTTPS protocols, you can define a list of trusted clients for both protocols. For example, you can restrict clients that attempt to access OpenEdge Management without cryptographic protocols. For HTTP, you might add the local host (or a subnet of HTTP local users) as a trusted client. For HTTPS, you can open data transfer to anyone, keeping in mind that it might add some overhead to communications.
Note: To use the existing command-line interface, HTTP must be enabled and localhost must be defined as a trusted client.
To change the Web server settings, after OpenEdge Management or OpenEdge Explorer are installed for the first time:
1. From the management console, click the Options icon.
The Options page appears.
2. Click Web Server Configuration.
The OpenEdge Management Web Server Configuration page appears with current Web server settings.
3. Select the following transfer protocol options per your requirements:
Enable HTTP protocol
Enable HTTPS protocol
Enable HTTP protocol and Enable HTTPS protocol
Type the port numbers in their respective HTTP port and HTTPS port fields.
To automatically upgrade insecure connection requests to secure connection requests, select Upgrade insecure HTTP requests to HTTPS.
To select this option, you must select Enable HTTPS protocol too.
Selecting this option along with Enable HTTP protocol and Enable HTTPS protocol allows the Web server to redirect all insecure HTTP connection requests to secure HTTPS connection requests. Deselecting this option can result in a less secure connection, so it is recommended that you configure OpenEdge Management with a valid certificate and use this option. For more information about using certificates, see Usingyour own certificate.
4. Set the login session timeout value in the Timeout for logins list. The default value is 30 minutes.
Note: You must log out and log in to enable the session timeout value.
You can also set the login session timeout value in the fathom.properties file by setting the websessiontimeout property with a positive value in seconds. This file is available in the $DLC/properties folder. The entered value is added to the Timeout for logins list.
For example, if you set the websessiontimeout property value as 30, the session timeout value is set to 30 seconds and the value is added to the Timeout for logins list. If you set the property value as 0, session timeout is disabled.
Note: Only users with the Administrator role can set the login session timeout value. Users with the operator role can only view this value.
5. Set one of the following options:
If you want to work with the demo keystore, click Submit. See Using Secure Communication for details about using an HTTPS connection.
Enable HTTP protocol
