Deployment workflows can be performed via 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"] as well as via the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. or the Enterprise Control CenterAutomic's web application that provides a single, browser-based interface for the ONE Automation platform.. The following description provides information on the requirements and the process.
Deployment workflows are workflows that were specially defined for Automic Release Automation. Deployment workflows are usually activated via Automic Release Automation and all values/parameters are forwarded to the Automation Engine. However, it is also possible to start workflows like this via the Automation Engine UserInterfaceThis is the Automation Engine's graphical user interface. [Formerly called the "Rich Client", "RichGUI" and "Dialog Client."]. In this case, all parameters/values required to execute the deploymentThe deployment of a single application revision to an environment within a single activity. 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."] are determined by Automic Release Automation.
Within the Automation Engine system, a Java-based work processA part of the component Automation Engine. It is responsible for an Automation Engine system's processes (see also 'Primary work process'). (JWP) must be installed and started. The JWP installation instructions can be found in the Administration Guide.
The following settings must be set in the UC_CLIENT_SETTINGS VARA objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task in every 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. in which deployment workflows are to be started:
UC_CLIENT_SETTINGS | Description | |
---|---|---|
Setting | Value | |
ARA_WS_INT | URL to the desired Automic Release Automation instance | Full URL (including protocol and port) of the Automic Release Automation instance |
DEPLOYMENT_CLIENT | Y | Specifies whether the client should be used for Automic Release Automation deployments. The Deployment tab of workflows is only displayed if this setting is activated. |
In order to enable communication between JWP and ARA, the ARA Web applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. certificate must be added to the keystore of the Java runtimeThe duration of a task's execution. It refers to the period between a task's start and end. It does not include its activation period (see also: activation and start). environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications., under which the JWP is started. To do this, import the certificate (e.g., "test.cer" file) with the Java keytool, which is located in the BIN directory of the Java home directory:
keytool -import -keystore cacerts -file <Path and file name of the certificate>
Next, enter the Java keystore passwordA secret combination of characters for a Automation Engine user. and confirm the "Trust this certificate?" request with "yes".
How the HTTPS certificate for the ARA Web application is set and exported is described in the Automic Release AutomationARA documentation.
If a workflow that was configured as a deployment workflow via the Deployment tab is activated, the Automation Engine sends a request to the ARA instance (1). Specifically, the deployment descriptor is requested – a packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components. with all of the parameters required to execute the deployment workflow. In the next step (2), general parameters of the Automation Engine (workflow RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component ., content of the Deployment tab such as workflow name and application name), which are required for the request, are transmitted to ARA.
In the final step (3), the ARA instance transmits all of the parameters/ values to the Automation Engine and the workflow is continued.
Workflows waiting for the ARA parameter have the following statusThis represents the condition of a task (such as active, blocked, generating).:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |