Welcome
Extending Product Function
Learn how to extend the function of HCL DevOps Deploy (Deploy).
Process-as-code feature
Programmatically manage processes with PAC language.
Generic process steps
Lists the various generic steps that can be used in a process.

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
A 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.
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).
- Plug-ins
  The HCL plug-ins provide tools for creating component processes and integrations. HCL plug-ins provides plug-ins for several common deployment processes, and others are available to integrate with a wide variety of tools, such as middleware tools, databases, and servers.
- Creating notification templates
  Notification templates are the basis for emails that the server sends to users after an event occurs on the server. You can create customized notification templates by modifying the default templates provided, or by creating new templates of your own.
- REST API reference
  You can use these REST interfaces to automate tasks.
- Command-line client (CLI) reference
  CLI is a command-line interface that provides access to the HCL DevOps Deploy (Deploy) server. It can be used to find or set properties and to run numerous functions.
- Process-as-code feature
  Programmatically manage processes with PAC language.
  - Using the PAC commands
    Use the PAC language to create HCL DevOps Deploy (Deploy) processes.
  - Understanding the PAC file format
  - Application process steps
    Lists the various application steps that can be used in a process.
  - Core component process steps
    Lists the various core component steps that can be used in a process.
  - Generic process steps
    Lists the various generic steps that can be used in a process.
    - add-process-warning
      The add-process-warning step adds a warning message to the executing process
    - acquire-lock
      The acquire-lock step allows acquisition of a process lock.
    - generic-manual-task
      The generic-manual-task step pauses the process until a manual approval is completed. This step is only valid in a generic process.
    - plugin
      The plugin step allows you to execute a plug-in command. Note that this step is not valid for an application process.
    - run-generic-process
      The run-generic-process step executes a generic process and waits for it to complete.
    - run-generic-process-for-each-affected-resource
      The run-generic-process-for-each-affected-resource step executes a generic process for each resource affected by the application process and waits for it to complete. This step is only valid in an application process.
    - set-final-process-status
      The set-final-process-status step that also appears as Set Status in the Web UI, forces the outcome status of a process to success or failure.
    - shell
      The shell step is a shortcut for the plugin step that specifies the Shell plug-in and the Shell command. Note that this step is not valid in an application process.
    - start
      The start step is a pseudo-step that defines the beginning of the process. As it is not a true step, it does not use the step keyword. The only completion condition is success. So, on success is not required or permitted.
    - switch
      The switch step allows decision logic in the process. It expands a variable by name or evaluates an expression containing a 'p' expression to a value. Based on the value, one case is selected and its actions are carried out.
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.

Generic process steps

Lists the various generic steps that can be used in a process.

To add feedback about this topic, select the following checkbox:

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 Four, 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. Personal data should not be shared in this comment box. See our Privacy Statement to understand how personal data is used.