Local agents are used for on-premise connectors that cannot be accessed through the cloud. Chift has developed a local agent that can be run on on-premise connectors’ servers and that will act as a proxy between your the server and Chift’s infrastructure making it possible to expose an API on top of those connectors.
This is typically used for connectors like Winbooks, Sage 100, Sage 50, etc.

​
How it works

The local agent does not require any specific network configuration. It will connect to Chift’s cloud infrastructure and it will not expose any port to the internet.

​
Setting up a local agent

Typically the process to set up a local agent is the following:

  1. The consumer visits the public connexion page of a connector and clicks on “Connect”.
  2. The consumer will have the possibility to download a zip file or send a link to this zip file to another person (useful when the installation needs to be done by a third-party)
  3. At this moment the consumer will have a connexion which not yet operational.
  4. The consumer or his technical contact will have to extract the zip file and install the Setup.exefile (alongside a settings.json file containing the information related to this specific connexion). This is will install a Windows service on the server on which the connector is running that will act as a bridge with Chift.
  5. Once the service is installed, the connexion will become green on the consumer’s dashboard and you will be able to execute requests.
  6. At any time, you can see the status of the local agent and see his latest heartbeat. Webhooks can be configured as well to be notified of the status of the local agent.

For every connector, you will find specific documentation in the connector’s documentation and as well in the end-user connector’s documentation to ease the process of installation.

​
Monitoring a local agent

Through the Chift’s dashboard, you will be able to see the status of the local agent and see his latest heartbeat (sent every 15-20 minutes).
On a consumer’s page, you will see wheter the agent is:

  • Online and operational: green
  • Offline: orange (it’s installed but not running currently)
  • Offline: red (the service is not installed)

As a local agent might be down, it’s advised to use retry mechanism or to implement webhooks.

​
Local agent updater