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 AR System server to rename the server

To configure the AR System server, you must update configuration files. On Windows, you must also update the Registry. On UNIX, you must also update the arsystem script.

Updating the configuration files

ar.cfg (ar.conf) 

In the ar.cfg (ar.conf) file, update the following properties. (You might not need to update all directory and file path properties, but update any properties that point to AR System servers and the mid tier.)

Property name

Comment

Db-name

Update with newDatabaseName

Db-user

Update with newDatabaseUserName

Default-Web-Path

Update with http://<newMidTierServerName>:<portNumber>/arsys

Server-Name

Update with newServerName

Server-Connect-Name

Update with newServerName

Server-Plugin-Alias

Update every occurrence of this parameter with newServerName

armonitor.cfg 

In the armonitor.cfg file, replace the old AR System server name with the new AR System server name in the following string: -x <newServerName>
You will see several lines that contain this string. Edit each occurrence.

pluginsvr_config.xml 

In the pluginsvr_config.xml file, the server_name user-defined tag contains the server name for the following plug-ins. Adjust the server_name value with newServerName.

Typically, when you install the BMC Remedy ITSM Suite, several Java plug-in servers are installed. Be sure to replace the server_name value for each plug-in server. To find the location of these plug-in servers, look at the -classpath parameter for each Java command in the armonitor.cfg file.

server.conf

Find and replace the occurrences of <oldServerName> by <newServerName>.

Making service registration changes on Windows 

The following is the process for deregistering and registering services:

  1. Before changing the services, export the following Registry entries from HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services.
    • BMC Remedy Action Request System Server - <oldServerName>
    • BMC Remedy Email Engine - <oldServerName 1>
    • BMC Remedy Flashboards Server - <oldServerName>

      Stop the services of BMC Remedy Action Request System, Email Engine, and Flash boards before proceeding with the next steps.

  2. Create new BMC Remedy Action Request System Server service in the Registry. 
    1. Open the registry backup of BMC Remedy Action Request System Server - <oldServerName> taken at step 1.
    2. Save this file as BMC Remedy Action Request System Server - <newServerName>.
    3. In the same file, find and replace the occurrences of <oldServerName> by <newServerName>. 
    4. Save the file.
    5. Right-click on the BMC Remedy Action Request System Server - <newServerName> file and click Merge to update the Windows registry settings.
  3. Create a new BMC Remedy Email Engine service in the Registry.
    1. Open the registry backup of BMC Remedy Email Engine - <oldServerName 1> taken at step 1.
    2. Save this file as BMC Remedy Email Engine - <newServerName 1>.
    3. In the same file, find and replace the occurrences of <oldServerName 1> by <newServerName 1>. 
    4. Save the file.
    5. Right-click on the BMC Remedy Email Engine - <newServerName 1> file and click Merge to update the Windows registry settings.
  4. Create a new BMC Remedy Flashboards Server service in the Registry.
    1. Open the registry backup of BMC Remedy Flashboards Server - <oldServerName> taken at step 1.
    2. Save this file as BMC Remedy Flashboards Server - <newServerName>.
    3. In the same file, find and replace the occurrences of <oldServerName> by <newServerName>. 
    4. Save the file.
    5. Right click on the BMC Remedy Flashboards Server - <newServerName> file and click Merge to update the Windows registry settings.

Updating UNIX environments 

  1. Create a matching /etc/arsystem/serverName directory that contains the armonitor.conf file for your server.
    In UNIX and Linux environments, the AR_SERVER_ID (set in the arsystem script) is used to find the subdirectory of /etc/arsystem/ that stores the armonitor.conf file.
  2. Edit the arsystemscript to set the following parameters correctly for the new server:
    • INSTALL_DIR
    • AR_SERVER_ID
    • CONFDIR (This is where the ar.conf file is located.)
    • TWO_TASK

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. Hans-joachim Ballin

    By changing server informations a lot, we also shouldn't forget the port number parameter called "TCD-Specific-Port". 

    Aug 18, 2013 08:40
    1. Hemant Baliwala

      Hi Hans-joachim, 

      Thanks for your comment.

      TCD-Specific-Port is required only if you have set Register with Port Mapper=False. See Understanding port numbers

      Thanks, 

      Hemant

      Aug 19, 2013 02:07
  2. John Marshall

    The flashboard update for server.conf links to this page, but there does not appear to be a section on updating that file (although it seems pretty straightforward, replace <old server> with <new server>

    Oct 25, 2013 10:02
    1. Hemant Baliwala

      Thanks for your comment, John. 

      I have updated the topic.

      -Hemant

      Nov 01, 2013 01:02
  3. Scott Skeate

    In the table above, you have the following:

    Server-Name   Update with newServerName

    Server-Connect-Name   Update with newServerName

    Server-Plugin-Alias   Update with newServerName

     

    This is confusing because newServerName is not the same for each instance.  The "newServerName" for Server-Connect-Name and Server-Plugin-Alias entries should be the newLocalServerName and for Server-Name should be newLocalServerName (for standalone server) or newServerGroupName when adding to a Server Group.

    I think other references throughout this section on duplicated/migrated servers should be updated to indicate whether the newServerName should be the local name or server group name.

    Sep 23, 2014 05:45