EMX-3011 (14043586)

Axeda Deployment Utility v.6.8.3 does not work with eMessage Connector - Deploy Changes cause it to hang.

After using the Axeda Deployment Utility to configure Axeda Gateway Agents (v.6.9.x) and clicking Deploy Changes to Agent, the configuration file is sent, but the Deployment Utility subsequently hangs on the message, "Retrieving device information from the Enterprise". After a while, a timeout occurs.

This issue is fixed in this release. The Utility no longer hangs after a user clicks Deploy Changes to Agent. Note that the ThingWorx Platform does not support the Axeda Platform concepts of Organization, Location, Region, and System, so the eMessage Connector cannot get or set that information for eMessage Agents. Instead, these fields are empty after a get or set operation. .

ThingWorx eMessage Connector

1.1.0.3

ThingWorx Axeda-ThingWorx Entity Exporter (ATEE)

1.1.0.0

Connection Services Extension (CSE)

1.5.4

ThingWorx Axeda Compatibility Extension (ACE)

2.4.17

ThingWorx Utilities

8.3.1-94

Java Development Kit (JDK)

v.1.8.0_u162 (64-bit)

Linux 64-bit operating system

Tested on Linux 64-bit platforms

Axeda Platform

v.6.9.0 or later to export users; otherwise, 6.8.0 or later

ThingWorx Platform

8.3.0 or later

Apache Tomcat

8.5.13 (64-bit)

Axeda Gateway Agent or Axeda Connector Agent

v.5.3.1 or later

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.

RESOLUTION: The eMessage Connector registration functionality now works similar to that of the Axeda Platform. The eMessage Connector parses the t= attribute in the registration tag (<Re> to set the First Registration and Latest Registration properties. Note that the Step 5. Registration Message step of the eMessage Connector smoke test has been revised as part of the resolution of this issue.

EMX-2473

Smoke test is not re-runnable.

This issue should not occur. To ensure that you do not encounter it, wait a few minutes between runs of the smoke test. Running the smoke test over and over within seconds may yield inconsistent results. The smoke test is not meant to be run over and over in quick succession.

ATEE-168 (13647337)

Unable to export User passwords on 6.9 Axeda Platforms when Central Administrator is configured.

RESOLUTION: This release provides fixes for handling when user password hashes are not present in Axeda’s internal User Store.

ATEE-170 (13647337)

ATEE Exports empty Users as part of User Groups

ATEE was incorrectly adding empty entries to XML when User Groups had more members than were being exported.

RESOLUTION: ATEE now correctly exports User Groups and Users.

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:

EMX-607

In the unlikely event of a setDataItem service call failing, the the ThingWorx Platform does not receive a notification event. It would be better if the eMessage Connector could notify the 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 the 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.

UTL-5173

Specifying a DownloadFromPlatform instruction with a file that is not compressed in the tar.gz format and also selecting the check box next to the option, "Agent should uncompress this file after downloading" results in the file not being downloaded correctly to the agent. Specify the uncompress option ONLY for files that are in the tar.gz format.

UTL-5181

If the File Transfer Subsystem is restarted during a file download, the platform is not able to cleanly terminate the download, causing the delivery target to be stuck in a non-terminal state until it times out.