In this step of the exe4j wizard, you define further options for Windows service executables. All options on this screen will only be enabled if the selected executable type in the executable step is "Service".
/install
to the
generated service executable. The default start mode of the service can be determined
in this step:
/install-demand
to the generated executable instead of
/install
.
/install-auto
to the generated executable instead of /install
.
/uninstall
to the
generated service executable. All command line switches also work with a prefixed dash
instead of a slash (like -uninstall
) or two prefixed dashes
(like --uninstall
).
To start or stop the service, the /start
, /stop
and /restart
options are available. In addition, a /status
argument
shows if the service is already running. The exit code of the status command is 0 when the service is running,
3 when it is not running and 1 when the state cannot be determined (for example when it is not installed).
As a second parameter after the /install
parameter, you can optionally pass
a service name. In that way you can
exe4j.launchName
for the service name. Note that
you also have to pass the same service name as the second parameter if you use the
/uninstall
, /start
and /stop
parameters.
/run
parameter. In that case, all output will be printed on the
console. If you want to keep the redirection settings, use the /run-redirect
parameter instead.
dependencies
text field.
You do not have to enter core OS services such as filesystem or network,
these services will always be initialized before your service is launched.
If you have dependencies on multiple services, you can enter a list of these service
names separated by commas.