Show TOC Start of Content Area

Component documentation Central Build Management  Locate the document in its SAP Library structure

Purpose

The Component Build Service (CBS) is part of the SAP NetWeaver Development Infrastructure (NWDI). The CBS is used in the different development scenarios for the central build of the source codes.

The CBS has two tasks:

     During the build process, it creates the runtime objects (archive) from the source files in the DTR.

     It manages the archives required for the development task: archives that already exist when the development starts are imported into the CBS and new archives are stored after the build process.

The build process in the CBS is based on the SAP component model. During the build process, the CBS checks whether the requirements of the component model are met. Only those components are built (made generally available) that fulfill the component model demands.

Integration

The handling for the developer is embedded into the SAP NetWeaver Developer Studio. For the build process, the CBS automatically communicates with the Design Time Repository (DTR). For further processing, the CBS communicates with the software logistics from Change Management Service (CMS) and Transport Control System.

Features

The CBS plays a central role in the realization of the concepts of the NWDI. Above all, it uses the concepts of the SAP component model. It offers the following main functions:

     Build on request

The central build of changes happens in real-time and at the developer’s request. Compared to the nightly build, this procedure considerably reduces the time needed for troubleshooting.

     Central storage of build results and build tools

CBS offers the build results and the environment required for the build (libraries, generators, build scripts needed for compilation) in a central archive pool. These archives can be downloaded from the SAP NetWeaver Developer Studio into the developers’ local environment. For different development configurations, the CBS provides appropriate versions of the archives.

     Activation concept

There is a distinction between an inactive and an active state of the development objects. To pass changes from the inactive to the active state, you must activate them.  A prerequisite for this is the successful central build of the changed development components. Other development components always use the active state of foreign components; thus they cannot be affected by errors in the inactive state.

Other important properties of the CBS are:

     Deliberately building the changed and dependent development components (incremental build) by using the Component Model.

     Predefined build procedure determined by the type of the development component. The developer no longer has to create build files manually.

     Synchronizing archives/assemblies with source code and used archives.

     Synchronizing the work of development teams in one central build process.

     Connection of the local development processes to a central test environment, which allows testing of how components integrate into the entire application at an early stage.

     Scalability due to multi-threaded build engines and distribution to several server nodes of an J2EE Engine cluster.

 

See also:

 

     CBS Buildspace

     Activation in the CBS

     Rebuild of Dependent Development Components

     Activation in Case of Errors

     Synchronizing Build Tasks

End of Content Area