This section provides end-to-end instructions for installing an on-premises ALM Octane server in a cluster configuration on Windows.
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."
We install ALM Octane in a cluster configuration by:
Verifying all requirements and prerequisites for every node in the configuration.
After you configured the setup.xml and octane.yml configuration files in the first node, copy these file to all other cluster nodes.
Start ALM Octane on all servers.
See also Installation flow.
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 System requirements 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 C:\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 C:\octane\repo and on additional nodes defined as C:\server1\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. For details, see Prerequisites.
Install ALM Octane on the first cluster node
Install ALM Octane on the first cluster node, as described under Installation.
Here we deploy the ALM Octane installation files onto the first node.
We configure ALM Octane by modifying the setup.xml configuration file.
Make sure to set the following setting to values that all cluster nodes can access.
RepositoryFolder The shared repository that all cluster nodes can access (read and write).
We configure other ALM Octane cluster settings by modifying the octane.yml configuration file. After you modify the settings, run Update ALM Octane Settings from the Start menu or run the updatesettings.bat script. For details, see Update settings.
ALM Octane validates these settings when starting. If the validation fails, the ALM Octane server does not start.
Start the ALM Octane service.
Set up a secure configuration on the first cluster node
If you want to set up a secure configuration for ALM Octane, follow the instructions in knowledge base article KM02707977.
Make sure ALM Octane is running on the first node in the cluster
Before installing on remaining cluster nodes, log in to ALM Octane.
For details, see Log in to ALM Octane.
Only after you successfully log in, deploy ALM Octane installation files on each additional cluster node
Caution: Do not do the following:
Do not configure the setup.xml and octane.yml files. You will be copying these files from the first node in the cluster during the next step.
Configure each additional cluster node
Copy the C:\octane\conf\setup.xml and C:\octane\conf\octane.yml files from the first cluster node to the C:\octane\conf folder on the cluster node.
Start ALM Octane on each additional cluster node
Select Start > ALM Octane > Initialize ALM Octane Server on each cluster node.
Set up a secure configuration on each additional cluster node
If you want to set up a secure configuration for ALM Octane in a cluster configuration, follow these instructions on each additional cluster node: Software Self-solve knowledge base article KM02707977.
Make sure ALM Octane is running on each additional node in the cluster
For details, see Log in to ALM Octane. Use the load balancer URL when you log in.