Archive for October, 2009

Things to Consider when changing Name of the AR Server

October 22nd, 2009

bmcWhat to Consider if the Name of the AR Server Changes

  • Windows Registry
  • Host File
  • AR Server Config File
  • AR Server Workflow
  • Licensing
  • AR System Email Engine
  • Remedy ODBC Configuration
  • Mid-Tier Configuration
  • Remedy Wireless
  • Remedy ITSM Applications
  • Flash boards
  • DSO – Distributed Server Option

The explanation for the above areas are:

Windows Registry

A Microsoft Windows operating system has a registry that is accessible by going to Start->Run->regedt32 (optionally regedit). Remedy will have references to the name of the server in the registry, however since the entire server name will be changing, we recommend scrolling to the top of the list on the left in the registry editor and selecting My Computer. Go under the Edit menu and select Find. Type in the old name of the server and everywhere you find it, change it to the new name. Normally this is done by double-clicking the key on the right with the server name reference and changing the value.

Warning: This will impact more than just Remedy software. The registry contains information for most applications including the OS. Editing the registry can have adverse affects. If you do not have experience editing the registry, contract Microsoft for more information.

Note: Many registry changes require a reboot afterwards.

Host file

The host file is a way of resolving IP addresses to server names. It is normally not used for AR Client machines on a network because of the administrative overhead. It is important to note that AR Server client communication looks to the host file first before going out to DNS or WINS to resolve a server name. If you change the name of AR Server, make sure you dont also have to change the value in the host file. The host file is normally located in the WINNT directory in System32\drivers\etc. The file has no extension and is just called “hosts”.

AR Server Configuration File

Reference to the name of the server is stored in the ar.cfg file with the parameter called Server-Name: <value>. This file is located in the AR Server install directory in a subfolder called Conf.

Look for other references to server names that might exist depending on how AR Server is configured, such as Server-Connect-Name, which is used in 6.0x server group environments, IP-Name parameter, DSO Host Name references, etc.

Note: When you login to the Admin Tool and bring up the Server Information dialog window, the Server Name Alias field on the Platform tab displays the value for the Server-Name parameter in the ar.cfg file. Changing the value in this field also changes the Server-Name parameter in the ar.cfg file.

AR Server Workflow

Server name references can be hard-coded in various database tables. The tables are part of the AR System Data Dictionary and they are populated as forms and workflow are created. Examples of some common actions that can have server name references are set fields, push fields, table fields, and menus. There is a KB that covers exporting definitions with the Admin Tool and running a utility on them called ARClean. This utility is available online at the Remedy Supportweb. The KB ID is 12219.


There is a license file located in C:\Program Files\Common Files\Remedy (or possibly AR System) called multilicense. This file should be deleted and the Remedy ARS service restarted or else AR Server will not recognize that the server is licensed. Note: The path to the remedy.lic file (may also be the arsystem.lic file) may reference a server name. Optionally you can change the name of the folder to the correct server name although its not required. If you do this, you must also change the path to the remedy.lic file in the armonitor.cfg file.

AR System Email Engine

When the Email Engine is installed, it prompts you for the name of the AR Server and it puts this value in the file located in the Email Engine install directory (normally called AREmail). This file can be opened with a Text Editor and the server name reference can manually be changed. Here is an example of a line containing the server name of ‘production’: com.remedy.arsys.emaildaemon.production.TCP=0   This line can be updated and the server name of ‘production’ changed to another name.

Remedy ODBC configuration

In Start->Programs->Administrative Tools->Data Sources (ODBC), select

the AR System ODBC drive and click the Configure button and change the

name of AR Server.


The AR System Web Configuration Tool will have a reference to the AR Server

it is connecting to. Note: Changing the name of AR Server requires a redeployment of applications and a restart of the web server service. Also with the AR System Web Configuration Tool, you can specify a Preference Server and Home Page Server.

Remedy Wireless

This product sits on top of the Mid-Tier and has a configuration tool very similar to the Mid-Tier Configuration Tool. Here there is also a similar reference to the AR Server that would need to be changed.

ITSM Applications

With the ITSM applications, it is possible to have certain fields that could reference the actual server name. For example, the SHR:ApplicationSettings form. In version 5.5 specifically, there is a reference to the server name.

The Report form has a field called Server. This is where you fill out the name of the AR Server. Various canned ITSM reports will reference this parameter. Note: It may be possible to reference this field with $SERVER$.

When the ITSM applications are installed, it does create an installation folder in Program Files called AR System Applications. The very next folder is the name of the server. This path is not referenced by default so changing the name of the AR Server will not impact this folder name. To avoid confusion, the name of the folder may be renamed.

If you have the ITSM applications, it would be a good idea to check with the Applications team depending on the version of the applications you have to see if there is a hard coded server name reference.


Inside the Flashboards install directory, the server.conf file will have reference to the name of the AR Server.

Distributed Server Option (DSO)

It is possible to have DSO configured between multiple AR Servers. Assuming a server name change to one of the AR Servers in a DSO group, the Distributed Mappings on the other AR Servers would need to be updated with the new server name. Sometimes, the DSO-Host-Name parameter has been added to the ar.cfg file and would need to be updated with the correct new server name. Also, if youre running multiple AR Servers in a load balanced configuration, its possible you could have a DSO-Source-Server parameter that may need to be updated.

Note: Changing the name of a server will have an impact beyond Remedy products, most notably the database software and/or database client software.

Source: Originally posted on BMCDN.

What’s new in BMC Atrium Core 7.5.0 and Remedy 7.5.0

October 21st, 2009
BMC Remedy ARSystem

BMC Remedy ARSystem

What’s new in BMC Atrium Core 7.5.0 and Remedy 7.5.0

A 36 page presentation which includes:

  • Whats New in Action Request System 7.5.00
  • Whats New in Atrium Core 7.5.00
  • Compatibility
  • Unified Installer
  • IDE – Integrated Development Environment
  • Enhanced UI
  • Flex based flashboards
  • Enhanced Approved Console
  • Improved overall performance
  • Enhanced Atrium Core 7.5
  • Atrium Integrated Engine
  • Product Catalog
  • Service Catalog
  • Atrium Impact Simulator

Originally posted on BMCDN by vwiles



%d bloggers like this: