This documentation supports the 20.02 version of Remedy Action Request (AR) System.

To view an earlier version, select the version from the Product version menu.

Managing AR Server Group components by setting global-level and local-level configurations

You can manage AR Server Group components more effectively and reliably by defining global-level and local-level configuration settings under Centralized Configuration. Earlier, you needed to define common settings for all servers individually, now you can set a global-level configuration value for all the common settings across the server group. Global-level configurations are defined for all servers in a server group. Local-level configurations are defined for an individual server. 

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 valueGlobal-level configurationLocal-level configurationEffective value
30002000Not set2000
3000Not setNot set3000 
3000Not set40004000

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.integrations.shared
  • As a best practice, BMC defines a scope for each configuration setting. Each setting is classified as either 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 Setting global-level and local-level configurations using 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

There are certain components such as Private-PRC-Socket that share the configuration key but has 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 Setting global-level and local-level configurations using the Remedy Management Console.


  • The AR System server sets a value in the Setting Reference Key field for all the configurations handled by BMC Remedy AR System. If you add a custom configuration of this type, you need to set the value for the Setting Reference key field.
  • The AR System server does not set value for com.bmc.arsys.pluginServer component type in the Setting Reference key field.

Setting global-level and local-level configurations

You can set global-level and local-level configurations by using either of the following methods.

Best practice

When setting the global-level and local-level configurations, we recommend that you use the Server Group Configuration screen of the Remedy Management Console to set the global-level and local-level configurations.

Related topic

Centralized configuration

Was this page helpful? Yes No Submitting... Thank you