Skip to main content
Skip table of contents

Configuring the tenant

The Tenant Configuration interface is used to set properties relating to the current RPI tenant. It contains the following:

  • Tenant ID: read-only; a GUID property that is used to uniquely identify the current RPI tenant.

  • Name: this mandatory property must be unique within the current RPI installation. It accepts a maximum of 100 characters.

  • Description: this optional property accepts a maximum of 1000 characters.

  • Database Suffix: read-only; the suffix appended to the names of the 'Interaction_[xxx]' and 'InteractionAudit_[xxx]' operational databases.

  • Icon: a default icon is provided. You can click the accompanying Change button to display a Windows file system dialog, in which you can select an image to serve as the tenant’s new icon.

  • Client colors: it is possible to customize the colors used to display the tenant’s name at the top of the RPI client application. Foreground and Background colors can be defined. You can set colors using the Choose Color dialog. Clicking OK changes the color; clicking Cancel removes the dialog from display without changing the color. The Revert button provided allows you to revert the client colors back to their defaults.

  • Install Status: one of:

    • Not Installed

    • Installed

  • Persistence State: one of:

    • Unchanged

    • Added

    • Edited

    • Deleted

Tenant Database Connections section

This section allow you to configure connection strings for the current RPI tenant. It contains the following:

  • Operational Database

    • Test button

  • Auditing Database

    • Test button

  • Database Mode: read-only; one of:

    • SQL data warehouse with any auxiliary databases

    • NoSQL databases only

    • NoSQL databases with SQL auxiliary databases

  • Data Warehouse Database

    • Encrypt button

    • Test button

  • Read-only Data Warehouse Database

    • Encrypt button

    • Test button

  • Data Warehouse Platform: read-only

  • Auxiliary databases: you can optionally define one or more auxiliary databases to augment the data warehouse, and to serve as an additional source of segmentation data.

The property is accompanied by a Manage Auxiliary Databases button, which, when clicked, displays the Manage Auxiliary Databases overlay, which is documented separately.

JavaScript errors detected

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

If this problem persists, please contact our support.