73
Business Availability Center Architecture Overview

Business Availability Center Architecture Overview

Embed Size (px)

Citation preview

Page 1: Business Availability Center Architecture Overview

Business Availability Center

Architecture Overview

Page 2: Business Availability Center Architecture Overview

2

BAC Overview

BAC provides:• Performance and application monitoring• End-user management• IT infrastructure availability management• Service-level management• Configuration management• Composite application diagnostics• Business Transaction Management• Business Process Management• Problem isolation• Vertical solutions management – SOA, Siebel, SAP

BUSINESS AVAILABILITY CENTER OVERVIEW

Page 3: Business Availability Center Architecture Overview

33

Business Availability Center

Business Process Monitor –

Synthetic End-user simulation

End Users

Internet/ Firewall

Lan/network User/Web front-end

Services Middleware Backend and Data

MiddlewareJ2EE, .NET

/MQ/Tibco/Sonic CICS

Application Aware Network

Management – relating the

application to the network (Network

Node Manager/RUM)

Discovery & Dependency Mapping

– population of UCMDB for services, infrastructure and

related dependencies

RUM/BPI /TV and Diagnostics collect information about

real users, business processes and transactions

Agents /Agentless (OPC/ SiteScope) –

Infrastructure Monitoring

including EMS integrations

Business Availability

Center

Universal CMDBBAC Dashboard• Problem Isolation Tools• Service Level Management• Topology Views• Detailed Reporting• Alert Notifications• Web-based Administration

Architectural Overview

August 11, 2008

Page 4: Business Availability Center Architecture Overview

4

BAC Architecture

BPI TV

Diagnostics

SiteScope BPM RUM Diagnostics BPI TV

EMS Tools

Page 5: Business Availability Center Architecture Overview

5

BAC Data CollectorsBAC ARCHITECTURE

BPI TV

Diagnostics

SiteScope BPM RUM Diagnostics BPI TV

EMS Tools

Diagnostics: Monitors J2EE and .NET application performance and bottlenecks in real time using a probe on the application server

BPI: Provides visibility into the health and performance of business processes that are running over the IT infrastructure

TV: Tracks business transactions as they progress through the enterprise.

RUM: Measures the online experience and behavior of the users from across the enterprise

SiteScope: Collects key performance measurements for a wide range of back-end IT infrastructure components. SAM provides centralized administration and reporting for SiteScope instances.

BPM: Proactively measures the end-user experience by executing controlled, repeatable transactions from multiple locations

Discovery Probe: Discovers the IT infrastructure and collects the topology information

Page 6: Business Availability Center Architecture Overview

6

BAC ServersBAC ARCHITECTURE

EMS Tools

Mail Server

SNMP Server

BPI TV

Diagnostics

SiteScope BPM RUM Diagnostics BPI TV

EMS Tools

Gateway Server: Runs the BAC application, handles reporting, administration console, receives data from data collectors and distributes it to the BAC Data Processing server and the Database server

Data Processing Server: Aggregates data, runs the online and offline Business Logic Engines (BLEs), and controls the CMDB. The online BLE calculates the Dashboard views in real time. BLE calculates SLAs and reports.

Database Server: Stores system-wide data, management-related data, topology data, and profile data

Page 7: Business Availability Center Architecture Overview

7

Third-Party Servers and ToolsBAC ARCHITECTURE

BPI TV

Diagnostics

SiteScope BPM RUM Diagnostics BPI TV

EMS Tools

SNMP Server: Receives SNMP traps sent by the BAC alerting mechanism

EMS Tools: Integrates data from EMS applications and servers into BAC server and sends data from BAC server to the EMS servers by using the generic data engine application programming interface (API) and EMS adapters

Mail Server: Sends alerts and scheduled reports to designated recipients

Page 8: Business Availability Center Architecture Overview

8

BAC Data FlowBAC ARCHITECTURE

BPI TV

Diagnostics

SiteScope BPM RUM Diagnostics BPI TV

EMS Tools

