Generic Load is able to unpack and transform files immediately after they are received, without waiting for download queues. Files for load should be sent via eagle_ml-2-0_default_cm_ndfa
In this page:
Table of Contents |
---|
Configure Profiling for Generic Load
First of all, create a profile in the EJM Monitoring Tool
...
profileName is the profile name used to generate names of new workflow and other files - must be unique for each profile;
workflowName is the source workflow name used to generate new workflow;
inMask{number} describe incoming file masks. Must be coherent and start with number 1. Each record should contain the following values, separated by “|”:
- incoming file mask;
- incoming file maskTranslator translator for incoming mask (if you do not want to use a translator, specify empty string). Must match transform_pairs.inc;
- comma-separated feed types for load available for this translator (should not contain duplicates).
...
Code Block | ||
---|---|---|
| ||
<CODE> :pair1: := '_SRM__PROFILED_LOAD_TST|_srm_tr'; :pair2: := '_FUND_PROFILED_LOAD_TST|_fund_profile_5_tr'; :pair3: := '_FUND_ALT_ID_PROFILED_LOAD_TST|_fund_profile_alt_id_tsk'; :pair4: := '_HOLDING_PROFILED_LOAD_TST|_wh_pos_tr'; :pair5: := '_TRANS_PROFILED_LOAD_TST|_wh_cash_activity_tr'; </CODE> |
Create Schedule Event
Info |
---|
Please note, that the schedule described below is time-based. This means that incoming files are expected to arrive within the time interval specified. If the files were not received on time, the cycle of pending for them is reset. |
Create workflow_restart stream (must be created once for a region)
...