Platform Analytics 9.1 Release Notes
The following sections describe the new enhancements, bug fixes, and known issues in Platform Analytics 9.1.
Enhancements
|
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.
|
|
|
Platform Analytics and Analytics Server: Improved the password and key encryption script
The script available for updating encrypted passwords and keys has been simplified to require fewer parameters. It has also been expanded to cover automated encryption of additional keys and passwords to support the use of SSL. The encryptionscriptis stored in the install bin directory and the encrypted keys and passwords that it can update include:
• Analytics API Key
• ThingWorx AppKey
• RabbitMQ Password, Keystore Password, and Truststore Password
• ZooKeeper Keystore Password and Truststore Password
• Flink REST Keystore Password, Truststore Password, and Key Password
For more information about using the script, see Updating Encrypted Keys and Passwords.
|
TA-4764
|
|
Platform Analytics and Analytics Server: Added support for Java 11
In this release, support for operating with Java 11 has been added. Open JDK (Amazon Corretto) and Oracle are both supported.Operating with Java 8 continues to be supported. To begin using Java 11, you can either of the following:
• A clean install Platform Analytics or Analytics Server 9.1 on a server that is running Java 11
• An upgrade, on a server running Java 8, to Platform Analytics or Analytics Server 9.1 from an earlier version. Then upgrade the server from Java to Java 11 and manually update the necessary service files and SSL certificates to point to your Java 11 installation. For more information about these update procedures, see Upgrading from Java 8 to Java 11.
|
TA-4949
|
|
Platform Analytics: Added SSL protection for RabbitMQ
SSL protection for RabbitMQ has been added to the connection information requested during Platform Analytics installation. SSL support is available whether you are installing the provided RabbitMQ instance or pointing to an existing external instance. SSL protects the RabbitMQ connections between both theThingWorxserver and the Flink service. SSL support is optional but is enabled by default. For information about generating the necessary certificates and keys before installation, see SSL Support for RabbitMQ.
|
TA-5028
|
|
Platform Analytics: Added SSL protection for Apache Flink
SSL protection for Flink has been added to the connection information requested during Platform Analytics installation. SSL support is available whether you are installing the provided Flink instance or pointing to an existing external instance. SSL protects both of the following types of Flink connectivity:
• External – REST endpoint connections between Flink processes and any external tools or services.
• Internal – Communication between the Flink job manager and Flink task managers.
The REST and internal SSL connectivity can be configure separately. SSL support is optional but is enabled by default. For information about generating the necessary keystores and truststore before installation, see SSL Support for Flink.
|
TA-5029
|
Known Issues
|
Known Issue Description
|
Reference #
|
||
|---|---|---|---|
|
Platform Analytics: RabbitMQ service fails during upgrade
When upgrading to Platform Analytics 9.1, the RabbitMQ service fails. As a work around, the service can be stopped manually before retrying the upgrade. For information about handling this issue, see the troubleshooting article Stop RabbitMQ for a Platform Analytics Upgrade. The article includes procedures for both Linux and Windows.
This issue will be resolved in a future release.
|
TA-6627
|
||
|
Platform Analytics: Property Transform fails when modifying Flink SSL status
When you run a modify or repair your 9.1 installation, and change the Flink instance from SSL disabled to SSL enabled, the Property Transform microservice fails to start and its calculations do not work as expected. As a work around, perform the following steps:
1. Navigate to the flink-conf.yaml file located in the flink-1.11.1/conf folder of your Platform Analytics installation directory.
2. Update the rest.port parameter in the flink-conf.yaml file to match the port number defined in the flink.properties file in the installation directory.
3. Run the following command to restart all of the Platform Analytics TWPAS services:
./twpas.sh restart
The Property Transform functionality will operate as expected.
|
TA-6697
|
||
|
Platform Analytics: RabbitMQ SSL check box selection does not persist after a modify or repair
When Platform Analytics was previously installed with SSL for RabbitMQ disabled, this selection is not persisted during a modify or repair installation. The RabbitMQ SSL check box defaults to enabled, regardless of the previous installation selection.
This issue will be resolved in a future release.
|
TA-6716
|
||
|
Platform Analytics: Silent mode installation does not validate RabbitMQ and Flink SSL parameters
During silent mode installation, the RabbitMQ and Flink SSL parameters are not validated. If you enter an invalid value, the installation will continue but will not be successful. If your silent mode installation fails, ensure that the SSL parameters you are entering, for both RabbitMQ and Flink, are correct. Then retry the installation. This issue will be resolved in a future release.
|
TA-6829
|
||
|
Platform Analytics: In a Windows environment, modify/repair fails on an installation with existing/customer's Flink
When Platform Analytics is installed, in a Windows environment, using an existing/customer’s Flink, the modify/repair process fails because it references a rest.properties file that does not exist. As a work around, perform the following steps before launching a modify/repair installation:
1. Navigate to your Platform Analytics installation directory.
2. Copy the flink.properties file and rename the copied file rest.properties.
3. Launch the Platform Analytics installer.
The modify/repair will run successfully.
|
TA-6858
|
