DMS Sensors Common DMS Terms and Concepts

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. Oracle Dynamic Monitoring Service 6-9

6.4.5 Viewing metrics with Oracle Enterprise Manager

Oracle Fusion Middleware automatically and continuously measures data regarding the components performance, state and on-going behavior. The metrics are automatically enabled; there is no need to set options or perform any extra configuration to collect them. For more information see Section 4.2.1, Viewing Performance Metrics Using Fusion Middleware Control .

6.4.6 Viewing metrics using WSADMIN IBM WebSphere

The following commands can be used with IBM WebSphere to display the following: For more information on using IBM WebSphere, see Managing Oracle Fusion Middleware on IBM WebSphere in the Oracle Fusion Middleware Third-Party Application Server Guide.

6.5 Accessing DMS Metrics with WLDF

The WebLogic Diagnostics Framework WLDF provides a diagnostic feature that allows MBean attributes to be harvested and monitored for specific conditions. This provides a proactive way of monitoring activity in your environment and creating E-mail and JMX notifications when a condition is triggered. The following steps describe how to configure WLDF to send an E-mail notification using the WebLogic Administration Console:

1. Select an existing or create a new Diagnostics Module from the Diagnostics screen.

2. Click on the Watches and Notifications tab.

3. Click New.

4. Enter a Watch Name and click Next.

5. Enter the text as the Watch Rule and click Next.

{ServerRuntime[NOUNTYPE]oracle.dms:name=starWarsalliance,type=NounTypef orceBalance_value} = BAD

6. Select Use a manual reset alarm and click Next. The manual reset option means

that once an E-mail is triggered, you must reset the watch using the WebLogic Administration Console.

7. Select the E-mail notification type and click Finish.

It is also possible to configure WLDF to collect the MBean data for offline storage and analysis. This is achieved by configuring a WLDF Diagnostic Module to collect specific MBean attributes, and can be done so using the WebLogic Administration Console. Use this command... To do this... OracleDMS.displayMetricTableNames List the names of the available metric tables. Its return value is the names of the available metric tables in a string array. OracleDMS.displayMetricTables Show the content of the DMS metric tables. It returns an array of JMX javax.management.openmbean.CompositeData objects. OracleDMS.dumpMetrics Display metrics in the internal format. The return value is a text document. 6-10 Oracle Fusion Middleware Performance and Tuning Guide For more information on using WLDF to harvest and monitor MBean data see Oracle Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.

6.6 DMS Execution Context

The DMS execution context is the mechanism by which requests such as HTTP or RMI requests can be uniquely identified and thus tracked as they flow through the system. It also provides a means by which context information can be communicated between cooperating Fusion Middleware components involved in fulfilling requests.

6.6.1 DMS Execution Requests and Sub-Tasks

The DMS execution context has been developed with the understanding that a single request or task may form the root of a tree of sub-tasks that are coordinated to complete the request or root task. Consider the following examples of requests and their associated sub-tasks:

1. An HTTP request sent directly to Oracle WebLogic Server from a browser:

■ Root task only on Oracle WebLogic Server

2. An HTTP request sent through Oracle HTTP Server acting as a reverse proxy to

Oracle WebLogic Server: ■ Root task on Oracle HTTP Server ■ Single sub-task on Oracle WebLogic Server

3. An HTTP request sent from Oracle HTTP Server acting as a reverse proxy to

Oracle WebLogic Server that then requires invocation of two remote web services from Oracle WebLogic Server in order to fulfill the request: ■ Root task on Oracle HTTP Server ■ Single sub-task on Oracle WebLogic Server ■ Two sub-sub-tasks, one on each web service A DMS execution context is composed of the following: ■ A unique identifier, the ECID The Execution Context ID ECID is unique for each new root task and is shared across the tree of tasks associated with the root task. ■ A relationship identifier, the RID The Relationship ID RID is an ordered set of numbers that describes the location of each task in the tree of tasks. The leading number is usually a zero. A leading number of 1 indicates that it has not been possible to track the location of the sub-task within the overall sub-task tree. ■ A set of name-value pairs by which globally relevant data can be shared among Oracle Fusion Middleware components. The following three scenarios illustrate how ECID and RID are used when an HTTP request is sent from Oracle HTTP Server acting as a reverse proxy to an Oracle WebLogic Server and the server requires invocation of two remote web services from Oracle WebLogic Server. 1. Root task on Oracle HTTP Server: – New ECID = B5C094FA...BE4AE8