In-Place Upgrade of ThingWorx Utilities
Refer to the upgrade table to determine your upgrade. The in-place upgrade feature is enabled in ThingWorx Utilities 9.2.x and later versions, retaining data after upgrading to a new version. This allows users to save time by avoiding the need for specific data backups during migration.
To upgrade to a new version of ThingWorx Utilities using in-place upgrade, perform the following steps:
1. Perform the in-place upgrade of the ThingWorx Platform manually or using the installer. For more information about the in-place upgrade of the Platform, see Installation and Upgrade
2. After the successful in-place upgrade of the Platform, import the ThingWorx Utilities extension package. For more information, see Importing the ThingWorx Utilities Extensions.
 |
When upgrading ThingWorx Software Content Management from an older version to 9.3.16 or 9.6.0, you should adjust the Timer. For manual modification of the Timer updateRate configuration, see Update Timer Rate Manually for ThingWorx Utilities.
|
|
|
While importing the ThingWorx Utilities extension package, you might see this warning:
Import requires platform restart. One or more warnings occurred.
Restart the Platform and you can continue with the upgrade.
|
3. For a non-High Available environment, restart the ThingWorx server after the imports have been completed successfully.
If you upgraded ThingWorx Utilities on a High Available Clustered ThingWorx platform, you must restart all nodes. For more information, see Managing ThingWorx Extensions in ThingWorx HA.
This enables ThingWorx Software Content Management to work properly.
4. If you upgrade ThingWorx Utilities 9.2.x and later for PostgreSQL, or from ThingWorx Utilities 9.4.x and later for MSSQL and from AzureSQL 9.5.x, and you want to migrate data from TW.RSM.SFW.SoftwareManager.Campaign or the DeliveryTarget to isolated database tables, perform the following steps:
a. Click TW.SCM.SFW.SCMUtilities resource in ThingWorx Composer.
b. Search for MigrateDataToIsolatedDB service. You can make use of Migration category.
c. Click Execute.
5. This service runs asynchronously in the background. Check the information level log for completion.
6. To avoid duplication of existing migrated entries on a successful run, a consecutive service execution will be aborted if forceMigration is not set to true. By default, forceMigration is false.
7. After a successful run, verify that the data is visible on SCM Track Deployments page and purge the old data from TW.RSM.SFW.SoftwareManager.Campaign/DeliveryTarget.