Activating Activities
Use
To activate objects, use the central build process in the Component Build Service (CBS). The activation is carried out if the process was successful or if the option Activate even if build fails has been selected.
The CBS does most of its work automatically – usually all you have to do is start the processes. This also applies to the calculation of activities, which is a prerequisite for the activation of an activity, the predecessor activities. Such a dependency exists if an activity that is not yet activated contains objects of a DC, from which objects are contained in the activity to be activated.
You can set the predecessor check to overlapping files: in this case, only those activities that have at least one file in common with the activity to be activated are considered as predecessors.
The CBS executes these tasks:
● Central build.
● Activating activities.
Typically, several build requests are executed in parallel in CBS. For more information, see Activation in the CBS.
Prerequisites
● You work in the SAP NetWeaver Developer Studio.
● The activities are checked in to the Design Time Repository (DTR).
● You have the required authorizations to perform the activation, which differs depending on whether you activate your own or other users activities. See Roles in the Component Build Service.
Procedure
...
1. From the menu path choose Window → Show View → Other... → CBS Activation and open the Activation view.
You see your closed activities.
2. From the context menu of the activity you want to activate, choose Activate.
The Activation wizard appears. If an activity has dependencies to other DCs, the display shows them: in this case, you get a pushbutton Activate with all Predecessors; if there are no dependencies, you get the pushbutton Activate.
Select Calculate predecessor activities based ONLY on overlapping files only if you are sure that all other objects of your DC will be checked in to other DCs.
3. Choose Activate or Activate with all Predecessors.
A dialog window Activation Request appears.
4. To trace the build process in the Activation Requests view, choose Open Request View; otherwise choose OK.
The source files in your activity are now built centrally and activated. In this process, the predecessors of an activity are activated as well, although only those that are required by the selected activity because it is built on them.
...
1. To get this option in spite of a failed build process, choose Advanced in the Activation wizard.
2. Select the option Activate even if build fails.
Usually, changes that contain errors are not activated because the build fails. In special cases, it may be necessary to activate changes with errors. To do this, use the “activate even if build fails“ option. If a change is activated even though the build fails, all involved development components are in an inconsistent state: the DTR activities were integrated into the active workspace, but no corresponding build results could be written to the archive pool. CBS flags the inconsistent development components as “BROKEN”.
3. Then execute the activation as described above.
Result
For the source files of all activated activities, the CBS now contains runtime objects (archives). Your DCs are now available in the new or changed version in the Active workspace. You can use the Transport view of the Change Management Service (CMS) to release them.
Example
This figure shows the activation of activities. Two groups of developers share DTR and CBS.
The first group creates files for an application (1). The resources are stored in workspace inactive (2). The resources are built centrally in the CBS (3a-c). After a successful build, the CBS automatically sends an integration request for the activity to the DTR (4). The DTR integrates the activity into workspace active (5).
The second group uses the SC of the first group. When they need the resources of the first group, the CBS accesses either the workspace active or the archives of the SC stored in the CBS.
More Information: