For logging on to a BOXI cluster, also know as @clustername, you need to have the clusters.properties file located on the webserver. By default this file is not there and needs to be created with e.g. notepad. The contents of the file is like below:
|cms.clusters=@cluster1, @cluster2, @cluster3
Save the file to ..\PlatformServices1.ear\PlatformServices.war\WEB-INF\classes directory on your webserver.
For JAVA webservers like Tomcat and Websphere you can also use the standard web.xml file, located at ..\PlatformServices1.ear\PlatformServices.war\WEB-INF, instead of the clusters.properties file. The clustering section of the file is like below:
- Sometimes the clusters.properties file is not recognized, forcing you to use the web.xml file and vice-versa.
- According to SAP, Lifecycle Manager (LCM), doesn't use a web.xml or clusters.properties for the clustering information. However logging on to a @cluster seems to work without any problems. In case it isn't working like the screenshot below. To get this working first logon to one of the servers which are member of the preferred cluster. E.g. enter server1.internaldomain.local:6400 in the System field in case you want to logon to @cluster1. The webserver than caches all the members of that @cluster in memory where after you are able to logon to the @cluster1. Unfortunately these cached servers are removed after each webserver restart!