About the Integration Agent

• Startup
• Business
• Enterprise
• On-Premise
• Add-on

About the Integration Agent

An Integration Agent is a zero-maintenance, easy-to-configure, fully autonomous ETL engine which runs as a background service behind the company’s firewall. It can be installed on Windows and Linux.

It allows you to run Flows that can access on-premise applications and databases. Outbound communication between Integration Agent and the Etlworks Integrator cloud instance is fully secured and data is never staged in the cloud. 

How it works

A few things you should know regarding the Integration Agent:

• It uses the same ETL engine as the Etlworks Integrator, so it can run the same Flows as the Etlworks Integrator, only locally, without going through the Etlworks Integrator cloud instance.
• It is fully integrated with the cloud Etlworks instance, so the Flows created in the Etlworks Integrator Web UI can be triggered to run manually or scheduled to periodically run in the remote Integration Agent.
• The communication session between the Agent and Etlworks Integrator is always initiated by the Agent as we assume that the Etlworks Integrator cannot access the Agent which is running behind the firewall.
• When the user triggers any action, such as Run Flow, Stop Flow, Stop Agent the action is added to the queue. The actions in a queue are executed in order on the next communication session between the Agent and the Etlworks Integrator.  
• The Integration Agent requires a separate subscription with a small monthly fee. Please contact Etlwork's support for more details.

For further reading, check out the articles below:

• Install, configure and monitor the Integration Agent
• Create Flows to run in the Integration Agent
• Schedule and Run Flows in the Integration Agent

Supported scenarios

On-premise to cloud

Example: load data from the on-premise SQL Server database to the Snowflake data warehouse.

In this scenario, the Integration Agent runs in your on-premise infrastructure and has access to the needed local resources (local file system, databases, and so on). The data extracted from the on-premise database ends up in the destination cloud application (like Snowflake) without going through the Etlworks Integrator cloud instance.

Cloud to on-premise

Example: load data from cloud application (for example, Marketo) to the on-premise database.

The Integration Agent runs in your on-premise infrastructure. It pulls the data from the cloud application without going through the Etlworks Integrator cloud instance.

On-premise to on-premise

Example: upload a local file to an on-premise database.

All traffic and data movements stay within your on-premise infrastructure.

Cloud to cloud 

Example: load data from the cloud application (for example, Marketo) to the cloud database (for example, Snowflake).

You would typically run this type of scenario directly in the Etlworks Integrator cloud instance. Still, there are some advantages of offloading this to the remote Integration Agent installed on-premise:

• Load balancing.
• Access to the private cloud resources, not otherwise available from the Internet. 
• Records processed by the Integration Agents will not count toward the record limits set for the account.