This documentation supports the 9.1 version of Remedy Action Request System.

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

Example configurations

This section contains examples of a simple configuration and a complex configuration.

Simple example

In the simplest form, a server group can be setup with two AR System servers and a database server. Each of the AR System servers have all Remedy products installed.

In this example, the first server installed should be configured to be the primary administration server. Then, using the AR System Server Group Operation Ranking form, the applications should be distributed evenly across both servers, so that each server handles about half of the load, and each server has the other server configured for failover on each of its applications.

The exception to this is the Email Engine and the Flashboards server. In a simple configuration, those two items are installed on every system but can be configured for only one server. Configuring failover for those operations can be complex and may not be necessary in a simple configuration.

The full text search feature should be configured on each server. Each server has the ability to read from FTS, but only one server can be set to write, which is the server that is set with a higher priority on the AR System Server Group Operation Ranking form. It is also recommended that the FTS collection directory (location where the search index files are stored) and FTS configuration directory (location where the search configuration files are stored) be located on the same computer.

Simple server group example 
 

Complex example

A more complex server group implementation contains three or more AR System servers. In this example we are using four AR System servers. The applications or components should be installed on every server in the group so that failover can be provided.

Again, the first server installed should be configured to be the primary administration server. Then, using the AR System Server Group Operation Ranking form, the applications are distributed evenly across all four servers, so that each server handles about one quarter of the load, and each server has at least one other server configured for failover on each of its applications and components.

In this case, even the Email Engine server and the Flashboards have a failover server assigned. Configuring failover for those operations is somewhat complex because it means that each server has to be specifically configured to handle those items, but the secondary server for each is suspended until the failover is activated.

Complex server group example 
 

Note

The applications and components listed for the servers above are just the primary roles for each server. It is recommended that all applications and components be installed on each server. This is important because users could be accessing any components from any server in the group, and there are dependencies such as plug-ins and other binary files that could be called when a user opens certain forms, creates a new record, or modifies a record.

In this example, FTS is setup on all the servers so that failover is possible. The FTS feature should be installed on each server. It is also recommended that the FTS collection directory (location where the search index files are stored) and FTS configuration directory (location where the search configuration files are stored) be located on the same computer.

Related topics

Configuring server groups

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

Comments