Welcome
Modeling Software Deployment
Modeling software deployment in HCL DevOps Deploy (Deploy) includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
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.
Using nested properties
You can use a property reference to construct the name of another property in a component process step.

Release Notes
This section includes what's new, defect fixes, and deprecations and removals in all releases.
System Requirements
This document includes information about the hardware, containers, prerequisite software, supported operating system, and database requirements with component level detail for the HCL DevOps Deploy (Deploy).
Getting Started
Quickly become productive with HCL DevOps Deploy (Deploy).
Installing
An HCL DevOps Deploy (Deploy) installation consists of a Deploy server, a database server, and at least one agent.
Upgrading and Migrating
Stay updated with latest features and functionalities by upgrading HCL DevOps Deploy (Deploy) server, agents, and relays. This section also provides instruction on how to migrate your Deploy instance.
Integrating
HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
Administering
Learn how to administer settings in HCL DevOps Deploy (Deploy) elements and communication between the elements.
Managing Security
HCL DevOps Deploy (Deploy) uses a flexible team-based and role-based security model that maps to your organizational structure.
Modeling Software Deployment
Modeling software deployment in HCL DevOps Deploy (Deploy) includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
- Dashboard
  The Dashboard is a live page that gives you real-time insights into the status of your deployments and agents through graphs and charts.
- 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 DevOps Deploy (Deploy).
- 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.
- Application pipelines
  Allows you to run application processes in multiple environments and promote versions through a set of stages.
- 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.
- 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 DevOps Deploy (Deploy) 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.
  - Creating, setting, and editing properties
    Properties can be created for most elements, including components, resources, applications, and agents. You can set and change properties in many different ways.
  - Property contexts
    Properties are available in various contexts. Not all properties are available for all contexts. To plan and set properties, you must know where to access properties and how that setting behaves in context.
  - Referring to properties
    HCL DevOps Deploy (Deploy) provides several ways to refer to properties.
  - Using nested properties
    You can use a property reference to construct the name of another property in a component process step.
  - Default properties
    Many default properties are available for use while a process runs. These properties provide information about the process and the elements that are involved in the process, such as applications, components, and resources.
  - Output properties
    Output properties are specialized properties that process steps generate. You use output properties to pass parameters to subsequent steps in a process.
  - System properties
    System properties are global variables for the server.
  - Property availability
    The properties that are available to you depends on the context. For example, in a component process, you can access the component properties of the current component. In an application process, you can access the application properties and environment properties, but not any component properties. The following table shows the processes in which each type of property is available.
- 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 a webhook, 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.
Deploying
Learn how to deploy applications in HCL DevOps Deploy (Deploy).
Reporting
Provides several different deployment and security reports.
Extending Product Function
Learn how to extend the function of HCL DevOps Deploy (Deploy).
Troubleshooting and Support
Learn how to troubleshoot some common issues with HCL DevOps Deploy (Deploy).
Security Considerations
You can act to ensure that your installation is secure and set up user access controls.

Using nested properties

You can use a property reference to construct the name of another property in a component process step.

About this task

Directly nesting property references, such as ${p:agent/{p:application/prop1}.agent.propertyname}, is not supported. However, you can use system properties to construct the outer property reference. Property resolution performs two passes after you run the component process. The first pass creates the property name, and the second pass resolves that property name.

Procedure

Create the following system properties from the Settings > Properties page:

Property name Property value
propStart ${p:
rightBracket }
In the component process step, replace the nested property reference with the following expression:
```
${p:propStart}agent/${p:application/prop1}.agent.propertyname${p:rightBracket}
```
Run the component process.
After you run the component process, property resolution performs two passes. In the first pass, if application/prop1 resolves to A, the expression becomes ${p:agent/A.agent.propertyname}. During the second pass, this property name is resolved and its value is returned.