Show TOC

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

 

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.

  • Monitoring of the NWDI.

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

This graphic is explained in the accompanying text.

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:

This graphic is explained in the accompanying text.

Technical System Landscape Overview

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 of all, 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.

For information about the hardware requirements of the NWDI, see SAP Note 737368.

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

For more information about the NWDI architecture, see Development Infrastructure (DI).

Scenarios

The Usage Type Development Infrastructure (DI) is a prerequisite for the following IT Scenarios:

  • Developing, Configuring, and Adapting Applications

    In this scenario, the following scenario variants need the Development Infrastructure:

    • Developing Java Applications Using Web Dynpro.

    • Using Java 2 Platform, Enterprise Edition (J2EE) standards to port and adjust applications.

    • Creating Composite Applications.

  • Software Life Cycle Management

    In addition, since using NWDI is part of the development lifecycle of a product, Usage Type DI is required for the software life cycle management.

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.

  • 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

You have installed the SAP NetWeaver including the usage types AS Java and DI.

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 (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 disc space.

For more information, see Landscape Configurator and Transport Studio.

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 server in the DTR Server Log.

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 buildspaces, 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, virus scanner should be deactivated. Since CBS store files in the file system, you must regularly check that there is enough free disc space.

For more information, see:

  • Administration of the Component Build Service Server. Introduces you to the documentation on CBS administration.

  • CBS Web UI: The Component Build Service (CBS) provides a Web user interface that can be used both by developers and 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 an interactive mode, you can also embed it into background processing.

    Caution Caution

    The CBS command line tool provides some commands that are related to software logistics. These commands are the following:

    End of the caution.

    • downloaddcarc

    • downloadsca

    • uploaddcarc

    • uploadsca

      We strongly recommend that you do not use these commands to bypass CMS. You should execute all tasks related to software logistics in the CMS.

  • Configuring the Component Build Service: Provides information about:

  • Troubleshooting in the CBS

Monitoring the NWDI

Monitoring the SAP NetWeaver Development Infrastructure: You can choose between different tools to monitor the functions of the NWDI.