Right now I am starting BaseX on my Windows developer machine with the command "basexserver -S" so that it's started as a service. Our admin preferred however to use a Java Service Wrapper (he uses YAJSW) because it gives him more options/monitoring and better control on restarts. I think that java service wrappers are a little to comprehensive. Maybe on Windows it's more convenient to let BaseX install as a windows service similar to the way that Jenkins does: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+...
Raymond,
thanks for the hint. Maybe we'll encounter some problems if we want to support all recent Windows platforms?.. If you find some time to try this out, your feedback is very welcome.
Christian ___________________________
On Wed, Oct 24, 2012 at 3:55 PM, Raymond Meester raymondmeester@gmail.com wrote:
Right now I am starting BaseX on my Windows developer machine with the command "basexserver -S" so that it's started as a service. Our admin preferred however to use a Java Service Wrapper (he uses YAJSW) because it gives him more options/monitoring and better control on restarts. I think that java service wrappers are a little to comprehensive. Maybe on Windows it's more convenient to let BaseX install as a windows service similar to the way that Jenkins does: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+...
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
I wonder how Jenkins does it.. By the way for starting the BaseX server at startup I created a scheduled task like this:
C:>schtasks /create /tn "BaseX Server" /tr "'C:\Program Files (x86)\BaseX\bin\basexserver.bat' -S" /sc ONSTART /ru system
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Raymond Meester