I am trying to get another VMware Linux server within my test environment. I currently have 1 environment up and running, and looking to deploy another XI3.1 enviroment on Linux using oracle db, looking to find some documentation on how to cluster with existing cms and audit database that is currently running. Setup in server1 when running initial install, I provided an SIA name of SIA, and cms name is equal to servername:6400. When running the 2nd install on server 2, what is the naming conventions for SIA, should it remain SIA, or call is SIA2 on server two, and cms naming, should it be servername2:6400. I have reviewed the admin guide, but still want to verify I have setup correct. Please if anyone has some documentation to help me with the setup please let me know, or send to my email robert.hicks@erieinsurance.com
Running cmsdbsetup.sh on server here are the details.
Stops - SIA
Lists current CMS Data Source- CMSDB
Current Cluster Name- DEVCMS
Current Audit- Audit DB name.
When running same on server2-
Stops SIA and lists same as server1.
I’m from the Windows side, but I assume the requirements and restrictions are the same. The key to clustering is the SIAs and the CMSs is that each should be installed with unique port numbers. Thus, on one server my SIA runs on 6410 and the CMS runs on 6400. The second server’s SIA runs on 6412 and the CMS 6402. If you attempt to have them on the same port, you will be unable to cluster the nodes. Indeed give the SIA a unique name, so you can keep track of what CMS is attached to what SIA. On windows the SIA takes on the name of the server itself. Good luck!
That’s twice I’ve seen that same advice, and I don’t know if I buy it - ports need only be unique on a box.
Your clustering is controlled by your CMS / SIA being able to contact a common repository; you should be able to use the same ports as long as you’re talking about different physical servers. Server 1 SIA connection 1 is never going to interfere with Server 2 SIA connection 1, regardless of port.
You can instlal SIAs on 1 box - that would require different ports, but I’m sure my last configuration had multiple servers (5) all using the defaults of 6400 and 6410. They all hit the same CMS repository, all got registered with their unique node names, and then they spun up as part of the cluster (after “discovering” the other agents). I modified my Web.xml to reference the 2 CMS servers, but they were both on 6400.
The only time I’ve ever had port conflicts is when I’ve tried to force ports on a box to get past a firewall. Anyone else back me up here?
Everyone’s experience is different. My advice is based on what I saw during DEV when we where standing up a clustered XI3.1 .Net install. I also used recommendations from a White paper, “Upgrading BI applications from XI Release 2 to XI 3.0: A Live Experience” found on SAP.com. You are right the port conflict comes into play if you are installing multiple CMSs on the same server, I should have clarified that with the OP. Truthfully, I did try installing the second CMS on a separate server using port 6400 and indeed ran into issues when installing it into the first node (SIA). I don’t know if it was a .Net issue or not. I was under the gun to get the solution out the door, thus I utilized the recommendations in the above study. This paper recommended to “distinguish” the ports by using a different port number for the second CMS/SIA (on the second server) which is what I did. I decided on this route and never looked back. The OP can take my advice/recommendation or simply ignore. What you say is indeed true, but having CMSs and SIAs on unique port numbers, while not required, can be done. We have been running this cluster with these unique port numbers for over a year and a half without issue. Remember there are many ways to skin the cat.
Thanks to you both for provided me some information. I went with my gut and named SIA’s, SIA01 and server1 and SIA02 and server 2, ports 6410 and 6510’s, and CMS kept as server name and running server1 on port 6400 and server2 on port 6500, I had to go into web.xml within tomcat/infoviewapp and edit the cms port #. So far so good. ready to start the import from the XI2 environments.
(BOB member since 2002-08-29)