Deployment Automation Overview


Examples and the Community

After you have installed and configured Deployment Automation, log in to the user interface.

Get started by configuring and running a simple deployment. See the Deployment Automation Walkthrough or visit the Community website to get pre-configured processes that you can import and run. A number of videos and other resources are also available on the Community website.

User Interface Overview

Deployment Automation enables you to create and configure elements and initiate the deployment of your component versions. You can only view and access the elements for which you are authorized. These are some of the common user interface elements:


  1. Click the navigation button image and select the module you want to work in. Depending on your role and privileges, you will see some or all of the following modules:
    • Management: create and configure the primary elements of Deployment Automation, design your processes, and run deployments.
    • Deployment: view information about deployments on a timeline, run deployments, and schedule deployments and blackouts.
    • Administration: configure selections that will be available to users when they work with Deployment Automation .
  2. The dashboard is shown at the top of the page. Options include:
    • Version Import Queue: view active version import requests.
    • Pending Approval Requests: view requests awaiting approval.
    • Processes: view processes executed within a given range of time.
    • User Profile menu: select from options to configure preferences such as locale, get help, visit the user community, view information about the product version, and sign out.

    In the dashboard you may also see a message indicator. Click to see important messages such as upgrade suggestions for your server and agent versions.

  3. Select an option from the navigation menu to view and manage information. This example shows Components selected.
  4. To filter the information shown in the content area, click the filter buttons to select or toggle filter criteria. The filter Search box searches various columns and further filters the list by showing only items that match the search string. In this example, the list is filtered by components that belong to the current user, and inactive components are not shown.
  5. Create or import an instance of the selected element.
  6. The content area of the page. In this example, the list of components is shown.
  7. Click any links in the content area to see more information. For example, for components, click the number under Used in Apps to see the names of the applications the component is associated with.
  8. Select from actions available for listed items. For example, in the component list click the Delete button to delete a component.


Before you get started with Deployment Automation, here are some terms you should know.

A Typical Sequence

Although there is no set order, a typical sequence for configuring Deployment Automation elements and deploying artifacts is as follows:

  1. Create components and set your source configuration type and version import approach. The source configuration type points to where the artifacts for a component are stored. You can import the artifacts into Deployment Automation CodeStation automatically or manually.

  2. Create and design component processes, defining the processes you want performed on target machines before, during, and after deployment of the component artifacts.

  3. Create resources to represent logical locations on agent machines.

  4. Create environments and assign resources to them.

  5. Create and configure pipelines, sequencing environments and adding approvals.

  6. Create an application, selecting the pipeline it will use.

  7. Add components to the application.

  8. Add environments to the application that are not included in the pipeline and map components to the environment resources they will use.

  9. Create and design an application process to control the deployment. An application process typically initiates multiple component processes.

  10. Run the application process to deploy the components.

  11. Create and design deployment packages to run multi-application deployments.