Optimize 10.3.0 | 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.
Password
Password needed to log in to the asset.
*Protocol
Protocol used to connect to the Universal Messaging server or cluster being discovered. Supported protocols are nsp. nsps, nhp, and nhps. The default is nsp. To monitor a Universal Messaging server or cluster with SSL, select nsps as the protocol. Note that when using SSL, the Universal Messaging server or cluster must be configured to support SSL and the Infrastructure Data Collector must be configured to use the appropriate key and trust stores using the JNDI Configuration setting on the Configure Servers tab of the My webMethods Define Environments page. See the Configuring BAM guide for more information about JNDI Configuration. Also, the Infrastructure Data Collector config.ini file must point to the appropriate key and trust stores. If you need to edit the config.ini file to point to key and trust stores other than the defaults, see Editing the config.ini file for Universal Messaging and My webMethods Server SSL Configuration for more information.
Client Authentication
Select the client authentication type appropriate for the Universal Messaging server or cluster being discovered. Currently, the only available option is “None”.
4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.