As there has been questions about controlling various parts of Mercury remotely from a batch file or a program I made a commandline version of the webtools package, available here:
The program can use the same command daemon as the webserver version (included in the zip archive), but will work without it as well. If running Mercury as a service under Windows Vista or later it's advisable to use the daemon or some functions will be unavailable.
Supported commands are:
To stop Mercury the command is "MercuryConsole exit"
To put Mercury offline: "MercuryConsole offline"
To put Mercury back online: "MercuryConsole online"
To pause Mercury core: "MercuryConsole pause"
To unpause Mercury core: "MercuryConsole unpause"
To pause a module, for instance MercuryS: "MercuryConsole pauseS"
To unpause MercuryS: "MercuryConsole unpauseS"
Depending on version of Mercury and Windows, if the command daemon is used, and if running in program mode or service mode, behavior will differ some. Please try it out in your environment so you know how it will work before using it in any automated routine.
The command daemon can only accept one connection at the time, so if you use it you can't run the web version and the commandline version at the same time.
To have the console window stay open until you press return (so you can read program output) add "debug" as a second parameter:
"MercuryConsole pause debug"