CBS Development Components Details

Properties

The upper part of the view shows the following properties of the DC:

• Name : The name of the DC.

• Vendor : The organization that originally created the DC.

• Parent DC : The DC that contains the current one, or unavailable if the current DC is top-level and has no parent

• Imported : True, if the DC was built somewhere else

• Metadata State : Shows a red light if there is a problem with the DC definition. For example: the DC has references to non-existing DCs; component definition file cannot be read, and so on.

• Compartment : The software component compartment that contains this DC.

• Buildspace : The name of the containing CBS buildspace. From here, you can follow a link to the pending activities of a DC.

From here, you can follow a link to the pending activities of a DC.

Tab Page

Build Status

Shows one line for each build variant that was built for this DC.

• Build Variant Name : The name of the build variant.

• Build Status : The traffic light displays whether the request was successful (green), failed (red), or if it is still being processed (yellow).

• Deployable : True, if the build produced results that can be installed in the target run-time platform (such as the AS Java). This would be false (a red minus sign) if the DC only produces a library that cannot be deployed but must be packed into the deployable result of some other DC.

• Created : The creation time of the latest build request for this DC.

• Completed : The completion time of the latest build request for this DC.

• Request ID : The number of the latest build request for this DC. Click the number to navigate to the request details view.

• Request Log : Shows the request build log.

• Build Log : Shows the build log.

Children DCs

Displays the DC parameters for the inner components of the current DC.

Used DCs

Displays the DC parameters for the used components of the current DC. The grid shows the same properties that are displayed at the top for the current DC.

Here you can select one of the two options:

• Directly used DCs : Shows all DCs that are directly used by the selected DC.

• Brokenness propagated from : Shows DCs that are the cause of a failed build process, or that are the first used DCs in a cyclic dependency.

  If you display DCs with the option Brokenness propagated from , the table contains the column Transitive Usage . This column indicates whether the displayed DC is used directly or indirectly using other DCs (transitively).

  Example

  DC A uses DC B and this uses DC C. In this case, DC A uses DC C transitively. If DC C again uses DC A, the usage is cyclic.

  Note

  If a transitively-used DC has defective metadata and uses another DC also with defective metadata, then the latter is not reported as a cause of the failed build (except if, in addition, a not allowed cyclic dependency exists).

  As in the CBS Buildspace Details view , here you also find links to the used DCs.

Public Parts

Displays the names of the public parts of the DC.

Build the DC

Allows you to trigger a re-build of the DC. The tabstrip is only shown if the DC resides in a compartment that supports activation and if the user has developer permissions.

1. Select the build variants that should be built.

2. Choose Initiate the build to trigger the build.

   Note

   The build is not executed immediately. Instead, the CBS creates a request and puts it into its request queue. The request is executed later by the CBS. The Web UI displays the request ID of the request that was created. By clicking on the request ID you can navigate to the Requests view and view more details.

   The Used DCs , Using DCs and Using DCs by Public Part tabstrips show the DC dependencies CBS has stored in its database.

CBS Web UI does not show all DC dependencies that are defined in the DC definition that is stored in the Design Time Repository. The Web UI shows only the information that is needed by CBS in order to build the components. For normal DCs, only the build-time relationships are shown. For DCs of type Infrastructure or Build Plug-in , the runtime relationships are shown too.

CBS Web UI allows monitoring the state of the CBS. It is not a general purpose DC inventory that shows properties and relationships.

Using DCs Tabstrip

Displays the DC components that are using the current DC. The grid shows the same properties that are displayed at the top for the current DC.

Archive Downloads

Displays links you can use to download different archives for particular DCs. The following archives are available:

• DC Interface Archive: Contains the DC definition and all archives of the public parts of a DC.

• DC Definition Archive: Contains the DC definition of a DC.

• DC Deployable Archive: Contains only the deployable elements of a DC. (Note that the DC must contain deployable elements in order for this type of archive to be available.)

• Public Part Archive: Contains archives of the public parts defined for a DC. (Note that all archives are specific for a particular build variant. You must therefore select the build variant from the dropdown box.)

Initialize Compartment

To repair an inconsistent state of a compartment between CBS and DTR, you use the Initialize Compartment option. For example, you use it if CBS does not have the latest sources from the DTR, or CBS and DTR have different information about the integration into the compartment or workspace. Initializing the compartments process:

1. Clears the caches of the compartment on the CBS.

2. Synchronizes the latest source from the DTR, and retrieves the latest information about the integration from the DTR.

3. Triggers an internal rebuild of all DCs of the compartment.