Architecture of ActiveControl

The architecture of ActiveControl can be broken down into several core components:

1) a Domain Controller
2) other participating satellite SAP systems.
3) Access methods – consisting of a Windows GUI client software, Web UI and SAPGUI screens.
4) Integration Framework

Figure: The ActiveControl architecture

Like the Transport Management System, ActiveControl has the concept of a Domain Controller. The Domain Controller does not need to be configured in any special way, it is simply the SAP system that the ActiveControl client software connects to and is where ActiveControl configuration and application data is stored.
The server software runs mostly within the ActiveControl domain controller. When necessary, the domain controller connects to the other SAP systems to gather change request information and to perform transports. These connections are made using SAP’s remote function call (RFC) protocol. The Integration Engine is part of the Domain Controller and manages communication with external products and systems.

! The ActiveControl Domain Controller must be the same system in which ChaRM is installed. At present time, it is not possible for ChaRM installed in a separate system to the ActiveControl Domain Controller to be integrated.