Development Infrastructure (DI) 

The SAP NetWeaver Development Infrastructure (DI) provides versioning and building functionality as well as life cycle management for Java applications. SAP NW DI is integrated in the SAP NetWeaver Developer Studio to allow the combination of local development and testing with centrally synchronized, team-oriented development.

The main building blocks of the usage type DI are:

·        Design Time Repository (DTR)

Java sources, XML files, and so on, are stored in a hierarchy of files and folders that are visible to the DTR client in the SAP NetWeaver Developer Studio. Each file or folder has its own version history. The definition of workspaces allows you to group sets of files in a particular version for a specific purpose (for example, development, maintenance of delivered releases, and so on).

Developers access the DTR simply by checking out source files or by synchronizing files for read access to their local hard disks. After local development and testing, they check their changes in. The DTR manages distributed versions and is capable of resolving version conflicts when integrating changes from other workspaces.

·        Component Build Service (CBS)

The Component Build Service (CBS) is responsible for building the sources in the DTR. CBS automates the build process in an incremental fashion, meaning, only the changed files, as well as files that have dependency on them, are built. This reduces the source code correction cycles. The build result is deployed to the target server when the build was successful.

·        Change Management Service (CMS)

The CMS is responsible for transporting the software changes centrally to various systems or tracks within the development landscape.