You can deploy assets from one environment to another (for example, from a development environment to a production environment) using Deployer and the ABE. In runtime-based deployment, you use Deployer to deploy assets from source servers to target servers. In repository-based deployment, you use ABE to build assets from source servers or a VCS to a file-based repository, and then use Deployer to deploy the assets from the repository to target servers. Software AG recommends using repository-based deployment.

If no firewall separates your development, test, and production environments, install one Deployer to handle all environments. The host machine must have access to all source servers you want to deploy from, and all target servers you want to deploy to. If you are using Command Central, install Deployer on the same machine as the Command Central you install to manage your development and test environments.

If you want to use repository-based deployment, install ABE on the same machine as Deployer. The machine must be able to access the file system that will host the file-based repository. If you want to build assets from a VCS instead of source servers, the machine must be able to access the VCS.

If a firewall separates your development and test environments from your production environments, install a separate Deployer to handle your production environments. The host machine must have access to all target servers you want to deploy to. If you are using Command Central, install Deployer on the same machine as the Command Central you install to manage your production environments.

Restrict access to the machine to only those people who need to use Deployer or ABE (and Command Central, if applicable), such as release managers, infrastructure engineers, system administrators, and operators.