7 Post Installation Steps

Credential Store Mapping

The OBAPI system utilizes external integrations to facilitate seamless communication with various services. To establish these connections, credentials are required to authenticate and authorize access. These credentials are not hardcoded but rather initialized post-installation. They are subsequently encrypted and stored within the database, ensuring confidentiality and integrity. Upon application startup, the credentials undergo decryption, enabling secure loading into the system. This subsequent section outlines the procedures and guidelines for configuring and managing these credentials within the OBAPI environment.

To configure and add credentials follow the steps mentioned in the below document

  • Oracle Banking APIs Credential Store Setup Guide

Fileupload with UBS

Refer below document for File upload configuration with UBS

  • Oracle Banking APIs File Upload Report Configuration

Origination with OBO

Refer below document (section 5 and 6) for enabling Origination with OBO

  • Oracle Banking APIs OBO Mid-Office and Third Party Setup and Configuration Guide

Trade Finance (LC and BG) with OBTFPM

Refer below document for enabling Letter Of Credit issuance and Bank Guarantee issuance with Oracle Banking Trade Finance Management.

Oracle Banking Mid-Office Product Setup and Configuration Guide

OHS

OHS server needs to be configured for all FLAVOR’s as a mandatory activity.

To configure OHS server follow steps mentioned in below document before proceeding further.

  • Oracle Banking APIs OHS User Interface Configuration user manual.

Feedback module:

In order to enable Scale (Rating) icons please refer the section Creating Procedure of Oracle Banking APIs Content Upload Guide user manual.

Table 7-1 WAR deployments

Sr No Module Mandatory (Y/N)
Domainwise deployments
2 digx-common Y
4 digx-infra Y
5 digx-coherence Y
8 digx-extxfacesimulator Y
9 digx-cms N
10 digx-corporateloan N
11 digx-creditfacility N
12 digx-edx N
14 digx-liquiditymanagement N
16 digx-payments N
17 digx-pfm N
19 digx-processmanagement N
20 digx-retail N
21 digx-scf N
22 digx-scfcm N
23 digx-tradefinance N
24 digx-virtual-account N
25 digx-genai Y
26 digx-ml-Indb Y
27 digx-sms Y
28 digx-ukob Y
29 digx-webauthn Y
30 weblogic-remote-cconsole-app Y

Enabling Kafka in OBAPI

Overview

OBAPI now supports Apache Kafka as a messaging system in addition to JMS. Kafka provides high throughput, scalability, and fault tolerance, making it an excellent choice for event-driven architectures. OBAPI will work with either JMS or Kafka but not both simultaneously. This section explains how to enable Kafka.

  1. Enable Kafka
    • JMS is the default messaging system in OBAPI.
    • Enable Kafka only if you want to switch the existing message system to Kafka by executing the following configuration queries in the database. If not enabled, the system will continue using JMS.

Configuration Queries:

UPDATE DIGX_FW_CONFIG_ALL_B SET prop_value = 'KAFKA' WHERE prop_id = 'MESSAGE_BROKER_TYPE';

UPDATE DIGX_FW_CONFIG_ALL_B SET prop_value = '{HOSTIP}:{HOSTPORT}' WHERE prop_id = 'bootstrap.servers';

Replace {HOSTIP}:{HOSTPORT} with the IP address and port of the Kafka broker running the Kafka service.

Note:

Ensure that Kafka is properly installed before making this change.

If you want to migrate the existing messaging system to Kafka, you need to implement Kafka consumer and producer equivalents for all the customized JMS queues and topics. Also, If there are any new customized Kafka topics to be created, the corresponding producer and consumer implementations must be developed. Refer to Section: Messaging System Integration for OBAPI in the document Oracle Banking APIs Extensibility Guide for the detailed steps and guidelines in implementing Kafka and JMS.

  • OBAPI Pre-defined External Kafka Topic Configurations

OBAPI listens to the following external Topics of OBVAM(Oracle Banking Virtual Account Management), OBLM(Oracle Banking Liquidity Management) and OBO(Oracle Banking Origination).

  • lm.accountnotification
  • vam.virtualaccountnotification
  • vam.accountstatusnotification
  • vac.accountfacilitynotification
  • externalSystemAlertMessage

For these Topics, the following properties need to be updated in the table DIGX_FW_CONFIG_ALL_B. Details should be obtained from the respective HOST system. If the HOST does not support the SSL property, it should be removed.

PROP_ID 
CATEGORY_ID 
PROP_VALUE  
        <topic_name>@ssl.truststore.password 
KAFKA_CONFIG 
<truststore_password>  
        <topic_name>@sasl.jaas.config 
KAFKA_CONFIG org.apache.kafka.common.security.scram.ScramLogin
Module required
        username="<jaas_username>" password="<jaas_password>";  
        <topic_name>@bootstrap.servers 
KAFKA_CONFIG 
<host_ip>:<host_port>  
        <topic_name>@ssl.truststore.location 
KAFKA_CONFIG 
<truststore_location>  
        <topic_name>@security.protocol 
KAFKA_CONFIG 
<security_protocol>  
        <topic_name>@sasl.mechanism KAFKA_CONFIG <sasl_mechanism>