Non-ABAP / Java transports and CTS+

In order to deploy non-ABAP / Java transports, ActiveControl utilises CTS+ so this must be setup and configured beforehand.

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 Transport Expresso section.

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

RFC Destinations
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:

• TRANSPORT EXPRESS JD1 – connects to CTS+ controller system CT1
• TRANSPORT EXPRESS JT1 – connects to CTS+ controller system CT1
• TRANSPORT EXPRESS JP1 – connects to CTS+ controller system CT1
  

Target Systems
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:

Transport Paths
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.

Note: For non-ABAP / Java merge targets please refer to the Target Properties Import Options II section for more details on how to setup the conflict detection.