Optimize 10.7 | webMethods Optimize Documentation | Administering webMethods Optimize | For System Administrators | Discovering Assets and Monitoring Components | Monitoring Components
 
Monitoring Components
 
Displaying a List of Monitored Components
Configuring Monitored Components
Monitored components are components of discovered assets, such as Integration Servers, Universal Messaging Servers, and Broker Servers, about which Optimize can report information. In order to monitor, or collect information about, a component of a discovered asset, one or more KPIs must be associated with that component. This section describes how to view and configure monitored components.
In an appropriately configured system, the Monitored Components page shows a tree view of component types that can be monitored. By default, a set of monitored component types is added to the Monitored Components page when you start the Infrastructure Data Collector, and these enable you to collect a baseline of information about your system infrastructure using KPIs. In addition, a set of KPIs is also provided for available components, and you must associate these with applicable components in order to initiate monitoring. Also, if you want to monitor additional system components, you must discover the appropriate assets as described earlier in this chapter, and then associate the appropriate KPIs with the appropriate components. An Edit icon is provided on the Monitored Components page to enable you to select those instances and KPIs.
Note that the Monitored Components page is empty until you start an Infrastructure Data Collector in your environment. The default set of component types that you can monitor is loaded when you start the Infrastructure Data Collector; however, the number of available components displayed in the Monitored Components page is zero until you have discovered assets of that component type (see Discovering Assets for instructions).
Tip:
If the default set of monitored components does not appear after you have started the Infrastructure Data Collector, first confirm that the Infrastructure Data Collector, Analytic Engine, and My webMethods with the Optimize user interface have been installed and started. If these components have been installed and started, it is likely that the metadata was not properly loaded. Use the following steps to reload the metadata: (1.) Verify that the JMS Queue configuration is the same for both the Infrastructure Data Collector and the Analytic Engine. This can be verified from the JNDI Configuration “Connection Uri” setting on the Configure Servers tab in the Edit Environment page (Navigate > Applications > Administration > System-Wide > Environments > Define Environments). (2.) Shut down the Infrastructure Data Collector (see Starting and Stopping Infrastructure Data Collector. (3.) Open Software AG_directory /profiles/InfraDC/configuration/infradc/config/infradc.cnf in a text editor, and set the metadataloaded property to false. (4.) Restart the Infrastructure Data Collector.
After you have discovered assets of a component type in your environment, you can configure the instances of that component type that you want to monitor, as well as the KPIs that you want to use to monitor the instances of that component type. For detailed information about the KPIs associated with each type of monitored component, see Monitored KPI Definitions
Note:
The Broker data collector does not automatically detect when a Broker territory or gateway is deleted. As a result, the Monitored Components and Analytics Overview pages still show that the Territories, Gateways, and related KPIs exist. As a workaround, you should manually remove territories and gateways from the Monitored Components page and delete the related KPIs.