Concepts

Configuration Service

You need a development configuration if you develop software based on the SAP component model and if you use SAP NetWeaver Development Infrastructure for managing sources and executing a central build. The development configuration contains, for example, the location of the Design Time Repository (Repository location) and the location of the Central Build Service (build tool location). One or many software components can be managed with a development configuration. The configuration is saved in the System Landscape Directory (SLD). Before starting with a development, the developer must first import the development configuration into the SAP NetWeaver Developer Studio. You can manage development configurations with the Configuration Service.

When creating a non-ABAP system you can specify whether a development configuration is required for the system. If you are creating a system with development configuration for the first time, then you must also specify which SLD is to be used. This paramater ( DI_SLD_URL) is global and is therefore valid for all systems of a domain.

If a development configuration is required then you must specify the related repository and build tool location and assign software components. Many factors dictate whether a development configuration is required. For example, you need a development configuration for the development system in your transport route if you want to use the activity-based SDA transport.

In addition to this, the Configuration Service enables you to set up your local Java development environment without transport paths to other development configurations and wihtout embedding it in a CTS transport landscape (standalone development configuration).

For more information, see Using the Configuration Service .

Export Service

You can use the Export Service to execute transports at the level of software components (SCAs) or development components (SDAs). The Export Service supports you when exporting SCAs and SDAs from a system by either including the archives in a transport request or putting them in an outbound directory.

For more information, see Using the Export Service .

Import Service

The Import Service supports you when importing SCAs and SDAs of standalone development configurations.

For more information, see Using the Import Service .

Synchronize Service

The Synchronize Service supports you when comparing source and archives between runtime system and NWDI. The versions of the runtime system are important.

For more information, see Using the Synchronize Service .

History Service

Using the History Service you quickly get information and imports and exports that were executed in a specific time period.

For more information, see Using the History Service .