How to work with BI Monitoring

Transcription

1 How to work with BI Monitoring

2 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 SAP AG. All rights reserved. 2

3 Agenda This demo introduces the BI Monitoring application and shows how to work with the below mentioned BI Monitoring applications. ointroduction obi Overview Monitor osystem Monitor o BO WebApp Systems o BO Server Systems o BW ABAP/Java Systems obi Detail Monitors o BO Job Monitor o BW Process Chain Monitor o BW Report Monitor 2011 SAP AG. All rights reserved. 3

4 Introduction - Monitoring for Business Intelligence SAP Solution Manager BI Overview Monitor System Monitor BI Detail Monitors Central system status overview for all technical components involved in SAP Business Intelligence Solution Capability to monitor cross-system SAP BW process chains and single process chain steps Central monitoring of SAP BW queries and templates Central monitoring of Business Objects specific jobs and correlation to system specific metrics Integration of Business Intelligence specific alerts in Alert Inbox including Notification Management, Incident Management, Task Assignment and forwarding to 3 rd party 2011 SAP AG. All rights reserved. 4

5 Introduction Monitored BI scenario and objects 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) BO Web Application Server Systems SAP BI Platform Systems (BusinessObjects Enterprise) SAP Data Warehouse Systems (SAP BW) Backend Systems / Data Sources e.g. SAP ERP Process Chains BO Jobs End user BOE Web Application Reports Info objects Queries / Templates 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 2011 SAP AG. All rights reserved. 5

6 SAP BusinessObjects Business Intelligence 4.0 Architectural Overview (simplified) WEBI CRYS TAL XCelsi us Live Office Frontends HTTP Web Crystal WEBI Pioneer.. Services Viewer Viewer Viewer SAP BusinessObjects Enterprise XI Web Application Java Platform SDKs BO Web App. Layer CORBA Others Crystal Services Multidim. Analy. Serv. WebI Services CMS BO Server Layer ODBO, MDX, RFC,.. SAP BW Data Sources 2011 SAP AG. All rights reserved. 6

7 Agenda ointroduction obi Overview Monitor osystem Monitor o BO WebApp Systems o BO Server Systems o BW ABAP/Java Systems obi Detail Monitors o BO Job Monitor o BW Process Chain Monitor o BW Report Monitor 2011 SAP AG. All rights reserved. 7

10 BI Overview Monitor Initial View The overview is grouped by the BI component types in your scenario Total number of alerts for the specific BI component type System Monitoring status (availability, performance and exceptions) Status of the monitored BI applications (BO jobs, BW process chains and queries and templates) 2011 SAP AG. All rights reserved. 10

11 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) BI monitored objects status (summary) System + host level status (worst case) Summary of alerts and status worst case of all systems in the same BI component type (web app, BO, BW) 2011 SAP AG. All rights reserved. 11

12 BI Overview Monitor Detail View (BO Web App) Clicking on a component type in the BI overview monitor expands the underlying single systems and technical instances with their separate alert and status aggregation per system resp. technical instance Tomcat example 2011 SAP AG. All rights reserved. 12

16 System Monitoring for systems in BI monitoring scenario 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 BO Web Application Server Systems SAP BI Platform Systems (BusinessObjects Enterprise) SAP Data Warehouse Systems (SAP BW) System type ATC (Tomcat) System type BOBJ System type ABAP or JAVA (SAP J2EE) With enhancements for BO web application Completely BO specific classical ABAP / SAP J2EE system monitoring (no BW specifics) 2011 SAP AG. All rights reserved. 16

18 Example: BO Web Application Systems Monitor The BO Web Applications System Monitor shows the single BO Web components that are part of your technical scenario. Drill down to the system monitoring application system hierarchy by clicking on the icon of a System Monitoring category you are interested in Each single instance of a BO Web component is shown including details like number of alerts, availability status, performance status and exception status. A direct start of the system monitoring application for each BO Web instance is provided SAP AG. All rights reserved. 18

20 Example: BO Web Application Systems Monitor The performance category and its subcategories are shown In the details section you can investigate now the single performancerelevant metrics 2011 SAP AG. All rights reserved. 20

21 Example: BO Web Application Systems Monitor By changing the view category you can directly switch between the single categories to Performance and examine the metric details 2011 SAP AG. All rights reserved. 21

22 BI System Monitor BO Web Application metrics Availability of BOE InfoView web application (HTTP ping from SMD agent) Introscope metric tree Avg. Response time of open session action Exceptions in BI launchpat = InfoView application or in Query As a Web Service QaaWS calls (Log file scanning via SMD agent) 2011 SAP AG. All rights reserved. 22

23 System Monitoring for BO Web Application System The system 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 Performance SMD Agent Introscope EM Performance Metrics Asb jj dds ds dd BO Web Application Server Systems Availability URL ping BOE Web Application Exceptions SMD Agent Asb jj dds ds dd Host Agent 2011 SAP AG. All rights reserved. 23

25 BO Enterprise System Model BOE Cluster BOE Server Process BOE node BOE Server Process BOE Service BOE Service BOE Service BOE Service BOE node B BOE Server Intelligence Agent BOE Server Intelligence Agent BOE Server Process BOE Server Process BOE Service BOE Service BOE Service BOE Service Technical system Currently no metrics on BO system level BOE nodes are not modelled but each server process name has the node name as prefix Softwarecomponent Monitoring templates per software component defined on technical instance level (corresponds to BO server types) Technical instances Many types of BO server processes exit. Different types correspond to different BO product instances A complete list of BOE 4.0 services and their mapping to BO server types and SAP BO metric templates can be found here: 2011 SAP AG. All rights reserved. 25

27 Example: BO Server Systems Monitor Choose the category that you are interested in like Availability - For BO systems each BO server represents a technical instance. Each technical instance provides its own metrics and alerts SAP AG. All rights reserved. 27

28 BI System Monitor BO Server Systems metrics Server Intelligence Agent (SIA) No BO specific metrics for performance or availability (SIA is the BO watchdog and not monitored itself) only receiving from Host level Exception for unexpected BO server restarts reported in SIA log For all other BO servers an inactive metric defintion exists that can be adapted by customers 2011 SAP AG. All rights reserved. 28

32 System Monitoring for BO Server System The system 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 Solution Manager Introscope EM BO Server Systems Performance SMD Agent Performance + Availability Metrics Asb jj dds ds dd BO Server BO Server Availability BO Monitoring Server JMX Exceptions SMD Agent Asb Asb jj dds jj dds ds dd ds dd Host Agent 2011 SAP AG. All rights reserved. 32

34 Agenda This demo shows how to work with the following BI Monitoring applications: ointroduction obi Overview Monitor osystem Monitor o BO WebApp Systems o BO Server Systems o BW ABAP/Java Systems obi Detail Monitors o BO Job Monitor o BW Process Chain Monitor o BW Report Monitor 2011 SAP AG. All rights reserved. 34

36 BO Job Monitor The BO Job Monitor opens in a separate tab Monitored jobs are grouped by the BO system they belong to For each job you can see the status of each monitored metric: - Not Started on Time - Out of Time Window - Duration - Status 2011 SAP AG. All rights reserved. 36

37 BO Job Monitor metrics details Delay in minutes of the last finished or currently running job run to the specified threshold timestamp (today if the timestamp is already reached or yesterday otherwise) Maximum distance in minutes of the last finished or currently running job run to the specified threshold time window on the day where the window start timestamp has the closest distance to the job start time. 0 if the job start time is > window start time and job end resp. current time for running job is < window end time. See details on next slide. Duration of last finished or currently running job run in minutes Status of the last finished job run (= job instance) Green if successful Red if failed 2011 SAP AG. All rights reserved. 37

38 BO Job Monitor out of time window calculation examples 0 now yesterday J3 today tomorrow W1 W2 W3 J1 J4 time J2 J5 J 6 Daily time window Job runs Closest window Reported metric value 2011 SAP AG. All rights reserved. 38

39 BO Job Monitor Checking Configured Thresholds Choose the job that you are interested in and check the thresholds How to check the thresholds of your technical scenario? Go to the SAP Solution Manager Configuration - BI Monitoring. Choose your technical scenario and go to the step Configure BO Job Monitor 2011 SAP AG. All rights reserved. 39

40 BO Job Monitor check job details in BO system Select Navigate to and then Central Management Console (CMC) For detailed analyis of a job in the BOE system and log on 2011 SAP AG. All rights reserved. 40

43 BO Job Monitor check job details in BO system Check the corresponding detail information for the alert you are investigating. In our case: check the error message to find the reason for the failed status SAP AG. All rights reserved. 43

