To do so, open the "Services" app (e.g., using the Windows search). Right-click the respective service entry to open the context menu for it and click "Properties". In the properties dialog, there is a tab "Recovery" where you can configure what to do in case of an unexpected shutdown.
== Logging ==
Especially for complex interfacing tasks, good logging is paramount.
Log entries are really your best way to find out what happens during the execution of an Enterprise Service task. They are also much more versatile than any UI we could provide. So even though it looks cumbersome, logs can help you a lot after you get used to them!
Our best practice recommendation is:
* In the custom code executed by the Enterprise Service, do very detailed logging in critical places (e.g., conditional actions depending on runtime input), especially for exceptional cases (missing or unexpected parameters).
* This detailed logging can be done with log level "Verbose". This way, you can switch it on and off on demand, for debugging - without filling the hard disk with irrelevant logs in production.
* For every log entry, create a randomly generated large number for finding the correct place in the code later. The random number helps you avoiding to maintain an incremental log ID list.
[[Category:Enterprise service|Install UBIK Enterprise Service]]
[[Category:How-To|Install UBIK Enterprise Service]]
[[Category:Installing|Install UBIK Enterprise Service]]
