Cluster installation flow

This section provides end-to-end instructions for installing an on-premises ALM Octane server in a cluster configuration on Linux. A cluster is a group of application servers that run as a single system. Each application server in a cluster is referred to as a "node."

To install ALM Octane in a cluster configuration:

  1. For each node in the cluster, check requirements and access:

    Check requirements Verify that the all cluster nodes, including the first, meet all requirements and prerequisites. For details, see Supported and required environments and Prerequisites.
    Check database server access All cluster nodes, including the first, must have access to the database server on which the site database schema resides.
    Check repository access

    The repository directory has to be a shared directory visible to all cluster nodes. All nodes must have read and write access to the repository.

    Generally, the repository is located on an NFS or SAN server.

    If the repository is not located on a remote, dedicated machine, the repository location cannot be /opt/octane.

    The repository must be configured to use the same mount point (path) on all nodes.

    It is important that you enter the repository path using the same path name on all nodes. For example, you cannot have the path on the first server node defined as /opt/octane/repo and on additional nodes defined as /server1/opt/octane/repo.

    Check access between nodes

    All nodes must have access to each other. Verify ports are open in your firewall.

    ALM Octane needs to communicate between the nodes in the cluster on port 5701. Therefore, make sure that your firewall enables communication between the nodes of the cluster on the specified port..

    By default, outbound ports are open. Check inbound ports.

  2. Install ALM Octane on the first cluster node, as described in Installation.

    1. Deploy the ALM Octane installation files on to the first node.

    2. Configure initial site settings in octane.conf and optional configuration files.

      • Make sure to set the database server name and repository folder to values that all cluster nodes can access.

      • Enter values described in Cluster settings.

        ALM Octane validates these settings when starting. If they are not valid, the ALM Octane server does not start.

    3. On the first node only, start the ALM Octane server by running systemctl start octane. See Start the ALM Octane server.

  3. (Optional) If you want to set up a secure configuration for ALM Octane, follow the instructions in knowledge base article KM02707977.

  4. Log in to the first node in the cluster. For details, see Log in to ALM Octane.

  5. Download and deploy the ALM Octane package on each cluster node. For details, see Deploy ALM Octane and Deploy in cluster environment.

      Caution:
    • Do not configure octane.conf or other configuration files on the nodes. You will copy these files from the first node in the cluster.

    • Do not run connectnode.sh scripts.

  6. Copy all the configuration files located in /opt/octane/conf/ from the first cluster node to the /opt/octane/conf folder on each other node.

  7. On each other node, start ALM Octane by running systemctl start octane.

  8. (Optional) If you want to set up a secure configuration for ALM Octane in a cluster configuration, follow these instructions on each other node: Software Self-solve knowledge base article KM02707977.

  9. Log in to make sure ALM Octane is running on each other node. For details, see Log in to ALM Octane. Use the load balancer URL when you log in.

    Tip: For best performance, configure your load balancer with round-robin (stateless) configuration.

Back to top

Next steps: