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.
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.
Typically the process to set up a local agent is the following:
Setup.exe
file (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.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.
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:
As a local agent might be down, it’s advised to use retry mechanism or to implement webhooks.
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.
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.
Typically the process to set up a local agent is the following:
Setup.exe
file (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.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.
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:
As a local agent might be down, it’s advised to use retry mechanism or to implement webhooks.