ActiveControl Integration Framework

ActiveControl Domain Controller

The architecture of ActiveControl can be broken down into: client software, a controlling SAP system, other participating SAP systems and integration systems. The diagram below illustrates the central role of the controlling SAP system – referred to as the ActiveControl “domain controller”.

The majority of ActiveControl (and Integration) configuration is done within the Domain Controller system. Unless specifically mentioned, all SAP setup detailed in this GitLab Integration Guide is done in the ActiveControl Domain Controller SAP system.

* More information on the ActiveControl Domain Controller concept can be found in the main ActiveControl Administrator Guide documentation available at https://docs.basistechnologies.com/.

The Integration Framework Architecture

The ActiveControl Integration Framework is divided between inbound and outbound processes.

• For outbound calls there is a configurable framework that includes data extraction, transformation, mapping and sending routines, alongside error detection, correction and reporting.

• For inbound calls, those made by a third party system into ActiveControl, a number of web services are exposed allowing the external system to manipulate ActiveControl objects. Calls to ActiveControl web services will return appropriate error messages, but expect the calling system to deal with queuing, service levels and retries for failed integration transactions. The inbound solution for the GitLab integration specifically, is detailed later in this Integration Guide.