3-12 Configuring and Using the Diagnostics Framework for Oracle WebLogic Server
The time interval can be constrained by using the range selection bars in the range navigator. You can grab these bars with your pointer and drag them inward or
outward to change the range of events displayed in the Event Log. The range selection bars are activated when you hover your pointer over either end of the navigator, as
shown in
Figure 3–9 .
Figure 3–9 Range Navigator Selection Bars
Events from additional producers, such as the JRockit JVM, can be selected in the Event Types Browser. Note that JVM events do not have ECID attributes, so they
cannot be included among the WLDF events in the operative set. So to view the JVM events, you need to de-select Show Only Operative Set.
At this point the events that are displayed in the Event Log are those that occurred during the selected time interval but not correlated otherwise.
Figure 3–10 shows
drilling down into JDBC activity by selecting only JDBC events and JVM socket events. The Event Log is updated and listed in chronological order to show the socket activity
that occurred simultaneously to the flow of the JDBC events in the selected time interval.
Figure 3–10 Adding JVM Events to JDBC Event Log
3.5.3 Changing the Location of Temporary JFR Files
The temporary JFR files created in the operating system’s temp directory are managed directly by JRockit. WLDF does not control these files. By default, WLDF temporary
files related to JFR recordings are placed in the DOMAIN_NAME\servers\SERVER_ NAME
serverlogsdiagnostic_images directory. However, you can change the location in which JRockit places its temporary files by
using the following command-line option when starting JFR, where path represents the preferred location:
Using WLDF with Oracle JRockit Flight Recorder 3-13
-XX:FlightRecorderOptions=repository=path For more information about JFR configuration settings, see Starting the Flight
Recorder in Oracle JRockit Flight Recorder Run Time Guide.
3-14 Configuring and Using the Diagnostics Framework for Oracle WebLogic Server
4
Understanding WLDF Configuration 4-1
4
Understanding WLDF Configuration
The WebLogic Diagnostics Framework WLDF provides features for generating, gathering, analyzing, and persisting diagnostic data from WebLogic Server instances
and from applications deployed to them. For server-scoped diagnostics, some WLDF features are configured as part of the configuration for a server in a domain. Other
features are configured as system resource descriptors that can be targeted to servers or clusters. For application-scoped diagnostics, diagnostic features are configured as
resource descriptors for the application.
The following sections provide an overview of WLDF configuration:
■
Section 4.1, Configuration MBeans and XML
■
Section 4.2, Tools for Configuring WLDF
■
Section 4.3, How WLDF Configuration Is Partitioned
■
Section 4.4, Configuring Diagnostic Image Capture and Diagnostic Archives
■
Section 4.5, Configuring Diagnostic Image Capture for JRockit Flight Recorder
■
Section 4.6, Configuring Diagnostic System Modules
■
Section 4.7, Configuring Diagnostic Modules for Applications
■
Section 4.8, WLDF Configuration MBeans and Their Mappings to XML Elements For general information about WebLogic Server domain configuration, see
Understanding Domain Configuration for Oracle WebLogic Server.
4.1 Configuration MBeans and XML
As in other WebLogic Server subsystems, WLDF is configured using configuration MBeans Managed Beans, and the configuration is persisted in XML configuration
files. The configuration MBeans are instantiated at startup, based on the configuration settings in config.xml. When you modify a configuration by changing the values of
MBean attributes, those changes are saved persisted in the XML files.
Configuration MBean attributes map directly to configuration XML elements. For example, the Enable attribute of the WLDFInstrumentationBean maps directly to the
enabled sub-element of the instrumentation element in the resource descriptor file configuration file for a diagnostic module. If you change the value of the MBean
attribute, the content of the XML element is changed when the configuration is saved. Conversely, if you were to edit an XML element in the configuration file directly
which is not recommended, the change to an MBean value would take effect after the next session is started.
