Overview of global configurations

The Global Configuration Management (GCM) application assembles configurations from itself and other contributing Rational® solution for Collaborative Lifecycle Management applications so teams can gain an overall view of the logical or configuration structure of their product offering.

A configuration is a baseline or stream that contains a set of versioned artifacts. A global configuration represents a logical piece of a product offering. By using global and local configurations together, you can manage artifact reuse, traceability between artifacts, and enable parallel development.

Global Configuration Management integrates with the following CLM applications:
  • The Requirements Management (RM) application provides requirements definition and requirements management capabilities.
  • The Quality Management (QM) application provides testing and test management capabilities.
  • The source-control management (SCM) part of the Change and Configuration Management (CCM) application provides work item and development artifact capabilities.
  • The Architecture Management (AM) application provides model design, change set, and requirements management capabilities.
  • The Design Management (DM) application provides design management capabilities.
  • RM and QM applications: An application administrator must activate configuration management in the application and then enable the capability in each project area that will contribute to global configurations.
  • AM application: No activation is required in the application, but an administrator must enable full configuration management in each project area that will contribute to global configurations.
By assembling streams and baselines from different CLM applications, global configurations provide a broader view of the logical structure of your product or solution and can help you achieve these goals:
  • Plan and manage the reuse of configurations in the many versions or variants of your physical or logical product line.
  • Work in parallel on multiple development streams.
  • Re-create a development environment from the past, for example, to branch and create a stream for a product fix.

Team members that use the contributing CLM applications can set a global configuration context in their familiar tools, and the global configuration provides the context across the applications, ensuring that artifact versions resolve to the correct stream or baseline in each application.

When engineering teams can work on multiple development streams or practice reuse across a vast product offering, project leads and their teams better understand the configurations they need to create and reuse, so they can make more effective and timely engineering decisions, while meeting quality goals.

Configuration leads can perform the following tasks that are related to global configurations. Other team members, such as project managers, development leads, or team leads might also complete these tasks when an administrator assigns the required permissions.
  • Set up global configurations to establish a work context across applications for a product offering.
  • Create, modify, and remove attributes, data types, and link types for users to add to global configurations.
  • Add and manage configurations for GCM and contributing CLM applications to a stream.
  • Create a global baseline to capture a milestone.
  • Create a variant of a configuration by branching.
  • Compare configurations.
  • Run a report to detect multiple configurations of a component.
  • Find where a stream or baseline is used in other configurations.
  • View local configurations in a global configuration tree view to see the configurations as a single, logical unit, to move, reorder, remove, or reuse configurations.
Team members can complete the following tasks that are related to global configurations:
  • In a CLM application, set their working context to a global configuration to create or see links to artifacts in other CLM applications.
  • View local configurations in a global configuration tree view to see configurations across applications as a single, logical unit.
  • Add and remove custom and branch attributes, tags, and links for global configurations.

Team members might complete other tasks such as creating streams and baselines if an administrator assigns them permission.

To learn more about getting started, see Getting started with global configurations.

To learn about the workflow, see Workflow for global configurations.

To learn about configuration management, see these articles:

Integration partners

The GCM application integrates with and assembles configurations that contain artifact versions that were created and managed in Rational DOORS Next Generation, Rational Quality Manager, Rational Team Concert®, Rhapsody® Model Manager, and Rational Rhapsody Design Manager.

Rational Jazz integration services

The GCM application is built on the Jazz® integration platform. The software architecture for the GCM application is based on an Open Services for Lifecycle Collaboration (OSLC) specification. OSLC uses a common set of resources, formats, and Representational State Transfer (REST) architectural services to enable data sharing between CLM applications. An Organization for the Advancement of Structured Information Standards (OASIS) OSLC Configuration Management specification describes how to identify and reference versioned artifacts. Applications must conform to the specification to participate in a global configuration and support versioned artifacts. The CLM applications conform to the OASIS OSLC Configuration Management specification.

OSLC provides an open, scalable set of specifications for integrating tools in development environments that include home-grown applications or tools from other vendors. The data sharing supports these transactions:
  • Linking that is based on HTTP protocol
  • Identification of resources by URIs
  • Information retrieval that uses industry standard media types
The collaboration server and data sharing are secured by using the standard HTTP authentication mechanisms and OAuth authorization protocol.