...
3. Install the 4.0.0 instance in its new OPENEMPI_HOME directory. Follow the installation instructions for installing a new instance of OpenEMPI from a distribution that can be found here. The recommended approach is to install new releases in the same directory so that openempi-4.0.0 and openempi-3.5.y are in the same directory. On our installations, we follow the convention of installing new releases in the /sysnet/openempi directory so that the 4.0.0 release would be installed in the /sysnet/openempi/openempi-4.0.0 directory and the 3.5.7 release would be installed in the /sysnet/openempi/openempi-3.5.7 directory.
...
| Code Block |
|---|
bin/setenv.sh
openempi-entity-3.5.x/conf/openempi-extension-contexts.properties
openempi-entity-3.5.x/conf/log4j.properties (not likely to have local changes for your environment)
openempi-entity-3.5.x/conf/jdbc.properties (more likely to have local changes for your environment)
openempi-entity-3.5.x/conf/applicationContext-resources.xml (more likely to have local changes for your environment)
openempi-entity-3.5.x/conf/applicationContext-services.xml (not likely to have local changes for your environment)
openempi-entity-3.5.x/conf/orientdb-server-config.xml |
5. Copy the following configuration files from the 3.5.x to the 4.0.0 directory.
...
Download and extract the 3.0.35 38 release of OrientDB community edition or later (You can download the 3.0.35 38 release from here.)
| Code Block |
|---|
$ cd /tmp $ wget https://s3.us-east-2.amazonaws.com/orientdb3/releases/3.0.3538/orientdb-3.0.3538.tar.gz $ tar xf orientdb-3.0.3538.tar.gz |
Export your current database using the following steps below. This process may take a while to run depending on the size of your database and the hardware configuration of your server. Make sure you have sufficient disk space and available memory for this operation. Note: Before starting the OrientDB console, you should adjust the memory settings and specifically the mx parameter. You can copy the mx setting from the setenv.sh file since it has probable already been tuned to support the size of your database. Since you don't need the OrientDB cache as much during the migration, you can increase the mx parameter a bit higher than its setting in the setenv.sh file. This section in the console script that you need to modify looks like this.
if [ -z "$ORIENTDB_OPTS_MEMORY" ] ; then
ORIENTDB_OPTS_MEMORY="-Xmx1024m "
fi
| Code Block |
|---|
$ cd /sysnet/openempi/openempi-3.5.7/data $ /tmp/orientdb-3.0.3538/bin/console.sh OrientDB console v.3.0.3538 - Veloce (build b636a4c891bc1b0f93df5bb16ec72dedee7a63e7, branch 3.0.x) https://www.orientdb.com Type 'help' to display all the supported commands. orientdb> connect plocal:./person-db openempi openempi Connecting to database [plocal:./person-db] with user 'openempi'...OK orientdb {db=person-db}> export database person-db Database export completed in XXXXXXms orientdb {db=person-db}> quit |
...
| Code Block |
|---|
$ /tmp/orientdb-3.0.3538/bin/console.sh $ cd /sysnet/openempi/ $ mkdir tmp $ cd tmp $ mv /sysnet/openempi/openempi-3.5.7/data/person-db.json.gz . $ /tmp/orientdb-3.0.3538/bin/console.sh Here OrientDB console v.3.0.3538 - Veloce (build b636a4c891bc1b0f93df5bb16ec72dedee7a63e7, branch 3.0.x) https://www.orientdb.com Type 'help' to display all the supported commands. orientdb> create database plocal:./person-db admin admin Creating database [plocal:./person-db] using the storage type [PLOCAL]... Database created successfully. Current database is: plocal:./person-db orientdb {db=person-db}> import database person-db.json.gz Database import completed in XXXXX ms orientdb {db=person-db}> quit |
...
| Code Block |
|---|
$ cd /sysnet/openempi/openempi-4.0.0 $ rm -rf data/person-db # Remove the target directory just in case it is already there. $ cp -r ../tmp/person-db data # Above we restored the database in the /sysnet/openempi/tmp directory |
7. Run any database upgrade scripts that are specific to the new version you are upgrading to. Not every release includes a database upgrade script but if there is one, it would be in the conf directory under OPENEMPI_HOME. Upgrading to the 4.0.0 release from 3.5.x requires that you run the script update_database_schema-4.0.0.sql.
| Code Block |
|---|
psql --user=openempi --password --host=localhost
\i update_database_schema-4.0.0.sql |
8. Start your instance of OpenEMPI using the startup script from the new release directory. If you are using a service startup script to automatically start your instance of OpenEMPI, make sure you update the script to reflect its new directory location (this is usually installed in /etc/systemd/system/openempi.service).
...