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.
Build System Toolkit
Each build computer contains an installation of the Rational® Team Concert™ Build System Toolkit.

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
  Approval processes are created when you want a manual intervention in executing a particular task or process step.
- 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.

Build System Toolkit

Each build computer contains an installation of the Rational® Team Concert™ Build System Toolkit.

The Build System Toolkit consists of the following major components:

Jazz™ Build Engine: The Jazz™ Build Engine is a command-line tool that polls for and processes build requests from Rational® Team Concert™. When the Jazz™ Build Engine is started, it must identify a corresponding build engine in Rational® Team Concert™. TheJazz™ Build Engine can then accept any build request whose build definition is supported by the build engine. The Jazz™ Build Engine runs the Ant script and targets that are specified in the build definition. Each build is represented in Rational® Team Concert™ by a build result.
Build toolkit: The build toolkit is a collection of Ant tasks. Ant scripts can use these tasks to send information (such as build progress, results, links, artifacts) to Rational® Team Concert™ to include in the build result.
Build agent: The build agent is a lightweight process that handles agent-based builds that support z/OS® or IBM® i build scenarios. Jazz™ Build Engine
Note: The Jazz™ Build Engine is a component of the Build System Toolkit; it refers to the process that runs on a build computer and runs Ant scripts.