Previous Next JavaScript must be enabled to correctly display this content

## Preface

- Purpose
- Audience
- Documentation Accessibility
- Critical Patches
- Diversity and Inclusion
- Related Documents
- Conventions
- Acronyms and Abbreviations
- Prerequisites
- General Prevention
- Best Practices

### Purpose

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

Parent topic: Preface

### Audience

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

Parent topic: Preface

### 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.

Parent topic: Preface

### 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.

Parent topic: Preface

### 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.

Parent topic: Preface

### Related Documents

The related documents are as follows:

- Oracle Banking Common Core User Guide
- Oracle Banking Security Management System User Guide
- Oracle Banking Getting Started User Guide
- Oracle Banking Liquidity Management User Guide
- Oracle Banking Liquidity Management Configuration Guide
- Oracle Banking Liquidity Management File Upload User Guide

Parent topic: Preface

### 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 user supply particular values.
`monospace` | Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that user enter.

Parent topic: Preface

### 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 Service
MOC | Mid office Common Core
ELK | Elasticsearch Logstash Kibana

Parent topic: Preface

### Prerequisites

Prerequisites for End Users

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

Parent topic: Preface

### General Prevention

Do not make any changes to Flyway scripts manually.

Parent topic: Preface

### 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.

Parent topic: Preface