Install and configure the OpenEdge Command Center server
- Last Updated: April 22, 2026
- 3 minute read
- OpenEdge Command Center
- Version 2.0
- Documentation
Before you install OpenEdge Command Center server, Progress recommends that you perform a set of planning tasks. These tasks include understanding the system requirements for the environment in which you plan to install OpenEdge Command Center server and determining the installation method to use.
Supported platforms
The OpenEdge Command Center server is compatible with multiple operating system platforms. For information on supported operating system platforms, see OpenEdge 12 Platform Compatibility Guide.
Installation modes
- Launch the OpenEdge Command Center server installer—Installs OpenEdge Command Center server and MongoDB in graphical user interface (GUI) mode.
- Install OpenEdge Command Center server in high availability setup—Installs additional server instances to ensure an agreed level of operational performance, usually uptime, for a higher than normal period. The additional servers use the MongoDB configuration of the first server.
- Install OpenEdge Command Center server in console mode—Installs the OpenEdge Command Center server and MongoDB in the console mode, which requires manual entry of configuration settings.
- Silent installation of OpenEdge Command Center server—Installs OpenEdge Command Center from a script, which requires a two-step process. In the first step, you run the interactive installer and record your installation choices in a response file. In the second step, you use the response file to perform non-interactive, batch-mode installations on other systems.
- GUI or interactive mode—The installer prompts you for responses before installing.
- Console or terminal mode—The installer prompts are displayed on the console.
- Silent—The installer runs in the background without any
interference with other processes. You can also record the response
properties file and use it to install OpenEdge Command Center server in
silent mode. Note: If you do not specify a mode, then the installer is launched in GUI mode.
-
Ensure that you have administrator privileges on the system where you are installing the OpenEdge Command Center server.
-
Ensure that the Java Development Kit (JDK) version 17.0.3 or later (within the 17.x major version) is installed on your system.
-
Ensure that you manually provide the MongoDB package if you are installing the server on a system where the firewall restricts the internet access. The installer cannot automatically download the package in restricted environments. For more information, see Provide MongoDB package for offline installation.
- Progress recommends that you uninstall earlier versions of the OpenEdge Command Center server before installing version 2.0. Migration from OpenEdge Command Center 1.3 to 2.0 is not supported.
- The terms OpenEdge Command Center data store, OpenEdge Command Center database and MongoDB are used interchangeably in this chapter and refer to the same database component.
- When you are providing an installation path during the installation and
configuration of the server, make sure that it does not include any of
the following characters:
Also, if the path contains percent‑encoded characters (such as* ? < > | ^ & ; ! $ `%20), verify that they are valid. The installer rejects paths with prohibited characters or invalid encoding. - When running the installer (
.bin) from a directory other than its location, use the absolute path to the file instead of a relative path to avoid any installation errors. - If you encounter any issues during installation or configuration, see Troubleshoot installation and configuration issues for OpenEdge Command Center server and agent.