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.
The Deployment Automation user interface enables you to create and configure the Deployment Automation elements and initiate the deployment of your component versions. You can see and access only the elements for which you are authorized. Some common elements of the user interface are indicated in the following figure.
When the navigation menu is expanded, click the pin icon at the top right of the menu to pin it so that it stays open. Click the pin again to make the menu automatically collapse.
In the dashboard you may also see a message indicator . Click this to see important messages, such as upgrade suggestions for your server and agent versions.
Before you get started with Deployment Automation, here are some terms you should know.
Applications bring together components with their deployment targets and orchestrate multi-component deployments.
Components typically map to a functional part of a real world application, and represent deployable items, or artifacts, such as files, images, databases, and configuration materials.
Plugins provide functionality in discrete steps to be used in component and global processes for configuration of or deployment into target environments.
Environments represent logical deployment locations. Your deployment processes must run in at least one environment. Environments and their resources are used by applications and components at runtime.
Resources represent a deployment target on a Deployment Automation environment. Examples include physical machines, virtual machines, databases, or J2EE containers.
A pipeline is a pre-defined sequence of environments in which application process requests are executed.
Agents are physical resources for deployment. To run a deployment, an agent must be installed on the target server.
Agent relays are used to manage communication between servers and agents. Agent relays are typically used when agents are dispersed across geographic locations or must communicate through firewalls. Agent relays can also be used to manage network traffic in implementations where you have many agents.
Deployment packages enable you to deploy artifacts for multiple applications. They may also include component processes where components are shared among multiple applications and associated versions are to be deployed as part of the larger package.
Although there is no set order, a typical sequence for configuring Deployment Automation elements and deploying artifacts is as follows:
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.
Create and design component processes, defining the processes you want performed on target machines before, during, and after deployment of the component artifacts.
Create resources to represent logical locations on agent machines.
Create environments and assign resources to them.
Create and configure pipelines, sequencing environments and adding approvals.
Create an application, selecting the pipeline it will use.
Add components to the application.
Add environments to the application that are not included in the pipeline and map components to the environment resources they will use.
Create and design an application process to control the deployment. An application process typically initiates multiple component processes.
Run the application process to deploy the components.
Create and design deployment packages to run multi-application deployments.
Copyright © 2011-2018 Serena Software, Inc., a Micro Focus company. All rights reserved.