Collect Diagnostic Data

Configuration and log files help you diagnose issues relating to the Oracle Identity Cloud Service and Oracle E-Business Suite integration using the E-Business Suite Asserter.

You must collect the following files:
  • The E-Business Suite Asserter configuration file (
  • The E-Business Suite Asserter diagnostic logs.
  • The domain log file for the WebLogic domain where the E-Business Suite Asserter is deployed.
  • The HTTP header trace.

Enable the E-Business Suite Asserter Debug Log

To send logs to a file, add FileHandler to the handlers property in the file. This will enable file logging globally.

  1. Create a file with entries as follows:
    handlers = java.util.logging.FileHandler, java.util.logging.ConsoleHandler
    java.util.logging.FileHandler.pattern = %h/ebsasserter.log
    java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
    java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
  2. Add the option -Djava.util.logging.config.file=< file created above> in Oracle WebLogic Server:
    1. Using a browser, access the Oracle WebLogic Server Administration Console.
    2. In the Oracle WebLogic Server Administration Console, click servers under Environment in the Domain Structure.
    3. In the Servers table, click the name of the server instance where the E-Business Suite Asserter is deployed.
    4. From the WebLogic Server menu, select Administration, then select Server Start.
    5. From the Server Start page, you can add the option -Djava.util.logging.config.file=< file created above> in the Arguments field.
    6. Click Save.
  3. Restart the Oracle WebLogic Server where the E-Business Suite Asserter is deployed.
    The E-Business Suite Asserter debug log file is located in <HOME DIR>/ebsasserter.log.

Use Fiddler to Capture HTTP Traffic

You can use Fiddler to view and debug HTTP traffic between a client and a host computer.

  1. Download the Fiddler installer.
  2. Run the Fiddler installer and follow the wizard to install Fiddler on your client machine.
  3. Stop all other programs and services that might access the internet or use HTTP. This helps to obtain a clean and uncluttered trace.
  4. Select the Fiddler icon in the workstation’s Start menu to run Fiddler.
    Fiddler starts capturing events as soon as it launches. Fiddler logs all network requests instantly and these requests are summarized in the left hand pane of the tool.
The individual sections of the Fiddler trace are color coded. Each color is meaningful, but failures are shown in red. The result column contains the HTTP code that the section returned. For example, if a section returned an HTTP 404 or Not Found error message, the section would be red. Since we are typically looking for errors or failures, the sections we want to concentrate on are the red sections in the trace. Fiddler creates a file containing the trace with a file extension of .saz.