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.
Components
Components represent deployable items along with user-defined processes that operate on them, usually by deploying them.
Component versions
Each time a component's artifacts are imported into the repository, including the first time, a separate version is stored in CodeStation. Versions can be assigned automatically by HCL™ Launch, applied manually, or come from a build server.
Restoring archived component versions
You can restore component versions by reloading archive files.

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.
  - Creating components
    A component consists of artifacts of a single source type and one or more processes. Component creation is the same for all source types, however; the content can be different.
  - Component processes
    A component process is a series of user-defined steps that operate on a component's artifacts.
  - Component versions
    Each time a component's artifacts are imported into the repository, including the first time, a separate version is stored in CodeStation. Versions can be assigned automatically by HCL™ Launch, applied manually, or come from a build server.
    - Tracking environment inventory for components
      You can track the environment inventory for each component by clicking the component and then going to the Usage tab.
    - Importing versions manually
      If the component does not import new versions automatically, you can import versions manually.
    - Cleaning up component versions
      You can configure the server to reduce the number of component versions by archiving them. You can specify global cleanup settings, cleanup settings for individual components, and cleanup settings for specific environments.
    - Restoring archived component versions
      You can restore component versions by reloading archive files.
    - Deleting versions
      If specific component versions meet the criteria for deletion, you can delete them.
    - Downloading component version artifacts
      Artifacts are generated when an application process of a component version runs successfully.
  - Component properties
    Components can have several types of properties. The server keeps track of changes to component properties as property versions.
  - Creating component manual tasks
    A component manual task interrupts a component process until manual intervention is done. To create a component manual task, add a manual step to a component process, and select a notification template.
  - Component templates
    With a component template, you can save and reuse component processes and properties and create components from them; template-based components inherit the template's properties and process.
  - Component change logs
    Change logs provide information about modifications to components.
  - Deleting components
    When a component is deleted, it is removed from the database and CodeStation and cannot be activated later.
- 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.
- 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.

Restoring archived component versions

You can restore component versions by reloading archive files.

About this task

These steps assume that you have cleaned up old component versions and stored them in archive files as described in Cleaning up component versions. To restore a component version, you must have the archive file that the server created for that component version.

Procedure

Click Settings > System Settings.
Under Legacy Configuration Options, select the Enable "Show Inactive" Links check box and then click Save.
Click Components, click the component, and go the Versions tab.
Select the Show Inactive Versions check box.
Click the component version to restore.
Click Restore from Backup.
Specify the path to the archive file on the server and then click Save.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.