Upgrading BMC Remedy AR System
After you prepare the server group for upgrade, you will run the installer multiple times to upgrade all of the AR System components. For example, you first upgrade the AR System server on one computer and then run the installer a second time to upgrade the mid tier on a different computer.
Before you upgrade BMC Remedy AR System
- If you have not done so already, perform the tasks in Preparing.
If you have not done so already, do one of the following to prepare the server group for upgrade:
- Preparing the AR System server for a server group upgrade - Perform these steps when you are performing a staged upgrade or plan to upgrade the server group during a scheduled outage window.
- Preparing for an in-place, zero-downtime upgrade of the platform - If you want to upgrade the platform components that are a part of a server group environment with no scheduled outage, you must perform pre-configuration steps on the primary and secondary servers prior to upgrade.
BMC Remedy AR System upgrade process
Upgrade the AR System products and components in the order listed, unless indicated otherwise.
|1||Perform the BMC Remedy AR System upgrade .|
Components and plug-ins upgraded
|2||Perform the BMC Remedy Smart Reporting upgrade.|
This step is required only if you have BMC Remedy Smart Reporting installed in your current environment.
If you are upgrading from a version earlier than 9.0.x, you have to perform a fresh installation of the BMC Remedy Smart Reporting component. For instructions, see Preparing to install BMC Remedy Smart Reporting.
|3||Perform the BMC Remedy AR System client upgrades.|
(Windows) You can upgrade clients before or after the AR System server upgrade. Use the BMC Remedy AR System installer (ARSuiteKitDeveloperWindows.zip) to upgrade the following clients:
Note: The clients can be installed on Windows only; they are not available for Linux or UNIX.
|4||Perform the BMC Remedy Encryption Security upgrade.|
Installing or upgrading a product on an encrypted BMC Remedy AR System server is not supported.
We recommend that you install BMC Remedy Encryption Security after you have upgraded all other components.
Before upgrading BMC Remedy ITSM applications, you must deactivate the BMC Remedy Encryption Security. For instructions, see Temporarily deactivating BMC Remedy Encryption Security.
|5||Install the offline documentation.|
(Optional) If you are bound by a firewall or do not have access to internet, install the latest offline Help content.
After you upgrade BMC Remedy AR System
After you finish upgrading the BMC Remedy AR System components, perform the Completing the BMC Remedy AR System upgrade.
|1.||Set the Java heap size.|
As a starting point, set the Java heap size to a minimum of 16 GB for a medium environment. After upgrading, you should monitor the memory usage to ensure that Java does not run out of memory. For complete recommendations, see Sizing baseline.
|2.||Update Java paths after upgrading.||If you have upgraded to the newer version of Java after upgrading to BMC Remedy Action Request (AR) System and BMC Atrium Core, manually update the Java paths as directed. |
|3.||Enable LDAP plug-ins for SSL connections postupgrade.||(Applicable only if upgrading from a version prior to 9.0) To enable LDAP plug-ins for SSL connections in configured networks after an upgrade, you must add an LDAP certificate to the certificate database for SSL communication.|
|4.||Update the armonitor configuration file for the plugin server.||You must update the armonitor configuration file for the plugin server to troubleshoot issues if the plug-in server runs out of memory.|
|5.||(Optional) Enable Call Home to monitor the upgrade.|
Enable the Call Home functionality to trace the upgrade sequence of plug-ins, tools, and components. This functionality is available after you upgrade BMC Remedy AR System sever. It tracks the sequence of upgrade activities performed by various plugins, tools, and components.
Where to go from here
|Up to process|
To install other platform components, return to Upgrading the platform.
When you have finished upgrading the platform, return to the appropriate upgrade process: