The ServiceManager allows you to start, stop and access components such as the Automation Engine processes or agents from a central point.
You can specify the particular components in the file definitions file.SMD. For more information, see Setting Up an SMD File. The ServiceManager starts the programs in the background, grants access to particular properties and ends the program if necessary. It is available for Windows and UNIX.
You can establish a secure connection (TLS 1.2) with the ServiceManager but still support non secure connections to legacy ServiceManagers. For secure connections, you need to have CAPKI installed on the same computer in which you have installed the ServiceManager Service. For more information, see CAPKI - Securing the ServiceManager.
On Windows, install the ServiceManager program as a service. The Automation Engine components can then automatically start in the background during Windows system start-up without having to be entered as a service.
Select the start type Automatic in the service properties if the ServiceManager should be started together with Windows.
A ServiceManager must be available on the same computer as the components it uses. If the components are installed on different hosts, you must install a ServiceManager on each of these computers.
The ServiceManager can be controlled with the support of two programs. The ServiceManager Dialog Program and the ServiceManager CLI allow access to all components to be started by the ServiceManager. The administrator can also define and modify start conditions and login information with these programs. It is not necessary to run the dialog program and/or the command line program on the same computer on which the ServiceManager has been installed.
For more information, see ServiceManager - Dialog Program and ServiceManager - Command Line Program (CLI).
See also: