Open Source Document Management System | OpenKM

Recently installed the OpenKM, and this is really a great piece of software!

I think I found a -really minor!- inconsistency in the concept. In my eyes it is always a good idea to keep system and data separated. So, I configured my OpenKM installation to have the repository stored on a different drive. This can be done quite easily. On server startup I noticed a message though that says the server can't locate the file 'indexing_configuration.xml' ... It is seemingly looking in a place like:
So far so good, but if the repository is split from the server installation, this points to the folder where the root node of the repository is. In my opinion this is kind of a wrong place. Again, I don't want to sound critical, but I think changing this file location would be a good thing. Any opinion on this?

if I understood you want to separate repository data from application is that ... then you should change repository.home parameter and move all repository folder to other location

is that ?

jllort wrote:if I understood you want to separate repository data from application is that ... then you should change repository.home parameter and move all repository folder to other location

is that ?

Yes, and I did all this .. and it works perfectly! Just made the observation that the file 'indexing_configuration.xml' needs to be copied to where the repository is. Only wanted to point out to that the software tries to open that file with relative path (like ../../../), three folders up. That is not a super clean approach, I guess.

I know it can lead to confusion. The reason is this (and is related to the underline repository storage engine called Jackrabbit): OpenKM read the $JBOSS_HOME/repository.xml and creates the $JBOSS_HOME/repository/workspaces/default/workspace.xml file from the previous onem which is the used to handle the repository storage. This is the "base" directory for Jackrabbit and this is why the index configuration is related to "${wsp.home}/../../../indexing_configuration.xml". Another approach is set to a absolute path, but it depends on your configuration.

As I said previously, this was not our decision but related to Jackrabbit developer team

pavila wrote:I know it can lead to confusion. The reason is this (and is related to the underline repository storage engine called Jackrabbit): OpenKM read the $JBOSS_HOME/repository.xml and creates the $JBOSS_HOME/repository/workspaces/default/workspace.xml file from the previous onem which is the used to handle the repository storage. This is the "base" directory for Jackrabbit and this is why the index configuration is related to "${wsp.home}/../../../indexing_configuration.xml". Another approach is set to a absolute path, but it depends on your configuration.

As I said previously, this was not our decision but related to Jackrabbit developer team

Thanks for the explanation! Like I said, this is nothing that prevents me or someone else from working. It's just only 99% "clean" No action needed, really.