Below is the detailed flow of OBTF integration through OBRH(SaaS).

• System enhanced to support OBTF integration through OBRH(SaaS)
• OBRH header parameters to be defined in HTTP Header Parameters (MSDHPROF) as profiles.
• Integration Parameters Maintenance – IFDINPRM enhanced as below:
  • New option OBRH is introduced in CommunicationChannel.
  • New field Header Profile introduced as LOV to capture profile defined in MSDHPROF
  • When Communication Channel isOBRH
    • Header profile should beprovided
    • Values should not be provided for fields namely WS Service Name, WS Port, WS Endpoint URL, WS User, WS Password, WS XSL File, CustomClassname,

ATM Server IP, ATM Server Port, MDB QCF, MDB Out Queue, MDB Response Queue, MDB Provider URL.

Validations introduced for the same with appropriate error messages

• Trade Finance External Service Maintenance – IFDTFXSE enhanced to capture OBRH details:
  • New field Header Profile introduced to capture profiles defined in MSDHPROF.
  • When External System Type is OBRH :
    • Header Profile should be provided
    • Type should not be Soap
    • Values should not be provided for fields namely WS Endpoint URL,

Rest Service Context, Rest Service IP, Rest Service Pattern and Rest Service Port.

Validations introduced with appropriate error messages.

• Trade Finance External System Maintenance – IFDTFEPM enhanced to capture OBRH details:
  • New field Communication Type introduced as a drop down with values Default and OBRH
  • New field Header Profile introduced as LOV with profiles defined in MSDHPROF.
  • When Communication Type is OBRH:
    • Header profile should beprovided
    • Values should not be provided for fields namely : Rest/Web Service User option, Rest/Web Service User and Rest/Web ServiceURL

Validations introduced with appropriate error messages.

• Scripts provided as part of brownfield deployment:
  • New parameter introduced in CSZB_PARAM to capture OBRH details withPARAM_NAME as OBRH_URL.