Requirements and installation

Requirements and installation


In order to run the agent correctly, the following setup is required.

Hard- en software requirements

  1. Windows Server 2012 64 bit or 2016 64 bit with 8 GB Ram, minimal of 2 CPU cores with 2.40 GhZ, 150 GB hard drive;
  2. Connection to the internet (possibly via a proxy);
  3. An internet and intranet registered DNS A. The DNS A record refers to the server on which the agent is installed;
  4. A public usable SSL certificate
  5. A web server. E.g. IIS, NginX, etc. which contains at least the configuration described in 1.2.


Authorization requirements

  1. It will need the rights to retrieve data from the given system;

Installation agent

The following steps must be taken to get the agent working correctly.
  1. Register a DNS record referring to the customer server on which traffic is coming in;
  2. Install a browser SSL certificate for the registered DNS record;
  3. In a web server, set the configuration where the following things are set. An example configuration for NginX is shown in appendix 1:
    1. HTTP redirect to HTTPS;
    2. SSL certificaat for all the traffic;
    3. Redirect any incoming request to the agent (port 7070);
  4. Create a separate folder in which the salureconnect_agent.exe is placed;
  5. Create a user who has the necessary rights to the folder where the agent is located and who has the rights as mentioned in the Requirements.
  6. Test the agent if it’s working by opening a Powershell window in the folder where the salureconnect-agent.exe file is located. Start the agent by just executing .\salureconnect-agent.exe. You can add 2 parameters if you want
    1. --listen: The default IP where the agent listens on is 127.0.0.1. You can change this IP with this parameter. For example: .\salureconnect-agent.exe -- listen 0.0.0.0;
    2. --port: The default port where the agent listens on is 7070. You can change this port with this parameter. For example: .\salureconnect-agent.exe -- listen 0.0.0.0 -- port 5005
    3. --ssl: Add the parameter --ssl true to enforce encryption. You can (you don't have to) also change the port to e.g. 443. This looks like this: `salureconnect-agent.exe --ssl true --port 443`
    4. --certfolder: When SSL is enforced, the agent needs a certificate to actually encrypt traffic. Make sure you have a certificate and a key file in a folder on the server where the agent is running. For example, in the certs folder. After you place the certificates in the folder, add the following parameter: --certfolder <folder certs>. Suppose you placed the certificates on c:certs, then the parameter becomes `--certfolder c:certs`. Combined with the previous parameter, the whole thing now looks like this: `salureconnect-agent.exe --ssl true --certfolder c:\agentcerts --port 443`. The certificates should be named as follows:
      1. salureconnect_agent_cert.pem
      2. salureconnect_agent_key.pem
Note that if you use the ssl parameter, the certfolder parameter is mandatory. 

    Create Task

    1. Create a task in the Windows Task Scheduler with the following settings:
      1. General
        1. Run with newly created user;
        2. Check “Run wheter user is logged on or not”;
        3. Do not check “Run with highest privileges”
      2. Triggers:
        1. Begin the task: At Startup
        2. Delay task for: 15 minutes
      3. Actions:
        1. Action: Start a program
        2. Program/Script: The full path to the salureconnect-agent.exe. Add the parameters (see step 6) if wanted.
        3. Start in: The directory where the salureconnect-agent.exe is placed
      4. Settings
        1. Uncheck “Stop the task if it runs longer than:”;
    2. Save the windows task and run it.




      • Related Articles

      • Set File Definition

        Users can upload files into SalureConnect. These files can then be used in dashboards or forwarded to external systems. This article describes how the File Upload functionality is set up. Add A user cannot upload files until a definition exists. A ...