Show TOC

Development Infrastructure (DI)Locate this document in the navigation structure

Use

Using the SAP NetWeaver Development Infrastructure (usage type DI or NWDI, for short), you can perform:

  • Common user management of the development infrastructure.

  • Configuration of the development environment in the NWDI and administrate the software logistics.

  • Administration of source files.

  • Management of the central build environment.

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

  • Monitoring of the NWDI.

In the following figure you can find a summary of the development and administrative tasks applied in NWDI:

Figure 1: Overview of the development process using the NWDI

Technical System Landscape

The NWDI services - Change Management Service (CMS), Component Build Service (CBS) and Design Time Repository (DTR) process all development steps as an integrated process. The following figure represents the details of this integration:

Figure 2: Technical System Landscape Overview

Tools

For the performance of the NWDI services it is very important that the database statistics are regularly updated. In the NWDI you can use the following tools for different administrative tasks:

Web-based administrative tools of the NWDI:

  • CMS: For creating logical development systems and for software logistics in 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.

Common SAP NetWeaver parts that are used by the NWDI are:

  • 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. The integration can either be done using CMS or CM Services. For details refer to SAP Note 1775838 Information published on SAP site - CMS / CM Services: What to use in which scenario?

  • The developers use the SAP NetWeaver Developer Studio, which is installed locally on their PC, to connect to the development infrastructure. The Developer Studio comes with a separate installation and is not a part of the NWDI installation.

Prerequisites

To be able to use the NWDI, when installing the SAP NetWeaver you have to include the installation options of Application Server Java (AS Java) and Development Infrastructure (DI) . For more information about AS Java, see Administration .

Once the installation is complete you continue with the post installation configuration steps. To manage the configuration, you execute the Functional Unit (FUN) Development Infrastructure (DI) configuration wizard. For more information, see Configuring the Development Infrastructure and Maintenance of an NWDI-Driven System Landscape .

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 SAP NetWeaver Development Infrastructure Security Guide and Configuring the NWDI User Management (in the Developer's Guide).

System Landscape Directory and Name Service

The System Landscape Directory (SLD) helps you to administrate your system landscape. SLD is tightly integrated with the NWDI. The SLD server contains component information, system landscape descriptions, and a name reservation. For more information about SLD, see System Landscape Directory .

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.

  • 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.

Since CMS store files in the file system, you must regularly check that there is enough free disk space.

For more information, see:

Design Time Repository

Regular administrative tasks for DTR are:

  • Creating workspace folders and workspaces.

  • Finding and listing activities.

  • Integrating activities.

  • Managing propagation lists.

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

For more information, see Development Infrastructure in the Developer's Guide.

Component Build Service

The CBS provides a Web-based 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 build spaces, compartments, build requests, development components, build variants and so on.

In addition, you can use the CBS command line tool. The CBS command line tool allows you to retrieve CBS status information and to perform administrative tasks in a shell-oriented environment. In addition to using this tool in interactive mode, you can also embed it into background processing.

The administrator should ensure that the file system folders used by CBS for the build are not under the control of a virus scanner; the, virus scanner should be deactivated. Since CBS store files in the file system, you must regularly check that there is enough free disk space.

For more information, see Development Infrastructure in the Developer's Guide.

More Information