This documentation supports the 21.05 version of Action Request 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 Defining default permissions.

The configuration data for the following components is centralized:

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

You can continue to change the configuration settings for the following components by using the listed form or tool:

You can use the AR System Administration: Plugin Server Information form form to change the configuration settings for Java plug-in server, ARDBC LDAP plugin-in, and AREA LDAP plug-in.

You can use the AR System Configuration Generic UI form form for Email Engine  configuration settings and any other configuration settings that are not available in the preceding forms.

The following topics provide detailed information about centralized configuration:

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

Comments