Serena Deployment Automation

The Deployment Automation Platform for Continuous Delivery


An environment is a user-defined collection of resources that host applications. An environment is the application's mechanism for bringing together components with the agent that actually deploys them. Environments are typically modeled on some stage of the software project lifecycle, such as development, QA, or production. A resource is a deployment target, such as a database or J2EE container. Resources reside on a host which can be a physical machine, virtual machine, or cloud-based.  

Comparing Environments with Serena Deployment Automation

Environments can have different topologies. For example, an environment can consist of a single machine, be spread over several machines, or be spread over clusters of machines. Approvals are generally scoped to environments. 

Environmental Control

Environments are created at the global level and used by multiple applications. This enables IT organizations to use shared or application-specific environments. Deployment Automation maintains an inventory of every artifact deployed to each environment and tracks the differences between them.

Environments can be imported and exported. Importing/exporting can be especially useful if you have multiple Deployment Automation servers, for example, and need to quickly move or update environments. After you create an environment, you add it to an application. Environments may be used by multiple applications. You can optionally enforce an approval process or implement application gates before the deployment can be deployed to the environment. You can also set black-out dates within an individual environment to make sure that it aligns to deployment schedules and policies.

Learn More

for Serena Deployment Automation

Solution Brief:
for Serena Deployment Automation