A silent installation runs the installer executable using the -i silent –f <response-filename> command line option. The response file is generated during an interactive installation using the -r <response-filename> option:

  1. When you start an interactive installation using the -r <response-filename> option as an administrator, the data that you enter is automatically recorded in a response file. You can use this file for silent installations in the future. The inputs are recorded in the location specified by the -r option. If you do not provide a full path, the file is created in the same location as the executable or binary (exe/bin).
    Note: You can generate the response file only in the GUI mode of the installer. The installer does not support recording in console mode (-i console).
  2. The installation data captured in the response file is available for playback to perform a silent installation through a batch mechanism.

Response file contents

The data captured in the <response-filename> file provides a detailed snapshot of the installation choices made during an interactive installation and can be used for silent installations after an interactive installation.

The <response-filename> file includes:

  • Host configurations
  • Install configurations

The following example shows an excerpt from the automatically-generated <response-filename> file:

# Mon Mar 17 22:56:37 EDT 2025
# Replay feature output
# ---------------------
# This file was built by the Replay feature of InstallAnywhere.
# It contains variables that were set by Panels, Consoles or Custom Code.



#Host Configurations
#-------------------
OECC_PORT=8000
OECC_MANAGEMENT_PORT=8001
OECC_NOHOST_VERIFY=1
OECC_JAVA_HOME=C:\\java\\jdk-17.0.3+7

#Install Configurations
#----------------------
USER_INSTALL_DIR=C:\\Progress\\OECC\\server
OECC_INSTALL_AS_SERVICE=1
IS_PRIMARY_SERVER=1
OECC_DATA_DIR=C:\\Progress\\OECC\\data

When you create the response file based upon the above template, enter values for the following variables within this template:

For the following variable . . . . . . specify the following

OECC_PORT

The port number on which the OpenEdge Command Center server runs.

OECC_MANAGEMENT_PORT

The OpenEdge Command Center server management port number on which the agent connects to the server.
OECC_NOHOST_VERIFY

Whether to perform the host validation when connecting the OpenEdge Command Center server with the Authorization server. The supported values are:

  • 0—The host name is validated during the mutual TLS handshake and after the installation is complete, the connection is not established automatically.
  • 1—The host name is not validated during the mutual TLS handshake and after the installation is complete, the connection is established automatically.

OECC_JAVA_HOME

The directory that contains JDK, version 17.0.3 or later.

USER_INSTALL_DIR
The directory in which you want to install the server.
Note: The directory must be empty, otherwise, the installation will be terminated.

OECC_INSTALL_AS_SERVICE

Whether to install the server as a service. The supported values are:

  • 0—The server is not installed as a service and not started automatically after installation is complete.
  • 1—The server is installed as a service and started automatically after the installation is complete.

IS_PRIMARY_SERVER

Whether to install the server as an additional server. The possible values are:

  • 0—The server is installed as an additional server and MongoDB is not installed.
  • 1—The server is installed as a primary server and MongoDB is installed during the server installation.

OECC_DATA_DIR
A directory that contains the configuration information of server.
Note: This directory must be empty for the primary server.

Create the response file

You can generate a response file in two ways:
  • Automatically by running the installer with the -r <response-filename> option during an interactive installation.
  • Manually by creating or modifying a response file based on the sample template provided above.
Note:
  • You can generate the response file only in the GUI mode of the installer. The installer does not support recording in console mode (-i console).
  • Before creating the response file, ensure that the OpenEdge Command Center server is not already installed on your system. If it is installed, uninstall it first and then proceed with creating the response file.

To create a response file:

  1. Open a command-line interface with administrative privileges. On Windows, run the command prompt as an administrator. On Linux, run the terminal as a root user.
  2. Navigate to the directory that contains the OpenEdge Command Center installer file, 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.
  3. To record installation choices in the <response-filename> file:

    • For the Linux platform: PROGRESS_OECC_SERVER_2.x.x_LNX_64.bin -r <response-filename>

    • For the Windows platform: PROGRESS_OECC_SERVER_2.x.x_WIN_64.exe -r <response-filename>

  4. Run the OpenEdge Command Center server installer file by performing the steps in Launch the OpenEdge Command Center server installer. The <response-filename> file is generated, which you can rename, if necessary.
    Note: You can modify the variable values in the <response-filename> file, but do not change the variable names.

Run the silent installation

  1. Open a command-line interface with administrative privileges. On Windows, run the command prompt as an administrator. On Linux, run the terminal as a root user.
  2. Navigate to the directory that contains the <response-filename> file.
  3. Enter the following command:
    • For the Linux platform: ./PROGRESS_OECC_SERVER_2.x.x_LNX_64.bin -i silent -f <response-filename>
    • For the Windows platform: PROGRESS_OECC_SERVER_2.x.x_WIN_64.exe -i silent -f <response-filename>
    After you enter the command, the OpenEdge Command Center server initiates silent installation without your intervention.

    A log file of the installation procedure is available in the install_logs subdirectory of the server installation directory.

Post-installation recommendations

After a successful installation, the following accounts are created:
  • Default super admin user account to log in to the OpenEdge Command Center server.
  • Built-in database user account to log in to the MongoDB.
Note: For an additional server configured for high availability, only the default super admin user account is created.

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.