1. User Guide
  2. Technical Details
  3. Executing Intraday Post Load Batch and Intraday Real Time Run

B.7 Executing Intraday Post Load Batch and Intraday Real Time Run

This section details the steps to execute Intraday Post Load Batch and Intraday Real Time Run from Command Line.
  1. Environment Prerequisites for External Scheduler Utility The following are the Environment Prerequisites for External Scheduler Utility:
    • JAVA_HOME (Required) points at JAVA bin installation directory.
    • ES_HOME (Required) points to the ES Home folder ($FIC_HOME/utility/ES).
    • Go to ES Utility directory in $FIC_HOME/utility/ES/conf.
    • Update <Infodom>.ini file and specify the values.
    • MISDATE= Enter the MIS Date in format mm-dd-yyyy (example: MISDATE=01-31-2010)
    • USERNAME= Log into OFSAAI (example: USERNAME=BASELUSER)
    This must be updated daily once for the MISDATE.

    Note:

    <infodom> in the name of the file <infodom>.ini must be replaced with the infodom name.
  2. Intraday – Real Time – Incremental Load Processing
    Prerequisite
    The following are the prerequisites for Intraday – Real Time – Incremental Load Processing:
    1. The Load Run ID must be generated and the corresponding entry is present in the table REV_LOAD_RUN_MASTER. The Load Run ID population occurs in sequence for every successive staging load. The application recognizes the maximum value of Load Run ID as corresponding to the latest data.
    2. The stage tables must be loaded with the load Run ID.
    3. For Incremental Snapshot Load: For <INFODOM>_INTRADAY_POST_LOAD batch, the parameter passed to Task1 is ‘I’ (By default ‘I’ is present).
      The following steps must be followed to execute the Intraday Post Load batch and Intraday –Real Time - Incremental Run:
    4. Go to $FIC_HOME/ficapp/icc/bin.
    5. Execute IntradayIncrementalLoadBatch.sh (The execute permission must be provided if needed).
      This triggers the Intraday Post Load batch and Intraday –Real Time - Incremental Run.
      To automate the incremental load process during the day, this task is appended as the last task while triggering stage table population.
    6. You can view the ES batch logs for individual batch run in the following location: $ES_HOME/log/ESIC_<batchrunid>.log
    7. You can view the task level logs in the following location:
      $FIC_HOME /ficdb/log
      /ftpshare/OFSTRINFO/logs
    8. All the latest records for the MIS_DATE are moved to reporting.
  3. Intraday – Real Time – Complete Snapshot Load Processing
    Prerequisite
    1. The Load Run ID must be generated and the corresponding entry is present in the table REV_LOAD_RUN_MASTER.
    2. The Load Run ID population occurs in sequence for every successive staging load. The application recognizes the maximum value of Load Run ID as corresponding to the latest data.
    3. The stage tables must be loaded with that load Run ID.
    4. For Complete Snapshot Load: <INFODOM>_INTRADAY_POST_LOAD batch, it must edited through OFSAAI and the parameter ‘S’ is passed to Task1. (By default, ‘I’ is present).
      The following steps must be followed to execute the Intraday Post Load batch and Intraday –Real Time - Snapshot Run:
    5. Go to $FIC_HOME/ficapp/icc/bin.
    6. Execute IntradaySnapshotLoadBatch.sh (Give execute permission if needed).
      This triggers the Intraday Post Load batch and Intraday –Real Time - Snapshot Run.
      To automate the incremental load process during the day, this task is appended as the last task while triggering stage table population.
    7. You can view the ES batch logs for individual batch run in the following location:
      $ES_HOME/log/ESIC_<batchrunid>.log
    8. You can view the task level logs in the following location:
      $FIC_HOME /ficdb/log
      /ftpshare/OFSTRINFO/logs
    9. All the records corresponding to the latest load Run ID registered in the table REV_LOAD_RUN_MASTER for the MIS_DATE is moved to reporting.