Appendix C. Windows Service Configuration

This document describes the file configurations required for registering a Windows service.

The following is an example of a Windows service registration file for a service named 'jeus' (file is named using the service name).

<jeus.ini>

[jeus]
jeus.home=C:\TmaxSoft\JEUS7.0
jeus.description=JEUS7 Windows service
java.home=C:\Java\jdk1.6.0_41
java.vm.type=hotspot
java.vm.option=-server
jeus.nm.classpath=C:\TmaxSoft\JEUS7.0\lib\system\jeus-nodemanager.jar;
                  C:\TmaxSoft\JEUS7.0\lib\system\jeusapi.jar;
                  C:\TmaxSoft\JEUS7.0\lib\system\jeusutil.jar;
                  C:\TmaxSoft\JEUS7.0\lib\system\jeus-network.jar;
                  C:\TmaxSoft\JEUS7.0\lib\system\jmxremote.jar;
                  C:\TmaxSoft\JEUS7.0\lib\system\jeusjaxb.jar;
                  C:\TmaxSoft\JEUS7.0\lib\system\jmx-description.jar;
                  C:\TmaxSoft\JEUS7.0\lib\system\javaee.jar;
                  C:\TmaxSoft\JEUS7.0\lib\system\tmaxjce_jdk15x.jar;
                  C:\TmaxSoft\JEUS7.0\lib\system\commons-cli.jar
jeus.nm.boot.param=-domain jeus_domain -server adminServer
jeus.nm.down.param=-stopServer
shutdown.previous.nodemanager=true
-Xmx1024m

The following describes each configuration item.

ItemDescription
jeus.homeDirectory path where JEUS is installed.
jeus.descriptionDescription of the Windows service.
java.homeDirectory path where Java is installed.
java.vm.type

Option to use the Java HotSpot JVM.

Options are:

  • hotspot: Use the Java HotSpot JVM. This runs with the '-server' option of java.vm.option.

  • old: Do not use the Java HotSpot JVM. The 'vm' option is not included. Must be set to 'old' when the equipment does not support the 'vm' option.

java.vm.option

Options for using the Java HotSpot JVM.

Options are:

  • When the HotSpot JVM is used: -server

  • When the HotSpot JVM is not used: -Djeus.dispatcher.blocking=true

jeus.nm.classpathClasspath required when starting the node manager.
jeus.nm.boot.param

Additional options required when node manager starts along with a Windows service.

Currently, JEUS can be configured to start DAS when a Windows service starts. Domain and server names can also be configured.

e.g., -domain jeus_domain -server adminServer

If not set, only the node manager will start.

jeus.nm.down.param

Additional options required when a Windows service terminates.

Currently, JEUS can be configured to terminate when the Windows service terminates.

e.g., -stopServer

shutdown.previous.nodemanager

Option to terminate an already running JEUS before starting a Windows service.

If set to false, a Windows service cannot start while JEUS is running.