The deployment server has a fulfiller service that periodically passes through each queue and performs tasks such as moving deployments whose deploy time has arrived into the appropriate queue. You can configure the frequency of these tasks through the schedule property in the /atg/epub/deployment/DeploymentFulfiller component.
The deployment fulfiller service is solely responsible for starting deployments. When a deployment reaches the head of the deployment queue, the fulfiller acts as follows:
Verifies the target site is in a deployable state—that is, the target site is: accessible, not in an error state, and not running a current deployment.
Moves the deployment out of the queue and into the position of the current deployment.
Starts the deployment and moves on.
Deployments that complete successfully delete themselves and nudge the fulfiller to check the queue for the next deployment. Deployments that fail wait in an error state and display as such in the Admin Console until a deployment administrator corrects the problem or abandons the deployment.
