Necessary Actions When Updating or Upgrading to 7.14

Owned by Mr. Schmittberger
Last updated: Nov 11, 2021

Necessary Actions When Updating/Upgrading

This page describes the actions that you must manually execute when updating from version 6.x to a newer version. It also lists things that you must pay special attention to. An update to a new version that skips some of the previous versions is possible and does not 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.


  • 7.10 --> 7.12

    • The new repository manager 4 (replacement for the ERM but ERM is still available) is added to the service-manager as a microservice.  Further information can be found at https://help.optimal-systems.com/yuuvisRAD/v70/sap/de/index.htm
      To complete the installation:
    • Edit the file <service-manager>\config\servicewatcher-sw.yml

    • Add the following section:

      - name: repositorymanager
        type: microservice
        profiles: prod,cloud,mq
        instances: 0
        arch: x64
        memory: 768M
        port: 8010
        path: "${appBase}/repositorymanager/repositorymanager-app.jar"

    • To use the new microservice, set the instances property to 1, else leave it at 0.


  • 7.12 --> 7.14

    • It is now possible to encrypt all passwords stored in the configuration files of the service-manager. For fresh installations the setup will do the encryption by default, for existing installations follow the below steps to encrypt the passwords.
      The encryption is optional and doesn't have to be done.
      1. Open a command prompt (cmd.exe) and navigate to the folder <service-manager>\tools
      2. Copy the plaintext password you want to encrypt
      3. Execute "encode.bat <plaintext_password>" (without < >)

      4. Replace the plaintext password in the configuration file with the return value of the form ENC(<characters>) (do not omit ENC( ))

        The encrypted passwords can not manually be decrypted anymore. Note the plaintext passwords at a safe location before overwriting them.

        Repeat these steps for all passwords you want to encrypt. The following configuration files support encryption: archive-prod.yml, application-dbs.yml, application-es.yml, application-red.yml, erm-prod.yml, gateway-prod.yml, repositorymanager-prod.yml, servicewatcher-sw.yml


    • The gateway can now optionally set the samesite cookie policy level as described here: https://blog.chromium.org/2019/10/developers-get-ready-for-new.html. To define it do the following:
      1. Edit the file <service-manager>\config\gateway-prod.yml
      2. Add a new line with "cookie.samesite: '<level>' " → replace <level> with your desired policy level. It can be one of 'none', 'lax' or 'strict'. 
      3. It should now look like this: