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:
 |
If you are using an Azure SQL database and are upgrading to ThingWorx Platform prior to 9.7.4 in the 9.7.x stream or prior to 9.6.7 in the 9.6.x stream, manual steps are required prior to upgrading the platform in order for the Software Content Management schema and database tables to be created. For more information, see Manual Steps Required if Upgrading
to a ThingWorx Platform Version Prior to 9.7.4 or 9.6.7 (Azure SQL).
These manual steps are not required if you are upgrading to 9.7.4 or later in the 9.7.x release stream or 9.6.7 or later in the 9.6.x release stream.
|
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 the "Installation and Upgrade" topic in the ThingWorx Platform Help Center for your ThingWorx version, available from the ThingWorx Help Centers landing page.
2. After the successful in-place upgrade of the ThingWorx Platform, import the ThingWorx Utilities extensions.
1. Import the ThingWorx Utilities Core extension zip file.
2. Restart the ThingWorx Platform server.
3. Import the ThingWorx Software Content Management extension.
4. Restart the ThingWorx Platform server.
For more information, see Importing the ThingWorx Utilities Extensions.
3. When upgrading ThingWorx Software Content Management from an older version to 9.3.16, 9.3.19, 9.4.11, 9.5.1+, 9.6.x, or 9.7.x, you should adjust the timer update rate configurations:
1. In the left navigation pane of ThingWorx Composer, select Timers. ThingWorx Composer displays the list of timers.
2. Select a timer from the list and click Edit to edit its update rate configuration value.
3. Enter the appropriate update rate value for your release in the updateRate field. The update rate values for each release are listed in the tables following this procedure.
4. Click Save.
5. Repeat steps 3.b through 3.d for each timer.
 |
Starting with 9.5.0, the StartDeploymentsTimer timer automatically starts the deployment. If you are using provisioning services, there is no longer a need to explicitly call the StartCampaign service from your provisioning service, as was required in previous releases.
|
4. 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 the "Managing ThingWorx Extensions in ThingWorx HA" topic in the ThingWorx Platform Help Center for your ThingWorx version, available from the ThingWorx Help Centers landing page.
This enables ThingWorx Software Content Management to work properly.
5. If you upgrade from ThingWorx Utilities 9.2.x for PostgreSQL, from ThingWorx Utilities 9.4.x and later for MSSQL, from ThingWorx Utilities 9.5.x for AzureSQL, 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.
6. This service runs asynchronously in the background. Check the information level log for completion.
7. 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.
8. 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.
|
|
After upgrading to ThingWorx Software Content Management 9.7.x from any version, ensure that the values specified for the performance configuration parameters have supported values. For more information, see Deployment.
|
Manual Steps Required if Upgrading to a ThingWorx Platform Version Prior to 9.7.4 or 9.6.7 (Azure SQL)
If you are using an Azure SQL database and are upgrading to a ThingWorx Platform version prior to 9.7.4 in the 9.7.x stream or prior to 9.6.7 in the 9.6.x stream, the following steps are required to ensure that the Software Content Management schema and database tables are created.
|
|
These manual steps are not needed if you are upgrading to ThingWorx Platform 9.7.4 or later in the 9.7.x stream or 9.6.7 in the 9.6.x stream.
|
Complete the following steps:
1. Navigate to support.ptc.com. Under Popular Tasks, select Download Software, then click Order or Download Software Updates.
2. Select ThingWorx Foundation.
3. Expand the folder for the release stream you are upgrading to (Release 9.6 or Release 9.7), and then expand the following folders: > .
4. Download the extension package ZIP file for the release you are upgrading to and extract the ZIP file.
5. Navigate to the install directory and open a command prompt.
6. Execute the database schema update script using the sqlcmd utility with the following command:
sqlcmd -S <SERVER>,<PORT> -U <LOGIN_NAME> -v database=<DATABASE> -P <PASSWORD> -d <DATABASE> -i ./thingworx-system-schema.sql
Replace the variables with values appropriate for your system:
◦ -S <SERVER>,<PORT>—Specifies the SQL server host, instance, and port to connect to.
◦ -U <LOGIN_NAME>—The SQL user name used for the connection. Ensure that this user account has sufficient privileges to run scripts.
◦ -v database=<DATABASE>—Sets the SQLCMD database variable. Used inside the script.
◦ -P <PASSWORD>—The password for the SQL login.
◦ -d <DATABASE>—Defines the initial database context used when the script runs.
◦ -i ./thingworx-system-schema.sql—Points to the SQL file to be executed.
For example:
sqlcmd -S localhost,1433 -U twadmin -v database=thingworx -P password -d thingworx -i ./thingworx-system-schema.sql
7. After the script completes, review any logs or messages that were generated during execution.
8. Validate that the SCM database tables are present in the database: scm_delivery_target, scm_delivery_target_history, scm_deployment, and scm_deployment_history.
9. Proceed with step 1 in the ThingWorx Utilities upgrade procedure.
Timer Update Rate Values
The following tables list the update rate values to be adjusted for each timer and release.
|
Timer Name
|
Update Rate
|
|---|---|
|
TW.RSM.SFW.Timer.AutoRetryTimer
|
47000
|
|
TW.RSM.SFW.Timer.CheckStateTimer
|
41000
|
|
TW.RSM.SFW.Timer.DownloadTimer
|
53000
|
|
TW.RSM.SFW.Timer.InstallTimer
|
43000
|
|
TW.RSM.SFW.Timer.NotifyTimer
|
37000
|
|
TW.RSM.SFW.Timer.ScanDeploymentsTimer
|
67000
|
|
TW.RSM.SFW.Timer.StartDeploymentsTimer
|
29000
|
|
Timer Name
|
Update Rate
|
|---|---|
|
TW.RSM.SFW.Timer.AutoRetryTimer
|
31000
|
|
TW.RSM.SFW.Timer.CheckStateTimer
|
37000
|
|
TW.RSM.SFW.Timer.DownloadTimer
|
43000
|
|
TW.RSM.SFW.Timer.InstallTimer
|
47000
|
|
TW.RSM.SFW.Timer.NotifyTimer
|
29000
|
|
TW.RSM.SFW.Timer.StartDeploymentsTimer
|
41000
|
|
Timer Name
|
Update Rate
|
|---|---|
|
TW.RSM.SFW.Timer.AutoRetryTimer
|
31000
|
|
TW.RSM.SFW.Timer.CheckStateTimer
|
37000
|
|
TW.RSM.SFW.Timer.NotifyTimer
|
29000
|
|
TW.RSM.SFW.Timer.StartDeploymentsTimer
|
41000
|