Optimize 10.7 | webMethods Optimize Documentation | Administering webMethods Optimize | For System Administrators | Discovering Assets and Monitoring Components | Discovering Assets
 
Discovering Assets
 
The Discovery Page
The Assets Page
Asset is a generic term for network-attached resources in your environment to which you can connect and which may require periodic administrative attention. Integration Servers, Integration Server clusters, My webMethods Servers, Software AG Universal Messaging, Brokers, as well as Adabas, Natural, and SNMP components that exist in your network are examples of assets. Note that Broker Servers and SNMP components generally have child components that are typically the specific targets for monitoring.
The Analytical section of My webMethods provides several pages that enable you to discover, configure, and monitor assets. While these pages appear similar, they have specific interactions and restrictions that you must be aware of when discovering and configuring assets.
Before you can monitor resources in your environment, you must discover them. Discovery is the process of locating and establishing communication with resources and their child components. Entries for resources on the Discovery page are called discoveries. The Discovery page enables you to specify the configuration used for initially conducting these discoveries. Valid discoveries become assets and are automatically propagated to the Assets page.
Once an asset has been discovered, its connection configuration information is displayed in the Discovered Assets table on the Assets page. Any changes or refinements to the asset's connection credentials (connection parameters) must be made on the Assets page, not on the Discovery page. Also these changes are not reflected on the Discovery page.
After assets are configured, they can be selected and configured for monitoring using the Monitored Components page. See Monitoring Components for more information.
Note:
It is recommended that only one Infrastructure Data Collector be used to monitor any single Integration Server instance. Optimize events are stored in memory on the monitored Optimize. Using more than one Infrastructure Data Collector on different JMS queues to monitor the same Integration Server instance could result in unexpected KPI behavior.
The Discovery and Asset page functionality is designed to accommodate complexities inherent in typical component configurations. The following example illustrates how and why these pages function as they do:
You know there is a Broker on a Broker Server somewhere in your network that you want to monitor. Also, the Broker you want to monitor has a different SSL setting than the parent Broker Server.
1. Using the Discovery page, create a discovery to locate the Broker Server and all its associated components.
2. Using the Assets page, locate the Broker you want to monitor in the Discovered Assets table, and modify its SSL settings via the Keystore connection parameters so that you can monitor the Broker.