ThingWorx Extensibility > Extensions > Remote Access > Requirements for Remote Access
Requirements for Remote Access
To use the capabilities for Remote Access in ThingWorx 8.5 and later, your environment must meet certain requirements. If your assets are running Axeda eMessage Agents, see the topic, Requirements for Remote Sessions in the Help Center for the ThingWorx Axeda Compatibility Package.
If your assets are running the ThingWorx WebSocket-based Edge MicroServer (WS EMS), Lua Script Resource (LSR), your environment must meet the following requirements:
1. The version of ThingWorx Platform for your version of the Remote Access Client (RAC) is installed and running. If you want to use v.1.2.0 of the Remote Access Extension (RAE), you must be running ThingWorx Platform v.8.5.2 or later. You can use RAC v.1.1.0 with ThingWorx Platform v.8.4.x through 8.5.x. The v.1.2.0 of the is not backwards compatible with ThingWorx Platform v.8.4.x through 8.5.1. Refer to Support Matrices for ThingWorx Remote Access Extension and Remote Access Client for more details.
* 
Make sure that you have changed the settings in its configuration file, platform-settings.json, to enable the import of extensions, and then restarted the platform. Refer to the following topics in this Help Center for details:
2. The ThingWorx Remote Access Extension (RAE) has been imported into the ThingWorx Platform. For devices running a WS EMS or LSR, this extension is the only one you need for remote access. Instructions for importing the RAE are provided in Importing Extensions.
3. If you want to use the ThingWorx Remote Access and Control application provided in ThingWorx Asset Advisor, you need to import the ThingWorx Apps Extension and the ThingWorx Remote Access and Control Extension into your ThingWorx Platform. If using ThingWorx Apps v.8.5, refer to the ThingWorx Apps 8.5 Help Center. If using v.8.4, refer to the ThingWorx Apps Setup and Configuration Guide for v.8.4. The guide is available through the Reference documents page on the PTC Support site.
4. An administrator needs to set up the security entities and run the services to grant visibility and permissions for remote access. Refer to Security for Remote Access.
5. Either your ThingWorx Edge SDK application or your WS EMS needs to be configured for tunneling and the tunneling configuration for Things needs to be set up in ThingWorx Composer. Refer to the Help Center for your ThingWorx Edge SDK or for the WS EMS for details.
Next Steps
Once your environment meets these requirements, administrators need to perform basic setup tasks. The next section, Administrator Setup Tasks for Remote Access, explains these tasks. For information about security and remote access, refer to Security for Remote Access. For information about the features of the ThingWorx Remote Access Extension (RAE), refer to the following topics:
Once the setup tasks are complete, an administrator or end user with appropriate visibility and permissions can perform any of the following tasks:
Create a mashup using the RAClientLinker widget and ThingWorx Mashup Builder. Refer to Using the RAClientLinker Widget .
Try remote sessions using the ThingWorx Remote Access Client (RAC). Refer to ThingWorx Remote Access Client (RAC).
Start a remote session using the mashup or using Asset Advisor, refer to the "Asset Advisor" section of the "Exploring the Apps" section of the ThingWorx Apps 8.5 Help Center for v.8.5 of ThingWorx Apps. If you are using v.8.4 of ThingWorx Apps, see the "Exploring the Apps" chapter of the ThingWorx Apps Setup and Configuration Guide (v.8.4). This guide is available through the Reference documents page on the PTC Support site.
Was this helpful?