This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

Sharing a database without using a server group

The recommended way to share a database is to create a server group.  Alternatively, you can configure two or more AR System servers to share the same database without making them members of a server group. In this case, automatic failover protection is unavailable, and when you change object definitions, you must manually refresh the cache on other servers in the group (for example, by restarting them).

This approach can be sufficient for managing performance. For example, you can use a shared database in an environment where the user traffic all goes to one AR System server. In this scenario, you can use another server on the same database to handle tasks such as reporting or reconciliation, which can have a performance impact on the AR System server.

When you share a database without using a server group, you must designate one server as the administrative server by disabling administrative functions on the other servers sharing the database. Also note that specific services can only be running on one system at a time, and in some cases, additional configuration is required to manage them (that is, escalations need to be disabled on all but one server and the assignment engine should only run on one server).

To share a database between AR System servers without using a server group, perform the following installation and configuration steps:

During installation

  • Select the Overwrite or Upgrade option for the first server installed.
  • Select the Server Group option when installing subsequent servers that share the same database.
  • Specify the same database information for all servers that share the database.


    Choosing Server Group during AR System installation does not configure the servers as members of a server group. It merely indicates to the installer that the server shares the database with an existing AR System server, with or without server group membership.

After installation

  • Determine which server is the administrative server, where you manage and modify forms, workflow, and applications with BMC Remedy Developer Studio.
  • Isolate BMC Remedy Developer Studio access, escalations, and archiving to the administrative server.

To turn off Developer Studio access, escalations, and archiving on the non-administrative servers (without server groups)

  1. In a browser, log on to each of the non-administrative servers as a user who is a member of the Administrator group.
  2. Click AR System Administration Console > System > General > Server Information.
  3. Click the Configuration tab, and select the following check boxes:
    • Disable Admin Operations
    • Disable Escalations
    • Disable Archiving

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.