Show TOC

Procedure documentationConfiguring Dual-Stack Systems Locate this document in the navigation structure


Your application system has Support Package level SAP NetWeaver 7.0 SPS 13 or higher.


Note Note

For imports of mixed transport requests, you can configure the transport tools in SAP NetWeaver Application Server ABAP to enable a deployment of non-ABAP objects on SAP NetWeaver Application Server Java.

You must execute configuration steps in all source systems and target systems.

End of the note.

Perform the following steps:

  1. Include the SAP NetWeaver Application Server ABAP in the transport domain.

  2. Configure the CTS Deploy Web service for the dual stack system.

    For more information, see Configuring the CTS Deploy Web Service.

  3. Log on to the domain controller.

  4. Call transaction STMS.

  5. Choose System Overview.

  6. Select the AS ABAP that you want to add an AS Java to.

  7. Choose   SAP System   Create   Java Stack Configuration  .

    The TMS: Configure Java Stack dialog box appears.

  8. Optional as of enhancement package 1 for SAP NetWeaver 7.0: If you want to transport Development Infrastructure objects (SCAs, SDAs, or DTR activities) with CTS and use CM Services, set the Create Development Configuration flag under Development Infrastructure.

    In addition to this, enter the URL for a System Landscape Directory (SLD) for the first system with Develpment Configuration in your transport landscape in the following format: http://<host of target system>:5<system number>00.

    Note Note

    You can only specify one SLD URL for each transport landscape. If you want to make changes to the URL for a specific system, then the changes also apply to all systems in the landscape.

    End of the note.
  9. Make the following settings, depending on whether your system is a source system or a target system:

    • Non-ABAP system as source system

      Under Source System Settings, select the Activate Transport Organizer flag and enter the client where you want to use Transport Organizer.

    • Non-ABAP system as target system

      Under Target System Settings, select the Activate Deployment Service flag. Select the required deployment methods. In the Target Host field, enter the host of your target system in the format <host name> and the two-character system number in the System No. field. After saving your settings, the system automatically generates the complete URL to the target system from the values you entered.

      If you have selected the deployment method File with which you can transport any files, then you have to enter a path to a directory in the Directory field where the files can be stored.

  10. Save your settings and confirm that you want to distribute the TMS configuration.

    The system now generates all required parameters and their values automatically by default. To display and modify these parameters, select your system in the system overview and choose the Transport Tool tab page.

    For more information, see Changing the Standard Settings for Source Systems and Changing the Standard Settings for Target Systems.

  11. Depending on the deployment methods selected, the system asks you for the users and passwords for the selected deployment methods. Enter them.

  12. If you selected the Create Development Configuration flag under Development Infrastructure, as described above, the system starts the Development Infrastructure - Configuration Service UI. You can create your development configuration here.

    For more information, see Using the Configuration Service.


You have configured your dual-stack system and you can now check whether your settings are configured correctly (using the transport control program).

To be able to execute transport for dual-stack systems, you must also set the global system change option of the client where the transports are to be executed in the Transport Organizer Tools (transaction SE03) to Modifiable.