Home
Administering
Learn how to administer settings in HCL Launch elements and communication between the elements.
Server settings and configuration
After you install HCL Launch, you can modify the server configuration and configure more options.
Modifying the context root of the server
After you install the server, you can modify the context root, if your server configuration requires it.

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, 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.
- Adding cold standby servers
  You can add cold standby servers to serve as a backup server or for disaster recovery. You must start the secondary server or servers when the active server fails, and network traffic is routed to the secondary servers.
- Backup and recover
  You can back up and recover the contents of your HCL Launch installation.
- Server settings and configuration
  After you install HCL Launch, you can modify the server configuration and configure more options.
  - Increasing the amount of memory that is available to the server
    If you see "Out of memory" errors or are using the server at high capacity, increase the amount of system memory that is available to the server.
  - Modifying the context root of the server
    After you install the server, you can modify the context root, if your server configuration requires it.
  - Enabling maintenance mode
    Maintenance mode stops activity on the server so you can run important tasks that require the server to be idle.
  - Changing the database password
    If you change the password for your database, you must update the password on the server.
  - Changing passwords for the server KeyStore
    You can change the Java™ KeyStore password for the server.
  - Changing passwords for the encryption KeyStore
    You can change passwords for the encryption KeyStore.
  - Changing or updating the JRE of servers
    You can change the JRE of active servers by editing their configuration files.
  - Working with Notifications
    HCL Launch can send email notifications whenever user-defined trigger events occur on the server.
  - Managing locks
    A lock ensures that processes do not interfere with one another. Normally, locks are released after they are no longer needed. Sometimes, a lock is not released, and its associated process is unable to complete.
  - Server settings
    These tables list the settings for several system-wide settings for the server.
- 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.
- 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

Modifying the context root of the server

After you install the server, you can modify the context root, if your server configuration requires it.

Procedure

Stop the server.
From the server installation directory, rename the directory server_install/opt/tomcat/webapps/ROOT to a new name, such as server_install/opt/tomcat/webapps/deploy
Use the server installation directory for server_install. The default server installation directory is /opt/launch/server on Linux™ and C:\Program Files\launch\server on Windows™.
Make a backup copy of the file opt/tomcat/conf/server.xml.
Open the file opt/tomcat/conf/server.xml in a text editor

In the server.xml file, find the following line of code:

<Context path=""
  docBase="ROOT"
  debug="0"
  reloadable="false"
  useHttpOnly="true"
  sessionCookieName="JSESSIONID_8080">

In this code, change both the docBase attribute and the path attribute to the name of the new folder.
For example, if you renamed the ROOT folder to deploy, the code looks like the following example:
```
<Context path="deploy"
  docBase="deploy"
  debug="0"
  reloadable="false"
  useHttpOnly="true"
  sessionCookieName="JSESSIONID_8080">
```
Save the file.
Restart the server.

Results

Now you can access the server at the following URL:

https://hostname:port/foldername

Use the new name of the folder as foldername.