44 BI Monitoring for BO Jobs The BI Monitoring for BO Jobs provides the following metrics for the execution of process chains in the Business Objects system: Performance: Duration Availability: Exceptions: Not Started on Time Out of Time Window Status Solution Manager (ABAP stack) Solution Manager (JAVA stack) BO Server system Extractor Name = DPC PUSH CORE SystemID=<SOLMAN-SID> Extended Content=<BO server host name> Web-Service BOBJMonService External Name= BOBJMonServiceVi_ Document Type= Consumer Proxy SMD Agent Agelet e2emai.bobj Agelet remoteos Script List Jobs bobjnormal.jar BO Server 2011 SAP AG. All rights reserved. 44

46 BW Process Chain Monitor - Starting In the BI Overview Monitor choose the BW Server Systems box and click then on the traffic light in the section Process Chains 2011 SAP AG. All rights reserved. 46

47 BW Process Chain Monitor Monitored process chains/steps are grouped by the BW system they belong to Monitoring of complete process chains as well as single process chain steps is supported. As of Solman 7.1 SP1 metrics are calculated from all process chain / step runs within the last 24h worst case values are reported. As of SP3 each single run may raise an alert. For each job you can see the status of each monitored metric: - Not Started on Time - Out of Time Window - Duration - Status - Records Processed - Data Packages Processed 2011 SAP AG. All rights reserved. 47

48 BW Process Chain Monitor Starting the Analysis Transaction 2. Start the BW Analysis Transaction by choosing Navigate to -> Analysis Transaction 1. Mark the BW process chain you want to investigate 2011 SAP AG. All rights reserved. 48

50 BW Process Chain Monitor Analysis with Service Tool ST13 Enter transaction here You can use the SAP WebGUI session also for calling other analysis tools like ST13 (BW-TOOLS) 2011 SAP AG. All rights reserved. 50

52 BW Process Chain Monitor Starting the Alert Inbox Open the alert inbox by clicking on the number of alerts or the traffic light of the BW process chain that you are interested in 2011 SAP AG. All rights reserved. 52

53 BW Process Chain Monitor Alert Inbox for BI 2. Select the alert group that you want to investigate in greater detail 1. Select the alert that you are interested in - for example BW Process Chain Records/Data Packages 3. Choose the Show Details button 2011 SAP AG. All rights reserved. 53

55 BI Monitoring for BW Process Chains The BI Monitoring for Process Chains provides the following metrics for the execution of process chains in the BW system: Performance: Duration Availability: Exceptions: Not Started on Time Out of Time Window Status Records Processed Data Packages Processed Solution Manager (ABAP stack) BW system (ABAP stack) Extractor RFC ST-PI: /SDF/E2E_BW_PROCESSCHAINS Name = DPC PULL CORE SystemID = <BW-SID> Extended Content = ST_PI ST-A/PI: BCC_BW_PC_MONITORING BW 2011 SAP AG. All rights reserved. 55

58 BW Reporting Monitor Monitored queries / templates are grouped by the BW system they belong to For each BW Query or Template you can see Average Response Time in seconds and the alerts 2011 SAP AG. All rights reserved. 58

59 BW Reporting Monitor Analysis with Workload Monitor ST03N 1. Mark the BW Query or Template you want to investigate 2. Start the BW Analysis Transaction by choosing Navigate to -> Analysis Transaction 2011 SAP AG. All rights reserved. 59

60 BW Reporting Monitor Analysis with Workload Monitor ST03N 1. Transaction ST03N opens in a SAPGui for HTML session 2. Choose section Queries: Bex Web (ABAP) 3. Check the details of the query you want to investigate 2011 SAP AG. All rights reserved. 60

61 BI Monitoring for BW Queries & Templates 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 Solution Manager (ABAP stack) BW system (ABAP stack) Extractor Name = DPC PULL CORE SystemID = <BW-SID> Extended Content = ST_PI RFC ST-PI: /SDF/E2E_BW_QUERY_TEMPLATES ST-A/PI: BCC_BW_QT_MONITORING BW 2011 SAP AG. All rights reserved. 61

62 2011 SAP AG. All rights reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. 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 trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities 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 document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. 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 shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. 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 use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages SAP AG. All rights reserved. 62