Important:   For the newest version of this integration, please see Integration ID #782

Description

Micro Focus Business Service Management Connector for Zenoss enables you to establish a link between the Zenoss network monitoring solution and Micro Focus Business Service Management (BSM) Operations Management.

The Connector for Zenoss is an add-on for the Micro Focus BSM Connector, providing the following Zenoss specific functionality:

  • Event synchronization between Zenoss and BSM
  • Topology synchronization between Zenoss and BSM

This functionality enables you to consolidate management data from Zenoss environments into a Micro Focus BSM Operations Management solution.

 

The HP Business Service Management Connector for Zenoss integration consists of three parts:

HPBSMCollector
Daemon that collects data from Zenoss (displayed as hpbsmcollector in Zenoss).

The HPBSMCollector is a daemon that integrates into the Zenoss daemons list so that it is started and stopped with Zenoss. The HPBSMCollector daemon  executes the following two tasks:

  • Event collection
  • Topology object collection

In the same way as most other Zenoss  daemons, the HPBSMCollector periodically sends a heartbeat event  to indicate that it is still running. If three heartbeats are missed, Zenoss creates an event informing that the daemon might have stopped.

Event and Topology Policies and Topology Mapping Rules
Rules that map data into the BSM common data formats.

Event data is mapped to the BSM conform form using an XML logfile policy. The policy also sets the drilldown URL for each event.
Topology objects are mapped to the RTSM using the local topology synchronization component provided by the BSM Connector. The mapping rules map the following CI Types: nt, unix, cpu (optional, if configured), file_system (optional, if configured), interface, node, and ci_collection. 

Back Synchronization Scripts
Scripts that enable the back synchronization of event information to Zenoss. If an event is closed in HP BSM Operations Management, it is also closed in Zenoss.

The data available on the BSM server is synchronized back to the Zenoss Server using the OMBackSync.pl and OMBackSync_Zenoss.pl Perl scripts. These scripts generate HTTP requests, using a JSON file to define attributes of the "close request" that is sent to Zenoss. It is recommended that you use HTTP/JSON requests to perform this type of tasks.

Event & topology data is transferred to the BSM Connector system using the Generic Integrator (GenInt).
 

 

General

Leading Product:
Operations Bridge Manager (OMi)


Secondary Product:
Zenoss

6/11/2018

Support Matrix

  Zenoss
Operations Bridge Manager (OMi)
Comments:   requires BSM Connector 9.21 or higher
SupportedSupported (see comments)Not Supported