Troubleshooting for Binary payload deployment
Starting with BMC Remedy AR System 9.1.04, you can create a custom binary payload, which reduces the time it takes to apply customization changes. This topic describes the issues that might occur while creating and deploying a binary payload. For more information about creating and deploying a binary payload, see Creating and deploying a binary payload.
Check for following possibilities if you detect issues while creating and deploying a custom binary payload:
|The AR System Server has multiple entries with different ranks|
The AR System Monitor form does not show an entry for the war file that is deployed on the mid tier.
Any specific process specified in the AR System Single Point Deployment Payload form is not responding.
The processes defined on the AR System Single Point Deployment Payload form are operated by the File Deployer process.
|The binary payload is not deployed on the admin server.|
The binary payload is not deployed because the admin server is down and the
See to it that the admin server is up and run the arpayloaddeploymentutil.bat (Microsoft Windows) or arpayloaddeploymentutil.sh (UNIX) file.
Create and deploy a new binary payload for the new admin server.
|You run the arpayloaddeploymentutil.bat (Microsoft Windows) or arpayloaddeploymentutil.sh (UNIX) file when File Deployer for the specific component is down.|