Show TOC

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

 

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

  • Common user management of the development infrastructure.

  • Change Management Service (CMS): You use the CMS to configure the development environment in the JDI 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, which guarantees the uniqueness of object names, is also located there.

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

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 central archive management and build environment.

SAP NetWeaver tools that are used by the NWDI:

  • UME: User Management

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

For more information about using these tools in NWDI, see Working with the SAP NetWeaver Development Infrastructure.

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 SAP NetWeaver Development Infrastructure 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. 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 "reserve" unique 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

Administration of the Change Management Service. Introduces you to the CMS administration. You use the CMS within the entire JDI for configuring the development environment and for software logistics administration. You use the CMS to perform the following administrative tasks:

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 SAP NetWeaver 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.

  • Administration of the Design Time Repository Server. Introduces you to the documentation on DTR administration.

  • User Authentication and Authorization in the DTR: For the DTR, you can grant permissions individually for each object.

  • Frequently required tasks in the DTR: You must perform these tasks more frequently if you do not use CMS. They are described here for the command-line client. For a list of all commands, see

    DTR Command Line Tool. To create workspace folders and workspaces and to maintain authorizations, you can also use the

    DTR administrator plug-in, which offers a graphical UI. These tasks consist of:

    • Creating workspace folders and workspaces: This is required only in scenario 1 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 SAP NetWeaver 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 SAP NetWeaver 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 SAP NetWeaver 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 server in the DTR Server Log.

Component Build Service

The Component Build Service is available only in development scenarios, 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 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 SAP NetWeaver Development Infrastructure

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