Show TOC

Procedure documentationUsing Configuration Services Locate this document in the navigation structure


Use the Development Infrastructure - Configuration Service when developing with Java and you want to manage it with Transport Management System (TMS). For example, you can specify and edit the Build Tool Location, Repository Location, or software components that are to be developed for a development configuration.

This service is available for administrators for including non-ABAP systems in transport domains in the TMS which use the SAP NetWeaver Development Infrastructure (NWDI) for the management and building of Java sources. You can import development configurations that were edited with this service into the SAP NetWeaver Developer Studio (NWDS).


In User Management Engine (UME) you have assigned your user to the group NWDI.Administrators. This group is created with a CTC template for Development Infrastructure (DI) and is only available on systems that were configured with this template.

If you run CM Services on a system other than NetWeaver Development Infrastructure, then you need the role SAP_DI_ADMINISTRATORor a group that contains this role.

For further information, see Authorizations for Change Management Services.


  1. Create a development configuration.

    When creating a non-ABAP system you can create a development configuration for the system by selecting the Create Development Configuration checkbox.

    More information, see Defining and Configuring Non-ABAP Systems.

  2. Load the development configuration.

    To be able to manage an existing development configuration, you first have to load it.

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

  3. Optional: Copy the settings of an existing development configuration.

    You can copy the local settings and software component definition of an existing development configuration to a new development configuration. This can be useful if you need similar development configurations for different systems. The development configurations that you can copy as templates are displayed in a list. You see all development configurations that are configured in the Configuration Service where you are currently logged on.

    For more information, see Copy Settings of an Existing Development Configuration.

  4. Make changes to the local settings.

    • Optional: Enter a logical path that the development configuration is to be assigned to.

      This function only makes sense if you use the NWDS. You can group development configurations by setting them in a logical path. In this way you can build a hierarchical structure that makes it easier to find development configurations for imports into the NWDS.

      For more information, see Grouping Development Configurations.

    • Specify the locations for the Design Time Repository and Build Tool.

      You can enter the required location and the required location of the Design Time Repository (DTR) for the development as well as the Build Tool Location (CBS).

      Note Note

      We recommend that you enter both a Repository and a Build Tool Location. If no Repository Location is entered, then you cannot assign any software components to be developed. If no Build Tool Location is entered, then you cannot assign any required software components.

      End of the note.

      For more information, see Specify Repository and Build Location.

    • Specify the transport settings.

      You can specify settings for exporting data from the system. The export can be executed using the Export Service Web UI or, for closely coupled SAP applications, started when an object is released from SAP NetWeaver Developer Studio.

      For more information, see Managing Transport Settings.

    • Check the settings for the runtime systems.

      You cannot manage the settings for the runtime systems in the Development Infrastructure - Configuration Service. You can only display the settings specified in TMS.

      For more information, see Checking Runtime System Settings.

  5. Specify the software components for the development configuration.

    You can specify which software components are to be developed or modified for every development configuration.

    For more information, see Managing Software Components.

  6. Optional: Export the development configuration.

    If required you can export and distribute the development configurations that you have configured (for example, you can send them as e-mails). The development configuration is exported in XML format. You can import it into your NWDS.

    To export the development configuration, choose the Download Development Configuration link and navigate to the point where you want to save the development configuration.