Maintenance outage for upgrade on Sunday, September 22

This site, docs.bmc.com, will be inaccessible for two hours starting at 8 AM CDT, Sunday, September 22, for a platform upgrade.

    Page tree
    Skip to end of metadata
    Go to start of metadata

    With Web URL Container as the selected monitor type, the Add Monitor Types dialog box enables you to configure details to monitor different Web URLs. For more information, see Configuring monitoring settings.

    Specify the following details of the Web URL you want to monitor:

    Field

    Description

    Instance name

    Enter the Web URL instance name. This is displayed on folders, graphs, lists, etc. If the instance name contains a space, it is not considered.

    Example: If "bmc software" is the instance name, it would be considered as "bmcsoftware".

    Web URLEnter the standard format of the Web URL you want to monitor. Include the protocol (HTTP or HTTPS) as part of the URL.
    Poll interval (sec)

    Specify the time interval between two consecutive statistical data polls. Default is 60 seconds. 

    Timeout (sec)Specify the time-out period for each poll of statistical data. If no data is available at the end of this interval, the system records Zero availability and proceeds with the next scheduled poll. Default is 30 seconds.
    Download full page

    Select this check box to download all the contents on the page (including images and other linked components). By default, only text data is downloaded.

    Enable monitoring

    Select/clear check box to enable/disable data monitoring for the instance. Monitoring is enabled (check box selected). 

    Content match options
    Alert on pattern not found (Positive match)

    Specify string for positive content match. The monitor generates an error if it does not find a match (for the specified string) in the page content. To specify multiple text strings, separate strings with semicolons. If a match is not found, the value of the ContentMatch attribute changes to 0, and when thresholds are set for ContentMatch, an event is triggered and the monitor generates an error.

    Alert on pattern found (Negative match)

    Specify string for negative content match. The monitor generates an error if it finds a match (for the specified string) in the page content. To specify multiple text strings, separate strings with semicolons. If a match is found, the value of the ContentMatch attribute changes to 0, and when thresholds are set for ContentMatch, an event is triggered and the monitor generates an error. 

    Source encoding

    This value is used by the Web URL monitor if it is unable to determine the character encoding of the page. Usually, the encoding information is specified in the HTTP response header and/or in the META tags of the page. In these cases, if the specified URL refers to a page that has Non-English content, it is necessary to enter the character encoding of the page. Example: Korean Encoding specified as euc-kr; Japanese Encoding specified as euc-jp or shift-jis.

    Java script
    Include internal script execution

    Select or clear the check box to enable or disable web URL monitoring that includes execution of any Java script included in the defined web URL. By default, collect internal Java script is disabled (check box cleared).

    Include external script execution

    Select or clear the check box to enable or disable web URL monitoring that includes execution of any external Java script referred by the defined web URL. By default, collection of external Java script is disabled (check box cleared).

    Execution time (ms)

    Specify the execution time. Execution time is the time taken to execute a single Java script. The monitor measures the Java script code execution time and reports the Java scripts that exceed the defined execution time. By default the execution time is 100 milliseconds.

    Valid values: 10 to 10000 milliseconds.

    Proxy
    HostEnter the name/IP address of the computer hosting the proxy server.
    PortEnter the port on which the proxy server is configured to listen for connections.
    Username

    Enter the user name used to access the proxy server. 

    Password

    Enter the password corresponding to the user name. 

    Client Certificate Details

    The KM supports monitoring of URLs that require Client Certificates by importing the Java key store database file (known as the .jks file) into the KM. 

    When you configure the URLs to be monitored that require a client certificate, those client certificates should be already imported into the .jks file so it can be used while communicating with the URLs. An authorization error will occur if the required certificates are not found in the .jks database file. 

    .jks file path

    Enter the path (along with the file name and .jks extension) where the Java key store database file is located.

    The Java key store database file must be accessible from the host where the PATROL Agent is running. BMC PATROL default account must have read permission on the directory where the .jks file is located.

    KeyStore password

    Enter a password for the Java keystore database file. This password is used by the KM to open the java keystore database (aka .jks file).

     
    Add to List

    To add the Web URL to the list, click Add to List button.

    Modify Selection

    To save the changes made to the Web URL already added, click Modify Selection button.

    Remove from List

    To remove the selected Web URL from monitoring, click Remove from List, button.

    List Web URLA list of all configured Web URLs is displayed here.

    After you add the Web URLs, enter the following details in the Administration section: 

    FieldDescription
    Root application display nameSpecify the display name of the root application. By default, the root application display name is Web URL.
    File base policy configurationSelect/clear the check box to configure the Web URLs from a file. The file is located at %PATROL_HOME%\WUM\Conf\ImportInstances\ImportInstances.txt, on the server where PATROL Agent is running.
    Enable device mappingSelect/clear check box to enable/disable device mapping. Enabling device mapping consolidates Web URL monitoring at device level. By default, device mapping is enabled (check box selected).
    Enable debugSelect/clear check box to enable/disable debugging. The log files are located at %PATROL_HOME%\WUM\logs,on the server where the PATROL Agent is running. By default, the debug is disabled (check box cleared).
    JAVA_HOME

    Enter the complete path of the Java home directory if you are not using the JRE that is installed with the PATROL Agent.

    Example:

    • (Windows) - If the JRE files reside at C:\Program Files (x86)\Java\jre8\bin\java.exe location then specify the path as C:\Program Files (x86)\Java\jre8
    • (Unix/LINUX) - If the JRE files reside at /usr/java/jdk1.8.0_65/bin/ location then specify the path as /usr/java/jdk1.8.0_65

    After adding all relevant hosts, click the Close button. Then click the Save button in the Add Policy dialog box.

    • No labels

    9 Comments

    1. can we get specifics on the Collector.Properties file?  What are the definitions of these attributes?  

      debug=0
      ConnectionPoolMax=2
      CommandTimeout=60
      SetMaxThreads=1000
      SetMinThreads=100
      DebugFileName=WUM_JavaCollector.txt
      ConnectionPoolMin=1
      ConnectionTimeout=60
      OperationTimeout_InSec=60

      Should these be altered if we are doing a large amount of WUM from a single Patrol Instance?

       

       

    2. Can we get an expansion or examples on configuring URLs from a file?

    3.  

    4. In the "Content Match options" portion of the configuration, there are two sections - Alerts on pattern not found (Positive Match) and Alert on pattern found (Negative Match). In both these sections it is mentioned that the value of "Availability" attribute is changed to 0 when the match is found/not found. This is incorrect. The parameter "Availability" does not change depending on the Content Match. The Parameter that changes the value and triggers an alert is ContentMatch instead.

    5. Hello,

      I think that the explanation of "Positive match" and "Negative match" is confusing and somethings are wrong. 

      After doing some tests, I concluded this:

      1.- If the string considered in the "Positive Check" is found, is considered as OK (value 0 = False). If not found, is considered as "not Ok" (value 1 = True).

      2.- If the string considered in the "Negative Check" is found, is considered as "not Ok" (value 1 = True). If not found, is considered as "Ok" (Value 0 = False).

      So:

      The true/flase terminology is confusing.

      The documentation is wrong about "Positive match" and "Negative Match", as it says the opposite of what really happens.

      1.  



    6.  

      1.  

      2.