CMS Clustering

server administration XI Server Discussion
22

Doug,

I managed to re-name the cluster but what I ended up doing sounds slightly different to yours and also varies ever so slightly from Admin guide, so I’d just like to just run through what I carried out - might just a case of lost in translation:

Step 1 - Rename Cluster on one SIA via CCM (which then cascades to other SIAs) to @BO_Development.

Step 2 - Carry out the following on each web app in cluster:

Edit web.xml in C:\Program Files\Business Objects\Tomcat55\webapps\InfoViewApp\WEB-INF\ and added the following:

    <context-param>
        <param-name>cms.default</param-name>
        <param-value>@BO_Development:6400</param-value>
    </context-param>

Edit web.xml in C:\Program Files\Business Objects\Tomcat55\webapps\PlatformServices\WEB-INF and added the following:

    <context-param> 
        <param-name>cms.default</param-name> 
        <param-value>@BO_Development</param-value> 
    </context-param>

Step 3 - Restart App Servers (in my case Tomcat)

At this stage the cluster is up and running for CMC and Infoview.

Notice I haven’t needed to actually define in any XML files what nodes make up the CMS Cluster.

Step 4 - To close loop with any thick clients referencing cluster (ie Universe Designer) make registry changes to local machine. Refer to this thread for specific details on this (although there is a bug with XI 3.x).

Cannot access the repository (USR0013)

I guess I’m a bit worried that whilst everything seems to work it’s still not 100% correct. :expressionless:

The Emu :australia: (BOB member since 2002-09-13)