In order to deploy non-ABAP / Java transports, ActiveControl utilises CTS+ so this must be setup and configured beforehand.
Configuring ActiveControl to manage non-ABAP systems
For each non-ABAP / Java system to be managed by ActiveControl, a new target and RFC destination must be setup as described in the ‘Configuring ActiveControl’ section of this Administration Guide. In this case there are some small differences in the configuration.
For example, you might have the following non-ABAP / Java systems:
- JD1 – Development
- JT1 – Test
- JP1 – Production
The CTS+ controller system in this example is CT1
An RFC destination is required for each system but for non-ABAP / Java systems this must connect to the relevant CTS+ controller system. In the example above these would be setup as follows:
- ACTIVECONTROL JD1 – connects to CTS+ controller system CT1
- ACTIVECONTROL JT1 – connects to CTS+ controller system CT1
- ACTIVECONTROL JP1 – connects to CTS+ controller system CT1
Each non-ABAP / Java system needs to be created as a Target System in the same way as ABAP systems, but with some subtle configuration differences:
|Clients||For the target client specify the client of the CTS+ controller system.|
|Ignore System Id during import (CTS+ only)||For CTS+ systems the SAP system ID is different to the system that is the CTS+ domain controller. In this case the flag should be set to inform ActiveControl that the target is a CTS+ system.|
When creating the transport path the “Valid Source Clients” should be setup for the relevant CTS+ development system and referencing the client for the CTS+ controller. E.g. JD1:100
Once the above setup has been done, ActiveControl will then automatically use CTS+ to process and import the non-ABAP / Java transports.