...
The workflow contains one ExecuteCM task only. The task runs eagle_wrf_generic_extract_mc2 workflow with the following pre-selected default parameters:
| Parameter | Default Value |
|---|---|
| ebs:default:DeltaBased | Y to extract delta only |
| ebs:default:DeltaBasedUID | AZURE_CLOUD unique uid for delta |
| ebs:default:OutputFormat | EagleJSON - to extract in EagleJson format |
| ebs:default:TargetSinkType | azureblob - to publish extract data to azure |
| DisableDistributionStep | Y - to skip distribution step in mc2 workflow |
| FeedType | ebs:warehouseposition, ebs:warehouseperformance, ebs:warehousenav, ebs:exchangeprice,ebs:smf,ebs:genericentity, ebs:codevalue, ebs:issuefxrate,ebs:warehousetrade, ebs:issueprice,ebs:errordefinition |
...
The following parameters can be set in the profile:
| Parameter | Value |
|---|---|
| interface | The list of ebs interfaces separated by comma |
| OutputFormat | Default value is EagleJSON |
| TargetSinkType | Default value is azureblob |
| ExcludeZero | Default value is Y |
| Includenull | Default value is Y |
| DisableDistributionStep | Default value is Y |
- To create a new profile, open Monitoring Tool and select the Activities tab.
- Click the Add Profile button.
- Complete the appeared form as shown below.
Action – Execute Workflow
Workflow – eagle_wrf_cloud_workflow
Task Parameters - the parameters to change - Select Save Profile As to save the profile.
You see the saved path in the Profile field.
- To use the profile in workflow execution by schedule, add in Automation Center to schedule the rule.
1166 tag with profile name, for example, eagle_wrf_cloud_extract_mlperf.profile.
For MC versions 2017 and higher, you can add the parameter ProfileName instead of 1166 tag.