On-Premises

You can install CloudCheckr FinanceManager in your on-premise data center using the provided installer. You can automatically deploy it using the silent installation command line options. But you may also execute it as an interactive installer.

Before you can install CloudCheckr FinanceManager, you’ll need the following:

  • a system that complies with the minimal system requirements
  • the software installation executable (EXE)
  • a valid CloudCheckr FinanceManager license key

If you need help on fulfilling one or more of the above requirements, please get in contact with our support department.


Interactive Installation

  1. Launch the EXE file.
  2. Following the instructions on the screen:

    1. Provide a valid license key.
    2. Pick a folder to install the program files.
    3. Pick a folder that the software will use to save its configuration, extraction, and reporting files. This is the home directory.
    4. Provide the TCP port for the API (default: 8002).
    5. Provide the TCP port for the GUI (default: 8001).
    6. Choose an admin username and password.
  3. After the installer completes, restart your computer.

Silent Installation

To execute a silent installation, consider the following command line parameters:

<setup>.exe /S /CLOUDCHECKRFINANCEMANAGER_PROGRAM_PATH=[path] /CloudCheckr FinanceManager_HOME_PATH=[path] /ADMIN_USER=[user] /ADMIN_PASSWORD=[password]

Example:

<setup>.exe /S /CLOUDCHECKRFINANCEMANAGER_PROGRAM_PATH="C:\Program Files\Exivity\program" /CLOUDCHECKRFINANCEMANAGER_HOME_PATH=D:\cfm\home /ADMIN_USER=master /ADMIN_PASSWORD=P@ssword


Upgrading

You can use one of these methods to upgrade your installation of CloudCheckr FinanceManager:

  • Manual upgrade: execute the setup EXE, which detects the installed version and automatically upgrades when you click Next.
  • Silent upgrade: when you execute <setup>.exe /S, your existing installation will be automatically upgraded.

Installing a Valid SSL Certificate

CloudCheckr FinanceManager comes standard with an insecure self-signed SSL certificate. It's recommended to replace the default certificate with an official one, signed by your Certificate Authority. To install a signed certificate, follow this procedure:

  1. Download the 32-bit version of openssl.exe from Win32/Win64 OpenSSL Installation, and install this tool on the server.
  2. Use the openssl.exe to generate a valid key file on the server by executing the following command:
    • C:\TEMP>c:\location\to\openssl.exe genrsa -out CLOUDCHECKRFINANCEMANAGER.key 4096
  3. Run the following command to create a certificate signing request file:
    • C:\TEMP>c:\location\to\openssl.exe req -new -key CLOUDCHECKRFINANCEMANAGER.key -out CLOUDCHECKRFINANCEMANAGER.csr
  4. Provide the general information and be sure to include the FQDN of the CloudCheckr FinanceManager server when asked for:
    • ‘Common Name (e.g. server FQDN or YOUR name) []’
      When asked for a password, leave this field blank and press return otherwise CloudCheckr FinanceManager cannot use your certificate.
  5. Send the generated CSR file to your Certificate Authority. After your CA processes it, you should receive a .crt file.
  6. Rename this file to CLOUDCHECKRFINANCEMANAGER.crt and copy it, together with your CloudCheckr FinanceManager.key file, in your %CloudCheckr FinanceManager_PROGRAM_PATH%\server\nginx\conf. This should overwrite the existing key and crt files.
  7. Restart the CloudCheckr FinanceManager Web Service Windows service, and your signed certificate should now be active.

Configuring a Separate Web Server Portal

In some cases, it might be desirable to separate the web server from the back-end components. You can achieve this by installing two separate instances. Place one instance in a DMZ, and the second instance within a local network as shown in the following diagram:

  1. Install CloudCheckr FinanceManager on both nodes using the standard procedure described in the Interactive Installation section.
  2. After installing the software on the system that should become the user portal, create the following file in the directory%CloudCheckr FinanceManager_PROGRAM_PATH%/server/nginx/conf/sites-enabled:

    server {
                  listen                  443 http2 ssl;
                  server_name             localhost;
              
                  ssl_certificate         CloudCheckr FinanceManager.crt;
                  ssl_certificate_key     CloudCheckr FinanceManager.key;
              
                  error_page              497 301 =307 https://$host:$server_port$request_uri;
              
                  root                    web/glass;
                  index                   index.html;
              
                  charset                 utf-8;
              
                  location ~ /v[0-9]+?/ {
                      proxy_pass          https://HOSTNAME_BACKEND_PORTAL:8002;
                      proxy_buffering     off;
                  }
              
                  location / {
                      proxy_pass          https://127.0.0.1:8001;
                      proxy_buffering     off;
                  }
              
                  access_log              logs/access-webproxy.log;
                  error_log               logs/error-webproxy.log error;
              
                  location = /favicon.ico {
                      access_log          off;
                      log_not_found       off;
                  }
                  location = /robots.txt  {
                      access_log          off;
                      log_not_found       off;
                  }
              
                  client_max_body_size    100m;
              }
  3. Replace HOSTNAME_BACKEND_PORTAL with the actual hostname or IP address of the system that serves as your backend portal.
  4. Set up the config.json in the %CloudCheckr FinanceManager_PROGRAM_PATH%/web/glass directory on the user portal:

    {
    "whiteLabel": false,
    "apiHost": "https://HOSTNAME_USER_PORTAL"
    }
  5. Replace HOSTNAME_USER_PORTAL with the actual hostname or IP address of the system that serves as your user portal. If the user portal must be accessible from the internet, you will need to ensure to provide the fully qualified domain of the user portal.
  6. Restart the CloudCheckr FinanceManager Web Service Windows services. You should now be able to access your user portal.

Using an Internet Proxy When Extracting Data

Because your CloudCheckr FinanceManager instance requires an internet connection, and your network infrastructure requires the configuration of an internet proxy, you must configure the following system environment variable:

  1. Right-click This PC in an Explorer Window and select Properties:

  2. Go to Advanced System Settings and click the Environment Variables button:

  3. Add a new System Variable with the name ALL_PROXY and provide the address of your proxy server as the value for this variable:

  4. In case you do not want to use the proxy for certain address or domains, you can add an additional variable NO_PROXY:

  5. Once you have confirmed the change, make sure to restart both the Windows Services.

How did we do?