UserActivityInfo.getParentResponseReceivedTime() UserActivityInfo.getResponseReceivedTime() Table 5-1 Click History Attribute Mapping Click History Attributes Odl_quicktrace502_Ī sample dump file output is shown in the following example. The suffix is the QuickTrace handler name defined in the server's logging.xml. Odl_quicktrace_i.app-clickhistory-handler.dmp The Click History dump file format convention is: This format can be parsed using the ODL LogQuery API as well as using the Enterprise Manager Cloud Control Support Workbench log query feature. It has the same format as the ODL log file. The Click History output file is a QuickTrace dump file. However, you can also access Click History data at any time using the WLST executeDump command.ĮxecuteDump(name="odl.quicktrace", args=, server="CRMCommonServer_1") When an incident occurs, Click History automatically dumps its data into a file. The default buffer size of 860 KB can hold approximately1,500 "click" events, which should be sufficient for incident analysis. It has minimal impact to Java Garbage Collection and its memory usage is strictly controlled. The data is packed in a single contiguous memory segment in the Java heap. Click History captures its data using ADF EUM (End User Monitoring) services It has a circular buffer that is optimized specifically for EUM data. The Click History record provides information about the UI component, the view, the region, the user, the Diagnostic Session Id (DSID), and other key application data. It is particular useful to help determine the last user action that had caused the failure or problem. You can use Click History data to help diagnose problems. For more information about diagnostic incidents, see the "Diagnosing Problems" chapter of Administering Oracle Fusion Middleware.You do not need to configure Click History to capture the "click" events, it is automatically enabled by default. When a diagnostic incident occurs, the data in the buffer is automatically written to disk as part of the diagnostic data. The data is continuously captured and stored in a circular buffer in memory. Click History is a Fusion Middleware diagnostics feature that captures ADF Faces events generated by user activities on ADF Faces components (for instance, clicking an ADF command button from a web browser).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |