Skip to content

Updating the server

When updating the server, no distinction is made between server installations with client and server installations without client. The update process is always the same. The server and client updates are carried out in two separate steps.

Info

The connected agents are updated automatically during the server update (when the service is started for the first time).

Prerequisites for the server update

  • All octoplant processes must be terminated.

  • The server archive data in the local directory or on the remote share must be backed up.

    Warning

    If you use a remote archive, you must always back up both the remote archive and the local server archive before an update.

  • The Setup.exe file must be executed with administrative rights on the server.

  • The user account under which the setup is executed must have full access rights to the following directories:
    • octoplant program directory
    • Local server archive and remote server archive (if remote server archive exists)

  • Executing files must be permitted on the drive on which the server archive is located. Any existing security policies that prevent the files from being executed must be deactivated. If the execution of files is not permitted, an error message (SQL exception) will be displayed later when you login to the system. The login is not possible in this case.

  • It is recommended not to install the octoplant hub on a computer on which a octoplant server is already installed. If this has already been done, the postgres service octoplant hub PostgreSQL 14 must be stopped manually when installing/updating the octoplant server.

Procedure

  1. Start the setup on the computer intended for the update by double-clicking on the Setup.exe file supplied in the octoplant software package. The installation wizard will start.
  2. Select a language version. Currently German and English are available.
  3. On the welcome page of the installation wizard, select Next.
  4. If octoplant processes are running, they will be displayed here. Terminate the displayed processes by clicking Next. If the processes cannot be stopped via the installation wizard, stop them in the Service Control Manager.

  5. Select the option Install octoplant applications and select Next.

    Figure: Installation wizard, octoplant Install applications

  6. Select I agree. and select Next. If you do not agree to the license agreements, the installation will not continue.

  7. Select the option Install server applications and select Next.

    Figure: Installation wizard, Server installation

  8. A note is displayed stating that an octoplant server is already installed. Click the Update button at to perform the server update.

  9. In the next step, you will be asked to create a backup of your server archive or to confirm that you have already created a backup of the server archive. Data backup is required as a data migration is carried out during the update, during which the server archive may be damaged and data may be lost.

    Figure: Installation wizard, Note on Backup of the server archive

  10. Confirm the path to the octoplant server applications directory by clicking on Next.

  11. TCP port 64023 is required for octoplant. If you are updating from a versiondog version older than 9.5, you will be shown a note stating that this port must be enabled. Confirm the note by entering the required text.

  12. Windows XP Professional SP3, Windows Vista SP2 and Windows Server 2003 are no longer supported for octoplant. When updating from an older versiondog version, a Note is displayed in the setup. This contains a link to a detailed list of the options you have if you are using older operating systems. Read the text carefully and confirm it if necessary by entering in the "I understand" input field.

    Figure: Installation Wizard, Note on Windows XP and Server 2003

  13. If you are using one or more BackupClient, synchronize them before updating the server. As the PostgreSQL database is updated during the update, synchronization is no longer possible afterwards and local changes may be lost. After the server update, update the BackupClient as usual before using them.

    Figure: Installation wizard, Note on synchronizing the BackupClients

  14. The server update is executed. The completion of the update is indicated by a message.

    Info

    A database migration is carried out during the update. This can take some time, especially for large archives. A progress bar is displayed.

  15. After a successful update, click on Finish to close the wizard.

Info

If you are using gateways, these must also be updated after a successful server update.