Open Source Document Management System | OpenKM

Hi
We're having a running Tomcat behind an Apache. I wanted to install the OpenKM on this Tomcat.
I took the OpenKM.war file and have it unzipped to the webapps directory. When I start the Tomact I'm getting this Error messages:
What does it mean, what do I have to change?

Thanks for your help

You should take a look at server.xml file, OpenKM.cfg and PropertyGroup.xml etc... only copy war to webaps is not enought.

Download the Tomcat + OpenKM bundle from SourceForge and look for differences. You need to modify some XML, add some JARs, modify configuration. Not easy task. This is why we provide a Tomcat + OpenKM bundle.

pavila wrote:Download the Tomcat + OpenKM bundle from SourceForge and look for differences. You need to modify some XML, add some JARs, modify configuration. Not easy task. This is why we provide a Tomcat + OpenKM bundle.

This is a bad excuse for a poor design. Linux is about modularity and bundling stuff together makes it very hard to maintain. If you Bundle them, can you explain how you want to use OpenKM on a system that already uses tomcat. For instance, if you already have LibrePlan installed then you cannot use OpenKM.

pavila wrote: You need to modify some XML, add some JARs, modify configuration.

Moreover, please be specific when you are referring to file names and instruction. If you are saying modify some files to do some stuff on in the thing it is only clear to yourself.

Regards

We have some of this kind of installations with our customers and they have no problems because we make the necessary steps to integrate (or deploy). I mean, if you want to deploy OpenKM in a Tomcat you can (of course) but you need to add some libraries to $TOMCAT_HOME/lib, and configure server.xml but I'm pretty sure you have the enough Tomcat administration knowledge.

About the libraries, it's simple: download a vanilla Tomcat and compare with the provided in the bundle. I guess you are intelligent enough to see which JAR where added. Yes, you have to invest a little of time (perhaps 15 mins). Are you too busy? Me too and I've dedicate some minutes to answer your questions.

Do we have a poor design? Perhaps, but you can teach us how to improve or create a Debian package ready to install in a Debian based distro.

But first of all you should try the bundle and if OpenKM meets your requirements, worry about installing in you own Tomcat.

Probably this url can help you http://wiki.openkm.com/index.php/Config ... ce_windows

I think you are missing a comprehensive setup strategy (maybe I just didn't find the documentation?)
A combined package including Tomcat is prohibitive because now I can't easily roll it out into my existing container.
(I also want to use our existing database setup.)

TeamCity is a build server package that runs on Tomcat; please have a look at their documentation / strategy.
https://confluence.jetbrains.com/displa ... ity+Server

In particular "Installing TeamCity into Existing J2EE Container"
If I have to copy files, configure things, et. al., that's fine.
I just need instructions.

Comparing to another Tomcat is asking for problems.
What if I don't get the exact version/setup of Tomcat you used?
What if I decide a file that you have changed is a file that should be kept from the original tomcat setup?
On & on. The odds of someone else - not a core developer - doing this correctly is low.
(e.g. Not even minecraft mod-packs use this poor of a strategy.)

It sounds like you have put together an amazing thing with OpenKM but I think the setup is currently a significant hurdle that is preventing you from reaching a wider user-base.

We try to do things as easy as we can, obviously is easier download Tomcat-OpenKM Bundle than this kind of configuration. We totally aggree with you about we have a documentation problem that won't be solved until next year, because need to invest a lot a time to improve it. But you forget something very important from our point of view, is a good idea using OpenKM in same application server than other applications? We only suggest this scenario when there's no other alternative and obviously for small repositories. What kind of repository you will got ( users and number of documents ) and also which is your hardware ?