I recently was called on to set up SQL Server monitoring in my OEM system in my lab. The OEM server is Oracle Linux 7 and my SQL Server platform is Windows 2016. It turns out that with only a few bumps, it is possible to install an OEM Windows agent from a Linux OEM platform. Since the OEM installation process uses ssh I had to add Cygwin to Windows.
Cygwin is downloaded from www.cygwin.com/install.html. Be sure to download the 64-bit version. The Cygwin installer is downloaded and will automatically download and install the packages from the internet. Unfortunately, openssh is not part of the default installation, so you will have to specifically select it.
When I installed Cygwin, I used the default installation directory of c:\cygwin64. This turned out to cause a little bit of an issue (more about this later). When you get to Select Packages, expand net, scroll down and change openssh from “skip” to “8.2p1-1”.
Once Cygwin is installed, setup SSH for incoming connections.
Open the Cygwin64 Terminal and run the following commands:
$ mkpasswd –local > /etc/passwd
$ mkgroup –local > /etc/passwd
When the dialog gets to the part
“*** Query: Enter the value of CYGWIN for the daemon:” this will be the name of the Windows service to be created. I just called mine CYGWIN.
In Windows Services, select the CYGWIN cygsshd service and start it.
You can now log in to the Windows server from your OEM Cloud Control server via SSH to test the connection.
Now, add the OEM agent by using the push method from the OEM 13c Cloud Control console.
Note: This operation initially caused a path error when trying to install the agent. This is because I used the default location of c:\cygwin64 for my Cygwin installation.
On the OEM OMS server copy and save the file: /u01/app/oracle/Middleware/oui/prov/resources/ssPaths_msplats.properties
Then, edit the original file. You will see that the paths file is expecting Cygwin to be in c:\cygwin. Make a global edit and change “c:\cygwin” to “c:\cygwin64”.
The agent can now be installed correctly and without a problem.
In the next installment, I’ll cover how to add SQL Server monitoring to OEM.