...

When running the Servoy Application Server and the database on the same Windows machine, both as a Windows Service, then a dependency can be configured between the different Windows services. See #Configuring Configuring Windows Service dependencies for more info.

In this Chapter

Supported platforms

The Java Service Wrapper used by Servoy supports virtually all platforms on which a Java Virtual Machine is available (also required to run the Servoy Application Server).

The Java service Wrapper component will create a Windows Service on the Windows platform and on other platforms it utilized Unix Daemons.

Installation

The Java Service Wrapper is by default installed by the Servoy All-In-One installer when installing a Servoy Application Server (see Running the All-In-One Installer for more info on the All-In-One installer).

...

The Service component installation comes with two files to install and uninstall the Service: install_service.[bat/sh] and uninstall_service.[bat/sh]. 

Additional configuration

The configuration of the Java Service Wrapper is done through the file wrapper.conf located in ../application_server/service.

 When changing the value of any any wrapper.ntservice.* property on Windows, the Service needs to be uninstalled first and reinstalled after the changes have been made.

Configuring the Windows Service to automatically start on reboot of the machine

By default the Windows Service is configured to be started manually. This can be changed by setting the wrapper.ntservice.starttype property to AUTO_START.

Configuring Windows Service dependencies

The Java Service Wrapper does NOT start the database, as in production environments the database could be installed on a different machine or is maintained by a DBA.

If the database is running on the same machine as a Windows Service as well, it is possible to configure a dependency to it in the Java Service Wrapper configuration. The dependency can be set by adding the name of the Windows Service for the database on which the Servoy Application Service depends as a the wrapper.ntservice.dependency.x property. The "x" at the end of the property name needs to be a sequential number, starting with 1, for each dependency.

Memory Setting

When the Servoy Application server is started as a service through the Java Service Wrapper, the assignment of memory goes through the configuration of the wrapper in wrapper.conf, instead of through servoy_server[bat/sh].

...

For more information on the the meaning of these settings and their suggested values, see Memory Management.

Running multiple Servoy Application Servers as a Service on a single machine 

When running multiple Servoy Application Servers as a Service on a single machine, some configuration adjustments are required to not let the different services influence eachother.

...

The wrapper.port value does not have to be unique, because the Java Service Wrapper automatically looks for a free port if the specified port is already taken.

Additional configurations

The Java Service Wrapper has extensive configuration options. The most fundamental settings have been discussed in this chapter already. In this paragraph some more advanced settings are detailed.

...

wrapper.filter.trigger.1=Exception in thread "*" java.lang.OutOfMemoryError
wrapper.filter.action.1=NONE

wrapper.filter.trigger.2=Exception in thread "*" java.lang.OutOfMemoryError
wrapper.filter.allow_wildcards.2=TRUE
wrapper.filter.action.2=DUMP,RESTART
wrapper.filter.message.2=The JVM has run out of memory.

More info on the Java Service Wrapper component

The Java Service Wrapper is a bundled third party component also called Java Service Wrapper Standard by Tanuki Software. For indepth documentation have a look here.

...