| Oracle® Retail Data Extractor for Merchandising Security Guide Release 16.0 E81280-01 |
|
 Previous |
 Next |
| Oracle® Retail Data Extractor for Merchandising Security Guide Release 16.0 E81280-01 |
|
Previous |
Next |
This chapter provides an overview of the security features included with Oracle Retail Data Extractor.
The following diagram provides a high-level overview of the physical deployment of Retail Data extractor.
Oracle Retail Data Extractor (ORDE) is the application which enables customers to extract data from Retail Merchandising System (RMS) source system for Oracle Retail Insights Cloud Services (RI) consumption previously known as RA (Retail Analytics).
Oracle Retail Analytics (RA) was converted from being an on-premise application to a cloud based service offering named Oracle Retail Insights Cloud Services (RI). Oracle Data Integrator (ODI) mappings for extracting data from the Retail Merchandising System (RMS) called as SDE Mappings (Source Dependent Extracts) were removed because RMS was an on-premise product and could not be sourced directly from the cloud.
RMS is the primary source of information for the RI application, so there was requirement to be able to extract data from RMS into flat files for uploading and importing into RI staging tables for loading the RI data warehouse.
Oracle Retail Data Extractor (ORDE) provides the functionality to integrate with RMS 16.0 and extract data in ORDE staging tables and then unload them in to respective flat files for RI consumption.
Oracle Database 2 Day + Security Guide, 12c Release 1 Oracle® Fusion Middleware Developer's Guide for Oracle Data Integrator
Authentication is required when Retail Data Extractor batch users execute Retail Data Extractor batch in the back-end. For the batch execution, the authentication, including the storage of the credentials of the database connection, is managed my ODI.
During the Retail Data Extractor installation, it is required to create a RI RMS batch user in RMS database. This user has the permission to access database objects owned by RMS data user. The permission is only on SELECT and is limited to the objects used by Retail Data Extractor.
During Retail Data Extractor installation, it is required to create different Retail Data Extractor database users with different permissions. The Retail Data Extractor database can be the same database with RMS. Within these database users, the Retail Insights data mart user is the user who owns target staging tables. The Retail Insights batch user is the user who executes Retail Data Extractor batch. The batch user is granted with SELECT, UPDATE/INSERT, and DELETE permissions to the resources owned by the Retail Insights data user. The Retail Insights batch user has the permission to logon on RMS database as RI RMS user to access RMS objects through a Database Link.
