Microsoft Operations Manager
The Microsoft Operations Manager DSM for JSA accepts Microsoft Operations Manager (MOM) events by polling the OnePoint database that allows JSA to record the relevant events.
Before you configure JSA to integrate with the Microsoft Operations Manager, you must ensure that a database user account is configured with appropriate permissions to access the MOM OnePoint SQL Server database. Access to the OnePoint database SDK views is managed through the MOM SDK View User database role. For more information, see your Microsoft Operations Manager documentation.
Make sure that the firewall rules are not blocking the communication between JSA and the SQL Server database that is associated with MOM. For MOM installations that use a separate, dedicated computer for the SQL Server database, the SDKEventView view is queried on the database system, not the system that runs MOM.
To configure JSA to receive MOM events:
- Click the Admin tab.
- On the navigation menu, click Data Sources.
The Data Sources pane is displayed.
- Click the Log Sources icon.
The Log Sources window is displayed.
- From the Log Source Type list, select Microsoft Operations Manager.
- From the Protocol Configuration list, select JDBC.
The JDBC protocol parameters appear.
- Configure the following values:
Table 1: Microsoft Operations Manager JDBC Parameters
Log Source Identifier
Type the identifier for the log source. Type the log source identifier in the following format:
<MOM Database>@<MOM Database Server IP or Host Name>
<MOM Database> is the database name, as entered in the Database Name parameter.
<MOM Database Server IP or Host Name> is the host name or IP address for this log source, as entered in the IP or Host name parameter.
From the list, select MSDE.
Type OnePoint as the name of the Microsoft Operations Manager database.
IP or Hostname
Type the IP address or host name of the Microsoft Operations Manager SQL Server.
Type the port number that is used by the database server. The default port for MSDE is 1433.
The JDBC configuration port must match the listener port of the Microsoft Operations Manager database. The Microsoft Operations Manager database must have incoming TCP connections that are enabled to communicate with JSA.
If you define a Database Instance when MSDE is used as the database type, you must leave the Port parameter blank in your configuration.
Type the user name that is required to access the database.
Type the password that is required to access the database. The password can be up to 255 characters in length.
Confirm the password that is required to access the database. The confirmation password must be identical to the password entered in the Password parameter.
If you select MSDE as the Database Type and the database is configured for Windows, you must define the Window Authentication Domain. Otherwise, leave this field blank.
Optional. Type the database instance, if you have multiple SQL server instances on your database server.
If you use a non-standard port in your database configuration, or block access to port 1434 for SQL database resolution, you must leave the Database Instance parameter blank in your configuration.
Type SDKEventView as the name of the table or view that includes the event records.
Type * for all fields from the table or view.
You can use a comma-separated list to define specific fields from tables or views, if you need it for your configuration. The list must contain the field that is defined in the Compare Field parameter. The comma-separated list can be up to 255 alphanumeric characters in length. The list can include the following special characters: dollar sign ($), number sign (#), underscore (_), en dash (-), and period(.).
Type TimeStored as the compare field. The compare field is used to identify new events added between queries to the table.
Start Date and Time
Optional. Type the start date and time for database polling.
The Start Date and Time parameter must be formatted as yyyy-MM-dd HH:mm with HH specified by using a 24-hour clock. If the start date or time is clear, polling begins immediately and repeats at the specified polling interval.
Use Prepared Statements
Select this check box to use prepared statements.
Prepared statements allow the JDBC protocol source to set up the SQL statement one time, then run the SQL statement many times with different parameters. For security and performance reasons, it is suggested that you use prepared statements.
Clearing this check box requires you to use an alternative method of querying that does not use pre-compiled statements.
Type the polling interval, which is the amount of time between queries to the event table. The default polling interval is 10 seconds.
You can define a longer polling interval by appending H for hours or M for minutes to the numeric value. The maximum polling interval is 1 week in any time format. Numeric values that are entered without an H or M poll in seconds.
Type the number of Events Per Second (EPS) that you do not want this protocol to exceed. The default value is 20000 EPS.
Use Named Pipe Communication
Clear the Use Named Pipe Communications check box.
When you use a Named Pipe connection, the user name and password must be the appropriate Windows authentication user name and password and not the database user name and password. Also, you must use the default Named Pipe.
Database Cluster Name
If you select the Use Named Pipe Communication check box, the Database Cluster Name parameter is displayed. If you are running your SQL server in a cluster environment, define the cluster name to ensure Named Pipe communication functions properly.
Selecting a value greater than 5 for the Credibility parameter weights your Microsoft Operations Manager log source with a higher importance compared to other log sources in JSA.
- Click Save.
- On the Admin tab, click Deploy Changes.