The ActiveControl server software must also be installed in each of the participating satellite SAP systems that will be managed by ActiveControl.
It is not necessary for any participating SAP systems to share transport directories with any of the other SAP systems in the ActiveControl system landscape. If transport files are missing, the ActiveControl domain controller automatically requests the transport files, on demand, from the source SAP system and forwards them to the SAP system that the changes are to be imported into.
The only requirement is that the ActiveControl domain controller must be able to connect to each of the participating SAP systems via the remote function call (RFC) protocol. This RFC connectivity is required to gather transport request information, release transport requests or to perform import actions.
Example 1: Multiple Development Streams with Separate Transport Directories
ActiveControl can support a system landscape with three development streams (such as ERP, CRM and BW), where each development stream has its own transport directories. That is, the development, test, production (etc.) ERP systems share a common set of transport directories, however these transport directories are not shared with any of the CRM or BW systems.
In this example, the ERP development system might be acting as the ActiveControl domain controller for all three development streams, even though none of the SAP systems in the ERP stream share transport directories with either the CRM or BW systems (and vice versa).
Example 2: Single Development Stream with Multiple Transport Directories
ActiveControl also supports a system landscape where the SAP systems of a single development stream do not share the same set of transport directories. It might be that the development and test systems share a common set of transport directories, but for security reasons, the production system has its own set of transport directories.