Welcome to the Vuforia Studio 9.0.3 Help Center > Security and Architecture
  
Security and Architecture
How It Works
The Experience service is used by both Vuforia Studio and Vuforia View. The following table lists simple use cases for an Experience Service.
Component
Use Case
Vuforia Studio
Published Experiences are stored on the Experience Service.
Vuforia View
Once a ThingMark, Model Target, Spatial Target, or Image Target is scanned, Vuforia View searches the Experience Service for all relevant Experiences. Once search results are returned and you select an Experience, the Experience is loaded in Vuforia View.
ThingWorx
Used to serve data from Edge devices. Optionally, it can delegate authentication.
Communication Ports and Protocols
Vuforia Studio leverages web-based protocols for communication with clients. These protocols are primarily HTTP(S) over standard web ports.
If your Experience Service has been installed on-premises and is not being hosted by PTC, here are a few things to keep in mind when identifying changes that might be necessary to allow communication between the different software components.
Software Component
Requirement
Experience Service
Vuforia Studio and Vuforia View must be able to connect to the machine running the Experience Service using the port that was configured when you installed the Experience Service. The clients connect to this port to make REST API calls, and to establish WebSockets. Depending on how the Experience Service is configured, either secure (HTTPS or WSS) or insecure (HTTP or WS) protocols will be used for this communication.
ThingWorx
The Experience Service must be able to connect to the machine running ThingWorx using the port that was configured when you installed the ThingWorx server. The Experience Service will connect to ThingWorx to make API calls and to establish WebSockets. Depending on how the ThingWorx server is configured, either secure (HTTPS or WSS) or insecure (HTTP or WS) protocols will be used for this communication.