Discovering Assets

Edit online

About this task

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, IBM My webMethods Servers, IBM webMethods Universal Messaging, Brokers, as well as Adabas (Deprecated), Natural (Deprecated), 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.

The Discovery Page

Edit online

About this task

The Discovery page shows information about all existing discoveries and enables you to create new discoveries. Components that can be discovered include Integration Servers, Terracotta Management Consoles, IBM webMethods Universal Messaging Servers, Broker Servers, IBM My webMethods Servers, and SNMP components as well as EntireX, ApplinX, Adabas (Deprecated), Adabas SOA Gateway (Deprecated), Com-plete (Deprecated), Natural (Deprecated), and Natural Ajax (Deprecated) components. Note that this page does not show the parent SNMP Config file for SNMP components or child Broker components underneath the parent Broker Servers. When you discover a component using Asset Discovery on the Discovery page, that discovery runs automatically and the discovered asset is listed on the Assets page. The Assets page shows the child Brokers and parent SNMP Config files in addition to Integration Servers, Broker Servers, and SNMP agents.

You may need to edit connection information for a discovery if the parameters used to create that discovery have changed. If you change information about a discovery on the Discovery page, the changes are not reflected on the Assets page unless you update the settings on the Discovery page and rerun the discovery.

The Broker auto-discovery feature automatically detects when new components have been created on a previously discovered Broker Server asset. For example, auto discovery can find a new Broker that has been created on a Broker Server. When Broker auto-discovery is enabled, it runs automatically on all available Broker Servers to discover newly added components. Note that Broker Servers must still be manually discovered, even if Broker auto-discovery is enabled.

Broker auto-discovery is disabled by default, because it can have a negative impact on system performance in some configurations. You must use the Central Configuration feature of My webMethods to enable auto-discovery. See the “Defining Logical Server Subcomponents for the Infrastructure Data Collector” section of the Managing webMethods Environments chapter of Configuring BAM for more information.

Note: If the Infrastructure Data Collector is down and a new Broker is added or deleted while auto-discovery is enabled, the new Broker is discovered or removed when Infrastructure Data Collector comes up. But if a document type/custom adapters/territory/gateway is changed while Infrastructure Data Collector is down then it will not be detected when Infrastructure Data Collector comes back up. In this case, you must manually re-discover the Broker Server to update these components.
Note: The Optimize Analytic Engine does not function with IPv6, so Optimize for Infrastructure must be run on IPv4 while it monitors resources running on IPv6. As a workaround, users need to discover IBM applications running on IPv6 using the appropriate host name rather than the IPv6 address.

To view the Discovery page

Procedure

In My webMethods navigate to Navigate > Applications > Administration > Analytics > Infrastructure Components > Discovery

Results

The primary Discovery page component is the Assets to Discover table. This table displays a No Discoveries Found message until you create a discovery. Two buttons titled Add Assets and Add Network enable you to create discoveries.

The following table describes the information that is available for the discovered assets.

Column Description
NAME The IP address or host name, and the port number for the discovery.
Note: Discovered Integration Server assets always consist of the Integration Server's fully qualified DNS name and port number, even if an IP address or range was specified at the Discovery page.
TYPE The component type (SNMP, Broker Server, Integration Server, My webMethods Server, Adabas (Deprecated), ApplinX, EntireX, Adabas SOA Gateway (Deprecated), Com-plete (Deprecated), Natural (Deprecated), Natural Ajax (Deprecated), Apama (Deprecated), MashZone NextGen (Deprecated), Terracotta or Universal Messaging) of the asset for which you are searching, and the type of discovery (Asset or Network).
DATA COLLECTOR The network address or host name of the data collector used for this discovery.
STATUS State of the discovery as listed below.
  • Configured: The discovery has been configured but has not been run. This status applies only to a Network search.
  • Running: Indicates a network discovery in progress.
  • Completed: Indicates a discovery that completed without errors.
  • Requested: Indicates that a discovery request has been made. The discovery may be in progress or the Infrastructure Data Collector may not have received the discovery request.
  • Cancelled: Indicates that there has been a request to stop a network discovery.
  • Failed: Indicates that a discovery failed. If status is Failed, position the mouse pointer over the status to display information about the cause of the failure.
LAST ACTION Time the last action indicated in the STATUS column was performed.
ACTIONS Selected actions you can perform on the discovery.

In addition, you can do the following on the Discovery page:

  • Click the Add Asset button to discover an asset for which you have specific addressing information. You can discover different types of components using this method. For more information, see Adding an Asset.
  • Click the Add Network button to discover network assets using a range of IP addresses. You can discover Integration Servers and Broker Servers using this method. For more information, see Adding a Network.
  • Click the Delete button to remove selected discoveries. Note that this button is inactive until an asset is selected. Also, you cannot remove a discovery in progress. Deleting an asset does not affect previously discovered or monitored assets. For instance, deleting an SNMP Discovery does not delete discovered SNMP assets or associated event data.
  • Click the Refresh button to update the discovery display. Click this button after adding or discovering any assets to ensure that the information displayed is current.
  • Click the Export Table button to view the contents of the Discovery page as a table.
  • Click a discovery name in the NAME column to view and/or edit the connection parameters for that asset.
  • To view information about an asset with a failed status, position the mouse pointer over the word Failed in the STATUS column.
  • Click beside a column heading to sort the display by the information in the column.
  • Click an icon in the ACTIONS column to manipulate a discovery.

The following table provides information about specific icons and the actions that they facilitate.

If you want to Do this
Cancel a network discovery that is in progress. Click Cancel icon in the ACTIONS column beside the network discovery you want to cancel. (This icon does not appear for asset discoveries or for network discoveries that are no longer in progress.)
Run a previously created asset discovery. Click Green arrow icon in the ACTIONS column beside the discovery you want to run. (You cannot run a discovery that is already in progress.)
Change the connection parameters of a previously created asset discovery. Click Edit icon in the ACTIONS column beside the discovery you want to edit. (You cannot edit an asset discovery that is in progress.)

