Does anyone have a prioritization of the startup and shut down order of the CME objects.
We are trying to put together a document for the server team when they have to patch and reboot the servers.
I am thinking once we get the order done, we should have the service set to manual and start them from the SCI (Keeping the SCS set to auto start)
Thanks,
AJ
If you look in the “Framework 7.x Deployment Guide”, there is a chapter on “Starting and Stopping Framework Components”. It tells you for most of the applications which need to be started before starting each application.
IMO, you can use the component’s dependencies to determine the order. For example, if your URS depends on certain DB Servers, those should be started before the URS. If a component needs to register DNs, then the TServer should be started before that component. And so forth.
TOP TIP:
…once you have determined the startup and shutdown order, create them as a grouped Solution in SCI - you can put the stop and start order within the parameters there.
That way, you’ll save yourself a document or 2 as your support guys only have to hit “start” or “stop” on the Solution. They don’t have to be told what order they need to to be started or stopped in so they’ll probably manage to get it right… probably… 