Passer au contenu principal
Adaptive Insights
Knowledge and Support - Adaptive Insights

Adaptive Integration Data Agent Technical Requirements

Adaptive Data Agents

The Adaptive data agent is a component of Adaptive Integration. It runs on a customer’s on-premises server and is used to extract information from a JDBC-compliant database or a custom scripted data source. Data agents can also be used to export data from Adaptive Planning. The data agent requires a computer running Windows. The data agent is hosted as a Windows service and is deployed behind a customer’s firewall. The data agent manages access to on-premises applications as well as connections to Adaptive Integration on the cloud.

Data agents are managed by the Adaptive Data Agent Service (the “Agent Service”), which is a Java application installed behind the customer’s firewall and that runs as a Windows service. The Agent Service long polls the Adaptive Gateway (a server that brokers communication through the firewall to on-premises instances of the Agent Service), which receives requests from Adaptive servers on behalf of all data agents hosted by that instance of the service. Each installed instance of the Agent Service can host multiple data agents.

The installation includes the Adaptive Data Agent Service Manager, a desktop utility the customer uses to perform the initial setup and configuration of the Agent Service. The installation optionally includes Pentaho Kettle and Spoon, the Kettle ETL Designer. If the optional Pentaho Kettle components are used, the Agent Service manages a pool of Kettle ETL execution instances (job runners), each of which is a Java virtual machine running in its own process. It delegates any Kettle ETL scripts to be launched to a free job runner. Adaptive has delivered plugins to enable design-time connectivity between the Spoon environment and Adaptive Integration. This allows for authenticating into a cloud instance of Adaptive, publishing scripts to the cloud, and testing the script-based integration from within the Kettle UI. Note that the optional Pentaho components are needed only if there is a requirement to use a Pentaho Kettle script to extract data. Such components are not needed if the data agent is being used to extract data out of JDBC-compliant databases using Adaptive Integration’s JDBC data sources.

The on-premises data agents are managed and controlled from the cloud using the agent UI. The agent UI is part of Adaptive Integration’s data designer, which is accessed through a web browser. When an agent is created in the data designer, the customer can download and install the latest version of the data agent, along with the optional Pentaho Kettle components. The agent UI shows the current status and version details of the agents and allows the customer to provision/unprovision/suspend/resume data agents. The customer can also upgrade to a newer version of the data agent through the agent UI. For more details, please refer to Adaptive Integration.

Technical Specifications

The following technical specifications are recommended for the machine the data agent will reside on. Exact specifications will depend on data volumes and should be reviewed with an Adaptive Professional Services consultant.

Operating System

Supported platforms:

  • Windows 2012 Server (R2)
  • Windows 2008 Server (R2 is recommended)
  • Windows 10
  • Windows 8.1
  • Windows 7

Java versions supported:

  • Java 8 (Only for the 2017.1 Data agent V60 and newer)
  • Java 7 for the legacy data agent earlier than V60.

Disk Space

60 GB of disk space is recommended. This is used for temporary files and disk caching and actual size needed will vary based on the needs of the customer’s implementation.


A minimum of 8GB is recommended. If a virtual machine is used to host the data agent, 12GB is recommended.


The data agent uses HTTPS to communicate with the Adaptive servers. Port 443 (default port for HTTPS) is used by the Data Agent Service Manager to communicate with the Adaptive servers and other web-based sources.


One machine running the agent service cannot serve tenants in multiple geographies.

Domain Whitelisting

Traffic balancing and data sovereignty/data residency management requires whitelisting * domains. 

  • Cet article vous a été utile ?