Previous versions of Elixir Repertoire Server included the tanuki windows service wrapper. 

For your convenience, this wrapper is still provided, but has been moved to 
the tanuki-windows-service directory. Please see the instructions there on how it
can be configured.

This release of Repertoire Server includes a new service mechanism based on running
Elixir Repertoire Service.exe or Elixir Repertoire Service(64).exe. If your machine
is running a 64-bit JVM, then choose the (64) version of the .exe. In the following
instructions we will assume the 64 bit version.

Critical Steps
--------------

In order to run Elixir Repertoire Server as a windows service, you need to copy your
server licence file into the RepertoireServer\ext directory. If the licence file is
not found in this directory, the service will not start.

The .vmoptions files corresponding to each .exe include Java command line configurations.
By default the memory usage limit is set to 512MB, if you are generating complex reports with a
lot of data you should probably increase this limit.

It is recommended that you launch the server directly first of all - not as
a service - so that any issues can be easily identified. Once the server runs
and you can connect via http://localhost:8080/ then you can shutdown the server
and follow the description below to set up the tool to run as a service. 

Operation
---------

To operate the service, you need to open a command line prompt and change to
the RepertoireServer\bin directory. Then:

"Elixir Repertoire Service(64).exe" /install

will install the service, you only need to do this once. The service will be
in the stopped state by default. To start the service after installation:

"Elixir Repertoire Service(64).exe" /start

Similarly, /stop and /uninstall will reverse these operations and
/status will tell you whether the service is currently running.

Once installed you can also control the service from the windows control panel 
- for example to have the service start automatically when the machine starts.

For troubleshooting, there are two files: RepertoireServiceOut.txt and
RepertoireServiceErr.txt - these contain the contents that would be written 
to the console, except a service has no console. These files will be located in
the same directory as the .exe files (bin). If you are unable to connect
to the server with your browser (eg. at http://localhost:8080/) then please
check the contents of these files for likely causes. Note that the first time
the server runs, it will start slower because it needs to create the initial
database configuration.

Note: make sure you stop the service and uninstall it using the commands above 
before attempting to upgrade the server.
