Upgrading ThingWorx
 |
From ThingWorx 9.5 onwards, support for H2 database has ended. To prevent any data loss, perform the following steps before upgrading to ThingWorx 9.5.
1. If you are using ThingWorx 9.3 or ThingWorx 9.4 with H2 database, move to a supported database, PostgreSQL , MSSQL, Azure SQL, InfluxDB, Azure PostgreSQL Flexible Server (available from ThingWorx 9.4.1 and later), of ThingWorx 9.3 or ThingWorx 9.4.
2. Upgrade to ThingWorx 9.5 or above, for the chosen supported database. For more information. see Manual Migration to ThingWorx 9.x: Linux and Manual Migration to ThingWorx 9.x: Windows.
|
|
|
If you are a hosted customer by PTC Cloud Services, please log a service request at eSupport to plan for your upgrade with the supported upgrade paths. The upgrade steps provided in this Help Center are intended for on premises installations only.
|
There are several options when performing an upgrade of ThingWorx. You can use the installer to upgrade or you can perform a manual in-place or migration upgrade. There is also an upgrade process if you are upgrading ThingWorx in an high availability environment.
|
|
Prior to upgrading, the persistence provider set on the AlertHistoryStream and AnomalyMonitorStateStream entities must match the data persistence provider set on the AlertProcessingSubsystem. If these aren't in sync, the persistence providers on AlertHistoryStream and AnomalyMonitorStateStream will be overwritten by the data persistence provider configured on the AlertProcessingSubsystem .
|
|
|
If you have ThingWorx Flow installed, make sure you upgrade ThingWorx Flow when upgrading ThingWorx.
|
Using the Installer to Upgrade
If you used the ThingWorx Foundation Installer to install ThingWorx Foundation 8.5.0 or later, you can use the installer to upgrade ThingWorx Foundation.
Manual Upgrade
When manually upgrading to a newer version of ThingWorx, administrators have two options for getting new features and enhancements into existing landscapes: in-place upgrades and migrations. Generally, for in-place upgrades, you do not need to delete the ThingworxStorage and ThingworxBackupStorage folders or import data/entities after installing ThingWorx, and is applicable when upgrading to the same persistence provider. Migrating requires exporting data and entities from the current ThingWorx, then importing those entities and data into the new version of ThingWorx. Refer to the following support matrices to determine your upgrade path:
Upgrading ThingWorx High Availability Clustering
If you are upgrading ThingWorx in a high availability environment in cluster mode, see Upgrading ThingWorx High Availability Clustering.