Show TOC

Background documentationDevelopment Infrastructure (DI) Locate this document in the navigation structure

 

In the SAP NetWeaver Development Infrastructure (NWDI), you can use:

  • Common user management of the development infrastructure.

  • Change Management Service (CMS): You use the CMS to configure the development environment in the NWDI and to administer the software logistics.

  • Design Time Repository (DTR): You use the DTR to administer the source files.

  • Component Build Service (CBS): You use the CBS as the central build environment.

  • System Landscape Directory (SLD) and Name Service: In the SLD, you find the Software Catalog and the landscape description; a Name Service that guarantees the uniqueness of object names is also located there.

  • Integration of the transports with the Change Transport System (CTS) of Application Server ABAP.

  • Tools for monitoring the development infrastructure are available.

This graphic is explained in the accompanying text.

Overview of the development process using the NWDI

Technical System Landscape

All services of the NWDI (CMS, CBS and DTR) process all development steps in integrated processes. The NWDI services use a database for data storage. The SLD integrates them into the entire SAP system.

This graphic is explained in the accompanying text.

Technical System Landscape Overview

All services can run on a shared instance of the SAP NetWeaver and store all their data in the same database in their respective schema. If systems are needed for large development groups, you can extend the landscape step-by-step, by distributing some of the services to own servers.

Note Note

First, you evacuate the CBS as the most performance-consuming service. If the demands continue to increase, several instances of the CBS that use the same database can work using a dispatcher.

End of the note.

The user interface for the developer is the SAP NetWeaver Developer Studio, which is installed locally.

Tools

Web-based administrative tools of the NWDI:

  • CMS: For creating logical development systems and software logistics for all development phases (development, consolidation, assembly, approval) with automated deployment to the runtime systems.

  • DTR: For versioned source file management.

  • CBS: For a central archive management and build environment.

SAP NetWeaver tools that are used by the NWDI:

  • UME: User Management Engine.

  • SLD: Management of available products and components and their names.

  • CTS: you can integrate the transports in mixed landscapes using the AS ABAP transport system.

Prerequisites

You have installed the SAP NetWeaver including the AS Java and DI. More information about AS Java: AS Java (Application Server Java).

Tasks
Security of the NWDI

The services of the NWDI are tightly integrated. To access the NWDI, you need certain roles and permissions. You can create them separately for administrators, developers, guests, and so on. For more information, see Security of the SAP NetWeaver Development Infrastructure.

System Landscape Directory and Name Service

The System Landscape Directory helps you to administer your system landscape. The SLD is a server application that communicates with a client application by using the Hypertext Transfer Protocol (HTTP). The SLD server contains component information, system landscape descriptions and a name reservation based on the standard Common Information Model (CIM).

  • Regular administrative tasks: In order for the SLD service to work properly, you must perform the following administrative tasks for server administration and data management.

  • Technical system landscape: You can use the Technical System Browser to display all registered application systems. From there you can start additional activities for technical systems.

  • Software Catalog: Provides information about products and software components (SCs) and tells you how to define dependencies between software components.

  • Name reservation: To avoid name conflicts, the System Landscape Directory (SLD) offers a name reservation service (also known as the Name Server) which allows you to reserveunique names globally.

  • Data Supplier for the System Landscape Directory: The data supplier for the System Landscape Directory (SLD) collects data on the systems installed in its system landscape and sends it to the SLD.

Change Management Service
  • Configuring tracks: Tracks determine the frame data for the development based on components. You manage and edit tracks in the Landscape Configurator, which allows you to:

    • Configure domains.

    • Create development tracks.

    • Create XI tracks.

    • Edit a track.

    • Connect tracks.

    • Delete a track, and so on.

  • Transporting and creating software component archives: You administer transports in the Transport Studio. You use the Transport Studio to organize and monitor the transport of resource files and archives within your transport landscape. You can also use it for:

    • Checking in archives.

    • Performing imports.

    • Creating software component archives (assembly).

    • Quality assurance (Approval).

Design Time Repository

The tasks you actually perform as an administrator in the DTR also depend on the selected development scenario. In scenarios in which you are using the Developer Studio for development and the DTR for storing and versioning the source files of the project, CMS is not used for software logistics, which is why you must perform many steps in the DTR manually; in other systems, these steps are performed automatically and are therefore not required in the DTR. If this applies to a task, it is mentioned below.

  • Frequently required tasks in the DTR. These tasks consist of:

    • Creating workspace folders and workspaces: This is required only in team development in which no CMS is used.

    • Finding and listing activities: This can be of advantage in all scenarios, but is especially necessary in scenarios in which you use the Developer Studio for development and the DTR for storing and versioning the source files of the project.

    • Integrating activities: This can be of advantage in all scenarios, but is especially necessary in scenarios in which you use the Developer Studio for development and the DTR for storing and versioning the source files of the project.

    • Managing propagation lists: This can be of advantage in all scenarios, but is especially necessary in scenarios in which you use the Developer Studio for development and the DTR for storing and versioning the source files of the project.

  • Logging: Administrators can find important information about the state of the DTR in the DTR Server Log.

Component Build Service

The Component Build Service (CBS) is used only in the development scenario in which the entire NWDI is used. For the software logistics, the CMS is used. This includes creating and preparing buildspaces for the development.

  • Administration of the server contents in the CBS: The CBS provides a Web user interface (UI) that can be used both by developers and by administrators. With the CBS Web UI, users can view the state of the various CBS entities such as buildspaces, compartments, build requests, activities, development components, build variants and so on.

  • CBS command line tool: The CBS command line tool is an addition to the CBS Web UI. It allows CBS status information to be retrieved and administrative tasks to be performed in a shell-oriented environment. In addition to using this tool in interactive mode, you can also embed it into background processing.

Monitoring the SAP NetWeaver Development Infrastructure

Several tools are available for monitoring the functions of the NWDI: