How to Create an OLE DB Data Source Monitor
Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1
Use the following procedure to create an OLE DB Data Source object type with the Add Monitoring Wizard. An OLE DB Data Source can be used to monitor any database, including those running on operating systems other than Windows. You can also run queries against the database to monitor performance.
If you have created an OLE DB monitor by using a previous release of Operations Manager 2007, before you can save any changes to that monitor, you must upgrade it to the new template. To do this, open the Properties for the OLE DB Monitoring template. The template will then be automatically upgraded. Click OK at the end of the upgrade process. You can now edit and save all OLE DB monitors.
To start monitoring an OLE DB Data Source with Operations Manager 2007
Start the Add Monitoring Wizard.
For information about starting the Add Monitoring Wizard, see How to Start the Add Monitoring Wizard in Operations Manager 2007.
On the Select Monitoring Type page, select OLE DB Data Source, and then click Next.
On the General Properties page, do the following:
Type the Name for the object, such as Operations Manager database.
Optionally, type the Description for the object.
Select a Management pack from the list or click New to create a management pack with the Create a Management Pack Wizard.
The object type will be added to the specified management pack, therefore only unsealed management packs are listed. By default, when you create a management pack object, disable a rule or monitor, or create an override, Operations Manager saves the setting to the Default Management Pack. As a best practice, you should create a separate management pack for each sealed management pack that you want to customize, instead of saving your customized settings to the Default Management Pack. For more information, see Default Management Pack.
On the Test OLE DB Source Settings page, click Build to create a connection string.
Select a Provider from the list, such as Microsoft OLE DB Provider for SQL Server.
Type the Computer or device name, such as MS1.corp.net\Instance1.
Type the name of the database, such as OperationsManager.
Optionally, select Use Simple Authentication RunAs Profile created for this OLE DB data source transaction.
The OLE DB connection string for the previous example is as follows: Provider=SQLOLEDB;Server= MS1.corp.net\Instance1;Database=OperationsManager;Integrated Security=SSPI. For more information about OLE DB connection strings, see http://go.microsoft.com/fwlink/?LinkId=70748.
If you want to run a query against the database, select Query to execute and type the query in the text box. Specify a time-out period for the query. Click Test to validate the query.
If you are using the Simple Authentication Run As profile, when you click Test, you will receive an error message (“Illegal token, $RunAs, is contained in task overrides”) . If you have configured the Run As profile correctly (as described in How to Create and Configure a Run As Profile in Operations Manager 2007), you will have full OLE DB monitoring functionality, despite not being able to test the query.
If you see an HRESULT error message when you click Test, or if you see an HRESULT error message in the Operations console after you create the OLE DB monitor, you may have made a mistake when you typed the connection string or the query. Check these and try again.
Optionally, specify the timing thresholds for the connection, query, and fetch time. Specify the thresholds, in milliseconds, for both error and warning alerts. Click Next.
Select one or more computers to act as watcher nodes.
Set the time period for running the query.
On the Summary page, review the settings, and click then Create.