...
- Open EJM Monitoring Tool (MT) and choose Activities tab
- Under drop-down menu choose Add Generic Load Profile option
- Enter required parameters.
- Press Publish button to publish the profile.
Configure Profile Name
Profile name is set in the field between Workflow Name and _wrf_generic_load. Please be informed that profile name will be used as a prefix for profiled generic load, thus it is redundant to add profile extension or word “profile” in this field.
Configure Data Files Processing
...
To add files to the workflow user can click Add File button.
Remove File
To remove a file from the profile use Remove File button with focus set on the row you want to remove.
Please be advised that order of files does not affect processing order or order of load. Files will be consumed by profile executor on arrival to the region and results of translation will be loaded according to dependencies that are determined by eagle_wrf_generic_load workflow.
Configure file processing options
File mask in File Mask field (please be advised that wildcards are not needed and are not supported. Date rules are supported. Anything after @ symbol is considered as date rule and will be handled accordingly on processing
Name of translator in Translator field. It drops down a list allowing to choose a specific translator from existing list of streams on the region.
| Info |
|---|
To pass files to profiled generic load without translation, you should type "no translation" instead of a translator name. |
Feed type or feed types that are expected as result of translation of incoming file by the specified translator. Please be advised that there is a menu under the three dots symbol which allows to add common EagleML objects.
But user is free to just type in EagleML object names in the Feed Types field. This may be useful for cases when user needs to add EBD files ({EagleML feed type}EDB_DATA, {EagleML feed type}EDB_KEYS) or Cancel ({Feed type group}CANCEL{Feed type name} such as WarehouseCancelTrade, WarehouseCANCELCashActivity) files.
Configure Post-processing
...
Parameters – incoming parameters for Post Processing step. Use EXPR# to set parameter values that should be evaluated on runtime based on workflow launch parameters.
Example:
Configure Custom Parameters
...
Parameter names can be dynamic. To set dynamic parameters use EXPR# prefix before expressions to evaluate.
Configure customer/transform_pairs.inc
...