My Oracle Support Banner

Configuring Application Logging For Diagnosis of Oracle Banking Digital Experience (OBDx) Technical Problems (Doc ID 2652506.1)

Last updated on JULY 10, 2020

Applies to:

Oracle Banking Digital Experience - Version and later
Information in this document applies to any platform.


OBDx default behavior logs the application logs/errors in application log files. For complex problems or due to insufficient logging in ERROR mode, available logs are not sufficient to diagnose the problem and warrant more fine grained logging. Purpose of this document is to elaborate various types of application logging available in OBDx application so that necessary logs can be captured. It will also demonstrate how those logging mechanism can be configured as per the requirement.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Troubleshooting Steps
 I. OBDx Application Logging
 A. Configuring Log Handlers and Loggers
 B. Changing Log Level at Run-Time for Specific OBDx Logger
 II. Configuring EclipseLink Logging
 III. Enabling SOAP Web Service Logging
 IV. Configure Weblogic Access Log to Determine Time Taken to Process
 V. Capturing HAR (HTTP Archive) For HTTP Network Log
     A. Firefox
     B. Chrome
 VI. Capturing Browser Console Screenshots For JavaScript Log
     A. Firefox
     B. Chrome
 Appendix - OBDx Logging Cheat Sheet

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.