• Import document to point different index

  • We tried to make OpenKM as intuitive as possible, but an advice is always welcome.
We tried to make OpenKM as intuitive as possible, but an advice is always welcome.
Forum rules: Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
 #45103  by openkm_user
 
Greetings,

We already have millions of documents in our repository so the index size is about 10GB, importing new documents now has reduced import speed considerably.

So we would like to point OpenKM to different index only for import (Administration -> Import) but the default index location can remain same for search.

Basically,
Administration -> Import will point to C:\okmrepo\index
Default index will point to C:\openkm\tomcat\repository\index

Please let us know how this can be achieved.

Thanks!
 #45106  by jllort
 
Remember do this action with openkm stopped. Take a look here https://docs.openkm.com/kcenter/view/ok ... -home.html . You can move whole repository or only index ( what seems is your case ). Remember after moving that the grants might be changed, the user who's starting openkm also must have grants for accessing there.

In professional edition we have an additional parameter for huge repositories "lucene works asynchronous" that means the new documents are not processed in real time while are imported what cause some delay when importing documents or change metadata and it goes into background queue. That means after few seconds you are able to search from search engine ( I'm talking about search by name or metadata, not search by contents what is another kind of feature ) and the performance of importing data is not affected by lucene search indexing process. Unfortunately is still not present in community edition. I talk about it, because you have milions of docs, I suppose you are using OpenKM from API scenario. Also in huge repositories I suggest you control the growing of OKM_ACTIVITY ( or disable if you really do not need it ) and also consider cleaning OKM_DASHBOARD and OKM_DASHBOARD_ACTIVITY, for huge repositories arrived some point you will need some optimization.
 #45109  by openkm_user
 
Hi,

Changing index path is not an issue, but we need to give 2 different index path for one OpenKM instance.

Importing pointing to,
C:\okmrepo\index

Default search in OpenKM pointing to,
C:\openkm\tomcat\repository\index

So the application (searching already imported old data) will continue working and the new import will not have any speed issues as well.
 #45147  by openkm_user
 
How can we stop indexing itself while importing new documents,
Administration -> Import

So after importing we will re-index whole repository. Any help is appreciated.

Thanks in advance!
 #45154  by jllort
 
If you stop the crotab task name "text extraction queue" will not index the content, what is not possible in community version is stop the indexing for document name, author etc.. when the document is created. In professional version exist a configuration parameter for disabling lucene index, but this parameter is still not present in community version.

About Us

OpenKM is part of the management software. A management software is a program that facilitates the accomplishment of administrative tasks. OpenKM is a document management system that allows you to manage business content and workflow in a more efficient way. Document managers guarantee data protection by establishing information security for business content.