Page Comparison

The following instructions explain how to upgrade an instance of OpenEMPI from a 4.2.x release to the 4.3.y release.

...

openempi-entity-4.2.y/conf/file-loader-map-*.xml

NOTES: Please read and understand the information in these notes.

• We use the convention of naming file loader mapping files file-loader-map-{VARIABLE].xml where VARIABLE is a unique name that identifies the specific mapping file. You only need to copy mapping files that are unique to your installation.

• Starting with the 4.3.0 release of OpenEMPI the Postgres relational database is no longer used so as part of this upgrade the next few steps will migrate the data from the relational database into the embedded graph database and specifically in the configuration database instance (openempiConfig-db).

• Make sure you delete old or unneeded audit log and identifier update notifications before performing the migration otherwise the migration process may take too long or fail to complete. Some sites don’t delete old entries and they may have accumulated millions of records. You can do that using the appropriate scheduled task or you can open a ticket in the customer support forum and we can help you with that.

• The installation of 4.3.x creates an initial configuration database instance openempiConfig-db but if you are migrating from a 4.2.x version, you should replace the openempiConfig-db created by the installation with a copy of the openempiConfig-db from the data directory of your 4.2.x instance. If you are using the shared data directory as suggested in step 3, you can ignore this step since the new configuration database instance is created in the data sub-directory of the 4.3.x installation directory but make sure you have modified the data directory in the setenv.sh file before beginning the migration process as described in step 6.

...

export ORIENTDB_OPTS_MEMORY="-Xms1G -Xmx6G"

The migration script assumes that the data directory for the 4.3.x instance is in the data directory under the installation directory (for example: /sysnet/openempi/openempi-4.3.0/data). If your directory is in a different location (for example /sysnet/openempi/data) then you should set the OPENEMPI_DATA_DIRECTORY environment variable to point to that directory before running the migration script. Here is an example but remember that you only need to do this if your data directory is not located in the default location.

export OPENEMPI_DATA_DIRECTORY=/sysnet/openempi/data

9. Run the migration script. If you encounter any issues with the migration process please open a ticket in the customer support forum and provide the output of the migration process.

...