Optimize 10.11 | webMethods Optimize Documentation | Administering webMethods Optimize | For System Administrators | Discovering Assets and Monitoring Components | Discovering Assets | The Discovery Page | Adding Universal Messaging Server or Cluster Assets for Discovery
 
Adding Universal Messaging Server or Cluster Assets for Discovery
*To add Universal Messaging Server and Universal Messaging cluster assets for discovery
1. In My webMethods: Navigate > Applications > Administration > Analytics > Infrastructure Components > Discovery
2. Click Add Asset.
The Add Asset Discovery dialog is displayed.
3. Populate the fields (required fields are identified with *).
The following table describes the fields in the Add Asset Discovery dialog.
Field
Description
*Asset Type
Select the type of asset (Universal Messaging server or Universal Messaging cluster) to discover.
*Data Collector
Select the Infrastructure Data Collector to use for the discovery.
*Host
Enter the host name or IP address for the discovery. The name must be unique.
*Server Port
Enter the server port number for the discovery.
Username
User ID needed to log in to the asset (for Basic Authentication).
Password
Password needed to log in to the asset (for Basic Authentication).
*Protocol
Protocol used to connect to the Universal Messaging server or cluster being discovered.
The supported protocols for Basic Authentication are nsp and nhp. The default is nsp.
The supported protocols for SSL are nsps and nhps.
Important:
To monitor a Universal Messaging server or cluster with SSL, you must configure:
*the Universal Messaging server or cluster to support SSL
*Infrastructure Data Collector to use the appropriate key and trust stores in the JNDI Configuration settings on the Configure Servers tab of the My webMethods Define Environments page. For more information about Defining JNDI Configuration Settings, see Configuring BAM.
*the Infrastructure Data Collector config.ini file to point to the appropriate key and trust stores. For more information about editing the config.ini file to point to key and trust stores other than the default ones, see Editing the config.ini file for Universal Messaging and My webMethods Server SSL Configuration.
Client Authentication
Client authentication type appropriate for the Universal Messaging server or cluster being discovered. The only available option “None” is used for both Basic Authentication and SSL, depending on the selected Protocol.
4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.