HP OM to Operations Bridge:

Technical evolution path

Key technical benefits for HP OM customers
HP OM HP Operations
Modern
UI Bridge
• Node-/
Nodegroup-centric Topology
-based • CI-/CI Type-centric
Policy
• Policy-centric • View concept
Event
• Single health state automation &
• Multiple CI types
correlation
Policy -
• Single service type Node
• Multiple KPIs
assignme
nt MPs, BSM
• Sophisticated Node
Connectors & • Fine-granular
RTSM Integrations
monitoring skills health indicators
Operator –
required Node
group Simplified • Tailored workflows for
• Deep understanding assignmen
t
Configuration
Monitoring, Designer,
of IT environment Deployer, Tuner
Collaboration
required
 Technical evolution in phases
Plan the Introduce OMi
Establish effective
Integrate event Switch off HP PM
evolution operator workflow
sources & topology
Execute at your own pace!
Evaluate your “Headless” OpsBridge
current OpsBridge with with key Manage Operations Agents from
monitoring topology integrations OMi step by step Switch off HP
for operators Choose Mgmt Packs or import OM
Plan how to Correlation policies
Easy tuning
automatically event enrichment Efficient
Configure SiteScope from
establish & automation operator
OMi Automated
topology workflow Import SiteScope monitoring
using the templates configuration
Plan modern UI
integrations and
embedded Move from HP Switch off HP
performance Reporter to SHR Reporter
Plan operator
grapher
groups, etc. Service Health
Reporting
Increased
user
motivation
Model business
through services, add more event type indicators for TBEC &
servicegamification
health

Gain additional benefits after each evolution

phase!
Phase 1: Plan the evolution (1/2)
Evaluate your current HP OM deployment
• Understand how your environment will benefit from using the Operations Bridge solution
• Review OMi deployment options and determine the deployment architecture suitable for your business
needs
• Plan implementation details: determine the policies that need to be migrated, decide which
customizations will benefit your environment, and so on
Plan how to automatically establish infrastructure topology
• Review the technologies for establishing infrastructure topology, such as Management Pack/custom
discovery policies, HP UCMDB and HP Universal Discovery, etc.
• Select the technology that will best help you facilitate the move from a node-centric approach (HPOM) to
a CI and topology-centric approach (OMi)
Plan operator groups and roles
• Determine operator groups, define responsibilities and permissions, decide how many My Workspace
pages you will have and what information they will show
Phase 1: Plan the evolution (2/2)
Determine the integrations that need to be migrated
• Depending on your needs, determine which integrations need to be re-established
and whether out-of-the-box integrations exist and can be used
Operations Bridge
Plan the monitoring configuration Evolution Guide
• Understand the value of the OMi Monitoring Automation functionality OMi Management
• Evaluate your current monitoring configuration and decide how you want to Packs Evolution
standardize and fine tune your monitoring Guide
Plan license migration
• Review the Operations Bridge License Exchange Program that offers you an easy way to exchange
your HPOM licenses to Operations Bridge and OMi Management Pack licenses.
• Contact your HP account team or HP partner for more information.

Plan your implementation upfront to take full advantage of OMi

capabilities!
Phase 2: Introduce OMi
Install OMi
• Follow the instructions provided in the interactive OMi Installation and Upgrade Guide
Establish automatic topology synchronization & discovery Operations
• Use Management Pack service discovery, HP UCMDB and/or HP Universal Discovery Bridge
interfaces Evolution Guide
Consolidate events from various sources OMi manuals

• Integrate HPOM and SiteScope events, integrate 3rd-party solutions using BSM Connector(s)
Establish event automation and enrichment
• Configure SBEC, TBEC, TBEA, EPI, event integrations via Web Services and CLI, integration with HP
Operations Orchestration
Establish integrations with trouble-ticket systems
• Configure incoming events to be automatically forwarded to Incident Management Systems, such as HP
Service Manager
Phase 3: Establish effective operator workflow
Define user roles, user groups, and set permissions
• Define roles and permissions and create users and groups to provide/restrict access to
the OMi functionality
Operations
Set up the customized operator environment Bridge
• Create one or more customized operator My Workspace pages for an individual Evolution Guide
operator or an operator group
• Re-create custom HP OM tools and import custom Performance Graphs
• Define auto-assignment rules to automatically assign events to user groups
Implement operator-workflow specific integrations
• If required, set up Operations Orchestration integration, cross-launches into other applications,
Knowledge Base systems, forwarding to Incident Management Systems, forwarding to User Notification
Systems
Increase operator motivation through gamification
Phase 4: Complete the evolution
At this stage of the evolution journey, you can:
• Move to Service Health Reporter (optional)
• Switch off HP Performance Manager (optional)
• Configure HP SiteScope from OMi (optional)
• Start managing HP Operations Agents from OMi
• Move to OMi Management Packs
• Add Business Services and Event Type Indicators (can be done during
various evolution phases)
• Switch off unnecessary HP OM Management Server(s)
Move to Service Health Reporter (SHR)
Establish reporting using Service Health Reporter
• Install Service Health Reporter (Already installed)
• Install available SHR Content Packs (Already installed) Operations
• Configure collections Bridge
• Re-define custom shifts and custom groups Evolution Guide
• Use out-of-the-box SHR reports SHR manuals
• Re-establish custom metric collection using Content Development Environment (if required)
• Re-establish custom reports using Business Objects 3.1 (if required)
• Continue using HP Reporter as a gatherer to simplify the move to SHR (if required)
• Verify that HP Service Health Reporter has taken over the tasks of HP Reporter
• Switch off HP Reporter

