Silent 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:
Silent mode installation of ThingWorx Analytics components is supported for the Windows environment. In contrast to the graphical mode, where the installation proceeds through a series of interactive steps, the silent installation requires that all of the necessary input be included in the launch command. The installation then takes place with no further interaction required.
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 Launch Command
To launch the silent installation in a Windows environment, open the Windows PowerShell (or the Command Prompt window) in Administrator mode and navigate to the directory where you saved the extracted launch files.
Run the following command, substituting specific information in the angled brackets:
.\ThingWorxAnalytics-<n.n.n>-windows-installer.exe --unattendedmodeui minimalWithDialogs --mode unattended --accept_eula YES --baseinstalldir "<base installation directory>" --THINGWORX_FOUNDATION_IP_ADDR "<IP address or host name>" --THINGWORX_FOUNDATION_PORT "<Port where ThingWorx is running>" --THINGWORX_APPKEY "<valid ThingWorx App Key>" --ANALYTICS_SERVER_THINGNAME "<name for the AnalyticsServer Thing>" --SSL_FOR_THINGWORX_CONNECTION "<false/true>" --UPLOAD_TWX_CERTIFICATE "<true/false>" --THINGWORX_CERTIFICATE_FILE_PATH "<path to a PEM or CER certificate file>" --THINGWORX_CERTIFICATE_ALIAS_NAME <alias name> --JAVA_TRUSTSTORE_PASSWORD <truststore password> --SSL_FOR_ANALYTICS_APIS "<false/true>" --ANALYTICS_SERVER_KEYSTORE_FILE_PATH "<path to keystore.jks file>" --ANALYTICS_SERVER_KEYSTORE_PASSWORD <keystore password> --ANALYTICS_SERVER_CERTIFICATE_ALIAS_NAME <alias name> --HOST_ADDRESS <IP Adress or FQDN of the primary adapter on the Analytics Server> --JAVA_TRUSTSTORE_PASSWORD <truststore password>
The following charts describes the information required for each parameter in the launch command:
Installation Directory
Launch Command Parameter
Description
--baseinstalldir
The path to the directory where the Analytics Server will be installed.
* 
If the installer detects a previous version of the ThingWorx Analytics Server, and you want to upgrade, the old installation directory is preselected for the baseinstalldir and you will not be able to change it. For more information, see Upgrade from an Earlier Version.
ThingWorx Connection Information
Launch Command Parameter
Description
--THINGWORX_FOUNDATION_IP_ADDR
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.
* 
If you are not integrating with ThingWorx, add the following disable parameter to the command and omit the other THINGWORX_FOUNDATION connection parameters:
--disable-components twas_twx_adapter
--THINGWORX_FOUNDATION_PORT
The port for communicating with your ThingWorx server.
* 
Can be omitted if you are not integrating with ThingWorx.
--THINGWORX_APPKEY
The value from the Key ID field of the application key you created in ThingWorx.
* 
Can be omitted if you are not integrating with ThingWorx.
--ANALYTICS_SERVER_THINGNAME
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.
* 
The AnalyticsServer Thing name must be unique within the server deployment.
* 
Can be omitted if you are not integrating with ThingWorx.
--SSL_FOR_THINGWORX_CONNECTION
Set to true in order to require the use of SSL when connecting to ThingWorx. The default value is false.
* 
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.
* 
Can be omitted if you are not integrating with ThingWorx.
--UPLOAD_TWX_CERTIFICATE
Set to true 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 false, but you will need to import the certificate manually if it is not uploaded by the installer. For more information, see Import a Self-signed SSL Certificate Manually.
* 
Can be omitted if you are not integrating with ThingWorx or if you are not using a self-signed SSL certificate.
--THINGWORX_CERTIFICATE_FILE_PATH
The location where the SSL certificate file is stored. This file is either a PEM or CER file.
* 
Can be omitted if you are not integrating with ThingWorx or if you are not using a self-signed SSL certificate that you want the installer to upload.
--THINGWORX_CERTIFICATE_ALIAS_NAME
An alias name that is assigned to the SSL certificate. Alias names are converted automatically to all lower case.
* 
Can be omitted if you are not integrating with ThingWorx or if you are not using a self-signed SSL certificate that you want the installer to upload.
--JAVA_TRUSTSTORE_PASSWORD
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.
* 
Can be omitted if you are not integrating with ThingWorx or if you are not using a self-signed SSL certificate that you want the installer to upload.
Launch Command Parameter
Description
--SSL_FOR_ANALYTICS_APIS
The default response is true. 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.
--ANALYTICS_SERVER_KEYSTORE_FILE_PATH
The location where the SSL Keystore file is stored. This file contains the signed SSL certificate.
--ANALYTICS_SERVER_KEYSTORE_PASSWORD
The password for the SSL Keystore.
--ANALYTICS_SERVER_CERTIFICATE_ALIAS_NAME
The alias name that is assigned to the signed SSL certificate. Alias names are converted automatically to all lower case.
--HOST_ADDRESS
IP address or fully qualified domain name of the primary network adapter on your ThingWorx Analytics Server. The value must match the SAN value provided on the SSL certificate.
--JAVA_TRUSTSTORE_PASSWORD
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.
* 
Can be omitted if you are not integrating with ThingWorx or if you are not using a self-signed SSL certificate that you want the installer to upload.
By default, when the installer runs, all Analytics Server components and Analytics Extension are included in the silent mode installation. However, you can choose to disable installation for certain components. For more information, see Disabling Components.
When the installation is complete, the command line prompt is returned.
* 
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.
Disabling Components
To disable one or more components during installation, add the following snippet to the installation launch command:
--disable-components <component_name>,<component_name>
The following chart describes the components that are available for installation:
Component
Component Name
Description
Async Microservice
async
Installs the Async 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
sync
Installs only the Sync Microservice.
Integration with ThingWorx
ThingWorx_Integration
This parameter must be selected if you plan to interact with ThingWorx Analytics via an integration with ThingWorx.
Analytics Extension
AnalyticsExtension
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.
Example:
To install only the Sync microservice and disable everything else, add the following to the installation command:
--disable-components async,AnalyticsExtension
* 
You still need the twas-twx-adapter to be installed if you plan to integrate with ThingWorx.
After Installation
To test the product installations, see:
* 
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.
Was this helpful?