This guide will provide instructions on how to perform tracing for the Oracle Access Manager (OAM) environment. This is useful when trying to debug errors pertaining to OAM and/or using Single Sign-On (not to be confused with Oracle’s Single Sign-On software used before OAM) on a protected ADF, Forms, or Java/JSP application. Using this method will NOT require a shutdown of your WebLogic servers. NOTE: The screenshots were taken from a Windows environment, but this works perfectly in Unix as well.
- Open up Command Prompt as an administrator
- Navigate to the %ORACLE_HOME%\common\bin ($ORACLE_HOME/common/bin in Unix) directory using the cd command.
- Log into WLST:
- Connect to your WebLogic domain using: connect()
- Type in the following information when prompted (Press Enter after typing in the requested information):
- Setting TRACE:16 or TRACE:32 for the OAM managed server (Example: oam_server1) will set up tracing for it. To do so, run the following:
- Once you have reached this step, replicate the OAM issue you are seeing. After the issue has been replicated, review the [OAM_managed_server]-diagnostic.log (oam_server1-diagnostic.log) to review the trace information.
- To return the trace level back to the default of NOTIFICATION:1, you may either:
- Restart the OAM managed server
- Run the following WLST command: setLogLevel(logger=”oracle.oam”,level=”NOTIFICATION:1”, persist=”0”, target=”oam_server1”)
NOTE: You may view the trace level of the OAM managed server at any time in WLST by running the command: listLoggers(pattern=”oracle.oam.*”,target=”oam_server1”). The logger “oracle.oam” will be the one to check.
Source: Oracle Support note 1298296.1.