Home
Extending product function
Learn how to extend the function of HCL Launch.
REST API reference
You can use these REST interfaces to automate tasks.
REST commands for the HCL Launch server
The following list shows the commands that are available for the HCL Launch server.
agentCLI resource
Resources for creating, editing, and deleting agents.
Get agent statuses
Returns a JSONObject with count of agents to status.

Extending product function
Learn how to extend the function of HCL Launch.
- 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.
  - Running REST commands
    Many different programs can run REST commands. To run the command, you call a method on a REST resource and pass parameters or a request in JSON format.
  - Examples of REST API commands
    Many REST and command-line client commands have examples in their help topics. A few more examples using various programming languages and scenarios are provided here. The commands are similar for the server.
  - Authenticating for REST commands
    The way that you authenticate to run REST commands depends on how the server is set up and the tool that you are using to run the commands.
  - Deploying applications by using REST commands: An example
    The following example describes how to use the REST commands to deploy an application.
  - REST commands for the HCL Launch server
    The following list shows the commands that are available for the HCL Launch server.
    - agentCLI resource
      Resources for creating, editing, and deleting agents.
      - Get an agent maintenance task
      - Get agent maintenance tasks
      - Add a tag to an agent
      - Add an agent to a team
      - Delete a tag from an agent
      - Delete an agent
        Agents should be shut down before deletion.
      - Get information about all agents
      - Get information about an agent
        This command returns a JSON representation of an agent.
      - Get list of managed Java installations
        This command returns a list of managed Java installations for an agent.
      - Get list of managed Java installations in bulk
        This command returns a list of managed Java installations for a set of agents. Individual sub-requests may succeed or fail independently. A single request may contain up to 250 sub-requests.
      - Get the value of a property on an agent
      - Install Java packages as a new managed Java installations in bulk
        This command request a set of agents install Java, but does not wait for or report the results. The returned maintenance tasks can be used to query the result. Individual sub-requests may succeed or fail independently. A single request may contain up to 250 sub-requests.
      - Install a Java package as a new managed Java installation
        This command requests the agent install Java, but does not wait for or report the result. The returned maintenance task can be used to query the result.
      - List all tags on an agent
      - Remove a property from an agent
      - Remove an agent from a team
      - Rename an agent
        Rename an agent. Use this command if running the agent configuration script in the agent bin directory is not convenient. Only the administrator can run this method.
      - Restart an agent
      - Return high watermarks for agent usage
      - Get agent statuses
        Returns a JSONObject with count of agents to status.
      - Set a property on a agent
      - Set the configured JAVA_HOME of agents in bulk
        This command requests a set of agents set JAVA_HOME, but does not wait for or report the results. Each new JAVA_HOME will not take effect until the respective agent is restarted. The returned maintenance tasks can be used to query the results.Individual sub-requests may succeed or fail independently. A single request may contain up to 250 sub-requests.
      - Set the configured JAVA_HOME of an agent
        This command requests the agent set JAVA_HOME, but does not wait for or report the result. The new JAVA_HOME will not take effect until the agent is restarted. The returned maintenance task can be used to query the result.
      - Shut down an agent
      - Test the connection from an agent to the server
      - Uninstall a managed Java installation
        This command requests the agent uninstall Java, but does not wait for or report the result. If an installation is the active JAVA_HOME or configured as JAVA_HOME, that installation is not removed.
      - Uninstall a managed Java installations in bulk
        This command requests a set of agents uninstall Java, but does not wait for or report the result. If an installation is the active JAVA_HOME or configured as JAVA_HOME, that installation is not removed. The returned maintenance tasks can be used to query the result. Individual sub-requests may succeed or fail independently. A single request may contain up to 250 sub-requests.
      - Update agent settings
      - Upgrade an agent
        The agent will be upgraded to the agent version corresponding with the server version.
    - agentPool resource
    - application resource
    - applicationPipeline resource
    - applicationProcess resource
    - applicationProcessRequest resource
    - applicationTemplate resource
      Resources for working with application templates.
    - approval/task resource
    - authenticationRealm resource
    - blueprint resource
    - calendar resource
    - component resource
      Resources for working with components and for retrieving new component versions.
    - componentProcess resource
    - componentProcessRequest resource
      Resources for working with component processes.
    - componentTemplate resource
    - deploymentTrigger resource
    - diagnostics/latency resource
    - environment resource
    - environmentTemplate resource
    - frontendServer resource
      Resources for viewing and deleting frontend servers.
    - group resource
    - inventory resource
    - javaPackage resource
    - login resource
    - postProcessingScript resource
      Resources for working with post processing scripts.
    - process resource
    - processRequest resource
      Resources for working with generic process requests.
    - relay resource
      Resource for relay cli
    - resource resource
      Resource for working with resources.
    - resourceTemplate resource
    - secretstore resource
    - snapshot resource
    - sshInstallAgent resource
    - status resource
    - systemConfiguration resource
    - tags resource
    - team resource
      Resources for creating, editing, and deleting teams.
    - teamsecurity resource
    - user resource
    - vault/appRole resource
    - version resource
    - webhookTemplate resource
    - workflowTrace resource
      Resources for manipulating workflows.
    - zInventory resource
- Command-line client (CLI) reference
  CLI is a command-line interface that provides access to the HCL Launch 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.

Get agent statuses

Returns a JSONObject with count of agents to status.

Expected format:

{
    "ONLINE":4,
    "UPGRADE_RECOMMENDED":1
}

Requires Settings Tab permission

Request

GET https://{hostname}:{port}
    /cli/agentCLI/statuses
Accept: application/json

Table 1. Header parameters
Parameter	Type	Required	Description
Accept	`application/json`	true

Related CLI command: getAgentStatuses.