Installing ThingWorx Navigate—Let’s go! > Prerequisites and Known Issues
  
Prerequisites and Known Issues
In this topic, you’ll find the prerequisites for ThingWorx Navigate. These include requirements for software versions, the ThingWorx platform, Windchill, and web browsers.
Software prerequisites
• Java SE Development Kit 8, Update 92, 1.8.0_92–b14 (64–bit)
• Software, databases, and web browsers—For the most up-to-date information on the software versions supported by this release of ThingWorx Navigate, check the Platform Support Matrix for ThingWorx Navigate.
• No previous installation of ThingWorx Integration Runtime. If you have Integration Runtime installed, uninstall now. The instructions are below.
Uninstall ThingWorx Integration Runtime
On Windows machines:
1. From the Control Panel, uninstall ThingWorx Integration Runtime.
2. Remove it from the registry: open the Registry Editor, regedit.exe.
3. Expand the SYSTEM folder, and then expand ControlSet001 and Control.
4. In the Control folder, right-click Thingworx-IntegrationRuntime and select Delete.
On Linux machines, an administrative user can perform these steps:
1. To start ThingWorx Integration Runtime, you run a Java command from the command prompt. Make sure this command prompt is closed.
2. Remove these files from the ThingWorxPlatform folder:
◦ integration-runtime-settings.json
◦ integration-runtime-<version>.jar
Windchill requirements
These are the requirements for Windchill:
• Windchill—Check the matrix for the supported versions.
• PTC Windchill Extension for ThingWorx—Includes a patch that corresponds with the Windchill release you have installed.
Diagram: ThingWorx deployment with Windchill
ThingWorx deployment with Windchill
Required browser setting for Microsoft Internet Explorer
The supported web browsers are listed in the Platform Support Matrix.
ThingWorx Navigate does not support Microsoft Internet Explorer’s Compatibility View. If your organization uses Internet Explorer, we recommend you roll out the following settings in Internet Explorer’s Compatibility Settings dialog box to your users:
• Display intranet sites in Compatibility View—Make sure this check box is cleared.
• Websites you’ve added to Compatibility View—Remove the URL and hostname for the Windchill server and the ThingWorx Navigate server from the list.
Requirements for SSL certificates
All certificates that you provide in the installation and configuration tools must be in Java KeyStore (*.jks) format.
Required settings for environment variables
Before you run ThingWorx Navigate Setup, make sure that you set these environment variables:
• JAVA_HOME—<JDK directory>
• PATH—<JDK_DIRECTORY>/bin
Do not set the variables to JRE.
Prerequisites for Windows Server 2016 installations
Database Name
Local database
Remote database
PostgreSQL 9.4.5, 9.5.11, 9.6 and 10
• PostgreSQL should be installed
• Path to PostgreSQL/bin must be in the PATH environment variable.
• Allowed connections to PostgreSQL from the ThingWorx Navigate host by updating pg_hba.conf located at \PostgreSQL\<Version>\data folder.
• On the machine where your postgres is installed, do the following:
◦ Ensure PostgreSQL/bin is in the PATH environment variable of the machine where postgres is installed
◦ Allowed connections to PostgreSQL from the ThingWorx Navigate host by updating pg_hba.conf located at \PostgreSQL\<Version>\data folder.
For example, if ThingWorx Navigate is installed on the same host as PostgreSQL, you can update pg_hba.conf to allow connections as follows:
# "local" is for Unix domain socket connections only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
• On the remote machine where you want to run the ThingWorx Navigate Installer, do the following:
◦ Install the psql client that is compatible with your PostgreSQL version.
◦ Add the installed psql to the PATH environment variable. Follow these steps:
2. Install the pgadmin client.
3. Update the PATH environment variable to append to the path where pgsql client is installed.
Microsoft SQL Server 2016
• The host on which ThingWorx Navigate is to be installed must have access to Microsoft SQL Server 2016
• Make sure that Microsoft SQL client (sqlcmd) is installed and is available in the PATH environment variable.
• A Microsoft SQL user with Administrator access.
• A Microsoft SQL user with Administrator access
• A valid Microsoft SQL client (sqlcmd) is installed and is available in the PATH environment variable.
Prerequisites for Red Hat Enterprise Linux 7.5 installations
• Red Hat 7.5 or CentOS 7.5 with Administrator access
• Software Collections enabled:
Red Hat
yum-config-manager --enable 'Red Hat Enterprise Linux Server 7 RHSCL (RPMs)'
yum-config-manager --enable 'Red Hat Enterprise Linux Server 7 Extra(RPMs)'
yum-config-manager --enable 'Red Hat Enterprise Linux Server 7 Optional (RPMs)'
yum-config-manager --enable 'Red Hat Enterprise Linux Server 7 RH Common (RPMs)'
yum-config-manager --enable 'Red Hat Enterprise Linux Server 7 Supplementary (RPMs)'
CentOS
yum install 'centos-release-scl'
• Enable EPEL repository
◦ Red Hat (Download and install)
wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
yum localinstall epel-release-latest-7.noarch.rpm
◦ CentOS
yum install 'epel-release'
Database name
Local database
Remote database
PostgreSQL 9.4.5, 9.5.11, 9.6 and 10
• The host on which ThingWorx Navigate is to be installed must have access to a PostgreSQL server.
• PostgreSQL is installed, and the path to PostgreSQL/bin should be in the PATH environment variable.
• A PostgreSQL user with administrator roles (SUPERUSER, CREATEUSER, or CREATEROLE).
The ThingWorx Navigate installer will create a user for the application.
• Allow connections to PostgreSQL from the ThingWorx Navigate host by updating pg_hba.conf located at \PostgreSQL\<Version>\data folder.
For example, if ThingWorx Navigate is installed on the same host as PostgreSQL, pg_hba.conf can be updated to allow connections as follows:
$ cat /var/lib/pgsql/9.6/data/pg_hba.conf
...
# "local" is for Unix domain socket connections only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
On the machine where your postgres is installed, do the following:
• Ensure PostgreSQL/bin is in the PATH environment variable of the machine where postgres is installed
• Allowed connections to PostgreSQL from the ThingWorx Navigate host by updating pg_hba.conf located at \PostgreSQL\<Version>\data folder.
For example, if ThingWorx Navigate is installed on the same host as PostgreSQL, you can update pg_hba.conf to allow connections as follows:
$ cat /var/lib/pgsql/9.6/data/pg_hba.conf
...
# "local" is for Unix domain socket connections only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
• On the remote machine where you want to run the installer, do the following:
◦ Run following command to install psql client:
yum install rh-postgresql96-postgresql-syspaths
Microsoft SQL Server 2016
Not supported
• The host on which ThingWorx Foundation is to be installed must have access to Microsoft SQL Server 2016.
• A valid Microsoft SQL client is installed (sqlcmd) and is available in the PATH environment variable.
• A Microsoft SQL user with administrator rights.
Install sqlcmd.
For installation instructions, see https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-tools?view=sql-server-2017#RHEL. After installation, run the following:
ln -s /opt/mssql-tools/bin/sqlcmd /usr/bin/sqlcmd
Known issues for the ThingWorx Navigate installation tools
The installation, licensing, and configuration tools have the following known issues:
• You cannot run ThingWorx Navigate Setup multiple times on the same machine.
• For Linux, the progress bar looks complete even while the installation is in progress.
• If you have an expired trial license, you cannot use the ThingWorx Navigate Licensing tool to upgrade to a paid license. Make sure to upgrade your license within 30 days to avoid this problem.
• For all configuration types, no validation is performed on your Windchill connection. Enter the connection information carefully.
• The configuration log file contains incomplete information about the Windchill version and CPS number. You can obtain this information from Windchill.
This issue is addressed in a future release of ThingWorx Navigate.