Beruflich Dokumente
Kultur Dokumente
Objectives
After completing this lesson you will e a le to! " #nderstand the $%&' architecture " (ave a asic understanding of the diagnostics system modules " Configure a diagnostics system module
2-2
Road Map
" Overview o WebLogic Diagnostics Framework
* +he ,urpose of &iagnostics * $%- ,re-9.0 &iagnostics * $%&'! A Coordinated Collection of &iagnostic +ools
" "
2-)
Diagnostics
" $hat can you do when your $e %ogic -erver instance, or an application running on it, is either not wor0ing properly or not wor0ing efficiently1 2ou generate, gather, and analy3e diagnostics on the system to find out information and fi4 the pro lem.
"
2-/
2-5
WLDF Data
" #sing $%&', you can do the following to diagnostic data generated y a running server and the applications deployed within its containers!
* * * * * Create Collect Analy3e Archive Access
"
+his data provides insight into the run-time performance of servers and applications that ena les you to isolate and diagnose faults when they occur.
2-6
!ection !ummar"
8n this section, you learned a out! " +he purpose of diagnostics " A framewor0 of diagnostic tools
2-7
#ui$
$hich of the following activities can you perform on diagnostic data generated y a running server and the applications deployed within its containers1 :. Create 2. Collect ). Analy3e /. Archive 5. Access
2-9
Road Map
" " Overview of $e %ogic &iagnostics 'ramewor0 $%&' Architecture
* * * * Architectural &iagram $%&' -ervices $%&' -cope ,utting 8t All +ogether
"
2-9
Manager
Instrumentation !ervice Watch Watch !ervice )arvest !ervice *oti ication Watch Ru(e
Instrumentation
Instrumentation
Data %ub(ishers Data %roviders
Watcher
'o((ector
Logger )arvester
&ccessor
'urrent )istorica(
Image 'apture
Image !ource Image Manager Image &rti act
2 - :0
&rchive
Log &ppenders Data &rchiver
WLDF !ervices
" " Data creators generate diagnostic data that is consumed y the Collector. The Collector coordinates with the Archive to persist this data and with the $atch and ;otification system to provide automated monitoring. The Accessor interacts oth with the Collector to e4pose current diagnostic data and with the Archive to present historic data. The Manager provides a configuration and control interface for managing the framewor0. The Image Capture provides a model for capturing a diagnostic snapshot of the 0ey server state.
"
" "
2 - ::
'ategories o 'omponents
'or this course, we have grouped these components into the following functional categories!
,enerating Data
Data 'reator
,athering Data
Data 'o((ector
2 - :2
Instrumentation
%ub(isher Monitors %rovider Monitors
Debugging
Logger
M-ean !erver
WL! Runtime M-eans 'ustomer M-eans
)arvester
2 - :)
&rchives
&ccessor
)istorica(
Logger
Fi(ters
&rchive
Log &ppenders +vent &rchiver Data &rchiver Log !torage
Log !torage
)arvester
)arvest .ab(e
Log !torage
2 - :/
2 - :5
Data &ccessors
&ccessor
'urrent )istorica(
)arvester
Data 'ache
&rchive
Log &ppenders +vent &rchiver Data &rchiver
2 - :6
Logger
Fi(ters Watch
Watcher
*oti ication
)arvester
)arvest .ab(e Watch Ru(e
2 - :7
Managers
Manager
Diagnostic !ervice Debug !ervice Logging !ervice Instrumentation !ervice )arvester !ervice &rchive !ervice Watch !ervice Diag/ Image !ervice &ccessor !ervice M-eans
Debug Config Debug Runtime Instrumentation Config Instrumentation Runtime Instrumentation Config Instrumentation Runtime Harvester Config Harvester Runtime Archive Config Archive Runtime Watch Config Watch Runtime Diag. Image Config Diag. Image Runtime Accessor Runtime
2 - :9
Image 'apture
First Fai(ure
Image !ource
Image Manager
2 - :9
Manager
Instrumentation !ervice Watch Watch !ervice )arvest !ervice *oti ication Watch Ru(e
Instrumentation
Instrumentation
Data %ub(ishers Data %roviders
Watcher
'o((ector
Logger )arvester
&ccessor
'urrent )istorica(
Image 'apture
Image !ource Image Manager Image &rti act
2 - 20
&rchive
Log &ppenders Data &rchiver
!ection !ummar"
8n this section, you learned a out! " +he $%&' architecture " +he $%&' components " $%&' scope " +he way all the pieces fit together
2 - 2:
#ui$
$hich of the following most accurately descri es the Accessor1 :. <enerates diagnostic data that is consumed y the Collector 2. Coordinates with the Archive to persist this data and with the $atch and ;otification system to provide automated monitoring ). 8nteracts oth with the Collector to e4pose current diagnostic data and with the Archive to present historic data /. ,rovides a configuration and control interface for managing the framewor0 5. ,rovides a model for capturing a diagnostic snapshot of 0ey server state
2 - 22
Road Map
" " " Overview of $e %ogic &iagnostics 'ramewor0 $%&' Architecture $%&' Configuration .asics
* =.eans and >=% * $ays to Configure $%&' Components * &iagnostics -ystems =odules
2 - 2)
<?xml version='1.0' encoding='UTF-8'?> <wldf-resource ...> <name> erver101-!iag"odule<#name> <ins$rumen$a$ion> <ena%led>$rue<#ena%led> <#ins$rumen$a$ion> <#wldf-resource>
2 - 2/ Copyright 2009, Oracle. All rights reserved.
2 - 25
2 - 26
2 - 27
2 - 29
"
2 - 29
2 - )0
2 - ):
2 - )2
2 - ))
2 - )/
2 - )5
!ection !ummar"
8n this section, you learned a out! " +he relationship etween $%&' configuration =.eans and >=% " +he various ways to configure $%&' components " +he diagnostics system modules " +he way to configure diagnostics system modules for systems
2 - )6
#ui$
$hich of the following is false1 :. A diagnostic system module can e targeted to any num er of servers. 2. +his allows for the creation of general purpose modules. ). A server can have multiple modules targeted to it at a time. /. &iagnostic modules can e retargeted without server restart.
2 - )7
!ummar"
8n this lesson, you learned how to! " &escri e the $%&' architecture from oth a high and low level " #nderstand how $%&' is partitioned " #nderstand the purpose of diagnostics system modules " Configure a diagnostics system module via the admin console " Configure a diagnostics system module via >=%
2 - )9