Show TOC

Managing Transport SettingsLocate this document in the navigation structure

Prerequisites

You have loaded a development configuration and are now in the Configuration Service.

For more information, see the Display/Change Development Configuration section in this documentation.

Procedure

You must only execute these steps if you want to configure a development configuration that was created in the Transport Management System.

To specify the transport settings for a development configuration, proceed as follows:

  1. Select the Local Settings tab page.

  2. Under Transport Settings - Export Mode enter the file types that are to be exported. You need to decide if you want to execute a Source Export or a Deployable Export (runtime objects). You can also specify the level of granularity with which the exports are to be executed.

    • No Export

      Select this option if you do not want to export any files from the Development Configuration.

    • Source Export

      Select this option if you want to execute source exports.

      • Software Components

        Select this checkbox if you want to allow transports of complete SCAs.

      • Activities

        Select this checkbox if you want to permit the transport of source modifications (Activity Transport) that were released by developers in SAP NetWeaver Developer Studio. In this case the system of your CTS landscape needs at least one target system of type Development Infrastructure DI with a Repository Location and a Component Build Service (CBS).

        For more information on activity transports, see Activity Transports .

      Note

      It only makes sense to transport sources and source modifications if a target system of type DI is connected with the system. Otherwise the import fails.

    • Deployable Export

      Select this option if you want to execute runtime object exports (without sources).

      • Software Components

        Select this checkbox if you want to permit exports at software component level.

        Note that using this export type you can ensure the consistency of software components to be exported since all active modifications of the software components are exported.

      • Development Components

        Select this checkbox if you want to permit exports for selected software components at development component (DC) level. All selected development components will be exported.

        Note that it is not possible to guarantee the consistency of the exported software components with this export type. The user who executes the export must know the dependencies of the development components.

      • Activities

        Select this checkbox if you want to permit transports for all runtime objects at development component (DC) level that belong to one of the activites released by developers in SAP NetWeaver Developer Studio. All deployable DCs that are affected by source modifications are transported.

        For more information on activity-based SDA transports, see Activity-Based SDA Transports .

      Note

      These transport requests do not contain any sources. Only runtime systems are refreshed during imports. It is not possible to import into a target system of type DI.

  3. Enter the export destination and check if the connection is specified correctly using the link to the SAP NetWeaver Administrator on the UI.

    The export destination produces the connection between the AS Java system (where the CM Services are running) and the CTS landscape (ABAP).

    You define the export destination itself in the SAP NetWeaver Administrator of the AS Java system. The destination must point to the communication system which was defined for the non-ABAP system. Destination sap.com/com.sap.tc.di.CTSserver is used by default.

    For more information, see Configuring Export Destinations .

  4. To save the changes, choose Save .