Managing server group components by setting global-level and local-level configurations
Any configuration in the centralized configuration that is specified under the Component Name field with an asterisk (*) is a global-level configuration and applies to all servers in the server group. Also, the component name pluginServer_default under the Component type: com.bmc.arsys.pluginServer is renamed to an asterisk (*).
Order of precedence for honoring the global-level and local-level configurations
- The local-level configurations value takes precedence over the global-level configurations.
- A global-level configuration is effective if you do not define a local-level configuration.
- If you do not set global-level or local-level configurations, the system uses the default value of the configuration.
Refer to the following example, showing how the AR System server determines the effective value of a setting:
Default value | Global-level configuration | Local-level configuration | Effective value |
|---|---|---|---|
3000 | 2000 | 5000 | 5000 |
3000 | 2000 | Not set | 2000 |
3000 | Not set | Not set | 3000 |
3000 | Not set | 4000 | 4000 |
Considerations for setting global-level and local-level configurations
- The following components have global-level configuration value. You cannot set local-level configuration for the following components:
- com.bmc.arsys.server.shared
- com.bmc.cmdb.services.shared
- com.bmc.cmdb.integrations.shared
- As a best practice, BMC defines a scope for each configuration setting. Each setting is classified as GLOBAL_ONLY, LOCAL_ONLY, or GLOBAL/LOCAL configuration.
You can check the scope of any setting at the following:
Remedy Management Console > AR System Server Group Console > Server Group Configuration screen > Global Settings > Scope - The Scope column on the Server Group Configuration screen shows the scope of a setting. If the Scope column has no value, you can define a global-level or local-level value for that specific setting.
- The scope of each setting is an out-of-the-box guideline provided by BMC. If a configuration has LOCAL_ONLY scope, you cannot set global-level configuration value for that specific setting by using the Server Group Configuration screen on the Remedy Management Console.
- You can use the AR System Configuration Generic UI if you want to define a global-level value for a setting that has LOCAL_ONLY scope or a local local-level value for a setting that has GLOBAL_ONLY scope. For more information, see Updating-configuration-settings-by-using-the-AR-System-Configuration-Generic-UI-form.
- You cannot fetch global-level configurations if you programmatically access the Centralized Configuration form.
Handling configurations that share the configuration key
Some components such as Private-PRC-Socket share the configuration key but have multiple configuration values.
- The AR System server handles these configurations by using the Setting Reference Key field on the Server Group Configuration screen.
- The combination of the Setting Name and the Setting Reference Key uniquely identifies the component.
The Setting Reference Key field enables you to identify a configuration that shares the configuration key and also enables you to set a Setting Value for a particular configuration. This helps if you have a global-level value set for a specific configuration, and you want to set a local-level value for a specific server. For more information, see Updating-configuration-settings-by-using-the-AR-System-Configuration-Generic-UI-form.
Setting global-level and local-level configurations
You can set global-level and local-level configurations as described in Updating-configuration-settings-by-using-the-AR-System-Configuration-Generic-UI-form.