Renaming an AR System server by using configuration files

Best practice
We recommend that you use the Renaming-the-AR-System-server-by-using-the-rename-utility utility to change the server name of .

To configure the , 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 s and the .)

Before you rename the server, make sure to do the database related changes in the ar.cfg (ar.conf) file.

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 name with the new 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 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:

Before changing the services, export the following Registry entries from HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services:
- - oldServerName
- - oldServerName 1
- Server - oldServerName
  Stop the services of , , and before proceeding with the next steps.
Create new service in the Registry.
1. Open the registry backup of - oldServerName taken at step 1.
2. Save this file as 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 Remedy Action Request System Server - newServerName file and click Merge to update the Windows registry settings.
Create a new service in the Registry.
1. Open the registry backup of - oldServerName 1 taken at step 1.
2. Save this file as 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 Remedy Email Engine - newServerName 1 file and click Merge to update the Windows registry settings.
Create a new Server service in the Registry.
1. Open the registry backup of Server - oldServerName taken at step 1.
2. Save this file as 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 Remedy Flashboards Server - newServerName file and click Merge to update the Windows registry settings.

Updating UNIX environments

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.
Edit the arsystem script 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.)