20.02.04: Patch 4 for version 20.02
This topic contains information about the fixes in this patch and provides instructions for downloading and installing the patch.
This release consolidates the patches and hotfixes delivered for version 20.02.02 and later of Remedy platform components (Remedy AR System Server, Remedy Mid Tier, BMC CMDB, Atrium Integrator) into a single patch.
Because this patch includes the updates delivered in version 20.02.03, you can directly upgrade from version 20.02.00 or later to version 20.02.04 of Remedy IT Service Management Suite.
Updates
The Remedy 20.02.04 patch release is only for the Remedy Platform components (Remedy AR System Server, Remedy Mid Tier, BMC CMDB, Atrium Integrator).
Learn about the updates in this patch:
-
20.02.04: Patch 4 for version 20.02
in the Remedy AR System online documentation.
-
20.02.04: Patch 4 for version 20.02
in the BMC CMDB online documentation.
Defect fixes
This patch includes fixes for some customer defects. For more information about the defects fixed in this patch, see known and corrected issues.
Downloading the patch
The following table lists the patch components and links to the deployment packages on the BMC Electronic Product Download (EPD) site.
Access the following links and click on the Patches tab to view the patches:
Component | Link to the deployment package |
---|---|
Remedy Mid Tier and Remedy AR System Server |
Remedy AR System Server Version 20.02.04
Warning If you previously installed Remedy Mid Tier 20.02 by using a WAR file, and you want to upgrade to Remedy Mid Tier 20.02.04, download the applicable WAR file from the Electronic Product Download (EPD) site:
For steps on installing Remedy Mid Tier using WAR file, see Configuring your web server and installing BMC Remedy Mid Tier with a .war file. |
BMC CMDB | |
Atrium Integrator |
Before you begin
Before deploying the Remedy Platform package, any Remedy service such as “Remedy Action Request System Server <servername>” or “BMC Remedy Email Engine - <servername>” should be up and running. Additionally, all processes enabled in the armonitor.cfg/conf file, such as Reconciliation server, plugin servers, and other, should be up and running.
Remedy Platform 20.02.04 patch installation will not work with OpenJDK version 16 or 17.
You must first install the patch on Java version 1.8.x, and then upgrade the Java to OpenJDK version 16 or 17.- (Optional) If you have customizations, create a snapshot for reconciliation. Capture a snapshot of your application objects. For instructions, see Capturing a snapshot of server application objects.
Applying the patch for on-premises deployment
A user with AR System administrator permission can apply the patch by performing the following tasks:
Task | Action | Additional information |
---|---|---|
1 | Download the patch from EPD | Download the relevant patch from the Electronic Product Distribution (EPD) site. |
2 | Review the Before you begin section | Review the information in this section and perform the prerequisite steps for a successful patch deployment. |
3 | Run the patch installer | Run the patch installer in the following order:
|
Running the patch installer
Perform the following steps to upgrade your Remedy Platform to version 20.02.04:
To upgrade Remedy Mid Tier and Remedy AR System Server
Perform the following steps to upgrade your Remedy Mid Tier and Remedy AR System Server to version 20.02.04:
Unzip the appropriate suite installer that you downloaded (for example, ARSuiteKitWindows.zip or ARSuiteKitLinux.zip).
Navigate to the Disk 1 folder.
Start the installer and then, in the lower right corner of the Welcome panel, click Next.
- (Windows) Run setup.exe.
- (UNIX) Run setup.bin.
In the lower right corner of the Welcome panel, click Next.
Review the license agreement, click I agree to the terms of license agreement, and click Next.
On the Install/Upgrade selection panel, perform the following actions:
For zero-downtime upgrade, click Upgrade.
For staged upgrade, do one of the following based on how you set up systems for a staged upgrade:
If you are using the replicated database of your current production environment, click Install.
If you are upgrading a clone of your current production environment, click Upgrade.
- Select the specific products to upgrade.
For example, select AR System Servers and Remedy Mid Tier. - (Optional) Add a new language.
You can select additional localized views to install later. - Navigate to the directory in which you want to install the BMC Remedy AR System application.
The default locations are as follows:- (Windows) C:\Program Files\BMC Software\ARSystem
- (UNIX) /opt/bmc/ARSystem
- Click Next.
Resolve the errors and warnings, if reported, in the BMC Remedy Configuration Check report before proceeding with the upgrade.
- After the installer validates your inputs provided in the previous panels, the Installation preview panel appears, listing the product and product features that will be upgraded.
- Click Install.
The BMC Remedy AR System features you have selected are installed. After the post-installation cleanup, a summary of the installation appears. - Click View Log to review the installer log for any errors or warnings. The install logs are available at the following location:
- (Windows) C:\Users\Administrator\AppData\Local\Temp\arsystem_install_log.txt
(UNIX) /tmp/arsystem_install_log.txt
- To exit the BMC Remedy AR System installer, click Done.
To upgrade BMC CMDB:
Perform the following steps to upgrade your BMC CMDB to version 20.02.04:
- Unzip the installer.
- Navigate to the Disk 1 folder.
- Start the installer.
- For Windows, run setup.exe.
- For UNIX, run setup.sh.
- In the Welcome panel, click Next.
- Review the license agreement, click I agree to the terms of license agreement, and then click Next.
- In the AR System Server Information panel, perform the following actions:
- Enter AR System username and password.
- Enter AR System port number and host name.
- Navigate to the directory in which you want to install BMC Atrium CMDB.
The default locations are:- Windows: C:\Program Files\BMC Software\AtriumCore
- UNIX or Linux: /opt/bmc/AtriumCore
- Click Next.
The installer validates the system resources of your computer.
If you have upgraded Tomcat before upgrading CMDB, on the Tomcat Deployment Directory Information panel, provide the path to the new Tomcat directory and wait for the Tomcat Service Name to get populated automatically.
- In the Install mode panel, select Upgrade, and then click Next.
During upgrade, only existing BMC Atrium Core components are upgraded. - In the Confirmation panel, review that the database is backed-up and the memory requirement is met. Then click Yes and Next.
- Resolve the errors and warnings, if reported, in the BMC Configuration Check report before proceeding with the upgrade. If you ignore the installer instructions, the installer requires that you acknowledge those errors and warnings by selecting a check box before you proceed with installation or upgrade.
- Review the NE Plugin and Atrium Plugin ports.
In the Java Information panel, select the JRE path and click Next.
The Run Health Check panel appears.- Click Next.
The installer validates your inputs in the previous panels, and then the Installation Preview panel appears, listing the product and product features that will be installed. - Click Install.
A summary of the installation appears. - Click View Log to review the installer log for any errors or warnings. The install logs are available at the following location:
- (Windows) C:\Users_<installUser>_\AppData\Local\Temp\atriumcore_install_log.txt
- (UNIX and Linux) \tmp\atriumcore_install_log.txt
- To exit the BMC Atrium Core installer, click Done.
- Restart the BMC Remedy Mid Tier.
To upgrade Atrium Integrator Server and Client
To upgrade Atrium Integrator server and client, perform the steps given in the topic Performing the Atrium Integrator upgrade.
Patch installation logs
You can check the log files to view the installation status or any related errors. For more information, see Working with logs.
Related topics
Troubleshooting package deployment issues
Creating and deploying a binary payload
in AR System online documentation.
Comments
Log in or register to comment.