ThingWorx Analytics Installation > ThingWorx Analytics Linux Installation > Analytics Server Installation for Linux > Text Mode Installation
  
Text Mode Installation
This procedure documents installation for the 8.5.x release. If you need installation information for one of the following earlier releases, use the links below to open earlier PDF installation guides maintained on the PTC eSupport Portal:
Release 8.4
Release 8.3
Release 8.2
Release 8.1
* 
This procedure represents the text installation mode, typically used in a Linux environment. For launch information using Graphical or Silent installation modes, see Graphical Mode Installation or Silent Mode Installation
Before Installation
Make sure all of the prerequisites have been met.
Download the appropriate installer files for your operating system.
Extract the downloaded files to a location on your host system.
Installation Steps
1. Open a terminal window and, as root user, launch the installer command: ./ThingWorxAnalytics-<n.n.n>-linux-x64-installer.run
* 
An advanced option is available if you want to override the default user account during the installation. For more information about launching the installer with this option, see Change the User Account.
2. Accept the license agreement. Press Enter.
3. Select the ThingWorx Analytics products you want to install.
The default response for each component is y for Yes. You can press Enter to accept it and move on to the next component or clear it by changing it to n for No.
The components available for installation include the following:
Analytics Server
Select either one or both of the following components:
Async Microservice
Installs the Asynchronous Microservice along with other necessary components, including ZooKeeper and Analytics Common Workers. During the installation, three Workers are installed but the number of Workers can be scaled up when the installation is complete. For information, see Scale the Number of Workers.
Sync Microservice
Installs only the Synchronous Microservice.
Integration with ThingWorx
The following components involve integration with ThingWorx:
ThingWorx Adapter for Analytics Server
This adapter generates the Analytics Things that can be accessed in ThingWorx Composer. It is selected by default if you have selected the Integration with ThingWorx parameter. If you plan to interact with ThingWorx Analytics via ThingWorx, this parameter is required.
Analytics Extension
Must be selected if you plan to use Analytics Builder or Analytics Manager. Analytics Extension can only be used if both the Async and the Sync Microservices are installed.
4. Specify an installation directory. You can accept the default or provide a different location.
* 
If the installer detects a previous version of the ThingWorx Analytics Server, and you want to upgrade, the old installation directory is preselected and you will not be able to change it. For more information, see Upgrade from an Earlier Version.
5. Enter ThingWorx connection information, including the following parameters:
* 
If you opt not to select the ThingWorx Adapter for installation, ThingWorx connection information will not be requested.
Parameter
Description
ThingWorx IP Address or Host Name
Enter the IP address or host name of your ThingWorx server, which must already be installed and running.
* 
If you are using SSL for your connection to ThingWorx, this IP Address or Host Name must match the SAN address or host used to create the ThingWorx SSL certificate.
* 
Use of the server’s primary, outward-facing IP address or host name is preferable for configuring the ThingWorx server connection. Even if ThingWorx and Analytics Server are hosted on the same server, using local host can cause problems when the SaveJobResult service is run to access saved results from outside of the server.
ThingWorx Port
Enter the port for communicating with your ThingWorx server.
ThingWorx AppKey
Enter the value from the Key ID field of the application key you created in ThingWorx.
Analytics Server Thing Name
Enter a name for the AnalyticsServer Thing that is created in ThingWorx during the Analytics Server installation. This full name is attached as a prefix to each microservice name. This Thing name must be unique within the server deployment.
SSL for ThingWorx Connection
Set to y for Yes in order to require the use of SSL when connecting to ThingWorx. The default value is n for No.
* 
In order to enable SSL support for the connection with ThingWorx, a signed SSL certificate must already be in place before installation can begin. See SSL Support for ThingWorx.
If you do not opt to use SSL for the connection to ThingWorx, continue with Step 6. If you enable SSL for the ThingWorx connection, complete the remaining parameters in this step.
Upload a Self-signed ThingWorx SSL Certificate
Set to y for Yes if you are using a self-signed ThingWorx SSL certificate and you want to allow the installer to upload it automatically. The default value is n for No, but you will need to import the certificate manually if you select No. For more information, see Import a Self-signed SSL Certificate Manually.
SSL Certificate File
Enter the path to the location where the SSL certificate file is stored. This file is either a PEM or CER file.
ThingWorx Certificate Alias Name
Enter an alias name that is assigned to the SSL certificate. Alias names are converted automatically to all lower case.
Java Truststore Password
Enter the password for the Java Truststore, a file where trusted SSL certificates are stored. The Truststore is created automatically, with a default password, when Java is installed. For more information about Java Truststore passwords, see Working with Certificates and SSL on the Oracle website.
6. Enter SSL connection information for the ThingWorx Analytics microservices, including the following parameters:
Parameter
Description
Use SSL for Analytics Microservices
The default response is y for Yes. You can press Enter to accept it and move on to the next parameter or clear it by changing it to n for No. When SSL authentication support is enabled for the microservices, communication is protected between the ThingWorx Adapter and the Analytics APIs. Communication between the APIs is also secured.
* 
In order to enable SSL support for the microservices, a signed SSL certificate must already be in place before installation can begin. See SSL Support for Analytics Server APIs.
SSL Keystore file
Enter the path to the location where the SSL Keystore file is stored. This file contains the signed SSL certificate.
SSL Keystore Password
Enter the password for the SSL Keystore.
Certificate Alias Name
Enter the alias name that is assigned to the signed SSL certificate. Alias names are converted automatically to all lower case.
Host IP Address or Fully Qualified Domain Name to access Analytics microservices
Enter either an IP address or a fully qualified domain name for the primary network adapter on your ThingWorx Analytics Server. The value must match the SAN value provided on the SSL certificate.
Java Truststore Password
Enter the password for the Java Truststore, a file where trusted SSL certificates are stored. The Truststore is created automatically, with a default password, when Java is installed. For more information about Java Truststore passwords, see Working with Certificates and SSL on the Oracle website.
When you press Enter at the completion of this step, the installation begins. Depending on your operating system, several windows may open and then close while the process unpacks and installs the necessary libraries and settings. When the installation process is complete, an installation summary is displayed.
7. To view the entire summary, continue clicking Enter to scroll through the list of installed components.
8. To test the product installations, see:
Verify the ThingWorx Analytics Server Installation
Verify the Analytics Extension Installation
* 
The Analytics Extension installation is not complete until you perform the necessary post-installation configuration steps. For information about these steps, see Perform Post Installation Configuration for Analytics Builder or for Analytics Manager.