On This Page:
| Table of Contents |
|---|
The eagle_wrf_cloud_extract workflow was created to periodically execute EBS extracts.
The workflow contains one ExecuteCM task only. The task runs eagle_wrf_generic_extract_mc2 workflow with following pre-selected parameters:
| Parameter | 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 |
FeedType The values for FeedType and ebs:default:TargetSinkType Values can be overridden by the following variables in the w_config_custom.inc file:
w_ebs_cloud_interfaces
...
There are two methods for adding a new interface , for example such as an interface called mycustomsmfextract.
...
- Open tpe\dynamic\msgcenter\eagle_ml-2-0_custom_cm\w_config_custom.inc
Add/modify w_ebs_cloud_interfaces value.
<CODE>
...
Code Block language js <CODE> :w_ebs_cloud_interfaces: := 'ebs:smf,ebs:mycustomsmfextract';
...
</CODE>
- Save the file.
- Re-
...
- initialize the classic MC cache.
Second way.
...
Method Two
You can add the new interface in IWS
- Open eagle_wrf_cloud_extract in IWS
- Expand CustomCMParams for execute_ebs_extracts
...
- Add the interface at the end of value before last single quote.
...
- Save &Publish 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
Add New Task Parameter for EBS Extracts
...
Add Common Parameter for All EBS Extracts
Common parameter name has ‘ebs:default:’ prefix.For For example, to reduce extracts and , apply maxrows=100 to all ebs EBS extracts.
- Open eagle_wrf_cloud_extract in IWS.
- Expand CustomCMParams for execute_ebs_extracts.
- Add a new parameter with the name ebs\5C3Adefault\5C3Amaxrows and value of 100.
Note: IWS does not replace the colon with \5C3A for parameter names automatically, so you must write \5C3A in place of 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
Add EBS Extract Specific Parameter
Extract specific parameter name has ‘ebs:[interface name]:’ prefix. For instance we have to , you can reduce mycustomsmfextract by applying maxrows=100 to the extract.
- 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 we decided to use , MC2 uses the workflow profile for eagle_wrf_cloud_extract workflow.
...