1.2.1 Prerequisites in Oracle Banking Trade Finance Cloud Service

The prerequisites in OBTFCS for this integration are as follows:
  • You have to maintain OBRH_URL param in CSTB_PARAM for communication type / Channel OBRH.
  • You have to maintain the following details in ‘Trade finance external service maintenance (IFDTFXSE) screen:

    Table 1-2 Trade finance external service maintenance

    Field Description
    External System Source code of external system For example: ‘ELCM’
    External User User to be provided, this user should be present in OBTF and ELCM
    Type Request Type should be selected.

    SOAPRequest – For External System type ‘Default’

    REST Request - For External System type ‘OBRH’
    Service Name ELUtilizationService
    WS Endpoint URL Related service name to be provided
    External System Type External System type should be selected.

    Default – Direct integration with FCUBS

    OBRH – Integration of DDA system via OBRH
    Header Profile Header Profile for the OBRH should be selected.

    Header profile can be maintained in the screen (MSDHPROF - HTTP Header Parameters)
  • Contracts are fetched from ELCM and displayed in OBTFCS through External LOV and the External LOV is applicable to Web-logic application. In order to fetch the details from ELCM, user has to maintain an active record in Integration Parameter Maintenance screen (IFDINPRM) with following details,

    Table 1-3 Integration Parameter Maintenance

    Field Description
    Branch Code Branch Code to be provided, branch should be present in OBTFCS and ELCM.
    External System Should be source code of external system e.g.: ‘ELCM’.
    External User User to be provided, this user should be present in OBTFCS and ELCM.
    Entity ID Entity ID to be provided, this external id should be present in external system.
    External Branch Code Branch code to be provided, this branch code should be present in external system.
    Service Name ExtLovServic
    Communication Channel Select the communication Channel for integration.

    REST – Default Communication channel for ExternalLovService

    OBRH – Communication channel for all services when integrated via OBRH
    Communication Mode SYNCHRONOUS
    Communication Layer Application
    Rest Service IP and Port Should be ‘ELCM’ Application IP and Port.
    Rest Service Pattern LovService
    Rest Service Context FCJNeoWeb
    Header Profile Header Profile for the OBRH should be selected.

    Header profile can be maintained in the screen (MSDHPROF - HTTP Header Parameters)

Parent topic: Prerequisites