Adding an Asset

Edit online

About this task

The Add Asset button on the Discovery page enables you to add asset discoveries to your environment when you have all of the information required to connect to those assets. You must have specific information about the host and port(s) used by the target asset to complete this procedure. Also, if you are adding an SNMP component, you must have the name and location of the SNMP Configuration file for the component. Use the following procedure and tables to add assets using the Add Asset button.

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.

To add a discovery using the Add Asset button

Procedure

  1. In My webMethods: Navigate > Applications > Administration > Analytics > Infrastructure Components > Discovery
    The Discovery page is displayed.
  2. Click Add Asset.
    The Add Asset Discovery dialog is displayed.
  3. Click the Down arrow to the right of the Asset Type field, and select the desired discovery type.
    Note: If you add an asset to your system or start an existing asset that was previously not running, you may need to refresh the Add Asset Discovery dialog in order for that asset to be displayed in the Asset Type list.
    The fields on the Add Asset Discovery dialog change to match those required by the selected discovery type.
  4. Complete the fields on the Add Asset Discovery dialog.
    Important: For the purpose of connecting and fetching data from the monitored component, in accordance with GDPR, Optimize for Infrastructure stores the username and password that you enter during the Asset Discovery. You can delete the username and password by editing the information in the Asset Discovery configuration.
    Refer to the sections below for information about the optional and required fields for each valid discovery type.
  5. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.
  6. Click Refresh to update the information on the Discovery page.

Adding Adabas (Deprecated) or Natural (Deprecated) Component Assets for Discovery

Edit online

About this task

To add Adabas or Natural component assets for discovery

Procedure

  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 (Adabas or Natural) to discover.
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    Tip: Only one Infrastructure Data Collector can be used to monitor the same component on different JMS queues, so if you use multiple Infrastructure Data Collectors, be careful not to point more than one to the same component.
    *Host Enter the host name or IP address for the EntireX Broker host. The name must be unique.
    *Port Enter the EntireX Broker port number. The default for both Adabas and Natural components is 1971.
    *RPC Server Enter the host name of the Natural RPC server.
    *Username User ID needed to log in to the asset.
    *Password Password needed to log in to the asset.
    KeyStore File (Optional) Enter the name and path of the EntireX Broker KeyStore file.
    RPC User User ID needed for secure connections to the Natural RPC server.
    RPC Password Password needed for secure connections to the Natural RPC server.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding Apama (Deprecated) Server Assets for Discovery

Edit online

About this task

To add Apama server assets for discovery

Procedure

  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
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    *Host Enter the host name or IP address for the Apama server. The name must be unique.
    *Port Enter the server port number for the applicable Apama server. The default port for the Apama Correlator is 15903.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding ApplinX, EntireX, Adabas SOA Gateway (Deprecated), Com-plete (Deprecated), or Natural Ajax (Deprecated) Component Assets for Discovery

Edit online

About this task

To add ApplinX, EntireX, Adabas SOA Gateway, Com-plete, or Natural Ajax (Deprecated) component assets for discovery

Procedure

  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 (ApplinX, Adabas SOA Gateway, Com-plete, EntireX, or Natural Ajax (Deprecated)) to discover.
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    Tip: Only one Infrastructure Data Collector can be used to monitor the same component on different JMS queues, so if you use multiple Infrastructure Data Collectors, be careful not to point more than one to the same component.
    *Host Enter the host name or IP address for the discovery. The name must be unique.
    *Port Enter the ApplinX or EntireX port number. For ApplinX components the default is 2380, and for EntireX components the default is 1971.The default port for Adabas SOA Gateway components is 56100, and the default for Com-plete components and Natural Ajax (Deprecated) components is 80.
    SSL (Optional for some components) Select if an SSL connection is required.
    *Username User ID needed to log in to the asset.
    *Password Password needed to log in to the asset.
    KeyStore File (Optional) Applies only to EntireX components. Enter the name and path of the EntireX KeyStore file.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding Broker Server Assets for Discovery

Edit online

About this task

Note: You can also add Broker Server assets to your environment when you do not know the exact connection information by using a range of IP addresses. For more information, see Adding an Asset.

To add Broker Server assets for discovery

Procedure

  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 (Broker Server) 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.
    *Monitor Port Enter the Broker Server monitor port number.

    Default = 6850.

    *Server Port Enter the Broker Server port number.

    Default= 6849.

    Client Authentication Select the client authentication type appropriate for the Broker Server being discovered. Available options are “None”, “Basic” and “Certificate”. Note that additional fields may be displayed on the Discovery dialog based on your selection as explained below.
    Encryption Select this check box if the Broker Server being discovered requires encryption. Note that TrustStore File and TrustStore Type fields are displayed and are required if encryption is selected.
    Username User ID required to log in to the asset. Displayed only when client authentication is “Basic.”
    Password Password required to log in to the asset. Displayed only when client authentication is “Basic.”
    KeyStore File Type the name and path of the Broker Server KeyStore file. This field is displayed, and required, only when client authorization is “Certificate”.
    KeyStore Type Type the KeyStore file type. This field is displayed, and required, only when client authorization is “Certificate”.
    KeyStore Password Type the password for the Broker Server certificate file. This field is displayed, and required, only when client authorization is “Certificate”.
    TrustStore File Type the TrustStore filename if required to identify the owner or issuer of the certificate file. This field is displayed only when either the client authorization is “Certificate” or the Encryption box is checked. If the Encryption box is checked, the field is required.
    TrustStore Type Type the TrustStore file type. This field is displayed only when either the client authorization is “Certificate” or the Encryption box is checked. If the Encryption box is checked, the field is required.
    Note: Some of the fields displayed vary according to the Broker Server’s client authentication level (“None”, “Basic”, or “Certificate”).
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding Event Routing Server Assets for Discovery (Deprecated)

Edit online

About this task

To add Event Routing assets for discovery

Procedure

  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 (Event Routing Framework) to discover.
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    *JMX Host Enter the JMX host name or IP address for the discovery. The name must be unique.
    *JMX Port Enter the JMX port number for the discovery.
    Username User ID needed to log in to the asset. Required if displayed but not displayed if a KeyStore file is listed.
    Password Password needed to log in to the asset. Required if displayed but not displayed if a KeyStore file is listed.
    SSL

    (Optional for some components) Select if an SSL connection is required.

    *TrustStore File This field appears if SSL is selected. Specify the location of the TrustStore file.
    *TrustStore Password This field appears if SSL is selected. Specify the password for the TrustStore file.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding Integration Server Assets for Discovery

Edit online

About this task

Note: If clustering is enabled on the Integration Server, the Discovery page is the same as for a standalone Integration Server. Following discovery of an Integration Server cluster, however, the logical cluster and individual cluster components are displayed on the Assets page, and you can monitor cluster components on the Monitored Components page.

To add Integration Server assets for discovery

Procedure

  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 (Integration Server) to discover.
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    Tip: Only one Infrastructure Data Collector can be used to monitor the same Integration Server instance on different JMS queues, so if you use multiple Infrastructure Data Collectors, be careful not to point more than one to the same Integration Server.
    *Host Enter the host name or IP address for the discovery. The name must be unique.
    *Port Enter the port number for the discovery.
    SSL (Optional) Select if an SSL connection is required.
    KeyStore File This field appears only if SSL is selected. Specify the location of the KeyStore file.
    *Username User ID needed to log in to the asset. Required if displayed but not displayed if a KeyStore file is listed.
    *Password Password needed to log in to the asset. Required if displayed but not displayed if a KeyStore file is listed.
    KeyStore Password This field appears only when KeyStore file information is supplied. Specify the password for the KeyStore file.
    KeyStore Alias This field appears only when KeyStore file information is supplied. Specify the alternate name for the KeyStore file.
    Include System Packages/Services (Optional) Select if you want to include webMethods-supplied packages and services in the data returned from the Integration Server. Disabled by default.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding JMX Assets for Discovery

Edit online

About this task

In order to monitor JMX assets, before discovering the JMX assets you must configure the Filter File. The Filter File is an .xml file that contains domains and mbeans. After you specify a domain, you can use a wildcard (*) to retrieve all mbeans within the domain. The format of the Filter File is the following: 
<?xml version="1.0"?>
<jmxfilter id ="testFilter">
   <domain id="java.lang">
      <mbeanType>Runtime</mbeanType>
      <mbeanType>Memory</mbeanType>
      <mbeanType>OperatingSystem</mbeanType>
   </domain>
   <domain id="Catalina">
      <mbeanType>WebModule</mbeanType>
      <mbeanType>BundleWebResourceRoot</mbeanType>
   </domain>
   <domain id="com.softwareag.events.routing">
      <mbeanType>EventTypes</mbeanType>
   </domain>
   <domain id="com.sun.management">
      <mbeanType>*</mbeanType>
   </domain>
</jmxfilter>

To add JMX assets for discovery

Procedure

  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 (JMX) to discover.
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    *Host Specify the host name or IP address for the discovery. The name must be unique.
    *Port Specify the port number for the discovery.
    SSL (Optional) Select the check box if an SSL connection is required.
    *Username User ID needed to log in to the asset.
    *Password Password needed to log in to the asset.
    *Filter File Specify the path to the filter file.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding MashZone NextGen (Deprecated) Server Assets for Discovery

Edit online

About this task

In order to monitor MashZone NextGen TomEE server component types, prior to discovering the MashZone NextGen assets, update the Software AG_directory\MashZone NextGen\apache-tomee-jaxrs\bin\startup.bat/sh script with the following:
  • Add Catalina variables to enable JMX:On Windows, before the call "%EXECUTABLE%" start %CMD_LINE_ARGS% command: 
    Dcom.sun.management.jmxremote=true� 
set CATALINA _OPTS=%CATALINA_OPTS% -Dcom.sun.management.jmxremote.port=8088� 
set CATALINA_OPTS=%CATALINA_OPTS% -Dcom.sun.management.jmxremote.ssl=false� 
set CATALINA_OPTS=%CATALINA_OPTS% 
-Dcom.sun.management.jmxremote.authenticate=false� 
rem ### Use actual ip if below doesn't work 
set CATALINA_OPTS=%CATALINA_OPTS% -Djava.rmi.server.hostname=host 
or IP 
set CATALINA_OPTS=%CATALINA_OPTS% -Djava.rmi.server.useLocalHostname=true
    And on UNIX before the exec "$PRGDIR"/"$EXECUTABLE" start "$@" command: 
    export CATALINA_OPTS="${CATALINA_OPTS} 
-Dcom.sun.management.jmxremote=true" 
export CATALINA_OPTS="${CATALINA_OPTS} 
-Dcom.sun.management.jmxremote.port=8088" 
export CATALINA_OPTS="${CATALINA_OPTS} 
-Dcom.sun.management.jmxremote.ssl=false" 
export CATALINA_OPTS="${CATALINA_OPTS} 
-Dcom.sun.management.jmxremote.authenticate=false" 
### Use actual ip if below doesn't work 
export CATALINA_OPTS="${CATALINA_OPTS} 
-Djava.rmi.server.hostname=host or IP"export 
CATALINA_OPTS="${CATALINA_OPTS} 
-Djava.rmi.server.useLocalHostname=true"
  • Add JMX variables: 
    -Dcom.sun.management.jmxremote=true 
