Preface

Purpose

This guide provides the guidance to users for the issues within the application. It describes the various methods to figure out the error and then troubleshoot it.

Audience

This guide is intended for the software developers and software testers.

Critical Patches

Oracle advises customers to get all their security vulnerability information from the Oracle Critical Patch Update Advisory, which is available at Critical Patches, Security Alerts and Bulletins. All critical patches should be applied in a timely manner to ensure effective security, as strongly recommended by Oracle Software Security Assurance.

Related Resources

For more information, refer to the following resources:

  • Oracle® Banking Common Core User Guide
  • Oracle® Banking Getting Started User Guide
  • Oracle® Banking Security Management System User Guide
  • Supply Chain Finance User Guide
  • Receivables and Payables User Guide

Conventions

The following text conventions are used in this document:

Convention Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Screenshot Disclaimer

Personal information used in the interface or documents is dummy and does not exist in the real world. It is only for reference purposes.

Acronyms and Abbreviations

Abbreviation Description
API Application Programming Interface
UI User Interface
PO Purchase Order
EOD End of Day
OBSCF Oracle Banking Supply Chain Finance
OBCM Oracle Banking Cash Management
OBSCFCM Oracle Banking Supply Chain Finance and Cash Management
OBCL Oracle Banking Corporate Lending
OBRH Oracle Banking Routing Hub
OBCL Oracle Banking Corporate Lending
FCUBS FlexCube Universal Banking System
MOC Mid office Common Core
OBMA Oracle Banking Micro Services Architecture
SMS Security Management System
CMC Common Core
ELK Elasticsearch Logstash Kibana

List of Topics

Table -1 List of Topics

Topics Description
Troubleshooting Technical Flows This topic provides the information about the platform-wide troubleshooting of technical flows. It includes UI side checking, Service side logs, and some environmental issues of WebLogic.
Troubleshooting Kafka This topic provides the information on the troubleshooting kafka.
Health Checks This topic provides the information about the health check measures and observability required.
Troubleshooting Functional Workflows This topic provides information about the troubleshooting flows and specific data stores that can be checked for issues.
Troubleshooting Transaction Issues This topic provides the troubleshooting information for the various exceptions and transaction issues.
Troubleshooting EOD This topic provides the troubleshooting information for the possible EOD failure scenarios and the logs that needs to be reviewed.
Troubleshooting OutOfMemory issues This topic provides the information on troubleshooting OutOfMemory issues.
Troubleshooting Infra Errors This topic provides the troubleshooting information for Infra related errors.
Troubleshooting Deployment Errors/ Exceptions This topic provides the troubleshooting information for Errors/ Exceptions that can occur due to flyway while deployment.

Prerequisites for End Users

Prerequisites

The prerequisites are as follows:
  • Basic understanding of Eventing platform
  • Basic understanding application log analysis using tools
  • Basic understanding DB changes

Pre-installed Softwares

The following softwares should be pre-installed:
  • Zipkin
  • Kafka
  • ELK
  • Any SQL Database like SQLDEVELOPER
  • WinSCP

General Prevention

Do not make any changes to Flyway scripts manually.

Best Practices

The best practices are as follows:

  • It is ideal to have ELK stack installed on a separate VM outside the product VMs to ensure the flow of logs in case of an app crash.
  • Log levels can be adjusted to INFO and above to enable relevant logs to flow in.