Oracle® Enterprise Manager

System Monitoring Plug-in Installation Guide for Microsoft .NET Framework



February 2014

This document provides a brief description about the Oracle System Monitoring plug-in for Microsoft .NET Framework, details on the versions the plug-in supports, prerequisites for installing the plug-in, and step-by-step instructions on how to download, install, verify, and validate the plug-in.

Microsoft .NET Framework is a component of the Microsoft Windows operating system used to build and run Windows-based applications. The following topics are presented:

1 Description

The System Monitoring plug-in for Microsoft .NET Framework extends Oracle Enterprise Manager Cloud Control to add support for managing the Microsoft .NET Framework. By deploying the plug-in within your Cloud Control environment, you gain the following management features for Microsoft .NET Framework:

  • Monitor availability and receive Microsoft .NET Framework Server data for the following performance areas:

    • .NET CLR Memory

    • .NET CLR Networking

    • .NET CLR Locks and Threads

    • .NET CLR Exceptions

  • Perform trend analysis on collected performance information.

  • Receive e-mail and/or page notification concerning potential problems surrounding availability, performance, and/or configuration data.

  • Gain access to rich out-of-box reports.

  • Support monitoring by a remote Agent. For remote monitoring, the Agent does not need to be on the same computer as the .NET Framework.

2 Supported Versions

This plug-in supports the following versions of products:

  • Enterprise Manager Cloud Control 12c Release 1 or higher

  • Oracle Management Agent 12c Release 1 or higher for Microsoft Windows

  • Microsoft .NET Framework 1.1.x, 2.0.x, 3.0.x, 3.5.x, and 4.0 running on supported Microsoft Windows Server (see note below):


For details on which editions (such as Enterprise, Standard, and so forth) and versions of Windows operating systems that this Microsoft product is supported to run on, refer to the Microsoft website and/or documentation.

3 Prerequisites

The following prerequisites must be met before you can deploy the plug-in:

  • Microsoft .NET Framework 1.1.x, 2.0.x, 3.0.x, 3.5.x, or 4.0 is installed.

  • The following components of Oracle Enterprise Manager Cloud Control 12c Release 1 or higher are installed:

    • Oracle Management Service with Oracle Management Repository

    • Oracle Management Agent for Windows

      You can install the Agent on the same computer as .NET Framework (referred to as local Agent monitoring), or you can install the Agent on a different computer from .NET Framework (referred to as remote Agent monitoring).

  • Ensure that the Windows Management Instrumentation Service is up and running.

  • For remote Agent monitoring, a remote Agent must be properly configured. See Configuring a Remote Agent for the procedure.

  • User privileges for the Job system of Enterprise Manager. For the procedure, refer to "Setting Credentials for the Job System to Work with Enterprise Manager" in Database Installation Guide for Microsoft Windows:

    This guide is listed in the Installing and Upgrading section of the Oracle Database Documentation Library at:


    If you do not assign the correct privileges for users, the deployment will fail.

4 Downloading the Plug-in

You can download plug-ins in online or offline mode. Online mode refers to an environment where you have Internet connectivity, and can download the plug-in directly through Enterprise Manager from My Oracle Support. Offline mode refers to an environment where you do not have Internet connectivity, or where the plug-in is not available from My Oracle Support.

See the Managing Plug-ins chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for details on downloading the plug-in in either mode:

5 Deploying the Plug-in

You can deploy the plug-in to an Oracle Management Service instance using the Enterprise Manager Cloud Control console, or using the EM Command Line Interface (EMCLI). While the console enables you to deploy one plug-in at a time, the command line interface mode enables you to deploy multiple plug-ins at a time, thus saving plug-in deployment time and downtime, if applicable.

See the Managing Plug-ins chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for instructions on deploying the plug-in:

6 Discovering Targets

After successfully deploying the plug-in, follow these steps to add the plug-in target to Cloud Control for central monitoring and management:

  1. Log in to Enterprise Manager Cloud Control.

  2. Click Setup, then Add Targets, and finally Add Targets Manually.

  3. Select Add Non-Host Targets by Specifying Target Monitoring Properties. From the Target Type drop-down, select the Microsoft .NET Framework target type. Click Add Manually.

  4. Provide the following information for the properties:

    • Name — Unique target name across all the Cloud Control targets, such as .net_Hostname. The name represents this .NET target across all user interfaces within Cloud Control.

    • Host — Full name (inclusive of domain, such as or the IP address of the host

    • Username — Host user name (must be an Admin account). Required only for remote Agent monitoring.

    • Password — Password for the user name. Required only for remote Agent Monitoring.

    • Agent Location — "Remote" specifies that the Agent monitoring .NET Framework targets is not on the same computer as the target being monitored. (See Configuring a Remote Agent for more information.) "Local" specifies that the Agent monitoring the target is on the same computer as the target being monitored.


      • The agent chosen must also be an agent running on a Windows host.

      • The "remote" and "local" identifiers are case-sensitive and should be lowercase.

  5. Click Test Connection to make sure the parameters you entered (such as the password) are correct. If the test was successful, proceed with adding targets.


After you deploy and configure the plug-in to monitor one or more targets in the environment, you can customize the monitoring settings of the plug-in. This alters the collection intervals and threshold settings of the metrics to meet the particular needs of your environment. If you decide to disable one or more metric collections, this could impact the reports that the metric is a part of.

7 Verifying and Validating the Plug-in

After waiting a few minutes for the plug-in to start collecting data, use the following steps to verify and validate that Enterprise Manager is properly monitoring the plug-in target:

  1. Click Targets, then All Targets. On the All Targets page, click the Microsoft .NET Framework target link from the Monitored Targets table. The Microsoft .NET Framework home page appears.

  2. Verify that no metric collection errors are reported in the Metrics table.

  3. Ensure that reports can be seen and no errors are reported by selecting the Reports property page.

8 Configuring a Remote Agent

The steps for deploying the plug-in are the same for remote Agent monitoring and local Agent monitoring. However, if the Agent is on a remote computer from the plug-in target, certain configuration changes are required to access the Windows Management Instrumentation (WMI) data on the computer where the plug-in target resides.

In a scenario where computer A runs the Agent, and the target is installed on computer B, do the following to set up computer A:

  1. Go to the Windows Control Panel and select Administrative Tools, then Services.

  2. Select the Oracle Enterprise Manager Agent service from the listed computer where the Agent is running.

  3. Right-click the service, then select Properties.

  4. Click the Log On tab. By default, this service is started with the Local System account.

  5. Change the default account by selecting the This account radio button, and provide an account and password that exist on both computer A and computer B.

    Note that the account should be a member of the Administrators group, and the account should have administrative privileges on computer B. The password should not be left blank.

  6. Click OK, then restart the Agent service.

  7. Ensure that the Windows Management Instrumentation Service is up and running on both computers.

The Agent should now be able to collect data from the remote plug-in target computer. If the configuration above is not initiated, metric collection errors can appear for the plug-in target's metrics.

To ensure that metric collection errors do not occur within Enterprise Manager, Oracle recommends reviewing the Microsoft documentation on the WMI setup. Refer to the Microsoft documentation from the Microsoft website for additional configuration details.


For a remote Agent, the platform to which the Agent is installed can be any Windows type that may not be supported for .NET Framework. For example, if .NET Framework is running on Windows 2003, you can install the remote Agent on Windows XP to monitor it.

9 Upgrading the Plug-in

The Self Update feature allows you to expand Enterprise Manager's capabilities by updating Enterprise Manager components whenever new or updated features become available. Updated plug-ins are made available via the Enterprise Manager Store, an external site that is periodically checked by Enterprise Manager Cloud Control to obtain information about updates ready for download. See the Updating Cloud Control chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for steps to update the plug-in:

10 Undeploying the Plug-in

See the Managing Plug-ins chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for steps to undeploy the plug-in:

11 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired.

System Monitoring Plug-in Installation Guide for Microsoft .NET Framework, Release


Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.