Central Management Server (CMS) is the heart of Business Objects. We cannot disable CMS by any means. However, we can stop it.
In a standalone environment, if we disable CMS [it's not possible though :)], we'll not be able to login to the system to enable it again, either through CCM / CMC.
If we stop the CMS server in a clustered system, all the sessions will be redirected / transferred to another CMS. Once we stop the CMS, it will not accept any new request even if it is enabled. It also serves as a name server with which all other servers / services in the cluster register.
We can disable every other server in BO but CMS.
There are times when it would be nice to disable a CMS, though. For instance we have a cluster of three servers and we have a home grown web service (uses the SDK) that triggers custom events. For some reason when it logs into the CMS on *one* of these three servers, it Windows AD authentication becomes disabled for the entire system. The other two are fine. Why? Dunno. But, because the web service was written with the R2 SDK and we are now on R3, we won't pursue it with SAP/BO until we have it rewritten with the R3 SDK. It's taking some time to get our developers on this task and in the mean time, it would be nice to disable that one CMS. As it is, we have it stopped and have to make sure all of our admins remember to keep it that way, especially after reboots, SIA restarts and the like.
ReplyDeleteWhy not just delete it? You have at least two other redundant CMS services. You don't need three.
ReplyDeleteThe insightful explanation on why disabling the CMS server is not advisable is enlightening. How Play Games Your clarity on the potential repercussions and dependencies involved showcases.
ReplyDelete