Release Notes > Version 8.4 Release Notes > ThingWorx Analytics 8.4.3 Release Notes
ThingWorx Analytics 8.4.3 Release Notes
The following sections describe the enhancements, bug fixes, and known issues in ThingWorx Analytics 8.4.3.
Operating System Support Enhancement
Enhancement Description
Reference #
Red Hat Enterprise Linux (RHEL) 7.6
Both ThingWorx Analytics and Platform Analytics have been updated to support RHEL 7.6.
Bug Fixes
Bug Fix Description
Reference #
ThingWorx Analytics Installer: RabbitMQ yml file contains a typo
In the rabbitmq_report.yml file, a typo appears in the listenerPort string. The typo has been corrected.
ThingWorx Analytics Installer: The thingworx.isSecure property is set to False even when Use SSL is enabled during installation
During installation, when the Use SSL option is enabled, the thingworx.isSecure property should be set to True in the file. However, the property is being set to False regardless of the Use SSL value. This issue has been resolved so the thingworx.isSecure property is set correctly.
ThingWorx Analytics Installer: Fails when installing Analytics Extension using HTTPS
When the Analytics Server installer is launched using HTTPS, and the Analytics Extension is an included component for the installation, an error message is generated and the installation fails. This issue has been resolved so that the installation can complete successfully.
Platform Analytics Installer: An earlier version of Descriptive Analytics is not uninstalled
When the Platform Analytics installer is launched to install Descriptive Analytics, the installer cannot automatically remove any pre-8.4 versions of Descriptive Analytics that are already installed. The installer does not provide any notification that an earlier version exists. The resulting problem is that two versions of Descriptive Analytics may be installed and both try to communicate with the same ThingWorx server.
To mitigate this issue, a message has been added to the Platform Analytics installer warning that any previous installations of Descriptive Analytics must be manually removed before the 8.4 installer can run. In addition, removal steps have been added to the Analytics Help Center. See the Notes for Upgrading Descriptive Analytics in one of the following sections:
ThingWorx Analytics Server Installer: Error on Analytics Extension install or upgrade
When the Analytics Server installer is launched with the Analytics Extension as an included component, the Analytics configuration occasionally tries to execute before the microservices are connected to ThingWorx. When this situation occurs, during a fresh install or an upgrade, an error message is generated and the configuration must be handled manually. This issue has been resolved so that the Analytics configuration successfully completes automatically.
ThingWorx Analytics Server and Analytics Builder: Automated metadata detection does not work with an HTTPS ThingWorx instance
When ThingWorx Analytics is connected to a ThingWorx server that is configured for HTTPS communication, metadata cannot be detected automatically. A hardcoded non-HTTPS scheme prevents the automated detection. This issue has been resolved so that metadata detection works as expected when connected to an HTTPS ThingWorx instance.
Analytics Builder: Screens do not load properly in IE 11
The View Datasets and View Models screens do not load properly in the Internet Explorer 11 browser for the Windows operating systems. This issue has been resolved.
ThingWorx entity import: Error on importing entities that include an anomaly model
When importing entities from ThingWorx, an operating system-specific error occurs if the thing contains anomaly alerts. Specifically, if both your ThingWorx and your ThingWorx Analytics servers are installed on Windows operating systems, the error occurs and the import fails. This issue has been resolved so that these entities can be imported successfully.
Known Issues
Known Issue Description
Reference #
ThingWorx Analytics Server: Two-at-a-time Signals request does not return MI for all field combinations
When running a request for Signals, and specifying maxAtATime = 2, Mutual Information (MI), in relation to the goal, is not returned for all field combinations as expected. Instead, individual (one-at-a-time) MI scores are returned for all fields and then are filtered down to the top 25% most relevant fields. Two-at-a-time signals are calculated only for those fields. There is currently no way to modify this filtering behavior.
Analytics Manager: An existing simulation event fails if it is triggered after server restart
Analysis agents must be restarted after a ThingWorx server restart. Without restart of the agent, any new simulation jobs will fail to execute.
Analytics Manager: Time window event does not work for non-time series models
When a non-time series model is uploaded using the Analytics Server Connector, and all of the properties, including the key field are mapped, a time window event does not work.
Analytics Manager: The Replay progress bar does not update as expected
When a replay event is executed, the on-screen progress bar does not update as the replay event progresses. The issue is related only to the user interface (UI), and the actual execution of the replay is not affected. As a work around, refresh the browser or navigate to another tab and then return to the Replay tab. The progress bar will update. This UI issue will be resolved in a future release.
Analytics Builder: Filtering on list pages does not work as expected
When filtering is applied to a list page with multiple pages (such as the Models list page), the filtered results are not aggregated for display on a single page. Instead, the filtered results remain on their original pages and multiple pages must be clicked through to find all the filtered results.
To improve handling of list page displays, a configurable parameter has been added to set the number of table items that can be displayed per page. A more permanent resolution for the filtering with pagination issue will be provided in a future release.
ThingWorx Analytics Server: Some datasets with a large number of columns fail to upload
There are currently some limitations on the size and number of columns a dataset can contain. These limitations depend on the mix of data types your data includes. For specific information, see the Data section of Prepare Data and Metadata.
When trying to upload a dataset with a large number of columns, if the upload fails and an error message is generated, try the following workarounds:
Where possible, use optimal data types, for example, convert INTEGER data to STRING and use DOUBLE for numeric data.
Reduce the number of columns.
ThingWorx Analytics Server: When dataset or metadata field names begin with a number, server queries fail
When a field that begins with a number is included in a dataset or in metadata, most Analytics Server jobs can run successfully, such as training a model, running or scoring. However, when a server query is executed, such as a BinnedDistribution, the query fails. As a work around, avoid using field names that begin with a number.
This issue will be resolved in a future release so that field names can begin with numbers.
Platform Analytics Installer: Error occurs during upgrade
Typically, when upgrading to a new version of Platform Analytics, all of the services are stopped and then restarted when the upgrade is complete. Periodically, when upgrading from 8.4 0 or 8.4.1 to a newer version, the RabbitMQ service does not stop. In both Linux and Windows environments, the running service causes an error and prevents the upgrade from completing. This error will look similar to the following example:
As a work around, when this error is displayed, the RabbitMQ service must be stopped manually and the upgrade process relaunched. For specific instructions on stopping the RabbitMQ service manually, see one of the following troubleshooting procedures:
Linux – See the procedure called Work Around to Stop RabbitMQ for a Platform Analytics Upgrade. It’s the final section of Troubleshooting.
Windows – See the procedure called Work Around to Stop RabbitMQ for a Platform Analytics Upgrade. It’s the final section of Troubleshooting.
This issue will be resolved in a future release.
ThingWorx Analytics Server Installer: Silent mode installation error
The Analytics Server installer should not allow installation of Analytics Extension without Analytics Server. In both graphical and text mode installations, a warning message is displayed when the Analytics Extension component is selected for installation but Analytics Server is deselected. The installer will not continue unless Analytics Server is also selected. However, in the silent install mode, no such warning is displayed and the installer completes successfully with only the Analytics Extension installed. Of course the Extension cannot run without the Analytics Server so it is not usable.
This issue will be resolved in a future release.
Analytics Builder and Analytics Manager: Sizing of pop-up windows is distorted
When the Analytics Extension is deployed on the 8.3.1 version of ThingWorx platform, the display of some pop-up windows might look compressed in Analytics Builder and Analytics Manager. In some cases, scroll bars will allow you to view truncated fields. However, the best work around for the issue is to maximize your browser view so that the pop-up windows can display fully. This issue will be resolved in a future release.
End of Life Information
ThingWatcher was discontinued as a standalone SDK in 8.3. However, ThingWatcher functionality is available in the Anomaly Detection features native to the ThingWorx platform. For more information, see Anomaly Detection.
ThingPredictor software media is no longer available for download as of 8.3. However, support will continue for 8.x users until the next major release. To replace ThingPredictor capabilities, an improved set of predictive services is being introduced in 8.3. For more information, see How Predictive Scoring Using the Analytics Server Connector Works.
DataConnect / Data Analytics Definition
DataConnect and the Data Analytics Definition are not available as of 8.3. Replacement functionality will be introduced in a future release.
Was this helpful?