Self-Solve Knowledge Search

Minimize Maximize
Essential things when installing ALM on a cluster environment1. To work with clu...
This document has not been formally reviewed for accuracy and is provided as is
Title :
Essential things when installing ALM on a cluster environment1. To work with cluster nodes, make sure that all nodes have access to the file repository path and that the path is UNC. All nodes in the cluster must have the same repository path.when installing ALM on a cluster environment
Document ID :
KM01178295
Product - Version:
quality center 12.00 ;
OS :
Windows
Updated :
Wed Sep 24 06:38:45 GMT 2014
Summary :
Essential things when installing ALM on a cluster environment
Solution

There are few things we need to check when installing ALM on a cluster environment:

1. To work with cluster nodes, make sure that all nodes have access to the file repository path and that the path is UNC. All nodes in the cluster must have the same repository path.
2. If the file repository is located on a remote machine:
- On the file server machine, share the file repository directory so that the user running the installation is the owner of the files.
- Clustering. On the ALM machine, or on each cluster node, create a mount directory that points to the file repository directory.
3. It is important that you enter the repository path using the exact same characters on all nodes. For example, you cannot have the path on the first server node defined as C:\alm\repository and on additional nodes defined as \\server1\alm\repository . Rather the \\server1\alm\repository path
must appear on every node.
4. All nodes must have access to the database server on which the Site Administration database schema resides.
5. All nodes must have access to all database servers.
6. Connect to existing schema / second node option when installing 2nd node.
7. If you are installing ALM on a cluster, you must use the same passphrase for all nodes.
8. If you are installing ALM on a secondary node of a cluster, some of the dialog boxes described in this configuration procedure are needed only for the primary node and are not displayed if you are installing a secondary node.