Deployment Automation Terminology

Component

A component maps to a functional part of a real world application and represents a deployable artifact, such as CM baseline items. Each component can have a version.

Application

An application brings together all the components that need to be deployed together. They define the versions of each component and the environment the components must go through on the way to production. They also map resources, which are the hosts and machines a component needs within each environment. SDA applications are mapped to CM products.

Component process

A component processes defines how a component should be deployed, installed, or interacted with. A process typically contains a number of steps that are inter-dependent, and may include complex logic if a step in the process fails.

Application process

An application process is a high-level automation orchestration that can execute multiple component processes such as the automation of deployments and rollbacks. Application processes are executed as part of Dimensions CM baseline promotion and demotion.

Environment

An environment represents logical deployment locations. Your deployment processes must run against at least one environment. Environments and their resources are used by applications and components at runtime. 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.

Pipeline

A pipeline is a sequence of environments.

Agent

An agent is a physical resources used to run a deployment and must be installed on the target server.