20.02.08: Patch 8 for 20.02
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 site:
Component | Link to the deployment package |
---|---|
Remedy Developer Studio | The latest available version of Remedy Developer Studio for on-premises environments is 21.3.10. Download the version here: Warning: Do not install Remedy Developer Studio in the same location where AR System or BMC CMDB is installed. AR System Clients: Developer Studio, Data Import Version 21.3.10 |
Remedy Mid Tier and Remedy AR System server | Remedy AR System Server Version 20.02.08 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.08, 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.Important: After you apply the Remedy Mid Tier and Remedy AR System Server patch 20.02.08, update the arreportingapi91_build009.jar file with a new JAR file. |
BMC CMDB | |
Atrium Integrator | Atrium Integrator Server: BMC Atrium Integrator Server Version 20.02.08 Atrium Integrator Client: BMC Atrium Integrator Client Version 20.02.08 |
Before you begin
- Before deploying the Remedy Platform package, a 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 processes, should be up and running. - (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. - In a server group, install the 20.02.08 patch on your primary server first and then install the patch on the secondary servers.
- To get the latest updates and fixes for Developer Studio, we recommend that you use Developer Studio 21.3.10 version with the Remedy 20.02.08 patch.
- The Remedy 20.02.08 patch is compatible with Open JDK versions 16 and 17.
However, to run the 20.02.08 patch with Open JDK versions 16 and 17, perform the following steps:- Install Open JDK 11.
- Run the Remedy 20.02.08 patch installer with Open JDK 11.
- Upgrade your Open JDK version to Open JDK 16 or 17.
Update the Java paths.
For more information, see Remedy AR Server -Running AR 2002 Patch005 installer with OpenJDK 16 and 17 and Updating-Java-paths-after-upgrading-Java.
- For the Windows environment, install the Visual Studio update as mentioned in the link: https://www.microsoft.com/en-us/download/details.aspx?id=30679.
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 relevant patch from the Electronic Product Distribution (EPD) site. | |
2 | Review the information in this section and perform the prerequisite steps for a successful patch deployment. | |
3 | Warning: Do not install Remedy Developer Studio in the same location where AR System or BMC CMDB is installed. 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.08:
To install Remedy Developer Studio
Download Remedy Developer Studio version 21.3.10 here - AR System Clients: Developer Studio, Data Import Version 21.3.10.
- Install Remedy Developer Studio by performing the steps given in Installing-the-BMC-Remedy-AR-System-Server.
To upgrade Remedy Mid Tier and Remedy AR System Server
- Unzip the appropriate suite installer 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, click Upgrade and 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.
After you apply the Remedy Mid Tier and Remedy AR System Server patch 20.02.08, update the arreportingapi91_build009.jar file with a new JAR file.
For more information, see Knowledge Article number 000415593 (Support logon ID required)..
To upgrade BMC CMDB
- 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 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 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
If the installation fails, see Troubleshooting-BMC-Atrium-Core-issues.
- To exit the BMC Atrium Core installer, click Done.
- Restart BMC Remedy Mid Tier.
To upgrade Atrium Integrator Server and Client
To upgrade Atrium Integrator server and client, perform the steps given in 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 payloadin AR System online documentation.