Open Source Document Management System | OpenKM

Good day,

I recently installed OpenKm 6.2.5 (build 8109). First tests with some documents were fine. Then I imported (through Admin utility) all our documents, about 86000 files, 12 GB. After that, I have the following problems:

- When Tomcat is started, it takes several minutes before it is ready. In the catalina log I see no errors. Eventually there is a log entry:
INFO org.apache.catalina.startup.Catalina - Server startup in 289086 ms (almost 5 minutes)
- With nobody logged in yet, and without any indexing going on, tomcat uses a lot of CPU time according to htop. This goes on indefinitely.
- Logging in with the browser also takes several minutes. The popup “Loading OpenKM” comes up and then it sits at “Getting taxonomy root node” for several minutes (3 blue blocks) and then it completes. Once logged in, the system is usable but sluggish.

I have 15 folders under okm:root, with varying numbers of subfolders and files under each.

Using the default HSQL database.

OS: Debian Wheezy (VPS)
CPU's: 1
RAM: 3 GB
Disk: 95 GB

Is my system too light? Should I rather use MySQL or PostgreSQL? Any help will be much appreciated!

Gert Koning

In production it is best to use a conventional database. I recommend you migrate to a MySQL . Migration from one to another is not straightforward, you will have to export the file and import it into a clean OpenKM .

The steps would be:
(You can stop or change the current tomcat ports again, this is because your decision ) . Add the repository temporarily in read for anyone applying changes during the parameter is system.readonly (from the administration )
1 - set in a clean tomcat mysql http://wiki.openkm.com/index.php/MySQL_-_OpenKM_6.2
2 - http://wiki.openkm.com/index.php/Repository_export export data ( metadata and historical )
3 - http://wiki.openkm.com/index.php/Repository_import import data ( categories first and then the rest , root, templates , trash , personal etc ... )
4 - you can export and import the configuration parameters of the application ( there is an icon in the upper right) http://wiki.openkm.com/index.php/Configuration_view
5 - export and import users from the old to the new application ( this can serve you .... 11_to_6.2 http://wiki.openkm.com/index.php/Migrat look at first as the consultations are to take users and create inserts )

Thank you, Sochoa. I think I will rather install OpenKM from scratch again, and then use PostgreSQL, which we use a lot.

As ochoa said, HSQL should not be used in production environment. With PostgreSQL you'll get good performance as Mysql among others.

I can now confirm that using PostgreSQL as opposed to the default HSQL makes a tremendous difference. All my problems mentioned above are gone!

HSQL is not a database for use in production environments. We set HSQL as default database because for beginners it's easy to get openkm started, but when for production environment always should be used MySQL, PostgreSQL etc.. not HSQL which is an embeded database.