CDA Architecture

This topic provides the big picture of the CDA system and dependencies between modules.

Definition and Purpose

Automic Continuous Delivery Automation (CDA) is an end-to-end solution for planning, coordinating and automating software release processes, including automated deployments of complex multi-tier applications and configurations across heterogeneous, large-scale server environments.

The purpose of CDA is to unify enterprise application and infrastructure automation functionality onto a single platform - without the need of managing multiple tools. Users first architect and control the execution of application process workflows and then orchestrate the underlying infrastructure to meet the required service levels.

To access the CDA functionality, you use the browser-based Automic Web Interface (AWI) and the Release Automation perspective that is delivered with the AWI Extension.

Database management tools are installed on one of the clients, which is specifically used for administrative purposes.

CDA Components

The CDA solution consists of the following components:

• Automic Continuous Delivery Automation (CDA)

  • Automic Continuous Delivery Automation Server (CDA Server)
    • Web application
    • Web services
    • Command Line Interfaces (import/export, admin-cli)
    • XML Templates

  • Automic Continuous Delivery Automation Database (CDA Database)

• Automic Web Interface(AWI)

  • Automic Web Interface

    • Process Assembly perspective
    • Process Monitoring perspective
    • Administration perspective 
    • My Catalog perspective

  • Automic Continuous Delivery Automation Plug-in for AWI

    Graphical CDA user interface for CDA web application (Release Automation perspective)

• Automation Engine (AE)

  • Automation Engine Server (AE Server)

    • Automation Engine Server
    • Automation Engine Command Line
      Utilities

  • Automation Engine Database (AE Database)

  • Automation Engine Agents (AE Agents)

    • Unix/Linux Agents
    • Windows Agents
    • VMWare Agent
    • Webservices Agent
      

• Other Components:

  • Package Manager
  • Plugin Manager
  • Action Builder
  • LDAP Sync
  • Proxy
  • Analytics
  • Infrastructure Manager

  Action Packs:

  • Packages delivered with the CDA bundle. See Automic Compatibility Matrix. For more information, see Compatibility Information.

All components can be defined, handled or monitored centrally by the AWI Web Application, a web-based graphical interface.

The AWI Server provides the main user interface and holds the Release Automation perspective for CDA specific interactions.

The CDA Server is the core system for release and environment management, especially for planning and monitoring tasks and triggering automated procedures. It is responsible for defining application deployments, its components, packages, environments, and all other relevant parameters. This information is stored in the CDA Database.

The AE Server is responsible for executing all defined deployment workflows. The execution is done on the underlying systems, where the Automation Engine Agents are installed. The Automation Engine Database contains all required workflow definitions and actions, and stores the complete statistical information.

An AE Agent (Agent) is a software module that provides a de-centralized service for the purpose of deployment, either executing processes on a target operating system or providing connectivity to a target system (for example, for databases or middleware). They are responsible for executing automated procedures directly to target systems.

Interaction of the Components of the CDA System