Prerequisite for Data Pipeline

The below are prerequisites for Data Pipeline. The steps need to be executed before triggering MMG Installer.
  1. Log in as DB user(ex: fccmdb) in your DB server (For example: 1759).
  2. Create one directory with preferred reference name (For example: datapipline) at the preferred location.
  3. Now execute below commands in putty session of DB server:
    • mkdir -p ##location of dir created in step 2##/file_store/fs_list/logs # A directory by the external table to write the logs.
    • mkdir -p ##location of dir created in step 2##/file_store/fs_list/script # A directory to hold a pre-processor script used to list the files in a directory. This needs Read-Execute permissions.
    • mkdir -p ##location of dir created in step 2##/file_store/fs_list/control # A directory to hold files to control which directories can be listed. This needs Read permissions.
    • mkdir -p ##location of dir created in step 2##/file_store/fs_list/fccm-data # A directory to store the csv files.
  4. After that login to DB server(For example: 1759) as sysadmin( For example: sys) in sqldeveloper or any preferred application execute below:
    • CREATE OR REPLACE DIRECTORY fs_list_logs_dir AS '##location of dir created in step 2##/file_store/fs_list/logs';
    • GRANT READ, WRITE ON DIRECTORY fs_list_logs_dir TO ##MMG Application Schema##;
    • CREATE OR REPLACE DIRECTORY fs_list_script_dir AS '##location of dir created in step 2##/file_store/fs_list/script';
    • GRANT READ, EXECUTE ON DIRECTORY fs_list_script_dir TO ## MMG Application Schema##;
    • CREATE OR REPLACE DIRECTORY fs_list_control_dir AS '##location of dir created in step 2##/file_store/fs_list/control';
    • GRANT READ ON DIRECTORY fs_list_control_dir TO ##MMG Application Schema##;
    • CREATE OR REPLACE DIRECTORY external_tables_dir AS '##location of dir created in step 2##/file_store/fs_list/fccm-data';
    • GRANT READ ON DIRECTORY external_tables_dir TO ## MMG Application Schema##;
    • GRANT CREATE TABLE TO ##MMG Application Schema##;
    Once the above steps are done, trigger the installation of Compliance Studio build.

    Note:

    • If the new schema is residing on any-other DB server other than the one on which above steps were performed. Please perform all the above steps on that respective server.
    • Once configured the DB server, if new schema is created on it. Need to perform the step for the respective schema.