These instructions are good and basically work. In a strict Microsoft deployment environment using WOStart is probably better then FireDamon or other Java wrappers.
The way to install WOStart is to rename the executable wotaskd.exe and Javamonitor.exe and place it in the same directory as each their UNIX or Windows shell scripts.
To install wotaskd as a service (you have to run Windows PowerShell as Administrator):
Unknown macro: noformat. Click on this message for details.
The [noformat] macro is not in the list of registered macros. Verify the spelling or contact your administrator.
You can repeat the same for JavaMonitor. I edited the Properties file for JavaMonitor to set the port.
These instructions are good and basically work. In a strict Microsoft deployment environment using WOStart is probably better then FireDamon or other Java wrappers.
The way to install WOStart is to rename the executable wotaskd.exe and Javamonitor.exe and place it in the same directory as each their UNIX or Windows shell scripts.
To install wotaskd as a service (you have to run Windows PowerShell as Administrator):
Unknown macro: noformat. Click on this message for details.
The [noformat] macro is not in the list of registered macros. Verify the spelling or contact your administrator.
You can repeat the same for JavaMonitor. I edited the Properties file for JavaMonitor to set the port.
Precompiled WOStart.exe for Windows 32 and 64 bit with JRE8, produced by Markus Stoll: