ThingWorx WebSocket-based Edge MicroServer (WS EMS) and Lua Script Resource (LSR) > Using ThingWorx Asset Advisor with WS EMS and LSR > Prerequisites to Setting Up a WS EMS Thing for Asset Advisor
  
Prerequisites to Setting Up a WS EMS Thing for Asset Advisor
It is important to remember that WS EMS performs all transactions with the ThingWorx platform and passes any requests for an LSR device on to that device. Most of the configuration you need to do
You need to configure your WS EMS and LSR, as follows:
Using ThingWorx Composer, create a non-administrator user and an Application Key for the WS EMS to use when connecting to a ThingWorx platform. When creating the Applicaton Key, associate that non-administrator user with the Application Key. For assistance, see
Configure the WS EMS for file transfers. For assistance, see Configuring File Transfers.
Configure the WS EMS for tunneling. For assistance, see Configuring Edge Settings for Tunneling.
Configure the parameters for the Lua Script Resource (LSR):
Connection to the WS EMS over HTTP or HTTPS Server (with an SSL/TLS certificate) — See Configuring the HTTP Server for the LSR (SSL/TLS Certificate)
Edge Thing (asset) to which you want to bind the properties — See Configuring Edge Things. Make sure that you use the name of the Thing here, not an Identifier.
Complete the following tasks using ThingWorx Composer, IN THE FOLLOWING ORDER:
1. Make sure that ThingWorx Composer v.8.2.0 or higher is installed on your ThingWorx platform.
* 
If you are using ThingWorx v.8.4.0 or later, you MUST configure the platform to allow the import of extensions and then restart the platform. For details, see Importing Extensions, "Enabling Extension Import", and platform-settings.json Configuration Details in the ThingWorx 8 Help Center for complete details.
2. Import the ThingWorx Remote Access Extension into your ThingWorx platform. For complete information, see Getting Started with the ThingWorx Remote Access Extension, available through the Reference Documents page on the PTC Support web site
* 
This extension adds a new widget to Mashup Builder for remote sessions, the RAClientLinker widget. If you want to use the new Remote Access functionality and you have previously used the Remote Access Widget in a mashup and want to continue using your mashup, you need to change the widget in your mashup and configure it.
3. Import the ThingWorx Software Content Management (SCM) Extension into your ThingWorx platform. For more information, see the ThingWorx Apps Setup and Configuration Guide for v8.4, also available through the Reference Documents page of the PTC Support site.
4. Import the ThingWorx Apps Extension and the ThingWorx Asset Remoting Extension into your ThingWorx platform. For more information, see the ThingWorx Apps Setup and Configuration Guide for v.8.4.
5. If you have not already done so, create a non-admin user and an Application Key for the WS EMS to present for authentication with the ThingWorx platform. For details, see Creating an Application Key for WS EMS.
6. Make sure that an Administrator has configured the settings for the subsystems, as explained in Administrator Tasks for Using Remote Access, File Transfers, and SCM in Asset Advisor.