2. Oracle Common Core - OBMA Core Integration
Common Core caters to the basic maintenances such as bank and branch parameters, currency, Currency Pair, Rate Type, Currency Holiday, Exchange rate, Local Holiday and Core Branch Maintenance.
Core entities will be maintained in the common core and it has to be replicated to OBMA Core, so OBMA Products can access these OBMA Core entities. The list of Core entities are:
l Currency
l Currency Pair
l Rate Type
l Currency Holiday
l Exchange rate
l Local Holiday
l Core Branch Maintenance
This section contains the following sections:
l Section 2.2, "Prerequisites"
l Section 2.3, "Integration Process"
This section describes the scope of the integration with respect to Common Core and OBMA Core.
With the integration Common Core entities can populate OBMA Core entities like:
l Currency
l Currency Pair
l Rate Type
l Currency Holiday
l Exchange rate
l Local Holiday
l Core Branch Maintenance
Set up Oracle FLEXCUBE Universal Banking Application and Oracle Banking Microservices Architecture Applications.
This section contains the following topics:
l Section 2.3.1, "Technical Flow"
l Section 2.3.2, "Core External system maintenance screen"
l Section 2.3.3, "Scheduler JOB for Replication"
l Section 2.3.4, "Error Queue Screen"
The system populates core entities through an ASYNC process. The below steps describes the integration flow in detail:
l Whenever the entities are saved the replication request will be stored with status as X, The status X indicates that it is not yet ready for replication. Whenever the entities are authorized the replication request will be updated with status as U, The status U indicates that it is ready for replication.
l A Job will pick these Core entity requests which are in pending status and form the web service XML requests.
l System creates a consolidated XML request for each transaction reference.
l Based on the OBMA Core System response, the status of the request will be updated in FCUBS. Status can be Work in Progress (W) Processed (P) and Error.
2.3.2 Core External system maintenance screen
Users can maintain external services using 'Core External Service Maintenance' screen. You can invoke this screen by typing 'IFDCREXS' in the top right corner of the Application toolbar and clicking the adjoining arrow button.
You can specify the following details:
External System
Specify the external system. Alternatively, users can select the external system from
the option list. The list displays all valid values maintained in the system to capture the External System code.
Description
The system displays the description based on the external system selected.
External User
Specify the external user. This will be used to send in replication request.
Retry Count
To capture the maximum retry count if replication request failed due to technical failure.
Read Time Out (In Seconds)
To capture the read time out in seconds.
Connection Time Out (In Seconds)
To capture the connection time out for connecting to external system.
External System AppID
To capture the external system Application id.
External System Type
This is to decide what type of system to communicate. The dropdown lists the below values,
l Default
l OBMA
l OBRH
l Pricing
Type
Select the type from the drop-down list i.e. SOAP request/REST request.
Service Name
The system captures the Service name used in replication request.
WS Endpoint URL
WS Endpoint URL is used for sending replication request to destination system.
Rest Service Context
The system captures the Rest-Service link used for sending replication request to destination system.
Rest Service IP
The system displays the rest service IP.
Rest Service Pattern
The system displays the rest service pattern.
Rest Service Port
This field is used to capture the rest service port.
2.3.3 Scheduler JOB for Replication
Users can perform the Pause or Resume operation using the Job Details screen. Users can invoke this screen by typing 'SMSJOBBR' in the top right corner of the Application toolbar and clicking the adjoining arrow button.
On Job Name, users can click the search icon and select CORE_EXTASYNC_CALL to replicate ODT core entities to OBMA Core entities. Users need to click on the Search button to view the job record. The job is scheduled to run every 5 minutes.
The parameter name for replication is OBMA_CORE_REP_REQ. This parameter has two options,
l Y- Replication required
l N- Replication not required
The defaulted option for the parameter is N. Users can modify the choice to Y if replication is required.
Users can re-submit or reject the Failure replication request using the Error Queue screen. Users can invoke this screen by typing ‘IFSOBERQ’ in the top right corner of the Application toolbar and clicking the adjoining arrow button.
The Failure replication request categories are:
l Functional Failure - Any function failure from an external system. For e.g any data validations. The Process status is P, and the External status is E.
l Technical Failure - Time out error from an external system. The Process status is P, and the External status is T.
l Technical Failure at Source - Interface data maintenance is wrong( Restservice URL etc.,). The Process status is P, and the External status is U.
Users need to select the records to perform the following operations.
l Re-Submit
l Reject
l Error Message
Re-Submit
The request status will be updated as U. The scheduler will pick up the request and re-send for replication.
Reject
The request status will be updated as R, No further action on the request.
Error Message
Users can view the Core External Error Description with Error details received from the OBMA system.
