Home  Administration > Data Collector Administration > SiteScope Administration > External Integrations and Functionality > Mercury Self-Alert Monitor > Mercury Self-Alert Monitor Templates



Mercury Self-Alert Monitor Templates

The Self-Alert monitors check the Mercury Business Availability Center components, according to the definitions in the *.mset files, located in the <SiteScope root directory>templates.sets.topazWatchdog directory.

The Mercury Self-Alert Monitors monitors can be customized either by changing one of the monitor templates or by adding monitor templates, and assigning them to a specific Mercury Business Availability Center service.

The file which maps monitor templates for each Mercury Business Availability Center service is named defaultMercury Application ManagementWatchdogMonitorSets.config, and is located in the <SiteScope root directory>\classes directory. This file is copied to the <SiteScope root directory>templates.sets.topazWatchdog directory with the name topazWatchdogMonitorSets.config the first time that SiteScope starts.

The following is an example of an entry in this file:

_descriptionForUi=Alert Server
_topazHostTypeMask=128
_monitorSets_Windows=Common.mset,Mercury Application ManagementSupervisor.mset,AlertServer.mset
_monitorSets_Unix=CommonUNIX.mset,Mercury Application ManagementSupervisorUNIX.mset,AlertServerUNIX.mset

where:

_descriptionForUi is a description of the specific Mercury Business Availability Center service

_topazHostTypeMask is an internal ID of the specific Mercury Business Availability Center service. You must not change this value.

_monitorSets_Windows is a comma separated list of Monitor Set files which are associated with this Mercury Business Availability Center service on a Windows platform (the specified monitor sets must reside in the <SiteScope root directory>templates.sets.topazWatchdog directory).

_monitorSets_UNIX is a comma separated list of monitor set files that are associated with this Mercury Business Availability Center service on a UNIX platform (the specified monitor sets must reside in the <SiteScope root directory>templates.sets.topazWatchdog directory).

Important: Before making any direct modifications, make a complete backup of the SiteScope folders. After making any modifications, test that your monitors, alerts, and reports are functioning correctly before returning them to a production environment.

Configuring Monitor Solution Templates

You can replicate monitors across multiple servers or locations using the SiteScope solution template functionality. You work with Mercury Self-Alert Monitor templates in the same way as you work with SiteScope monitor solution templates.

To enable working with Mercury Self-Alert Monitor monitor sets:

  1. In the <SiteScope root directory>templates.sets.topazWatchdog directory, choose the templates with which you want to work. Monitor template files have the .mset extension.
  2. Each template includes a list of variables, their descriptions and values, and the monitors that are configured by the template. For example, the Mercury Business Availability Center Centers Server template includes the variable $TOPAZ_HOST_NAME$. Its description is Server_to_monitor (the underscores do not appear in the SiteScope page.

    Copy the template .mset files to the <SiteScope root directory>templates.sets directory.

  3. To use the templates, click the Mercury Self-Alert Monitor group in the SiteScope main view, then click Add Monitor Set. The Add Monitor Set to Group page opens. Select the monitor template that you want to configure, and click Configure.
  4. Click Submit to save the new monitor template.



Copyright 2006 Mercury Interactive Corporation