Analytics Server 9.2.2 Release Notes

Enhancement Description	Reference #
ThingWorx Analytics: security improvements Fixed potential security issues, including items proactively identified by vulnerability scanning software or PTC Quality Assurance testing. Please upgrade as soon as possible to take advantage of these important improvements. For important recommendations about the use and update of third-party software, see technical support article CS320194.
Anomaly Alert: Validation added to ThingWorx Composer New validation has been added to Anomaly Alert processing. When creating an anomaly alert, the new validation confirms that the Analytics Gateway is configured properly and connected. Appropriate error messages are displayed so that issues can be resolved in a timely fashion.	TA-7734
Anomaly Alert: Validation added to the ThingWorx AddOrUpdateAlert service In ThingWorx, if the Alert Processing Subsystem is not configured to point to the Analytics Server, anomaly alerts cannot be created. Previously, when an anomaly alert was created on a Thing, this connection was not validated during the alert creation. The anomaly alert still went through the calibration stage and then failed on training with an unclear message. With this release, validation has been added so that proper configuration of the Alert Processing Subsystem is confirmed. Anomaly alerts will not be created if the configuration is invalid. Clear error messages have been added to the process. This validation has been added for Anomaly Detection in the standalone mode only. It will be added for ThingWorx cluster mode in the next release.	TA-6973 TA-6976

Bug Fix Description

Reference #

Analytics Server and Analytics Builder: Predictive scoring limitation on large datasets

There is currently a dataset size limit of 9 million rows by 30 columns for predictive scoring. When scoring is run on a larger dataset, an error is generated and scoring fails. This issue has been resolved by making a specific buffer maximum flag available in the system-environment-variables.properties file. The maximum size of this flag can be increased. For more information, see Handling Large Datasets.

TA-6780

Analytics Manager: Performance issues when running discrete analysis events

When running discrete analysis events, where a new job is created for every event trigger, performance issues are occurring. Either the data sent from ThingWorx to the agent is not processed in a timely manner, or the agent appears to stop working. The faster data is scheduled for processing, the faster the agent fails. This issue has been resolved.

Before using this version of Analytics Manager, all Java SDK agents must be recompiled. For more information, see Build an Agent Using Java SDK.

TA-7374

TA-7375

ThingWorx Analytics: Distribution statistics queries and synchronous scoring jobs fail because temp files cannot be stored

When a distribution statistics query or a synchronous scoring job is executed on a Linux server, the system cannot write to /tmp directory that is mounted with noexec permissions. This issue has been resolved.

TA-7709

Analytics Server Installation: SSL issue prevents connect to ThingWorx in a Windows environment

When installing Analytics Server on Windows, and using a self-signed SSL certificate to protect the connection with ThingWorx, the installation fails to connect to ThingWorx. The issue was introduced when the product moved away from using Java CA cert. This issue has been resolved so that self-signed certificates can be used in both Windows and Linux installations.

TA-7743

Analytics Server: Manually created jobs with no filter cause errors in Builder

When a signals, profile, model, or predictive scoring job is created manually through Analytics Server microservices, and the DataRef filter is left blank, other jobs disappear from display on Analytics Builder list pages. This issue has been resolved so that all jobs display in Analytics Builder as expected.

TA-7876

Known Issue Description	Reference #
Analytics Builder: Scoring records from a REST request are not displayed correctly When a predictive scoring job is submitted via a REST API request, the information displayed on the Model list page in Analytics Builder is incorrect. The Number of Records Scored column should reflect the number of data rows submitted in the REST request. Instead, it displays a value of 0. This issue will be resolved in a future release.	TA-4715
Analytics Builder: Signal job results not cleared in Chrome browser When a filter is applied to the Signals list page and results in no matching jobs, the list is not cleared properly in a Chrome browser and previous results are displayed. This issue will be resolved in a future release.	TA-4972
Analytics Server: A large dataset can slow the display performance of model results When a model is created using a large dataset (1 GB or more), the display of the model results can be slow. To avoid a timeout failure, change the timeout settings as follows: 1. In your ThingWorx installation directory, navigate to the ThingworxPlatform/platform-settings.json file and open it. In the BasicSettings section, add a new ScriptTimeout parameter as follows: "PlatformSettingsConfig": { "BasicSettings": { "ScriptTimeout": "3000" }, 2. Restart your ThingWorx server. 3. Log into ThingWorx Composer and navigate to Security > Subsystems > WSCommunicationsSubsystem > Configuration > Amount of time a request will wait for the response message before timing out (secs). Change the value to 3000. Changing the timeout settings will not resolve the slow performance but it will prevent a timeout failure. This issue will be resolved in a future release.	TA-6766
Analytics Manager: Empty analysis replay instance created When an analysis replay is created and it does not include data for the specified time frame, an error is generated. However, an empty analysis replay instance is still created containing no records. The empty instance must be deleted before another replay can be created for the same time frame. This issue will be resolved in a future release.	TA-7619
Anomaly Alert: Returns an inaccurate error message during modification When modifying an existing anomaly alert on a Thing in ThingWorx Composer, an inaccurate error message displays saying that the selected Analytics Gateway does not exist. As a work around, change the Alert Type to something other than Anomaly, make the desired modification, and then switch the Alert Type back to Anomaly. This issue will be resolved in a future maintenance release.	TA-8012

Confidence Model Scoring for Boolean and Categorical Goals
In ThingWorx Analytics Server 8.5, confidence models for Boolean and categorical goals could be created during training. When these confidence models are scored, the scoring output includes confidence interval information along with the prediction results. In a future release, the confidence interval information will no longer be returned as part of the scoring results for confidence models created in Analytics Server 8.5 with Boolean or categorical goals. In preparation for future upgrades, you should update any application code that is related to scoring these types of models. Ensure that your application code does not rely on the confidence interval results.

Confidence Model Scoring for Boolean and Categorical Goals

In ThingWorx Analytics Server 8.5, confidence models for Boolean and categorical goals could be created during training. When these confidence models are scored, the scoring output includes confidence interval information along with the prediction results. In a future release, the confidence interval information will no longer be returned as part of the scoring results for confidence models created in Analytics Server 8.5 with Boolean or categorical goals. In preparation for future upgrades, you should update any application code that is related to scoring these types of models. Ensure that your application code does not rely on the confidence interval results.