ThingWorx Axeda Compatibility Package Release Notes, v.1.3.0
These release notes are for the ThingWorx Axeda Compatibility Package, version 1.3.0. Refer to the release notes for previous versions for information about changes made for those releases.
IMPORTANT! This release of the Axeda Compatibility Package is not compatible with ThingWorx Platform, v.9.0.x. You must upgrade to v.2.0.0 of the Axeda Compatibility Package to use ThingWorx Platform 9.0.x.
IMPORTANT! For security reasons, the ThingWorx IDM Connector is no longer available, starting with the 1.2.1 release. In addition, the IDM Agents (formerly Questra Service Agents) moved to End of Life in June 2020.
Security
This release of the ThingWorx Axeda Compatibility Package includes security-related updates, as follows:
• 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.
• See this technical support article for important recommendations regarding the use and update of third-party software for ThingWorx.
ACP Component Versions for Release 1.3.0
The following table shows the versions of the components included in this release of the Axeda Compatibility Package (ACP).
|
Component
|
Version
|
|---|---|
|
ThingWorx eMessage Connector
|
1.2.6
|
|
Axeda-ThingWorx Entity Exporter (ATEE)
|
1.2.3.1
|
|
ThingWorx Connection Services Extension (CSE)
|
1.6.0
|
|
ThingWorx Axeda Compatibility Extension (ACE)
|
3.0.43
|
|
ThingWorx Migrator for the Axeda Compatibility Extension (ACE)
|
3.0.43
|
|
ThingWorx Remote Access Extension (RAE)
|
1.2.1
|
|
ThingWorx Utilities Core (Thingworx-Utilities-Core-8-5-0.zip)
|
8.5.3-b51
|
|
ThingWorx SCM Extension (ThingWorx-Utilities-Software-Content-Management-8-5-3.zip)
|
8.5.3-b51
|
 |
For Remote Access, you need to download a Remote Access Client (RAC) separately from the Axeda Compatibility Package. If you have been using the most recent version of Axeda Desktop Viewer, you can continue to use that client.
|
Additional Software Requirements
The following table lists the additional, required software for this release of the Axeda Compatibility Package (ACP):
|
Required Product
|
Required Version
|
|---|---|
|
Java Development Kit (JDK)
|
To use 256-bit encryption with the Security Management Tool to encrypt the configuration file for the eMessage Connector, PTC recommends v.1.8.0_u162 or later (64-bit)
|
|
Linux 64-bit operating system
|
Tested on Linux 64-bit version of Ubuntu 16.04.6 LTS
|
|
Axeda Platform
|
v.6.9.0 or later to export users; otherwise, 6.8.0 or later
|
|
Axeda Global Access Server
|
v.6.9.2 or later
|
|
ThingWorx Platform
|
8.5.2 through 8.5.x
|
|
ThingWorx Remote Access Client (RAC)
|
1.1.0
|
|
Axeda Gateway Agent or Axeda Connector Agent
|
For security reasons, PTC strongly recommends that these Axeda Agents be at v.6.6.3 or later. In addition, if you require the remote interfaces configuration from Axeda Platform, the Agents must be at version 6.8.2. Refer to the Caution below.
|
 |
