Welcome
Modeling Software Deployment
Modeling software deployment in HCL DevOps Deploy (Deploy) includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Components
Components represent deployable items along with user-defined processes that operate on them, usually by deploying them.
Component processes
A component process is a series of user-defined steps that operate on a component's artifacts.
Importing specific component processes
Component processes define the steps required to deploy, configure, or update a specific component. You can import specific component processes to reuse a standardized deployment across multiple applications or environments without recreating a process each time.

Release Notes
This section includes what's new, defect fixes, and deprecations and removals in all releases.
System Requirements
This document includes information about the hardware, containers, prerequisite software, supported operating system, and database requirements with component level detail for the HCL DevOps Deploy (Deploy).
Getting Started
Quickly become productive with HCL DevOps Deploy (Deploy).
Installing
A HCL DevOps Deploy (Deploy) installation consists of a Deploy server, a database server, and at least one agent.
Upgrading and Migrating
Stay updated with latest features and functionalities by upgrading HCL DevOps Deploy (Deploy) server, agents, and relays. This section also provides instruction on how to migrate your Deploy instance.
Integrating
HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
Administering
Learn how to administer settings in HCL DevOps Deploy (Deploy) elements and communication between the elements.
Managing Security
HCL DevOps Deploy (Deploy) uses a flexible team-based and role-based security model that maps to your organizational structure.
Modeling Software Deployment
Modeling software deployment in HCL DevOps Deploy (Deploy) includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
- Dashboard
  The Dashboard is a live page that gives you real-time insights into the status of your deployments and agents through graphs and charts.
- Components
  Components represent deployable items along with user-defined processes that operate on them, usually by deploying them.
  - Creating components
    A component consists of artifacts of a single source type and one or more processes. Component creation is the same for all source types, however; the content can be different.
  - Component processes
    A component process is a series of user-defined steps that operate on a component's artifacts.
    - Importing specific component processes
      Component processes define the steps required to deploy, configure, or update a specific component. You can import specific component processes to reuse a standardized deployment across multiple applications or environments without recreating a process each time.
    - Exporting specific component processes
      You can export specific component processes to save and share deployment configurations for reuse across applications or environments.
  - Component versions
    Each time a component's artifacts are imported into the repository, including the first time, a separate version is stored in CodeStation. Versions can be assigned automatically by HCL DevOps Deploy (Deploy), applied manually, or come from a build server.
  - Component properties
    Components can have several types of properties. The server keeps track of changes to component properties as property versions.
  - Creating component manual tasks
    A component manual task interrupts a component process until manual intervention is done. To create a component manual task, add a manual step to a component process, and select a notification template.
  - Component templates
    With a component template, you can save and reuse component processes and properties and create components from them; template-based components inherit the template's properties and process.
  - Component change logs
    Change logs provide information about modifications to components.
  - Deleting components
    When a component is deleted, it cannot be activated later.
- Resources
  A resource is a logical deployment target that typically resolves to an agent and a user-defined construct that is based on the architectural model of HCL DevOps Deploy (Deploy).
- Applications
  Applications are responsible for bringing together all the components that must be deployed together.
- Application environments
  An environment is a user-defined collection of resources that hosts an application.
- Application templates
  With an application template, you can save and reuse a collection of resources, environments, processes, and tagged components or component templates to create a standardized application.
- Application processes
  Application processes, like component processes, are created with the process editor. You use application processes to deploy or to roll back components.
- Application blueprints
  An application blueprint maps application components to a resource template. When you create an environment or provision one from the cloud, you can use the blueprint as a model.
- Application pipelines
  Allows you to run application processes in multiple environments and promote versions through a set of stages.
- Snapshots
  A snapshot is a collection of specific versions of components and processes. Typically, a snapshot represents a set of component versions that are known to work together. In most cases, snapshots include all of the components in an application.
- Manual application tasks
  A manual application task interrupts an application process until manual intervention is done. To create a manual task, add a manual step to an application process and select a notification template.
- Approval process
  You can add approval requirements to deployments. Deployments with approvals cannot be completed until all approvers respond. Approvers can respond to requests on the Work Items tab, or by email.
- Inventories
  You use different inventories to track installed components and properties in HCL DevOps Deploy (Deploy) elements.
- Processes
  Processes are automated tasks that run on agents.
- Statuses
  Create and apply statuses to track component inventory states or to track component versions in environments and resources.
- Properties
  Properties are variables that store information about many different elements, including components, environments, processes, and applications. You can also set global properties for the system.
- Tags
  A tag is a user-defined, shared, short label that you use to classify, view, and conduct operations on objects such as applications, components, agents, and resources.
- Webhooks
  Using the webhooks, you can send text-based responses to users in messaging platform such as MS Teams and Slack when a specific event occurs during deployment process.
Deploying
Learn how to deploy applications in HCL DevOps Deploy (Deploy).
Reporting
Provides several different deployment and security reports.
Extending Product Function
Learn how to extend the function of HCL DevOps Deploy (Deploy).
Troubleshooting and Support
Learn how to troubleshoot some common issues with HCL DevOps Deploy (Deploy).
Security Considerations
You can act to ensure that your installation is secure and set up user access controls.

Importing specific component processes

Component processes define the steps required to deploy, configure, or update a specific component. You can import specific component processes to reuse a standardized deployment across multiple applications or environments without recreating a process each time.

Before you begin

You must have ensured that the component process source file to be imported is a JSON or YAML file.

About this task

By importing processes in HCL DevOps Deploy (Deploy), you can incorporate specific deployment logic for components, making them reusable across different applications and environments.

Note: When you export components, applications, processes, or templates, and then import them on a different computer, you must ensure that you install the same versions of the same plug-ins on both computers.

Procedure

Log in to Deploy.
Click Components.
Components page is displayed.
Select the component to which you want to import specific component processes.
Click Processes > Import component process.
The Import Component process dialog is displayed.
Select Process Upgrade Type from the dropdown list.
Click Choose File to upload the component process source file that you want to import.
Notes:
- You must create the JSON or YAML file that contains the component definition on a server that uses the same version of Deploy as the destination server.
- Only JSON and YAML file types are supported.
Click Submit.

Results

You have imported the specific component process. The imported component process is listed in Processes tab for the component.

What to do next

You can set environment-specific properties by editing the process in the process editor. See Editing processes.

To add feedback about this topic, select the following checkbox:

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners Four, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site. Personal data should not be shared in this comment box. See our Privacy Statement to understand how personal data is used.