Home
Administering
Learn how to configure 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.
Changing passwords for the server KeyStore
You can change the Java™ KeyStore password for the server.

Administering
Learn how to configure 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.
- 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.
  - 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.
  - Relocating CodeStation
    You can move the CodeStation artifacts to a different location on the server.
  - 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.
  - Updating the JRE for agent relays
    If you upgrade the JRE and change the JRE location, you must also update the agent relays. If you do not change the location of the JRE, you do not have to update these 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.
  - Customizing the Getting Started window
    You can customize the URLs that are contained in the Getting Started window that is displayed the first time that a user logs in to the HCL Launch server.
  - 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.
- Releasing VC LOB space
  After you upgrade to HCL Launch 7.0.5 and later, you can compress the amount of large object (LOB) storage space that HCL Launch uses in the vc_persistent_record database table.

Changing passwords for the server KeyStore

You can change the Java™ KeyStore password for the server.

About this task

The server Java™ KeyStore password must be identical to its certificate password. After you change both the server KeyStore password and certificate password, you must update the password in the server properties.

Procedure

Stop the server.
Open a command-line window, and go to the appdata/conf directory.
Change the server KeyStore password by using this command:
```
keytool -storepasswd -new newStorePassword -keystore server.keystore
-storepass changeit
```
The default server password is changeit. The keytool application is included in the Java™ developer kit and is not part of HCL Launch.

Change the certificate password by using this command:

keytool -keypasswd -alias server -keypass changeit -new newKeyPassword -keystore server.keystore -storepass newStorePassword

The default server alias is server.

In a text editor, open the server-install\conf\server\secured-installed.properties file.
Specify the new Java™ KeyStore password for the server in the following line of code:
```
server.keystore.password=newStorePassword
```
The javax.net.ssl.trustStorePassword property takes precedence over the secured-server.keystore.password property. If it is present in server-install\conf\server\secured-installed.properties file, update its password with this code: javax.net.ssl.trustStorePassword=newpassword. This property applies to all relevant KeyStores.
Specify the new Certificate password for the server in the following line of code:
```
server.key.password=newKeyPassword
```
Start the server.

Results

The server KeyStore password is changed and is obfuscated in the server-install/conf/server/secured-installed.properties file.