Table of contents 

• Abstract
• Why do we need a connector?
• A connector in detail
• Connector info
• Schedule list
• Host field list

Abstract

A Connector is a definition of a specific location where a host system stores its data, including necessary authentication information to access the data. A connector will use an API to access planning data that is stored in a database or a file location to access planning data that is stored in a file. Connectors are managed by Setup users. Other users don’t have access to the details of the connectors.

Conceptual visualization of how a connector works: as the connection with the Host system’s database via an API

Why do we need a connector?

ILAP Data exchange needs to understand how to connect to the Host systems that planning data shall be received from and sent to within a transfer. By defining a connector for both the sender and receiver of data, ILAP exchange agreements enable a pathway from and to a specific location.

A connector in detail

Connectors are created and managed by Setup admin, therefore the following information is most relevant to these users. Connectors differ per Host system, but all of them contain the following: connector info, a schedule list and a Host field list.

Connector info

All connectors contain specific information. This is usually the following:

• Connector ID
• Connector title
• Host system
• Authentication type
• Executing component
• Last health check - The timestamp of the last successful connection to the connector

Connector info page of the connector

Schedule list

In most cases, many schedules are stored within the connector. The schedule list offers an overview of all these schedules.

Schedule list page of the connector

Host field list

The third and last page within the connector gives an overview of all host fields that are available in the connector. Some systems allow multiple definitions for use of host fields, these are referred to as Code set.

Host field list page of the connector