Share this page

# Cluster installation flow

This section provides end-to-end instructions for installing an on-premises OpenText Software Delivery Management server in a cluster configuration. 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 in a cluster configuration:

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

   Area | Instructions
   --- | ---
   Check requirements | Verify that the all cluster nodes, including the first, meet all requirements and prerequisites. For details, see 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. 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. Linux only: Create an environment variable OCTANE_REPOSITORY_DIR. If this variable is missing, the installation will fail.
   Check access between nodes | All nodes must have access to each other. Verify ports are open in your firewall. OpenText Software Delivery Management 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 OpenText Software Delivery Management on the first cluster node. For details, see Installation.

   1. Deploy the installation files onto the first node.

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

      - Make sure to set the database server name to a value that all cluster nodes can access.

      - Enter values described in Cluster settings.

        These settings are validated when starting. If they are not valid, the OpenText Software Delivery Management server does not start.

   3. On the first node only, start the OpenText Software Delivery Management server. See Start the server.

3. (Optional) If you want to set up a secure configuration, follow the instructions in OpenText Software Delivery Management Secure Deployment and Configuration Guidelines.

4. Log in to the first node in the cluster. See Log in.

5. Download and deploy the OpenText Software Delivery Management package on each cluster node. See Deployment.

   Caution: Do not configure octane.conf or other configuration files on the nodes. Each node is automatically configured using the configuration files located in the repository, as defined when you configured the first node.

   Linux: Do not run connectnode.sh scripts.

6. On each node, start the OpenText Software Delivery Management server. See Start the server.

   Each node is automatically configured using the configuration files located in the repository, as defined when you configured the first node.

7. (Optional) If you want to set up a secure configuration for OpenText Software Delivery Management in a cluster configuration, follow these instructions on each other node: OpenText Software Delivery Management Secure Deployment and Configuration Guidelines.

8. Log in to make sure OpenText Software Delivery Management is running on each other node. See Log in.

   Use the load balancer URL when you log in.

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

9. If you need to make changes in configuration settings later, edit the octane.conf file in the <Repository folder>\conf directory. Watch out that you don't configure the octane.conf.new file, which is a temporary file that is for internal use only.

   After modifying these settings, restart the OpenText Software Delivery Management server on each node to pull the configuration changes from the repository.

### Troubleshooting

If the cluster was not properly defined, you may receive an error message when you start the OpenText Software Delivery Management server:
`Cluster is unhealthy...`

During installation, values in the hazelcast.xml file change according to the octane.conf configuration. The configuration of the hazelcast.xml file is the one that controls the cluster behavior.

Make sure that the member element of the hazelcast.xml file contains the same values that were defined in the nodes section of the octane.conf file.

https://admhelp.microfocus.com Software Delivery Management 8942
Tips to improve your search results... OpenText™ Software Delivery Management Help Center OpenText™ Software Delivery Management Help 26.3 All View Local Help Center View Online Help Center Version: