Migrating from OpenKM 2.0 to 4.0

[davegball]

Hi

I'm migrating repository data and user permissions from an OpenKM 2.0 install to an OpenKM 4.0 install on a different physical server. Is there an easy way to auto export the configuration data and documents or I need to recreate everything on the new machine? Maybe I need to manually copy the users and roles config files across. Not sure.

Thanks for any help.

[jllort]

We're finishing documentation, in next week it'll be available.

You must migrate from version 2.0 to version 3.0

And after it, from version 3.0 to 4.0 I advance here - new wiki - what must be done in this case:

Download the migration utility called OKMUtils-4.0.jar. This is a self-contained JAR with all the required dependencies. Can be executed from command line as:

Code: Select all

$ java -Xmx512m -jar OKMUtils-4.0.jar

And will show the parameters needed:

* RepositoryOldConfig: Path to the old repository configuration file. This is the $OLD_JBOSS_HOME/repository.xml file by default. Perhaps is different if you changes the repository.config property in OpenKM.cfg file.

* RepositoryOldHome: Path to the old repository directory. This is the $OLD_JBOSS_HOME/repository directory by default. Perhaps is different if you changes the repository.home property in OpenKM.cfg file.

* RepositoryNewConfig: Path to the new repository configuration. If you downloaded the JBoss + OpenKM bundle, there is a default $NEW_JBOSS_HOME/repository.xml file.

* RepositoryNewHome: Path to the new repository directory. This is the $NEW_JBOSS_HOME/repository directory by default. This folder actually does not exists and will be created in the migration process.

These are the required steps to make a migration.

* Download the new OpenKM version and uncompress it.

* Stop the actual JBoss instance and make a backup.

* Modify the $NEW_JBOSS_HOME/server/default/conf/login-config.xml according to the old settings. If you didn't change it in the actual installation, this step is not required.

* Modify the $NEW_JBOSS_HOME/server/default/deploy/openkm-ds.xml according to the old settings. If you didn't change it in the actual installation, this step is not required.

* Modify the $NEW_JBOSS_HOME/server/default/deploy/mail-service.xml according to the old settings.

* Modify the $NEW_JBOSS_HOME/OpenKM.cfg according to the old settings. Remember to check the changelog because some properties can be deprecated.

* Perhaps you need to copy the JDBC library from $OLD_JBOSS_HOME/server/default/lib to $NEW_JBOSS_HOME/server/default/lib. You can skip this step for a default OpenKM installation.

* Run the migration utility.

* Start the new JBoss.

[davegball]

Thanks for your reply.

Once I migrate from 2.0 to 3.0 do I use the same migration utility to go from 3.0 to 4.0?

Also what exactly is the migrate utility processing? Just the format of the repository.xml file or is it also moving the documentation across?

Does the utility also migrate the users/permission or I need to recreate (or copy the flat files across).

Regards

[jllort]

Take a look at wiki.openkm.com

You might recreate users and passwords, becuase there's so much changes between 2.0 to 4.0 ( your must create some script from initial database to final database ). Take a look how to explore database ( there's something in developer guide, in wiki too ).