Configuring the AR System server to rename the server
Best practice
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.)
Before you rename the server, make sure to do the database related changes in the ar.cfg (ar.conf) file.
Property name | Comment |
| Update with newDatabaseName |
| Update with newDatabaseUserName |
| Update with http://<newMidTierServerName>:<portNumber>/arsys |
| Update with newServerName |
| Update with newServerName |
| 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:
- 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.
- Create new BMC Remedy Action Request System Server service in the Registry.
- Open the registry backup of BMC Remedy Action Request System Server - <oldServerName> taken at step 1.
- Save this file as BMC Remedy Action Request System Server - <newServerName>.
- In the same file, find and replace the occurrences of <oldServerName> by <newServerName>.
- Save the file.
- Right-click on the BMC Remedy Action Request System Server - <newServerName> file and click Merge to update the Windows registry settings.
- Create a new BMC Remedy Email Engine service in the Registry.
- Open the registry backup of BMC Remedy Email Engine - <oldServerName 1> taken at step 1.
- Save this file as BMC Remedy Email Engine - <newServerName 1>.
- In the same file, find and replace the occurrences of <oldServerName 1> by <newServerName 1>.
- Save the file.
- Right-click on the BMC Remedy Email Engine - <newServerName 1> file and click Merge to update the Windows registry settings.
- Create a new BMC Remedy Flashboards Server service in the Registry.
- Open the registry backup of BMC Remedy Flashboards Server - <oldServerName> taken at step 1.
- Save this file as BMC Remedy Flashboards Server - <newServerName>.
- In the same file, find and replace the occurrences of <oldServerName> by <newServerName>.
- Save the file.
- Right click on the BMC 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 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.)
Comments
Log in or register to comment.