Accelerator architecture

The objective of this accelerator is to limit the amount of coding within the AR experience while delivering a robust set of data and features to build CX AR experiences on top of. To achieve this, we leverage a set of generic integration calls from the AR experience to Oracle Integration Cloud (OIC) or simulated within JSON files included within the app itself..

OIC contains the majority of the configuration for both the AR application and its integrations to other services to take place. Within this accelerator’s downloadable content, we have included a number of OIC flows that provide API endpoints for the following:
  • Getting demo specific configurations, such as what service application (Engagement Cloud or Service Cloud) to use for service requests.

  • Pulling device and message IoT data for the device from IoT Cloud Service.

  • Submitting service requests about the device to either Engagement Cloud or Service Cloud.

  • Retrieving knowledge content from a knowledgebase.

For functionality that is not served by an Oracle application, such as the contextual data related to a 3D model node, the application simulates REST API calls to a service that would host contextual data about each node in a 3D model.
Note: The models/simulator folder in the project source contains example JSON files as examples for API calls to both Oracle REST endpoints and simulated endpoints. The “ARContextNode.json” file contains much of the configuration for interacting with the 3D model included with this accelerator.

The following images describe the high-level approach to the data processes within the application.