-Dcom.sun.management.jmxremote.rmi.port=port 
-Dcom.sun.management.jmxremote.authenticate=false 
-Dcom.sun.management.jmxremote.ssl=false 
-Djava.rmi.server.hostname=host_name 
-Djava.rmi.server.useLocalHostname=true
Important: If you are monitoring MashZone NextGen Universal Messaging server component types, and they are missing after the discovery of MashZone NextGen assets, check the Infrastructure Data Collector error.log file available at Software AG_directory\profiles\InfraDC\logs for an error message, telling you that the MashZone NextGen Universal Messaging realm lacks the proper privileges. Add the required privileges, and rediscover the MashZone NextGen Universal Messaging component type assets.

To add MashZone NextGen server assets for discovery

Procedure

  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 (MashZone NextGen) to discover.
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    *Host Enter the host name or IP address for the MashZone NextGen Server. The name must be unique.
    *Port Enter the port number for the applicable MashZone NextGen Server.
    *Username User ID needed to log in to the asset.
    *Password Password needed to log in to the asset.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the asset discovery.

Adding IBM My webMethods Server Assets for Discovery

Edit online

About this task

To add IBM My webMethods Server assets for discovery

Procedure

  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 (IBM My webMethods Server) 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.
    *Port Enter the port number for the discovery.
    SSL (Optional) Select if an SSL connection is required.
    Root Context (Optional) Enter the root context if it is defined for this IBM My webMethods Server instance.
    *Username User ID needed to log in to the asset.
    *Password Password needed to log in to the asset.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding Presto Server version 9.9 (Deprecated) Assets for Discovery

Edit online

About this task

In order to monitor Presto TomEE server component types, prior to discovering the Presto assets, update the Software AG_directory\Presto\apache-tomee-jaxrs\bin\startup.bat/sh script with the following:
  • Add Catalina variables to enable JMX:On Windows, before the call "%EXECUTABLE%" start %CMD_LINE_ARGS% command: 
    Dcom.sun.management.jmxremote=true� 
set CATALINA _OPTS=%CATALINA_OPTS% -Dcom.sun.management.jmxremote.port=8088� 
set CATALINA_OPTS=%CATALINA_OPTS% -Dcom.sun.management.jmxremote.ssl=false� 
set CATALINA_OPTS=%CATALINA_OPTS% 
-Dcom.sun.management.jmxremote.authenticate=false� 
rem ### Use actual ip if below doesn't work 
set CATALINA_OPTS=%CATALINA_OPTS% -Djava.rmi.server.hostname=host 
or IP 
set CATALINA_OPTS=%CATALINA_OPTS% -Djava.rmi.server.useLocalHostname=true
    And on UNIX before the exec "$PRGDIR"/"$EXECUTABLE" start "$@" command: 
    export CATALINA_OPTS="${CATALINA_OPTS} 
-Dcom.sun.management.jmxremote=true" 
export CATALINA_OPTS="${CATALINA_OPTS} 
-Dcom.sun.management.jmxremote.port=8088" 
export CATALINA_OPTS="${CATALINA_OPTS} 
-Dcom.sun.management.jmxremote.ssl=false" 
export CATALINA_OPTS="${CATALINA_OPTS} 
-Dcom.sun.management.jmxremote.authenticate=false" 
### Use actual ip if below doesn't work 
export CATALINA_OPTS="${CATALINA_OPTS} 
-Djava.rmi.server.hostname=host or IP"export 
CATALINA_OPTS="${CATALINA_OPTS} 
-Djava.rmi.server.useLocalHostname=true"
  • Add JMX variables: 
    -Dcom.sun.management.jmxremote=true 
-Dcom.sun.management.jmxremote.rmi.port=port 
-Dcom.sun.management.jmxremote.authenticate=false 
-Dcom.sun.management.jmxremote.ssl=false 
-Djava.rmi.server.hostname=host_name 
-Djava.rmi.server.useLocalHostname=true
Important: If you are monitoring Presto Universal Messaging server component types, and they are missing after the discovery of Presto assets, check the Infrastructure Data Collector error.log file available at Software AG_directory\profiles\InfraDC\logs for an error message, telling you that the Presto Universal Messaging realm lacks the proper privileges. Add the required privileges, and rediscover the Presto Universal Messaging component type assets.

To add Presto server assets for discovery

Procedure

  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 (Presto Server version 9.9) to discover.
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    *Host Enter the host name or IP address for the Presto Server version 9.9. The name must be unique.
    *Port Enter the port number for the applicable Presto Server version 9.9.
    *Username User ID needed to log in to the asset.
    *Password Password needed to log in to the asset.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding SNMP Component Assets for Discovery

Edit online

About this task

To add SNMP component assets for discovery

Procedure

  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 (SNMP) to discover.
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    Tip: Only one Infrastructure Data Collector can be used to monitor the same SNMP component on different JMS queues, so if you use multiple Infrastructure Data Collectors, be careful not to point more than one to the same SNMP component.
    *SNMP Version Select the appropriate SNMP version to use when connecting to the SNMP agent for the discovery.
    *SNMP Host Enter the host name or IP address for the discovery. The name must be unique.
    *Port Enter the port number for the discovery. The default is 161.
    *Username (SNMPv3 only) User name for accessing the discovery.
    Authentication Protocol (SNMPv3 only) Type of authentication protocol to be used. Possible values are SHA1 and MD5.
    Authentication Password (SNMPv3 only) Password needed for the specified authentication protocol.
    Privacy Protocol (SNMPv3 only) Type of encryption protocol to be used. Possible values are AES and DES.
    Privacy Password (SNMPv3 only) Password needed for the specified encryption protocol.
    *Community Password (SNMPv1 and SNMPv2c only) Password needed to log in to the asset. This is the community password used for secure connections to the SNMP Agent.
    *SNMP Config Location of the SNMP MIB Configuration file on the Infrastructure Data Collector host for this SNMP component discovery.
    Note: Note that a single MIB filename cannot be used in two different locations on the same host; however, the same filename (with exactly the same path) can be used to discover SNMP agents located on different hosts.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding Terracotta Server and Terracotta Server Array Assets for Discovery

