Internal Chat

Multiplatform Enterprise Instant Messaging.
Smart. Powerful. Extendable.


Upgrade::Major server upgrade from 5.5/5.6 to 5.7.

If you use previous version of Internal Chat (5.5 or 5.6 branches, which are nearly compatible) and want to upgrade to 5.7 then some specific actions should be done. It is due to the significant inner changes in server logic and database structure.

For example, since 5.7 all the files sent are kept in database rather then filesystem.

In order to convert your server to 5.7, do the following:

  1. Stop Internal Chat Server.

  2. !!!Make full database backup and server folder backup!!!

  3. Download the latest 5.7 server (IntChatServer-5.7.Z.zip) package.

  4. Perform the minor server upgrade without starting of the server (i.e. just overwrite old JARs with the new ones).

  5. Open command line, change directory to your server folder and run the following command:

    java --dbconvert -jar IntChatServer.jar
    

    Command line argument --dbconvert will show to server that you want to upgrade your database structure.

    Pay your attention that conversion is VERY time-consuming operation!

    For example, conversion of database with about 4 million messages inside can take from 6 to 12 hours on common hardware (usual SATA drives, RAID1).

    Conversion consists of 2 stages:

    • Database conversion itself. It is executed inside the transaction, so if you decide to cancel it, all the changes will be rolled back.
    • Upload the files from filesystem storage to the database. Upload is made consequent, so you can stop it any time and it will be started from the same place, without reupload.

    DO NOT START YOUR SERVER IN COMMON WAY UNTIL CONVERSION COMPLETE!

    Program will just exit after conversion will be completed. If you try to run conversion again it will answer that "no need to convert database".

  6. Examine the differences between your old Server.xml and new one (found in ZIP-package). Usually the newer version of server you use the more options you can tune via Server.xml.

  7. Start Internal Chat Server as usual and examine its logs.

  8. If everything is started properly then you can remove your spool/ subfolder in server folder with all the files inside because they are no longer needed. Additionally, you can remove parameter FileSpool in Server.xml.

If you have any questions or problems, do not forget to write them down to Forums, and I'll try to help as soon as possible.

SourceForge.net Logo

(C) 2007-2011 Andrew Orlov