JDBC Log Source Parameters for Microsoft Operations Manager
If JSA does not automatically detect the log source, add a Microsoft Operations Manager log source on the JSA Console by using the JDBC protocol.
When using the JDBC protocol, there are specific parameters that you must use.
The following table describes the parameters that require specific values to collect JDBC events from Microsoft Operations Manager:
Table 1: JDBC Log Source Parameters for the Microsoft Operations Manager DSM
Log Source Type
Microsoft Operations Manager
Log Source Identifier
Type a name for the log source. The name can't contain spaces and must be unique among all log sources of the log source type that is configured to use the JDBC protocol.
If the log source collects events from a single appliance that has a static IP address or host name, use the IP address or host name of the appliance as all or part of the Log Source Identifier value; for example, 192.168.1.1 or JDBC192.168.1.1. If the log source doesn't collect events from a single appliance that has a static IP address or host name, you can use any unique name for the Log Source Identifier value; for example, JDBC1, JDBC2.
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 SDKEventView as the name of the table or view that includes the event records.
Type TimeStored as the compare field. The compare field is used to identify new events that are added between queries to the table.