Before You Install the Experience Service > Communication Ports and Protocols
  
Communication Ports and Protocols
Vuforia Studio leverages web-based protocols for communication with clients. These protocols are primarily HTTP(S) over standard web ports.
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.