Home
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.
Application environments
An environment is a user-defined collection of resources that hosts an application.
Environment gates
An environment gate is a requirement that must be met before component versions can be deployed to an environment. For example, a component version might need to pass certain tests or receive an approval.

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.
  - Creating environments
    Before you can run a deployment, you must define at least one application environment that associates components with an agent on the target host.
  - Creating environments from WebSphere® Application Server cells
    You can import information about a WebSphere® Application Server cell into resources and then use those resources in an environment.
  - Deployment triggers
    Starting with HCL Launch version 7.1.0, deployment triggers replace the run process after a version is created feature.
  - Environment gates
    An environment gate is a requirement that must be met before component versions can be deployed to an environment. For example, a component version might need to pass certain tests or receive an approval.
    - Creating environment gates
      Create gates that specify the conditions that must be met before a component version or snapshot is deployed to the environment. The conditions are defined on the component version statuses and snapshot statuses.
  - Mapping resources and components to environments
    Specify where components are deployed by adding a resource or resource group to the environment. Then, map the components to those resources.
  - Comparing environments
    You can compare two environments to see differences in their inventories or property values.
- 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.
- 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 HCL Launch to retrieve credentials of individual servers from the Vault and authenticates a plug-in step in the deployment process.

Environment gates

An environment gate is a requirement that must be met before component versions can be deployed to an environment. For example, a component version might need to pass certain tests or receive an approval.

Each environment gate can require a combination of version statuses. These statuses can be combined by using "and", "or" or "not" operators. When the component version has satisfied the statuses and operators, it can be deployed to the environment.

For example, the following figure shows the gate for an environment. The gate has three component version statuses: Passed Tests "or" both Latest "and" along with "Not" Failed Tests. In this case, a component version cannot be deployed to the environment unless it has the Passed Tests status or the Latest status and not Failed Tests. A simple environment gate that requires components to have at least one of two component version statuses

To see the statuses on a component version, click Components > selected component > Versions and look in the Statuses field.