Skip to main content

Install the Production Agent

This guide shows how to install an agentseparated from the server, for production environment.

Overview

Like all agents, the production agent aims to extract data from a given managed system, and transmit said data to the Usercube server. If necessary, the agent also enables the managed system's provisioning according to the orders computed by the Usercube server.

Usercube solution can use several agents, each of them manages a given system. This section is about installing the agent managing the production environment.

Once agents are configured in addition to the default one provided by SaaS, you need to think about what agent to choose during each connector declaration. The appropriate agent has access to the managed system.

Requirements

Ensure that all agent requirements can be met before starting the installation of the production agent.

Requirements for the agent installation can change over the course of the project, according to the project purpose.

Encryption certificates

Ensure that your encryption certificates are valid by checking their: expiration date; signatory; key size exceeding 2048; sha256 and not sha-1.

Server Manager

Ensure that the device used for the installation has the Server Manager program.

Participants and Artifacts

Integrators should have all the elements they need to operate.

InputOutput
Agent prerequisites (required)Production agent

Install the Production Agent

Install the production agent by proceeding as follows:

  1. Create the working directory and make sure it contains the folders: Mails; Sources; Temp; Work.
  2. Configure the agent's application settings via the web.config, appsettings.json and appsettings.agent.json files.
  3. Configure the local server to install IIS via Server Manager.
  4. Configure the application pool and website via IIS.
  5. Set the right permissions on the working directory.
  6. Finalize the production agent's installation.

Verify Agent Installation

In order to verify the process:

  • make sure the website is accessible from IIS by clicking on Browse (in the menu on the right), and from your browser;
  • if logs are enabled, then stop the pool to make sure that no error is thrown;
  • perform from a local device agent-side actions such as sending test emails, reading and/or writing inside working folders, or launching/scheduling agent-side tasks.