On This Page:

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:

The values for FeedType and ebs:default:TargetSinkType can be overridden by the following variables in the w_config_custom.inc file:

        w_ebs_cloud_interfaces

       w_ebs_cloud_targetsink

For instance, to extract SMF interface only and to disable distribution to Azure, define the parameters as shown below:

<CODE>

   :w_ebs_cloud_interfaces: := 'ebs:smf';

   :w_ebs_cloud_targetsink: := ' ';

</CODE>

The workflow can be executed periodically using schedule rule/events.

Add New Interface

There are two methods for adding a new interface such as an interface called mycustomsmfextract.

Method One

You can override the default feedtype value using the w_ebs_cloud_interfaces variable.

1. Open tpe\dynamic\msgcenter\eagle_ml-2-0_custom_cm\w_config_custom.inc

2. Add/modify w_ebs_cloud_interfaces value.

   <CODE>
   
      :w_ebs_cloud_interfaces: := 'ebs:smf,ebs:mycustomsmfextract';
   
   </CODE>

3. Save the file.
4. Re-initialize the classic MC cache.

Method Two

You can add the new interface in IWS

1. Open eagle_wrf_cloud_extract in IWS
2. Expand CustomCMParams for execute_ebs_extracts
   
3. Add the interface at the end of value before last single quote.
   
4. Save &Publish solution.
5. Re-initialize the classic MC cache.
6. 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 example, to reduce extracts, apply maxrows=100 to all EBS extracts.

1. Open eagle_wrf_cloud_extract in IWS.
2. Expand CustomCMParams for execute_ebs_extracts.
3. 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.
   
4. Save and publish the solution.
5. Re-initialize the classic MC cache.
6. 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, you can reduce mycustomsmfextract by applying maxrows=100 to the extract.

1. Open eagle_wrf_cloud_extract in IWS.
2. Expand CustomCMParams to execute_ebs_extracts.
3. 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.
   
4. Save and publish the solution.
5. Re-initialize the classic MC cache.
6. 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 profile:

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 new profile please open Monitoring Tool, go to “Activities” tab and press Add Profile button:

Fill the appeared form as shown below

Action – Execute Workflow

Workflow – eagle_wrf_cloud_workflow

Task Parameters: - the parameters to change

Then press Save Profile As.. button and save profile

The saved path will be shown in Profile field:

To use the profile in workflow execution by schedule you should add in Automation Center to schedule rule

1166 tag  with profile name(E.g. eagle_wrf_cloud_extract_mlperf.profile). For mc versions  2017 and higher you can add parameter ProfileName instead of 1166 tag.