Page 9: Business Availability Center Architecture Overview

9

Data Collectors Overview

Page 10: Business Availability Center Architecture Overview

10

BAC ARCHITECTURE

Introduction to Data Collectors

Business Process Monitor

Real User Monitor

SiteScope

Diagnostics

TransactionVision

Business Process Insight

Discovery Probe

Page 11: Business Availability Center Architecture Overview

11

Business Process Monitor

• Installed on host machines located on network or on the internet at global locations

• Use a recorded script to run synthetic transactions

• Send the collected data to BAC

• Use the HTTP(S) protocol for collection & configuration

• Run independently as a service on the host machine

DATA COLLECTORS OVERVIEW

Page 12: Business Availability Center Architecture Overview

12

Real User Monitor

RUM probe:• Passively monitors the

requests and responses sent to and from a monitored Web server

• Monitors HTTP(S) and TCP/IP protocols

DATA COLLECTORS OVERVIEW

RUM engine:

•Configures the RUM Probe

•Receives data collected by the RUM probe using SSH

•Filters information based on configuration

•Stores data samples in a database

•Sends page, transaction, user, server data samples to BAC over HTTP(S)

MySQL database:

Provides a repository for RUM data

Stores session details, and session summary

Page 13: Business Availability Center Architecture Overview

13

SiteScope

Monitors infrastructure components

• Servers, network elements, application services - Weblogic, Websphere, Oracle, SOA

• Uses many standard protocols for monitoring:

• Uses HTTP(S) to communicate metrics back to BAC

• SiteScope interface can be accessed over ports 8888 and 8080.

Other Sitescope roles:

• Integration gateway for External Monitoring Systems (EMS)

• Automatically deploys monitors for newly discovered CIs

• Validates problem isolation issues via on-demand-monitors

• Acts as system health using preconfigured built-in monitors for BAC

DATA COLLECTORS OVERVIEW

Page 14: Business Availability Center Architecture Overview

1414

Diagnostics MonitorDiagnostics Probe:

• Installed on the customer’s Java, J2EE or .NET application servers.

• Observe user activity at the class, method and JDBC/ADO call level

DATA COLLECTORS OVERVIEW

Diagnostics Server:

• Can control multiple diagnostic probes

• Integrates with BAC and Quality Center

Diagnostics Collector:

• Supports remote collection of metrics from SQL Server (2005 only) and Oracle 10g Database, WebSphere MQ and SAP NetWeaver - ABAP system.

Diagnostics Profiler:

• Monitor hotspots, exceptions, threads, stack traces, method latency in real time.

• Monitoring Application Memory

• Light Weight Memory Diagnostics

• Heap Breakdown

Page 15: Business Availability Center Architecture Overview

15

TransactionVision

Main Features:• Transaction tracking solution that graphically shows you the interaction

between all components of your system• Non-intrusively records individual events flowing through a computer network• Patented algorithm assembles events into single, coherent business transaction• Graphical analysis tools enable users at various levels to get the information

they need

DATA COLLECTORS OVERVIEW

Page 16: Business Availability Center Architecture Overview

16

Business Process Insight (BPI)

• Up-to-the-minute view into the health, performance & effectiveness of a business process or process segment.

• Based on real business transactions providing ability to drill into specific process instances (e.g. orders, trades or payments)

• Automatically track and escalate against business level KPIs & service objectives for business flow rates, timings and backlogs

• Translate IT service impact into business (financial) impact information

• Allow business users to improve the effectiveness of their business processes

DATA COLLECTORS OVERVIEW

Page 17: Business Availability Center Architecture Overview

17

Discovery Probe• Dynamically discovers and maps IT

service dependencies to provide visibility and control over business services with minimal effort and cost

• Populates the HP Universal CMDB to create an accurate model

• Uses spiral discovery processes• Object-oriented, allowing specific CIs to

be discovered using a library of discovery patterns that can capture:

–High-level applications and their components like SAP, Siebel, Citrix and MQ Series J2EE or .NET components and interdependencies

–Database components such as tablespaces, users and jobs

–Software assets such as installed products and patches

–System resources such as servers, CPUs, memory, network interfaces and storage devices

–Network devices such as routers, switches, load balancers, switch ports, VLANs and firewalls

DATA COLLECTORS OVERVIEW

Page 18: Business Availability Center Architecture Overview

18

Data Collectors Review

CHAPTER REVIEW

Data Collectors Functionality

1. BPMA. Emulates user experience with the application by running transactions

and collecting application availability and response time data.

2. RUMC. Tracks the experience of end users with the application and collects

availability and response data in real-time.

3. SiteScopeD. Monitors the application infrastructure and collects network and server

performance data in real time.

4. DiagnosticsB. Collects key performance measurements for J2EE and .NET applications

at the class, method and JDBC call level

5. TransactionVisionE. Provides visibility into the health and performance of business

processes that are running over the IT infrastructure

6. Business Process Insight

F. Provides visibility into the health and performance of business processes that are running over the IT infrastructure

7. Discovery ProbeG. Discovers hardware, network and application infrastructure

components and the relationship between them and populates the Configuration Management Data Base (CMDB)

Page 19: Business Availability Center Architecture Overview

19

Universal Configuration Management Database - UCMDB

Page 20: Business Availability Center Architecture Overview

20

Universal CMDB

Automated and integrated Universal CMDB and Application Mapping

Key Benefits:• Understand and visualize how IT

infrastructure delivers business services• Gain visibility and control over changes to

business services• Improve business agility by proactively

analyzing change impact• Smart, topology-based monitoring reduces

likelihood of spurious alarms

Key Capabilities:• Automatically discover and map business

services and its infrastructure (Layers 2-7)• Gather deep configuration detail and track

configuration change history• Topology Query Language to automatically

create and maintain business service maps• Correlation rules to assist in business impact

analysis

Page 21: Business Availability Center Architecture Overview

21

ITSM and ITIL

Ensure ITIL alignment and improve productivity

Key Benefits:• Improve agent effectiveness and first call

resolution• Reduce service resolution times and improve

incident prioritization• Enhance problem management process

effectiveness

Key Capabilities:• Common CI definition provides help desk

agents and IT Operations a consistent view• Business service views enable agents to

prioritize and route calls appropriately• History of CI changes enables quick

recognition and correlation to previous problems/incidents

Page 22: Business Availability Center Architecture Overview

22

HP Universal CMDB & Application Mapping

STORAGE

Oth

er

dis

cover

y

sourc

es

Web S

erv

ices

base

d S

DK

Know

ledge M

odule

s (S

AP,

Sie

bel, C

ust

om

applic

ati

ons,

etc

.)

Impact analysis Reporting (Change, comparison, gold masters, statistical, etc.) AdministrationA

ct

HOST/NETWORK SOFTWARE BUSINESS APPLICATIONS

Security • Authentication • Alerts/Notification • Scheduler

Dis

cover

Network map Application Software mapComposite application map

Map

Topological data model

Enrichment Impact rulesReconciliation

TQL – Smart Mapping

Other repositories

Change tracking

Mod

el

Federa

tion

Repository

How it works

Page 23: Business Availability Center Architecture Overview

23

Federation with authoritative repositories

HP Universal CMDB

ServiceCenter

Reduce MTTR, minimize support costs

Process artifacts, RFCs, incidents,

problems

Business Avail. Center

Improve availability, prevent problems

Operational KPIs, end-user performance

Change & Config Center

Business Services based configuration mgmt.

Policies, release process artifacts and DSL

Third party products

Leverage domain specific meta data, process

outcomes

AssetCenter

IT financial management, sw/hw asset management

Contracts, ownership, financial, licenses etc.

HPUNIVERSAL

CMDB

CIs, CI attributes, relationships,

business services

SOA Center

Identify rogue web services, map services

SOA library, policies, performance KPIs

Operations Center

Monitor health and performance, filter

events

Performance metrics, deep configuration data

Network Mgmt. Center

