Release Notes > Release Notes for Versions 1.x.x of the Axeda Compatibility Package > Axeda Compatibility Package for Axeda eMessage Agents Release Notes, v. 1.0.0
Axeda Compatibility Package for Axeda eMessage Agents Release Notes, v. 1.0.0
The Axeda Compatibility package is the collection of ThingWorx products that Axeda customers need to migrate their assets and data from Axeda Platform to ThingWorx, enabling their assets to communicate with ThingWorx. This package consists of the following products:
• eMessage Connector, which allows Axeda assets that are running Axeda eMessage Agents (Axeda Gateway, Axeda Connector) to work with ThingWorx Platform. The eMessage Connector is comprised of the base ThingWorx Connection Server and the Axeda Adapter (referred to as one product in documentation, called the “eMessage Connector”). The eMessage Connector must be installed and configured. Then, after switching to the DNS where the Connector is running, the assets can start communicating with an instance of ThingWorx Platform. A PDF for the Connector is available in the package. Refer to the PDF for the Connector for complete information about its supported features and procedural information for installation, configuration, operation, and troubleshooting.
• Connection Services Extension (CSE), which must be imported into ThingWorx Platform to support a centralized hub that manages event notifications between Connectors and ThingWorx Platform. This extension is documented in the PDFs for ATEE and eMessage Connector. The information is the same in the two PDFs. You only import them ONCE.
• Axeda Compatibility Extension (ACE) that must be imported into ThingWorx Platform to support Axeda entities.This extension is documented in the PDFs for ATEE and eMessage Connector. The information is the same in the two PDFs. You only import them ONCE.
• ThingWorx Utilities, which provides a user interface for interacting with your assets. Documentation for ThingWorx Utilities is available on the PTC Support site, Reference Documents page for ThingWorx and ThingWorx Utilities Help Center. It is NOT available in this package. However, what you need to do to make your Axeda assets visible in ThingWorx Utilities is documented in the PDF for the ATEE.
When deployed assets contact eMessage Connector, they can register and bind with ThingWorx Platform. You then can use ThingWorx Composer, Mashup Builder, and ThingWorx Utilities v.7.3 to fully interact with these devices. Note that a few additional steps are needed for you to be able to access your assets through ThingWorx Utilities.
Known Issues
The following table describes the known issue for ATEE operating with Axeda Platform:
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 ManagedDevices 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.
The following table lists and describes the known issues for the eMessage Connector in this release:
ID
Description
EMX-607
In the unlikely event of a setDataItem action failing, 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 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-1897
Edge-controlled Things should solicit egress by invoking DequeueEgress once per Thing. Concurrent invocations of DequeueEgress yield unpredictable results. Axeda agents send only one message that solicits egress at a time, so this should not be observed in the field. However, it would be better to prevent this from even being a possibility.
EMX-1901
In Axeda Platform data item writes, where one data item fails, cause the whole batch to fail. ThingWorx Platform does not behave in the same way — any failed writes cause only that property to fail.
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. It is just wasteful
EMX-2197
Agent registration differs between Axeda Platform and eMessage Connector. The eMessage Connector parses the "t=" attribute during registration (<Re>) tag to set the "First Registration" and "Latest Registration" properties. The Axeda Platform completely ignores the "t=" attribute and simply uses current time (System.currentTimeMillis()) to set the registration time.
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 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-2410
EventConverter and AlarmConverter may report
"Failure when writing assetLogEvents property
com.Thingworx.sdk.api.concurrent.RequestException:
Server returned an error with status STATUS_INTERNAL_ERROR...
[remainder truncated]".
This message is known to appear when more than one process tries to update the same property at the same time. This is not an expected occurrence during normal Axeda Agent/eMessage Connector operation
EMX-2412
NotifyPropertyUpdate invocations to the eMessage Connector are not handled, resulting in a WARN message being logged. The operation of the Connector is not affected.
EMX-2473
Do not attempt to run the smoke test very soon after the last run (within minutes). Running the smoke test over and over can yield inconsistent results. The smoke test is not meant to be run over and over in quick succession.
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 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
Flood scenarios can cause latency while agents re-register with the eMessage Connector. If the eMessage Connector goes down and experiences a significant amount of requests per second for *different* agents (~10+ new agent communications per second), the eMessage Connector can cause strain on ThingWorx Platform.
Was this helpful?