Using ICC Batch

To execute a Pipeline from the Operations menu as an ICC batch, the ./pipelineExecutor.sh script file is made available in the $FIC_DB_HOME/bin directory. You must enter the specified parameters in the ./pipelineExecutor.sh file required for Run Pipeline execution and then create an ICC Batch to call this script file through the Run Executable component.

To update the parameters in the ./pipelineExecutor.sh script file for Run Pipeline execution, follow these steps:

1. Navigate to the $FIC_DB_HOME/bin directory.
2. Update the script file by modifying the values that are enclosed within the ## symbols. The following is an example for the format:
   pmfscriptexe="./wfExecExternal.sh null '##PROCESS_NAME##' $objectId null '##INFODOM##' '##SEGMENT##' '##USER##' en_US '{##EXECUTION PARAM JSON##, \"FIC_MIS_DATE\":\"$datevar\"}' null"
   The following list provides descriptions of the script file parameters:
   • Process_Name - Enter the process name of the Pipeline. This is a required parameter.
   • $objectId - This is an auto-generated unique Object ID that you must not modify. Retain $objectId in the script as this mandatory parameter is created by the PMF application during the execution of the Run Pipeline.
   • INFODOM - Enter the Information Domain name here.
   • SEGMENT- Enter the Segment name here.
   • USER - Enter the user ID here.
   • locale - Modify the locale as required. For example, for English-United States, enter en_US.
   • EXECUTION PARAM JSON - Enter the Run Execution parameters in JSON format.
   The following code snippet is an example:
   {\"hierDetailsLE\":[{\"hierValueCode\":\"ORG_NAME\",\"value\":\"ORG_NAME\",\"hierNodeCode\":\"ORG_NAME\",\"leafCondition\":\"CASE WHEN DIM_ORG_STRUCTURE.f_latest_record_indicator = 'Y' THEN DIM_ORG_STRUCTURE.v_entity_code END='ORG_NAME'\",\"hierNodeDesc\":\"ORG_NAME\"}],\"CONSOTYPE\":\"SOLO\",\"hierDetailsRCY\":[{\"hierValueCode\":\"INR\",\"value\":\"India n Rupee\",\"hierNodeCode\":\"INR\",\"leafCondition\":\"DIM_CURRENCY.v_ iso_currency_cd = 'INR'\",\"hierNodeDesc\":\"Indian Rupee\"}],hierDetailsUDRS: [{\"hierValueCode\": \"BISNONSECSTD- SETUP1\", \"value\": \"BIS Non Sec STD - Setup 1\",\"hierNodeCode\":\"BISNONSECSTD-SETUP1\",\"leafCondition\":\"USR_DEFINED_RUN_PARAMETERS.V_RUN_PARAMETER_SETUP_CODE ='BISNONSECSTD-SETUP1'\", hierNodeDesc: \"BIS Non Sec STD - Setup 1\"}],\"FIC_MIS_DATE\":\"$datevar\",\"V_RUN_MAIN_DESC\":\"RUNMARCH09\"

   • $datevar - Retain $datevar variable in the execution param JSON specified in the preceding list without any modification as this gets replaced by the FIC_MIS_DATE selected during batch execution as the date value for the Run execution.
3. Create a new batch in the Batch Maintenance window in the Operations menu. For more information, see the Adding Batch Definition section in the OFS Analytical Applications Infrastructure User Guide.
4. Create a new task with the Run Executable task component. For more information, see the Adding Task Details section in the OFS Analytical Applications Infrastructure User Guide.

   Figure 5-10 Call pipelineExecutor.sh in the Executable field

   
   

   

   
   

   • Call the pipelineExecutor.sh script file in the Executable field.
   • Select Y in the Batch Parameter drop-down list for all cases.
   • Select Y in the Wait drop-down list if you want the Run executable to wait to finish the task execution and then update the task status.
5. Click Save to execute the Batch.
6. Schedule a batch through the Batch Scheduler window in the Operations menu or schedule and execute the batch through the External Scheduler (ESIC). For more information, see the Batch Scheduler and External Scheduler Interface Component sections in the OFS Analytical Applications Infrastructure User Guide.