This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Creating and deploying a binary payload

A binary payload is a set of binary files, configuration files, batch, or Shell scripts. Binary payload deployment refers to the deployment of a custom binary payload across environments. 

Starting with BMC Remedy AR System 9.1.04, BMC provides all the hotfixes and patches in the binary payload format. You can download the patch or hotfix from the Electronic Product Download site and deploy the patch to your server group without running an installer. For more information, see  Applying a hotfix and a patch

Additionally, you can create a custom binary payload, which reduces the time it takes to apply customization changes. For example, you can promote the custom plugin changes from your development environment to the production environment. 
In summary, a custom binary payload provides these advantages:

  • You can deploy a patch or hotfix without using an installer.
  • The update is applied to all the servers in a server group.

 AR System components that support binary payload

You can deploy a binary payload onto the following components. 

  • BMC Remedy Action Request System Server
  • BMC Remedy Mid Tier 
  • (Version 9.1.04.001 and later) Remedy with Smart IT 2.0
  • (Version 9.1.04.002 and later) CMDB

Process for deploying a binary payload

The BMC Remedy Deployment application and binary payload deployment are two different applications. The BMC Remedy File Deployer process deploys a binary payload to the specified system. This triggers binary payload deployment. The payload can include binaries, scripts, and command line execution. For more information about BMC Remedy Deployment Application, see Creating and deploying a package using BMC Remedy Deployment Application.


The armonitor runs the File Deployer process. The operating system administrator controls the File Deployer process. An administrator can configure parameters for the File Deployer process. For more information, see File Deployer configuration parameters.

A binary payload is automatically deployed on the system when the filedeployer.localDeploymentRequired parameter is set to false. When the parameter is set to true (default), the administrator must run the arpayloaddeploymentutil.bat (Microsoft Windows) or arpayloaddeploymentutil.sh (UNIX) file on each server or component from the following location:

For AR Server—<Install Directory>

For components—<Component>/filedeployer 
For example, midtier/filedeployer

Navigate to AR System home directory (Microsoft Windows) or to ARSystem/bin directory (UNIX) and change the filedeployer.localDeploymentRequired parameter value from the deployconfig.properties file.

Administrators use the following information to create, deploy a binary payload:

Note

The armonitor.cgf file has the following new entries:

  • External-Windows-Service: process-type = BMC:EmailEngine, service-name="BMC Remedy Email Engine - 1"
  • External-Windows-Service: process-type = BMC:FlashBoardServer, service-name="BMC Remedy Flashboards Server -

These entries are used to start and stop the Flashboard and Email engine services when you apply a patch that is provided as a binary payload.

Related topics

Creating and deploying a package using BMC Remedy Deployment Application

Troubleshooting for Binary payload deployment

Was this page helpful? Yes No Submitting... Thank you

Comments