1.2.2 Non-Functional Changes

This topics describes about the Non-Functional Changes.

Batch Service Adoption

  • Oracle Banking Liquidity Management batches are now migrated to Oracle Banking Micro Services Architecture Batch framework. This change would mean that the existing EODs will have to be redefined with new end points.
  • The following functional activity codes are added for the EOC process.
    • LMS_FA_SWEEPDATA_VIEW
    • LMS_FA_SWEEPDATA_CREATE
    • LMS_FA_SWEEPDATA_UPDATE
  • The following property is added for oblm-integration-services in the PROPERTIES table to enable/disable the Pending Maintenance check during EOD execution. "eod.pendingMaintenanceCheck.enabled"
  • For configuration and new functional activity code details, refer to Oracle Banking Liquidity Management Configuration Guide
  • For data migration details, refer to Oracle Banking Liquidity Management Data Migration User Guide

Event Hub Library Adoption

  • Oracle Banking Liquidity Management Event Hub is now based on the Oracle Banking Microservices Architecture Event Hub framework.
  • For further details, refer to Oracle Banking Liquidity Management Kafka Configuration Guide

Feed Service Adoption for File Uploads

  • The file uploads from Oracle Banking Liquidity Management will now happen through the Oracle Banking Microservices Architecture Feed Service. Please note the below changes in UI & Services due to Oracle Banking Microservices Architecture Feed Service adoption.
  • UI Changes:
    • The file upload screen under menu “Oracle Banking Liquidity Management System > Maintenance > Upload” will no longer be available. File uploads is now available in main screen itself, “File Management > File Upload” screen.
    • The screen Oracle Banking Liquidity Management System > Monitors > File Upload Monitor will no longer be available. The new screen to track status of uploaded files is now available in main screen itself, “File Management > View File Upload Status
  • For the File Management screen details, refer to Oracle Banking Microservices Platform Foundation User Guide
  • For the File Upload templates, refer to below guides:
    • Oracle Banking Liquidity Management File Upload User Guide
    • Oracle Banking Common Core User Guide
  • For the File Upload initial setups, refer to Getting Started Installation Guide

Oracle Banking Routing Hub adoption for investment sweeps

  • Following integrations for investment sweeps will happen through Oracle Banking Routing Hub:
    • Integration with Oracle Banking Treasury Management for Money Market investments
    • Integration with Oracle FLEXCUBE Universal Banking System for Term Deposits

Day 0 Configuration Changes

  • The current process of manually doing Day 0 set up using SQL scripts has been changed and UI has been made available.
  • For further details, refer to Oracle Banking Multi-Entity Deployment Guide

Migration of Schema for Existing Pool Structures

  • Existing clients who have deployed oblm-pool-services need to migrate from existing pool schema (XXXLMP) to new schema (XXXLMX).
  • For further details, refer to Oracle Banking Liquidity Management Installation Guide

SSL Changes

  • Oracle Banking Liquidity Management application has been SSL enabled by default both at api-gateway level and for inter-service calls.
  • For further details, refer to Oracle Banking Liquidity Management Pre-Installation Guide