Edit online

About this task

Note: You can monitor only Terracotta 4.1 and newer servers.
Note: Following discovery of an Terracotta Server Array, the logical server and individual array components are displayed on the Assets page, and you can monitor individual components on the Monitored Components page.

To add Terracotta Server and Terracotta Server Array assets for discovery

Procedure

  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 (Terracotta) to discover.
    *Data Collector Select the Infrastructure Data Collector to use for the discovery.
    Tip: Only one Infrastructure Data Collector can be used to monitor the same Integration Server instance on different JMS queues, so if you use multiple Infrastructure Data Collectors, be careful not to point more than one to the same Integration Server.
    *Host Enter the host name or IP address for the Terracotta Management Console. The name must be unique.
    Connection Type Select TMS or Direct as the type of an existing connection.
    Note: When you select the TMS connection type, in order to monitor Terracotta servers and server components, you must have an appropriately configured Terracotta Management Console. For information about configuring a Terracotta Management Console, see the Terracotta Management Console section of the Terracotta 4.1 documentation that is available on the Terracotta website.
    *Port Enter the port number for the applicable Terracotta Management Console.
    *Group Name (Available if Connection Type is set to TMS) Enter the name of an existing Terracotta Server group as defined in Terracotta Management Console.
    SSL (Optional) Select if an SSL connection is required.
    Note: Infrastructure Data Collector does not support SSL discovery for Terracotta assets with Connection Type set to Direct.
    *TSA Name (Available if Connection Type is set to Direct) Enter the name of the relevant Terracotta Server as defined in Terracotta Management Console, or the enabled REST service in Optimize clusterable cache configuration. If a REST service is enabled, the TSA name (as defined by the user at discovery time) is used to help identify the connection.
    Username User ID needed to log in to the asset.
    Password Password needed to log in to the asset.
  4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.

Adding Universal Messaging Server or Cluster Assets for Discovery

Edit online

About this task

To add Universal Messaging Server and Universal Messaging cluster assets for discovery

Procedure

  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, and for SSL when Basic Authentication is also enabled).
    Password Password needed to log in to the asset (for Basic Authentication, and for SSL when Basic Authentication is also enabled).
    *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 IBM My webMethods Server SSL Configuration.
    Important: If you want to use SSL to monitor a Universal Messaging server or cluster which also has Basic Authentication enabled, you must provide a username and password.
    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.

Adding a Network

Edit online

About this task

The Add Network button on the Discovery page enables you to add assets to your environment when you do not know the exact connection information for the desired assets on your network. You can locate and add Integration Server and Broker Server assets using a range of IP addresses. Use the following procedure and tables to add assets using the Add Network button.

Note: Only Integration Server and Broker Server components can be discovered using the Add Network button. For more information about adding other assets, see Adding an Asset.

To add a discovery using the Add Network button

Procedure

  1. In My webMethods: Navigate > Applications > Administration > Analytics > Infrastructure Components > Discovery
    The Discovery page is displayed.
  2. Click Add Network.
    The Add Network Discovery dialog is displayed.
  3. Populate the fields (required fields are identified with *).
    The fields on the Add Network Discovery dialog change to match those required by the selected discovery type.
  4. Complete the fields on the Add Network Discovery dialog.
    Refer to the tables that follow this procedure for information about the optional and required fields for each valid discovery type.
  5. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the discovery.
  6. Click Refresh to update the information on the Discovery page.
    Note: Network discovery sends UDP echo and NETBIOS Name Server query requests to each address within the specified address range. When a host responds to these requests, it is added to the list of servers. The UDP echo service (port 7) and NETBIOS Name Server (port 137) must be available on the remote hosts for them to be discovered through Network Search.

Results

To discover an Integration Server, enter the information from the table below on the Add Network Discovery dialog (required fields are identified with *) :

The following table describes the fields in the Add Network Discovery dialog.

Field Description
*Asset Type Select the type of asset (Integration Server) to discover.
*Discovery Name Enter a name for this discovery.
*Data Collector Select the Infrastructure Data Collector to use for the discovery.
Tip: Only one Infrastructure Data Collector can be used to monitor the same Integration Server instance on different JMS queues; so if you use multiple Infrastructure Data Collectors, be careful not to point more than one to the same Integration Server.
*Start IP Enter the IP address at the beginning of the range to scan.
*End IP Enter the IP address at the end of the range to scan.
*Port Enter the port number for the discovery.
SSL (Optional) Select if an SSL connection is required.
KeyStore File This field appears only if SSL is selected. Specify the location of the KeyStore file.
*Username User ID needed to log in to the asset. Required if displayed but not displayed if a KeyStore file is listed.
*Password Password needed to log in to the asset. Required if displayed but not displayed if a KeyStore file is listed.
KeyStore Password This field appears only when KeyStore file information is supplied. Specify the password for the KeyStore file.
KeyStore Alias This field appears only when KeyStore file information is supplied. Specify the alternate name for the KeyStore file.
Include System Packages/Services (Optional) Select if you want to include webMethods-supplied packages and services in the data returned from the Integration Server. Disabled by default.
Note: To discover an Integration Server which is hosted on a separate virtual machine, using its IPv6 address, open the Software AG_directory/profiles/IS_default/configuration/custom_wrapper.conf file located on that virtual machine and add the following line:
wrapper.java.additional.400=-Djava.rmi.server.hostname=[IPv6 address of the machine which hosts the Integration Server]

The IPv6 address should be enclosed within square brackets.

To discover a Broker Server, enter the information from the table below on the Add Network Discovery dialog (required fields are identified with *).

The following table describes the fields in the Add Network Discovery dialog.

Field Description
*Asset Type Select the type of asset (Broker Server) to discover.
*Discovery Name Enter a name for this discovery.
*Data Collector Select the Infrastructure Data Collector to use for the discovery.
*Start IP Enter the IP address at the beginning of the range to scan.
*End IP Enter the IP address at the end of the range to scan.
*Monitor Port Enter the Broker monitor port number.
*Server Port Enter the Broker Server port number.
Client Authentication Select the client authentication type appropriate for the Broker Server being discovered. Available options are “None”, “Basic” and “Certificate”. Note that additional fields may be displayed on the Discovery dialog based on your selection as explained below.
Encryption Select this check box if the Broker Server being discovered requires encryption. Note that TrustStore File and TrustStore Type fields are displayed and are required if encryption is selected.
KeyStore File Type the name and path of the Broker Server KeyStore file. This field is displayed, and required, only when client authorization is “Certificate”.
KeyStore Type Type. the KeyStore file type. This field is displayed, and required, only when client authorization is “Certificate”.
KeyStore Password Type the password for the Broker Server certificate file. This field is displayed, and required, only when client authorization is “Certificate”.
TrustStore File Type the TrustStore filename if required to identify the owner or issuer of the certificate file. This field is displayed only when either the client authorization is “Certificate” or the Encryption box is checked. If the Encryption box is checked, the field is required.
TrustStore Type Type the TrustStore file type. This field is displayed only when either the client authorization is “Certificate” or the Encryption box is checked. If the Encryption box is checked, the field is required.

Editing the config.ini file for Universal Messaging and IBM My webMethods Server SSL Configuration

Edit online

About this task

If you want to discover a Universal Messaging server or a IBM My webMethods Server that uses SSL, you must ensure that the config.ini file contains the correct location for the KeyStore and TrustStore certificates.
Note: If you are using both a Universal Messaging server and a IBM My webMethods Server that use SSL, you must combine their KeyStore and TrustStore certificates.

To update the TrustStore/KeyStore location in the config.ini file

Procedure

  1. Open the <installdir>/profiles/InfraDC/configuration/config.ini file using an appropriate text editor.
  2. Locate and edit the TrustStore and KeyStore locations so that they are accurate for the Universal Messaging server or the IBM My webMethods Server being discovered.
  3. Save the file and close it.
  4. Restart the Infrastructure Data Collector for your changes to take effect.

The Assets Page

Edit online

About this task

The Assets page enables you to view information about discovered assets and, in some cases, modify or refine their connection credentials. It also enables you to delete assets, subject to certain restrictions and limitations, particularly in regard to Integration Server clusters and SNMP assets. In addition, this page also enables you to suspend monitoring of selected components.

If Broker auto-discovery is enabled, brokers and related components are automatically updated for all Broker Servers, though only Brokers and Broker Servers are displayed on the Assets page.

To view the Assets page, navigate the following path in My webMethods: Navigate > Applications > Administration > Analytics > Infrastructure Components > Assets.

The primary component of the Assets page is the Discovered Assets table. This table displays all discovered SNMP assets, Integration Servers, Integration Server clusters, IBM My webMethods Servers, and Broker Servers/Brokers arranged in a hierarchical order. For Broker assets the parent Broker Server is added as a node in the tree view of assets, and all related Broker components appear beneath that node. Similarly, for SNMP assets the parent SNMP file is added as a node in the tree view of assets, and all related SNMP components appear beneath that node. The name, asset type, data collector used, connection status, and when the asset information was last updated are listed.

If a cluster enabled Integration Server is discovered, the IS Cluster asset is added as a parent node in the tree view of assets and all IS Cluster Server members appear beneath that node. Note that there are some restrictions on suspending and deleting these components as discussed below.

The Discovered Assets table provides information about each asset, as described in the table below.

Column Description
NAME Click a name to edit connection parameters for an asset. Click to expand a parent asset to view its children.
TYPE Asset type: Universal Messaging Server,Broker Server, Broker, SNMP Configuration, Integration Server, IS Cluster, or IS Cluster server, My webMethods Server, SNMP, SNMP Agent, Adabas (Deprecated), ApplinX, EntireX, Natural (Deprecated), Natural Ajax (Deprecated), MashZone NextGen (Deprecated), or Terracotta.
DATA COLLECTOR The name of the Infrastructure Data Collector associated with this asset.
Note: If you have discovered the same Integration Server asset with two or more Infrastructure Data Collectors on different JMS queues, you must delete the asset here and then create a new discovery at the Discovery page that uses a single Infrastructure Data Collector.
ENABLED The Enabled icon indicates the status of asset monitoring:
  • A green enabled icon means monitoring is enabled for all components of the asset.
  • A red suspended icon means monitoring is suspended for all components of the asset.
CONNECTION STATUS Connection status (Accepted, Refused, or Connecting) of the asset. If the status is Refused, you can move your mouse over the status indicator to view a description of the associated error.
LAST UPDATED The date/time when this asset was last updated.
ACTIONS Click Edit icon to edit communication parameters for this asset.

