Home
Administering
Learn how to administer settings in HCL Launch elements and communication between the elements.
Agents and agent relay configuration
After you install an agent for HCL Launch, you can modify its configuration or create an agent relay to facilitate communication to remote relays.
Web agent configuration
Web agents use WebSocket and HTTP connections for communication. Web agents do not use JMS.
Web agent relay configuration
Starting with V7.0.4.0, relays can be configured to support web agents exclusively.

Administering
Learn how to administer settings in HCL Launch elements and communication between the elements.
- High availability and failover
  You can configure clustered HCL Launch servers, blueprint design servers, and agents for high availability. You can also configure agents and agent relays for failover.
- Setting up high-availability clusters
  To configure a high-availability cluster, you store shared files on network storage. Then, you configure multiple servers, set each server to access the same files and database, and configure a load balancer to distribute the traffic between the servers.
- Backing up and recovering
  You can back up and recover the contents of your HCL Launch installation.
- Configuring agents for failover
  To configure agents for failover, you specify two or more target servers for the agent to use. If one of the servers fails, the agent switches to another server from the list.
- Configuring agent relays for failover
  To configure agent relays for failover, you specify two or more target servers for the agent relay to use. If one of the servers fails, the agent relay switches to another server from the list.
- Server settings and configuration
  After you install HCL Launch, you can modify the server configuration and configure more options.
- Setting user preferences
  Each user can specify display options for the server, including the language for the server and how the server shows times and dates.
- Agents and agent relay configuration
  After you install an agent for HCL Launch, you can modify its configuration or create an agent relay to facilitate communication to remote relays.
  - Changing or updating the JRE of agents
    You can change the JRE of active agents by editing their configuration files.
  - Changing passwords for the agent relay keystores
    You can change the Java™ keystore passwords for the agent relay.
  - Caching artifacts on agent relays
    Agent relays can cache downloaded artifacts. Caching artifacts in this way improves performance because agents retrieve artifacts from agent relays instead of from the server.
  - Migrating agents to Web
    Agent Configuration Templates allow you to migrate JMS agents on a server to Web agents with the ability to revert back to the original JMS configuration. This allows you to specify connection details for groups of agents.
  - Migrating agents relays to Web
    JMS agent relays on a server can be migrated to Web with the ability to revert back to the original JMS configuration. This allows you to specify connection details for groups of agent relays.
  - Agent security and communication
    Agents use SSL-secured JMS, WebSocket, HTTP, and HTTPS protocols to communicate with the server.
  - Web agent configuration
    Web agents use WebSocket and HTTP connections for communication. Web agents do not use JMS.
    - Web agent communication
      For successful server and web agent communication, you must have configurations on the server and agent sides.
    - Web agent relay configuration
      Starting with V7.0.4.0, relays can be configured to support web agents exclusively.
    - Keystores configuration
      Server, agents, and agent relays keystores are used for a secured web communication between servers and agents.
    - Custom trust stores
      A custom trust store is simply another keystore file containing the custom trust roots. Unlike default trust store, a configuration step is required enable use of a custom trust store.
  - Removing and reinstalling agents as Windows™ services
    If you installed an agent as a Windows™ service, you can remove and reinstall the service.
  - Managing agents remotely
    After an agent is installed, you can manage (with the monitor process) many of its features from the HCL Launch web application.
  - Agent relay actions
    After an agent relay is installed, you can manage many of its features from the HCL Launch web application.
  - Setting agent properties
    Agent properties store information that is relevant to a specific agent.
  - Creating and managing agent pools
    Similar to resource groups, agent pools help you organize and manage agents that are installed in different environments.
- License management
  HCL Launch provides a 60-day license-free evaluation period. To use all product features after the evaluation period, you must have a license.
- Setting up the wizard for new users
  HCL Launch includes a wizard to help users become familiar with the procedures and steps in creating a deployment. Some configuration is required before the wizard can be used.
- Customizing the table views
  Customize a table view in the HCL Launch application by hiding or showing, and reordering of the table columns.
- Managing data

Web agent relay configuration

Starting with V7.0.4.0, relays can be configured to support web agents exclusively.

In this mode, no JMS connection between relay and server is required and JMS agents will not be able to connect. You must upgrade relays for agents with web communication enabled and associate with the relay from the UI. However, a successful agent communication does not require any configuration. The following web communication parameters are defined in the relayInstallDir/conf/agentrelay.properties file:

agentcomm.enabled=true
agentcomm.server.uri=random:(wss://ucd1.example.org:7919,wss://ucd2.example.org:7919)

Agent relay limits

The maximum number of agents that can be assigned to a relay is limited in each of the releases. See to the following table to check the number of agents that are allowed for a relay for your installed HCL Launch version.


Version	Relay mode	Agent type	Limit with default proxy	Limit with legacy proxy
7.0.4.0 or before	JMS mode	Web Agents	1K	N/A
		JMS Agents	1K	N/A
		Total	1K	N/A
7.0.4.0 to 7.0.5.0	Web mode	Web Agents	1K	N/A
		JMS Agents	0	N/A
		Total	1K	N/A
	JMS mode	Web Agents	1K	N/A
		JMS Agents	1K	N/A
		Total	1K	N/A
7.0.5.0 or later	Web Mode	Web Agents	10K	1K
		JMS Agents	0	0
		Total	10K	1K
	JMS Mode	Web Agents	10K	1K
		JMS Agents	1K	1K
		Total	10K	1K

In Linux, use the following utilities to reach the design limit of 10K concurrent agents:

sysctl:
```
fs.file-max >= 40000
```
ulimit:
```
nofile >= 40000
```

sysctl:

net.ipv4.ip_local_port_range >= "10000 65000"