Many organizations find it difficult to consolidate events from increasingly complex IT infrastructures into a single event stream. They have many best-of-breed tools but lack the overall visibility to triage events and prioritize responses based on common information.
Operations Bridge and its powerful Operations Connector (OpsCx, previously known as BSM Connector) solves this challenge. With OpsCx it’s very easy to consolidate IT events from all of your domains into Operations Bridge. There the consolidated view, shared across multiple domain “towers,” helps your IT operators quickly identify the causes of IT incidents.
Because of the business critical function that the Operations Bridge provides it is typically deployed as a high-availablity solution. The OMi high availability concept consists of a load balancer, two or more gateway servers and a primary and backup data processing server. This HA concept assures high availability for your Operations Bridge.
Integrations to domain managers such as Microsoft System Center Operations Manager (SCOM) or Zenoss are implemented using an Operations Connector system that can gather and receive data using a variety of technologies. For example, an Operations Connector can query databases and read data from logfiles and it can also receive data from domain managers via SNMP traps or a REST web service.
These Integrations are often business critical as well. If an integration is not working for an extended period, operators of the Operations Bridge lose their overall visibility and can no longer identify the true cause of IT incidents.
Therefore it’s very important to assure high-availability for integrations as well.
The new OMi 10.11 Operations Connector cluster concept provides that!
With this new cluster concept it’s now possible to group two or even more OpsCx systems together into a logical cluster – no special hardware required - and to deploy several integration packages to this cluster. The cluster nodes then distribute the integration packages to all nodes and decide among themselves where an integration is started:
In a setup with two nodes and two integration packages each cluster node handles one integration package:
Metrics collected by one Operations Connector as well as important state information (when did the last data retrieval occur) are synchronized to all other Operations Connector systems.
If one cluster node goes down or can’t be reached anymore because of network problems, then another node takes over the integration package automatically:
For an Operations Bridge user this failover is transparent. The integration of topology, metrics and events continues and as all metric data is kept on all nodes, an operator is able to query all collected metrics using OMi’s Performance Dashboard at any time, without having to know where an integration package is currently running.
Once the OpsCx1 system is available again, the package distribution mechanism will make sure that integration packages are distributed equally again among the nodes.
To learn more about this Operations Connector cluster concept, check out the help topic “Configuring Operations Connector High Availability Policies” in the OMi 10.11 online help or in the OMi Administration Guide.
OMi 10.11 comes pre-loaded with a number of Management Packs that you can try out without the hassle of getting management pack software or evaluation license.