About the Integration Agent

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

About the Integration Agent

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

Remote Integration Agents allow you to run Flows that use on-premise applications and databases. Outbound communication between the Etlworks Integrator cloud instance and Remote Integration Agent is fully secured as data is not staged. 

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 can be integrated with the cloud Etlworks Integrator instance, so the Flows created in the Etlworks Integrator Web UI can be downloaded and scheduled to run in the Integration Agent.

Records processed by the Integrations Agents will not count toward the record limits set for the account.

The Integration Agent requires a separate subscription with a small monthly fee, but it is also possible to purchase a perpetual site license. Please contact Etlwork's support for more details.

For further reading, check out the articles below:

• The Integration Agent user guide
• Install and configure the Integration Agent
• Create Flows to run on a remote Integration Agent
• Run Flows on a remote Integration Agent

Supported scenarios

Local to cloud

Example: load data from the local SQL Server database to Snowflake data warehouse.

In this case, the Integration Agents are within your data center with access to the needed resources (local file system, databases, and so on). The data ends up directly in the destination cloud application (like Snowflake) without going through the Etlworks Integrator cloud instance, as the communication is only outbound.

Cloud to local

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

The Integration Agents within your data center are pulling the data from the cloud application without going through the Etlworks Integrator cloud instance.

Local to local

Example: upload a local file to a local database.

All traffic stays within your on-premise data center.

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 on the Etlworks Integrator cloud instance. Still, there are some advantages of offloading this to the remote Integration Agents installed in your data center:

• load balancing
• records processed by the Integration Agents will not count toward the record limits set for the account