Remedy - AR System Midtier - How to manually apply the Midtier hotfixes or patches when File Deployer(D2P) process is not available

Manage Support IDs

Use checkboxes to 'Remove support IDs/Users' or 'Allow to create Cases'
Support IDs for BMC Customer Support Site Guest User
Profiles Which Include    Back to All Support IDs
 

Knowledge Article

Remedy - AR System Midtier - How to manually apply the Midtier hotfixes or patches when File Deployer(D2P) process is not available
Remedy - AR System Midtier - How to manually apply the Midtier hotfixes or patches when File Deployer(D2P) process is not available
Remedy AR System Server
AR System Mid Tier
Hotfixes/Patches Deployment for AR System Midtier 9.1.04.002 or above.
Remedy AR System Server
AR System Mid Tier
Hotfixes/Patches Deployment for AR System Midtier 9.1.04.002 or above.
Starting Midtier 9.1.04 or above,  patches and hotfixes are designed to be applied using the BMC Remedy Deployment Management Console.
However, there are some instances where this process is not available like using Midtier 9.1.04 or newer against an older AR Server.  How can the hotfix(patch) be applied manually?.
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.


1.  Download the Hotfix or patch package.  For ex:  MT_2002P2_20220801_CU_ALL.zip   
Note:  The name of the hotfix zip file will vary as well as the GUID and the midtier_common_0.zip content

2.  Using the 7zip or Winzip utilities, unzip to a temporary location such as c:\temp 
Note:  Windows Explorer will not successfully unzip the files.
      The original zip file will need to be drilled down as follows using the MT_2002P2_20220801_CU_ALL.zip as an example:
  •       MT_2002P2_20220801_CU_ALL.zip unzips to a directory called MT_2002P2_20220801_CU_ALL
  •       Drill down into the MT_2002P2_20220801_CU_ALL
  •       Locate midtier.zip file.
  •       Unzip the midtier.zip.   
  •       The first directory level will be an unlabeled directory.   Open that to find the _items.zip file.
  •       Unzip the _items.zip file.   There will be another unlabeled directory.   
  •       Open that to find another directory labeled with the product GUID, IDGAA5V0G7T7AAR5Y5OTR4YVQFF8GM
  •       Open the IDGAA5V0G7T7AAR5Y5OTR4YVQFF8GM directory,    
  •       Open the ARSystemSinglePointDeploymentPayload_1659387634 directory
  •       Open find and extract the midtier_common_0.zip
  •       The midtier_common_0.zip contains directories.   Open the zip file to determine which directories need to be backed up.
3.  Stop the Tomcat supporting the midtier application and the BMC Midtier FileDeployer process/service.

4.   Make a backup copy of the needed midtier subdirectories structure.
Note:  backups will need to be made of all directories being updated by the hotfix.     

5.  Extract the contents of the midtier_common_0.zip to the midtier directory.   It will overwrite the files updated by the hotfix and leave in place the files that are not updated. 

6.   Clear the contents of the midtier/cache, midtier/PluginsCache directories.  Do not delete the entire directory.
      Clear the contents of the tomcat/work/Catalina/localhost directory.

7.   Restart Tomcat and the filedeployer service/process

NOTE : Please note that these instructions were written for hotfix Midtier 9.1.10.002 202208012248. If manually applying a later hotfix, the file and directory names will change but the directions will still apply. 

NOTE 2 : If the issue persists, check if the Java registry key is pointing to the right location
Remedy AR System Server
AR System Mid Tier
Hotfixes/Patches Deployment for AR System Midtier 9.1.04.002 or above.
Attachment(s):