2.2.2 ELCM with FCUBS/OBCL-ASYNC Mode

This topic describes about the ELCM with FCUBS/OBCL-ASYNC Mode in oracle banking ELCM Integration with OBCL/ FCUBS Process.

• For ASYNC installation mode, communication between the FCUBS/OBCL and ELCM does not happen in single transaction window.
• FCUBS/OBCL transaction authorization would not be allowed until response from limit system is received.
• During contract creation, if a limit request is created, FCUBS/OBCL logs the request to the service log tables.
• A job/scheduler processes these records from this table, creates a request xml and the sends the request to ELCM for processing.
• If the processing from the ELCM side has any overrides, then an override error message is converted to an information message, sent to FCUBS side stating the record have overrides which needs to be manually accepted/rejected.
• Override error message details and request xml are logged into the override tables in ELCM and to the cstb_overide tables.
• Override Action screen is introduced for accepting or rejecting the override information. In addition, the processing of the transactions are performed after the overrides are accepted or rejected.

Figure 2-2 ASYNC Mode

Description of "Figure 2-2 ASYNC Mode "