Optimize network avail., performance &

bandwidth

Network performance, configuration data

Page 24: Business Availability Center Architecture Overview

24

CI RelationshipsUCMDB IN BAC

Page 25: Business Availability Center Architecture Overview

25

Discovery – Process, Packages and Patterns

Page 26: Business Availability Center Architecture Overview

26

Methods for Populating UCMDBDISCOVERY – PROCESS, PACKAGES AND PATTERNS

Page 27: Business Availability Center Architecture Overview

27

Overview of the Discovery Process

CIs CIs

The discovery process is an ongoing, automatic process that continuously detects changes in your IT infrastructure and updates CMDB accordingly. • The spiral discovery continues until your entire IT infrastructure

is discovered and mapped. 

DISCOVERY – PROCESS, PACKAGES AND PATTERNS

Page 28: Business Availability Center Architecture Overview

28

Components of the Discovery Architecture

DISCOVERY – PROCESS, PACKAGES AND PATTERNS

Page 29: Business Availability Center Architecture Overview

29

Business AvailabilityBusiness AvailabilityCenterCenter

29 10 April 2023

DDM Workflow

DashboardDashboard

UCMDB

SLMSLM

UCMDBUCMDB

Element Managers

End User Experience

DDM

Operations

Manager

Infrastructure

Service View

Service View

Service

Applications

Hosts

Resources

1. Discovery & Dependency Mapping

• Performs dynamic discovery

• Populates the CMDB with CIs and Relationships

1. Discovery & Dependency Mapping

• Performs dynamic discovery

• Populates the CMDB with CIs and Relationships

Model of the service based on CIs and

relationships

Page 30: Business Availability Center Architecture Overview

30

Run DiscoveryDISCOVERY – PROCESS, PACKAGES AND PATTERNS

Page 31: Business Availability Center Architecture Overview

31

Views

Page 32: Business Availability Center Architecture Overview

32

UCMDB ViewsIn BAC, you can create a Pattern View:

• A Pattern View is a view based on a query for extracting information from CMDB and created from CI types, the result of a TQL query

– You create a pattern view if you want to dynamically update the view with changes in UCMDB.

– A pattern view updates itself dynamically – as new configuration items or changes that match the pattern are updating the UCMDB they are added to the view

– E.g.: all <UNIX servers connected to a win server running a Weblogic application> [this is a pattern]

VIEWS

Page 33: Business Availability Center Architecture Overview

33

Role based views

33 10 April 2023

Service

Applications

Hosts

ResourcesEvents

User Experience KPIs

Page 34: Business Availability Center Architecture Overview

34

Introduction to Topology Query Language - TQL

A pattern view is the result of a TQL query that is executed for extracting information from UCMDB.• TQL is a language and tool for discovering, organizing, and

managing IT infrastructure data.• TQL example: return all Unix hosts running an Oracle DB [on

port 1522]

VIEWS

Page 35: Business Availability Center Architecture Overview

35

Dashboard

Page 36: Business Availability Center Architecture Overview

36

Dashboard OverviewDashboard – displays operational viewsView – a way to organize data in a business meaningful way• Line of Business – e.g Consumer Banking• Data center – Austin Data Center• Applications – Bill Payment, Funds Transfer, SAP• Custom – all Oracle database servers

Views are fully configurable• KPIs – Define goals and objectives based on metrics• Status – condition of a metric in relation to thresholds (e.g.

performance [KPI] >99.5% [threshold] -> Status = green)• Business Rules – calculate the status of KPIs. Create your own

rules (e.g. percentage, worst/best child, etc..). Define propagation

• Alerts – triggered when a node in the view meets preset conditions (e.g. availability [KPI] < 99.2% [threshold] more than 30 minutes)

DASHBOARD

Page 37: Business Availability Center Architecture Overview

37

The Top View TabDASHBOARD

Root CI

Child CI

KPIs

Tooltip

Page 38: Business Availability Center Architecture Overview

38

The Console TabDASHBOARD

Status trend & history indicator

CIs

KPIs

Page 39: Business Availability Center Architecture Overview

39

DashboardPart of Gateway

Server

DashboardPart of Gateway

Server

UCMDB

UCMDBUCMDB

Service View

Service View

Service

Applications

Hosts

DDM

ResourcesEvents

Model of the service based on CIs and

relationships

User Experience KPIs

How it all fits together

Adapters & discovery populate

the UCMDB

Business Availability Business Availability CenterCenter

Gateway Server

Data Processing Server

Handles incoming/outgoing requests

Bus carries data samples

Web Data EntryDispatcher & Loader

BusAuthentication &

AuthorizationBAC Dashboard (BAC applications/Admin &

Config)

Data Collectors

Email/opcmsg

Alerts engine

UCMDB ServiceAdapters FrameworkOnline Business Logic

EngineOffline Business Logic

EngineOffline Aggregator

System HealthAlerts Engine

End Users

Page 40: Business Availability Center Architecture Overview

40

Service Level Management - SLM

MetricsMetrics

Page 41: Business Availability Center Architecture Overview

41

Overview of Service Level Management

SLM is used to:• Manage service levels with the service providers• Determine compliance with your SLAs• Compare KPIs such as availability and performance

with defined service levels• Applying ITIL concepts to manage and deliver

services effectively• Improve business processes• It should not be used for finger pointing

SLM

Page 42: Business Availability Center Architecture Overview

42

Best Practices for Implementing SLM

The best practices that you can use to implement SLM are:

• Determine a baseline for performance and availability.• Identify the risks or incidents associated with agreeing to

service levels.• Define a set of internal and external incident priorities.• Establish an escalation path for each incident priority.• Baseline the customer perception of the service levels. • Identify all internal and external suppliers and service

providers.• Understand and communicate the benefits of the SLA to all

stakeholders, such as the IT service manager and service level manager.

SLM

Page 43: Business Availability Center Architecture Overview

43

Building a Service Model

The following steps are involved in building a service model:• Define a business unit. • Define a service.• Add monitors CIs to the created service.

SLM

Page 44: Business Availability Center Architecture Overview

44

Types of SLM Reports

SLM provides the following types of reports:• Status Snapshot• SLA Reports• Outage Reports• User Reports

SLM

Page 45: Business Availability Center Architecture Overview

45

Generating Status Snapshot ReportSLM

Page 46: Business Availability Center Architecture Overview

46

Generating CI Status ReportSLM

Page 47: Business Availability Center Architecture Overview

47

Problem Isolation

Page 48: Business Availability Center Architecture Overview

48

Overview of Problem Isolation

Problem Isolation delivers:

• Integrates with HP Universal CMDB to link end-user problems with the underlying infrastructure

• Provides a central place to view critical information about problems and reduces manual correlation to improve MTTR

• Places systems information in a defined context for faster troubleshooting

• Performs real-time problem validation and provides recommendations and advanced analysis

• Provides automated data collection for tier one

Page 49: Business Availability Center Architecture Overview

4949 April 10, 2023

Problem Isolation

Key Benefits:• Ensure problem ownership and

improved real time communication• Reduce manual troubleshooting

through advanced analysis tools• Empower users to isolate performance

problems in composite environments• Triage problems in production via a

single unified UI

Key Capabilities:• Automatic correlation of end-user

problems and underlying infrastructure issues

• Analysis of changes for improved suspect identification

• Automatic identification of end-user behavior anomalies

• Automatic deployment of ad-hoc monitors for additional decision-supporting information

Reactive and proactive analysis

Reactive Analysis

Proactive Analysis

Page 50: Business Availability Center Architecture Overview

50

EUM MonitoringPrinciples

Page 51: Business Availability Center Architecture Overview

51

Business AvailabilityBusiness AvailabilityCenterCenter

DashboardDashboard

UCMDB

SLMSLM

UCMDBUCMDB

Service View

Service View

Service

Applications

Hosts

Element Managers

End User Experience

DDM

