BOXI R3 CCM MSCS aware?

[Former Member]

Hi Guys,

May be this is a dumb question, but we had an BO Enterprise Installation on a Windows 2003 Cluster. Now our BI Admins update BO to R3 and with this release the way to start and stop the BO services had changed:

example:

"C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\ccm.exe" -managedstop machine1.WebIntelligenceProcessingServer -cms machine1:6500 -username SysAdmin -password 35%bC5@5 <mailto:35%bC5@5> -authentication secLDAP

Now the BI guys ask me how we implement this in the cluster, that this works with the MSCS.

Any hints?

regards

Timo

[Former Member]

Hello,

Do we need to follow this for restart of BO ?

I do not see ccm.sh after the fresh install of 3.1 on Unix

its strange for me no bin directory and no ccm.sh, uninstall.sh ccmdbsetup.sh scripts are available.

Please advice if you are aware.

Regards,

Neo

[Former Member]

Hi Neo,

Sorry i don't know. We operates BO on a Windows enviroment!

[Former Member]

Did your administrators want to stop all servers or an individual server?

If you want to stop all servers, you can just shut down the SIA (Server Intelligence Agent) to stop all the servers.

[Former Member]

Hi Ka-Lok

What we need is a classical "failover" ability with the mscs.So if we move the cluster from one node to the other:

Stop the services on node 1 and start the services on node 2.

standard movement...

regards

Timo