In-Place Upgrade
The in-place upgrade path is only applicable for upgrading from ThingWorx Navigate versions 9.3.0, 9.2.0, 9.1.0, and 9.0.0, installed using the installer. If you installed ThingWorx Navigate manually (without using the installer), migrate your ThingWorx Navigate to an instance that is installed using the installer. This will enable future in-place upgrades.
The ThingWorx Navigate Setup tool identifies your previous ThingWorx Navigate installation and guides you through the upgrade.
Before you begin with the upgrade, ensure that you have completed the steps in this topic.
 |
If you are upgrading from ThingWorx Navigate 9.2.0 and you wish to uninstall ThingWorx Flow since it is no longer a prerequisite for ThingWorx Navigate, ensure that you uninstall it only after you are done upgrading to ThingWorx Navigate 9.3.x.
|
Prepare for In-Place Upgrade
Before you begin upgrading, back up your custom tasks and save a copy of any changes you made to the deny list, formerly known as the blacklist. The sections that follow provide instructions for performing these steps.
Back Up Your Custom Tasks
If you have custom tasks that were built by modifying out-of-the-box ThingWorx Navigate extensions, make backups, so you can redeploy them after the upgrade. This prevents overwriting of these custom tasks during the upgrade process. For more information, see Best Practices for Developing Solutions in the ThingWorx Help Center.
If you are upgrading from ThingWorx Navigate 9.3.0, 9.2.0, 9.1.0, and 9.0.0, your custom tasks that were created using components will be automatically upgraded. It is not required to back up your custom tasks. However, it is a good practice to back up your custom tasks and review these tasks after the upgrade. If required, redeploy the custom tasks you backed up.
 | All BETA components used in custom mashups will be removed when you upgrade to ThingWorx Navigate 9.3.x. Plan to update your mashups after the upgrade with the 9.3.x version of those components. |
Save Your Changes to the Deny List
If you made any changes to the deny list, save a copy of your changes so you can reapply them after the upgrade. See the Add Attributes to the Deny List topic for more information.
Prerequisites for In-Place Upgrade
Upgrade ThingWorx Foundation
Before upgrading to ThingWorx Navigate 9.3.x, ensure that you have upgraded to the compatible ThingWorx Foundation version using the installer. Refer to the following steps:
2. Upgrade to the compatible ThingWorx Foundation version using the installer. For help with upgrade, refer to the Using the Installer to Upgrade ThingWorx Foundation topic from the ThingWorx Help Center.
| | ThingWorx Foundation 9.3.x requires JAVA 11. If you are upgrading from a version deployed with JAVA 8, install JAVA 11, import the relevant certificates from JAVA 8 into JAVA 11, and then proceed with upgrading ThingWorx Foundation. |
Review Windchill Requirements
Ensure you meet the Windchill requirements before you begin upgrading ThingWorx Navigate.
See the "Windchill Requirements" section in the Prerequisites topic for details.
Prerequisites for SSO Authentication
If you are upgrading from ThingWorx Navigate 9.2.0 and using the SSO authentication, perform the following steps before you begin upgrading:
1. It is recommended that your Windchill is up and running. If Windchill is down, your tailoring data will not be retained.
| | This step is only applicable if you are upgrading to ThingWorx Navigate 9.3.4 and later versions. |
2. Replace the ThingWorx Flow URL with the ThingWorx URL in the sso-settings.json file:
◦ Open the sso-settings.json file located in the $<installdir>\ThingworxPlatform\ssoSecurityConfig folder.
◦ Under BasicSettings, replace the ThingWorx Flow URL with the ThingWorx URL for the following keys: "clientBaseUrl" and "metadataEntityBaseUrl".
You can use the following code snippet for reference:
{
"BasicSettings":
{
"clientBaseUrl": "ThingWorx URL",
"metadataEntityBaseUrl": "ThingWorx URL",
"idpMetadataFilePath": "C:\\PROGRA~2\\ThingWorxFoundation\\ThingworxPlatform\\ssoSecurityConfig\\sso-idp-metadata.xml",
"metadataEntityId": "NAVIGATE_SP_8443",
"webSSOProfileConsumerResponseSkew": "300",
"webSSOProfileConsumerReleaseDOM": "true",
"webSSOProfileResponseSkew": "300",
"retriggerOnScopesRemoval": "true",
"samlAssertionUserNameAttributeName": "uid",
"samlAssertionMaxAuthenticationAge": "28800"
},
"BasicSettings":
{
"clientBaseUrl": "ThingWorx URL",
"metadataEntityBaseUrl": "ThingWorx URL",
"idpMetadataFilePath": "C:\\PROGRA~2\\ThingWorxFoundation\\ThingworxPlatform\\ssoSecurityConfig\\sso-idp-metadata.xml",
"metadataEntityId": "NAVIGATE_SP_8443",
"webSSOProfileConsumerResponseSkew": "300",
"webSSOProfileConsumerReleaseDOM": "true",
"webSSOProfileResponseSkew": "300",
"retriggerOnScopesRemoval": "true",
"samlAssertionUserNameAttributeName": "uid",
"samlAssertionMaxAuthenticationAge": "28800"
},
◦ Save the sso-settings.json file.
◦ Restart Apache Tomcat and ThingWorx Integration Runtime.
3. Update the PingFederate configuration with the ThingWorx URL. For more information, refer to the PTC Identity and Access Management Help Center.
Prerequisites for Fixed and Windchill Authentication
| | This step is only applicable if you are upgrading to ThingWorx Navigate 9.3.4 and later versions. |
It is recommended that your Windchill is up and running. If Windchill is down, your tailoring data will not be retained.