Skip to content

Post-Installation Configuration

After successful installation using the NorthStar CCM installer, follow these additional steps to ensure your machine is configured properly.

Changing Initial Configuration

Some settings like database, storage, ports, or SSL are configured during installation. To modify these settings, we recommend running the installer again.

The installer will automatically detect previous database/storage configurations and offer to use them. We recommend using this option if you want to review and modify the settings for your database and storage.

Warning

Specifying database and storage explicitly is not recommended when a previous configuration is available. If you need to specify database and storage explicitly, read below:

  • If you point the installer explicitly to a database previously used, the installer will upgrade the database to the current version while preserving its contents.
  • If you point the installer explicitly to a storage folder previously used, the installer will use the contents of that folder without deleting them.

Note

The database and storage are deeply linked and cannot function properly if they are out of sync. It is critical that the selected database and storage have been used by the NorthStar CCM Platform in the same configuration before, and that they have not been altered since the last time they were used.

IIS Manager Configuration

Updating Bindings for Website Remote Access

If you want to access one of the NorthStar CCM Platform websites remotely, follow these steps for each NorthStar CCM website:

  1. Open IIS Manager.
  2. From the Connections tree view, navigate to the NorthStar CCM website exhibiting the issue.
  3. On the right-side pane, select Bindings.
  4. Edit the existing binding and change localhost to * (to accept all connections) or specify an IP address.
  5. Click OK to save the changes.

Warning

Doing this makes the website accessible from the intranet if the firewall allows it. Make sure this is the intended functionality, and that website access (especially for System Administration) is properly secured before making the change.

Enabling Secure Connections

Enabling HTTPS can be done in two ways:

  • Automatically, by re-running the installer.
  • Manually, by changing bindings in IIS and updating the main configuration file.

Both methods require a valid and appropriate SSL certificate to be installed on the server hosting the website(s) for which you want to enable HTTPS.

Note

In a multi-server setup, regardless of which method (automatic or manual) is used, the steps must be performed on all servers in the multi-server setup. This includes HA scenarios.

Enabling HTTPS automatically

Re-run the installer and choose Enable Web Site SSL for each website you want to make accessible through HTTPS. When checking the box, make sure to select the correct certificate from the list that appears.

Enabling HTTPS manually

  1. Add the appropriate bindings in IIS:
    1. Open IIS Manager.
    2. From the Connections tree view, navigate to the NorthStar CCM website for which you want to enable HTTPS.
    3. On the right-side pane, select Bindings.
    4. Add a new binding, or edit the existing binding and change http to https.
    5. Click OK.

  2. Update the corresponding host URL in Domain Settings:

    • Enterprise Website: https://<hostname>:<port>
    • Sysadmin Website: https://<hostname>:<port>
    • Customer Portal Website: https://<hostname>:<port>

    Usually this only means changing http to https in the configuration file, leaving the hostname and port (if present) unchanged.

  3. After making these changes, apply the new configuration values:

    • Restart the MHC service: open Windows Task Manager and restart the MHC Omni System 4 Service.
    • Restart the IIS service, either from the IIS Manager tool or by opening an administrator command prompt and running iisreset.

Note

This procedure can also be applied in reverse, to change from HTTPS to HTTP.

Set up Whitelist Folders

Configure the whitelist folders as needed for the new NorthStar CCM version. These folders should allow specific permissions and ensure smooth operation while maintaining security.

Whitelist for HTTP(s) Calls

In the latest version, enabling the Publishing/Data Engines to make HTTP(s) calls requires additional configuration.

  1. Navigate to C:\ProgramData\MHC Software. Create a file named appSettings.json with the following content:

    appSettings.json
    {
  "http_dns_whitelist": [
    {
      "address": "*"
    }
  ]
}

    Note

    The configuration above will whitelist all URLs.

  2. Add the following parameter to the configuration files for both the Publishing Engine (PublisherSvc.config) and Data Engine (DASSvc.config):

    AppSettingsPath=appsettings.json

Whitelist setup to enable GetFiles and CopyToFolder workflow steps

  1. Navigate to the server where NorthStar CCM has been installed.
  2. Create a text file on the server — for example, Whitelist.txt.

  3. Open it in a text editor and list all directories/paths or shared network folders to be whitelisted, for example:

    Whitelist.txt
    C:\Temp\outfiles
D:\
\\ROECR-LP49\GetFiles

  4. Go to C:\ProgramData\Ecrion and open EOS4.config.

  5. Add the following parameter, pointing to the path of the whitelist file you just created:

    WorkflowWhiteListPath=<the path where your above .txt is>

  6. Restart the MHC services — specifically the MHC Workflow Windows Service and MHC Omni System 4 Service — to apply the changes.

Additional Optional Configuration

All configurations described below can be found at C:\ProgramData\MHC Software.

EOS4.config Config Parameters

MaxAllowedRequestSize

MaxAllowedRequestSize = 2000
  • Specifies the .zip size limit for Environment imports.
  • Default value: 100 MB

Request Body Limitation Parameters

These parameters are used to limit the request body size, to prevent timeouts caused by data arriving too slowly:

MinRequestBodyDataRate = 240        # bytes per second (default)
MinRequestBodyDataRateGrace = 5     # seconds (default)

Uninstallation

Follow these steps to remove NorthStar CCM from your computer.

  1. On the computer running the NorthStar CCM software, log in as a local or domain administrator.
  2. Open Control Panel.
  3. Select Uninstall a program from the Programs area.
  4. In the Uninstall or change a program window, select your version of NorthStar CCM.
  5. Click Uninstall from the toolbar.
  6. A confirmation message appears — select Yes to remove the NorthStar CCM software from your machine.
  7. A warning message appears — click Yes to continue, then wait until the software finishes uninstalling.