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.
BMC provides all the patches in the binary payload format. You can download the patch from the Electronic Product Download site and deploy the patch to your server group without running an installer. For more information, see
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
- Remedy with Smart IT
- BMC 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 AR Monitor runs the File Deployer process. The AR Monitor for mid tier runs at port number 7320. For inward traffic, the AR Monitor listens on port 7320 and for outward traffic, the AR Monitor connects to the AR System server on the regular TCP port. The File Deployer process polls the AR System server to get deployment packages and informs the respective AR Monitor whenever a payload is available for deployment.
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—
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:
- Setting the component ranking order before deploying a binary payload
- Defining a custom binary payload
- Viewing the status of a binary payload|
- Deleting the binary payload backup files
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.