If a system that runs the OpenEdge Command Center server becomes unavailable, installing OpenEdge Command Center in high availability setup provides failover capabilities. When OpenEdge Command Center is configured for high availability, multiple installations of the OpenEdge Command Center server can be linked by the OpenEdge Command Center database. In the event of a planned or unplanned outage of an OpenEdge Command Center server system, other OpenEdge Command Center server systems balance the load without negatively impacting on the end user as long as the OpenEdge Command Center database remains reachable.

To configure additional systems with the OpenEdge Command Center server, install the OpenEdge Command Center server on each additional system in the same way as you did for the first system. However, during installation, ensure the server is not configured as the primary server, and specify the same data directory used on the first system. The installer validates the database connection from the specified data directory and displays a warning if any errors are detected. After the validation is successful, the database connection details are retrieved automatically, simplifying the installation on the secondary systems.
Note: For a successful connection between the additional server and MongoDB, Progress recommends that you set the dbHostNameAndPort value in the db-config file to <IP of the system hosting the primary server>:<MongoDB port>. This file is located in the data\conf directory within the primary server installation directory on the system. For information on how to edit configurations, see OpenEdge Command Center server configuration.

Install additional OpenEdge Command Center servers

You can install one or more additional OpenEdge Command Center servers to an existing High Availability (HA) deployment.

Prerequisites

Before you install an additional OpenEdge Command Center server in high availability setup, ensure that the following requirements are met:
  • A primary server is already installed and configured on another system.
  • The data directory from the primary server is available on a shared drive that the additional servers can access with read/write permissions.
  • You have the OpenEdge Command Center server installer file that was used for the earlier OpenEdge Command Center installation. For example, PROGRESS_OECC_SERVER_2.x.x_LNX_64.bin or PROGRESS_OECC_SERVER_2.x.x_WIN_64.exe for the Linux and Windows platforms, respectively.
  • The Java Development Kit (JDK) version 17.0.3 or later (within the 17.x major version) is installed on your system.
  • You have administrator privileges on the system where you are installing the OpenEdge Command Center server.

On each additional system that you want in your high-availability deployment of the OpenEdge Command Center server, perform the following steps:

  1. Open a command line as a user with administrator privileges and navigate to the directory that contains the installer file. The installer files available for the platforms are as follows:
    Platform Installer file name
    Windows PROGRESS_OECC_SERVER_2.x.x_WIN_64.exe
    Linux PROGRESS_OECC_SERVER_2.x.x_LNX_64.bin
  2. Run the installer file to launch the installation procedure.

    The installer prompts you to make installation choices and records them after the installation is complete.

  3. On the Introduction page, read the information and then click Next.
  4. On the Host Configurations page, enter the values in the following fields and click Next:
    1. In the Port field, enter the port number on which the OpenEdge Command Center server runs. Its default value is 8000.
    2. In the Management Port field, enter the port number on which OpenEdge Command Center agent connects to the OpenEdge Command Center server. Its default value is 8001.
    3. The Do not validate hostname in TLS connection (nohostverify) checkbox is selected by default, to skip the validation of host name when establishing a connection between the OpenEdge Command Center server and the Authorization server. If you clear this checkbox, the nohostverify property performs host validation, which fails with default certificates, causing failure in:
      1. Connecting the OpenEdge Command Center server with the Authorization server.
      2. Starting the OpenEdge Command Center server.
    4. In the Java Home Directory field, enter the location where you installed the JDK on your system.
      Note: If the JAVA_HOME environment variable is already set, this field is populated automatically.
  5. On the Install Configurations page, enter the values in the following fields:
    1. In the Install Directory, enter the installation directory path. The default installation location for the Linux platform is /usr/oecc/server, and that for the Windows platform is C:\Progress\OECC\Server.
    2. The Install Server as a Service checkbox is selected by default, to install the OpenEdge Command Center server as a service, enabling you to launch OpenEdge Command Center as a service on Windows or Linux platform.
    3. Clear the Primary Server checkbox that is selected by default, to set the OpenEdge Command Center server that you are currently installing as an additional server.
    4. In the Data Directory, enter the path where the primary server stores its data, including the configuration files and email templates.
  6. Review the following information before you complete the installation to ensure that it is correct, and then click Install:
    • Product Name—Progress OpenEdge Command Center Server.
    • Install Directory—Path where the OpenEdge Command Center server will be installed.
    • Data Directory—Path where the OpenEdge Command Center server will store the configuration files and email templates.
    • Port—Port where the OpenEdge Command Center server runs.
    • Management Port—Port where OpenEdge Command Center agent connects to the OpenEdge Command Center server.
    • Java Home Directory—Path where JDK is installed on your system.
    • Disk Space Information (for Installation Target)—Amount of space required or occupied by the OpenEdge Command Center server.
  7. In the Finish Installation section, confirm the successful installation of OpenEdge Command Center server. The OpenEdge Command Center server starts automatically if it is installed as a service. Otherwise, you must start it manually. For information on starting the server as a process, see Start OpenEdge Command Center server.

    If you are using a load balancer, add the newly installed server to it so the server can handle traffic and support failover. Before proceeding, ensure that the primary server is already included in the load balancer configuration. The instructions for adding the server vary depending on the load balancer you are using. See your load balancer's documentation for detailed instructions.

Post-installation recommendations

After a successful installation, the default super admin user account is created to log in to the OpenEdge Command Center server.

Change the password of the default super admin user after your first login to enhance security. Also, change the default email address for creating new users. For more information, see Log in to OpenEdge Command Center.