Open Source Document Management System | OpenKM

PostPosted:**Wed Mar 28, 2012 11:48 am**

Hi,

I'm trying to migration from OpenKM 4.1 to OpenKM 5.0 by following this wiki page: http://wiki.openkm.com/index.php/Migrat ... 4.1_to_5.0

I have created the jaas.conf in the local directory and run:

Code: Select all

sudo java -Xmx512m -Djava.security.auth.login.conf=jaas.conf -cp ~/Desktop/OpenKM/utilities-5.0.jar com.openkm.util.RepositoryUpgrade -roc OpenKM-4.1_JBoss-4.2.3.GA/repository.xml -roh OpenKM-4.1_JBoss-4.2.3.GA/repository -rnc OpenKM-5.0_JBoss-4.2.3.GA/repository.xml -rnh OpenKM-5.0_JBoss-4.2.3.GA/repository

I get few warnings, as per the wiki page, but the migration fails with the following error:

Code: Select all

WARN  org.apache.jackrabbit.core.query.lucene.SearchIndex - OpenKM-5.0_JBoss-4.2.3.GA/repository/workspaces/default/../../../indexing_configuration.xml ignored. 
ERROR org.apache.jackrabbit.core.security.simple.SimpleSecurityManager - No valid LoginModule configuriation for OpenKM 
javax.jcr.RepositoryException: No valid LoginModule configuriation for OpenKM
	at org.apache.jackrabbit.core.security.simple.SimpleSecurityManager.init(SimpleSecurityManager.java:120)
	at org.apache.jackrabbit.core.RepositoryImpl.getSecurityManager(RepositoryImpl.java:440)
	at org.apache.jackrabbit.core.SessionImpl.retrieveUserId(SessionImpl.java:312)
	at org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:292)
	at org.apache.jackrabbit.core.XASessionImpl.<init>(XASessionImpl.java:124)
	at com.openkm.core.OKMSystemSession.<init>(OKMSystemSession.java:85)
	at com.openkm.core.OKMSystemSession.create(OKMSystemSession.java:72)
	at com.openkm.util.RepositoryUpgrade.repositoryUpgrade(RepositoryUpgrade.java:168)
	at com.openkm.util.RepositoryUpgrade.main(RepositoryUpgrade.java:133)

We are running 4.1 with bundled JBoss 4.2.3.GA on a Mac OS X 10.6.8. Our repository is around 28GB. We are using LDAP for user authentication and our 4.1 OpenKM.cfg file
reads (with names changed to protect the innocent:)):

Code: Select all

# Default configuration values
#
# repository.config=repository.xml
# repository.home=repository
# system.user=system
# default.user.role=UserRol
# default.admin.role=AdminRol
# principal.adapter=es.git.openkm.core.UsersRolesPrincipalAdapter
max.file.size=500
# max.search.results=25
# system.demo=off
# update.info=off
# system.ocr=/usr/bin/tesseract
system.openoffice=on
system.pdf2swf=/opt/local/bin/pdf2swf
# system.readonly=off
# system.antivir=/usr/bin/clamscan
restrict.file.mime=off
restrict.file.extension=*~,*.bak,._*

principal.adapter=es.git.openkm.principal.LdapPrincipalAdapter
principal.ldap.server=ldap://local_ldap_server
principal.ldap.security.principal=cn=someone
principal.ldap.security.credentials=password
principal.ldap.user.search.base=ou=people,dc=company,dc=com
principal.ldap.user.search.filter=(objectClass=posixAccount)
principal.ldap.user.attribute=uid
principal.ldap.role.search.base=ou=groups,dc=company,dc=com
principal.ldap.role.search.filter=(objectClass=posixGroup)
principal.ldap.role.attribute=cn
principal.ldap.mail.search.base=ou=people,dc=company,dc=com
principal.ldap.mail.search.filter=(objectClass=posixAccount)
principal.ldap.mail.attribute=zimbraMailDeliveryAddress
system.login.lowercase=on

Please help!

BTW, I've looked at doing an export then import but it appears as if we will lose our history information.

Raffaele

PostPosted:**Fri Mar 30, 2012 9:58 am**

If you want not change log history you should take a look at older activity log table structure and newer and then create insert scripts from old table to new tables ( that can be doing with correct select ). Otherside simply you could mantaining these tables in other DBMS if you want in future make any consult on it.

PostPosted:**Sat Mar 31, 2012 6:15 am**

Our installation is quite standard apart from using an external LDAP database for users. I was hoping this was going to be straightforward (this is for a small company and it's not
my full time job). I'm just going to export the data from 4.1 and import into 5.1.9 and lose the history/metadata.

Also the migration tool corrupted our existing database but thank goodness for Time Machine backups!

PostPosted:**Mon Apr 02, 2012 12:05 pm**

The migration utility can't hurt your old OpenKM installation because it does not modify anything, only read. Anyway you have a very old OpenKM version and even if you migrate to OpenKM 5.0 it is also old. The fastest and simpler way to upgrade to a recent OpenKM release is exporting and importing the whole repository.

And remember, you can get professional support from us

Open Source Document Management System | OpenKM

Error migrating from 4.1 to 5.0

Error migrating from 4.1 to 5.0

Re: Error migrating from 4.1 to 5.0

Re: Error migrating from 4.1 to 5.0

Re: Error migrating from 4.1 to 5.0