Fast shutdown by file "force_stop"

If you want to force the Integration Server to stop running jobs immediately and mark them as crashed jobs, you can put a file with the name force_stop in the installation directory of the Integration Server before the stop. The file may be empty (size 0 kB).

As soon as the shutdown is initiated, this file is deleted.

To ensure that this file is created automatically each time the Integration Server is started, you can set the property "createForceStopFile" to "true" in the configuration file ./etc/startup.xml. Then each stop is going to be a fast shutdown.

<Call name="addApplication">
	<Arg>
		<New class="com.ebd.hub.datawizard.app.DataWizardSetup">
			<Call name="setConfiguration">
				<Arg>
					<New class="com.ebd.hub.datawizard.app.DataWizard">
						...
						<Set name="createForceStopFile">true</Set>
						...
						<Set name="createCleanStopFile">true</Set>
						...
					</New>
				</Arg>
			</Call>
		</New>
	</Arg>
</Call>

Note: There is also the possibility to trigger a force stop via HTTP.

File "clean_stop"

If the "createCleanStopFile" property is set to "true" in the configuration file ./etc/startup.xml, a file named "clean_stop" is created in the installation directory of the Integration Server as soon as the server process has terminated.

When the Integration Server is restarted, an existing "clean_stop" file is deleted. This feature can be used to evaluate the status of the Integration Server through external applications or scripts.

Automatically terminate an incompletely started Integration Server or Lobster Integration

If there are errors in the XML configuration files, or if a required port is already occupied by another process, it is possible that the Integration Server or Lobster Integration does not start completely. In that case, depending on the operating system and startup type, error messages will either appear in input prompt or in the files ./logs/wrapper.log or ./hub.txt. In order to ensure that the entire Integration Server is automatically stopped in case of such an error, the "stopServer" property must be set to "true" in the configuration file ./etc/startup.xml file.

<Call name="addApplication">
	<Arg>
		<New class="com.ebd.hub.datawizard.app.DataWizardSetup">
			<Set name="stopServer">true</Set>
			<Call name="setConfiguration">
				<Arg>
					<New class="com.ebd.hub.datawizard.app.DataWizard">
					...
					</New>
				</Arg>
			</Call>
		</New>
	</Arg>
</Call>

Note: The property "stopServer" is expected in the context of class "DataWizardSetup" and not in the context of class "DataWizard".