Operations

Manager

Infrastructure

ResourcesEvents

Model of the service based on CIs and

relationships

User Experience KPIs

EUM Walkthrough3. End User Experience

• Passive and active monitoring of user experience KPIs

• KPIs update the status in the CMDB and service view

3. End User Experience

• Passive and active monitoring of user experience KPIs

• KPIs update the status in the CMDB and service view

Page 52: Business Availability Center Architecture Overview

52

The BAC Workflow - OnboardingBAC ARCHITECTURE

Page 53: Business Availability Center Architecture Overview

53

MonitoringInfrastructure• Servers – up/down, CPU, memory, disk• Network – availability, packets lost, routing tables• Services – queue length, availability, DNS, FTP, SMTP

End User• How does the user perceive the application• Measure business impact

Server down – not a problem with load balancingSystem slow – user takes business somewhere elseBAC = all about the end-user, different paradigm

OVERVIEW OF MONITORING

Page 54: Business Availability Center Architecture Overview

54

Monitoring Key Points

Plan for monitoring• Decide

• Applications and infrastructure to be monitored • Locations to be monitored• Frequency of monitoring• Monitoring goals.• User roles and backgrounds – operations vs. business

• Identify the critical business process and business process steps to be monitored.

• Identify the user tasks• Identify integration points into customer processes

CHAPTER SUMMARY

Page 55: Business Availability Center Architecture Overview

55

Introduction to Business ProcessesOVERVIEW OF MONITORING

End User Monitoring is based on Business Processes

Page 56: Business Availability Center Architecture Overview

56

End-User Management (EUM) Reports

Page 57: Business Availability Center Architecture Overview

57

The BAC Workflow – End User Management

BAC ARCHITECTURE

Page 58: Business Availability Center Architecture Overview

58

Types of EUM ReportsEUM REPORTS

Page 59: Business Availability Center Architecture Overview

59

EUM Reports

Page 60: Business Availability Center Architecture Overview

60

Vertical Solutions

- BAC for SAP- BAC for Siebel- BAC for SOA

Page 61: Business Availability Center Architecture Overview

61

Vertical Solution Components

Vertical Solution – a management solution for a specific type or set of application• E.g. Siebel, SAP, SOA

Solution specific (out-of-the-box) monitoring protocols• E.g. SOAP for SOA and Web Services

Solution specific monitoring templates• UDDI for SOA• SARM for Siebel

Solution specific discovery patterns

Solution specific views for discovered information• Siebel hosts• Well behaved and rogue web services

Solution specific integrated reporting• BAC for Siebel• BAC for SAP• BAC for SOA

VERTICAL SOLUTION CONCEPTS

Page 62: Business Availability Center Architecture Overview

62

Customization

Supply custom-made capabilities in discovery, monitoring and views

Encapsulate domain expertise for the specific environment• RUM - meaningful URL (Siebel)• Discovery of changes (SAP)• Discovery of Web Services (SOA UDDI)

Utilize and integrate with solution-specific tools• SARM (Siebel)• TMS (SAP)• UDDI (Systinet)

VERTICAL SOLUTION CONCEPTS

Page 63: Business Availability Center Architecture Overview

63

Best Practices

Incorporate best practices in generic BAC tools• SiS solution templates

Document system-specific “how-to”• Configuring SARM (Siebel)

VERTICAL SOLUTION CONCEPTS

Page 64: Business Availability Center Architecture Overview

64

BAC for verticalsolution

Typical ApplicationUnder Test (AUT)Siebel/SAP/SOA

BusinessProcessMonitor

SiteScope

ApplicationMapping

Changes

End User Monitoring

DiscoveryProbe

RUMProbe

RUMEngine

Real User Monitoring

WSAS

DB

Architecture - General

DiagnosticsProbe

DiagnosticsEngine

System Monitoring,WS Synthetic Transactions

Topology

DiscoveryReal User Monitoring

VERTICAL SOLUTION CONCEPTS

Page 65: Business Availability Center Architecture Overview

65

