About Integration Agent

About Integration Agent

Integration Agent is a zero-maintenance, easy-to-configure, fully autonomous ETL engine, running as background service behind the company’s firewall.  

Integration Agent 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 Etlworks cloud instance and Remote Integration Agent is fully secured as data is not staged. 

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

Integration Agent uses the same ETL engine as Etlworks Integrator so it can run the same flows as Integrator, only locally, without going through the Etlworks cloud instance.

Integration Agent can be integrated with the cloud Etlworks instance, so the flows created in Etlworks Web UI can be downloaded and scheduled to run in Integration Agent.

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

Read more

• Integration Agent user guide.
• Installing and configuring Integration Agent
• Creating flows to run on a remote Integration Agent
• Running 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, Integration Agents are within your data center with access to the needed resources (local file system, databases and so on) and the data ends up directly in the destination cloud application (like Snowflake) without going through Etlworks cloud instance, as the communication is only outbound.

Cloud to local

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

Integration Agents within your data center are pulling the data from the cloud application, without going through Etlworks 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 cloud instance but there are some advantages of offloading this to the remote Integration Agents installed in your data center:

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