Managing the global configuration hierarchy
The configuration hierarchy is managed by configuration leads, or the team member who
knows how to create and organize configurations contributed by
IBM® Engineering Lifecycle Management ( ELM)
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 reports, and in IBM Engineering Lifecycle Optimization - Engineering Insights ( ENI) views and impact analysis diagrams.
Teams have many reasons to move, replace, remove, and rename configurations in the Global Configuration Management (GCM) tree view.
Customizing access to components and configurations by using team areas
To refine write access to components and configurations in the Global Configuration Management (GCM) application, you can assign a team area to specific items.
Comparing global configurations
Compare global configurations to see content differences between milestones, for example, between Sprint 7 and Sprint 8. The comparison report shows you the child configurations in each configuration that are included, missing, or different.
Updating streams to match baselines in the GCM application
You can update a global stream by replacing its baselines with those from another global baseline. For example, update a stream to include content from a more recent milestone baseline, or roll back to a previous baseline. Configurations in the global stream are added, removed, and replaced to match the baseline that you choose.
Working with sections of the global configuration hierarchy
Focus on a specific section of the configuration hierarchy by setting another configuration as the root in the tree view. You must do this for some tasks, for example, creating streams or baseline staging streams from a baseline that is not at the top of the tree view.
Finding where a stream or baseline is used in configurations
Global configurations contain configurations from this and other applications, often in a tree hierarchy. A find use report shows the list of configurations that are impacted because of a change. For example, if a defect is fixed or a configuration is updated in a contributing IBM Engineering Lifecycle Management ( ELM) application that is part of the current configuration, you might want to understand the impact of this change.
Viewing the history of a configuration
Show history to understand and explore the relationships between and properties for streams and baselines of a component. History results show all configurations of a component. You can show history from a component or a configuration. If you show history from a configuration, it is preselected in the history results.
Archiving global configurations and components
An archived configuration or component is removed from general use. In the Global Configuration Management (GCM) application, archive any global configuration or component that is no longer needed to reduce clutter in lists of configurations or components.
Restoring archived global configurations and components
Restore an archived global configuration or component that you need. For example, your team creates weekly baselines and at the end of a release, you archive the many intermediary baselines that the team no longer needs. After the product is released, the team needs to re-create an environment from one of the intermediary baselines.
Detecting component skew (checking for different configurations of a component)
Component skew occurs when a configuration hierarchy contains different configurations of the same component. The configuration hierarchy can contain multiple contributions from the same configuration, which is not component skew. Configuration leads or administrators in the Global Configuration Management (GCM) application can help determine whether component skew is intentional and fix it as needed.