Using Database Performance Warehouse to Monitor IBM …a248.g.akamai.net/.../2015/07/80b5d887-5b7c-0010-82c7-eda71af511fa… · His areas of expertise include database monitoring

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2011 SAP AG 1

Using Database Performance

Warehouse to Monitor IBM DB2 for

z/OS – Customizing Reports (Part 3)

Applies to:

Enhancement Package 1 for SAP Solution Manager 7.0 (SP21) and IBM DB2 for z/OS. For more information, visit the Performance homepage.

Summary

In the Database Performance Warehouse, all relevant data concerning database space consumption that is collected by the DBA Cockpit is stored in an SAP Business Intelligence (BI) system. This SAP BI system is used by the SAP Solution Manager Diagnostics (SMD) back end of an SAP Solution Manager system. SAP provides content for the DBA Cockpit to analyze the different technical areas related to space consumption of a DB2 system.

Authors: Dr. Jochen Röhrig, Software Engineer, IBM Deutschland Research & Development GmbH Steffen Siegmund, Senior Developer, SAP AG

Created on: 30 November 2011

Author Bio

Dr. Jochen Röhrig is a member of the joint IBM/SAP platform team for SAP on IBM System z at SAP in St. Leon-Rot, Germany. His areas of expertise include operating system and database system monitoring of SAP systems on IBM System z. In addition, he is responsible for the SAP application server on Linux for IBM System z.

Steffen Siegmund works as a developer in the IBM DB2 for Linux, UNIX, and Windows development team at SAP. His areas of expertise include database monitoring based on SAP BI, integration with SAP Solution Manager and the setup of highly available cluster solutions with IBM DB2 for Linux, UNIX, and Windows and IBM Tivoli System Automation for Multiplatforms.

http://www.sdn.sap.com/irj/sdn/bi-performance-tuning

Using Database Performance Warehouse to Monitor IBM DB2 for z/OS – Customizing Reports (Part 3)


© 2011 SAP AG 2

Table of Contents

Customizing Reports .......................................................................................................................................... 3

SAP BI Basics ..................................................................................................................................................... 3

BEx Web Applications ..................................................................................................................................... 3

BEx Query ....................................................................................................................................................... 3

InfoCube .......................................................................................................................................................... 3

MultiProvider ................................................................................................................................................... 3

Customizing an Existing Report ......................................................................................................................... 4

DBA Cockpit: Report Configuration ................................................................................................................ 4

BEx Web Template (Part 1) ............................................................................................................................ 5

BEx Query Designer ....................................................................................................................................... 8

BEx Web Template (Part 2) .......................................................................................................................... 11

DBA Cockpit: Guided Activity for the Integration of Web Reports ................................................................ 14

Related Content ................................................................................................................................................ 19

Copyright........................................................................................................................................................... 20



© 2011 SAP AG 3

Customizing Reports

As already described in the first part of this series of articles, the Database Performance Warehouse uses the SAP BI of the SAP Solution Manager to store the database-specific performance metrics and the DBA Cockpit provides a flexible analysis application based on BI technology. SAP already provides content that is described in part 2 of this article series. This article focuses on the modification of BI Business Explorer (BEx) reports. At the end of this article, you will know how to modify existing reports and how to create new reports.

SAP BI Basics

The following section provides you with a very short introduction into some SAP BI terms and concepts.

BEx Web Applications

The generated BEx Web applications are Web-based applications from the Business Explorer (BEx) that are used for data analysis and for reporting on the Web. BEx Web applications are executed Web templates. The DBA Cockpit uses BI BEx Web applications to analyze the performance data that is stored in the Solution Manager BI. You can create your own BI BEx Web applications based on this data and integrate new BI BEx Web templates into the performance warehouse.

Note: You have to use the Web Application Designer (SAP BW 3.x) to create web templates that are rendered in the SAP ABAP application server.

BEx Query

In the BEx Web applications, you use one or more data providers. The data providers are the BEx queries that provide the data for reporting. In the BEx queries, you specify the characteristics and key figures that you want to have in your reporting. In addition, you can define calculated key figures, restricted key figures, exceptions and conditions in the queries.

Note: You have to use the BEx Query Designer for SAP NetWeaver BI 7.0 and 7.1 to define BEx queries for the Database Performance Warehouse.

InfoCube

An InfoCube describes (from an analysis point of view) a self-contained data set, for example, for a technical entity in DB2. You analyze this dataset in a BEx query. An InfoCube is a set of relational tables that were arranged according to the star schema: A large fact table in the middle surrounded by several dimension tables.

The InfoCubes physically contain the DB2 performance metrics that were collected by the DBA Cockpit back-end.

