Learn how to extend the function of HCL Launch.
The HCL Launch server and blueprint design server each have a separate REST interface. You can use these REST interfaces to automate tasks on those servers.
The following list shows the commands that are available for the HCL Launch server.
Resources for reading, creating, and deleting deployment triggers.
UrbanCode plug-ins provide tools for creating component processes and integrations. IBM UrbanCode 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.
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.
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.
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 and for the blueprint design server.
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.
The following example describes how to use the REST commands to deploy an application.
Resources for working with agent pools.
Resources for working with applications, including manipulating the components and environments that are associated with applications.
Resources for editing and creating application processes.
Resources for creating, editing, and deleting agents.
Resources for working with application blueprints, which map application components to resource templates.
Resources for working with component processes.
Resources for working with component templates.
This command creates a deployment trigger for the given environment, component, application process, and user.
This command deletes a deployment trigger with the given ID.
This command returns a JSON representation of all users that can run deployment triggers.
This command returns a JSON representation of a single deployment trigger.
This command returns a JSON representation of all deployment triggers for an environment.
Resources for creating, editing, and provisioning environments.
Resources for working with environment templates.
Resources for viewing and deleting frontend servers.
Resource for managing inventory.
Resources for working with generic process requests.
Resource for relay cli
Resources for changing system properties and for updating system configuration settings.
Resources for adding users and groups to teams and for creating authorization tokens.
Resources for manipulating component versions.
Resources for manipulating workflows.
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.
Programmatically manage processes with PAC language.