Server Update

Information

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.
PLANTA Server update also includes necessary adjustments to the database via migration process.

Caution

The update does not include a migration of functional data. If you have any questions, please contact 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 must be available.
An Oracle or MSSQL database must be available.
The executing user must have a profound knowledge of the required 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.

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

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.

Procedure

Terminate the PLANTA Server service of the system you want to update.
Start the update via PLANTA Installer. Please observe the description of the PLANTA Installer.

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 will automatically be 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

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, please go to the Overview of All Previous Runs topic.
Additionally, migration packets with Upon system start = , which were not run automatically in step 3 due to their setting, can be run manually in this module.

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