Administering global configuration project areas
A project area is an area in the repository where information about one or more projects
is stored. Administrators can create, configure, and manage global configuration project
areas.
Project areas for Global Configuration Management (GCM)
The configuration lead is responsible for managing configuration hierarchies and must be a member of the GCM project area with the Configuration Lead role. This role has permissions to create, modify, and manage the global components and configurations.
Team areas in the GCM application
Use team areas for greater control over write access to components and configurations in a project area. By creating different team areas, you can grant specific privileges to specific users for specific artifact types. For example, you can use team areas to allow or prevent team members from editing particular configurations.
Finding different configurations of the same component in Engineering Workflow Management SCM and RMM contributions (Detecting deep component skew)
In a global configuration, contributions from IBM® Engineering Workflow Management source control management (SCM) and IBM Engineering Systems Design Rhapsody® - Model Manager , often contain nested local configurations. When a configuration hierarchy contains different configurations of the same component, skew occurs. To detect skew in nested local configurations, install the Eclipse Amlen MQTT broker and set values for the MQTT advanced server properties.
Limiting GCM contributions by enforcing project area associations
To limit which project areas team members see when they add local or global configurations to global streams or set their configuration context in applications such as the Requirements Management (RM) or Quality Management (QM) applications, you can configure the Global Configuration Management (GCM) application to enforce project area associations.
Enabling GCM servers to contribute configurations to other GCM servers
Some teams with isolated IBM Engineering Lifecycle Management deployments need to collaborate on product assemblies across multiple lines of business. As an experiment in implementing this use case, you can configure a Global Configuration Management (GCM) server to accept contributions from different GCM servers. The contribution of a global configuration from one GCM server to a global configuration on a different GCM server is called an external contribution .
Assigning URIs and creating RDF vocabulary documents
When you create type definitions in your project area, assign a unique URI to each of those definitions before you share them with other Global Configuration Management (GCM) project areas. Otherwise, you might end up with inconsistencies such as unintended type definition duplication.
Managing type definitions
Type definitions are artifact types, attributes, data types, and link types that you can customize for a Global Configuration Management (GCM) project area. Users can select attributes and links that are defined at the project area level when they create or edit a global configuration or global component.
Sharing GCM type definitions across project areas
You can share type definitions for global components and configurations to maintain consistency across Global Configuration Management (GCM) project areas.
Adding release links in global configurations
Associate global configurations with releases to ensure that versioned artifacts show incoming work item links. Releases are defined and managed in the IBM Engineering Workflow Management application, but can be added within global configurations in the Global Configuration Management (GCM) application. A global configuration's release links are used for viewing incoming links in IBM Engineering Requirements Management DOORS® Next (DOORS Next ) and IBM Engineering Test Management from work items to versioned artifacts, such as requirements and test cases.
Administering personal streams in the GCM application
A personal stream can be modified only by its owner or a Global Configuration Management (GCM) administrator. As an administrator, you can view, scrub, modify, and archive or restore team members' personal streams.
Role-based permissions for Global Configuration Management (GCM)
Global Configuration Management (GCM) project areas and team areas have specific role-based permissions that determine which actions you can perform in the application.
Creating global configuration process templates
You can create a process template from an existing process template and then customize the process name, process ID, and summary.
Adding data providers to Lifecycle Query Engine by using root services documents
If the lifecycle management application has a root services document that declares its OAuth URLs, you can register the TRS feed for that data provider by using the root services URL. This is an easy method for adding an LQE data provider if the application is registered with a different Jazz® Team Server than LQE .
Managing global configuration process templates
You can create, edit, delete, export, and import process templates from the project administration Templates page. You can use the export and import capabilities to copy a process template to another Jazz repository.