Necessary Actions When Updating/Upgrading

This page describes the actions that you must manually execute when updating from version x.y.z to a newer version. It also lists things that you must pay special attention to. An update to a new version that skips some previous versions is possible and doesn’t require updating to each version in between. However, in this case you must carry out all the actions from your previous version to the target version in the order listed here.

• 4.12 --> 5.0

  • Before upgrading to version 5.0, you must have upgraded to version 4.12 and you must have completely removed any folder-in-folder structures in your schema and object instances (see Migrating folder structures from version 3.3 to 4.0).

  • With enaio redline 5.0 the Elasticsearch service has to be updated to version 6.3. Reindexing the enaio data is neccessary. How to update the service and how to migrate the data is documented here: Migration of Elasticsearch from version 5.5 to version 6.3

  • The StructureService MicroService is now part of the service-manager Setup. Before updating the service-manager service, please uninstall the previously manually installed StructureService:

    • delete the following folder and all its contents: <service-manager>\apps\structureservice
    • edit the file <service-watcher>\config\servicewatcher-sw.yml and delete the entire structureservice section.
  • The import organisation (AD-Sync) operation is now only available via the management-studio and the parameters "import method" "import mode" and "rootpath" have been removed from the GUI form.
    • import method: This is automatically determined by the ID in the specified configuration file
    • import mode: This will be taken from the value specified in the configuration file. Please make sure you have the correct mode ("NORMAL" or "SIMULATION") in the configuration file
    • rootpath: This will be taken from the value specified in the configuration file. Please make sure you have the correct rootpath in the configuration file
  • Edit the file <service-manager>\config\application-es.yml and add the line spring.elasticsearch.rest.uris: '<es-server-ip>:9200' - where <es-server-ip> needs to be replaced with the ip of the elasticsearch server.
    Multiple elasticsearch server (cluster environment) can be defined by '<es1-server-ip>:9200,<es2-server-ip>:9200,<es3-server-ip>:9200'

  • archiveservice: the service-specific configuration is done via the archive-prod.yml file.
    The structure in the archive-prod.yml has changed.
    At the top level, the property "archives" is replaced by the property "storage".
    The next property level defines the „profiles“ for the different storage types (e.g. iternity)
    From that level on the property structure remains unchanged.
    Compared to the previous format example the level of depth from the properties „profiles“ and „iternity“ is switched.

    now:

     storage:
      profiles:
        iternity:

    previous:

    
    

     archives:
      iternity:
        profiles: