News
Perth, Australia
+ (61) 417713124
prosolutions@gavinsoorma.com

Installing the 12c Cloud Control plug-in for Microsoft SQL Server Database

  • Posted by Gavin Soorma
  • On June 14, 2012
  • 1 Comments
  • 12c, cloud control, plug-in, sql server

 In an earlier post I had described how to use the Self Update feature of 12c Cloud Control to deploy the 12c management agent on a Windows 64 bit server.

Let us now see how to can deploy the 12c Plug-in on the same Windows server to enable us to monitor a Microsoft SQL Server 2008 environment running on the same Windows server.

 A plug-in is an additional component which can be plugged into an existing 12c Cloud Control installation in order to extend the default out-of-the-box management and monitoring capabilities.

 The plug-ins as well as updates to the plug-ins are released from time to time and these plug-ins enable us to monitor both Oracle as well as non-Oracle database and applications.

 Deploying a plug-in essentially consists of the following:

 a)     Download the plug-in archive and store it in the Software Library configured on the OMS host

b)    Deploy the plug-in first to the OMS host which manages and monitors the target pertaining to the particular plug-in type. In this example the plug-in is Microsoft SQL Server.

c)     Update the OMS repository with metadata information about the plug-in

d)    Deploy the plug-in on the Management Agent

 Note that in this example we will be using the Offline Patching mode to update the Software Library.

From the Setup menu, choose Extensibility, then select Plug-ins.

 

From the Actions drop-down menu, select Check Updates 

 

This will take up to the Self Update page. Note our Connection Mode is Offline

Click on Plug-In

 

 

The Plug-in Updates page will show us all the updates available for the various plug-ins. We can see that there is a newer version of the plug-in which is available for Microsoft SQL Server Database.

Select that line and click on Download

 

 

Since we using the Offline Patching mode, we need to download the file using the URL shown and then copy that file to the OMS host.

We will then use the EMCLI to run the command to import the plug-in metadata into the OMS rtepository.

 

 

From the OMS $ORACLE_HOME/bin run the following emcli commands:

[oracle@kens-oem-prod bin]$ ./emcli login -username=”sysman” -password=”xxx”
Login successful
[oracle@kens-oem-prod bin]$ ./emcli import_update -omslocal -file=”/u01/stage/p14047236_112000_Generic.zip”

Processing update: Plug-in – Microsoft SQL Server Plugin for monitoring SQL Server database from Enterprise Manager
Operation completed successfully. Update has been uploaded to Enterprise Manager. Please use the Self Update Home to manage this update.

 

We will now see that  the plug-in status has now changed to Downloaded from Available for Microsoft SQL Server Database

 

Click on Plug-in

 

Now click on Deploy On and select Management Servers…

 

The Microsoft SQL Server Database updated plug-in will now be deployed on the Management Server.

 

 

 

 

We can monitor the progress of the plug-in deployment on the Management Server – click on the Show Status button.

 

 

Once the deployment job is completed, we can see that the column “On Management Server” has been populated with the Microsoft SQL Server Database plug-in details.

 

 

We now have to deploy the plug-in on the Management Agent.

Click on Deploy On drop-down menu and select Management Agent …

 

 

 

 

 

 

Select the Management Agent where this plug-in needs to be deployed.

Click on the Add and select the Management Agent and its associated Operating System.

Click on Continue

 

Click on Next

 

 

Click on Deploy button

 

 

 

 


Click on Setup, Add Targets, Add Targets Manually

Select the option Add Non-Host Targets by Specifying Target Monitoring Properties

In the Target Type field, select Microsoft SQL Server.

In the Monitoring Agent field , select the agent deployed on the Windows server hosting the SQL Server instance to be monitored.


Here we will need to now enter the SQL Server credentials for the sa database user account as well as the TCP/IP Port number for SQL Server

Click on the Test Connection button

 

 

From the Targets menu, Select All Targets. We can now see the SQL Server target we configured earlier.

 

 

 

 

1 Comments

Almin Valyani
  • Dec 20 2017
server monitoring tool Thanks a lot for the great article. I have a quick question. I have 40 tables in my source

Leave Reply

Your email address will not be published. Required fields are marked *