...
The eagle_wrf_cloud_extract workflow was created to periodically execute EBS extracts.
Default Parameters
The workflow contains one ExecuteCM task only. The task runs eagle_wrf_generic_extract_mc2 workflow with following pre-selected 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 |
...
- Open eagle_wrf_cloud_extract in IWS.
- Expand CustomCMParams to execute_ebs_extracts.
- Add a new parameter with the name ebs\5C3Amycustomsmfextract\5C3Amaxrows and a value of 100.
Note: IWS does not replace the colon with \5C3A for parameter names automatically, so you must write \5C3A in place of the colon in the parameter name.
- Save and publish the solution.
- Re-initialize the classic MC cache.
- To save changes in Bitbucket, commit the following files:
tpe\dynamic\msgcenter\eagle_ml-2-0_workflows\eagle_wrf_cloud_extract.wrf
tpe\dynamic\msgcenter\eis\ejmwf\eagle_wrf_cloud_extract.ejmwf
Use Profile to
...
Run the
...
Workflow
To support custom parameters, MC2 uses the workflow profile for eagle_wrf_cloud_extract workflow.
The following parameters can be set in the profile:
interface – the list of ebs interfaces separated by comma
...
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 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.
...