Integration Server 10.15 | Integration Server Administrator's Guide | Starting and Stopping the Server | Running Integration Server as a Windows Application vs a Windows Service
 
Running Integration Server as a Windows Application vs a Windows Service
 
Switching the Server from a Windows Service to a Windows Application
Switching the Server from a Windows Application to a Windows Service
Integration Server can run as either a Windows application or a Windows service.
*Use a Windows application if you want to control when the Integration Server initializes. When Integration Server is a Windows application, you must manually start it.
If you installed the Integration Server as a Windows service and now want it to be a Windows application, you can manually remove the Windows service for the Integration Server. After removing the Windows service, the Integration Server will still be available as a Windows application. See Switching the Server from a Windows Service to a Windows Application.
*Use a Windows service to have Integration Server automatically initialize when the machine on which it is installed initializes. When you use a Windows service, you do not have to manually restart Integration Server following a machine restart.
If you installed Integration Server as a Windows application and now want it to be a Windows service, you can manually register the Integration Server service.
See Switching the Server from a Windows Application to a Windows Service.
You can run multiple Integration Server instances as applications and multiple Integration Server instances as services on a single machine. For example, you can run two instances of Integration Server as an application and two instances of Integration Server as services on the same machine.
Note:Microservices Runtime cannot be registered as a Windows service. An Integration Server equipped with an Microservices Runtime license can be registered as a Windows service.