Getting started with configuration management

Configuration management capabilities in the IBM® Engineering Lifecycle Management (ELM) enable multi-stream development, artifact reuse, and linking to artifacts across project areas. These links bring you information about initial steps for you to take.

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 ELM 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 ELM applications.

After an administrator enables these capabilities for a project area, you cannot disable them.

To watch YouTube videos about configuration management, go to the Introduction to configuration management with the IBM Engineering Lifecycle Management playlist on the Software Education channel.

Teams use their configuration management-enabled ELM 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.

Before your team can use these capabilities, these actions are required:
  • ELM 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 Configuration management in IBM Engineering Lifecycle Management (ELM) version 7 releases for links to videos, considerations, and other resources to help you decide whether configuration management 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 ELM applications.
    • Obtain an activation key:
      • 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 should only be enabled 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.
    • 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 IBM Engineering Lifecycle Management.

The following diagram shows a simplified workflow for configuration management. Click a box in the diagram to see more information about a high-level configuration management task.
Note:
  • For the Install > Install ELM task: if your project links to artifacts in other ELM 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 GCM applications.
  • For the Change and Configuration Management (CCM) > Analyze the impact of a requested change 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.
The image shows high-level steps for using configuration management capabilities. Click for more about installing ELM Click for more about upgrading ELM Click for more about activating configuration management capabilities in ELM applications Click this area to get information about enabling configuration management in project areas Click for more about creating a component to establish a work context Click for more about creating the global configuration hierarchy Click for more about enabling linking between EWM work items and versioned artifacts Click for more about creating configurations in ELM project areas Click for more about creating a stream to work in Click for more about switching to a configuration to work in Click for more about optionally creating change sets to group your changes Click for more about creating and editing artifacts in the RM application Click for more about cross-application linking to versioned artifacts after enabling configuration management in RM and QM project areas Click for more about working with multiple change sets in a personal stream Click for more about making your changes visible by delivering your change sets Click for more about comparing configurations Click for more about reusing artifacts by delivering change sets to other streams Click for more about creating baselines Click for more about creating a stream to work in Click for more about switching to a configuration to work in Click for more about creating and managing test artifacts Click for more about cross-application linking to versioned artifacts after enabling configuration management in RM and QM project areas Click for more about comparing and reusing test artifacts by merging configurations Click for more about planning the project Click for more about creating tasks or change requests Click for more about linking to artifacts that are affected by the change Click for more about linking tasks to change sets Click for more about creating EWM streams to work in Click for more about creating baselines to capture the state of work for a release Click for more about showing versioned artifact information in dashboard widgets Click for more about exploring ready-made reports in Report Builder Click for more about creating traceability reports on data from across projects by using Report Builder Click for more about generating document-style reports from Report Builder content

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki