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.

Centralized configuration

Configuration data is stored in the centralized configuration forms and is also displayed in the ar.cfg configuration file (for backward compatibility). Centralized configuration not only simplifies the management of configuration data, but also simplifies the sharing of configuration settings across servers. Also, because configuration data is stored directly in the database, the data is more secure.

BMC offers Role-to-Group mapping of components in Centralize Configuration. An administrator can choose to modify this mapping by using the AR System Configuration Permission Model Registry form. For more information, see Modifying the permissions of components by using Centralized Configuration.

The following topics provide detailed information about centralized configuration:

The configuration data for the following components is centralized:

  • BMC Remedy AR System server
  • BMC Remedy Mid Tier
  • BMC Remedy Approval server
  • BMC Remedy Email Engine
  • BMC Remedy Java plug-in server
  • BMC Remedy Shared (Shared parameters for all components)
  • BMC Remedy Distributed Server Option
  • BMC Remedy Flashboards server
  • BMC Remedy Assignment Engine
  • AR System Database Connectivity (ARDBC) LDAP plug-in
  • AR External Authentication (AREA) LDAP plug-in


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