Skip to main content
Skip table of contents

RPI Realtime architecture


The following sections describe RPI Realtime’s components.

RPI Realtime API

The RPI Realtime API is an interface that provides functionality such as:

  • The management of visitor profiles

  • The ability to make content applicability decisions

  • The processing of RPI web forms

  • The handling of communication with the RPI application server

RPI’s realtime capabilities are exposed via a website, which provides an API, and, optionally, its associated documentation.

You can access the site by navigating to the RPI Realtime website, either directly within a browser, or using the Browse command in Internet Information Services (IIS).

When you do so, the following web page is displayed:

If enabled, clicking the button in the API Documentation section displays details of the RPI Realtime API’s endpoints.

Realtime Agent Service

The RPI Realtime Agent Service is an ASP.Net Web API service which provides the ability to load information from the RPI app server, including:

  • Cached attribute lists

  • Message history

  • Page and decision metadata

  • Database connectivity to facilitate usage of the same as a cache

Realtime Cache

The RPI Realtime realtime cache is used to persist data such as the following:

  • Visitor profiles

  • Rules as defined in realtime decisions

  • Text content (if published directly from a smart asset)

A variety of technologies can be used to host the realtime cache, including:

  • Azure Redis Cache

  • Cassandra

  • CosmosDB

  • Google Bigtable

  • MongoDB

  • Redis

  • SQL Server


RPI Realtime makes use of the following queues, which are used to provide asynchronous connectivity from the RPI Realtime API to the RPI application server:

  • Form submission: used to process data submitted in a web form.

  • Web events: used to process web events other than form submissions.

  • Visitor profile: used to process visitor profile data from the realtime cache to a database or file.

Each queue has its own matching system configuration setting that must be set appropriately.

Queues can be hosted using a variety of technologies. Queue Providers can be created and managed in a dedicated configuration interface. The following technologies can be used to host RPI Realtime queues:

  • Azure Event Hubs

  • Azure Service Bus

  • Azure Storage Queues

  • Google Pub Sub

  • RabbitMQ

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.