You can do the following on the Assets page:

  • Click the Delete button to remove selected assets. Note that the Delete button is inactive until at least one asset is selected. Deleting an Integration Server or Broker Server asset removes it from monitoring but does not remove the asset itself, nor does it remove historical data collected for the asset. Note that check boxes for individual Brokers are not available because they cannot be removed.
    Note: In the case of IS Clusters, you can only delete at the IS Cluster asset level. Deleting an IS Cluster asset will delete all IS Cluster Server assets associated with the specified IS Cluster. The IS Cluster and IS Cluster Server KPIs use a connection with any of the participating Integration Server to poll for KPI values and status, and thus at least one of the participating Integration Server must be discovered so that an Infrastructure Data Collector can establish a connection. When all Integration Servers that participate in an IS Cluster are deleted from the Assets page, the IS Cluster and IS Cluster Server KPIs will no longer be updated. Delete the IS Cluster asset from the Assets page if you no longer need to monitor this component.

    Note also that users are not notified when an Integration Server leaves an IS Cluster. When an Integration Server instance leaves a cluster, Infrastructure Data Collector is not notified of the change, and the Integration Server remains on the Assets page. As a workaround, delete the Integration Server cluster asset from the Assets page and rediscover the IS Server. Then, re-select the component for monitoring.

    Similarly, if KPI values are not being generated for an IS Cluster because the associated Integration Server asset has been suspended or deleted, then you should delete and re-discover the Integration Server asset associated with the cluster.

  • Click the Refresh button to update connection status information for discovered assets.
  • Click the Export Table button to view the contents of the Assets page as a table.

  • See Deleting SNMP Component Assets for special instructions for deleting SNMP component assets.

  • Click beside a column heading to sort the display by the information in the column.
  • Click to expand the hierarchical tree to view all children, if applicable.
  • Click the name of an asset, or click Edit icon, in the EDIT column to edit the connection parameters used to communicate with the asset. See Editing Connection Parameters for more information. Note that changes to these parameters are not reflected on the Discovery page.

Editing Connection Parameters

Edit online

About this task

You can edit connection parameters for assets from the Assets page. These parameters are a subset of the connection information specified when creating a discovery, though changes to these parameters are not reflected on the Discovery page.

Note: Connection parameters for IS Cluster and IS Cluster Server asset types cannot be edited.

To edit the connection parameters for an asset

Procedure

  1. Click the name of the asset, or click Edit icon.
    The Edit Connection Parameters dialog appears.
  2. Edit the connection parameters.

    • The following table describes the parameters that you can edit for a Universal Messaging Server asset.

      Parameter Description
      Data Collector Specifies the Infrastructure Data Collector to be used by the Universal Messaging Server.
      Host Specifies the host machine for the Universal Messaging Server.
      Server Port Specifies the communication port for the Universal Messaging Server.
      Username User ID required to login on the Universal Messaging Server.
      Password Password for logging in to the Universal Messaging Server.
      Protocol Specifies the protocol for communicating with the Universal Messaging Server.
      Client Authentication Specifies the client authentication type appropriate for the Universal Messaging Server. Currently, the only available option is “None”.

    • The following table describes the parameters that you can edit for an Adabas SOA Gateway (Deprecated), or Com-plete (Deprecated) asset.

      Parameter Description
      SSL (Optional) Select if SSL is required.
      *Username User name for logging in to the asset.
      *Password Password for logging in to the asset.

    • The following table describes the parameters that you can edit for a IBM My webMethods Server asset.

      Parameter Description
      SSL (Optional) Select if SSL is required.
      *Username User name for logging in to the IBM My webMethods Server.
      *Password Password for logging in to the IBM My webMethods Server.
      Root Context (Optional) Enter the root context if it is defined for this IBM My webMethods Server instance.

    • The following table describes the parameters that you can edit for an Integration Server asset.

      Parameter Description
      SSL (Optional) Select if SSL is required.
      *Username User name for logging in to the Integration Server. Required if displayed but not displayed if a KeyStore file is listed.
      *Password Password for logging in to the Integration Server. Required if displayed but not displayed if a KeyStore file is listed.
      KeyStore File This field appears only if SSL is selected. Specify the location of the KeyStore file.
      KeyStore Password This field appears only when KeyStore file information is supplied. Specify the password for the KeyStore file.
      KeyStore Alias This field appears only when KeyStore file information is supplied. Specify the alternate name for the KeyStore file.
      Include System Packages/Services (Optional) Select if you want to include webMethods-supplied packages and services in the data returned from the Integration Server.

    • The following table describes the parameters that you can edit for a Broker or Broker Server asset.

      Parameter Description
      Client Authentication Select the client authentication type appropriate for the Broker Server being discovered. Available options are “None”, “Basic” and “Certificate”. Note that additional fields may be displayed on the Edit Connection Parameters dialog based on your selection as explained below.
      Username User ID required to log in to the asset. Displayed only when client authentication is “Basic.”
      Password Password required to log in to the asset. Displayed only when client authentication is “Basic.”
      KeyStore File Type the name and path of the Broker Server KeyStore file. This field is displayed, and required, only when client authorization is “Certificate”.
      KeyStore Type Type the KeyStore file type. This field is displayed, and required, only when client authorization is “Certificate”.
      KeyStore Password* Type the password for the Broker Server certificate file. This field is displayed, and required, only when client authorization is “Certificate”.
      TrustStore File Type the TrustStore filename if required to identify the owner or issuer of the certificate file. This field is displayed only when either the client authorization is “Certificate” or the Encryption box is checked. If the Encryption box is checked, the field is required.
      TrustStore Type Type the TrustStore file type. This field is displayed only when either the client authorization is “Certificate” or the Encryption box is checked. If the Encryption box is checked, the field is required.

    • The following table describes the parameter that you can edit for an SNMP component asset.

      Parameter Description
      Password Password for the MIB file.

    • The following table describes the parameters that you can edit for an Adabas (Deprecated) or Natural asset.

      Parameter Description
      Username* User ID needed for secure connections to the EntireX Broker.
      Password* Password needed for secure connections to the EntireX Broker.
      Keystore FIle Name and path of the EntireX Broker KeyStore file.
      RPC User User ID needed for secure connections to the Natural RPC server.
      RPC Password Password needed for secure connections to the Natural RPC server.

    • The following table describes the parameters that you can edit for an EntireX asset.

      Parameter Description
      Username* User ID needed for secure connections to the EntireX Broker.
      Password* Password needed for secure connections to the EntireX Broker.
      KeyStore FIle Name and path of the EntireX Broker KeyStore file.

    • The following table describes the parameters that you can edit for an ApplinX or Natural Ajax asset.

      Parameter Description
      SSL (Applies only to Natural Ajax). (Optional) Select if SSL is required.
      Username* User ID needed for secure connections to the asset.
      Password* Password needed for secure connections to the asset.

    • The following table describes the parameters that you can edit for a Terracotta asset.

      Parameter Description
      *Data Collector Select the Infrastructure Data Collector to use for the discovery.
      Tip: Only one Infrastructure Data Collector can be used to monitor the same Integration Server instance on different JMS queues, so if you use multiple Infrastructure Data Collectors, be careful not to point more than one to the same Integration Server.
      *Host Enter the host name or IP address for the Terracotta Management Console. The name must be unique.
      Connection Type Select TMS or Direct as the type of an existing connection.
      *Port Enter the port number for the applicable Terracotta Management Console.
      *Group Name (Available if Connection Type is set to TMS) Enter the name of an existing Terracotta Server Array group.
      SSL (Optional) Select if an SSL connection is required.
      *TSA Name (Available if Connection Type is set to Direct) Enter the name of the relevant Terracotta Server.
      Username User ID needed to log in to the asset.
      Password Password needed to log in to the asset.

    • The following table describes the parameters that you can edit for a MashZone NextGen (Deprecated) Server asset.

      Parameter Description
      *Data Collector Select the Infrastructure Data Collector to use for the discovery.
      Tip: Only one Infrastructure Data Collector can be used to monitor the same Integration Server instance on different JMS queues, so if you use multiple Infrastructure Data Collectors, be careful not to point more than one to the same Integration Server.
      *Host Enter the host name or IP address for the MashZone NextGen (Deprecated) Server. The name must be unique.
      *Port Enter the port number for the applicable MashZone NextGen (Deprecated) Server.
      *Username User ID needed to log in to the asset.
      *Password Password needed to log in to the asset.