BAC for Siebel

Siebel Enterprise7.5.3/7.7/7.8

BusinessProcessMonitor

SiteScopeSystem Monitoring

ApplicationMapping

Changes

End User Monitoring

Siebel Diagnostics

SARM, DB Breakdown

DiscoveryProbe

RUMProbe

RUMEngine

Real User Monitoring WS

GW

AS

DB

Architecture – BAC for Siebel

Discovery

Topology

VERTICAL SOLUTION CONCEPTS

Page 66: Business Availability Center Architecture Overview

66

BAC for verticalsolution

Typical ApplicationUnder Test (AUT)Siebel/SAP/SOA

BusinessProcessMonitor

SiteScope

ApplicationMapping

Changes

End User Monitoring

DiscoveryProbe

RUMProbe

RUMEngine

Real User Monitoring

WSAS

DB

Architecture – BAC for SOA

DiagnosticsProbe

DiagnosticsEngine

System Monitoring,WS Synthetic Transactions

Topology

DiscoveryReal User Monitoring

VERTICAL SOLUTION CONCEPTS

Page 67: Business Availability Center Architecture Overview

67

Solution Walkthrough

Page 68: Business Availability Center Architecture Overview

68

Business AvailabilityBusiness AvailabilityCenterCenter

10 April 2023

Solution Workflow

DashboardDashboard

UCMDB

SLMSLM

UCMDBUCMDB

Element Managers

End User Experience

DDM

Operations

Manager

Infrastructure

Service View

Service View

Service

Applications

Hosts

Resources

1. Discovery & Dependency Mapping

• Performs dynamic discovery

• Populates the CMDB with CIs and Relationships

1. Discovery & Dependency Mapping

• Performs dynamic discovery

• Populates the CMDB with CIs and Relationships

Model of the service based on CIs and

relationships

Page 69: Business Availability Center Architecture Overview

69

Business AvailabilityBusiness AvailabilityCenterCenter

10 April 2023

DashboardDashboard

UCMDB

SLMSLM

UCMDBUCMDB

Service View

Service View

Service

Applications

Hosts

Element Managers

End User Experience

DDM

Operations

Manager

Infrastructure

ResourcesEvents

Model of the service based on CIs and

relationships

2. Events

• Events are detected by Element Managers

• Events are sent to BAC and update the CMDB

2. Events

• Events are detected by Element Managers

• Events are sent to BAC and update the CMDB

Solution Walkthrough

Page 70: Business Availability Center Architecture Overview

70

Business AvailabilityBusiness AvailabilityCenterCenter

10 April 2023

DashboardDashboard

UCMDB

SLMSLM

UCMDBUCMDB

Service View

Service View

Service

Applications

Hosts

Element Managers

End User Experience

DDM

Operations

Manager

Infrastructure

ResourcesEvents

Model of the service based on CIs and

relationships

User Experience KPIs

Solution Walkthrough3. End User Experience

• Passive and active monitoring of user experience KPIs

• KPIs update the status in the CMDB and service view

3. End User Experience

• Passive and active monitoring of user experience KPIs

• KPIs update the status in the CMDB and service view

Page 71: Business Availability Center Architecture Overview

71

Business AvailabilityBusiness AvailabilityCenterCenter

DashboardDashboard

UCMDB

SLMSLM

UCMDBUCMDB

Element Managers

End User Experience

DDM

Operations

Manager

Infrastructure

Model of the service based on CIs and

relationships

10 April 2023

Service View

Service View

Service

Applications

Hosts

ResourcesEvents

User Experience KPIs

Solution Walkthrough4. Service Impact

• The service model is dynamically updated

• New infrastructure automatically added to view by DDM

4. Service Impact

• The service model is dynamically updated

• New infrastructure automatically added to view by DDM

Page 72: Business Availability Center Architecture Overview

72

Role based views

10 April 2023

Service

Applications

Hosts

ResourcesEvents

User Experience KPIs

Page 73: Business Availability Center Architecture Overview

73

Q&A