Consistency Checks for Tracks 

Software components are created and maintained in System Landscape Directory (SLD). This means that any changes made in SLD may make the definition of the software components inconsistent with the configuration information of the track in Change Management Service (CMS).

Changes made to the Name Server in SLD may also make the development configuration inconsistent.

Since the data in CMS and SLD is synchronized manually when you use the Update CMS function, it can occur that tracks are still flagged as inconsistent after the synchronization (see also Updating the CMS).

The following checks are possible:

Consistency Check Between the Track Configuration and the SLD Data

If this check discovers an inconsistency, the track is flagged with  Track State is INCONSISTENT in the State column of the track list. You also see a warning dialog box when you select the track in the track list. This warning contains a list of the modified software components that have caused the inconsistency.

This check is made automatically when CMS is updated.

Synchronization of the Dependency Definitions of the Software Components with the SLD Data

When you enter software components in a track, CMS automatically generates a description of the dependency definitions of the software component. When you save the track, this description is saved in the development configuration. Any changes made to the dependency descriptions in SLD or CMS may create conflicts in the dependency definitions.

During this comparison, CMS only takes into account build-time dependencies.

When you save the track, CMS compares the dependency definitions for the software component in SLD with the dependency description configured in the development track. You can see the result of this comparison in the SC State column. The following statuses are possible:

●       SC dependencies are not synchronized

The dependency definitions have not been synchronized with each other. To do this, choose Synchronize SC Dependencies.

●       SC dependencies are synchronized with SLD

The dependency definitions of a software component are the same in both SLD and CMS; no other action is required.

●       SC dependencies are different but accepted by a synchronization

The dependency definitions of a software component in SLD are not the same as in CMS. During synchronization of the differences, the dependency definition in CMS was accepted.

●       SC dependencies are different between SLD and CMS – synchronize the SC dependencies and accept the valid definition

The dependency definitions of a software component in SLD are not the same as in CMS. Synchronize the dependency definitions with Synchronize SC Dependencies and define which dependency definition is valid for the track.

 

For more information, see Resolving Inconsistencies.