Upgrade & migration

Two kinds of upgrades matter for otwatch: upgrades of otwatch itself, and upgrades of the monitored OpenText platform. Both are handled by handel gmbh.

Upgrading otwatch

  1. The new version (components, checks, alert rules, dashboards) is prepared as code.
  2. It is deployed to QA and validated with automated checks of targets, alert rules and dashboards.
  3. It is rolled out to production in an announced maintenance window.

New OpenText releases

otwatch supports all OpenText Extended ECM releases from 22.x onwards. With each new release, handel gmbh:

  1. reviews the release notes for changes to monitoring interfaces (endpoints, SNMP MIBs, REST APIs, configuration files),
  2. adapts checks, alert rules, dashboards and reference configurations as soon as possible after general availability,
  3. tests them in a TEST environment before use in production,
  4. documents the support status in the release notes.

We recommend the annual x.4 releases, as these are also tested with SAP and are the most stable in operation.

Supporting your OpenText upgrade

End of support

OpenText versions leaving OpenText support remain monitored on a best-effort basis. Customers are informed in advance and receive an upgrade recommendation. Discontinued otwatch functions are announced in the release notes in advance.

Further reading

handel gmbh · otwatch documentation · Last updated 19 October 2026