Skip to content

Migration Guide

Available migration paths

new section

Principles

  • Consecutive updates always migrate automatically (e.g. 1.7 to 1.8)
  • Any backup can be restored in any version released after that version (e.g. backup of 1.2 in 2.0)

It is recommended to perform consecutive version updates. In case versions need to be skipped, please follow the below migration paths.

This only covers updating to the latest version. When updating to any other version, please contact the support.

Migration path from any version to the latest version

  • For any version starting from 1.4 to 1.11, jumping to version 2.0 will automatically migrate the data.
  • For any version below or equal to 1.3, jumping to version 2.0 will loose all data. If such an update should be performed, please backup your data and restore it in the version 2.0.

Migrating from a standalone IIH Essentials to 2.0

If IIH Essentials was used standalone, the above migration paths can be followed.

No additional limitations need to be considered.

Migrating from an integrated IIH Essentials to 2.0

If IIHE Essentials was used in the integrated mode together with IIH Semantics and Common Configurator, multiple apps need to be installed to complete the migration.

However, the migration process has been designed in a way, that no fixed order of steps has to be followed. This prevents accidental data loss.

When updating from the last version, 1.11, you can execute these steps in any order:

  • Update IIH Essentials
  • Update IIH Semantics
  • Update Common Configurator

When skipping versions, for updating IIH Essentials the above steps still apply.

Please keep in mind that IIH Semantics can behave differently. Details should be checked in the IIH documentation before starting the process.

API stability

Principles

At any given time, the API remains stable for at least one year.

With every release, some routes might be marked as deprecated with a deprecation date. Starting from this date, the route will be supported for one year and then be removed.

If you are an app provider or developer, you should monitor the API specification (available within the app or here) with every release. In case routes are used which have been deprecated, either:

  • provide an update that doesn't use the deprecated routes within one year or
  • inform customers, not to update IIH Essentials if they want to continue using your app

Except where otherwise noted, content on this site is licensed under the Siemens Inner Source License .