Use > Application deployment > Components

Components

Overview

You can create and modify components in applications that you have permissions to edit (see Set permissions).

To view an example of an application with simple components, see .

About components

Components represent the content of an application. The components implement the various functions of the application. A component is associated with a specific tier. There are eight types of components that you can use to populate the tiers of an application.

Component type

Icon

Purpose

Code

Copies files to a target server. For example, this might be a set of HTML files that implement a web-based store. See Code components.

Script

Runs a script on a target server during the deployment of an application. For example, you might have two scripts: one that shuts down all applications before the deployment, and another that starts the applications up again after deployment. See Script components.

Configuration File

Creates a new configuration file on a target server. These files typically contain very specific information for a particular application. For example, you might need to create a configuration file that specifies information about a database. See Configuration File components.

Application Configuration

Deploys existing Application Configurations from the SA Library to a target server. See Application Configuration components.

Software Policy

Attaches a Software Policy from the SA Library to a target server. Alternatively, you can specify that the policy be installed instead of attached. See Software Policy components.

Package

Installs a Software Package from the SA Library on a target server. Alternatively, you can specify that the package be attached as a policy. See Package components.

OO Flow

Initiates an HPE Operations Orchestration (OO) workflow. For example, the workflow might be that whenever a specific application is deployed, an email is sent to the product owner. See OO flow components.

DMA Flow

Initiates an HPE Database and Middleware Automation (DMA) workflow on a target server, instance, or database. For example, you could use a DMA workflow to install critical database patches.

Windows Registry

Adds or deletes Windows registry keys or values. This type of component is only available for Windows tiers. See Windows Registry components.

Components are executed against servers. By default, components are deployed in the order in which they were created. You can modify this order if you have permission to edit the application (see Changing the deployment order of components).