The server configuration file (server-config.json) defines the configuration settings that control how the OpenEdge Command Center server operates.

The default location for this file on the Windows platform is C:\Progress\OECC\Server\conf, and that for the Linux platform is /usr/oecc/server/conf.

The sample server-config.json configuration file is as follows: 

{
    "_comment": "Provide complete path for key and certificate files",
    "nodeId": "",
    "port": 8000,
    "managementPort": 8001,
    "dataDir": "",
    "security": {
        "nohostverify": true,
        "key": "${OECC_SERVER}/conf/certs/oeccserver.key",
        "keyPassPhrase": "password",
        "certificate": "${OECC_SERVER}/conf/certs/oeccserver.crt",
        "rootCA": ["${OECC_SERVER}/conf/certs/oeccrootca.crt"],
        "intermediateCerts": []
    }
}
The following table describes the attributes in the server-config.json file:
Attribute Description
nodeId Identifier for the server node.
port Specifies the port number on which the OpenEdge Command Center server runs. The default value is 8000.
managementPort Specifies the port number on which the OpenEdge Command Center agent connects to the OpenEdge Command Center server. The default value is 8001.
dataDir Specifies the path to the server data folder. For example, C:\Progress\OECC\data or /usr/oecc/data.
nohostverify Controls whether the server verifies the host name during mutual TLS handshake. The default value is true. If you want the host name to be validated during the mutual TLS handshake, change its default value from true to false.
Note: When you set nohostverify to false, it performs host validation, which fails with default certificates, resulting in failure of connection between OpenEdge Command Center server and agent. To prevent these failures, you must provide signed certificates to configure mutual TLS authentication with custom certificates, as described in Configure mutual TLS authentication.
key Specifies the path to the private key file of the server used for encryption and decryption.
keyPassPhrase Specifies the password to encrypt the private key. This value is stored in an encrypted format. Similar to database password, you must provide the passphrase in cleartext during server startup. The system automatically encrypts and securely stores it upon initialization.
certificate Specifies the path to the public certificate of the OpenEdge Command Center server that is signed by the root Certificate Authority (CA). For more information, see Configure mutual TLS authentication.
rootCA The path to the public certificate of the signing authority. For example, C:\Progress\OECC\Server\conf\certs\oeccrootca.crt or /usr/oecc/server/conf/certs/oeccrootca.crt
Note: Make sure that you use a valid set of certificates which are signed by same rootCA at both the agent and the server side.
intermediateCerts The certificate chain or the series of certificates between root CA and the public certificate of the OpenEdge Command Center server.
Note: Progress recommends that you replace the default certificates with custom certificates in production environments.