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 BMC Remedy Mid Tier to rename the server

This topic describes how to update the BMC Remedy Mid Tier components.

Updating the configuration with the BMC Remedy Mid Tier Configuration Tool

  1. Use the following URL to open the BMC Remedy Mid Tier Configuration Tool: http://<midTierServerName>:8080/arsys/shared/config/config.jsp.
    Replace midTierServerName with your mid-tier server name to form the actual URL in your case.
    The system prompts you for a password (default is arsystem) to open the Mid Tier Configuration Tool.
  2. Update the AR Server Settings.
    1. Click AR Server Settings.
      (Click the image to expand it.)
    2. Add the new AR System server.
    3. For name resolution, register newServerName in the new environment, and delete the existing servers (if any) in the host file or DNS.
  3. Update the General Settings.
    1. Click General Settings.
      (Click the image to expand it.)
    2. Update the following fields with the newAR System server name:
      • Preference Server(s)
      • Data Visualization Module Server(s)
      • Homepage Server
      • Authentication Server (if you want the mid-tier to use a specific authentication server)
  4. Click AR Server Settings, and delete the old AR System server name.
  5. Update the Report Settings.
    1. Click Report Settings.
      (Click the image to expand it.)
    2. If the BOXI/Crystal Report Server 11 Location field is not empty, update the field with the new BOXI/Crystal server name.
    3. Make sure that the Report Working Directory field is pointing to the correct directory.

Cleaning up files in the mid tier

  1. After you rename the server for the mid tier, stop the Java Virtual Machine (JVM) on which the mid tier is running.
  2. Delete all the contents of the midTierInstallationFolder/cache folder and midTierInstallationFolder/cachetemp folder (if it exists).
  3. Delete the viewStats.dat and viewStats.dat.bak files if they exist under midTierInstallationFolder/WEB-INF/classes folder.
  4. In you are using the prefetchConfig.xml file in midTierInstallationFolder/WEB-INF/classes folder to precache forms, update the server-name element to the new server name.
  5. Start the JVM mid tier.
  6. Delete the browser's temporary internet files.

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