When embedding Reveal into web applications, the architecture is slightly more complex than with native apps, as two components are always involved:

  • Reveal Client SDK: a set of JavaScript libraries that needs to be integrated into the web application.

  • Reveal Server SDK: the server-side component to be integrated into the server application, currently this is an ASP.NET Core application targeting .NET Core 3.1 and newer.

In the following diagram you visualize the architecture for a web application embedding Reveal Web SDK:


As shown above, the SDK works pretty much the same way as with native apps. The difference is that some of the callbacks are invoked in the client side (like the event sent when a data point is clicked) and others are invoked server side (like the callback to load the dashboard or to provide in-memory data).

Hosting the Client-side and Server-Side Parts on Different Servers

You can host the client-side and the server-side parts separately i.e. on different urls.

To achieve this, set a property on the window object, as shown below:

$.ig.RevealSdkSettings.setBaseUrl("{back-end base url}");

Please, note that the trailing slash symbol is required in the URL in order to set the property successfully.

Set this property prior to the instantiation of the $.ig.RevealView.