Enabling configuration management in project areas (AM application)
This topic applies to the Architecture Management application. To work with multiple versions of architecture elements, link to artifacts in other applications, and work in a global configuration context, an application administrator must enable configuration management capabilities for that project area. After you enable this capability for a project area, you cannot disable it.
Before you begin
- You must be a project area administrator.
- You should understand configuration management concepts. See Getting started with configuration management.
- Back up existing repositories before you enable configuration management capabilities. If you restore from a backup, you will lose any changes that were made in all project areas managed by that server.
- You should understand the effects of enabling configuration management.
- If you integrate with other tools that are not part of IBM
Engineering Lifecycle Management (ELM), such
as through linking or synchronizing data, you must understand how they link to your ELM
In other tools, versions of artifacts might not exist in multiple streams or baselines, so enabling configuration management might cause unexpected behavior.
About this task
After you enable a project area for configuration management, you cannot disable it. There is no way to reverse the action after you enable a project area. Back up existing repositories before you enable configuration management capabilities. If you restore from a backup, you will lose any changes that were made in all project areas managed by that server.
To support OSLC links between artifacts in ELM applications, all related project areas must be enabled for configuration management as explained on the Configuration Management page in the AM application. To go to this page, see the Procedure.
If you do not enable configuration management for a project area, you can still create development streams and baselines to work with variants in a project area in a lifecycle application, but you cannot include them in global configurations.
For information about reporting and configurations, see Reporting on data in configurations.
|From a project area administration page||
|From a project area||
What to do next
After you enable configuration management, use the options on the Source Control menu to manage your configurations and workspaces.
The configurations in this project area can be grouped with configurations from this project area and other ELM applications to give you a view of all the artifacts (such as requirements, source code, and test artifacts) that are associated with a product version. These groupings of configurations are called global configurations.
You must enable linking of architecture elements to versioned artifacts in other ELM project areas.