If the SAS Deployment Agent is not started, the following messages appear repeatedly in the SAS Web Application Server log.

2014-06-27 08:51:52,304 [localhost-startStop-1] INFO  [sasadm@saspw] com.sas.svcs.backup.dao.DeploymentAgentClient - Set connection properties for SAS Deployment Agent.
2014-06-27 08:51:52,605 [localhost-startStop-1] ERROR [sasadm@saspw] com.sas.svcs.backup.dao.DeploymentAgentClient - Command Status: 4
2014-06-27 08:51:52,606 [localhost-startStop-1] INFO  [sasadm@saspw] com.sas.svcs.backup.dao.DeploymentAgentClient - Unable to connect to agent.
2014-06-27 08:51:52,606 [localhost-startStop-1] INFO  [sasadm@saspw] com.sas.svcs.backup.dao.DeploymentAgentClient - java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
. . .more message lines. . .
2014-06-27 08:51:52,608 [localhost-startStop-1] ERROR [sasadm@saspw] com.sas.svcs.backup.dao.BackupServerHelperDAO - Error occurred while copying file /SAS/ebivaconfig/Lev1/Utilities/configuration.properties on host mdtrhel.unx.sas.com !
com.sas.svcs.backup.client.BackupServiceException: java.lang.NullPointerException
. . .more message lines. . .

You can either ignore these messages or you can start the deployment agent by following the steps in the section "Starting and Stopping the Deployment Agent" in "Chapter 6: Operating Your Servers" of the SAS^® 9.4 Intelligence Platform: System Administration Guide, Fourth Edition.