Publishing Original and Transformed Inbound Files in Generic Loader

This feature works in Message Center classic Generic Load Workflow implementation only.
The Generic Loader can be configured to publish either the Original or Transformed inbound data files (or both) to Azure or SFTP.
The publication is done using MC2 to distribute the files to destinations configured in EDS Distribution Profiles. The configuration of distribution profiles is detailed at https://eagledocs.atlassian.net/wiki/spaces/MC2/pages/881786970/Distribution+to+Multiple+Destinations+Starting+August+2019+Release. This page will guide you on how to configure a distribution profile. The Generic Loader workflow supports publishing Original and Transformed files to different profiles. Also, the user can choose to distribute only the Original or only the Transformed files.

Configuring the Default Distribution

The eagle/estar/tpe/dynamic/msgcenter/w_config_custom.inc can be used to configure the default distribution profiles. To configure the distribution profiles you can add the following parameters to w_config_custom.inc:
<CODE>
:TransformedFileDistributionProfile: := 'transformed_distribution_profile_name';
:OriginalFileDistributionProfile: := 'original_distribution_profile_name';
</CODE>
The TransformedFileDistributionProfile parameter defines the name of the Distribution Profile to be used to distribute the transformed file.
The OriginalFileDistributionProfile parameter defines the name of the Distribution Profile to be used to distribute the original files. If a ZIP file is received the Generic Loader Workflow will distribute unzipped files.
If the above parameters are not defined or are empty the files will not be distributed.