53257135 BW 7 0 Performance Best Practices
description
Transcript of 53257135 BW 7 0 Performance Best Practices
SAP NetWeaver BW andBusinessObjects Web IntelligencePerformance Best Practices
Tanner SpauldingSAP NetWeaver RIG AmericasMay 6th, 2009
© SAP 2009 / 2
1. Product Positioning & Roadmap2. Implementation Guidelines3. Troubleshooting Tips and Tricks4. Wrap-up5. Q&A
Agenda
© SAP 2009 / 3
EnterpriseReporting
Dash-boards
Crystal
Xcelsius
Pioneer
WebIntelligence
Ad-hocReporting
Ad-hoc BISearch
How Business Objects Tools Expand theScope of BI
EnterpriseReporting
Dash-boards
AdvancedAnalytics
Polestar
Functional Scope of the SAPBusinessObjects Tools Suite
© SAP 2009 / 4© SAP 2008 / SAP TechEd 08 / IM201 Page 4
BEx Suite Use Cases and how they should behandled
Business ExplorerSuite
Base: BEx QueryDesignerRecommended: BExQuery DesignerSpecialized tool for for BWqueries , stays as is, nochanges planned
Base: BEx AnalyzerRecommended: PioneerOffice
Multi-source OLAP client
Base: BEx Web AppDesignerRecommended: dependson scenario
(BEx WAD, CE, Xcelsius,WebI, Pioneer Web )
Base: BEx ReportDesignerRecommended:Crystal Reports
Specialized tool for pixel-exact reporting
Query Design
Web-based Analysis
Form
atte
dR
epor
ting
Excel-basedAnalysis
Excel-based OLAP analysisand workbook design
Highly-formattedenterprise reports
Multi-purpose Web templatesfrom IT for business users
Focus on designing virtualsub-cubes, mainly IT
© SAP 2009 / 5© SAP 2008 / SAP TechEd 08 / IM201 Page 5
BEx Web Application Designer / Web TemplateUse Cases and how they should be handled
BEx WebTemplate
Use Cases
Pioneer WebSpecialized tool for web-based OLAP Analysis
BEx WAD or NWCompositionEnvironment Note: TheBEX WAD still avialable , noEOL planned.
Xcelsius(BI Dashboards andPresentations)
WebIntelligenceAd-hoc tool enablingbusiness users toanswer unpredictedquestions
OLAP analysis
Storytelling
Auto
nom
y of
end
-us
ers
Pre-definedapplications
Templates for advanced BWspecific apps with custom
coding
Templates with simplified &pre-defined navigation,
focus on reporting
Templates for high-leveldashboards & advanced
visualization
Templates focusing onOLAP
© SAP 2009 / 6
1. Product Positioning & Roadmap2. Implementation Guidelines3. Troubleshooting Tips and Tricks4. Wrap-up5. Q&A
Agenda
© SAP 2009 / 7
Performance Considerations
SAP Business WarehouseBusinessObjects Enterprise
Service Load Distribution andResource Allocation
Tuning Web Tier
Network Bandwidth
WebI Connectivity OptionsOLAP vs Relational
Support Package / FixPack Level
Product Positioning
SAP Notes
RSADMIN Parameters
SAP Profile/Kernel Settings
BEx Query Settings
Data Manager Runtime
OLAP Engine Runtime
Support Package Level
Enhancement Package Level
© SAP 2009 / 8
OLAP Universes: Recommendations &Considerations
Overall RecommendationBEx queries are recommended as data sources for generating Universes for thefollowing reasons:
BEx queries offer a flexible extension to the data modeling environment and require lesseffort to change than InfoCubesBEx queries offer significant functionality to create customized data sources that meetend-user requirements, such as Calculated & Restricted Key Figures and SAP Variables
You do not need a BEx query for every report and you do not need a Universe forevery existing BEx query
Focus the implementation strategy on limiting the number of Bex Queries and Universesthat share common elementsBuild a small set of BEx queries focusing on sharing common elements in a small numberof Universes
Understand that primarily the WebI Query Panel definition influences how muchdata is retrieved from BW, and not the BEx query design or the WebI Report layout*
In some situations extremely large queries and universes can adversely affectperformance
© SAP 2009 / 9
Architecture of Layers – WebI Connectivity toSAP BW
BW Accelerator
NetWeaver BW 7.0 BOE XI 3.1Physical Virtual Semantic 1 Semantic 2 Semantic 3 Report
Aggregation Engine
MultiProviders,HybridProviders
BEx QueriesInfoProviders
Uni1
Uni2
Uni3
Uni4
Universes WebI Query,QaaWS
WebI Report
It is important to understandwhere time is spent in the
runtime and how it influencesthe overall performance
© SAP 2009 / 10
Architecture of Layers – WebI Connectivity toSAP BW
BW Accelerator
NetWeaver BW 7.0 BOE XI 3.1Physical Virtual Semantic 1 Semantic 2 Semantic 3 Report
Aggregation Engine
MultiProviders,HybridProviders
BEx QueriesInfoProviders
Uni1
Uni2
Uni3
Uni4
Universes WebI Query,QaaWS
WebI Report
Data ManagerRuntime
© SAP 2009 / 11
Architecture of Layers – WebI Connectivity toSAP BW
BW Accelerator
NetWeaver BW 7.0 BOE XI 3.1Physical Virtual Semantic 1 Semantic 2 Semantic 3 Report
Aggregation Engine
MultiProviders,HybridProviders
BEx QueriesInfoProviders
Uni1
Uni2
Uni3
Uni4
Universes WebI Query,QaaWS
WebI Report
OLAPRuntime
© SAP 2009 / 12
Architecture of Layers – WebI Connectivity toSAP BW
BW Accelerator
NetWeaver BW 7.0 BOE XI 3.1Physical Virtual Semantic 1 Semantic 2 Semantic 3 Report
Aggregation Engine
MultiProviders,HybridProviders
BEx QueriesInfoProviders
Uni1
Uni2
Uni3
Uni4
Universes WebI Query,QaaWS
WebI Report
Semantic LayerRuntime
© SAP 2009 / 13
Architecture of Layers – WebI Connectivity toSAP BW
BW Accelerator
NetWeaver BW 7.0 BOE XI 3.1Physical Virtual Semantic 1 Semantic 2 Semantic 3 Report
Aggregation Engine
MultiProviders,HybridProviders
BEx QueriesInfoProviders
Uni1
Uni2
Uni3
Uni4
Universes WebI Query,QaaWS
WebI Report
WebI QueryPanel
© SAP 2009 / 14
Architecture of Layers – WebI Connectivity toSAP BW
BW Accelerator
NetWeaver BW 7.0 BOE XI 3.1Physical Virtual Semantic 1 Semantic 2 Semantic 3 Report
Aggregation Engine
MultiProviders,HybridProviders
BEx QueriesInfoProviders
Uni1
Uni2
Uni3
Uni4
Universes WebI Query,QaaWS
WebI Report
WebI ReportDefinition
© SAP 2009 / 15
Architecture of Layers – WebI Connectivity toSAP BW
The Query Panel Definition iswhat defines the “Microcube”and thus the MDX Query whichis executed on SAP BW
When refreshing the data inthe WebI report, the entireMicrocube is refreshed
© SAP 2009 / 16
SAP Notes to Improve MDX Interface
1142664 MDX: Composite SAP note about performance improvements
1156101 MDX: Composite SAP note for incorrect data
1157922 System error in CL_RSR_HIERARCHY_DIM and SELECT_SIDS_3
1161911 OLE DB for OLAP: Many read accesses to table RSRREPDIR
1162349 OLE DB for OLAP: Restriction on text and performance
1164552 Performance improvement if zero suppression is active
1169205 MDX: Filter transfer in the case of cross join
1170323 MDX: Performance when filtering on hierarchy node
1172076 Performance improvement in special situation
1230303 MDX: Buffering of hierarchy metadata
1236241 MDX: System error in CL_RSR_HIERARCHY_DIM SELECT_SIDS_3
1237104 Performance problems occur when reading the master data
1238661 Slight performance improvement in internal business volume
1240165 Performance optimization for hierarchy authorizations
1252372 OLE DB for OLAP: Additional corrctions for new MDX parser
1257723 OLE DB for OLAP: Short length specified for MEMBER_CAPTION
1265072 MDX: No data in a very specific situation
These SAP Notes willimprove the overallPerformance and Stability ofthe MDX interface in SAPBusiness Warehouse
If applicable, apply theadvance correction in the SAPNote
Refer to the Composite Note(1142664) for the latestPerformance Improvements forthe MDX Interface
It is preferable to import arelatively recent Support
Package rather thanindividual corrections.
© SAP 2009 / 17
“Use Selection of Structure Elements” QueryProperty in RSRT
This simple propertychange helps improveperformance in situationswhere there are a lot ofRestricted Key Figuresand other calculations inthe Query Definition
If you analyzeperformance of the queryand find very highEVENTID 3200 times,and/or the FEMS numberis very high try enablingthis property and checkperformance
This ensures thatstructure elements aresent to the database forprocessing
© SAP 2009 / 18
SAP & Business Objects Integration OverviewPositioning
BOBJ/SAP End-to-End Solution
Web Intelligence(uses for analysis and reporting)
Relational Universes(business objects defined using SQL)
NetWeaver BI
SAP NetWeaver 7.1 – Enterprise Data Warehouse
SAP NetWeaver 7.1 – BW InfoProviders
OLAP Universes(business objects defined using MDX)
MDX Queries SQL Queries
© SAP 2009 / 19
BIA
SAP & Business Objects Integration OverviewPositioning
Audience
Business users
Analysts
Access to BW
MDX Queries SQL Queries
Combine the SAP robustness with the BOBJ front end ease of use
Optimized for ReportingCore set of analyticalfeaturesEasy to understand and useaddressing business userneedsRelational metaphors
SQL Object definitionScale to large datavolumeData warehouse
Optimized for AnalysisDeep analytical capabilitiesAddressing experienced BIUsersOLAP metaphors
Rich MetadataMDX Object definitionInfoCubes
© SAP 2009 / 20
Overview:Options for Universe-Based Access to BW 7.0
BW
Data Federator
RDBMS Analytic Engine
OLAP BAPI ODBOXMLA
UniversesQT ODA
SQL Access MDX Access
WebI XcelsiusQaaWS
BIA
© SAP 2009 / 21
Overview:Options for Universe-Based Access to BW 7.01
BWDF Fascade
Data Federator
RDBMS Analytic Engine
OLAP BAPI ODBOXMLA
UniversesQT ODA
SQL Access MDX Access
WebI XcelsiusQaaWS
BIA
changes and additions in red
© SAP 2009 / 22
Comparison
BW Server Feature MDX SQL
BW Hierarchies
Restricted and Calculated Key Figures
Security
BW Variables
Currency and Unit Conversion
Exceptions, Conditions
SUM, MIN, MAX Aggregations
AVG, COUNT, COUNT DISTINCT, … Aggregations
OLAP Cache
Navigational Attributes
Mass Data Enabled
Federation (e.g. BW – RDBMS, BW – BW)
= fully supported= limited support / workaround
© SAP 2009 / 23
WebI – BW Interoperability via ODA (MDX)Details
Improvements1. Avoid unnecessary sorting
MDX standard imposes results to be sortedHowever, those sorts are typically ignored or not required by WebIsorting can be avoided by using a new UNORDER() function in SAP's MDX
2. Leaner memory consumption during flatteningoptimized flattening algorithmnon-standard result structure
3. Leaner communication ODA – OLAP BAPIuse compressed data exchange via binary XML
AvailabilitySAP NetWeaver BW 7.01 SP 3Business Objects Enterprise XI3.0
Fix Pack 2 w/ LAFix2.1SAP Integration Kit Fix Pack 2 w/LAFix2.1
© SAP 2009 / 24
Data Federator Limitations & WorkaroundsNon-Exhaustive List
BW Server Feature Workaround
Calculated Key Figures, Formulas Define calculated measures in Universes / WebI
BW Variables Define @prompt in Universes or WebI Query Panel; does notwork for exit variables or variables filled through authorizations
Currency and Unit Conversion Simulate via joins in Data Federator
Exception Aggregations SQL standard aggregations (AVG, COUNT DISTINCT) availablevia Data Federator processing
Display Attributes Define joins (in DF) from InfoProvider to master dataInfoProvider tables
Conditions Use filters on measures
BW Hierarchies No workaround
Non-Cumulative Key Figures No workaround
© SAP 2009 / 25
WebI – BW Interoperability via Data FederatorAvailability
SAP NetWeaver 7.01 (Enhancement Package 01) Support Package Stack 03Delivered with the BW Data Federator facade
BOE XI 3.1 Fix Pack 1 or BOE XI 3.0 Fix Pack 2 (+ LaFix 2.1 and 2.3)Include the BW Universe strategiesInclude Universe Designer strategy bug fix
Data Federator XI 3.1Include the BW SQL connectorInclude specific BW SQL compensation techniquesUpdated optimizations for BWSupport for BW authentication mode
SAP Integration Kit XI 3.1For Single-Sign On (SSO) – Available in Q2 09
© SAP 2009 / 26
Summary
Take-AwaysThere is no black & white.It's a trade-off between the two interfaces.
MDX (ODA) SQL (Data Federator)
leads to an OLAP universe leads to a relational universe
exposes almost all semanticsdefined on BW server
exposes only basic semanticsdefined on BW server
enriches data via centrallydefined calculations (e.g.currencies, KPIs, …)
accesses materialized data andallows for ad-hoc enrichment inWebIallows for federation with otherrelational sources via DF
for OLAP-minded analysts for SQL-minded end users
© SAP 2009 / 27
WebI – BW Interoperability via Data FederatorAvailability
Reduce the amount of cells being received from the SAP BW systemOnly include items in the WebI Query Panel that are being leveraged in thereportWebI will not automatically optimize the query based on the report definition
Report design considerationsLeverage report linking (aggregated reports linking to more detailed reports)Leverage Query Drill mode for hierarchical reports
Master Data Style ReportsIn scenarios where the largest parts of the dataset retrieved are master data(i.e. display attributes) consider breaking up the single query into two: one forthe master data display attributes, and one for the actual dataMerge Dimensions functionality can be used to consolidate the dataset
Leverage Publications functionality whenever possible to schedule the reportrefresh in background to reduce end user wait time
This has been greatly improved and extended in XI 3.1 for WebI (Multi-PassBursting)
© SAP 2009 / 28
1. Product Positioning & Roadmap2. Implementation Guidelines3. Troubleshooting Tips and Tricks
1. Overview2. Query3. MDX
4. Wrap-up5. Q&A
Agenda
© SAP 2009 / 29
Layers of Performance Analysis:Web Intelligence to BW
Web Intelligence
BOE / Semantic Layer
MDX
Query
AnalyzePerformance
Network
Network
AnalyzeSAP
NetWeaverBI
Performance
Key Message: Start performance analysis on Query layer. If performance is not sufficienton this layer, continue with general analysis of SAP NetWeaver BI.
© SAP 2009 / 30
Overview
Check the Query performance on SAP NetWeaver BW as benchmark
Perform BOBJ‘s MDX directly on SAP NetWeaver BW
Compare runtime of Query with the overall time it takes to Refresh the report
Optimizations
1. Optimize Query definition
2. Optimize MDX execution on SAP NetWeaver BW (notes)
3. Optimize Universe definition and generation of MDX on BOE (WebI)
4. Optimize Report definition and generation of MDX on WebI
© SAP 2009 / 31
Relevant SAP BW Transaction Codes
RSDDSTAT - Statistics AnalysisStatistics are very good in 7.0 – understand how to read them and you will be able to troubleshoot any long runningqueryTables RSDDSTAT_OLAP & RSDDSTAT_DM
SM66/SM51 - Work Process MonitorUsed to watch processes, see when the complete in BW to deduct how much time was spent rendering in WebI
ST03N – Workload monitorUseful in evaluating more system level workload
RSRT – Query MonitorServes many purposes – one of the most useful BI transactions for analyzing query performance issues
RSTT – Trace ToolVery useful tool for tracing and debugging performance issues – allows you to turn a trace on for given user, then go tothe trace and see detailed runtimes by ABAP class, as well as actually debug the executionThis can be used to capture the MDX Query passed to BI
RSRCACHE – Cache Monitor
MDXTEST – MDX Query Testing Transaction
© SAP 2009 / 32
1. Product Positioning & Roadmap2. Implementation Guidelines3. Troubleshooting Tips and Tricks
1. Overview2. Query3. MDX
4. Wrap-up5. Q&A
Agenda
© SAP 2009 / 33
QuerySAP Transaction RSRT (1)
1. EnterQuery 2. Press Enter
to seeInfoCube
3. Choose Listas QueryDisplay
4. PressExecute +
Debug
© SAP 2009 / 34
QuerySAP Transaction RSRT (2)
5. EnableDisplay
Statistic Data
6. Okay
7. Result set
8. Press Back(F3)
© SAP 2009 / 35
QuerySAP Transaction RSRT (3)
9. List of allevents
10. Selectcolumn
Duration
11. PressTotal
© SAP 2009 / 36
QuerySAP Transaction RSRT (4)
12. Totalruntime asbenchmark
© SAP 2009 / 37
QueryGeneral Information
If the Query performance is not sufficient on layer RSRT, check the followingdocuments.
http://help.sap.com/saphelp_nw70/helpdata/EN/43/e39fd25ff502d2e10000000a1553f7/frameset.htm
https://www.sdn.sap.com/irj/sdn/bi-performance-tuning
© SAP 2009 / 38
1. Product Positioning & Roadmap2. Implementation Guidelines3. Troubleshooting Tips and Tricks
1. Overview2. Query3. MDX
4. Wrap-up5. Q&A
Agenda
© SAP 2009 / 39
Voyager / WebI OLAP Universe Registry trace settings in folder:HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\MDA\Log
In generalEach module (e.g. SAPMODULE, ESSBASEMODULE, ODBOMODULE, etc) has its ownverbosity value setting and module specific settings
OLAP Connectivity Tracing
© SAP 2009 / 40
Tracing SAP BW Connectivity: SAP MODULEtraces
1. MDA log file: These traces are instrumental when troubleshooting or seekingto understand what is happening between the lowest level of SAPBusinessObjects XI 3.x ODA (OLAP Data Access) Driver and the BWsystem/APIs e.g the input prameters for SAP BAPI Function calls.
2. MDX log file: includes the MDX Statements that sent for execution on theSAP Backend – note: there can multiple MDX statements as there are MDXStatements executed to also receive certain meta-data, in addition to the dataitself.
3. Web Intelligence logs: show the XML queries sent by WebI to ODA driverwhich is translated into MDX.
At the highest verbosity levels, the axis and member datais written to the log, potentially incurring a significant
runtime penalty. Set verbosity level to 0 in production.
© SAP 2009 / 41
Voyager / OLAP Universe Registry trace settings are in the folder:HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\MDA\Log
1. ..\Suite 12.0\MDA\LogLogFile : REGSZ value (full path to MDA log file, including file name)
e.g C:\traces\mda.log
2...\Suite 12.0\MDA\Log\Modules\SAPMODULEVerbosity : REG_DWORD value (highest value is 10 decimal = 0x0000000a)
0 (for production systems), 5 (development, UAT), 10 (only when troubleshooting).At the highest verbosity levels the axis and member data is written to the log,potentially incurring a significant runtime penalty.
MDX Query Log : REG_DWORD (full path to MDX log file)E.g C:\traces\mdx_sap.log
OtherOther modules for SAP connectivity tracing (only if required)
RORFLATTENER
Tracing SAP BW Connectivity: SAP MODULEtraces
© SAP 2009 / 42
Create an MDX Log out of WebI Rich Client
1. Create the following Windows Environment Variables:BO_TRACE_CONFIG=c:\bologBO_TRACE_CONFIGFILE=c:\bolog\BO_trace.iniBO_TRACE_LOGDIR=c:\bolog
2. Create the folder c:\bolog
3. Place the file BO_trace.ini into the folder c:\bolog
4. Open the Registry Editor (REGEDIT) and backup the Registry, then import theattached Registry Files
5. Run the WebI Query and the logs will be generated in the specified file path
© SAP 2009 / 43
RSTT – Capturing the MDX Statement (1)
Activate the Trace User which is executing the WebI Report Data Refresh
Execute the Data Refresh in WebI (Run Query / Refresh Data button), thenDeactivate the trace once the data refresh completes
© SAP 2009 / 44
RSTT – Capturing the MDX Statement (2)
© SAP 2009 / 45
RSTT – Capturing the MDX Statement (3)
Double Click on theBAPI_MDDATASET_SELECT_DATAProgram Module and it will open an
ABAP Debugger session
Set a breakpoint at MethodCL_RSR_MDX_COMMAND~START
and Execute until reaching thebreakpoint
© SAP 2009 / 46
RSTT – Capturing the MDX Statement (4)
Set a watch on Variable N_T_MDX
View Table contents for N_T_MDX tocapture the MDX statement
© SAP 2009 / 47
MDXSAP Transaction MDXTEST (1)
1. Paste MDXstatementfrom BOE /Web I here
© SAP 2009 / 48
MDXSAP Transaction MDXTEST (2)
2. ChooseMenu MDX
Command / SetDebug Flags
3. EnableDisplay
Statistic Data
4. Okay
© SAP 2009 / 49
MDXSAP Transaction MDXTEST (3)
5. Press RunQuery
Multidim.
© SAP 2009 / 50
MDXSAP Transaction MDXTEST (4)
6. List of allevents
7. Selectcolumn
Duration8. Press Total
© SAP 2009 / 51
MDXSAP Transaction MDXTEST (5)
Result set
Characteristicsand Key
Figures ofInfoCube
© SAP 2009 / 52
Demo – Troubleshooting Tips
© SAP 2009 / 53
1. Product Positioning & Roadmap2. Implementation Guidelines3. Troubleshooting Tips and Tricks4. Wrap-up5. Q&A
Agenda
© SAP 2009 / 54
7 Key Points to Take Home
Proper product positioning can ensure the “right tool for the right job” is selectedand improve user satisfaction as well as ensure optimal performanceUnderstand where time is spent during the overall runtime using tools availablesuch as RSRT, RSDDSTAT, MDA Logs, etcUtilize Publication capabilities whenever possible to avoid end user wait timeFocus on Query optimization and simplification from the beginningThere are new connectivity options in BOE XI 3.1 and Enhancement Package 1for NetWeaver BI 7.0 (7.01)There are significant performance and stability improvements in BOE XI 3.1 andEnhancement Package 1 for NetWeaver BI 7.0 (7.01)Focus on building SAP Integration Kit knowledge and cross-training on BusinessObjects and SAP BW skills
© SAP 2009 / 55
SAP BusinessObjects ResourcesOn Service MarketPlace
SAP BusinessObjects Support Sitehttp://service.sap.com/bosap-supportA Service MarketPlace logon User and Password required.Wealth of information including, Product Guides, Product Overviews, Install Guides, SupportedPlatforms information, Samples, etc..
© SAP 2009 / 56
SAP BusinessObjects ResourcesSAP Help and SDN
Help @ SAPhttp://help.sap.com > ‘BusinessObjects’ top level navigation tab
SAP BusinessObjects Developer Community on SDNhttp://boc.sdn.sap.com‘BusinessObjects version of SDN’Communities, Beta Product downloads, Webinar information, E-Books, DeveloperConference 2007 slides, Free Trial downloads, more!...Check out the blogs and forums – there is already some great content posted– Ingo Hilgefort’s bolg:https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/u/251909211
SAP NetWeaver Business Warehouse Roadmap and Roadmap FAQhttps://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b00a1a75-c49d-2b10-0ebb-ecc80ab88994https://www.sdn.sap.com/irj/boc/business-objects-for-sap-faq
© SAP 2009 / 57
1. Product Positioning & Roadmap2. Implementation Guidelines3. Troubleshooting Tips and Tricks4. Wrap-up5. Q&A
Agenda