Administering configurations
Before your team can use components and configurations (streams and baselines) in a Requirements Management (RM) or Quality Management (QM) project area, you must activate configuration management capabilities in these applications and complete several other administrative tasks. After you enable this capability, you cannot disable it.
Before you begin
- Read about how activating and enabling configuration management affects project areas and other
features in IBM
Engineering Lifecycle Management (ELM)
applications, and then:
- For pilot environments, generate an activation key at https://jazz.net/products/clm/cm/get-key.Note: The configuration management capabilities of the RM, QM, and Global Configuration Management applications are added services for IBM Engineering Lifecycle Management Base SaaS and IBM Engineering Lifecycle Management Extended SaaS customer environments and must be enabled only by the SaaS provider. The source-control management (SCM) feature 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.
- To activate configuration management for the RM and QM applications, you must have Jazz® Administrator privileges.
- To view and manage configurations, you must have either project area administration or configuration management permissions. On the Permissions page for an RM or QM project area, see the Configuration Management permissions.
- QM application only: If your team doesn't do multi-stream development, and doesn't use components and global configurations, you can enable a project area to use only baselines: work in one stream and take baselines as needed to capture artifact versions at milestones or critical points in a release. See Enabling QM project areas to use baselines.
About this task
After you activate configuration management for an application, enable the capabilities for the project areas that will use it, and assign configuration management permissions to your team members, your team can create and use configurations to work in parallel streams.
Your team can then group configurations to represent components of a product. These groupings of configurations are called global configurations. To use them, you must install the Global Configuration Management (GCM) application and complete other administrative steps. For more information, see Getting started (with global configurations) for application administrators.