Compatibility of GAS and RAE Versions
The following configurations are supported for remote access, the eMessage Connector, and the ThingWorx Platform:
• eMessage Connector v.3.0.0, RAE v.3.0.0, and ThingWorx Platform v.9.x
• eMessage Connector, v.2.x, RAE v.2.x, and ThingWorx Platform v.8.5.x
All other configurations are not officially supported but should work as indicated in the following table. Note that the dark gray background indicates configurations that are not officially supported but are still expected to work.
Footnotes
• † The AxedaProtocolAdapterServices Thing Shape support was removed from eMessage Connector v.3.0.0 and RAE 3.0.0. ThingWorx to GAS message cannot be sent via the Connector/ConnectionServicesHub.
• †† RAE v.2.x is not supported with eMessage Connector v.3.0.
• ‡ RAE v.2.x does not support direct egress to GAS.
• ※ RAE v.2.x does not support the services required for GAS to communicate with ThingWorx Platform directly.
RAE v.2.x cannot communicate directly with GAS. All ingress and egress from and to GAS goes through the eMessage Connector and the Connection Services Hub.
RAE v.3.0 can communicate directlry with GAS v.6.9.x or later to start and end remote sessions.
GAS v.6.9.2/v.6.9.3 must communicate only through the eMessagee Connector for ingress messages such as status updates and "foreign" messages.
GAS v.7.1.x can communicate directly with the ThingWorx Platform for status updates (ingress). It can communicate indirectly through the eMessage Connector for ingress (AXEDA mode).
 | If a given eMessage Connector version supports a single path of egress, customers can upgrade to the eMessage Connector v.3.0 after their Global Access Servers have been upgraded and RAE v.3.0.0 is installed. |