ThingWorx Axeda Compatibility Package Release Notes, v.2.2.0
These release notes are for the ThingWorx Axeda Compatibility Package, version 2.2.0. Refer to the release notes for previous versions for information about changes made for those releases.
Important Information
Fos compatibility of the ThingWorx Axeda Compatibility Package, v.2.2.0, with other ThingWorx products, such as ThingWorx Platform and ThingWorx Utilities/SCM , visit the PTC tool, Release Advisor. To learn how to use Release Advisor, refer to the Technical Support article, "How to plan an upgrade using PTC Release Advisor".
The Axeda-ThingWorx Entity Exporter (ATEE) tool has been removed from the distribution bundle for the Axeda Compatibility Package. Customers who want to migrate from Axeda Platform to ThingWorx Platform should contact the PTC Axeda Transition Team for more information and guidance.
For security reasons, the ThingWorx IDM Connector is no longer available, starting with the 1.2.1 release. of the Axeda Compatibility Package In addition, the IDM Agents (formerly Questra Service Agents) 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 . Also, information for previous releases is available in the Release Notes section of this Help Center. |
Security Improvements
This release of the 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 2.2.0
The following table shows the versions of the components included in this release of the Axeda Compatibility Package (ACP).
| | The table below lists the versions of components provide in the package. For ThingWorx Utilities Core and the ThingWorx Software Content Management (SCM Extension, keep in mind that the version of these products must match the version of your ThingWorx Platform. The ACP is compatible with more than one version of ThingWorx Platform Refer to PTC Release Advisor for complete compatibility information. |
Component | Version |
|---|---|
ThingWorx eMessage Connector | 2.2.0 |
ThingWorx Connection Services Extension (CSE) | 2.2.4 |
ThingWorx Axeda Compatibility Extension (ACE) | 5.0.0 |
ThingWorx Remote Access Extension (RAE) | 3.0.0 |
ThingWorx Utilities Core (Thingworx-Utilities-Core-9-2-0.zip) ThingWorx SCM Extension (ThingWorx-Utilities-Software-Content-Management-9-2-0.zip) | 9.2.x |
| | The ThingWorx Utilities Core and SCM Extension, v.9.2.x are provided for compatibility with ThingWorx Platform v.9.2.x. However, you can also use the ACP v.2.2.0 with ThingWorx Platform v.9.0.x and v.9.1.x . If that is your use case, you need the version of the ThingWorx Utilities Core and SCM Extension that matches your version of the platform. You can download them from the PTC Support site. |
 | For Remote Access, you need to download a Remote Access Client (RAC) separately from the Axeda Compatibility Package. The latest version of the RAC is always backwards compatible with previous releases of the Remote Access Extension (RAE). If you have been using the most recent version of Axeda Desktop Viewer, you can continue to use that client via the RAC. If you use an SSH client, you can use that through the RAC as well. For more information, refer to ThingWorx Remote Access 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) | Oracle JDK 11 (64-bit) Amzaon Corretto 11 (Open JDK 11, 64-bit) |