MultiProvider

A MultiProvider is a type of InfoProvider that combines data from a number of InfoCubes and makes it available for analysis purposes. The MultiProvider itself does not contain any data. Its data comes entirely from the InfoCubes on which it is based. These InfoCubes are connected to one another by a union operation.

In the Database Performance Warehouse, MultiProviders are used for abstraction of underlying data aggregation:

To save space in the SAP Solution Manager system, the performance data is aggregated according to the time dimension. After 9 month the data is compressed to have metrics based on month granularity. To ease reporting, MultiProviders are used to abstract from this underlying architecture.

In the Database Performance Warehouse, all BEx queries are defined at MultiProviders.



© 2011 SAP AG 4

Customizing an Existing Report

The use case for this scenario is that the report for the top 50 largest tables Table Sizes (Top 50) will be changed to provide a new report Table Sizes (Top 25) for the top 25 largest tables where free storage is not reported any longer.

DBA Cockpit: Report Configuration

You configure all configuration parameters that are related to the performance warehouse on the Configuration screen. For example, you can configure the framework, the templates used for the reports and the report categories. You can access the Configuration screen of the performance warehouse by calling the DBA Cockpit and choosing Performance → Performance Warehouse → Configuration.

On the Web Reports tab page, you find the definition of all available reports.

1. Open the DBA Cockpit by calling transaction DBACOCKPIT. The initial screen DBA Cockpit: System Configuration Maintenance appears.

2. Connect to the database for which you want to modify or add the report. 3. In the navigation frame of the DBA Cockpit, choose Performance Performance Warehouse

Configuration. If you are using the SAP GUI-based user interface, the application starts in a separate Web browser.

4. Choose the Web Reports tab strip . 5. Open the Tables category and select the report for Sizes (Top 50). 6. Add the technical name for the Web Report to the clipboard or note it somewhere. In the example,

the technical name is 0TPL_DB2_MP01_Q0020_D.



© 2011 SAP AG 5

BEx Web Template (Part 1)

You have to open the BEx Web template to get the technical name of the BEx queries used in the template.

7. Open the Web Application Designer by choosing Start Programs Business Explorer Business Explorer (SAP BW 3.x) Web Application Designer (SAP BW 3.x).

Note: To create web templates that are rendered in the SAP ABAP application server, you have to use the Web Application Designer (SAP BW 3.x).

8. Open the BEx Web template with the technical name that the DBA Cockpit configuration provided you with. In the example, the name is 0TPL_DB2_MP01_Q0020_D.



© 2011 SAP AG 6

In the BEx Web template, you see different areas for the items used in the report. In the right area, there is a placeholder for the navigation pane for the table, the detailed table itself, the table exceptions and the conditions (there are additional placeholders for Web templates that contain charts: for the navigation pane for the chart, for the chart itself, and for the chart exceptions). For each item, you can set some parameters in the lower left area.

9. Save the BEx Web template with a different name in your customer name space. In the example, the BEx Web template is saved as ZTPL_DB2_MP01_Q0200_D.



© 2011 SAP AG 7

10. In the lower left area, you can see the mapping of a data provider in the BEx Web template and the BEx query itself. Copy the technical name of the BEx query to the clipboard or note it somewhere.

11. Save your work.



© 2011 SAP AG 8

BEx Query Designer

To modify the query of the data provider, you have to open the BEx Query Designer.

12. Open the BEx Query Designer by choosing Start Programs Business Explorer Query Designer.

Note: To define BEx queries for Database Performance Warehouse, you have to use the BEx Query Designer for SAP NetWeaver BI 7.0 and 7.1.

13. Open the BEx query with the technical name that you copied to the clipboard (see step 10). In the example, the name is 0DB2_MP01_Q0020.

14. Save the BEx query with a different name in your namespace. In the example, the BEx query is saved as ZDB2_MP01_Q0200.



© 2011 SAP AG 9

In the BEx Query Designer, you have different frames available (see the following screenshot):

In the left (InfoProvider) frame, you find all the characteristics and key figures that are available in your MultiProvider. In the Rows/Columns frame, you can see which characteristics and key figures are available in your current BEx query. The Columns and Rows frame should be self-explanatory. The Free Characteristics stands for all characteristics that you can add to the report using the BI drilldown feature. In the BEx Web application, you can add these characteristics to get the key figures at a more detailed level. In the right Properties frame, you have attributes for any item of the BEx query. Here, you specify for example key figure attributes like display behavior and calculation. To remove the Free Storage column from the BEx query and change the query to report the top 25 instead of the top 50 largest tables, proceed as follows:



© 2011 SAP AG 10

