Escolar Documentos
Profissional Documentos
Cultura Documentos
BI Monitoring
Disclaimer
This presentation outlines our general product direction and should not be relied on in
making a purchase decision. This presentation is not subject to your license agreement
or any other agreement with SAP. SAP has no obligation to pursue any course of
business outlined in this presentation or to develop or release any functionality
mentioned in this presentation. This presentation and SAP's strategy and possible future
developments are subject to change and may be changed by SAP at any time for any
reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no
responsibility for errors or omissions in this document, except if such damages were
caused by SAP intentionally or grossly negligent.
This demo introduces the BI Monitoring application and shows how to work with the
below mentioned BI Monitoring applications.
oIntroduction
This picture shows a typical BI scenario (between backend systems and end user). Two monitoring levels are provided:
System level monitoring for the involved technical systems
Monitoring of important BI objects (process chains, queries, templates, BO jobs)
Process Chains
BO Jobs
Info
objects
BOE Web
Reports
Application
Queries /
Templates
End user
Monitored BI objects (process chains, queries and templates in SAP BW system; jobs in BO system)
Monitored systems in BI scenario grouped by BI component type (BW systems, BO server systems, BO web app server systems).
BI monitoring scenario
HTTP
CORBA
Multidim. BO
Crystal WebI
Others Analy. CMS Server
Services Services
Serv. Layer
SAP Data
BW Sources
oIntroduction
1. Select a
scenario...
Status of
Total number of the
alerts for the monitored
specific BI BI
component type applications
(BO jobs,
BW process
System Monitoring status (availability, chains and
performance and exceptions) queries and
templates)
2011 SAP AG. All rights reserved. 10
BI Overview Monitor
The BI Overview Monitor shows at a glance the summary of the current status and
the open alerts of all BI components that are included in your technical scenario.
Alert (summary)
Technical instances status
(worst case)
Summary of alerts and status worst case of all systems in the same BI component type
(web app, BO, BW )
Tomcat example
Technical instances
of a BO system
Two BO systems
Tomcat example
Switch between
Graphical and
Tabular View
Allows
comprehensive
overview for large
number of
instances
oIntroduction
This picture shows a typical BI monitoring scenario and the monitored technical objects:
The involved technical systems in a full scope BI monitoring scenario include
BO Web Application Systems (with SP1 only Tomcat is supported for system monitoring). For SP2 SAP J2EE
and WebSphere are planned to follow
BOBJ server systems.
SAP BW systems. Technically the SAP BW systems may consist of a ABAP type system and a SAP J2EE type system
The system monitoring for each involved system has to be setup separately via the system monitoring setup
System monitoring for each system can be viewed via the system monitoring UI or as jump in from the BI monitoring UI
SAP Data
Warehouse
Systems
SAP BI Platform Systems
BO Web Application (SAP BW)
(BusinessObjects Enterprise)
Server Systems
System
System type ABAP
type System or JAVA
ATC type BOBJ (SAP
(Tomcat) J2EE)
oIntroduction
The BO Web Applications System Monitor shows the single BO Web components
that are part of your technical scenario.
Select a System
Monitoring category you
are interested in, for
example Performance
Availability of BOE
InfoView web application
(HTTP ping from SMD agent)
Thesystem monitoring for the BO Web Application System provides all general system monitoring capabilities for the
underlying web application system plus specific monitoring for BO web application metrics
Currently the following BO web application specific metrics are provided
Category Availability: regular http ping check for the BO InfoView web application (web UI for BOE). The URL is
defined during managed system setup and stored in the Solution Manager URL framework.
Category Performance: average response time of BO web application frontend calls (Introscope metric)
Category Exceptions: any message of type ERROR in the BO web application log of the InfoView webapp.
More specific ERROR patterns can be customized by the customer based on customer need / experience.
Solution Manager
Introscope EM BO Web Application
Server Systems
Performance
Metrics
Performance
SMD Asb
jj dds
Agent
ds dd
Availability
BOE Web
URL ping
Application
Exceptions SMD
Agent Asb
jj dds
ds dd
Host
Agent
oIntroduction
BOE Cluster
BOE node
Technical system
BOE node
BOE Server Process BOE Server Process
Currently no metrics
BOE Server Process BOE Server Process on BO system level
BOE BOE B BOE BOE
Service Service Service Service
BOE BOE BOE BOE
Service Service Service Service BOE nodes are not
BOE Server
modelled but each server
Intelligence Agent
BOE Server process name has the
Intelligence Agent node name as prefix
Thesystem monitoring for the BO ServerSystem provides all general system monitoring capabilities for the
underlying operating system plus specific monitoring for BO metrics
Currently the following BO Server specific metrics are provided
Category Availability: BOE Server availability metric from Introscope (collected by BO monitoring service and
offered via JMX)
Category Performance: average response time of BO Server Introscope metric
Category Exceptions: unexpected server stops logged in the SIA (Server Intelligence Agent) log (BO watchdog
server)
More specific ERROR patterns can be customized by the customer based on customer need / experience. An
inactive metric entry is available for BO server type in the SAP template
BO
Solution Manager Server Systems
Introscope EM
Performance
+ Availability Metrics
Performance SMD BO Server
Agent
Asb
jj dds
ds dd
BO Server
Availability
BO Monitoring
Server
JMX
Host
Agent
oIntroduction
This demo shows how to work with the following BI Monitoring applications:
oIntroduction
In the BI Overview
Monitor choose the BO
Server Systems box
Monitored jobs are For each job you can see the status of
grouped by the BO each monitored metric:
system they belong to
- Not Started on Time
- Out of Time Window
- Duration
- Status
J3
yesterday today tomorrow
W1 W2 W3
time
J1 J4
J2
J
J5 6
Job runs
Closest window
Reported metric value
and log on
The BI Monitoring for BO Jobs provides the following metrics for the execution of process chains in the Business Objects
system:
Performance:
Duration
Availability:
Out of Time Window
Exceptions:
Status
Solution Manager (ABAP stack) Solution Manager (JAVA stack) BO Server system
SMD Agent
Web-Service Agelet e2emai.bobj
Extractor
BOBJMonService
Name = DPC PUSH CORE
Agelet remoteos
External Name=
SystemID=<SOLMAN-SID> BOBJMonServiceVi_
Extended Content=<BO server Document
host name> Type= Consumer Script List Jobs
Proxy
bobjnormal.jar
BO Server
oIntroduction
In the BI Overview
Monitor choose the BW
Server Systems box
Monitored process
chains/steps are
grouped by the BW
system they belong to
Monitoring of complete
process chains as well as For each job you can see the status of
single process chain each monitored metric:
steps is supported. - Not Started on Time
- Out of Time Window
As of Solman 7.1 SP1 metrics are calculated - Duration
from all process chain / step runs within the - Status
last 24h worst case values are reported. - Records Processed
As of SP3 each single run may raise an alert . - Data Packages Processed
or ST03N
2. Select the alert group 1. Select the alert that you are interested
that you want to investigate in - for example BW Process Chain
in greater detail Records/Data Packages
The BI Monitoring for Process Chains provides the following metrics for the execution of process chains in the BW
system:
Performance:
Duration
Availability:
Out of Time Window
Exceptions:
Status
Records Processed
Data Packages Processed
RFC
Extractor ST-PI:
/SDF/E2E_BW_PROCESSCHAINS
BW
oIntroduction
In the BI Overview
Monitor choose the BW
Server Systems box
Monitored queries /
templates are grouped
by the BW system they
belong to
2. Choose section
Queries: Bex Web
(ABAP)
The BI Monitoring for Queries & Templates provides the following metrics for the execution of queries and templates in
the BW system:
Performance:
Average response time of queries
Average response time of templates
ST-PI:
Extractor /SDF/E2E_BW_QUERY_TEMPLATES
RFC
BW
No part of this publication may be reproduced or transmitted in any f orm or f or any purpose Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
without the express permission of SA P AG. The information contained herein may be Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
changed without pr ior notice. mentioned herein as well as their respective logos are trademarks or r egistered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Some s oftware products marketed by SAP AG and its distributors contain proprietary
software c omponents of ot her software vendors. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQ L Anywhere, and other Sybase
products and services mentioned herein as w ell as their respective logos are trademarks or
Microsoft, Windows, E xcel, Outlook, and PowerPoint are r egistered trademarks of Microsoft
registered trademarks of Sybase, Inc. Sybase is an SAP c ompany.
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, All other product and service names mentioned are the t rademarks of their respective
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, companies. Data c ontained in this document serves informational purposes only. National
z/VM, z/OS, i5/OS, S /390, OS /390, OS/400, AS/400, S/390 Parallel Enterprise Server, product specifications may var y.
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, The information in this document is proprietary to SAP. No part of this document may be
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, reproduced, copied, or transmitted in any f orm or for any purpose without the express prior
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, written permission of SAP AG.
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix ar e trademarks or r egistered
This document is a preliminary version and not s ubject to your license agreement or any
trademarks of IBM Co rporation.
other agreement with SAP. This document contains only intended strategies, developments,
Linux is the registered trademark of Linus T orvalds in the U .S. and other countries. and f unctionalities of the SAP product and is not intended to be binding upon SAP to any
particular course of business, product strategy, and/or development. Please note that this
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are ei ther trademarks or
document is subject to change and may be changed by SAP at any time without notice.
registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries. SAP assumes no responsibility for errors or omissions in this document. SAP does not
Oracle i s a registered trademark of O racle Corporation. warrant the ac curacy or c ompleteness of t he i nformation, text, graphics, links, or ot her items
contained within this material. This document is provided without a warranty of any kind,
UNIX, X/Open, OSF/1, and Motif are r egistered trademarks of the O pen G roup. either express or implied, including but not limited to the implied warranties of
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, V ideoFrame, and MultiWin are merchantability, fitness f or a particular purpose, or non-infringement.
trademarks or r egistered trademarks of C itrix Systems, Inc. SAP shall have no liability for damages of any kind including without limitation direct,
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W 3C, World special, indirect, or consequential damages that may result from t he u se of t hese materials.
Wide Web Consortium, Massachusetts Institute of Technology. This limitation shall not apply in cases of intent or gross negligence.
Java is a registered trademark of Oracle Corporation. The statutory liability for personal injury and defective products is not affected. SAP has no
control over the information that you may access through the u se of h ot links contained in
JavaScript is a registered trademark of Oracle Corporation, used under license for these materials and does not endorse your use of third-party Web pages nor provide any
technology invented and implemented by Netscape. warranty whatsoever relating to third-party Web pages.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, and other SAP products and services mentioned herein as well as their
respective logos are t rademarks or registered trademarks of S AP AG i n Germany and other
countries.