Home
Administering
Learn how to administer settings in HCL DevOps Deploy (Deploy) elements and communication between the elements.
Server settings and configuration
After you install HCL DevOps Deploy (Deploy), you can modify the server configuration and configure more options.
Changing or updating the JRE of servers
You can change the JRE of active servers by editing their configuration files.

Administering
Learn how to administer settings in HCL DevOps Deploy (Deploy) elements and communication between the elements.
- Backup and recover
  You can back up and recover the contents of your HCL DevOps Deploy (Deploy) installation.
- High availability and failover
  You can configure clustered HCL DevOps Deploy (Deploy) 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.
- Server settings and configuration
  After you install HCL DevOps Deploy (Deploy), 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 DevOps Deploy (Deploy) 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.
  - System settings
    System settings allows you to manage global settings for components, clean up, password requirement, security, mail-server, and much more.
- 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 DevOps Deploy (Deploy), you can modify its configuration or create an agent relay to facilitate communication to remote relays.
- Licensing
  HCL DevOps Deploy (Deploy) 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 DevOps Deploy (Deploy) 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 DevOps Deploy (Deploy) application by hiding or showing, and reordering of the table columns.
- Managing data

Changing or updating the JRE of servers

You can change the JRE of active servers by editing their configuration files.

About this task

Procedure

Note:

Any certificates that you imported to the old JRE cacerts file must be imported into your new JRE cacerts file as well. SeeConfiguring SSL on Apache Tomcat and LDAP servers for more information.
Starting from v7.2.1, the keystore converter utility is no more needed, and Deploy handles any necessary conversions itself.

Procedure

Install the new JRE.
Stop the server.
Update the location of the JRE in the following files:
- In the file server_install/bin/set_env, set the value of the JAVA_HOME system variable to the location of the JRE.
- In the file server_install/conf/server/installed.properties, set the value of the install.java.home property to the location of the JRE.
Note: As a shortcut, you can delete the old JRE and move the new JRE into the location of the old JRE. In this case, you do not need to update the JAVA_HOME system variable and install.java.home property because they now point to the new JRE.

Note: The value of the JAVA_HOME system variable must match the value of the install.java.home property.

Note: If you are upgrading to Java 9 or above and are moving off Oracle Java to AdoptOpenJDK you must manually remove the -Djava.endorsed.dir entry from the server_install/bin/set_env file.
If the server is running as a service on Windows:™
1. Open the file server_install\bin\service\_service.cmd in a text editor.
2. Edit the line that starts with the code set JAVA_HOME to the path to the new JRE.
3. Open a command prompt as an administrator.
4. Go to the server_install\bin\service folder.
5. Remove the service by running the following command:
```
service.cmd remove service_name
```
  Use the name of the service for service_name. To find the service name, open the services view and find the entry that starts with Deploy. The service name is in parentheses in this entry.
6. Reinstall the service by running the following command:
```
service.cmd install service_name
```
Start the server.