Viewing the status of a binary payload

After you create and deploy a binary payload, you can view the status in the AR System Single Point Deployment Status form.

Binary payload deployment status values on the AR System Single Point Deployment Status form

The Status field on the AR System Single Point Deployment Status form shows the status of all the components in a payload. The following table lists the status values.

Status	Description
Not Ready	When there is a dependent process, this status indicates that the dependent process is pending completion.
Pending Download	Indicates binary payload download is pending.
Downloading	Indicates that the binary payload is downloading.
Download Success	Indicates that the binary payload download is completed successfully.
Download Failed	Indicates that the binary payload download is failed.
Deployment Success	Indicates that the binary payload deployment is successfully completed.
Deployment Failed	Indicates that the binary payload deployment is failed.
Pending Rollback	Indicates that the rollback is pending for the binary payload.
Rollback Success	Indicates that the binary payload rollback is successfully completed.
Rollback Failed	Indicates that the binary payload rollback is failed.
Skipped	Indicates that the binary payload deployment for a particular component was skipped because it is not applicable. For example, a binary payload cannot be deployed on .
User Cancelled	Indicates explicit cancellation of the binary payload on a specific server in a server group.
Timed Out	Indicates that the binary payload deployment timed out because the payload has remained in the same status for 48 hours, which is the default time-out criteria.
Monitor Unreachable	Indicates that the BMC Remedy File Deployer process is stopped or is not working.

When a payload is deployed, the files are asynchronously deployed and each system might succeed or fail. If a file cannot be deployed to a specific system, the system automatically rolls back to the previously deployed version. In this case, you must correct the issues and Retry the deployment by using the Retry Deployment button on the AR System Single Point Deployment Status form.

As a result, the status of a binary payload is different from the status displayed by BMC Remedy Deployment application.

The following table explains how rollback works when you create a binary payload using the AR System Single Point Deployment Payload form:

Status of a binary payload deployment	Action
Deployment fails	The Retry Deployment button on the AR System Single Point Deployment Status form is enabled.
Deployment is successful	The Retry Deployment button on the AR System Single Point Deployment Status form is disabled.
When you click Start Rollback on the AR System Singe Point Deployment Payload form and the binary payload deployment fails.	The Retry Deployment button on the AR System Single Point Deployment Status form is enabled.
When you click Start Rollback on the AR System Singe Point Deployment Payload form and the binary payload deployment is successfully rolled back.	The Retry Deployment button on the AR System Single Point Deployment Status form is disabled.

In AR System Deployment Management console, when a binary payload is successfully deployed, you can rollback the binary payload by using the Rollback button. If the binary payload deployment fails and you want to re-try, you must re-import or copy the package (binary payload) and deploy it.

Example: Understanding overall status of a binary payload

Consider you are deploying a binary payload in a server group with five servers. The following table shows the status of the binary payload on all five servers:

Server 1	Server 2	Server 3	Server 4	Server 5	Auto roll-back	Overall payload status	Description
None	None	None	None	None	None	Pending	Status entry is not created.
Deployment successful	Downloading	Not Ready	Not Ready	Not Ready	None	In Progress	The deployment has started.
Deployment successful	Deployment successful	Deployment successful	Deployment successful	Deployment successful	None	Successful	The deployment was successful on all the servers.
Deployment successful	Deployment successful	Rollback Successful	Rollback Successful	Rollback Successful	No	Failed	The deployment was successful on two servers but failed on three servers.
Deployment successful	Deployment successful	Rollback failed	Rollback failed	Rollback Successful	No	Failed	The deployment was successful on two servers but auto rolled back on two servers after failure.
Rollback Successful	Pending Rollback	Deployment successful	Deployment successful	Deployment successful	No	Rollback in progress	The deployment has failed. Rollback is in progress.
Rollback Successful	Rollback Successful	Rollback Successful	Rollback Successful	Rollback Successful	No	Rollback successful	The rollback was successful.
Rollback Successful	Rollback Successful	Rollback failed	Rollback failed	Rollback Successful	No	Rollback failed	The rollback is failed on two servers.
Deployment successful	Deployment successful	Deployment successful	Deployment successful	Skipped	No	Partial success	The deployment was successful on four servers but it was skipped on one server.
Deployment successful	Deployment successful	Deployment successful	User cancelled	User cancelled	No	Partial success	User Cancel was selected while the deployment was active on the third server.
Rollback successful	Rollback successful	Rollback successful	User cancelled	User cancelled	Yes	Rollback successful	User cancel was selected while the rollback was active on the third server. The first three successful deployments were rolled back.
Skipped	Skipped	Skipped	Skipped	Skipped	None	Skipped	There was no process to deploy or no path was found.
Deployment successful	Deployment successful	Deployment successful	Deployment successful	Timeout	None	Partial success	The deployment timed out because the status remained the same for more than 48 hours.
Deployment successful	Deployment successful	Deployment successful	Waiting for manual signal	Deployment successful	None	Waiting for manual signal	Since manual deployment was selected for the fourth server, the server waits for the administrator to run the arpayloadutil.bat or arpayloadutil.sh file.

In a server group environment with servers on multiple operating systems (for example Microsoft Windows and UNIX), the Microsoft Windows binary payload is successfully deployed on the Microsoft Windows server and the UNIX binary payload is successfully deployed on the UNIX server. However, because the Microsoft Windows binary payload gets skipped on the UNIX server and the UNIX binary payload gets skipped on the Microsoft Windows server, the overall payload status is displayed as Partial Success, even though the deployment is successful on that server.

Viewing the status of a binary payload

Binary payload deployment status values on the AR System Single Point Deployment Status form

Example: Understanding overall status of a binary payload

On this page