AnsweredAssumed Answered

What is the best Practice to set-up the Clarity Services Start-up condition

Question asked by shalinee on Sep 10, 2012
Latest reply on Sep 11, 2012 by shalinee
Looking for some suggestions for --- What is the best Practice to set-up the Clarity Services Start-up condition. Specially when maintenance activities are getting schedule on Clarity Server in every month.

We are on CA Clarity 12.0.4 with Tomcat Web-Server and Load Balancing mechanism with two Application Servers.

In SERVER1 we have the following services

1- NSA
2-BG
3-APP
4-APP2 (XOG)
5-APP4 (Via SSO users are using this instance)
6-APP5(Via SSO users are using this instance)
7-NO Becon


In SERVER2 we have the following services

1- NSA
2-APP
3-APP3 (Via SSO users are using this instance)
4-APP4(Via SSO users are using this instance)
5-NO BG,APP2,BECON

In present scenario at customer side they are following the manual practice like-

-> whenever any maintenance activity had planned customer is doing the manual step (via command prompt) to bringing down the services and later bringing up these services. This is little pain when any activity has scheduled on long weekend/Holidays etc.

->Now We are planning to automate it so we put all the above services start-up condition auto-start in Services.msc wizard. This means whenever the machine reboot will happen this will stop all the services and bring up automatically.

Is there any possibility of issues/errors without proper bringing down the services before server reboot and later bringing up them manually(via command prompt)?

How does the start-up order of each service work. For Example, we usually type, Niku start nsa bg app app2 app4 app5 via command prompt to start the services on Server 1 and Niku start nsa app app3 app4 on Server 2.

Thanks,
Shalinee

Outcomes