Achieve the model-driven cross-domain reporting!

HP Reporter to SHR evolution in phases
Can be done in days Can be done in weeks

Plan the Install and Configure SHR Customization and new content Switch off HP
evolution deploy SHR (collection) creation Reporter
Prerequisite:
OMi RtSM as the Replace Enablement and
Deployed topology source multiple PSO/Partner
instances of involvement
List domains Systems/Standard OVR
covered by edition CDE for new metrics
HP Reporter
Audit OOTB SHR BO Report
Evaluate customization
reports and
OVR
deployment coverage
(Gatherer vs.
Reporter use
cases)

Review SHR
handbook of
reports and
Equivalence
guide
Switch off HP Performance Manager
Import custom graphs
• If you created custom graphs in Performance Manager,
import them into OMi and map them to CI types
• You can also manually re-create custom graphs in OMi directly Operations
Bridge
Switch off Performance Manager Evolution Guide
Configure SiteScope from OMi
On the SiteScope system:
• Install and configure the HP Operations Agent and connect
it to OMi
Operations Bridge Evolution
•Adjust SiteScope templates so that the import tool recognizes
SiteScope variables and converts them into OMi instance parameters Guide
OMi Administration Guide
On the OMi system:
OMi Integration Guide
• Set up the SiteScope system as an OMi connected server
• Verify that a node CI has been created for the SiteScope system and make sure that the systems
monitored by SiteScope are represented as node CIs in the RTSM
• Import SiteScope templates (these templates can be grouped into aspects, included in management
templates and assigned manually or automatically by OMi)
• Move SiteScope monitor deployment from HP OM for UNIX to OMi
Manage Operations Agents from OMi
Choose and import policies
• Choose a node group that you plan to manage from OMi
• Identify the node representing the node group
Operations
• Determine policies that need to be exported and imported or use
Bridge
existing Management Packs
Evolution Guide
Adjust, group and test
• Adjust policies, group them into aspects (if necessary)
• Create management templates (if necessary)
• Manually assign to test nodes, verify configuration
Automate configuration
• Create auto-assignment rules using aspects or MTs
• Switch the target server
Move from Smart Plug-Ins to OMi Management Packs
OMi Management Packs – additional value:
• Automated Monitoring
• Simplified Configuration
• Composite Application Monitoring OMi Management Packs Evolution
• Topology-Based Event Correlation Guide
• Extended Coverage OMi Management Pack Development
Guide
• Simplified Licensing

You can create your own OMi Management Pack!

You can build your own OMi Management Pack for your application using the OMi Management Pack
development kit.
Smart plug-ins and corresponding Management Packs
HP OM Smart Plug-ins
HPOM Smart Plug-in for Oracle Database
HPOM Smart Plug-in for System Infrastructure
HPOM Smart Plug-in for Virtualization Infrastructure
HPOM Smart Plug-in for Cluster Infrastructure
HPOM Smart Plug-in for Microsoft SQL Server
HPOM Smart Plug-in for Microsoft Exchange Server
HPOM Smart Plug-in for Microsoft Active Directory
HPOM Smart Plug-in for SAP
HPOM Smart Plug-in for Sybase
HPOM Smart Plug-in for WebSphere
HPOM Smart Plug-in for WebLogic
HPOM Smart Plug-in for Web Server(Apache)
HPOM Smart Plug-in for Web Server(IIS)
HP OM Smart Plug-in for Microsoft Enterprise Server
(SharePoint)
OMi Management Packs
HP OMi Management Pack for Oracle Database
HP OMi Management Pack for Infrastructure
HP OMi Management Pack for Infrastructure
HP OMi Management Pack for Infrastructure
HP OMi Management Pack for Microsoft SQL Server
HP OMi Management Pack for Microsoft Exchange Server
HP OMi Management Pack for Microsoft Active Directory
HP OMi Management Pack for SAP
HP OMi Management Pack for SAP Sybase ASE
HP OMi Management Pack for IBM WebSphere Application Server
HP OMi Management Pack for Oracle WebLogic
HP OMi Management Pack for Apache Web Server
HP OMi Management Pack for Microsoft IIS
HP OMi Management Pack for Microsoft SharePoint Server
Add business services & event type indicators
Add Business Services
• … and their relationships to underlying discovered CIs to provide more information
to operators
Different business service criticality influences event priority! OMi manuals

Add ETIs for TBEC & Service Health (if an ETI represents an HI)
• Using ETI mapping rules on the OMi server
• In policies: when editing policies, when events occur again and again and must be correlated
Switch off HP OM
Steps:
• Switch all Operations Agents to OMi
• Remove the flexible management template from nodes Operations
• Remove server from trusted certificate list (optional) Bridge
• Delete the HP OM Connected Server in OMi Evolution Guide
• Delete the HP OM certificate authority private key
• Switch off HP OM

Note: When using the License Exchange Program, OMi and OM can be used in parallel until the
evolution is completed.
Thank you