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.

Configuring the next server for the server group

Before you begin

Open the text file of the servers in the server group that you previously created. It should list the entire set of IP-Name entries. Each server must have the same set of entries containing all resolvable names for each server.

To configure the next server for the server group

  1. Confirm that the server is a server group member.
    1. In a browser, open the Home page of the first server.
    2. Choose Administration Console > System > General > System Information.
    3. Click the Configuration tab.
    4. Verify that the Server Group Member check box is selected.  If it is not, select it.
    5. Click Apply.
  2. Edit the ar.cfg file on the second (third, fourth, and so on) server computers.
    1. On a Microsoft Windows server, open the <ARSystemInstallDir>\ARSystem\Conf\ar.cfg file in a text editor.
    2. Confirm that the Server-Group-Member setting is set to T (Server-Group-Member: T).
      If the setting is set to F, change it to T. If you do not see this setting, create it and set it to T.
    3. Check for an entry called Server-Name.
      If it exists, verify that is set to a name that resolves to your load balancer. If it does not, modify the setting's value so that it does. If the entry does not exist, create it, and set it accordingly. For the installation test example, the name is RemedyServerGroup.
      If you are not using a load balancer, you must specify the primary server's server name for all the server's in the server group.
    4. Check for an entry called Server-Connect-Name.
      If it exists, verify that it is set to the unique name of the second server (or third, or forth, and so on). If it is not, modify the setting's value so that it is. If the entry does not exist, create it, and set accordingly. For the installation test example, the name of the second AR System server is svr_grp_tst3.
    5. Check for an entry called Domain-Name.
      If it exists, verify that it is set to the lowest subdomain name used in your implementation.  If it is not, modify the setting's value so that it is. If the entry does not exist, create it, and set it accordingly. For the example, the lowest subdomain name is test.svgroup.com.
    6. Open the text file that you created with the IP-Name entries for all servers in the server group, when you were configuring the first server.
    7. Copy and paste the text with the IP-Name entries for all servers into ar.cfg.
    8. Save the ar.cfg file and restart the server.

Related topics

Opening the text file of the servers in the server group

Where to go from here

Testing and confirming that the current server is working properly

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.

Comments

  1. Lj Longwing

    I would like to know where documentation exists regarding 2c.  According to every version of documentation that I have been able to find, this setting is directly related to multiple ar servers running on a single host, and have NOTHING to do with server groups (other than the fact that you can't have two servers on a single host in a server group).  So, I would like to know why it's recommended above that this setting be set to true, because I don't feel that it should be, nor have I found it required in any way, unless of course that you are running multiple remedy servers on one host...which this article isn't discussing.

    Mar 01, 2013 08:42
    1. John Stamps

      Hi LJ,
      We've actually been doing our own Server Group installs recently, so we're doing lots of hands-on work on this topic. We'll research this particular step further and get back to you. It worked but I don't know why it worked.
      Sincerely,
      John

      Mar 01, 2013 01:02