Service Dependencies
- Last UpdatedJun 06, 2024
- 1 minute read
The Client Service, Advanced Service, Workflow Engine, Task Scheduler, and Communication Service are inter-dependent. These dependencies will be considered for monitoring.
Dependencies
-
If the Client service is stopped on a machine, all other services in that machine are also stopped. Similarly, if the Client service is started on a machine, all other services in that machine are also started.
-
If a service crashes or is stopped manually, then its dependent services also must be stopped and restarted in a sequential manner.
-
Order of starting ad/or stopping the services: Communication Service, Task Scheduler, and WorkFlow Engine.
-
Advance service is present only in the load balanced environment. If the Advance service has to be stopped by the Client service, then stop the services in the following order: Advance Service, Communication Service, Task Scheduler, and Workflow Engine. Follow the same order while starting the services.
-
For the remaining services (CS, TS, and WF Engine), if any service is stopped, then all the services are restarted in an order. For example, if Task scheduler needs to be stopped by service monitoring, then Communication Service, Task Scheduler, and WorkFlow Engine are stopped. The service monitoring will start Communication Service, Task Scheduler, and Workflow Engine in an order.