This section introduces Deployment Automation environments and provides instructions on creating, configuring, and managing them.
Deployment Automation environments represent logical deployment locations. Environments and their resources are used by applications and components at runtime.
Your deployment processes must run in at least one environment.
An environment brings together components with the agent that deploys them. Deployment Automation maintains an inventory of every artifact deployed to each environment and tracks the differences between them.
Environments are created at the global level and used by multiple applications. This enables you to use either shared or application-specific environments. Environments are typically modeled on stages of the software project life cycle, such as development, quality assurance, and production.
Environments can have different topologies. For example, an environment can consist of a single machine or can be spread over several machines or clusters of machines. Approvals are often required before processes can run in an environment.
After creating environments, you can create pipelines, which are sequences of environments where application process requests run. You can associate a preconfigured pipeline of environments and individual environments to an application.
Before you can run a deployment, you must create at least one environment and associate the environment with an application. Then you configure the environment for that application and its component versions. The configuration associates components with an agent on the target host. For details on configuring environments at the application level, see Application environments.
To work with environments, navigate to Management > Environments in the Deployment Automation user interface.
The following table describes the main tasks you can do on the Environments page.
View the following information about an environment:
Filter environments by their owner:
|Search||Search environments by name, description, or user role.|
|Create||To create an environment, click the Create button. For details, see Create environments.|
|Import||To import an environment, click the Import button. For details, see Import and export environments.|
|Edit||To modify the environment's name, description, color identifier, and replication export setting, click the Edit icon next to the environment.|
|Inactivate||To deactivate an environment, click the Inactivate icon next to the environment.
To make an environment active, click the Show Inactive button, and then click the Activate icon next to the environment.
|Export||To export an environment, click the Export icon next to the environment. For details, see Import and export environments.|
Note: Environments cannot be removed. This prevents any alteration of the deployment history for the environments.
Individual environment page
Clicking the name of an environment opens the selected environment's page where you can further configure and monitor the environment.
The following table describes the available options on the environment's page.
|Edit||To modify the environment, click Edit on the right.|
|Applications||View a list of applications associated with the environment.|
|Inventory||View the inventory for this environment. For details on application environments inventory, see Viewing the Environment Inventory.|
|Timeline||View the timeline specific to this environment.|
|Resources||View, add, or remove resources and resource groups associated with this environment. For details, see Map agents and other resources to environments.|
View and set environment properties:
For details, see Add or edit environment properties.
|Security||Set role membership and default permissions for this environment.|
To schedule processes and blackouts, click the Schedule button and select from these options:
Note: Some environment settings, such as overrides to security, are application-specific and are set as part of the application configuration. For more information, see Add environments to applications.