User Guide > Objects > Alphabetical Listing > Deployment Tab

Deployment Tab

The Deployment tab is an objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task-specific tab that is only avaialble in workflows provided that the clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type.'s deploymentThe deployment of a single application revision to an environment within a single activity. functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… is active.

You activate the client's deployment function in the setting DEPLOYMENT_CLIENTof the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_CLIENT_SETTINGS.

This tab includes the settings that are required for the installation and deployment processes. Deployment processes and their parameters are defined in the Automic Release AutomationAutomic Release Automation (ARA), is an end-to-end solution for planning, coordinating and automating software release processes, including automated deployment of applications across large-scale server environments and covers all mentioned use cases. [Formerly called "Application Release Automation", "Release Manager" and "Deployment Manager"] and processed by using workflows in the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes..

You can activate deployment workflows via Automic Release Automation, the Automation Engine or the Enterprise Control CenterAutomic's web application that provides a single, browser-based interface for the ONE Automation platform.. Note that certain requirements must be met in order to be able to activate them via the Automation Engine or the Enterprise Control Center.

You can also define the workflows using the Enterprise Control Center's "Process Assembly" perspective.

Field/Element Description
Deployment

Check this box to activate the workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."]'s deployment settings.

When you have activated it, you can select whether you use an application workflowA workflow which is defined on application level and consists of a number of component workflows. or a component workflowA workflow which should be executed for a component of an application within one ore more application workflows for installing, udating or removing the application.. The other fields that display depend on the selection you have made.

Application Workflow

The workflow that is responsible for an applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity.'s complete deployment process.

It includes one or several component workflows.

Application Name

The name of the application as defined in the Automic Release Automation.

Examples: ECCAbbreviation for the Enterprise Control Center, Tomcat, etc.

Workflow Name

The name of the workflow.

It is defined for the application in the Automic Release Automation. This makes it possible to assign several application workflows to an application.

Examples: installation, de-installation, etc.

Component Workflow

The workflow that is responsible for a certain step in the deployment process (such as the installation of a certain program or the configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied.).

It is part of an application workflow.

Application Name The name of the specified componentA component is a single deployable application artifact. As an example, this can be yourfile.war to be deployed into a Tomcat container. Each component has different properties which determine where to get it from, how to configure it, etc. You will need one component per application artifact: e.g., one for the application tier and one for the database backend.'s application.
Component Name

The name of the specified application's component.

It is defined for the application in the Automic Release Automation.

Examples: databaseA database is an organized collection of data including relevant data structures., configuration, etc.

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH