Welcome
Modeling software deployment
Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Creating 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.

Welcome
Welcome to the HCL Launch 7.3.0 documentation, where you can find information about how to install, maintain, and use HCL Launch.
Release information
Overview
This section provides overview and getting started information.
Learning
Tutorials and instructions for all experience levels.
Installing
An HCL Launch installation consists of the HCL Launch server, a database, and at least one agent.
Upgrading and migrating
Learn how to upgrade HCL Launch elements, including the server, agents, and how to migrate data.
Uninstalling
Learn how to uninstall an HCL Launch server, or agent.
Integrating
HCL Launch supports integrations with other IBM® products, products from others, and certain cloud systems.
Administering
Learn how to administer settings in HCL Launch elements and communication between the elements.
Managing security
HCL Launch uses a flexible team-based and role-based security model that maps to your organizational structure.
Modeling software deployment
Modeling software deployment in HCL Launch 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.
- 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 Launch.
- 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.
- Creating 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 Launch 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.
- Secret Stores
  Allows you to retrieve credentials of individual servers from the Vault and authenticates a plug-in step in the deployment process.
Deploying
Learn how to deploy applications in HCL Launch.
Reporting
provides several different deployment and security reports.
Extending product function
Learn how to extend the function of HCL Launch.
Troubleshooting and support
Learn how to troubleshoot some common issues with HCL Launch.

Creating 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.

Procedure

Open an application process in the process editor.
From the Utility Steps folder, add a Manual Application Task step to the process.
In the Edit Properties window, specify the following properties for the step:

Name

Specify a name for the step.

Notification Template

Specify the notification template to use. These templates refer to the notification scheme that is used by the application (see Creating Notifications in a Notification Scheme). If you select None, notifications are not created when the step runs.

Only Allow Deploying User To Complete

Restrict approval to the user who started the deployment.

Properties

Optionally, add one or more properties to the task. You can use these properties later in the process just like output properties from other steps.

Who can approve this task

Any User

Any user can approve the task.

Role Member By Environment

Specify an environment role that can approve the task.

Role Member By Application

Specify an application role that can approve the task.
Click Save to save the properties for the step.
Include the manual task in the process as with any other step.
Save the process.

Results

When you run the process, it pauses at this step, sends a notification, and waits for approval before the process continues. To approve the task and resume the process, click the Respond link for the step in the process log, click Approve, and then click Submit. You can also resume the process from the Work Items tab.

Note: Starting in version 7.2.1, you can view the name of the approver of a manual task under ManualTask/ApproverName on the properties page.