DMS Nouns Common DMS Terms and Concepts

6-6 Oracle Fusion Middleware Performance and Tuning Guide and you can look this up using the string: ,default,WEBs,defaultWebApp,JSPs,examplejspnumnumguess.jsp,service where the delimiter is the , character. ■ Event sensor and PhaseEvent sensor names should have the form verbnoun. Examples: activateInstance and runMethod. When a PhaseEvent monitors a function, method, or code block, it should be named to reflect the task performed as clearly as possible. ■ The name of a state sensor should be a noun, possibly preceded by an adjective, which describes the semantics of the value which is tracked with this state sensor. Examples: lastComputed, totalMemory, port, availableThreads, activeInstances ■ To avoid confusion, do not name sensors with strings such as .time, .value, or .avg, which are names of sensor metrics, as shown in Table 6–3 , Table 6–4 , and Table 6–5 .

6.2 DMS Availability

DMS functionality is available on all certified Java EE servers. This includes both the runtime features and supporting commands. Also, several features of DMS will operate in JSE applications and standalone C applications. For more information, see the Oracle Fusion Middleware Certification Matrix at http:www.oracle.comtechnologysoftwareproductsiasfilesfus ion_certification.html .

6.3 DMS Architecture Overview

DMS consists of the following features: ■ DMS Metrics - The DMS metrics feature provides Java and C APIs that are also used by other Oracle Fusion Middleware components for instrumenting code with performance measurements and other useful state metrics. In addition, the metrics feature provides an aggregation language for computing derived metrics and tools for accessing the metrics. ■ Execution Context - Execution Context supports the maintenance and propagation of a specific context structure throughout the Oracle stack. By making the context structure available consistently across all Oracle code, the potential for cross component and cross product correlation of diagnostic data increases. For more information see Section 6.6, DMS Execution Context . ■ Events and Tracing - Event Tracing enables you to configure live tracing with no restarts. DMS metrics updated during the course of using Oracle Fusion Middleware products may be traced using the DMS Event Tracing feature. The system has been designed to facilitate not only tracing, but also to support other functionality that may be driven from DMS activity. Figure 6–1 shows the components of DMS and how they interact with other Oracle Fusion Middleware components. Arrows show the direction in which information flows from one component to the next. Oracle Dynamic Monitoring Service 6-7 Figure 6–1 DMS Interactions with Oracle Fusion Middleware Components

6.4 Viewing DMS Metrics

Oracle Fusion Middleware components are instrumented with DMS metrics in order to collect information that developers, system administrators, and support analysts can use to analyze system performance or monitor system status. The Fusion Middleware Control online help provides information on each of the specific metrics. See Section 4.2.1, Viewing Performance Metrics Using Fusion Middleware Control for information on accessing metric information. The Oracle Fusion Middleware metrics come from various sources and locations. They include MBean attributes and DMS metrics. They also come from non-Java EE servers, such as Oracle HTTP servers and Oracle WebCache. The following sections describe how to use various tools to view the DMS metrics: ■ Viewing Metrics Using the Spy Servlet ■ Viewing Metrics with WLDF WebLogic Diagnostic Framework ■ Viewing metrics with WLST Oracle WebLogic Server ■ Viewing metrics with JConsole ■ Viewing metrics with Oracle Enterprise Manager ■ Viewing metrics using WSADMIN IBM WebSphere

6.4.1 Viewing Metrics Using the Spy Servlet

The Spy Servlet is part of the DMS Application that is deployed by default on JRF-extended installations. The Spy Servlet is launched from http:host:portdmsSpy . The default port for WebLogic is 7001. The DMS Applications web archive file is dms.war, and can be found in the same directory as dms.jar: oracle_commonmodulesoracle.dms_ 11.1.1dms.war. For more information see Section 4.6, DMS Spy Servlet . Note: The Spy Servlet is secured using standard Java EE declarative security in the web-applications web.xml file, and will only grant access to the Spy Servlet to members of the Administrator’s group. 6-8 Oracle Fusion Middleware Performance and Tuning Guide

6.4.2 Viewing Metrics with WLDF WebLogic Diagnostic Framework

You can use WebLogic Diagnostic Framework WLDF to harvest DMS metrics from DMS metric MBeans. You can also use WLDF to monitor changes to the attribute value of an MBean. For more information see Configuring the Harvester for Metric Collection in Oracle Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.

6.4.3 Viewing metrics with WLST Oracle WebLogic Server

DMS provides three commands to view metrics in WLST: As well as displaying textual output, theses commands also return a structured object or single value that you can use in a script to process. For more information on using these commands, see the following: ■ Section 4.5.1.1, Using WLST Commands for System Components ■ DMS Custom WLST Commands in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference

6.4.4 Viewing metrics with JConsole

To provide a standards-based way to access metrics, DMS exposes them through MBeans. An MBean will be created and registered for each typed noun with the runtime MBean Server. The DMS sensors contained by the noun are exposed as the attributes of the MBean. Exposing the DMS metrics as MBeans allows administrators to use tools such as JConsole the Java monitoring and management console, and other Java Management Extension JMX clients, to access the DMS metrics. MBeans also allow for integration with other Oracle diagnostics software such as WLDF WebLogic Diagnostics Framework, which is described in Section 6.5 . The noun name and noun type are exposed as the name and type properties of the metric MBean object name. The MBean domain name is oracle.dms. The object name also reflects the DMS noun hierarchy. Use this command... To do this... displayMetricTableNames List the names of the available metric tables. Its return value is the names of the available metric tables in a string array. displayMetricTables Show the content of the DMS metric tables. It returns an array of JMX javax.management.openmbean.CompositeData objects. dumpMetrics Display metrics in the internal format. The return value is a text document. Note: You can use JConsole to view DMS generated MBeans on a Java EE server either locally or remotely. DMS generates an MBean for each Java DMS noun that has a valid noun type. It does not generate MBeans for the non-Java EE components metrics and the DMS nouns that have no noun types. Each DMS metric contained under the noun is mapped to an attribute in the metric MBean.