Service Management System
The AS Java service management system is responsible for resolving references between components and providing a set of properties for setting load, stop, and event timeouts.
The basic module of the service management system is the Service Manager, which acts as a container in which all services in the AS Java cluster work. Using the functions of other runtime subsystems, it manages the lifecycle of AS Java system components - interfaces, libraries and services. The Service Manager loads and starts the components when the AS Java is started, manages components at runtime, and stops them when the AS Java is stopped.
The process of starting (loading) the AS Java system components is strictly defined. The Service Manager performs the following steps:
-
Reads the components persistent data from the database.
-
Resolves components for which the previous steps are successfully completed.
-
Checks whether all core components are resolved. If not, the Service Manager stops the whole system.
-
Creates the class loaders of the components and loads them.
-
Starts service components.
-
Performs a check whether all core service components are started. If not, the Service Manager stops all started components, unloads them and stops the whole system.
The service management system also provides states for starting AS Java service depending on the configuration template. More information: Zero Administration .
You can configure load and stop timeouts in case of startup and shutdown problems. More information: