Update guide

Esta página aún no está disponible en tu idioma.

Download the latest “Updater utility” named OKMUpdater.jar

Once downloaded, put it in the $TOMCAT_HOME directory and execute:

$ java -jar OKMUpdater.jar -l

Follow the wizard steps.

If you access the Internet using a proxy, just configure it when executing the application:

$ java -Dhttp.proxyHost=192.168.0.1 -Dhttp.proxyPort=3128 -jar OKMUpdater.jar -l

You may also need https.proxyHost and https.proxyPort or even http.proxyUser, http.proxyPassword, https.proxyUser and https.proxyPassword parameters.

If you have a Cluster configuration, be careful because all OpenKM instances share the same database. Once you have updated a node, the others should be updated without executing the actions so the actions can be reviewed and executed manually. Ask for support if unsure about which actions should be executed on slave nodes.

$ java -jar OKMUpdater.jar -l -m

Troubleshooting

If you have problems after configuring HTTPS in Tomcat, follow these steps:

Change the Tomcat configuration back to the HTTP port 8080
Execute the OKMUpdater utility
Change the Tomcat configuration to HTTPS port 8443 again (change only server.xml and web.xml)

In early OpenKM installations, the upgrade process may require some preliminary steps. If you see an error like the one below, you have this problem:

To be able to use the updater utility, follow these steps:

Download the same version of your current OpenKM instance from http://download.openkm.com.
Stop OpenKM.
Replace the $TOMCAT_HOME/webapps/openkm.war file with the downloaded one.
Delete the $TOMCAT_HOME/webapps/openkm directory.
Start OpenKM.

Once OpenKM is running, you can use the updater utility again.

If the problem persists, please open a support ticket and attach the OKMUpdater.log and $TOMCAT_HOME/logs/catalina.log files.