Admin: Data Intake Setup

Please follow these steps to set up RPI’s Data Intake functionality, which allows you to load files into your data warehouse using the Data Project Designer.

Before commencing setup of Data Intake, please ensure that the following pre-requisites are in place:

1. RPI is installed.

2. Redpoint Data Management v6 or later is installed.

Follow these steps to install Data Intake:

Data Intake Share Folder

1. Create a folder named DataIntake where files will be loaded and processed.  ‘C:\Program Files\Redpoint Global\RPI\’ is a reasonable place to create this, but it may be created anywhere.

2. Create four sub-folders inside the newly created folder.

   • Processing

   • Archive

   • Upload

   • Reference

3. Open the DataIntake folder’s Properties dialog, and navigate to the Sharing tab.  Ensure that the RPI Execution service user has read and write access to this folder and all of its sub-folders.

4. If the above folder and share do not reside on the same physical or virtual as the RPI server, update the following configuration values in RPI:

   • DataIntakeArchiveDirectory

   • DataIntakeLandingDirectory

   • DataIntakeProcessingDirectory

   • DataIntakeProcessingDirectoryDataManagement

Data Management Configuration

1. Macros

   1. Connect to Redpoint DataManagement via your RedpointDM.exe client.

   2. On the left side are the Palette and Repository tabs, select the Repository tab.  Right click on repository and select load from archive.

      

   3. Import Redpoint_macros_object.dlb from the source folder (Example: C:\source\Resonance\Database Scripts\DataManagement Macros).

   4. If the following dialog is displayed, please select Skip duplicate items.

      

   5. Validate that a folder named “RedpointMacros” now exists in the repository.

2. Database Connections

   1. Browse in the repository to data connections.

   2. Right-click on data connections – select “New connection”.

   3. Create 2 new data connections: 

      • RPI_AuditDB – this connection will connect to the interaction audit database.

      • RPI_MainDB – this connection will connect to the main data warehouse.
        Note that the data connections should be in sync with the respective connections in the Server Workbench Clients interface.

   4. Configure the above data connections per the specifics of your environment, with users who have DB owner level permissions.

   5. If you are configuring a multi-tenant environment on the same data management instance, an additional pair of connections will be required for each tenant.  The names of the connections must start with “RPI_”.  We recommend RPI_AuditDB_[Tenant Name] and RPI_MainDB_[Tenant Name].  In this case, the AuditDatabaseSourceName and MainDatabaseSourceName configuration values in RPI must also be configured. 

3. Set the following system configuration settings:

   • AuditDatabaseSchema: the schema to use for the processing engine to write back logging information.

   • AuditDataSourceName: the connection string to use for the processing engine to write back logging information.

   • MainDatabaseSchema: the Data Intake data warehouse schema.

   • MainDatabaseSourceName: the Data Intake data warehouse connection string.

   • DataManagementCredentials: the credentials used to sign in to Data Management.

   • DataManagementExecutionServer: Optional setting to force RPI triggered data management jobs to run on a specific execution server.

   • DataManagementIntegrationType: the method to be used in communicating with Data Management. Set 0 to designate legacy method, set 1 to use the Operational API web service.

   • DataManagementOAPIWebServiceAddress: the configured URL to connect to the OAPI web service.

   • DataManagementServerName: the RPDM Site server hostname to be used.

   • DataManagementServerPort: the Port number used to connect in Data Management (normally 20400 for DM7, 20410 for DM8).