This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

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

Setting failover rankings for servers and operations

The AR System Server Group Operation Ranking form contains entries that define the failover ranking for servers that handle certain operations in the server group, and the delinquent threshold that helps determine when another server takes over an operation. This form is automatically created when you specify the first server as a member of the server group and restart the server.

When the form is created, it is populated with default entries and the first server added to the server group is assigned the primary ranking for all operations. The remaining server group members have null (empty ranking) entries, serving as placeholders. Entries for operations that require a license (for example, DSO) are not pre-populated unless a valid license is detected. You can add these operations at any time.

Note

Remove the default entries for operations that do not run in your environment.

AR System Server Group Operation Ranking form
(Click the image to expand it.)

Operation rankings

The fields named Operation, Server, and Rank work together to define which server is the primary server for the operation, which server takes over if the primary server fails, and so on.

Guidelines to set operation rankings for the server group

Use the following guidelines to determine how to set operation rankings for the server group:

  • The servers for any one operation are ranked lowest to highest. A value of 1 indicates the server chosen first to perform the operation. The next highest value indicates the server that takes over the operation if the first server fails, and so on.
  • Ranking numbers do not need to be consecutive.
  • If a value is null, the server ignores the entry.
  • If an operation has no server designated with a valid rank, it is not run on any of the servers in the group.
  • Avoid assigning two servers the same ranking for the same operation. (For ease of configuration, the form enables you to do this temporarily.)
  • Operations can be spread freely across different servers, with the exception of operations involving BMC Remedy Approval Server, BMC Atrium CMDB, and the BMC Service Level Management engine (labeled Business Rules Engine in the form). These operations must reside on the same server as the administration operation; therefore, the operations must have the same ranking as the administration operation so that they move as a unit.
  • If you are implementing full text search (FTS), an additional restriction for multi-platform server groups exists. The Administration and Full Text Indexing operations must be restricted to server group nodes that can have a compatible directory structure for the Search Server configuration files.

To establish operation rankings in the server group

  1. In a browser, log on as a user with Administrator privileges to any server in the group.
  2. Open the AR System Server Group Operation Ranking form in search mode.
    http://<midTierServer>:<portNumber>/arsys/forms/
    <ARSystemServer>/AR+System+Server+Group+Operation+Ranking/
  3. Perform an unqualified search to see the entries in the form.
  4. Modify entries as required to construct a fail-over hierarchy for ownership of operations.
  5. Save the AR System Server Group Operation Ranking form.
  6. Restart all the AR System servers in the group.

Delinquent threshold

The Delinquent Threshold field determines the number of times the specified server can miss reporting its status before the next server in the ranking takes responsibility for the operation. This setting works together with the Check Interval to determine the total time to failover for any operation.

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

Comments