Infrastructure Management Software Blog

New SiteScope Adapter version 2.0

A guest post from Alfred Hermann, Operations Center Technical Marketing Manager.
- Peter


You probably know what the SiteScope Adapter is used for. Its purpose is to glue together HP SiteScope with HP Operations Manager to combine agent-based with agent-less monitoring. It offers the following capabilities:



  • You can forward SiteScope alerts into HP Operations Manager to manage from a single operations console.

  • The OM agent discovers SiteScope configuration and monitor groups, and publishes discovered information to the Operations Manager service maps.

  • You can launch SiteScope tools in-context from the OM console for further diagnostics of the environment.

  • Multiple SiteScope servers are supported (you have to install an OM agent on each SiteScope server).


In the first version of the adapter all alerts originating from SiteScope would relate to a single node in the OM Nodes / Node Group / Node Bank environment. Even though the alerts come from a variety of nodes monitored in an agent-less fashion, their status contribute only to a single element in the console.


This has changed with version 2 of the SiteScope adapter: SiteScope events can now explicitly be mapped to their respective nodes rather than consolidated altogether to the SiteScope server. The resulting value is obvious: The operator immediately notices where the problems are. No longer digging through some more event details…


In addition, interoperability with Operations Manager i  has been improved by setting a CI as resolution hint for OMi. Remember, OMi relates events to CIs in the UCMDB, and any resolution hint is mostly appreciated.


The new SiteScope Adapter 2.0 is available with HP Operations Manager version 8.16, alternatively as patch OMW_00039. For the UNIX based OM management servers you need OMU version 9.x. 


For HP Operations Center, Alfred Hermann.

Extending out-of-the-box integration capabilities of HP software products with APIs

A guest post by Alfred Hermann, technical marketing manager for Operations Center.
- Peter


I was looking at Closed Loop Incident Process (CLIP) and wanted to introduce a new member of the HP operations family of products, Operations Manager i (OMi).  My goal was to use OMi as the only operational console, as I hate to switch between consoles for day-to-day operational tasks.


It quickly became apparent that there are many out-of-the-box integrations with HP Service Manager, but no direct integration between OMi and Service Manager. Since OMi is still relatively new, it does not contain some of the integration adapters. However, there is an existing integration between HP Operations Manager and HP Service Manager, and as OMi sits on top of HP Operations Manager, I explored some of the existing OM interfaces hoping to improve the situation.


And this is what I wanted to achieve: OMi has some fancy capabilities around topology based event correlation (TBEC), and thus can identify cause/symptom relationships between events. The existing “scauto” based integration between HP Operations Manager and HP Service Manager, however, will not exchange this important piece of information, a user at the Service Manager console is unable to see how events that have become incidents are related.


What I found is that HP Operations Manager (in my case the Windows management server version) has a wealth of WMI interfaces. Some of them can be used to investigate OM messages as they are stored on the OM for Windows management server. You can walk through the set of CMAs that are attached to an OM message, and create new annotations. In my case I was looking for a particular CMA “CauseEventId” being added to the message, and generated out of that an annotation. The interesting thing is that annotations are synchronized between Operations Manager and Service manager, and as a result of adding a small VB script and a WMI policy I was able to synchronize causal message relationships.


This leads me to the question how widely APIs are used with eg. HP Operations Manager for Windows? Please comment if you have been able to extend the product’s out-of-the-box capabilities by using the provided interfaces.


For HP Operations Center, Alfred Hermann.


Get the latest updates on our Twitter feed @HPITOps http://twitter.com/HPITOps


Join the HP OpenView & Operations Management group on LinkedIn.

Search
Showing results for 
Search instead for 
Do you mean 
HP Blog

HP Software Solutions Blog

Featured


Follow Us
Labels
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.