Differences

This shows you the differences between two versions of the page.

--- rundevicesdeploymentsasaservice [2022/09/22 22:25]
wikiadmin [TransSECS Deployment Service]
+++ rundevicesdeploymentsasaservice [2022/09/22 22:40] (current)
wikiadmin
@@ Line 33: / Line 33: @@
 Note: the default minimal configuration uses a %BASE% variable which could be defined instead of entering the full path to the application to run.
+. Install the Service
+To install the service, open a command shell where you have just edited the GEMTool.xml (in the GEMTool project deployment directory), and enter this command:
+<code>
+GEMTool install
+</code>
+<note important>Note: Be sure that you do not have the GEMTool (or your project deployment) running before you start the service. You cannot have two deployments using the same port running at the same time.</note>
+. Open the Windows services console. You will see a GEMTool service listed. By default it is set to "Automatic" which means it will start when the computer starts.  You can start it by selecting "Start". It will then change to status "Running".
+You can stop/start/restart the service from this services console, or you can enter commands in the Windows command shell to do these functions. In the command shell you can also uninstall the service and stop or start it.
+To get the full list of options for the service type "GEMTool -h" into the Windows command shell.
+Examples:
+<code>
+GEMTool uninstall
+</code>
+<code>
+GEMTool stop
+</code>
+. Logging
+The service will log just as the deployment which is started from the "run.bat" would log, i.e., SECSMessages.log. There are two additional logs, GEMTool.err.log and GEMTool.out.log. These will contain runtime errors and information from stderr and stdout printouts from the application, if any.