Running the standalone server as a Windows service - continued

When running the server as a Windows service our recommendation is to use the internal utility JbsToService.exe in order to register the service.
The advantage of JbsToService.exe over standard 3rd party service registration utilities is that when stopping the service, standard utility programs will not stop all the java.exe processes comprising the server deployment. Therefore the user will either have to restart the machine or selectively stop the java.exe processes from the Windows Task Manager in order to completely stop the server.

On the contrary, when registering the service using JbsToService.exe, stopping the service from the services palette will issue a standard QUIT command to the server which will stop all the server java.exe processes and return the machine to a clean state so that the server can be started again immediately after performing some maintenance.

When using JbsToService.exe, starting the service will invoke the program JBSService.exe in the same folder. In turn JBSService.exe reads the first line in jacadasv.bat and invokes the resulting command. Therefore make sure that the first line in jacadasv.bat contains the java command line and not a comment line (and also make sure the -Xrs flag is being used - see previous post)

For more information about the JbsToService.exe utility take a look at the “Running the JIS Server as a Windows Service” in the Java and/or Xhtml manuals and also take a look at the product release notes at http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/jis/jis92/rln920.pdf paragraph “Simplifying JIS Windows Service Configuration” on page 58.