ALM Octane 12.60 installation - Repository

[Ravi4it]

Hi All,

We are deploying ALM Octane 12.60 enterpise edition. 

We have 6 servers (2 for ALM Octane, 3 for Elastic Search, 1 for Jenkins - CI ).
In addition, we already using ALM server (1), Performance Center Server (1), PC Host server & Load Generators 

Unfortunately, we dont have any server for Shared repository for ALM Octane. 
As per the ALM Octane Installation guide, we need 1 server for  ALM Octane repository (shared)

I am looking for ideas, if the respository can be located in any of the exisiting servers or do i need a dedicated server for shared repository. Currently, we are very much new to ALM Octane, i guess the usage will not be very high initially.

Thanks

[Ziv_Birer]

Hi,

The repository can be on one of the octane servers and shared on the netowrk.

IMPORTANT: the repository location is written in setup.xml file. You must use the same folder path in both octane nodes. So you need to write the same shared path description in both files.

Regards

Ziv

[Ravi4it]

Many thanks for the reply Ziv_Birer

I have 2 servers for ALM Octane which i am planning top use primary node and secondary node and configure them as cluster.

As per the ALM Octane installation guide or online help for cluster configuration, it states not to have the Repo on the first server node.

"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.

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

Does it mean, i can have the repository on the secondary node but not in the installation folder. Kindly correct me. Can i have the shared repository for cluster in the secondary node different from the installation folder

Thanks

[Ziv_Birer · Accepted solution]

Hi,

The guide means that you should not define the repository as local folder in setup.xml (for cluster configuration) .

If you write 'C:\server....' it means that the path is local. 

The reason for this guideline is that setup.xml of both nodes must be the same. If you define repository in node 1 as 'C:\server..' than on second node it can't also be 'C:\server....' because the repository is on first node,

You can define repository on machine 1 or 2, share it (like \\node1\repo) and write it's location in both setup.xml using the shared location notation (for example \\node1\repo).

So:

1. You can define the repository on first node (or second node).

2. When you have cluster, it is not recommended to keep it in installation folder of one of the nodes. It should be on different folder in one the machines.

Regards,

Ziv

[Ziv_Birer · Accepted solution]

The guide means that you should not define the repository as local folder in setup.xml (for cluster configuration) .

If you write 'C:\server....' it means that the path is local. 

The reason for this guideline is that setup.xml of both nodes must be the same. If you define repository in node 1 as 'C:\server..' than on second node it can't also be 'C:\server....' because the repository is on first node,

You can define repository on machine 1 or 2, share it (like \\node1\repo) and write it's location in both setup.xml using the shared location notation (for example \\node1\repo).

So:

1. You can define the repository on first node (or second node).

2. When you have cluster, it is not recommended to keep it in installation folder of one of the nodes. It should be on different folder in one the machines.

Regards,

Ziv

[Ravi4it]

Many thanks.