Knowledge Article
Remedy - D2P - ITSM / Remedy AR Server - How to deploy a Remedy patch using the AR Deployment Console and use arpayloaddeploymentutil utility
How to deploy a Remedy/Midtier patch using the AR Deployment Console and arpayloaddeploymentutil utility
Remedy AR System Server
AR System Server
Remedy AR System /Midtier / ITSM 9.1.04 and higher
From Remedy version 9.1.04 and higher new patches will be implemented using the AR System Deployment Management Console (D2P) and the arpayloaddeploymentutil utility. How is a patch deployed? |
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. To deploy a new patch into Remedy or any custom packages the same procedure is used and needs to be done in two stages: 1- Deploy the package using the AR System Deployment Management Console. 2- Run the arpayloaddeploymentutil utility. 1- Deploy the package using the AR System Deployment Management Console. For this example we will use the AR System 9.1.04 Patch001 package. If you are going to apply MidTier hotfix, after downloading package (for example MT_9104P2_20200108_CU_ALL.zip) you need to unzip it, then import the zip file you got after unziping it (for example D2P_midtierARS_9.1.04.002-S202001081556200108.zip) 1- Go to AR System Administration > AR System Deployment Management Console 2- In the AR System Deployment Management Console select Transfer Package and Import : 3- Select the package to import and deploy: 4- Press Refresh after a few seconds or until the package has been imported and it will be listed with status Ready to Deploy : 5- Select the package and under Operations press Deploy : 6- The following message will appear : 7- And then the package will start being deployed: Note: To see the status of the different components being deployed and having the package selected go to the Manage Package section and press View: 8- Once the Package has been deployed it will be displayed the status in the main AR System Deployment Management Console: 2- Run the arpayloaddeploymentutil utility. 1- To run the arpayloaddeploymentutil utility open a Command Prompt session (preferably Run as administrator in some cases) and browse to the ARS installation directory: ...\BMC Software\ARSystem and type arpayloaddeploymentutil.bat For Linux: Location : Installed directory bmc/ARSystem/bin File : arpayloaddeploymentutil.sh step 2 for : For Midtier hotfix To run the midtier arpayloaddeploymentutil utility open a Command Prompt session (preferably Run as administrator in some cases) and browse to the Midtier installation directory ...\BMC Software\ARSystem\midtier\filedeployer\ and type arpayloaddeploymentutil.bat For Linux: Location : Installed directory bmc/ARSystem/midtier/filedeployer run using command ./arpayloaddeploymentutil.sh Press Enter. Note: You may receive the message: ........ .......\BMC Software\ARSystem>arpayloaddeploymentutil.bat AR System Deployment Utility JAVA_HOME env variable is not defined ........ If this is the case run the command java -version to know which is the current default Java version, for example: ........ C:\Program Files\BMC Software\ARSystem>java -version java version "1.8.0_92" Java(TM) SE Runtime Environment (build 1.8.0_92-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) ........ Go to the Java installation directory to confirm this. In the same CMD session set the JAVA_HOME to the directory where the Java version obtained in the previous step is located, for example: set JAVA_HOME=<full path to the java installation directory> For Linux: [root@serverabc bin]# export JAVA_HOME=/opt/java/jre1.8.0_201 [root@serverabc bin]# echo $JAVA_HOME /opt/java/jre1.8.0_201 Press Enter and then run again arpayloaddeploymentutil.bat 2- The arpayloaddeploymentutil utility will run displaying the following: 3- The arfiledeployer.log is For AR server : Logs are located in ....\BMC Software\ARSystem\Arserver\Db For Mditier refer the logs at ...\BMC Software\ARSystem\midtier\filedeployer\Logs
|
Attachment(s):