Deleting SNMP Component Assets

Edit online

About this task

There are several options for deleting SNMP component assets, and each has significant implications that you should be aware of before proceeding. You can delete only selected SNMP assets, or you can delete an entire SNMP Configuration node. The following list explains the results and implications of each option.

  • If you delete one or more specific SNMP assets under an SNMP Configuration node, the specified assets are removed from the Assets page, associated components are hidden on the Monitored Components page, and associated KPIs are hidden on the Analytics Overview page. Note that the KPIs are only flagged as inactive; if you rediscover the assets, the associated KPI instances are reactivated.

    If you delete an SNMP configuration, all underlying SNMP assets are selected automatically. Deleting an SNMP configuration is handled the same as deleting specific SNMP assets, meaning the configuration is removed from the Assets page, and associated components are hidden on the Monitored Components page.

    This option is appropriate if you have made no changes to the MIB file and want to delete only specific assets and leave the MIB and other related assets intact.

  • If you delete a SNMP Configuration node, all SNMP assets and related event data (including historical data) associated with the SNMP Configuration file are deleted, all associated SNMP components are removed from the Monitored Components page, and all associated KPIs are removed from the Analytics Overview page. Note that all monitored instances are actually deleted from the system, and they cannot be recovered.

    This option is appropriate if you have made changes, or have added SNMP MIB configuration types to the SNMP MIB configuration file, and want those changes to take effect.

To delete SNMP component assets

Procedure

  1. In My webMethods: Navigate > Applications > Administration > Analytics > Infrastructure Components > Assets
  2. Do one of the following in the Discovered Assets panel:
    • Select the check box beside the SNMP Configuration to delete all SNMP assets and event data associated with this SNMP MIB configuration file.
    • Select the check box beside one or more SNMP assets to delete only the selected asset(s) without deleting other assets and event data associated with the SNMP MIB configuration file.
    When you select an asset, the Delete button becomes active.
  3. Click Delete.
    A dialog is displayed asking if you want to delete the specified asset(s).
  4. Answer Yes to delete the selected assets and configurations, or No to take no action.
    Note: Deleted assets are not immediately removed from the Monitored Components page. Depending on the number of monitored components, it can take some time for deleted assets to be removed from the Monitored Components and Analytics Overview pages. As a workaround, after deleting the asset, wait a few moments before verifying that the information of the Monitored Components and Analytics Overview pages has been updated.

Suspending Monitoring

Edit online

About this task

The suspend monitoring feature enables you to suspend monitoring of any discovered assets for any period of time. This feature is particularly useful when performing system maintenance to avoid generating inaccurate data in system reports and inappropriate alerts.

To suspend asset monitoring

Procedure

  1. In My webMethods: Navigate > Applications > Administration > Analytics > Infrastructure Components > Assets
  2. Locate the asset that you want to suspend, and click the Enabled icon in the Enabled column to suspend monitoring of that asset.
    A dialog is displayed asking if you want to suspend monitoring.
  3. Click Yes to suspend monitoring of the selected asset.
    The Status column displays an Disabled icon indicating that monitoring for the asset is suspended. Rule instances that are associated with this asset will not fire while it is suspended.

Resuming Monitoring

Edit online

About this task

If you previously suspended monitoring, you can resume monitoring.

To resume asset monitoring

Procedure

  1. In My webMethods: Navigate > Applications > Administration > Analytics > Infrastructure Components > Assets
  2. Locate the asset for which you want to resume monitoring, and click the Disabled icon.
    A dialog is displayed asking if you want to resume monitoring for the selected asset.
  3. Click Yes to resume monitoring.
    The Status column displays an Enabled icon indicating that the asset is being monitored.