At the heart of an RPI server lies its ‘core’. The core consists of:
•An initial cluster node (installed on a single physical or virtual machine). By default, the initial node always supports the Node manager role.
•Core operational databases (which can be installed upon the same or another machine).
Optionally, the RPI server cluster can be expanded to include additional cluster nodes. Each cluster node, including the initial node, will expose the Node manager role. In addition, each can expose the following roles:
•Windows services
•Web services
•Help files
The server communicates with a data warehouse (SQL Server, Oracle, Teradata, Netezza, GreenPlum Database, MySQL, Sybase IQ, AWS RedShift, Postgres, SQL Server PDW, DB2, Splice Machine, Azure SQL Database, Azure Synapse Analytics, Azure Database for MySQL, Azure Database for PostgreSQL, MariaDB, Vertica, SAP HANA, Amazon Aurora, Google BigQuery, Snowflake or Yellowbrick), which contains details of the individuals (typically customers and/or prospects) with whom you wish to communicate using RPI.
An RPI server must contain at least one client. If operating in a multi-tenancy capacity, many clients can be hosted in the same installation.
In addition, a server can support many users. Each user may access one or more clients.
The concepts introduced above are described below: