Compound Operations Configuring the DMS Event System

6-18 Oracle Fusion Middleware Performance and Tuning Guide Use in the default configuration: An instance of the HTTP request tracker destination is enable by default. In the case of a DFW incident being generated the active HTTP request list will be dumped automatically, allowing an administrator to correlate the failure with a specific request. For each HTTP request the following information will be dumped: ■ URI such as webcenterhome ■ Start time of the request ■ ECID ■ Query string ■ HTTP Headers When the HTTP request tracker is not enabled the HTTP Request Dump will output the following: HTTP Requests are not being tracked. To enable HTTP request tracking enable the DMS oracle.dms.event.HTTPRequestTrackerDestination in dms_config.xml

6.7.2.3.1 Executing the HTTP Request Tracker Dump The information being maintained by

the HTTP request tracker can be accessed manually. In order to execute the dump that reports the HTTP request information the WLST executeDump command can be used, when connected to a server, as follows: executeDumpname=http.requests Active Requests: StartTime: 2009-12-14 02:24:41.870 ECID: 0000IMChyqEC8xT6uBf9EH1B9X9000009,0 URI: myAppWelcome.jsp QueryString: Headers: Host: myHost.myDomain.com:7001 Connection: keep-alive User-Agent: Mozilla5.0 Windows; U; Windows NT 5.1; en-US AppleWebKit532.5 KHTML, like Gecko Chrome4.0.249.30 Safari532.5 Accept: applicationxml,applicationxhtml+xml,texthtml;q=0.9,textplain;q=0.8,imagepng, ;q=0.5 Accept-Encoding: gzip,deflate Cookie: ORA_MOS_LOCALE=en7CGB; s_nr... Accept-Language: en-GB,en-US;q=0.8,en;q=0.6 Accept-Charset: ISO-8859-1,utf-8;q=0.7,;q=0.3

6.7.2.4 JRockit Flight Recorder Destination

The JRockit Flight Recorder JFR records information regarding the runtime status and behavior of the JRockit JVM. JFR also exposes an API through which third party events can be reported. JFR is available in JRockit R28 and beyond. By themselves DMS traces and JFR traces only show part of the picture of the actions being performed in the server. DMS integration with JFR enhances the diagnostic information available to administrators and developers as follows: 1. Application level events and JVM level events can be reported as a single sequence therefore avoiding the need to combine such events from separate log files based Oracle Dynamic Monitoring Service 6-19 only on timestamp which may not tick over fast enough to accurately order events created at or around the same time. 2. Recent DMS activity can be dumped, retroactively, from the JVM at will. 3. Recent DMS and JVM events can be dumped to disk in the event of a fatal error that causes the JVM to exit gracefully. 4. The DMS ECID can be used to correlate activity relating to the same request, or unit of work, across the span of a JFR recording. 5. The DMS ECID can be used to collect diagnostic information from all systems involved with an event, or series of events, recorded by JFR.

6.7.2.4.1 Dynamically Derived JFR Event Types – Names, Values and Descriptions A DMS

noun type will be associated with a JFR InstantEvent event type: ■ The name of the JFR event type for a noun type will be the noun type’s name with the suffix “ state”. ■ The path of the JFR event type for a noun type will be “dms” followed by the producer-name, followed by the event type name. ■ Event sensors will not contribute any values to the noun type’s JFR event type. ■ The values of the JFR event for a noun type are described in Table 6–6 : A DMS phase sensor will be associated with a JFR DurationEvent event type: Table 6–6 Values of the JFR Event for a Noun Type Value Name Description Relational Notes ECID The Execution Context ID ECID associated with the action. Yes RID The RID associated with the action. Yes noun type name The full path of the noun. This field will be populated with the full path of the noun. The field’s name assumes that the noun_type meaningfully categorizes all objects being measured by the nouns of that type. state-sensor-name The value of the state sensor. No Each state sensor belonging to the noun will contribute one of these values to the instant event. There may be more that one value in each noun. event name The name of the event sensor that was updated, left null otherwise. No The event name field is required for being able to count the number of times a DMS event sensor has been updated in a recording event sensors do not contribute values to an event type.