Documentation on OBM/OMI

By: Muhammad UMER

Multilynx Islamabad.
Friday, December 14, 2018
Preface:

Basic and advanced learning of (Operational Bridge Manager),

In easy wording, examples and visual help.
Chapter 1 OBM Introduction

Single view of operations data

Get insight about issues instantly and over time by using easy-to-understand HTML-5 dashboards that summarize
service health.

Advanced correlation
Unify the data from your existing management tools. Apply time, stream, and topology-based analytics with
enriched rules to simple and runtime service models.

Gamification and collaboration methods

Increase your ROI by rewarding operators for efforts to solve issues. Support development and sharing of best
practices for optimal results, and use exploration map to optimize progress and ROI.

Dynamic monitoring and automation

Monitor and automatically respond to events with adjustments—including application onboarding—based on
changes in the topology by using cross-IT domain reporting and forecasting that leverages a dynamic model of IT
resources
Management packs and connectors
Apply monitoring automation to agent-based management packs, and leverage Micro Focus and third-party
connectors to manage more than 100 IT application and infrastructure domains.

Sense your environment

Sense the state of the IT environment, Consolidate 110+ integrations into a single pane of glass. For us, the story is
tying together all of the disparate systems. Micro Focus OMi—the OpsBridge—is the only tool I know that lets you
do that, and automate management from a single pane of glass.
Jay Rooney – SYSTEMS ANALYST III
Vancity Credit Union
Chapter 2 Operation Agent Policies
1. Policies Introduction
2.Management Templets
3.New Policies types
4.Policies Examples

Polices Introduction

Operation agents are installed on the nodes you want to monitor in your IT environment. Nodes
on which Operational Agents are installed are called monitored nodes. Now we must specify
how and what needs to be monitored on our node (windows Server), for that purpose we use
monitoring policies. Polices contain information related the CI (RAM, Applications, LOG etc..)
to be monitored, thresholds on which event needed to be generated e.g. when CPU reach 30%
generate event and send it to OBM/OMI. Some of predefined, out of the box management
templets are also provided by OBM/OMI.

Management Templates

Management templets are group of policies designated to monitors specific group of CIs’ in
monitored node e.g. CPU monitor Management template may contain policies CPU threshold,
RAM threshold, DISK usage etc. Some of predefined, out of the box management templets are
also provided by OBM/OMI.

New Policy Types

Although OBM provide most of the commonly used policies by default but you can define your
own policy, depending on your need you can choose your own policy type and create policy
accordingly.
1.Creating CPU Threshold Policy.
Note Category is not important yet!
2.Creating Ram Monitoring Policy
3.Windows service monitoring Policy
If you want to make copy of same rule
4.Windows Process Monitoring Policy.
5.Log Entry monitoring file.
Chapter 3 RTSM
Configuration Items CI’s

A configuration item (CI) is any service component, infrastructure element, or other item that needs to
be managed in order to ensure the successful delivery of services.
Each CI has several characteristics:
 A classification, or type, which indicates what kind of item it is.
 Attributes, which vary by classification and describe the characteristics of the individual CI.
 A status value, which represents the CI's state in the lifecycle used for CIs of this classification.
 Relationships, which indicate how the CI is related to other CIs.
 An owner, the person who is responsible for the CI.

1.Creating new CI.

2.Creating Relationships Between CIs.
Perspective Views
1.Intoduction
Perspective based view models are TQL based models. These models can be defined and created in modeling
studio of RTSM. View models are used for the creation of topology-based event correlation and also used to filter
out events.

2.Creating Perspective based Model.

Chapter 4 Topology Bases Event Correlation
1.Introduction
2.Steps and Examples
Then save your work.
Chapter 5 Key Performance Indicators (KPIs)

1.Introduction

Key Performance Indicators (KPIs) provide quantifiable measurements to help you monitor
business performance, and assess the business impact of problems in the system. For more
information about KPIs, see HI and KPI Definitions.

The KPI Definitions page includes definitions of all the KPIs that can be used in OBM. Each
KPI definition is assigned a default business rule. For a list of out-of-the-box KPI definitions,
see List of KPI definitions.

Advanced users can modify the predefined KPI definitions and create new KPI definitions to
customize how information is presented. For example, you may want to create new KPI
definitions when integrating data from a new external system into OBM.

KPI definitions are categorized as follows:

 Predefined. Out-of-the-box KPI definitions.

 Predefined (Customized). Out-of-the-box KPI definitions that have been edited.
 Custom. New or duplicated KPI definitions.

2.Steps and Examples

Chapter 6 Monitored and Unmonitored nodes
1.Introduction
Monitored nodes are those nodes which have active agent monitoring it, and unmonitored nodes are those nodes
which do not have active agents installed over them but still are added to OBM and RTSM as valid nodes.

2.Steps and Examples