Multiplatform Enterprise Instant Messaging.
There are two ways to start Internal Chat Server under Windows as a service.
The way #1
It is recommended way, based on great Java Service Wrapper from Tanuki Software. Theoretically may lead to some issues on x64 platforms because Community Edition of wrapper is not released for Windows x64, but I haven't met them myself. To make it work do the following:
Useful tip. I suppose that it is more flexible to run the service under some specific user account rather than SYSTEM account. So I recommend to change this setting for the service.
The way #2
Follow this way only if you have problems with the way #1. On Windows you can use well-known resource kit tools instsrv.exe and srvany.exe (the last one allows to run any executable as Windows service), see http://support.microsoft.com/kb/137890 for more info. As an executable to run in background we will use run.cmd, tuned earlier.
Note. There is a problem to STOP the service, created this way. If you tell the service to stop, it will stop only the "Windows half" of the service. The Java-process will continue to run. You will need to kill it explicitly from the Task Manager, so it is important to make the process run not under the SYSTEM account, but under some user (for example, Administrator) account. The process owner can be set via the Services applet, through IntChatService properties, Log On tab.
(C) 2007-2011 Andrew Orlov