15. Right click on the Free Storage [MB] key figure in the Columns frame and select Remove in order to remove the Free Storage column from the BEx query.

16. Click on the Conditions tab strip just above the Messages frame in order to navigate to the Conditions frame. Right click on the Top 50 (Allocated Storage) condition and select Edit.



© 2011 SAP AG 11

17. The Change Condition popup window opens. Select the only available condition parameter and change its value to 25. Change the description of the condition accordingly.

18. Repeat the previous step for the Top 50 (DASD Usage) condition. 19. Save your work.

BEx Web Template (Part 2)

In the previous steps a new BEx query has been created. To enable the new BEx query in the BEx Web template, you have to change the definition of the data provider.

20. Open the Web Application Designer. 21. Open the BEx Web template with the technical name that you have chosen in step 9. In the example,

the technical name is ZTPL_DB2_MP01_Q0200_D. 22. In the lower left section, select the data provider DATAPROVIDER_1.



© 2011 SAP AG 12

23. Choose the Select Query pushbutton right next to the BEx query to change the BEx query.

24. Choose the BEx query that you saved in step 14. In the example, the BEx query is called ZDB2_MP01_Q0200.



© 2011 SAP AG 13

25. Select the placeholder for the detailed table in the right area of the BEx Web template and change the title of the BEx Web template to Sizes (TOP 25).

26. If you have more than one data provider in your BEx Web template, you have to repeat from step 10

to modify all BEx queries used in the BEx Web template. 27. Save your work.

28. Copy the technical name of your new BEx Web template to the clipboard



© 2011 SAP AG 14

DBA Cockpit: Guided Activity for the Integration of Web Reports

DBA Cockpit provides a guided activity to integrate your modified or new BEx Web applications into the DBA Cockpit. As a result, you will have a Sizes (Top 25) pushbutton in the Tables category of the performance analysis application to easily run your new report.

29. Call the DBA Cockpit (transaction DBACOCKPIT). 30. Connect to the database for which you want to modify or add the report. 31. In the navigation frame of the DBA Cockpit, choose Performance Performance Warehouse

Configuration. If you are using the SAP GUI-based user interface, the application starts in a separate Web browser.

32. Choose the Web Reports tab strip 33. To integrate a web report, choose the Add pushbutton.

A wizard appears guiding you through the procedure as shown in the following screenshot.

34. To skip the Introduction, choose Continue



© 2011 SAP AG 15

35. In the General setup step, you have to specify a name for your report, a description for the tooltip and a category. After you have entered the required values, choose Continue. In the example, the attributes are as follows:

Report: Sizes (Top 25)

Description: Sizes (Top 25)

Category: Tables

36. In the next step, you specify the technical attributes of the BEx Web application and the BEx queries. Paste the technical name of the BEx Web application in the Web Report (Default) field. If you would like to have different granularities for the time dimension, you could specify either different reports for the granularities or you could define the data providers in the BEx queries that you want to change the drilldown on. Since in the second approach you need only one set of BEx Web application and BEx queries, this approach is recommended.



© 2011 SAP AG 16

37. In the Database Filter step, you specify the availability of the report according to different database versions or database features. We use the settings of the original report.



© 2011 SAP AG 17

38. To get to the summary screen and to verify all parameters, choose Continue.

39. To add your report to DBA Cockpit, choose Execute. In the resulting screen you should get a message about the successful integration of the new BEx Web template.



© 2011 SAP AG 18

Finally, your report Sizes (Top 25) is available for your database in the category Tables.

You should now be able to modify reports that are provided by SAP or to create your own reports and integrate them into the DBA Cockpit.

You are welcome to provide feedback - your ideas and input on performance reporting will be highly appreciated and will be taken into consideration for the SAP-provided content.



© 2011 SAP AG 19

Related Content

Using Database Performance Warehouse to Monitor IBM DB2 for Z/OS – General Overview (Part 1)

Using Database Performance Warehouse to Monitor IBM DB2 for Z/OS – The Content (Part 2)

For more information, visit the Performance homepage.

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/7016fece-d0d1-2c10-6db2-c799e4405436

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8048ac68-a9f0-2d10-7b8c-f1c0ce532f64

http://www.sdn.sap.com/irj/sdn/bi-performance-tuning



© 2011 SAP AG 20

Copyright

© Copyright 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, IBM DB2 Analytics Accelerator, Netezza, 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 Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 S.A. in the United States and in other countries. Business Objects 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.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Documents

Using Database Performance Warehouse to Monitor IBM …a248.g.akamai.net/.../2015/07/80b5d887-5b7c-0010-82c7-eda71af511fa… · His areas of expertise include database monitoring