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.
Creating applications
You can create an application from scratch or import an existing one.
Exporting applications
Exporting applications creates a JSON file (file extension json) that contains the properties, components (and their associated properties and processes), and processes of the applications.

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.
    - Importing applications
      If you exported an application, you can import the application on a different server. When you import an application, you can create an entirely new application or upgrade an existing one.
    - Exporting applications
      Exporting applications creates a JSON file (file extension json) that contains the properties, components (and their associated properties and processes), and processes of the applications.
  - Rational Team Concert™ Build
    The Rational Team Concert™ Build system defines resources that are used to describe and manage builds.
- 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.

Exporting applications

Exporting applications creates a JSON file (file extension json) that contains the properties, components (and their associated properties and processes), and processes of the applications.

About this task

For information about JSON, see http://www.json.org/.

Note: Exporting applications in this way includes only the most recent version of each component process and application process.

Procedure

When you export an application, components, snapshots and other items that are associated with the application are also exported, including their properties and processes (if they are available to the exporting server). Notification schemes are not exported.

To export one or more applications:

On the Applications pane (Applications), select the check box next to one or more applications.
At the top of the table, click Actions and then click Export.
The file is saved in the default download location for your browser.

What to do next

You can import the application to another server that uses the same version of HCL Launch. See Importing applications.