Linux 64-bit operating system | Tested on Linux 64-bit version of Ubuntu 20.04.2 LTS |
Axeda Global Access Server or ThingWorx Global Access Server | Axeda Global Access Server, v.6.9.2 or later. ThingWorx Global Access Server v.7.0 or later. |
ThingWorx Platform | Version 9.0.x or later |
ThingWorx Remote Access Client (RAC) | RAC is backwards compatible. Always download the latest version of the RAC from the ThingWorx Remote Access Client Downloads. |
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. |
Axeda Policy Server or ThingWorx Policy Server (optional) | Axeda Policy Server, v.6.9.2 ThingWorx Policy Server v.7.0 or later |
ThingWorx eMessage Connector, v.2.2.0, and ThingWorx Remote Access Extension (RAE), v.3.x, Release Notes
These releases of the eMessage Connector and the Remote Access Extension (RAE), as well as the Remote Access Client (RAC), v.2.2.1 and later, support controlling remote sessions with assets through Axeda Policy Server v.6.9.2 or later and ThingWorx Policy Server, v.7.0.0, 7.0.1, and 7.1.0 and later. The other activities that Policy Server can control, such as file transfer requests, are not supported at this time. Refer to for a list of new topics and a list of topics related to remote sessions that have changed for Policy Server Support.
| | Throughout this help center, references to "Policy Server" include both the Axeda Policy Server and ThingWorx Policy Server. |
The eMessage Connector v2.2.0 and RAE v.3.0.0 releases also support the ThingWorx Global Access Servers (GAS) when it is used to connect directly to ThingWorx Platform. For details about the changes to the affected components of the ACP (Remote Access Extension v.3.0.0, Axeda Compatibility Extension v.5.0.0, and eMessage Connector v.2.2.0), to the Remote Access Client (RAC), and to the ThingWorx GAS, refer to GAS (Global Access Server) Enablement.
ID (SFID) | Description |
|---|---|
EMX-3727 and TW-84489 | To support Policy Server, ThingWorx Platform now has a System Name property on the Platform Subsystem.This System Name is sent to edge devices with egress messages so that Policy Server can use it for policy evaluation. Note that Policy Server requires that the System Name from the platform be a maximum of 14 characters. For more information, refer to Configuring Support for Policy Server. |
EMX-3693 | Support is provided for Axeda Policy Server, v.7.0.0, and ThingWorx Policy Server, v.7.1.0, for controlling remote access only. Note that Axeda Policy Server is rebranded to ThingWorx Policy Server as of v.7.1.0. For details, refer to the following topics: • Support for Policy Server — Provides an overview of support for Policy Server. • Configuring Support for Policy Server — Explains the properties to set in the configuration file for the eMessage Connector for Policy Server support. • Using Policy Server with the eMessage Connector — Explains what you need to know about the changes to support remote sessions with the eMessage Agents, the eMessage Connector, and Policy Server. • The following topics for remote sessions with eMessage Agents via the eMessage Connector have changed to explain changes made to the ThingWorx Remote Access Extension (RAE) for Policy Server support: |
ThingWorx Remote Access Extension, v.3.0.0 | |
RAE-256 / RAE-258 | The documentation of the ProviderConfig property has been updated for this release. Refer to Using the RAClientLinker Widget for the revised step for setting the property, and for complete specifics, refer to RemoteAccessProvider providerConfig Property Details . |
RAE-243 | Support for Policy Server's control of remote sessions is provided in the ThingWorx Remote Access Extension, v.3.0.0. |
| | The Policy Server application user interface has been rebranded for ThingWorx and updated to use the PTC Visual Design API. As a result, a few changes to procedures have been incorporated into the help and the guides for the ThingWorx Policy Server. |
Support for ThingWorx Global Access Server, v.7.x, "GAS Enablement"
The following table describes the enhancements made to the eMessage Connector, the Remote Access Extension (RAE), and the Axeda Compatibility Extension (ACE) to support the ThingWorx Global Access Server, v.7.x while continuing to support Axeda Global Access Server, v.6.9.2 and later 6.9.x. The support for ThingWorx GAS v.7.x is applicable only if the GAS v.7.x is pointed directly at the ThingWorx Platform.
For information about the Remote Access Client (RAC) releases, refer to the topic, What's New in ThingWorx Remote Access Extension and ThingWorx Remote Access Client? in the ThingWorx Platform 9 help center.
ID (SFID) | Description | ||
|---|---|---|---|
Axeda Compatibility Extension (ACE) | |||
ACE-170, ACE-138, ACE-136, and ACE-123 | As part of GAS Enablement, functionality specific to Axeda for Remote Access has been moved to the Remote Access Extension (RAE) from the ACE. These changes include: • Changes to the permission/visibility-granting services of the eMessageServices Thing in the ACE and to the corresponding services of the RemoteAccessPermissionServices Thing in the RAE. For details, refer to the section, Permissions Details, in the topic, Security Background: ThingWorx Permissions for the eMessage Connector • Token validation changes, including any related files for token validation, have been moved to the RAE. • The Axeda.RemoteAccessible Thing Shape has been removed from ACE. Its endpoints property was moved to the new GASRemoteAccessible Thing Shape in the RAE. The RAE Thing Shape provides the functionality that was previously provided by the Axeda.RemoteAccessible Thing Shape. • All of the Axeda Remote Access functionality has been moved from ACE to RAE. For details, refer to the section, "ThingWorx Axeda Compatibility Extension (ACE), v.5.0.0" in the topic, GAS (Global Access Server) Enablement . | ||
eMessage Connector (EMX) | |||
EMX-3693/ RAE-254 | The online property of a remote access server is now read only. For the ThingWorx Global Access Server (GAS), this property represents whether or not the GAS has registered with the ThingWorx Platform. | ||
EMX-3686 (15628111, 15635507) | When a remote session with an Axeda Agent requires Policy Server approval, the eMessage Connector will allow the remote session if the policy is set to "Always Allow" or if an operator at Policy Server console approves the remote session. If the operator denies the remote session or if the policy is set to "Never", the remote session is not permitted. | ||
EMX-3610 | GAS audit message processing has been updated to include file transfer information that comes from the Axeda Desktop Server. The audit record for a file transfer during a remote session includes: • Details about the user initiating the transfer • The date and time that the transfer completed • The device transferring the file • The name and size of the file that was transferred.
| ||
ThingWorx Remote Access Extension (RAE) v.3.0.0 | |||
RAE-285 | In v.3.0.0 of the RAE, the StartEdgeSession and StopEdgeSession services have been removed from the RemoteAccessible Thing Shape. These services applied too ThingWorx Edge agents. The ConnectToSession service replaces StartEdgeSession in the RemoteAccessible Thing Shape. In addition, the new GASSessionConfig Data Shape contains the GAS session configuration data needed by the ThingWorx Edge agent to start a session with GAS. | ||
RAE-263 | Errors in the flows for the GAS StartSession and EndSession services are now propagated up through the RAClientLinker widget so that remote access users are more aware of failures, such as non-success result from GAS or I/O exception communicating with GAS due to a connect timeout or a read timeout. | ||
RAE-257 | Fixed an issue where the StartSession and EndSession services of the GASModel Thing Template would generate an error in ThingWorx ScriptLog when an agent serialNumber or thingName contained spaces. | ||
RAE-256 and RAE-258 | The documentation of providerConfig has been updated to clarify when this proeprty is required and provide examples of valid values. Refer to Using the RAClientLinker Widget , specifically the table of properties for the widget, and to the new topic, RemoteAccessProvider providerConfig Property Details. | ||
RAE-254 | The online property of a remote access server is now read only. For GAS, this property represents whether or not the GAS has registered with the ThingWorx Platform. | ||
RAE-210 | For the StartSession and EndSession services of the GASModel Thing Template, a GAS request timeout configuration option has been added. The timeout defaults to 60 seconds. For a description, refer to the description of the timeout property in the topic, GASModelConnectionSettings Data Shape. | ||
RAE-192 | The service, UpdateExternalRemoteAccessServerStatus, has been added to the Remote Access Subsystem to handle status updates and audit records sent directly from a GAS. For example, the service updates the currentNumberOfSessions property on a GAS Thing. | ||
RAE-188 | The permissions services of the RemoteAccessPermissionServices Thing grant permissions to non-admin users such as the eMessage Connector user to use GAS. | ||
RAE-187 | The endpoints property and the ConnectToSession service have been added to the RemoteAccessible Thing Shape in RAE. The Axeda.RemoteAccessible Thing Shape has been removed from the Axeda Compatibility Extension (ACE) v.5.0.0 and is replaced by a new GASRemoteAccessible Thing Shape in RAE v.3.0.0. For details on the new Thing Shapes, refer to RemoteAccessible Thing Shape and GASRemoteAccessible Thing Shape in the Extensions Reference section of this help center. | ||
RAE-166 | The functionality of the token validation for GAS is identical to that of the Axeda Platform: • When a GAS token mismatch is detected, the platform marks the server status as invalidToken by setting the invalidToken property to true. • The platform ignores all communication where the token is invalid. • The platform accepts new token and communications from GAS once an Administrator has reset the token. | ||
RAE-158 | To support GAS, two services have been added to the RAE: • RegisterExternalRemoteAccessServer — Allows a GAS to register itself directly with ThingWorx Platform. • UnregisterExternalRemoteAccessServer — Allows a GAS to unregister itself or a user to unregister a GAS that is no longer needed. | ||
Additional Enhancements and Issues Fixed in eMessage Connector, v.2.2.0, ACE v.5.0.0, and RAE v.3.0.0
The following enhancements not related to GAS or Policy Server have been added to this release of the Axeda Compatibility Package. In addition, the following issues have been fixed in this release:
Issue ID (SFID) | Description | ||
|---|---|---|---|
Enhancements | |||
EMX-3902 | The eMessage Connector now detects and logs when NIO threads are blocked, waiting for platform responses for too long. The log message uses the WARN level. The allowable time for blocking and the frequency of checking for blocked threads are configurable. The default values are a frequency of every 10 seconds and a log threshold of 1 minute. Note that the blocked thread checker is enabled by default for the eMessage Connector. | ||
EMX-3886 | The ThingWorx Utilities Software Content Management (SCM) Extension requires that the user group of the eMessage Connector user be added to the TW.RSM.RemoteServices user group to all the Connector to run the TW.RSM.* services. | ||
EMX-3885 | After reviewing customer logs, log levels have been changed from DEBUG to TRACE in several areas of the eMessage Connector. In addition, the logback.xml file was updated to set com.thingworx.sdk.impl.correlation.DefaultCorrelationChannelImpl to the WARN level to reduce logging a DEBUG message on every ThingWorx Platform response. | ||
EMX-3878 | Compatibility with Java 8 has been removed from eMessage Connector in v.2.2.0. To minimize the potential for security vulnerabilities, you must upgrade to Java 11 for your eMessage Connector and ThingWorx Platform. This version of the Connector and v.9.2.x of the ThingWorx Platform will not work with Java 8. | ||
EMX-3847 | The smoke test for the eMessage Connector now uses the transport.websockets.service-discovery.tls-enabled config file value to determine whether or not to use wss (TLS). | ||
Issues Fixed | |||
ACE-194 | The tokenInvalid property is now being set properly to true for Axeda Agent Things and GAS Things on ThingWorx Platform so that errors related to token authentication in the eMessage Connector logs can be linked to an invalid token. End users should understand why their token error occurred and assess whether it could be the result of tampering. A reset of the token should only occur after they determine that the result of an invalid token was not the result of some attack on their system.
For instructions on resetting a token for an Axeda Agent Thing, refer to Resetting a Token. You can also follow these instructions for a GAS Thing, just going to the GAS Thing instead of the Axeda Agent Thing. For information about the tokenPropertyAuthenticator , refer to TokenPropertyAuthenticator Behavior (eMessage Connector). For information about configuring the token property authenticator, refer to Configuring the TokenPropertyAuthenticator (eMessage Connector). For information about the exceptions that would necessitate resetting a token, refer to Connector Exception 8: Invalid Thing token property and Connector Exception 9: Blank token property on Thing. | ||
EMX-3996 | This help center includes updates that clarify how the download.overwriteExisting option is intended to work for file downloads to Axeda eMessage Agents. The changes were made to the descriptions of the option in the topics, Downloading Files to Axeda Gateway and Connector Agents and Metadata for File Transfer Jobs. | ||
EMX-3722 (001A000000TOM37IAH) | Threads are left in "blocked" state on exception. This issue is fixed in this release. | ||
EMX-3565 | The GetThingNameAndIdentifierByModelAndSerial service had been modified to return an empty infotable if the Thing could not be found. The empty infotable caused an exception which in turn blocked a Vert.x thread. This issue is fixed in this release. | ||
RAE-287 | The eMessage Connector throws a token authentication failure error message when a GAS sends an invalid token when communicating with the Connector. However, the GAS Things that send an invalid token did not have their invalidToken property set to true. In addition, since the property value did not change, the GAS selection process did not ignore a GAS that had sent in an invalid token. The setting of the invalidToken issue is fixed by the fix for ACE-194 (see the entry above). The fix for this issue updates the GAS selection process to ignore any GAS Thing whose invalidToken property is true. | ||
RAE-283 | As typically done by a time invoking the TerminateInactiveSessions service of the Remote Access Subsystem, terminating an inactive session removed the session from the ThingWorx Platform but left the session running on GAS. The GAS could send session audit messages in the future for this session, leading to errors in the application log for unprocessed audit messages. This issue is fixed in this release. Instead of updating the session with the status of TERMINATED, the status of the session is updated to CLOSE_REQUESTED. This status triggers the endSession workflow so that the session is removed from GAS as well as the platform. | ||
Known Issues - eMessage Connector
The following table lists and describes the known issues for the eMessage Connector in this release:
Issue ID | Description |
|---|---|
CXS-1131 | When running the eMessage Connector on Oracle JDK 11 or Amazon Corretto 11, the following DEBUG messages are written to the Connector logs: 14:20:13.581 [metrics-logger-reporter-1-thread-1] DEBUG c.t.shepard.metrics.CpuGaugeSet - Unable to invoke getProcessCpuLoad: {} java.lang.reflect.InaccessibleObjectException: Unable to make public long com.sun.management.internal.OperatingSystemImpl.getProcessCpuTime() accessible: module jdk.management does not "opens com.sun.management.internal" to unnamed module @4b952a2d at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340) at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280) at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:198) at java.base/java.lang.reflect.Method.setAccessible(Method.java:192) at com.thingworx.shepard.metrics.CpuGaugeSet$3.getValue(CpuGaugeSet.java:56) at com.thingworx.shepard.metrics.CpuGaugeSet$3.getValue(CpuGaugeSet.java:50) at com.codahale.metrics.Slf4jReporter.logGauge(Slf4jReporter.java:307) at com.codahale.metrics.Slf4jReporter.report(Slf4jReporter.java:221) at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:237) at com.codahale.metrics.ScheduledReporter.lambda$start$0(ScheduledReporter.java:177) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) 14:20:13.581 [metrics-logger-reporter-1-thread-1] DEBUG c.t.shepard.metrics.CpuGaugeSet - Unable to invoke getProcessCpuLoad: {} java.lang.reflect.InaccessibleObjectException: Unable to make public double com.sun.management.internal.OperatingSystemImpl.getProcessCpuLoad() accessible: module jdk.management does not "opens com.sun.management.internal" to unnamed module @4b952a2d at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340) at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280) at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:198) at java.base/java.lang.reflect.Method.setAccessible(Method.java:192) at com.thingworx.shepard.metrics.CpuGaugeSet$2.getValue(CpuGaugeSet.java:38) at com.thingworx.shepard.metrics.CpuGaugeSet$2.getValue(CpuGaugeSet.java:32) at com.codahale.metrics.Slf4jReporter.logGauge(Slf4jReporter.java:307) at com.codahale.metrics.Slf4jReporter.report(Slf4jReporter.java:221) at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:237) at com.codahale.metrics.ScheduledReporter.lambda$start$0(ScheduledReporter.java:177) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) These DEBUG messages can be safely ignored. They do not impact the operability of the system. |
EMX-607 | In the unlikely event of a setDataItem service call failing, the ThingWorx Platform does not receive a notification 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. The Connector is working as expected. |
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. There are no plans to implement a change for this issue. |
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:
ID (SFID) | 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. |