Configuration management in the RM application
This high-level overview briefly describes the configuration management capabilities in the RM application. For comprehensive and task-related information, see Getting started with configuration management.
- For pilot environments, read the considerations and generate an activation
key.Note: Configuration management capabilities of RM and QM, and global configuration management is an added service 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. 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.
Use the configuration management capabilities in the RM application to set up unique working environments for individuals or teams. For example, you can create components to represent collections of artifacts, instead of working with all the artifacts from the project in one stream. You can create streams and baselines of projects at specific points in time, review and approve changes to artifacts, and make changes visible to other teams or individuals. You can also enable link validity in a configuration management enabled project.
Streams, baselines, and change sets in configuration management
A stream is a configuration in which you create and modify artifacts at a specific development level. For example, you might create a stream when you start a new release or branch of a design, project, or product.
A baseline is an immutable configuration that provides a snapshot of your project at a specific point in time. Baselines are useful for capturing the state of a stream, and are typically used to record important stream configurations so that they can be re-created. When you create a new stream, a baseline of the previous stream is created automatically.
A change set is a grouping of changes that remains separate from the stream in which it was created until you deliver the change set to the stream. After you deliver your change set to the originating stream, you can then deliver the change set to other streams. Using change sets is an optional but convenient way to track and deliver changes in your development environment.
When you first create a project, an initial component and stream are automatically created that manage the artifact versioning information for the project. You can create more components to organize artifacts based on your project needs. To manage components and configurations, from the Administration menu, select Manage Components and Configurations.
- To see the baselines that were created in a stream, click the stream and then click the Baselines tab. To compare the contents of two streams, select the streams and click Compare .
- If your team uses global configurations, you can create a baseline of an RM stream from the configuration tree view in the Global Configuration Management (GCM) application. See Creating baselines of streams contributed by other ELM applications.
If you are working in a parallel development environment, you might have individual streams whose contents are derived from a common stream. To make changes in your stream visible to other team members, you deliver your changes to the common stream, which also known as the flow target. From the common stream, team members can accept changes into their own streams to ensure that they have the most recent versions of artifacts.
For more information about configuration management, see the following related topics.