Preface

• Purpose
  
• Audience
  
• Documentation Accessibility
  
• Diversity and Inclusion
  
• Related Resources
  
• Conventions
  
• Screenshot Disclaimer
  
• Acronyms and Abbreviations
  
• Prerequisites
  
• General Prevention
  
• Best Practices
  

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.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Diversity and Inclusion

Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.

Related Resources

The related documents are as follows:

• Oracle Banking Common Core User Guide
• Getting Started User Guide
• Oracle Banking Security Management System User Guide
• Cashflow Forecasting User Guide
• Collections User Guide
• Netting 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

Information used in the interface or documents are dummy, it does not exist in real world, and its only for reference purpose.

Acronyms and Abbreviations

The list of the acronyms and abbreviations used in this guide are as follows:

Table -1 Acronyms and Abbreviations

Abbreviation	Description
SMS	Security Management System
CMC	Common Core
MOC	Mid office Common Core
ELK	Elasticsearch Logstash Kibana

Prerequisites

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.