ThingWorx Axeda Compatibility Package Release Notes, v.1.3.1
These release notes are for the ThingWorx Axeda Compatibility Package, version 1.3.1 Refer to the release notes for previous versions for information about changes made for those releases.
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) are deprecated and moved to End of Life in June 2020.
 |
The ThingWorx Axeda Compatibility Package for Axeda eMessage Agents Help Center is updated outside of releases. For information on what has changed in this help center, go to What’s New in This Help Center?. Also, information for previous releases is available in the Release Notes section of this Help Center.
|
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.1
Starting with v.1.3.1 of the ThingWorx Axeda Compatibility Package, the Axeda-ThingWorx Entity Exporter (ATEE) tool is no longer distributed with the package. Axeda customers who want to migrate to ThingWorx should contact the PTC Axeda Transition Team for assistance with their migration. Accordingly, information about ATEE has been removed from this help center.
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.7
|
|
ThingWorx Connection Services Extension (CSE)
|
1.6.0
|
|
ThingWorx Axeda Compatibility Extension (ACE)
|
3.0.44
|
|
ThingWorx Remote Access Extension (RAE)
|
1.2.2
|
|
ThingWorx Utilities Core (Thingworx-Utilities-Core-8-5-3.zip)
|
8.5.3-51
|
|
ThingWorx SCM Extension (ThingWorx-Utilities-Software-Content-Management-8-5-3.zip)
|
8.5.3-51
|
 |
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 via the RAC.
|
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)
|
Java SE Development Kit 8, Update 162 or later (64-bit)
|
||
|
Linux 64-bit operating system
Windows 64-bit operating system
|
Tested on Linux 64-bit version of Ubuntu 18.04.2 LTS
|
||
|
Axeda Global Access Server
|
v.6.9.2 or later
|
||
|
ThingWorx Platform
|
8.5.2 or later
|
||
|
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.
|
Use ThingWorx Asset Advisor, v.8.5.3 or later. It 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, the ThingWorx Asset Remoting extension.
ThingWorx eMessage Connector, v.1.3.1, Release Notes
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.
Known Issues - ThingWorx Software Content Management (SCM) 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 - 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.
There are no plans to implement a change for this issue.
|
|
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
There are no plans to implement a change for this issue.
|
|
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.
There are no plans to implement a change for this issue.
|
|
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.
There are no plans to implement a change for this issue.
|
|
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
There are no plans to implement a change for this issue.
|
|
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.
There are no plans to implement a change for this issue.
|
|
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.
Asia/Riyadh87 is no longer a valid time zone. There are no plans to implement a change for this issue.
|
|
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.
There are no plans to implement a change for this issue.
|
|
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.
The creation of a logs subdirectory from the current working directory is how the default logback works. It is expected that customers will create their own logback file when they deploy to place the logs in their desired location.
|
|
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.
There are no plans to implement a change for this issue.
|
|
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.
There are no plans to implement a change for this issue.
|
|
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.
|