1. Administering Oracle Integration Classic
  2. Manage Oracle Integration Classic (User-Managed)
  3. Diagnose Oracle Integration Classic (User-Managed) Problems

Diagnose Oracle Integration Classic (User-Managed) Problems

Oracle Integration Classic (user-managed) provides log files containing reports of an event, errors, warning messages. You can diagnose problems using these log files.

Topics:

Access and View Diagnostic Logs

Use log files such as WebLogic Server log files or Java Flight Recorder to diagnose problems, and report incidents in Oracle Integration Classic (user-managed).

Topics:

Use WebLogic Server Logs

Use WebLogic Server Administration Console logs to diagnose errors.

To find the log files in WebLogic Server Administration Console:
  1. Sign in to the Oracle Cloud Infrastructure Console.
  2. Click Manage this service Manage this service icon and select Open WebLogic Server Console.
    A new browser opens and you are redirected to the login page.
  3. Enter the user name and password you provided when you created the service instance.
  4. In the Domain Structure area, expand Diagnostics.
  5. Click Log Files.

    The Log Files table appears.

  6. Select the option to the left of the log file you want to view.
  7. Click View.

    The log file you selected appears in the table.

    Note:

    If you do not find the information you are looking for, click the Customize this table link above the log file and select the Time Interval or use the other filter options available.

Use Java Flight Recorder Performance Profiles

You can use Oracle’s commercial profiling tools, Java Flight Recorder and Java Mission Control, to analyze the performance of applications deployed on Oracle Java Cloud Service.

Java Flight Recorder (JFR) and Java Mission Control (JMC) collect detailed runtime information so that you can analyze incidents after they occur. JFR, available in Oracle HotSpot JVM, is a performance monitoring and profiling tool that records diagnostic information on a continuous basis, making it always available, even in the wake of catastrophic failure such as a system crash. JMC enables you to monitor and manage Java applications without introducing the performance overhead normally associated with these types of tools. It includes the JFR user interface, which allows users who are running a Java Flight Recorder-compliant version of Oracle HotSpot to view JVM recordings, current recording settings, and runtime parameters. The JFR interface includes the Events Type View, which gives you direct access to event information that has been recorded in the .jfr file, such as event producers and types, event logging and graphing, event by thread, event stack traces, and event histograms.

Basic Workflow for Profiling Applications with JFR

Monitoring applications with JFR comprises these steps:

  1. Enable JFR in your WebLogic Server instance.

  2. Obtain the flight recording by generating a diagnostic image capture.

  3. Analyze the recording with the Flight Recorder UI.

Enable JFR in Your WebLogic Server Instance

Because it is a commercial feature, if WebLogic Server is configured with Oracle HotSpot, Java Flight Recorder is, by default, disabled. To enable it, use the following JVM commands in the startup script for the WebLogic Server instance in which the JVM runs:

-XX:+UnlockCommercialFeatures -XX:+FlightRecorder

Note:

The sequence of these commands is critical: +UnlockCommercialFeatures command advises the JVM to recognize the command +FlightRecorder. The commands must be entered in that order or the JVM will not start.

For example:

java -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:FlightRecorderOptions=defaultrecording=true,maxage=20m MyApp

You can also enter the +UnlockCommercialFeatures and +FlightRecorder commands in the WebLogic Server configuration file’s JAVA_OPTIONS (or equivalent) variable.

For more detailed information on enabling JFR, see Running Java Flight Recorder in the Java Platform, Standard Edition Java Flight Recorder Runtime Guide.

Obtain the Flight Recording by Generating a Diagnostic Image Capture

The diagnostic image capture itself is a single JFR file that contains individual images produced by the different server subsystems. If the JFR file is available, it is included in the diagnostic image as the file FlightRecording.jfr.

You can generate a diagnostic image capture on-demand — for example, from the WebLogic Server Administration Console, Fusion Middleware Control, WLST, or a JMX application — or as the result of an image action. To generate a diagnostic image captures and configure the location in which they are created, see Configuring and Capturing Diagnostic Images in Oracle® Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.

Analyze the Recording with the Flight Recorder UI

Once you’ve obtained the recording, you can then view and analyze it by using the Flight Recorder user interface, a JMC component. Assuming you are running a Java Flight Recorder-compliant version of Oracle HotSpot, the JFRUI allows you to view JVM recordings, current recording settings, and runtime parameters. The JFR interface includes the Events Type View, which gives you direct access to event information that has been recorded in the JFR file, such as event producers and types, event logging and graphing, event by thread, event stack traces, and event histograms. Some of the activity you can monitor on the JFR UI includes:

  • Display Event Data for a Product Subcomponent

  • View the Event Log to Display Details

  • Track Execution Flow by Analyzing an Operative Set

  • Expand the Operative Set and View Correlated Diagnostic Data

Use of the JFR UI for these tasks and more is described in greater detail in Analyzing Java Flight Recorder Data in Oracle® Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.

Use Oracle Integration Report Incidents

You can report incidents for problematic issues that occur during design time in Oracle Integration (for example, being unable to open an integration, the failure of connection testing, or the failure of artifact regeneration).

To report incidents in Oracle Integration, see Report Incidents in Using Integrations in Oracle Integration Generation 2.

Export Suite-Generated Artifacts

Download artifacts of an integration to view and diagnose problems.

You can download artifacts as a zip file using the Download Artifacts option in Oracle Integration, see Downloading Generated Artifacts for an Integration in Using Integrations in Oracle Integration Generation 2.

Collect Database Statistics

Collect database statistics to diagnose performance problems by comparing statistics captured in a baseline to those captured during a period of poor performance.

See Gathering Database Statistics in the Oracle Database Performance Tuning Guide.

View System Health

You can view information about the system health of Oracle Integration components. As you navigate around Oracle Integration, you receive a system health state that is not older then five minutes. The only exception is the Messaging Service state, which may take longer than five minutes to update.

The state of system health is viewable from multiple locations in Oracle Integration instance:

  • From the main banner of pages

  • From the Integrations, Connections, and Lookups pages

  • From the mapper or expression builder

  • From the System Health section on the Dashboard page

See View the Dashboard in Using Integrations in Oracle Integration Generation 2.