Add the interface at the end of value before last single quote.
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 New Task Parameter for EBS Extracts
The common parameter name has ‘ebs:default:’ prefix. For example, to reduce extracts, apply maxrows=100 to all EBS extracts.
To add new task parameter for 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, you can reduce mycustomsmfextract by applying maxrows=100 to the extract.
To add EBS extract specific parameter:
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.
To use profile to run the workflow:
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.
Select Save Profile As to save the profile. You see the saved path in the Profile field.
Action – Execute Workflow Workflow – eagle_wrf_cloud_workflow Task Parameters - the parameters to change
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.