A.20 Microsoft Operations Manager (MOM)

Table A-20 Microsoft Operations Manager (MOM) Adapter Properties



Alarm Columns

A comma-separated list that determines which alarm columns display and the order in which the alarm items display (date/time, rule, etc.) in the Alarms view. The default list is Source, RepeatCount, and State.

These alarm columns are added to the base alarm properties such as Severity, Element, and so on.

Configuration File

This file is for SQL queries and column strings. The default file name is /OperationsCenter_install_path/database/msmomConfiguration.xml. If a different file name is specified but does not exist, it is created upon adapter startup. If the configuration DTD file does not exist in the directory, then it is written there when the adapter is started.

You might need to adjust the Severity Remappings (Numeric) adapter property appropriately for the MOM 2005 or MOM 2007 severity mappings.

Configuration Version

The database version; can be either MOM2005 or MOM2007 and determines the properties to use from the configuration file.

Database Hostname

The name of the SQL server on which the MOM database is installed.

Database Login ID

The login ID for the adapter to connect to the database. The default is sa.

Database Name

The name of the database that stores the MOM repository. The default is Onepoint for MOM and OperationsManager for SCOM.

Database Password

The password that corresponds to ID specified in the Database Login property.

Database Port

The port on which the SQL Server listens for database connections. The default is 1433.


SQL Server provides authentication based on Windows accounts and a named SQL server login ID and password. If SQL Server is configured for Windows Only authentication mode, then you must provide the domain name as well as the login ID and password in the adapter properties.

If SQL Server is configured for SQL Server and Windows authentication mode, then providing the domain name is optional. Either provide the user name, password, and domain in the adapter properties, or provide the SQL login ID and password and leave the domain empty.

Elements Timeout

If there are no open alarms and the element’s condition hasn’t changed in the last n seconds, and if the element has no children, then the element disappears from the display. If another alarm is generated for this element, then it reappears. The default is -1, elements are never removed even if they have no condition changes or alarms. Set the Elements Timeout property value using one of the following logic:

ElementsTimeout < 0: Never time out.

ElementsTimeout = 0: Time out immediately.

ElementsTimeout > 0: Time out after specified time expires.

If set to 0 or a number greater than 0, the initial population of computers is not performed at adapter start up; therefore, the adapter does not show any elements without alarms.

Event Viewer Exec Command

Command used to start the MS Windows Event Viewer. If no value is specified, the following command is used:

cmd.exe /C eventvwr.exe

The MS Windows Event Viewer can only be run on client machines running MS Windows. The Event View might display “access or permission denied” message if the Windows user does not have sufficient permissions to connect to the remote computer. If this occurs, contact your Windows Administrator.

Hierarchy File

A file in the /OperationsCenter_install_path/database directory that contains an XML description of the element hierarchy to build below the adapter element. The default is examples/msmom.xml.

Polling Interval (Seconds)

The number of seconds between queries for new alarms or re-queries for updating existing alarms. The default is 5.


A script that executes if the adapter fails for any reason. For example, the script can print the reason for the failure as msg using log.info(msg).


A script that executes when the adapter initializes.


A script that executes when the adapter starts, either manually or automatically when the Operations Center server starts.


A script that executes after manually stopping the adapter.

Seed File

The seed file by default is blank, so there are no seed alarms. If a file name is provided and it does not exist in the directory given (the base directory is the /OperationsCenter_install_path/database directory), then an example file is created when the adapter is started. If the seed file DTD file does not exist in the directory, then it is written there when the adapter is started.

Severity Remappings

It is necessary to translate the severity levels in MOM to the severity codes used in Operations Center. Operations Center allows the following severities:

  • OK (usually green)

  • INFORMATIONAL (usually blue)

  • MINOR (usually yellow)

  • MAJOR (usually orange)

  • CRITICAL (usually red)

  • UNKNOWN (usually gray)

The MOM severity definitions are discovered at startup from the Onepoint.ResolutionState table. This mapping process uses the contents of the State column. The process requires mapping a MOM state (such as Success) to a Operations Center severity (such as OK). For example:


The default mappings are:

Success=OK:Information=INFORMATIONAL:Warning=MINOR:Error=MAJOR:Critical Error=CRITICAL:Security Breach=CRITICAL:Service Unavailable=CRITICAL

For MOM 2005:


For MOM 2007, change to:


Stylesheet File

The stylesheet file in the /OperationsCenter_install_path/database directory that applies to the HierarchyFile as a style markup to produce the final output.


Specifies a socket timeout, in seconds, for database communications. If there is a faulty network connection, the database communications times out after this period. Default is 0.

If database queries are running longer before results are returned, it is best to set a high enough socket timeout to alleviate the risk of the timeout being triggered while results are still being gathered on the database server. However, we recommend that you don’t set the socket timeout value too high because if the connection is unexpectedly dropped, the next query might not be executed until the connection is re-established and the timeout value is reached.

Use Alarm Times For Condition Changes

The date/time stamp to use for all alarm data stored by the Operations Center Data Warehouse. If true, the alarm’s date/time stamp is used. If false, the date/time stamp of when the Operations Center server received the alarm is used. The default is true.

Alarm history is stored based on the alarm time rather than alarm receipt time. Also, for SLA metric data based on alarm properties, the property values are recorded based on the alarm time instead of the alarm receipt time. Note that recording historical condition data for historical alarms is not supported.