Internal Chat

Multiplatform Enterprise Instant Messaging.
Smart. Powerful. Extendable.

[an error occurred while processing this directive]
• Home
[an error occurred while processing this directive]
• History
[an error occurred while processing this directive]
• Features
[an error occurred while processing this directive]
• Screenshots
[an error occurred while processing this directive]
• System requirements
  • Server
  • Client
[an error occurred while processing this directive]
• Installation
  [an error occurred while processing this directive]
  • Database
  [an error occurred while processing this directive]
  • Server
    [an error occurred while processing this directive]
    • Windows service
    [an error occurred while processing this directive]
    • *NIX daemon
    [an error occurred while processing this directive]
    • Enabling SSL
  [an error occurred while processing this directive]
  • Client
    [an error occurred while processing this directive]
    • Client deployment using Java Web Start
[an error occurred while processing this directive]
• Upgrade
  • Server (minor upgrade)
  • Client (minor upgrade)
  [an error occurred while processing this directive]
  • Major server upgrade from 5.5/5.6 to 5.7
[an error occurred while processing this directive]
• Known issues
[an error occurred while processing this directive]
• Download
• Forums
[an error occurred while processing this directive]
• Acknowledgements

Installation::Server::Windows service

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:

1. Make steps 1 and 2 described earlier.

2. Change current directory to FOLDER\IntChatServer-X.Y.Z\bin and run IntstallIntChatServer-NT.bat. New service (named IntChatService) will be created.

3. Change current directory to FOLDER\IntChatServer-X.Y.Z\conf and edit the following configuration files:

   • Server.xml. See step 4 here for details.
   • wrapper.conf. Correct path to java.exe in wrapper.java.command parameter and possibly (NOT RECOMMENDED, but if you have not server JVM you must do it!) remove "-server" from wrapper.java.additional.1. In addition, you can set some other parameters if you need (for example, Maximum Java Heap Size etc.).

4. Go to Control Panel -> Administrative Tools -> Services and start the service "Internal Chat Server" (or run from the command prompt "net start IntChatService"). Your server must be started.

5. If you have any problems, review logs in FOLDER\IntChatServer-X.Y.Z\logs.

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.

1. Create a user-defined service (we will call it IntChatService):

   >instsrv IntChatService PATH_TO_SRVANY_EXE\srvany.exe
   

2. Run Registry Editor (Regedt32.exe) and locate the following subkey:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntChatService
   

3. From the Edit menu, click Add Key. Type the following and click OK:

   Key Name: Parameters
   Class: leave blank
   

4. Select the Parameters key.

5. From the Edit menu, click Add Value. Type the following and click OK:

   Value Name: Application
   Data Type: REG_SZ
   String: FOLDER\run.cmd
   

   (remember that FOLDER is the place where we unpacked IntChatServer-X.Y.Z.zip)

6. Close Registry Editor

7. Now you can run IntChatService as a common Windows service, either from the command line or from the Services applet.

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