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.
Applications
Applications are responsible for bringing together all the components that must be deployed together.
Rational Team Concert™ Build
The Rational Team Concert™ Build system defines resources that are used to describe and manage builds.

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.
  - Getting started with creating applications
    Applications associate resources with environments and define processes to run deployments.
  - Creating applications
    You can create an application from scratch or import an existing one.
  - Rational Team Concert™ Build
    The Rational Team Concert™ Build system defines resources that are used to describe and manage builds.
    - Build System Toolkit
      Each build computer contains an installation of the Rational® Team Concert™ Build System Toolkit.
- 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.
- 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.

Rational Team Concert™ Build

The Rational Team Concert™ Build system defines resources that are used to describe and manage builds.

The Rational Team Concert™ Build system in IBM® Rational® Team Concert™ defines the following types of logical resources that are used to describe and manage builds:

Build definition

A build definition describes:

The workspace to process.
The Ant scripts and targets to run against the workspace.
The schedule for the build.
The properties to simplify the configuration of the build.
The build engines that can handle build requests for the build definition.

Build engine

A build engine represents a Build System Toolkit Jazz™ Build Engine running on a designated build computer. A Jazz™ Build Engine running on a build computer correlates itself to a build engine in Rational® Team Concert™ by specifying the unique identifier of the build engine.

Build request

A build request represents a scheduled or explicitly issued request to run a build according to a specified build definition. Build definitions are submitted to a build queue. A Jazz™ Build Engine receives and processes the build request if its corresponding build engine in Rational® Team Concert™ is listed as a supporting build engine for the build definition.

Build result

A build result represents the output of a build.