_upgrade
Apply deployment package (post_upgrade)
After you upgrade Remedy applications to 18.05, you must apply the latest deployment package to complete the upgrade of your applications to the latest release. For more information, see Applying-a-deployment-package.
Check for patch include (upgrade_patch)
After you upgrade, check whether a patch or fix has been released in Release-notes-and-notices. When you upgrade the product, you must install the latest service pack and then apply the latest patch (if available). Patches are not full installations and must be applied over the latest full installation (main release or a service pack).
Planning AR upgrade (upgrade_planning_ar)
You can upgrade the platform components (BMC Remedy AR System and BMC Atrium Core) separately from any applications on the system. You must upgrade the AR System server and the Atrium Configuration Management Database (CMDB) together, and they must be at the same version. You can perform an in-place upgrade the platform components with zero downtime if they are deployed in a server group environment.
You must upgrade BMC Remedy Mid Tier to 18.08 or 18.05 at the same time or before upgrading the AR System server and the Atrium Core CMDB. AR System Server 18.05 introduces new dynamic data menus that do not work if a lower version of Mid Tier is used against AR System Server 18.05 or 18.08
Post-AR upgrade DDM config (upgrade_ddm_post_ARupgrade)
(Staged upgrade only) Immediately after you upgrade the BMC Remedy AR System server on the destination server (production staging server or QA), disable the AR System application dispatcher, Email Engine, and Assignment Engine in armonitor.conf or armonitor.cfg by placing a leading # (hash) on each line:
- arsvcdsp
- emaild
- apsvcae
Restart the AR System server. For instructions, see Starting-and-stopping-the-BMC-Remedy-AR-System-server.
Post-AR upgrade DDM config (upgrade_ddm_post_CMDBupgrade)
(Staged upgrade only) Immediately after you upgrade BMC Remedy Atrium CMDB on the destination server (production staging server or QA), disable the Reconciliation Engine and the Service Level Management collector in armonitor.conf or armonitor.cfg by placing a leading # (hash) on each line:
- arcmdbd
- arrecond
- slmbrsvc
- slmcollsvc
- BMC.FILTERAPI.NORM.ENGINE (from the ar.cfg file)
Restart the AR System server. For instructions, see Starting-and-stopping-the-BMC-Remedy-AR-System-server.
Before you begin the upgrade process (upgrade_beforeyoubegin)
Plan | Create an upgrade plan by reviewing the section Planning-an-upgrade. This document covers important upgrade decisions and considerations, such as system requirements, which upgrade method to use, and which components to upgrade. |
|---|---|
Prepare | Complete the tasks in the Preparing section, which will help you prepare for running the upgrade installers. |
Before you begin the upgrade procedure (upgrade_permissions)
If you have not done so already, prepare the system to run the installers. If you want to run in nonadmin mode on Windows, see Preparing-a-Windows-environment. If you want to run in nonroot mode on UNIX, see Preparing-a-UNIX-environment.
DDM migration support (upgrade_ddm_support)
Product | Earliest supported version from which you can migrate data |
|---|---|
BMC Remedy AR System | 7.6.04 |
BMC Atrium Core | 7.6.04 |
BMC Atrium Integrator | 7.6.04 |
BMC Remedy ITSM applications | 7.6.04 |
BMC Service Request Management | 7.6.04 |
BMC Service Level Management | 7.6.04 |
BMC Remedy Knowledge Management | 7.6.04 |
BMC Service Impact Manager | 7.6.04 |
Integration for BMC Remedy Service Desk | 7.6.04 |
BMC Process Designer | 7.6.04 |
BMC ProactiveNet Performance Management | 7.6.04 |
Preupgrade configuration (upgrade_preconfig)
In Centralized Configuration, under the com.bmc.cmdb.server setting, turn off the Normalization Engine by setting CMDB-Inline-Normalization to F. For details about Centralized Configuration, see .
Resetting to pre-9.1.02 values for Submitter mode and Localized server
Set the Submitter mode and Localize server to their pre-9.1.02 default values: changeable and False, respectively. See Setting license options and Setting the Localize Server option.
Commenting out NE and RE
Disable the Reconciliation Engine and the Normalization Engine by commenting out the following lines from the armonitor file and restart the AR System server.
For Windows
#"<...>\Program Files\Java\jre1.8.0_74\bin\java" -Xmx512m -classpath "<...>\AtriumCore\cmdb\plugins\ne;<...>\AtriumCore\cmdb\plugins;<...>\AtriumCore\cmdb\sdk\bin\arpluginsvr91_build001.jar;...\AtriumCore\cmdb\sdk\bin\arapi91_build001.jar;<...>\AtriumCore\cmdb\sdk\bin\arutil91_build001.jar;<...>\AtriumCore\cmdb\sdk\bin\log4j-1.2.14.jar;<...>\AtriumCore\cmdb\sdk\bin\cmdbapi91.jar;" com.bmc.arsys.pluginsvr.ARPluginServerMain -x <server-name> -i "<...>\ARSystem"
For Linux
#/opt/bmc/atriumcore/cmdb/server/bin/normeng.sh
Installing and upgrading sections for other spaces
The Remedy Deployment online documentation provides instructions on how to install and upgrade the components in the BMC Remedy IT Service Management (ITSM) Suite, which includes the following:
- Platform components: BMC Remedy Action Request (AR) System components and BMC Atrium Core components
- Application components: BMC Remedy ITSM core components, BMC Service Request Management, BMC Service Level Management, and BMC Remedy ITSM Process Designer
The following graphic illustrates scope and the contents of this online documentation.
Go to the following sections in the BMC Remedy ITSM deployment documentation for details.
Related topics
BMC Remedy with Smart IT installing
BMC Remedy with Smart IT upgrading
BMC Digital Workplace installing
Upgrading BMC Digital Workplace
BMC Remedy Single Sign-On installing
BMC Remedy Single Sign-On upgrading