2019031419PM-Enable ADF Logging

Description

This page will provide guideline to turn on ADF Request Logging/ enable loggers to generate logs that can be used to diagnose and troubleshoot issues.

Find out what is the Logger Named you want to Change?

FMW is a complex stack. Ask your developer the following info

1. What is the logger name to be enabled e.g. oracle.adfdiagnostics or oracle.adf.model
2. What is the log level for that logger e.g. CONFIG or FINEST

Once you have the above info, you can use the following mechanism to apply the Logger Name to your AppServer (typically WLS) env. If you need this info for non-WLS platforms - like WAS, Glassfish or Tomcat, contact dipankar.bajpai.

Typical ADF Functional Areas and Logger Mappings

ADF	Symptom	Logger Name	Level	Owner
ADF Diagnostics		oracle.adfdiagnostics	CONFIG	Trina.Dsouza
Model		oracle.adf.model, oracle.jbo	FINEST	Sekhar.Korupolu
Jedi		oracle.adf.model.businesseditor	FINE	Juan.Oropeza
Controller		oracle.adf.controller, oracle.adfinternal.controller	FINEST	Peter.Pressley
ADF Faces		oracle.adf.view, oracle.adfinternal.view	FINE	Michael.Mcgrath
ADFShare		oracle.adf.share	FINEST	Dipankar.Bajpai
ADFShare	Default or wrong adf-config.xml - Sometimes characterized by read-only MDS	oracle.adf.share.config.ADFConfigFactory, oracle.adf.share.config.FallbackConfigImpl	FINEST	Dipankar.Bajpai
User Interface Text (aka string editor)	Searched strings aren't being found or being replaced after preview changes commit	oracle.adf.stringeditor, oracle.adf.resourcebundle.stringeditor	FINEST	Dipankar.Bajpai
ADFSecurity	ADF authorization errors	oracle.adf.share.security	FINEST	yvonne.chua
ADFDi		oracle.adf.desktopintegration		alex.davis
MDS	See Diagnostic Logging section of MDS Information for Support wiki			denny.mckinney

Configuring Settings for Log Files

• Changing Log File Locations
• Configuring Log File Rotation
• Setting the Level of Information Written to Log Files
• Specifying the Log File Format

Modifying Logging.xml

On Standalone WeblogicServer

• Stop the Server.

• Modify <DOMAIN_ROOT>/fmwconfig/config/servers//logging.xml and enable logger by setting it to appropriate level. Add the logger if logger is missing in logging.xml.

  'oracle.adfdiagnostics' level='CONFIG'/>

• Re-start the server.

On Integrated WeblogicServer (JDeveloper)

Open Logging.xml in Jdeveloper.

• View->Application Server Navigator
• Expand Application Servers
• Right Click IntegratedWeblogicServer
• Select "Configure Oracle Diagnostics Logging for "IntegratedWeblogicServer" "
• Search for the logger. Add the logger if logger is missing in logging.xml.
• Set appropriate log Level and save.

You need not re-start the server.

Using EM Console

Configure logger level

• Log into Enterprise Manager (eg: http://slc08yla.us.oracle.com:7011/em )with username/password(eg: weblogic/weblogic1) with ADMIN role privilege and navigate to the Log Configuration page for your server.
• To open the Log Configuration page, right-click the Server node in the navigation tree and select Logs > Log Configuration.

• For each logger, select the desired log level.

• Add the logger (if missing) and set the log level.

Reset logger level

• To reset logger, set log level to OFF using above steps.

Configure logger for a User

• Follow the instructions here

Verify appropriate logger name for different use-cases

Using WLST

• Use WLST commands to set the log level. Be sure to start WLST command prompt using a username/password with ADMIN role privilege:

  setLogLevel(logger="oracle.adfdiagnostics", level="CONFIG", addLogger=1)

  Note: if after setLogLevel you do getLogLevel and logger level isn't set on the target server, then use setLogLevel with option target="" as seen below.

• setLogLevel(logger="oracle.adfdiagnostics", level="CONFIG", addLogger=1,target="serverName")

Turn ON Per User ADF Request Logging 

• Be sure to start WLST command prompt using a username/password with ADMIN role privilege:

  configureTracingLoggers(action='disable') configureTracingLoggers(pattern=['oracle.adfdiagnostics'], action='enable') startTracing(user='oracle.firstname.lastname', level='CONFIG')

Turn OFF Per User ADF Request Logging 

• Be sure to start WLST command prompt using a username/password with ADMIN role privilege:

stopTracing(user='oracle.firstname.lastname')

 

How to start WLST

From middleware/oracle_common/common/bin execute following:

./setWlstEnv.sh ./wlst.sh

How to connect to Weblogic Server from WLST

1. Start WLST How to start WLST
2. Connect to the Weblogic Server

• connect(user,password,'t3://host:port')

user- User name with ADMIN role privilege
password - password of above user.
host - host where app is deployed
port - Weblogic Server port

connect('weblogic','weblogic1','t3://localhost://7001')

User, password, host and port are used as an example.

Generate Incident in an event of JBOException

Configure incident generation