The DIAG_MODULE.xml Resource Descriptor Configuration Managing Diagnostic System Modules

4-6 Configuring and Using the Diagnostics Framework for Oracle WebLogic Server wldf-system-resource wldf-system-resource namenewDiagnosticModname targetManagedServer1,ManagedServer2target descriptor-file-namediagnosticsnewDiagnosticMod.xml descriptor-file-name descriptionA diagnostic module for my managed serversdescription wldf-system-resource -- Other WLDF system resource configurations -- domain The relationship of the config.xml file and the MyDiagnosticModule.xml file is shown in Figure 4–1 . Figure 4–1 Relationship of config.xml to System Descriptor File

4.6.3 The DIAG_MODULE.xml Resource Descriptor Configuration

Except for the name and list of targets, which are listed in the config.xml file, as described above, all configuration for a diagnostic system module is saved in its resource descriptor file. Example 4–3 shows portions of the descriptor file for a diagnostic system module named myDiagnosticModule. Example 4–3 Sample Structure of a Diagnostic System Module Descriptor File, MyDiagnosticModule.xml wldf-resource xmlns=http:xmlns.oracle.comweblogicweblogic-diagnostics xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation=http:xmlns.oracle.comweblogicweblogic-diagnostics1.0webl ogic-diagnostics.xsd nameMyDiagnosticModulename instrumentation -- Configuration elements for zero or more diagnostic monitors -- instrumentation harvester -- Configuration elements for harvesting metrics from zero or more MBean types, instances, and attributes -- harvester watch-notification -- Configuration elements for one or more watches and one or more notifications-- Understanding WLDF Configuration 4-7 watch-notification wldf-resource

4.6.4 Managing Diagnostic System Modules

A diagnostic system module can be targeted to zero, one, or more servers or clusters, although a given server can have only one module targeted to it at a time. You can create multiple modules that monitor different aspects of your system. You can then choose which module to target to a server or cluster, based on what you want to monitor at that time. Because you can target the same module to multiple servers or clusters, you can write general purpose modules that you want to use across a domain. You can change the target of a diagnostic module without restarting the server instances to which it is targeted or untargeted. This gives you considerable flexibility in writing and using diagnostic monitors that address a specific diagnostic goal, without interfering with the operation of the server instances themselves.

4.6.5 More Information About Configuring Diagnostic System Resources