Using global configurations

Installation

The Global Configuration Management (GCM) application is part of the Rational® solution for Collaborative Lifecycle Management (CLM) application installation. You must install the CLM application, which includes GCM.

Administration

Because the GCM application is part of the CLM application, there are two kinds of administration: CLM administration and GCM administration.

CLM administration includes tasks such as server and repository setup, registering applications with the Jazz Team Server, managing licenses and users, configuring and managing the server.

You can find information about these tasks in Administering Rational solution for Collaborative Lifecycle Management.

Some GCM-specific application administration steps are necessary to enable communication between GCM and the CLM applications, which are outlined in Getting started for application administrators.

GCM administration includes tasks such as creating global configuration project areas, creating and managing global configuration project templates, and role-based permissions.

You can find information about these tasks in Administering global configuration project areas.

Initial setup

Before teams can use global configurations, the user with the Configuration Lead role must set up the GCM environment. This includes setting up components and streams where the teams develop requirements, tests, or designs, adding configurations to the stream, managing the configurations that are part of a stream, and more.

Find information about the workflow in the "Initial setup" section of the Workflow for global configurations

Find out more about tasks for configuration leads in Getting started by task.

Usage

Project managers, requirements engineers, test engineers, design engineers, and developers create configurations in their CLM application, such as for requirements, test plans, design models, and work items. After the initial GCM setup is complete, the configuration lead creates global configurations to assemble the configurations contributed by the CLM applications into a hierarchical tree that shows the product offering.

CLM teams can view their configurations in the higher-level global configuration to create a patch to solve a development problem, privately test changes before they deliver them to a shared stream, create a variation of a physical product or software application by creating a branch, and more.

Find information about how to work in the application in the "Workflow for users" section of the Workflow for global configurations.

Find out more about tasks for configuration leads in Getting started by task.

Find out more about tasks for users in Working with configurations in CLM applications.