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::Client::Deployment using Java Web Start

I suppose that the most advanced and convenient way to deploy and start Internal Chat Client is to use Java Web Start.

The only thing you need to have on client computers is JRE. The rest will be done by Java Web Start.

Starting from version 5.6.0 Internal Chat Server serves specific JNLP-file which is recommended to be used for deployment.

1. Install and run Internal Chat Server. Suppose it is configured to listen on host intchat.mydomain, port 6556, SSL is enabled (i.e. it uses HTTPS, not HTTP).

2. Make sure that JRE is installed on client computers.

3. Using your favourite browser on client computer load the following URL:

   https://intchat.mydomain:6556/webstart/IntChatClient.jnlp
   

   I.e. we just ask our Internal Chat Server for page webstart/IntChatClient.jnlp.

4. Usually Java Web Start must start automatically because JNLP is its filetype. If not, check MIME database in your system.

5. First time Java Web Start downloads the client JAR from Internal Chat Server, then asks you if you trust to this file, signed by Andrew Orlov, i.e., by me (it is the Java security requirement - in order to run all the JAR-files downloaded from the Internet using Java Web Start must be signed by trusted issuer). Say YES, otherwise client could not be run.

   Next times if client is not changed, Java Web Start will not download client package.

6. Use client as usual.

Background

Client package is kept on server in subfolder webstart. If new version of Internal Chat Client is released, just change the client package to the new one and Java Web Start will renew it on client computers automatically (of course if you run the client using JNLP URL above). In this case Internal Chat Server works as common HTTP server, serving some static content.

(C) 2007-2011 Andrew Orlov