Update Server 39.5.x (Venus) to 39.5.y (Venus)

Information

• This topic provides a description of the technical procedure for the PLANTA server update which is already on a 39.5 version (Venus) to a higher 39.5 version (Venus).
• For the description of the PLANTA server update from version 39.4.4.0 (Venus) to another 39.5 version (Venus), please go to the UpdateServer394To395 topic.
• This topic only addresses issues which apply to the server update alone. If you want to update your database as well, please take note of this description.
• For a complete overview of different combinations (according to your system version and the version to which you want to update), please refer to this description.

General

Information

• The PLANTA server update from a 39.5 version (Venus) to a later 39.5 version (Venus) includes necessary database adjustments via the new migration process which was implemented in S 39.5.0.

Attention

• The update does not contain a migration of functional data. If you have any questions, please consult your PLANTA consultant.

Requirements

Information

• All requirements described in the System Requirements topic must be met, including the PLANTA project user rights for Oracle databases described in there.
• On Linux systems, rsync should be available.
• An Oracle or MSSQL database must be available before installation.
• The executing user must have profound knowledge in the required special fields and be logged on to the server as administrator (Windows) or root (Linux). On Windows, the installation can also be started by using the Run as administrator context menu.

Procedure

The update including the migration process is carried out via the PLANTA installer.

Step 1: Download New Release

The download files for current releases are made available on the PLANTA Transfer Server_

Procedure

• Please download the required release to which you want to update.
• The downloaded ZIP archive must be stored and unpacked on the system on which the PLANTA server is to be installed and updated.

Step 2: Installing the new server

Procedure

• Terminate the PLANTA server service of the system you want to update.
• Start the update using the PLANTA installers. Please observe the description of the PLANTA installers.

If a migration was carried out in the course of your update, please note the following:

• If the MIGRATION user and the persons assigned to it are deleted, they are automatically created anew in the next update.
• Make sure that the database connection corresponds to the existing system. Currently, the installer does not check the database connection before starting the update, i.e., the installation fails automatically if an incorrect database connection is entered without pointing it out explicitly.

Notes

• Available Python adjustments are applied.
• The existing PLANTA server service is uninstalled.

Step 3: Checking the Migration Results

Procedure

• After starting the PLANTA server service, the migration packet status (i.e. whether they have run correctly) must be checked in the Migration Packets module.
  • If a packet has not been run correctly, you must check the log file of the migration packet and take appropriate measures. For further information, refer to the Overview of All Previous Runs topic.
• Additionally, migration packets with Upon system start setting = , which were not run automatically in step 3 due to their setting, can be run manually in this module.

Step 4: Necessary steps after migration

Information

• After migration, the following steps must be carried out.
  • Transfer SAP-dll-files from predecessor system
  • Transfer Kerberos and Stunnel configurations from predecessor system