Introduction

This document describes the Upgrade Index function in the ELO Server Setup, as well as its application.

Please note

The Upgrade index function in the ELO Server Setup must not be performed on the production database in ELO 12 or higher, as changes to the database during the installation process will cause issues in older versions of ELO.

If you still want to use the function, you must duplicate the data of the production database in a separate database instance. You must specify this separate database instance when you run the Upgrade index function.

These instructions do not cover the installation. A reindex of the full text database takes place before installation and should be completed before you begin installation.

Descriptions of functions

Before you update ELO iSearch to a new version, you need to reindex the full text database. To ensure the availability of the full text search during this process, the Upgrade Index function in the ELO Server Setup allows you to set up the full text database before updating the server.

An isolated system is used, which consists of an Apache Tomcat with ELO Indexserver and an ELO iSearch instance that can be used for reindexing, while the ELO server components continue running with their former versions. Once reindexing is completed, the ELO server can be updated with very little downtime.

Use case

You should use the Upgrade Index function if the duration of the reindex process and the resulting limited availability of the full text search would exceed the tolerance limit.

A reindex of up to approx. 1 million documents (sum of all repositories) should be done over the weekend. Of course, this depends on the hardware used as well as the average document size.