HCL Portal high availability

HCL Digital Experience is licensed for use in a single-server configuration and might not be used in either a cloned configuration or a clustered configuration except when implementing idle standby for the purpose of failover.

In an idle standby configuration, a server is considered idle if it is used exclusively for administrative needs and to help a failover situation. HCL Portal is installed on the idle standby server, but it is not operational to service user transactions or to query workloads.

Implementing idle standby requires the purchase of a separate HCL Portal Idle Standby Part Number, in addition to licensing the primary server, regardless of whether your primary servers are currently licensed under the per User License Option or the per Processor Value Unit License Option.

Once you have an Idle Standby License Option, you can use HCL Portal in an idle standby configuration. To achieve failover, implement a primary node and a secondary node. The primary node can be configured to be active always; the secondary node becomes active only if the primary node fails.
Remember: For the deployment manager and each HCL Portal node to be in the cluster, verify that each system clock is set to within 5 minutes of the others or the addNode command fails.

The deployment scenario, Deploying HCL Portal for high availability using idle standby, in the HCL Portal wiki provides information about setting up an idle standby configuration.