Working with the Build Environment (SAP Library

Working with the Build Environment

Use

The Component Build Service (CBS) is part of the Development Infrastructure (NWDI). Here you can find information about how to complete the development processes and build the sources with CBS.

An important function of the central build process is to align the work of large development teams. Unlike in the local build, the central build builds the sources in the context of the entire application (as far as it exists at that moment). This allows you to judge at a very early stage whether the individual parts integrate well.

The environment for developing a software component is determined by the import of a development configuration. The development configuration determines the contents of Design Time Repository (DTR) and Component Build Service (CBS). For more information, see CBS Buildspace.

This graphic is explained in the accompanying text

Build process in the CBS

We build the component HR2. The software component (SC) HR is based on the SCs FI and TC.

The build process in the CBS is a build on demand of all the new and dependent components (incremental build), in contrast to the regular build of all components. By knowing the dependencies between components, which are described according to the SAP component model when you create the components, the CBS must execute the build process only for changed and dependent components.

The build process covers the following steps:

...

1. A developer starts the build from within the SAP NetWeaver Developer Studio.

2. The CBS starts a build task.

The build script is provided for a large number of component types.

● The CBS automatically receives the required resources and archives.

● The latest resources (HR2) from the DTR.

● The required archives from the CBS buildspace (HR1, FI and TC).

● The build process starts in the build tool.

● The newly built archives (HR2) are stored in the buildspace (HR_DEV).

Synchronizing Build Tasks

Serializing build tasks would slow down the build process considerably. Therefore, the CBS is able to process several build tasks in parallel. However, this could lead to using obsolete archives, because they may be changed in parallel to the build of a dependent component. (If this happens at a later time, the inconsistent state is automatically corrected by rebuilding the dependent component.) This prevents the CBS from recognizing archives that become obsolete during the build process. In such case, the build process runs again, retrieves the new version of the archive, and stores the version built on the correct archives in the buildspace.

Deployment

The deployment after a successful build process happens automatically. One target is the central test system.

Process Flow

The figure below describes the steps you have to perform to a build in the CBS:

This graphic is explained in the accompanying text

Process Flow

Procedure

1. Configure the system

Prior to working with the CBS, you must have set up the build environment.

More information: Configuring the System for the CBS.

2. Create a buildspace

More information: Managing Buildspaces.

3. Activate the activities from the SAP NetWeaver Developer Studio

More information: Activating Activities.

4. Trigger the build

Using the CBS Web UI you trigger the DC build. The CBS Web UI enables you to check the state of a Component Build Service as well as to perform administrative tasks. To start it, in a browser, go to the CBS Web address: http://<host>:<port_number>/tc.CBS.Appl/ and open the CBS Web UI link.

More information: Triggering a DC Build.