2.2 Linux Installer

The Linux servers are provided by you. The Linux installer installs the appliance administration console, along with Reflection for the Web.

2.2.1 System requirements - Linux installer

Supported operating systems

These versions or greater of the following operating systems are supported.

  • SUSE Linux Enterprise Server 15 SP4

  • OpenSUSE Leap 15.4

  • Red Hat Linux 9

  • Rocky Linux 9

  • Oracle Linux 9

  • AlmaLinux 9

Minimum CPU and memory requirements

The following minimum resources are required for each node. These requirements assume that no other production software is installed on the node. If additional software will be run on the node, more resources need to be added to accommodate the other software accordingly.

  • 8 CPU Cores

  • 16 GB RAM

  • 100 GB disk space (SSD)

    NOTE:Be sure that a large part of the 100 GB is available to /var/opt/opentext.

Fast storage

To ensure optimal performance and reliability, the use of a solid-state drive (SSD) or other fast storage solutions is required. Not using SSD based storage may lead to inconsistent behaviors and errors.

Disable swapping

For optimal performance and reliability, swap must be turned off on every node. Please refer to the specific documentation of your Linux distribution for guidelines on how to disable swapping.

Fixed IP address

A fixed, non-changing IP address is required for each node. DHCP (Dynamic Host Configuration Protocol) is supported but the IP must be reserved and cannot change.

Network ports

The following ports must be exposed and available between all nodes.

Port

Purpose

6443

Kubernetes API Server

8472

Virtual LAN

10250

Kubernetes metrics

2379-2380

etcd

The following ports must be exposed for outside access:

Port

Purpose

443

Product access

3000

Security Proxy Server*

8001

AJP**

* The Security Proxy port use is optional.

** The AJP port is used when optionally integrated with Microsoft's IIS web server.

Additional firewall rules

The following source IP ranges must be added to the trusted zones list:

Source IP Range

Purpose

10.42.0.0/16

Pod communication

10.43.0.0/16

Service communication

Required third-party packages

The following third-party Linux packages are required for installation:

bash, curl, grep, gawk, wget, jq, haveged, zip, bind-utils, sysstat, strongswan, apparmor-parser, util-linux, iscsi-initiator-utils or open-iscsi, nfs-utils or nfs-common, supportutils or sos

These packages will be installed automatically for you during product installation. However:

  • In the case of Red Hat, you must add the EPEL (Extra Packages for Enterprise Linux) repository in order to gain access to these packages. Specifically, the epel-release repository is required.

  • For OpenSUSE, add the SUSE Linux Enterprise (sle) repository to retrieve the supportutils package.

Some of these packages are platform-specific and are not required on all platforms.

Supported web browsers

The following web browsers are supported:

  • Google Chrome (recommended)

  • Mozilla Firefox (recommended)

  • Microsoft Edge

Other Reflection for the Web requirements

Check the requirements for the Reflection for the Web clients and SDK.

Terminal session (client)

When clients are centrally managed by MSS, only Windows is supported.

An MSI file (Windows only) is provided to install the RWeb Launcher on Windows workstations, from which the RWeb client is launched.

NOTE:You will use the MSS Assigned Sessions list and the Reflection for the Web Launcher to launch Reflection for the Web sessions.

RWeb SDK

The RWeb SDK is supported on any platform.

2.2.2 Installing using the Linux installer

To install your product, be sure the System Requirements are met before you proceed.

Installation steps

  1. From the Downloads site, download the Linux installer script (install*.sh) for Reflection for the Web.

  2. Enable execute permissions for the installer: chmod 744 install*.sh

  3. Ensure that an operating system firewall is not blocking any required ports, and thatmasquerading is enabled.

  4. With elevated privileges (for example, sudo), run the Linux install script (.sh) to install the product.

  5. A PGP key is used to verify that the downloaded file has not been manipulated by a third party. If the displayed signing information represents a known and trusted entity, such as Micro Focus, then enter y to install the public key and continue.

    Alternatively, refer to this knowledge base article to download the key separately and verify the file: Get public keys

  6. When the installation completes, a verification tool is automatically executed.

  7. If verification succeeds, then the services automatically start, and you can move on to the next step.

    If verification fails, see Troubleshooting the Linux installation

Troubleshooting the Linux installation

Symptom: “Permission denied" messages with references to zgrep in the output

Possible fix: Check that the AppArmor profile for zgrep is not too restrictive for the verification process.

Once the issues are addressed and sudo cspctl verify runs without errors, run sudo cspctl start to start the system. Then run sudo cspctl enable to have the system start automatically after server restarts.

If issues remain, please contact Customer Support for assistance.

Next step:

After you install Reflection for the Web, it’s time to Configure your Cluster.

2.2.3 Upgrading using the Linux installer

When upgrading, it is important to remove any activation files from MSS associated with previous versions of Host Access for the Cloud. Leaving obsolete activation files in place may result in limited access to sessions.

What’s required before upgrading?

  • Administrative privileges for the operating system.

  • The cluster will be unavailable for end users during the upgrade process. We recommend planning a maintenance window accordingly.

  • Each node in the cluster must be in a Ready state before you attempt to upgrade.

Upgrade steps

To upgrade your product, first ensure all nodes in the deployment are in a Ready state. Then perform these steps:

  1. From the Software Licenses and Downloads (SLD) portal, download the Linux installer script (install*.sh) for your product.

  2. Enable execute permissions for the installer:

    chmod 744 install*.sh

  3. On each node in the cluster, update one node at a time by repeating the following steps:

    1. Copy the installer to the node, run the Linux install script (.sh) with elevated privileges, (for example, sudo), to upgrade the product.

    2. After the upgrade is complete, the verification tool automatically runs.

      • If verification succeeds, the services will automatically start.

      • If verification fails, review the troubleshooting steps.

    3. After the CSP service starts, wait until the updated node shows a status of Ready. The cluster status can be checked by running the following command with elevated privileges: cspctl status

      NOTE:

      • Throughout the cluster upgrade process, it is normal to see warnings and errors in output of cspctl status. These will clear once the entire upgrade process is complete.

      • It can take up to 15 minutes for the node to become Ready.

    4. Move on to the next node in the cluster.

  4. After all of the nodes in the cluster have been updated, on any node in the cluster with elevated privileges, run: cspctl cluster scale

  5. Wait for the cluster to return to a healthy state with all nodes showing Ready using: cspctl status. This process can take up to 15 minutes.