An issue with the Axeda Platform REST API prevents the ATEE from exporting remote interface data from Axeda Platform versions prior to 6.8.2. On the affected versions, any exported assets are treated as if they had no remote interfaces, and will not be compatible with the ThingWorx Remote Access Extension. The ATEE will record a log message, if debug logging is enabled, when it detects the REST API issue.
|
For ThingWorx Asset Advisor, version 8.5.2, is available on the Software Downloads page. On the Step 1 page, select THINGWORX FOUNDATION. On the Step 2 page, expand the nodes as follows: > > to locate the latest distribution bundles for ThingWorx Apps, ThingWorx Asset Advisor Integrations, and for remote sessions, ThingWorx Asset Remoting. The Datecode is SP2.
Issues Fixed in v.1.3.0 of the Axeda Compatibility Packcage
As part of PTC's ongoing efforts to improve security, this release of the eMessage Connector includes software fixes for potential security issues, as well as additional issues proactively identified by vulnerability scanning software or PTC QA testing. PTC strongly recommends upgrading to the latest version of the Axeda Compatibility Package as soon as possible to take advantage of security enhancements.
In addition to security enhancements, this release of the eMessage Connector includes software fixes provided in previous releases as well as the following changes:
|
ID (SFID)
|
Description
|
|---|---|
|
EMX-3539
|
Updates were made to work around a bug in versions of the Axeda Agent Embedded prior to version 6.9 that cause a crash of Axeda Agent Embedded during file download.
|
|
CXS-861
|
Non-administrative users could not use remote access in the ThingWorx Platform, v.8.5.2.
Security permissions changed in ThingWorx Platform v.8.5.2. New releases of the Connection Services Extension (CSE) and the Remote Access Extension (RAE) are required for compatibility. The versions of the CSE (1.6.0) and RAE (1.2.1) provided in this package require ThingWorx Platform v.8.5.2 through 8.5.x. Do not use these extensions with ThingWorx Platform 9.0.x.
|
ThingWorx eMessage Connector, v.1.2.5, Release Notes
As part of PTC's ongoing efforts to improve security, this release of the eMessage Connector includes software fixes for potential security issues, as well as additional issues proactively identified by vulnerability scanning software or PTC QA testing. PTC strongly recommends upgrading to the latest version of the Axeda Compatibility Package as soon as possible to take advantage of security enhancements.
In addition to security enhancements, this release of the eMessage Connector includes software fixes provided in previous releases as well as the following changes:
|
ID (SFID)
|
Description
|
|---|---|
|
EMX-3391 (15170045)
|
An SCM deployment with an instruction to download a file failed for Axeda Agent Embedded.
With this release, it is possible to download a file successfully to Agent Embedded. However, it does not mean that the eMessage Connector fully supports Agent Embedded yet. Keep in mind the following limitations of Agent Embedded:
• Agent Embedded does not handle compressed files.
• Agent Embedded supports only Upload, Download, and agent Restart instructions.
• Agent Embedded does not support the Execute instruction that can be added for a ThingWorx SCM instruction-based package.
|
|
EMX-3408 (15166839)
|
The SCM Execute instruction should be synchronous by default.
With this release of the eMessage Connector, the SCM Execute instruction is synchronous by default.
|
|
EMX-3451 and UTL-5962
|
Software fixes for security-related issues.
|
|
EMX-3482
|
The Download Instruction of an SCM package for the ThingWorx Platform differs in behavior from the Download Instruction of an SCM package for the Axeda Platform. On the Axeda Platform, a Download Instruction compresses the file to download by default, unless the user explicitly selects a check box stating not to compress the file before downloading. If you choose not to compress the file, read and write access are provided only to the user context of the user who started the Axeda agent.
On the ThingWorx Platform, there is no option to compress the file before downloading and the file is transferred uncompressed. As a result, when a Download Instruction sent from ThingWorx completes, the file permissions of the file after the download are the same as if you chose not to compress the file on Axeda Platform.
To work around this limitation on ThingWorx, you can manually compress the file before including it in your SCM package and select the Agent should uncompress this file after downloading check box when adding the Download Instruction to your SCM package.
|
|
EMX-3383
|
eMessage Connector 1.2.4 will not start up on Windows machines if the Connector home path is sufficiently long
This issue is for Windows only. To avoid it, install the Connector in a location that results in a short path to the start-up script for the Connector. The documentation has been updated to explain how to avoid it and how to resolve it.
|
ThingWorx eMessage Connector, v.1.2.4, Release Notes
The ThingWorx eMessage Connector is a component of the ThingWorx Axeda Compatibility Package (ACP).
As part of PTC's ongoing efforts to improve security, this release of the eMessage Connector includes software fixes for potential security issues, as well as additional issues proactively identified by vulnerability scanning software or PTC QA testing. PTC strongly recommends upgrading to the latest version of the Axeda Compatibility Package as soon as possible to take advantage of security enhancements.
In addition to security improvements, this release of the eMessage Connector provides the following changes:
|
ID (SFID)
|
Description
|
|---|---|
|
EMX-3332
|
eMessage Connector — ThingWorx 8.5 support
The eMessage Connector v.1.2.4 has been tested with ThingWorx Platform, v.8.5.0 and v.8.5.1.
|
|
EMX-3340
|
Build eMessage Connector with new libraries for the ThingWorx Security Management Tool
The eMessage Connector v.1.2.4 provides the following updates:
• Upgrades to support the latest version of the ThingWorx Security Management Tool (needed to encrypt the configuration file). Note that this upgrade requires Java 1.8_u141 or later if you want to use 128-bit encryption or Java 1.8_u162 or later if you want to us 256-bit encryption.
• Updated the Smoke Test utility to support an encrypted configuration file.
• Upgraded Open Source libraries.
|
|
EMX-3347
|
Update services that grant permissions to grant EventSubscribe runtime permission to the eMessage Connector.
In the 8.5.0 release of ThingWorx Platform, the EventSubscribe run time permissions are needed to run a subscription associated with an event.
The GrantEMessageConnectorPermissions service now grants EventSubscribe Run Time permission to the non-admin user/user group of the Connector. If an event subscription script is rejected by the ThingWorx Platform, make sure that you have run this permissions-granting service.
|
ThingWorx Axeda-ThingWorx Entity Exporter (ATEE) v.1.2.2 Release Note
As part of PTC's ongoing efforts to improve security, this release of the ATEE includes software fixes for potential security issues, as well as additional issues proactively identified by vulnerability scanning software or PTC QA testing. PTC strongly recommends upgrading to the latest version of the Axeda Compatibility Package as soon as possible to take advantage of security enhancements.
Axeda Compatibility Extension (ACE) v.3.0.43 Release Note
The following table lists and briefly describes the previously known issue that has been fixed in this release:
|
Issue ID
|
Description
|
|---|---|
|
ACE-115
|
ACE import has an error message because runAsUser is not set on the AxedaRemoteViewerRefreshScheduler.
The runAsUser field for all Timers and Schedulers in the ACE are now set to System by default.
|
About ThingWorx Remote Access Extension (RAE) v.1.1.0 and ThingWorx Remote Access Client, v.1.0.4
The ThingWorx Remote Access Extension (RAE), v.1.1.0, and ThingWorx Remote Access Client, v.1.0.4, have been verified against ThingWorx Platform, v.8.5.0. While the RAE is provided in the Axeda Compatibility Package, the RAC must be downloaded separately, from the ThingWorx Remote Access Client Downloads page.
As part of PTC's ongoing efforts to improve security, the 1.1.0 release of the RAE and the 1.0.4 release of the RAC included software fixes for potential security issues, as well as additional issues proactively identified by vulnerability scanning software or PTC QA testing. PTC strongly recommends upgrading to the latest versions of the Axeda Compatibility Package and the RAC as soon as possible to take advantage of security enhancements.
The 1.0.4 release of the RAC included the following additional software fix:
|
Issue ID (SFID)
|
Description
|
|---|---|
|
TW-65634 (15018378)
|
Added user-agent header with value ThingWorx Remote Access Client to the ThingWorx connection request to the Thingworx/WebSocket endpoint.
|
Known Issues - ThingWorx Software Content Management Extension
The following table lists and briefly describes known issues for the ThingWorx Software Content Management Extension and ThingWorx Platform:
|
Issue ID
|
Description
|
|---|---|
|
UTL-5611
|
After importing the SCM extension bundle, a warning message about the extension trying to overwrite existing entities may appear. This message is expected and does not cause an issue. You can ignore it. In addition, refer to Importing ThingWorx Utilities Core and the SCM Extension.
|
|
UTL-5462
|
Delivery target times out of the Instructions Received state when its installation date is set too far in the future. Currently, the Instructions Received timeout does not take the installation date into account. For now, be sure that installation dates and the Instructions Received timeout are configured in such a way that package installation will being on the targeted devices before the Instructions Received timeout is exceeded.
|
|
EDGA-1853
|
The Axeda Connector Agent ignores the deviceRelativePath setting for SCM deployments. The deployment of a package with the following Download instruction succeeds when it should fail::
• Destination: /
• SourceFiles: ["C:\\qsaconfig.xml"]
• RepositoryName: TW.RSM.Thing.FileRepository
This same deployment to an Axeda Gateway device or a device managed by an Axeda Gateway Agent fails as expected.
|
Known Issues - Axeda-ThingWorx Entity Exporter (ATEE)
The following table describes the known issue for ATEE operating with Axeda Platform:
|
Issue ID
|
Case
|
Description
|
|---|---|---|
|
CORE-4376
|
113580
|
Gateway Asset Link is missing
This issue affects Axeda Platform, versions 6.8.0, 6.8.1, and 6.8.2, and impacts the Axeda-ThingWorx Entity Exporter (ATEE) as follows:
• Prevents the ATEE from populating the Managed Devices infotable on Things that represent Axeda Gateway entities in ThingWorx.
• Prevents the ATEE from populating the gatewayId on Things that represent Axeda Managed Device entities in ThingWorx.
|
Known Issues - eMessage Connector
The following table lists and describes the known issues for the eMessage Connector in this release:
|
Issue ID
|
Description
|
|---|---|
|
EMX-607
|
In the unlikely event of a setDataItem service call failing, the ThingWorx Platform does not receive a notification event. It would be better if the eMessage Connector could notify ThingWorx Platform of this event
|
|
EMX-1749
|
File transfers to the ThingWorx Platform instances that are running on the Windows OS are subject to the file naming restrictions of Windows, including the use of special characters such as question mark, colon, and so on. Refer to https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx
|
|
EMX-1892
|
eMessage XML is incomplete and does not send specific information back to the agent in the status message. This did not appear to cause issues with the Axeda agents that were tested; it is just a difference between the Axeda Platform and the eMessage Connector.
|
|
EMX-1893
|
Invalid Axeda alarms result in a blank value being written to the alarm field. Axeda Platform would reject these bad values. This is a difference between Axeda and the eMessage Connector.
|
|
EMX-2178
|
In eMessage Connector, if a configuration value is not provided, the helper method that is used to obtain it (except getIntegerValue() and getLongValue()) throws a ConfigException
|
|
EMX-2193
|
Axeda Gateway agents receive too much xml when registering. Currently, a redundant SetPingServlet is returned to Gateway agents. This has no known effects on the agents.
|
|
EMX-2198
|
Currently, selecting the time zone, Asia/Riyadh87, causes an error in the eMessage Connector, saying that the time zone was not valid, even though it is one of the time zones in the TimezoneMapper class.
|
|
EMX-2232
|
When a download request is issued from the ThingWorx Platform with targetPath:<empty>, the job eventually transitions to a state of CANCELLED, and a null pointer exception is observed in the Connector log.
|
|
EMX-2319
|
After starting the eMessage Connector, the logs directory is in a subdirectory from the current working directory and not where one would expect, at $EMESSAGE_CONNECTOR_HOME/logs.
|
|
EMX-2412
|
NotifyPropertyUpdates invocations to the eMessage Connector are not handled, resulting in a WARN message being logged. The operation of the Connector is not affected.
|
|
EMX-2482
|
When performing a download that is relative to the agent's home directory, use only the forward slash ("/") to specify the root directory and not "./". Using "./" results in the ThingWorx Platform sending an empty value to the Connector, which triggers an error being logged in the eMessage Connector. In addition, the file transfer will not complete successfully.
|
|
EMX-2486
|
Certain scenarios can create a flood of Thing look-ups to the ThingWorx Platform. The most likely cause for this situation is if an eMessage Connector fails unexpectedly and is restored while experiencing many requests per second for different agents (~10+ new agent communications per second). During this scenario the eMessage Connector can cause strain on ThingWorx Platform.
|
|
EMX-3083
|
Older agents using protocols that have been deemed insecure may experience issues connecting, such as agents utilizing SSLv2Hello. This issue will be resolved in an upcoming release.
|