Enabling configuration management in project areas (AM application)

Edit online

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 the configuration management capability for a project area, you cannot disable it.

Before you begin

  • You must be a project area administrator.
  • You must understand configuration management concepts. For more information, see Getting started with configuration management.
  • Back up existing repositories before you enable configuration management capabilities. If you restore from a backup, you lose any changes that were made in all project areas that are managed by that server.
  • You must 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 those tools link to your ELM applications.

    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. You cannot 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 lose any changes that were made in all project areas that are 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 Architecture Management > Configuration Management UI page in the RMM application. To go to the UI page, read the following 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.

To know about reporting and configurations, see Reporting on data in configurations.

Procedure

You can enable configuration management from a project area administration page or in a project area.
Option Description
From a project area administration page
  1. Go to the application administration page: https://fully_qualified_host_name:9443/application_context_root/admin
  2. On the toolbar, click Project Areas > Active Project Areas.
  3. Click the name of the project that requires configuration management capabilities.
  4. Go to Architecture Management > Settings, and click Enable Architecture Management.
  5. A confirmation message pops up, click OK. Save your changes.
  6. Go to Architecture Management > Configuration Management, and select the Enable full configuration management (for use with global configurations) radio button.
  7. Read the information on the page, and then click Enable Full Configuration Management button. Follow the prompt, and click OK.
From a project area
  1. Click Administration Administration menu > Manage This Project Area.
  2. Go to Architecture Management > Settings, and click Enable Architecture Management.
  3. A confirmation message pops up, click OK. Save your changes.
  4. Go to Architecture Management > Configuration Management, and select the Enable full configuration management (for use with global configurations) radio button.
  5. Read the information on the page, and then click Enable Full Configuration Management button. Follow the prompt, and click OK.

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 the current project area can be grouped with configurations from the current 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.