Getting started with configuration management
Configuration management capabilities in the Rational® solution for Collaborative Lifecycle Management (CLM) enable multi-stream development, artifact reuse, and linking to artifacts across project areas. For the Quality Management (QM) and Requirements Management (RM) applications, a Jazz® administrator must have an activation key and activate this feature at the application level, and then enable individual QM and RM project areas. After you enable these capabilities for a project area, you cannot disable them.
Use configuration management capabilities to create versions of artifacts and link them to other team artifacts, such as requirements and designs. Use configurations (streams and baselines) from CLM applications to manage reuse, traceability, and parallel development. Use the Global Configuration Management (GCM) application to assemble configurations into global configurations to provide a context for resolving links between versioned artifacts within and across CLM applications.
To watch YouTube videos about configuration management, go to the Introduction to configuration management with the IBM® Rational solution for Collaborative Lifecycle Management playlist on the IBM Rational User Education channel.
Teams use their configuration management-enabled CLM applications to contribute requirements, designs, tests, and global configurations to a larger working environment. Global configurations assemble contributed configurations in a hierarchical tree view. Use global configurations to plan and manage the reuse of configurations in the many versions or variants of your software or product line.
In the Design Management (DM) application, you do not have to enable project areas to use configuration management. By default, these project areas are compatible with RM and QM project areas that are enabled for configurations, and team members can create cross-application links to artifacts they need.
In the Change and Configuration Management (CCM) application, there are steps that you must complete to be able to link work items to versioned artifacts in RM and QM project areas. See Linking work items to artifacts in Configuration Management-enabled project areas.
- CLM must be installed. If your project will use global configurations, the Link Index Provider (/ldx) and GCM supporting applications must also be installed.
- Administrators, project leads, configuration leads should see this guidance article for links to videos, considerations, and other resources to help you decide if using configuration management tools is right for your team.
- A Jazz administrator must complete these steps:
- Read about how activating and enabling configuration management affects project areas and other features in CLM applications.
- Obtain an activation key:
- For pilot environments, generate an activation key at https://jazz.net/products/clm/cm/get-key.Note: Configuration management capabilities of RM and QM, and global configuration management is an added service for IBM Collaborative Lifecycle Management on Cloud and IBM IoT Continuous Engineering on Cloud customer environments, and should only be enabled by the SaaS provider. Software configuration management (SCM) in CCM is included in Cloud offerings at no additional cost.
- For production environments, discuss your plans with your IBM Client representative or contact IBM Support.
- For pilot environments, generate an activation key at https://jazz.net/products/clm/cm/get-key.
- Activate configuration management in the QM, and RM applications.
- Project area administrators must enable configuration management for the QM and RM project areas that will use it.
- After one QM or RM project area in a solution is enabled for configuration management, a Report Builder administrator must refresh the list of data sources. This action makes the LQE scoped by a configuration data source available for reporting on data in configurations. See Connecting to data sources.
To read more about local configurations, global configurations, and using them together, see Configurations: Global and local.
To read more about best practices, see Best practices for configuration management in CLM and the IBM Internet of Things Continuous Engineering Solution.
- For the task: if your project links to artifacts in other CLM applications, you must install the Link Index Provider supporting application. If you project will use global configurations, make sure you install the Link Index Provider and the Global Configuration Management applications.
- For the task: this task refers to the process of understanding which development artifacts, such as code libraries, user interface, and so on, are affected by changes. In the CCM application, there is no tool to run to complete this task.