Install and Configure the Experience Service
  
Install and Configure the Experience Service
The Experience Service is composed of the following components:
Component
Description
Content Delivery Service (CDS)
The CDS manages experience content by providing APIs for publishing, retrieving, updating, and deleting experience content. It provides access control capabilities that can be used to control the actions users can perform on content.
ID Resolution Service (IRS)
The IRS manages mappings that are used to link the identities of things to content managed by the CDS. The mappings are used to associate Experiences with things. The mappings can provide direct links from identifiers to Experiences or create a chain of mappings between multiple identifiers that eventually leads to an experience. When queried for the set of Experiences associated with a particular identifier, the IRS navigates all links, including chains of links, to find all Experiences associated with that identifier.
ThingWorx integration
The Experience Service leverages the user and group management capabilities of the ThingWorx core server for authentication and authorization. The Experience Service also acts as a proxy for the ThingWorx core server. These two characteristics allow clients to access both experience content and IoT data with a single set of credentials.
* 
Edge devices and mashups should not be connected to the ThingWorx server using the proxy provided by the Experience Service. Instead, they can be accessed directly through ThingWorx using alternative ports, Enterprise Load Balancer (ELB), and so on.
An Experience Service project is composed of content for one or more Experiences and a metadata file that specifies information about the Experiences. For example, the device features required to render the experience and the identifiers that each experience should be associated with.
When a client, such as Vuforia Studio, publishes a project to the Experience Service, the content for the Experiences is stored in the CDS, and the required mappings are created in the IRS to link the experience content with the identifiers that were specified in the project's metadata.
After the project has been published, a client, such as Vuforia View, can query the IRS to find Experiences that are associated with a particular identifier such as a ThingMark. After receiving the list of Experiences, the client can choose to download the content for one or more of the Experiences. When a client renders an experience, the experience uses the ThingWorx proxy to access IoT data to be displayed in or modified by the experience.
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 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.