Requirements for Remote Sessions
 |
If you are a PTC Cloud Services customer using the ThingWorx Axeda Compatibility Package (ACP), you do not need to download and install the ThingWorx Remote Access Extension to perform remote sessions. Cloud Services performs this upgrade for you when upgrading the ACP. Similarly, if you are a PTC customer who uses ACP at your site, you also do not need to download and install the extension separately from the upgrade (or new installation) of ACP.
|
To use the Remote Access features of the ThingWorx Asset Advisor, ThingWorx Remote Access Client, ThingWorx eMessage Connector, and ThingWorx Platform, your environment must meet the following prerequisites):
1. The version of ThingWorx Platform for your version of the Axeda Compatibility Package (ACP) is installed and running.
2. The latest version of the ThingWorx Remote Access Client (RAC). To download the latest version for your operating system, go to ThingWorx Remote Access Client Downloads.
 |
Make sure that you have changed the settings in the platform configuration file, platform-settings.json, to enable the import of extensions and restarted the platform. Refer to the following topics in the ThingWorx Platform Help Center for details:
|
3. The ThingWorx Axeda Compatibility Package (ACP) has been downloaded and extracted. This package provides the versions of the Connection Services, Remote Access, and Axeda Compatibility Extensions and of the eMessage Connector that are required to use Remote Access features. Refer to the release notes for the exact versions.
4. The following extensions that are included in the ACP have been imported into your ThingWorx Platform in the following order:
a. ThingWorx Connection Services Extension (CSE)
b. ThingWorx Remote Access Extension (RAE)
c. ThingWorx Axeda Compatibility Extension (ACE)
|
|
The CSE and RAE must be imported before the ACE.
|
5. The ThingWorx eMessage Connector is installed, configured for remote access, and running.
|
|
After importing the extensions either during an upgrade or new installation, you must restart the ThingWorx Platform.
|
6. You have created Things to represent your devices, using ThingWorx Composer and the latest Thing Templates provided in your version of the ACE.
7. The ThingWorx Global Access Server v.7.1.0 can operate either through the eMessage Connector or directly through ThingWorx Platform. Using ThingWorx GAS v.7.x with the Connector is the same as if you are using an Axeda GAS v.6.9.2 or v.6.9.3. Make sure that you have configured the GAS to connect to the appropriate destination - the eMessage Connector or the ThingWorx Platform.
|
|
When connecting GAS to the ThingWorx Platform, the eMessage Connector registers the GAS with the platform and automatically creates a Thing to represent the GAS. In ThingWorx Composer, navigate to the GAS Thing and run the EnableForRemoteSessions service to enable that GAS to be used for remote sessions.
When communicating directly with the platform, the ThingWorx GAS v.7.1.x registers with the ThingWorx Platform and a Thing is automatically created from the GASModel Thing Template provided in the RAE. An administrator must run the service, EnableForRemoteSession, for the GAS to be available for remote sessions.
|
8. As needed, you have set up the Remote Access Provider for your Axeda Gateway and/or Axeda Connector agents. The GASRemoteAccessProvider Thing provided in the RAE is enabled once you import the Remote Access Extension (RAE) into ThingWorx Platform. It does NOT represent a ThingWorx GAS. Rather, it is the provider that you must assign to each Thing that represents an Axeda agent. Further, each Axeda Thing must implement the GASRemoteAccessible Thing Shape or the RemoteAccessible Thing Shape.
|
|
The Axeda.RemoteAccessible Thing Shape has been replaced in RAE v.3.0.0 by the GASRemoteAccessible Thing Shape.
|
9. Depending on how you want to run remote sessions:
◦ If you want to use ThingWorx Asset Advisor, you have downloaded the ThingWorx Apps, imported the required extensions into your ThingWorx Platform, and followed the setup, configuration, and permissions instructions in the ThingWorx Apps Help Center for your version:
▪ ThingWorx Apps, v.9.0.0 — ThingWorx Apps 9 Help Center
▪ ThingWorx Apps, v.9.1.0 — https://support.ptc.com/help/thingworx/apps/r9.1/en/
.
◦ The Remote Access Client (RAC) is available separately and needs to be downloaded to the computer where a user will launch a remote session. Refer to ThingWorx Remote Access Client for details.
◦ End users have been assigned permissions and visibility to the devices they need to access.
10. The ThingWorx Remote Access Subsystem is configured and running on your ThingWorx Platform. ThingWorx Platform administrators should refer to Configuring the Remote Access Subsystem for details on configuring the subsystem.
11. You have run the services that grant visibility and permissions for remote access to your end users. Refer to Security for Remote Sessions.
12. End users have the following permissions so that they can start a remote session on a RemoteAccessible Thing:
◦ READ on the remotely accessible Thing
 |
For remote access to work for Axeda Agent Things, the following rules apply:
• The Thing must be created using one of the Axeda Thing Templates for Axeda Gateway and Axeda Connector agents. If this rule is followed, the next one is automatically fulfilled when you have imported v.3.0.0 or later of the ThingWorx Remote Access Extension (RAE) .
• The Thing must implement both the RemoteAccessible and GASRemoteAccessible Thing Shapes. You cannot just apply these Thing Shapes to a Thing that is not derived from the Axeda Thing Templates.
|
◦ PROPERTY READ on the remotely accessible Thing
◦ SERVICE INVOKE on the services for remote sessions, such as StartSession
To assign end users these permissions, refer to the topic, Entity Permissions, in the ThingWorx Platform Help Center.
Next Steps
Once all of the steps above are complete, end users can access remote devices through ThingWorx Asset Advisor or the Remote Access Client that is launched from your own custom mashup. If creating your own mashup, use the raClientLinker widget that is provided in the Remote Access Extension. Follow a link below to take your next step:
• To create a mashup using the widget and ThingWorx Mashup Builder, refer to Using the raClientLinker Widget and ThingWorx Remote Access Client.
• To start a remote session using Asset Advisor, refer to the "Asset Advisor" section of the "Exploring the Apps" section in the ThingWorx Apps 9 Help Center..