Professional Documents
Culture Documents
505 Tips and Tricks For Using SAP BusinessObjects Web Intelligence With SAP NetWeaver BW - WebI 3.1 Version
505 Tips and Tricks For Using SAP BusinessObjects Web Intelligence With SAP NetWeaver BW - WebI 3.1 Version
Tips and tricks for using SAP BusinessObjects Web Intelligence with SAP BW
Deepu Sasidharan
[ Agenda
Introduction System Landscape Advanced WebI Functionalities Performance Considerations Life Cycle Manager Security considerations Report Deployment Options
[ Introduction
WebI provides end to end self-service experience covering a range of users:
Casual reporting users Ad-hoc reporting users
[ Agenda
Introduction System Landscape Advanced WebI Functionalities Performance Considerations Life Cycle Manager Security considerations Report Deployment Options
[ System Landscape
System landscape design:
Different options are available for implementing BOE XI in your landscape. Various factors like corporate standards for Software Platform, Web Server, DB, High availability requirements, expected system load etc. should be considered while designing the BOE landscape.
[ System Landscape
Highly recommended to size the BOE system prior to project start. Key considerations for sizing:
Input:
Report volume Number of concurrent users % break down of users types (Power user vs. Casual users etc.)
Output:
Number of CPUs (BOE licenses are usually CPU based and need to know this during the initial phase of the Project) Total amount of Memory Number of CMS, Processing servers and Job servers
[ System Landscape
BW
DEV QA PROD
BOE XI
DEV
QA
PROD
LCM
Real Experience. Real Advantage.
[ System Landscape
BOE XI Architecture
[ System Landscape
Technical Considerations:
During the starting phase of the project make sure BOE XI Support Packages and Fix Packs are up to date.
Server and Client tools should be at same Support Package and Fix pack levels. Recommended Support Packages:
BW 7.0 EHP 1 SPS 5 or higher BOE XI 3.1 SPS 3 FP 3.1 or higher
[ Agenda
Introduction System Landscape Advanced WebI Functionalities Performance Considerations Life Cycle Manager Security considerations Report Deployment Options
10
[ Input Controls
WebI provides Input Controls which can be used for filtering report data.
Provides easy to access to filter WebI report. Different types of controls are available for Measures and Dimensions.
Measures: Slider, Spinner and Entry Field
Example: Use a slider to display all values greater than a threshold set from the slider, Sales Revenue > $1million etc.
11
[ Input Controls
Input Controls can be added to the WebI document from the tab Input Controls New Select the Object and Type of Control.
12
[ Scope of Analysis
Scope of analysis lets you create pre-defined drilldown path within your WebI reports providing easy analysis functionality for the users. User can click on the high level object within the report to drilldown to the next level.
13
[ Scope of Analysis
Drilldown path can be pre-defined from Universe Designer Tools Hierarchies.
Create a Custom Hierarchy selecting the objects and order of drilldown.
14
[ Merge Dimensions
Merge dimension allows you to merge data from two different Universes.
Relational and OLAP Universes could be used as source. For example data from a SAP BW based and MS SQL Server based Universe could be combined into one single WebI document.
15
[ Merge Dimension
Accessible from the WebI toolbar.
16
[ Merge Dimension
Merging high volume data is not recommended as this will impact the performance of the report.
Alternate options like storing the data within BW or using BOBJ Data Federator should be considered for high volume data.
17
[ Query Stripping
Query Stripping enables you to bring only the data which is required for the current WebI Report layout.
Default design brings in all the objects available in the WebI Query Panel. This could help improve the performance of the WebI Report. This setting is available only for OLAP Universe based reports. There is a known error with query stripping that will be fixed with BOE XI 3.1 SPS 4. Check OSS note 1516054 for more details.
[ Query Stripping
This is similar to setting the Read Mode for the BW query. Setting need to be done at the WebI Query level and document level.
19
[ Custom Formula
Custom Formula can be created using measures and Dimension.
A custom field can be added to the WebI report comparing two dimension field. BW currently doesnt provide the ability to create formula based on a dimension (Characteristic).
20
[ Custom Formula
Various operators are available: String, Boolean, Date etc. Examples:
Find date differences between two date fields or between the report date and current date. Various business rules can be implemented at the WebI Report level without having to make changes to the BW data model or underlying query.
21
22
23
[ Agenda
Introduction System Landscape Advanced WebI Functionalities Performance Considerations Life Cycle Manager Security considerations Report Deployment Options
24
[ Performance Considerations
Avoid use of Navigational attributes were ever possible.
Navigational attribute requires an extra join during the report execution and will affect the report performance.
OLAP Universe is not designed to handle heavy data volume. For large volume reports consider workarounds:
Split into smaller reports and provide hyperlinks via OpenDoc API.
WebI Processing Servers can only handle upto max. 2 GB per report. Running very large reports which are beyond this limit will result in crashing the WebI Processing server.
25
[ Performance Considerations
WebI Processing Server:
Create more WebI Processing Servers and reduce the number of connections per WebI Processing. This will help better load balancing of the servers. CMC Servers Server Categories WebI Report Processing Servers Properties.
26
[ Performance Considerations
Consider to scheduling large reports during off-peak hours for off-line consumption.
Latest Support Package on BW and BOE XI provides several performance related enhancements. Recommended Support Package levels:
SAP BW EHP1 SPS 5 BOE XI 3.1 SPS 3 FP 3.1
Real Experience. Real Advantage.
27
28
29
[ Transaction MDXTEST
Transaction MDXTEST can be used for executing MDX Statements within the SAP BW System.
Either the MDX Statement can be hand written/pasted into the execution area or can be generated using the system.
Make sure to select XML Mode while doing the test, data returned from BOE XI from BW will be identical to the data from the results of XML Mode. You can use the document below to enable logs on the BOE to view the MDX statement which gets executed.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0e1ec594bd0-2c10-c38b-e51393775064
30
[ Agenda
Introduction System Landscape Advanced WebI Functionalities Performance Considerations Life Cycle Manager(LCM) Security considerations Report Deployment Options
31
[ LCM
LifeCycle Manager lets you move BOE XI Objects (Folders, WebI Documents, Universes etc.) within the landscape.
32
[ LCM
LCM also provides the option for Version management of BOE XI objects. Connection Mapping for the target SAP BW system can be maintained within LCM. LCM doesnt support SAP authentication. LCM is integrated to the BI platform as of BI 4.0.
For BOE XI 3.1 requires a separate installation.
33
[ Agenda
Introduction System Landscape Advanced WebI Functionalities Performance Considerations Life Cycle Manager Security Report Deployment Options
34
[ Security
Different options are available for implementing security within BOE.
It is critical to develop a clear security strategy.
Main considerations:
Is this a new BOE installation? Are there SAP and non-SAP users? What is the current report deployment option? What are the types of users who will need access to the reports?
Power users, casual users etc.
35
[ Security
BOE XI Supports different Authentication methods.
Windows AD Recommended if SAP BW and non-SAP BW users requires access to the BOE system. LDAP SAP (requires SAP IK) Enterprise
36
[ Security
Recommended approach:
Implement SSO between BOE XI and BW.
Requires installing and configuring SAP Integration Kit and SNC
Use Windows AD as the primary authentication mechanism. User mapping between Windows AD User and SAP BW user can be maintained at the BOE level. Import Windows AD Groups/Users into BOE XI. Assign Folder level Security to access WebI Reports to the Windows AD Group. Data level security will be maintained using SAP BW based Analysis authorization.
37
[ Security
To import users in simple format (user id and not systm~clnt\userid format) maintain Registry keys mentioned in OSS note 1343537. This helps user mapping with Windows AD.
38
[ Security
Security can be set at Group level or Individual user level.
Based on the authentication method used groups could be Windows AD Group, SAP BW Role etc. Best practice is to maintain the object security at the Group level. Custom Access levels or Security objects can be created for meeting security requirements which cannot be met using standard objects.
39
[ Security
Various roles which will need to be defined within the BOE XI environment.
Access In CMC Designer Infoview WebI Data Federator
Administrators
Yes
Yes
Yes
Yes
Yes
Security
Yes
No
Yes
Yes
No
Universe Developer
No
Yes
Yes
Yes
Yes
Report Developer
No
No
Yes
Yes
No
Report User
No
No
Yes
Yes
No
40
[ Agenda
Introduction System Landscape Advanced WebI Functionalities Performance Considerations Life Cycle Manager Security considerations Report Deployment Options
41
42
Provide access to Infoview from SAP EP. Users logging into EP will have the ability to view Infoview and launch reports from Infoview.
Report access will be controlled using Infoview Folders. Better option for Power users who will need to create new WebI documents, schedule existing documents etc.
Real Experience. Real Advantage.
43
[ Learning Points
Advanced techniques within WebI to create User friendly reports. Options to implement security for a BOBJ/BW Implementation System Landscape/technical considerations for BOBJ/BW Implementation. Report deployment options
44
[ Best Practices
Prior to Project Implementation design a System landscape that works for your organization and perform a hardware sizing. Develop a clear security strategy for your BOE/BW implementation.
45
[ Key Learnings
Technical landscape design considerations Advanced techniques within WebI. Different options and considerations for BOE security Report deployment strategy. Performance considerations
46
[ Questions
47