molgenis
8.0
8.0
  • Introduction
  • What is MOLGENIS
  • Try out MOLGENIS
  • Quick start (docker)
  • Find, view, query
    • Using the navigator
    • Using the search-all
    • Using the dataexplorer
    • Setup authentication
  • Data management
    • EMX format
    • Quickly import data
    • Advanced data import
    • Modify metadata
    • Questionnaires
    • Downloading data
    • Using expressions
  • Access control
    • Users
    • Groups and roles
    • Finegrained permissions
  • Data processing
    • Scripts
    • R
    • Python
    • Schedule jobs
  • Configuration
    • Settings
    • Customize MOLGENIS
    • Localization
    • Apps in MOLGENIS
    • Creating themes
  • Interoperability
    • Swagger specification
    • REST api v1
    • REST api v2
    • Files api
    • Import api
    • Python-api client
    • R-api client
    • Beacon api
    • FAIR api
    • RSQL operators
  • For developers
    • Developing MOLGENIS
    • Developing frontend in MOLGENIS
    • Developing Apps in MOLGENIS
    • Using an IDE (Intellij)
    • Technologies
    • Dynamic decorators
    • Running the integration tests
    • Jobs
    • Security
  • For system administrators
    • Kubernetes (experimental)
    • Standalone server (tomcat)
    • Migration guide
Powered by GitBook
On this page
  • From 7.x to 8.0.x
  • Operational requirements
  • EMX models and other configuration
  1. For system administrators

Migration guide

PreviousStandalone server (tomcat)

Last updated 4 years ago

From 7.x to 8.0.x

There are a few major changes in the migration from 7.x to 8.x.

  • The PostgreSQL version was 9.6 and is now 11.0.1

  • We're transitioning the filestore to , but the old filestore is still in use.

Operational requirements

There are a few services you need to migrate data from.

    • for 7.x PostgreSQL 9.6

    • for 8.x PostgreSQL 11.0.1

    • for 7.x /srv/molgenis/data

    • for 8.x /home/molgenis/data

    • for 7.x /srv/molgenis/molgenis-server.properties

    • for 8.x /home/molgenis/molgenis-server.properties

PostgreSQL

Go to a terminal and dump your database using (as root-user):

cd /tmp/
pg_dump molgenis > molgenis.sql

Load you database using on the new server (as root-user):

Be sure you drop the database before you load the customer database.

cd /tmp/
psql molgenis < molgenis.sql

FileStore

Go to a terminal and tar you files into an archive (as root-user):

cd /home/molgens/
tar -pzcvf /tmp/molgenis.tar.gz /data

Restore the filestore on the new server (as root-user):

cd /home/molgenis
mv data data_backup
tar -pxvzf molgenis.tar.gz
  • execute: chmod -R 770 /home/molgenis

Configuration

Go to a terminal and tar you files into an archive (as root-user):

cd /tmp/
cp /home/molgenis/molgenis-server.properties .

Restore the filestore on the new server (as root-user):

cd /tmp/
cp molgenis-server.properties /home/molgenis/ .

You need to add additional properties to make the deployment work with MOLGENIS 8.0.x

MINIO_ACCESS_KEY=molgenis
MINIO_SECRET_KEY=molgenis

EMX models and other configuration

The following changes require manual actions (if applicable for your application):

    • You can migrate the database first and if you encounter the following error

      Error:
        Conversion failure in entity type [#name#] attribute [#name#]; No converter found capable of converting from type [org.molgenis.data.support.DynamicEntity] to type [java.lang.String]

      You can fix these attributes in the Metadata Manager by editing the expression of the mentioned attribute.

  • If users or groups were giving special permissions on the Settings Manager Plugin, these permissions should be set again for the replacement Settings Plugin. The plugin itself is replaced automatically.

note: if you use our to deploy MOLGENIS you have to do the following steps:

MREF as labels are not allowed anymore. You should use template expressions. Please check: .

Ansible playbook
Minio
PostgreSQL
FileStore
Configuration
template expressions