How it works

Edit online

Datalink (Classic)  architecture

The following diagram illustrates the basic architecture for Datalink (Classic) . One or more connectors reside in one or more agents and control the transfer of data from a variety of data sources to your Apptio instance. You typically configure one connector for each data source. You can run a connector manually or schedule it to run at set time intervals.

The key components of Datalink (Classic) include:

  • Datalink (Classic) Manager - Provides status of the Datalink (Classic) Agents and resides in the Apptio environment .
  • Datalink (Classic) Agent - By default, an Apptio -hosted Datalink (Classic) Agent is preinstalled and can be used to configure connectors for cloud-based data. Other agents can be installed on-premises to access data behind your firewall. All communication between Apptio components is encrypted using TLS.
  • Connector - Datalink (Classic) connectors extract data from a source database and load data or data files into an Apptio instance. You can run connectors manually or schedule them to run automatically at set time intervals.
  • Engine - The Datalink (Classic) Engine is part of each Datalink (Classic) Agent. The engine runs the connectors.
  • Apptio Customer Instance - The Apptio Customer Instance is the database provisioned for each customer.

Apptio includes:

  • Support for Linux and Windows environments.
  • TLS-secure communication between all components.
  • Scheduled automatic running of connectors.

Datalink (Classic) Agent verification process

To prevent unauthorized agents from connecting to the Datalink (Classic) Manager, there is a manual agent verification process. During the Datalink (Classic) Agent installation process, the Datalink (Classic) Agent pings the Manager requesting verification. The administrator manually accepts the agent verification. After an agent is verified, the agent can begin the TLS connection cycle with the Datalink (Classic) Manager.

Datalink (Classic) Agent-Manager communications

Datalink (Classic) agents communicate with your Apptio instance over the internet. For each customer, there is a single Apptio -hosted Datalink (Classic) Agent, but each customer can have multiple Datalink (Classic) agents behind their firewalls. All communication is encrypted using TLS over TCP port 443 (HTTPS). Port 443 must provide full TCP level outbound connectivity. Datalink (Classic) supports TLS 1.2 by default, but also supports TLS 1.0 and TLS 1.1 when required by the source system. It is possible to disable older versions of TLS by changing a system setting. To do so, please contact Apptio Support for assistance.

Datalink (Classic) Agent and manager connection cycle

The following table describes the communications cycle that occurs between the Datalink (Classic) Manager and each Datalink (Classic) Agent. The cycle is repeated periodically.

Step Datalink (Classic) Manager Agent Description
1 <=

Session start

Datalink (Classic) Agent initiates a TLS connection to the Datalink (Classic) Manager registration service.

2 => <=

Data transmission over TLS

  • Heartbeats sent from the Datalink (Classic) Agent to the Datalink (Classic) Manager.
  • Connector heartbeat, execution, and health status is sent from each Datalink (Classic) Agent to the Datalink (Classic) Manager.

Customer data is sent from each Datalink (Classic) Agent to the Apptio customer instance through the Apptio API.

3 <=

Session end

Agent terminates connection to the manager.