ThingWorx Axeda Compatibility Package Release Notes, v.1.2.1
These release notes are for the ThingWorx Axeda Compatibility Package, version 1.2.1. Refer to the release notes for version 1.2.0 for additional information about changes made since the 1.1.0 release.
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 will move to End of Life in June 2020.
IMPORTANT! The ThingWorx eMessage Connector, ThingWorx Axeda-ThingWorx Entity Exporter (ATEE), and the ThingWorx Remote Access Client have NOT been certified on ThingWorx Platform v.8.5.0.
ACP Component Versions for Release 1.2.1
The following table shows the versions of the components included in this release of the Axeda Compatibility Package (ACP).
|
Component
|
Version
|
|---|---|
|
ThingWorx eMessage Connector — For information about the changes in v.1.2.3 of this Connector, refer to the section below, ThingWorx eMessage Connector, v.1.2.4, Release Notes.
|
1.2.3
|
|
Axeda-ThingWorx Entity Exporter (ATEE)
|
1.2.1.0
|
|
ThingWorx Connection Services Extension (CSE)
|
1.5.5
|
|
ThingWorx Axeda Compatibility Extension (ACE)
|
3.0.41
|
|
ThingWorx Migrator for the Axeda Compatibility Extension (ACE)
|
3.0.41
|
|
ThingWorx Remote Access Extension (RAE)
|
1.0.2
|
|
ThingWorx Utilities Core (Thingworx-Utilities-Core-8-4-0.zip)
|
8.4.0-88
|
|
ThingWorx SCM Extension (ThingWorx-Utilities-Software-Content-Management-8-4-0.zip)
|
8.4.0-88
|
For Remote Access, you need to download a Remote Access Client 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.
ThingWorx eMessage Connector, v.1.2.3, Release Notes
The ThingWorx eMessage Connector is a component of the ThingWorx Axeda Compatibility Package (ACP). This release of the Connector is compatible with releases 1.2.0 and 1.2.1 of the ACP package. Refer to ThingWorx Axeda Compatibility Package Release Notes, v.1.2.0 for information about that release and the software requirements for the package and its components..
This release of the eMessage Connector provides the following enhancement updates:
|
ID (SFID)
|
Description
|
||
|---|---|---|---|
|
Enhancement
|
|||
|
EMX-3328
|
Add support for AES encryption and decryption.
The eMessage Connector v.1.2.3 supports eMessage AES encryption. AES encryption must be configured in the eMessage Connector. Please contact support for assistance in implementing this feature.
|
||
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)
|
v.1.8.0_u162_b12 or higher (64-bit)
|
|
Linux 64-bit operating system
|
Tested on Linux 64-bit version of Ubuntu 14.04.5 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.4.0-b2013 or later
|
|
Axeda Gateway Agent or Axeda Connector Agent
|
v.5.3.1 or later
|
 |
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.
|
Known Issues - Axeda Compatibility Extension (ACE)
The following table lists and briefly describes a known issue with the ACE:
|
Issue ID
|
Description
|
|---|---|
|
ACE-115
|
When importing the Axeda Compatibility Extension, the following error message appears in the ApplicationLog for the ThingWorx Platform:
2019-01-28 14:00:44.791+0000 [L: ERROR] [
O: c.t.t.Thing] [I: AxedaRemoteViewerRefreshScheduler] [U: SuperUser] [S: ] [T: https-jsse-nio-8443-exec-7] Thing State is being set to ERROR because it failed during the initialization phase: The runAsUser field was empty! The runAsUser field for any Timers and Schedulers in ThingWorx Platform, v.8.4.0, cannot be empty. This field for the AxedaRemoteViewerRefreshScheduler entity in the ACE is empty on import. You must navigate to the entity in ThingWorx Composer and set a valid user. After saving the entity, you MUST restart ThingWorx Platform.
|
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.
|