Global Configuration or no...
Mahari Hill (486●1●138●229)
| asked Sep 25 '17, 8:32 a.m.
retagged Jan 03 '18, 1:34 a.m. by Minakshi Jaint (511●3) Hello,
|
Accepted answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 25 '17, 11:04 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Sep 25 '17, 12:02 p.m. To avoid confusion, it probably is important to be a bit more precise. The Global Configuration Management application (/gcm) is not something that you activate. If it is installed, it is active, and you can create global components, global streams, and global baselines. But those global configurations are not very useful until you have configurations that actually contain versions of artifacts, and you contribute those configurations to a global configuration.
What you "activate" is (1) configuration management on a given DNG or RQM server, and (2) configuration management of a given DNG or RQM project area (you cannot activate configuration management of a project area until after you have activated configuration management on the server for that project area). The DNG and RQM configurations are the configurations that actually contain versions of artifacts, and that can contribute to a global configuration.
As Shrada says, there actually is an initial stream created in a DNG project area before you turn on configuration management for that project area, and you are allowed to create baselines on that stream (so you can compare current and previous states). The reason there is a configuration context for a DNG project area even before you have activated configuration management for that project area is to allow you to set your current configuration to be an arbitrary baseline, so you can browse through the content of that baseline.
Mahari Hill selected this answer as the correct answer
|
One other answer
Hi Mahari,
Comments Also, just by installing GC it won't be activated. You need to go to each and every PA to enable it explicitly.
|