Vuforia Studio Deployment
The deployments discussed here are focused on the server-side aspects of Vuforia Experience Service, the components that store and distribute Vuforia Studio experiences.
Vuforia View - Delivers experiences rich with 2D and 3D graphics, augmented reality (AR), and real-time product data. Experiences augment the view of your immediate surroundings with context-sensitive information and graphics, enabling you to interact directly with the things around you.
Vuforia Studio - A web-native, easy-to-use tool for authoring domain and task specific experiences that provide an integrated view of digital and physical product data, dashboards, and alerts with 2D, 3D, and augmented reality. When creating experiences in Vuforia Studio, you can choose from various tracking methods:
Spatial tracking
Model targets
Image tracking
Vuforia Experience Service - An enterprise-class, secure, and scalable server that publishes, updates, and deletes experience content generated through Vuforia Studio. It also identifies and delivers Experience content requested through Vuforia View.
Vuforia Global Experience Index (GXI) - Allows for multiple Vuforia Experience Services to be queried by the Vuforia View application. The GXI creates and maintains an index of all Experiences that are maintained within the associated Vuforia Experience Service.
When the GXI receives a ThingMark query, it identifies the Vuforia Experience Service that hosts the desired Experience and redirects the query to that specific Vuforia Experience Service. By default, Vuforia View uses the GXI, but it can also be manually configured to reference a different Vuforia Experience Service.
Deployment Considerations
ThingWorx Foundation must be installed and established before installing the Vuforia Experience Service.
For production systems, it is recommended to run ThingWorx Foundation and Vuforia Experience Services on separate servers.
For production systems, it is recommended to use PostgreSQL as the database associated to the Vuforia Experience Service.
To avoid performance lag, it is recommended to have separate PostgreSQL servers for ThingWorx Foundation and Vuforia Experience Service.
Reference Architectures
The following diagrams focus on Vuforia Experience Service, and only depict a simplified reference to ThingWorx Foundation. However, any ThingWorx Foundation architecture shown in this guide may be used instead.
Production Deployment - The following diagram depicts a production deployment of the Vuforia Experience Service. It includes the following features:
One Vuforia Experience Service
Hard disk space to store Experiences
PostgreSQL database to maintain Experience metadata
Access to ThingWorx Foundation Server to manage authentication and authorization
Cloud Deployment - Vuforia Experience Service can be deployed in cloud services such as Azure or AWS. The Experience Service would be installed on its own virtual machine, with attached storage for the experience repository.
List of Components
Number of Components
Vuforia Studio Experience Service
ThingWorx Foundation Server
Enterprise NFS Repository
Vuforia Experience Service Database
Was this helpful?