Activating configuration management in applications

This topic applies only to the Quality Management (QM) and Requirements Management (RM) applications. Configuration management helps you develop in multiple streams, reuse versioned artifacts in different streams and baselines, and use components to organize artifacts into logical collections. The environment where you will use these capabilities determines how you activate them. In the QM and RM applications, you activate these capabilities by using a key.

Before you begin

  • You should understand the effects of enabling configuration management. Then:
    • For pilot environments, generate an activation key at
      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.
  • You must have Jazz® Administrator privileges.

About this task

This procedure applies to the QM and RM applications.


  1. For the QM and RM applications, go to the administration page: https://fully_qualified_host_name:9443/application_context/admin.
  2. In the left navigation pane, click Advanced Properties.
  3. On the application administration page, search (click Ctrl+F) for Local Versioning Component.
  4. For the Enter license key to enable configuration management property in that section, in the Current Value field, paste the activation key.
    Note: Other IBM Engineering Lifecycle Management (ELM) applications and Jazz Team Server also have this advanced property, but you add the key to the property only in the QM and RM applications.
  5. Scroll to the top of the page and click Save.

What to do next

QM and RM applications: Configuration leads and project administrators must now enable configuration management capabilities in specific project areas. By enabling this feature, these roles can create components that represent collections of artifacts instead of working with all the projects artifacts in one stream; and, within components, team leaders or members can create streams and baselines that use versioned artifacts. Then, teams can add streams and baselines to global configurations.

Change and Configuration Management (CCM) and Architecture Management (AM) applications: No additional enablement steps are required. You can now add streams and baselines to global configurations.