Installation and Configuration > Upgrading ThingWorx
Upgrading ThingWorx
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.
Prerequisites: Determine Upgrade Path: In-place or Migration
When 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 includes more steps, since you must export data and entities then import those entities and data into the new version of ThingWorx.
Supported Upgrade Paths
9.0 on Azure SQL
9.0 on PostgreSQL
9.0 on H2
9.0 on MS SQL Server
Upgrading from ThingWorx
8.3 on Neo4j
Not supported
Migration
Not supported
Not supported
8.3, 8.4, 8.5 on PostgreSQL
Not supported
In place
Not supported
Not supported
8.3, 8.4, 8.5 on H2
Migration
Migration
In place
Migration
8.3, 8.4, 8.5 on MSSQL
Migration
Migration
Not supported
In place
8.4, 8.5 on Azure SQL
In place
Not supported
Not supported
Not supported
InfluxDB Upgrade Paths
Upgrading to ThingWorx 9.0 with Influx 1.7.10
PostgreSQL with Influx v 1.7.10
MS SQL with Influx v 1.7.10
Upgrading from ThingWorx
8.5 on PostgreSQL with InfluxDB 1.7.7
Supported
Not supported
9.0 on PostgreSQL
Supported
Not supported
8.5 on MSSQL with InfluxDB 1.7.7
Not supported
Supported
9.0 on MS SQL
Not supported
Supported
Database Options: PostgreSQL, Microsoft SQL Server, InfluxDB, AzureSQL, or H2
You can use PostgreSQL, Microsoft SQL Server, InfluxDB, AzureSQL, or H2 for your data solution. The following download package options are available when obtaining the Thingworx.war file from PTC Software Downloads:
H2: Thingworx-Platform-H2-9.0.0
PostgreSQL/HA/InfluxDB: Thingworx-Platform-Postgres-9.0.0
AzureSQL: Thingworx-Platform-Azuresql-9.0.0
Microsoft SQL Server/InfluxDB: Thingworx-Platform-mssql-9.0.0
Before You Begin the Upgrade Process
Before upgrading, back up your model and runtime data.
If you have localization tables with locales that are not in the language-Script-REGION-variant format, you should rename them before migrating by doing the following:
1. From ThingWorx Composer, select System > Localization Tables. A list of localization tables appears.
2. Select a localization table with a non-conforming name (for example, French).
3. Choose Duplicate.
4. Enter the standard locale name (in this example for French, enter fr).
5. Choose Save.
6. Delete the original localization table with the non-conforming name.
7. Repeat the above steps for all tables with names that do not conform to the standard.
After importing the localization tables into your new system, do the following:
1. From ThingWorx Composer, select System > Localization Tables.
2. Select a localization table to edit.
3. Enter values in the Language Name (Native) field (for example, français) and Language Name (Common) field (for example, enter French).
4. If you want to choose or change an avatar (such as a national flag), click Change next to the Avatar field.
5. The avatar appears in the language preferences editor.
6. Repeat these steps for all imported localization tables.
ThingWorx High Availability Clustering
If you want to configure ThingWorx to operate in a high availability environment in cluster mode after you upgrade, see the Overview of ThingWorx High Availability Clustering for configuration details.
ThingWorx Analytics
If you are using ThingWorx Analytics as part of your solution, two installers are available to handle component upgrades:
Analytics Server – installs or upgrades Analytics Server and Analytics Extension
Platform Analytics – installs or upgrades Descriptive Analytics and Property Transforms
For more information about the upgrade procedures, see ThingWorx Analytics Upgrade, Modify, Repair.