The following topics are provided:
After successfully deploying the plug-in, follow these steps to add the plug-in target to Cloud Control for central monitoring and management:
Log in to Enterprise Manager Cloud Control.
Click Setup, then Add Targets, and finally Add Targets Manually.
Select Add Non-Host Targets by Specifying Target Monitoring Properties. From the Target Type drop-down, select the Microsoft Internet Information Services target type. Click Add Manually.
Provide the following information for the properties:
Name: Unique target name across all the Cloud Control targets, such as iis_Hostname. The name represents this Microsoft Internet Information Services target across all user interfaces within Cloud Control.
Host: Full name (inclusive of domain, such as machineA.com
) or the IP address of the host
Username: Host user name that must be an Administrator user. Required only for remote Agent monitoring.
Password: Password for the Username. Required only for remote Agent monitoring.
Agent Location: "Remote" specifies that the Agent monitoring Internet Information Services 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.
Note:
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.
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.
Note:
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.
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:
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:
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.
Note:
For a remote Agent, the platform to which the Agent is installed can be any Windows type that may not be supported for the Internet Information Services. For example, if the Internet Information Services is running on Windows 2003, you can install the remote Agent on Windows XP to monitor it.