About archived global configurations and components

An archived configuration or component is an artifact that is removed from general use. This topic discusses the visibility of archived global configurations and components in the Global Configuration Management (GCM) application, in Jazz™ Reporting Service (JRS) reports, and in Rational® Engineering Lifecycle Manager views and impact analysis diagrams.

To archive or restore archived configurations and components, you must have the Configuration Lead role or the Archive or Unarchive permission for components and configurations, such as streams, baselines, baseline staging streams, or personal streams.

If you have the Archive or Unarchive permission for components, and then you archive or restore a component, you must have permission for the configurations that are part of the component.

JRS and Rational Engineering Lifecycle Manager users:

Archived configurations and components are revealed through the GCM application's tracked resource set (TRS) data source to index providers, such as the Lifecycle Query Engine (LQE). (JRS and Rational Engineering Lifecycle Manager consume the LQE index; the SPARQL queries used to build reports, views, and impact analysis diagrams access the LQE data directly.) Therefore, archived configurations and components might be included in SPARQL query results, which populate JRS reports and Rational Engineering Lifecycle Manager views and impact analysis diagrams.

Update your SPARQL queries if you want to exclude archived configurations and components from the results. Modify the query to add a query match for oslc:archived "false"^^xsd:boolean to exclude archived artifacts.

GCM application users:

Archived configurations and components are not displayed in search and query results, cannot be edited, and are not available when adding global configurations. They are displayed only when referenced by an active configuration. Find archived components and configurations by using the Archived Artifacts search scope.

For example, a baseline is created from a stream. The baseline is then archived, but still is displayed in the Baselines tab of the stream. Similarly, if an archived global configuration is used in another global configuration, the archived global configuration is displayed in the tree view beneath the parent configuration.

Archive and Find Where Used

The results of a Find Where Used operation can include archived global configurations if the root configuration is active. Intermediate nodes on the paths that are used from the root configuration can include archived configurations, as shown in the following image and table.

Example of results for a Find Where Used operation that include archived global configurations

The following table summarizes the expected results of a Find Where Used operation started on Configuration C.

Table 1. Archived global configurations and Find Where Used operation
Archived global configurations Result of Find Where Used on C
None is archived A > B > C
Only A is archived B > C
Only B is archived A > B > C
Both A and B are archived No results

video icon Watch videos

CLM playlist
Jazz.net channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions

Jazz.net forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog