Grouping Centralized Configuration File Parameters

When you want to assign parameter values differently for sets of users, sets of machines on your network, or according to machines with specific operating systems, you could create a unique corporate WDIR directory for each scenario and modify the local WDIR environment variable accordingly. But an easier way to maintain these groups of parameters is to use the special grouping statements that RSCM understands.

Grouping statements define sets of conditions which must be met to apply the associated configuration entries. Condition statements are set of with curly brackets {condition1, condition2, condition3, ... , conditionN}.

Example of a grouping statement:

{all} 
[Logging] 
Level = 1 
 
{unix} 
[System] 
TimeStampCheck* = no

In the first grouping statement, all logging levels are set to 1, regardless of the user, machine, or operating system. In the second grouping statement, the TimeStampCheck parameter is set to “no” for all UNIX machines. Notice this parameter is locked so this parameter cannot be changed at a local WDIR level. See Locking Centralized Configuration File Parameters for more information about locking parameters.

Guidelines to help you understand and use grouping statements:

All configuration parameters that follow a grouping statement (until another grouping statement appears) belong to that group.
Grouping statements do not allow nesting groups: RSCM evaluates statements in order of appearance in the configuration file.
Combine conditions in a grouping statement (separating them with a comma) to “and” them together.
All conditions in the grouping statement must be met to satisfy a grouping statement and apply the configuration parameters to that group.
Configuration parameters that appear before the first grouping statement, apply to all groups.
The same configuration parameter can appear in multiple groups. If an end user’s machine belongs to multiple groups, and more than one of those groups contain the same configuration parameter, RSCM uses the value that last appeared in the configuration file.
You can view the effective Server configuration (Server.cfg) parameter values for any project’s iCDB Server in Server Manager. View a project in Server Manager and expand the Settings tree for that project in the left-hand window. The contents of the Server configuration file appear in the Properties window (View > Properties).
Configuration groups cannot contain configuration parameters without the section name. The section name is the heading of a section of parameters that is surrounded by square brackets, such as [Logging].

Grouping Statement Conditions

The following list shows the conditions you can use to create grouping statements:

Table 1. Grouping Statement Conditions
Condition	Description	Example
windows	True on all Windows platforms	{windows} [Logging] Level = 3;
solaris	True on all Solaris platforms	{solaris} [Logging] Level = 1
client	True for client applications (such as PADS Designer, CES, and PADS Layout).	{client} [Logging] Level = 5
server	True on server processes (such as iCDB Server, and RSCM Server).	{server} [Logging] Level = 1
machines:	True on any machine in the list (separate multiple machines with spaces).	{machines: win-abc-def-10 win-abc-def-11} [System] AutoBackupSupport = no
users:	True for any user whose name is on the list (separate multiple machines with spaces).	{users: jsmith fdoe gbrady} [Permissions] KillServer* = no
all	Special Condition: suppresses all other conditions. Forces the condition to always be met.	{all} [Logging] Level = 1
continue	Special Condition: Causes the next grouping statement to be evaluated after applying the current configuration group. This is the default configuration behavior.	{continue, machines: win-abc-def-10} [System] TimeStampCheck* = no {users: jsmith fdoe} [Permissions] DefragmentDatabase* = no
stop	Special Condition: If this grouping statement’s conditions are met, no more grouping statements are considered. Any following grouping statements are ignored. (In the example, if the user is jsmith, then use the first mapping and stop. All other users get the global mapping.)	{unix, users: jsmith, stop} /home/pcb1 \\server\homes\pcb1 {unix} /mnt/global/share \\global\share