Optimize 10.11 | webMethods Optimize Documentation | Administering webMethods Optimize | For System Administrators | Discovering Assets and Monitoring Components | Overview of Discovering Assets and Monitoring Components | Infrastructure Data Collector
 
Infrastructure Data Collector
Infrastructure Data Collector enables you to identify Software AG component resources to monitor and analyze. Using Infrastructure Data Collector, you can monitor the following:
*Software AG Universal Messaging servers
When you start monitoring a Universal Messaging Server, Infrastructure Data Collector makes related items available for monitoring. Such items include Universal Messaging channels, queues, and datagroups that are running on the Universal Messaging Server.
*Broker Servers.
When you start monitoring a Broker Server, Infrastructure Data Collector makes related items available for monitoring. Such items include Broker clients, document types, and gateways and territories that are running on the Broker Server.
*Integration Servers.
When you start monitoring an Integration Server, Infrastructure Data Collector makes related items available for monitoring. Such items include the Integration Server clusters (if enabled) and all Integration Server ports; Trading Networks Server, if you have that component installed; and packages that are running on the Integration Server. To lessen the load on Infrastructure Data Collector, you can choose to monitor only certain services on an Integration Server.
If clustering is enabled on an Integration Server, the logical cluster and all nodes of the cluster are shown on the Discovered Assets and Monitored Components pages. That is, there are three or more components displayed on the Monitored Components page: the Integration Server asset, the IS Cluster asset, and one or more IS Cluster Server assets. For Integration Server clusters, there are several intrinsic KPI available that enable you to monitor cluster components. Refer to Monitored KPI Definitions for more information about KPIs that are available for Integration Server cluster monitoring.
Note:
To monitor an Integration Server which uses a webMethods API Gateway license, the Publish/Subscribe property in the license file must be set to Yes. If Publish/Subscribe is set to No, contact your Software AG sales representative and request a new API Gateway license file.
*webMethods Adapters.
Infrastructure Data Collector lets you monitor adapters installed on Integration Servers. When you start monitoring an Integration Server, Infrastructure Data Collector makes all adapter components that are installed on the Integration Server available for monitoring.
*SNMP Agents.
The Infrastructure Data Collector lets you specify how often SNMP data is collected and delivered to the analytic engine for processing. By selecting which monitored components and KPIs you want to monitor on the Optimize Monitored Components page, you can instruct Infrastructure Data Collector to collect monitored SNMP data.
*webMethods EntireX, webMethods ApplinX, Adabas, Adabas SOA Gateway, Com-plete, Natural, and Natural Ajax components.
Infrastructure Data Collector enables you to discover and monitor these components.
*My webMethods Servers.
Infrastructure Data Collector enables you to discover and monitor My webMethods Servers in your environment.
*Terracotta Servers and Server Arrays
Infrastructure Data Collector enables you to discover a Terracotta Server, Server Arrays, and Terracotta Ehcache.
*MashZone NextGen Servers
Infrastructure Data Collector enables you to discover and monitor MashZone NextGen Servers in your environment.
Note:
If you want Infrastructure Data Collector to monitor MashZone NextGen Server 10.1, you must modify the wrapper.conf file. For more information, see Configuring Infrastructure Data Collector for Monitoring MashZone NextGen Server 10.1.