Remote Access in a High Availability Cluster
The Active-Active Clustering (HA) feature for ThingWorx Platform 9.x.x and 2.0 and later of the ThingWorx Remote Access Client (RAC) enable you to run remote sessions in a high availability ThingWorx cluster. For remote access sessions to work in this environment, here are the requirements:
• You must have at least one ThingWorx Connection Server 9.x.x, in the cluster to handle remote access sessions. You do not need one Connection Server per ThingWorx Platform instance. The Connection Server acts as an HA proxy to ThingWorx Platform instances.
• You must install the Remote Access Extension (RAE) on the primary server in the cluster. After installing it there, the extension is copied to the other nodes in the cluster. Use 2.0.0 or later of the RAE with ThingWorx Platform 9.x.x.
• If your edge devices are running ThingWorx Edge MicroServer or applications written using ThingWorx Edge SDKs, you must update the ThingWorx Tunneling Subsystem to point at the HA proxy (Connection Server). The RAC connection to a ThingWorx Platform is called a command channel. The Connection Server provides this command channel in an HA environment. No special configuration is required for RAC, as long as you point the Tunneling Subsystem to the HA proxy.
• Performing remote access in an HA environment requires 2.0.0 or later of the RAC.
 |
To ensure that you have the latest features, bug fixes, and security fixes, check the RAC download site periodically for updated RAC packages.
|
For an overview of Connection Servers in an HA environment, refer to Using the Connection Server in a ThingWorx High Availability (HA) Clustering Environment in the ThingWorx Connection Server Help Center. To configure the Connection Server for an Active-Active environment, refer to High Availability Configurattion in the ThingWorx Connection Server Help Center.