3.2 Technical Enhancements

This topic explains the technical enhancements of this release.

  1. OBELCM migration to OBMA architecture: Oracle Banking Microservices Architecture is a cloud-native, microservices-based architecture that enables banks and financial institutions to build scalable, flexible, and secure banking platforms. The architecture is designed to support the evolving needs of the banking industry, including digital transformation, innovation, and regulatory compliance.

    Oracle Banking Enterprise Limits and Collateral Management (OBELCM) is delivered as a set of microservices within the Oracle Banking ecosystem, enabling modern, modular integration with the bank’s broader digital landscape. The migration of OBELCM to the OBMA architecture enhances agility, scalability, and resilience in delivering core credit management functionalities.

OBMA Foundation Components:
  • API Gateway: Acts as an entry point for external requests, providing a unified interface for accessing Oracle Banking microservices.
  • Service Registry: Maintains a registry of available microservices, enabling discovery and communication between services.
  • Config Server: Centralized configuration management for microservices, allowing for easy management of configuration data.
  • Routing hub: Routing Hub enables seamless integration between different systems, services, and channels, reducing integration costs and complexity.
OBELCM Components:
    1. User Interface (UI): The OBELCM User Interface has been migrated using the OBMA Toolkit. The UI is designed to provide an intuitive, responsive, and role-based experience for users across business functions. It enables seamless navigation across modules and ensures efficient execution of day-to-day credit operations.
    2. Maintenance Services: Maintenance Services have been migrated using the OBMA RSO Framework. These services provide the foundational capabilities for setting up, managing, and maintaining all master data, reference data, and configuration parameters essential for system operations. Key entities such as liabilities, customers, limits, collaterals, covenants, and conditions are accurately defined and consistently maintained across the system.
    3. Transaction Services: OBELCM Transaction Services are supported on both the Spring and Helidon frameworks. Both frameworks share common business logic to avoid duplication. These services provide core capabilities to process and manage all transactional activities related to credit facilities and collaterals, ensuring that all financial movements and credit operations are captured, validated, and tracked in real time.
    4. Batch Services: Batch Services have been migrated using the OBMA Scalable Batch Framework. These services handle large-scale, automated processing of limits and collateral data that cannot be efficiently managed in real time, supporting periodic calculations, reconciliations, and bulk operations.
    5. Notifications: Notifications have been migrated using Kafka topics. They provide real-time alerts and updates to users and administrators regarding critical events, actions, or exceptions within the limits and collateral management lifecycle, enabling timely decision-making and operational efficiency.

Parent topic: Release Enhancements