As we've already stated, there are three opportunities for automation of the build and deploy process:
The actual building and assembling of the code into EARs
The deployment of EARs onto a runtime
The preparation of a runtime for the EAR (that is, configuration of the server (J2EE resources, clusters, etc.) to support the application)
In addition, you can also choose to automate the validation of the deployment by automatically running verification tests after deployment. In fact, the entire process can be combined together into a larger set of scripts that performs everything in one single operation. You can imagine that such a set of steps might be performed every night against a development integration environment on a development ...