SAP #BOBJ #BI 4.1 Upgrade Webcast Series 2: Best Practices

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 1Customer
SAP BusinessObjects BI 4.1 Upgrade
Webinar Series
BI 4.1 Upgrade and Update – Best
Practices
Presenter: Sathish Rajagopal
SAP BI Solution Management
Brought to you by the Customer Experience Group

SAP BusinessObjects BI Platform 4.1 Upgrade
Enablement
We bring to you all that you need to
successfully upgrade to the SAP
BusinessObjects BI Platform 4.1.
On SCN, you can find a BI 4.1 Upgrade
Overview and other resources at:
http://scn.sap.com/docs/DOC-56525
Webinars will complement these
published resources:

Sathish Rajagopal
Director, Solution Management - BI Solutions GTM
SAP Labs. USA.
Upgrading to SAP BusinessObjects BI 4.1
July 30 2014

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the
permission of SAP. This presentation is not subject to your license agreement or any other service or subscription
agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation
and SAP's strategy and possible future developments, products and or platforms directions and functionality are all
subject to change and may be changed by SAP at any time for any reason without notice. The information in this
document is not a commitment, promise or legal obligation to deliver any material, code or functionality. 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. This document is for informational
purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP´s willful misconduct or gross negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Legal disclaimer

What to expect from this session?
Why to Upgrade
 Evolution of BI – Requirements & Technology
 Value proposition – top reasons to upgrade
Getting ready for your migration - upgrade
 Planning
 Pre-upgrade technical considerations
Migration - Upgrade challenges & Lessons Learned
 Common Challenges
 Lessons Learned
 Customer success stories

Evolution of BI
• The Requirements
• The Technology

7© 2014 SAP AG or an SAP affiliate company. All rights reserved.
The Forrester Wave™: Self-Service Business Intelligence Platforms, Q2 2012
Market conditions and customer expectations
are changing rapidly
Volatility
Globalization
Cost conscious
New generation

The reality of the Internet of Everything
1 billion
Facebook
users
4 billion
YouTube views
per day
Data
doubles
every 18
months
15
billion
web-enabled
devices
5 billion
in emerging
middle class

9© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Nucleus Research, Gartner, Forbes, Fortune Magazine, Forrester
The Forrester Wave™: Self-Service Business Intelligence Platforms, Q2 2012
Key Trends shaping the future of BI
33% 80%
of BI consumed on handhelds
in 2013
of information needs handled
by end users
$1
$10.66
Spent on BI Return
>10x ROI

10%
75%
Use Analytics
Today
Need
Analytics
by 2020
Nucleus Research, Gartner, Fortune Magazine
Unlocking the value of Big Data
Ability to manage and
consume all data is getting
harder
Not utilizing all the
information out there
Not leveraging the power of
collective insight
Missing new insights
IT is not agile enough and
the business wants to get
involved
=

Analytics solutions from SAP
Agile
Visualization
Advanced
Analytics
Big Data
Mobile
Collaboration
Cloud
Enterprise
Business Intelligence

Value Drivers of SAP BusinessObjects BI4.1
Native
SAP
HANA
support
Designed to
support
future
innovations
Mobile
Upgrade
Ready
Reduced
TCO
DeskI
Compatibility
Native
SAP
BW
support
Focus on
Quality

Getting ready to upgrade
• Planning – how to best plan my migration

BI 4.1 is more than a technical upgrade…
BI 4.1 is 64 bits
• The XI platform was designed to squeeze the suite within a 32 bits architecture
• BI 4.1 is designed to take full advantage of modern hardware and memory by 64 bits technology
BI 4.1 is architecturally different from the XI platform
• The XI platform was a collection of applications all using their own connectivity stack
• BI 4.1 shares a new common Semantic Layer and Dedicated Services for data connectivity

BI 4.1 is more than a technical upgrade…contd.
BI 4.1 has a larger footprint due to new services and applications
• BI 4.1 is designed for the modern infrastructure – do not expect to run this on the same hardware
• BI 4.1 is designed as a first-class and highly integrated solution to SAP clients
• BI 4.1 has new components out-of-the-box – Analysis, Monitoring, Native BICS connectivity, Multi Source Universe,
Exploration Views, Mobility, HTML5 Dashboards, etc.

General upgrade path & process
BI 4.1
BOE XI 3.x
BOE XI R2 SP2+
BOE XI
CE8, CE9,
CE10
E5, E6
Main Steps:
 Setup the new landscape with the new software version
 Move the BI content from the existing system to the new one
BI 4.0

Define a manageable scope
Technical
or functional?
Check your
upgrade path
Identify a
target
Stay
focused
Technical Upgrade
existing applications
as-is to the new
platform
Functional Design a
new BI application with
BI 4.0
Technical Identify one
good BI application
candidate for upgrade
Functional Identify a
new business need to
be served
Technical Check if all
elements of the BI
application can be
upgraded
Functional
N/a due to design
phase
Upgrade less critical
apps first to get familiar
with the process
Never try to both
upgrade and introduce
new functionalities in
the same project
Iterate on smaller
scopes

Update your skills
Administration
 Architecture design
 Sizing
 Upgrade process
 LCM process
 Portal and customization
BI Applications
 Choice of client tool
 Data Federation
 Access to SAP
NetWeaver BW
 OpenDocument and drill-through
 Portal and workspaces
Operations
 Setup and configuration
 Tuning
 Backup and restore
 Traces and diagnosis
 Audit and monitoring
 Updates and patching
BI 4.1 is better, BI 4.1 is different XI R2, XI 3.x best practices may not apply

Getting ready to upgrade
• Technical considerations before executing your
upgrade

Be aligned with SAP’s product roadmap & strategy
- Support maintenance streams
End of mainstream maintenance dates for:
• SAP BusinessObjects Enterprise 5.x/6.x & CE9.x/10.x = 2009 or before
• SAP BusinessObjects XI R2 = June 2010
• SAP BusinessObjects XI 3.0 = March 2013
• SAP BusinessObjects XI 3.1 (SP7) = December 2015
End of support
• SAP BusinessObjects XI 3.0 = March 2015
• SAP BusinessObjects XI 3.1 (SP7) = December 2017
SAP’s public roadmaps on SAP Service Marketplace: www.service.sap.com/roadmap
SAP’s release strategy for large enterprises: www.service.sap.com/releasestrategy
SAP’s maintenance schedule : https://websmp210.sap-ag.de/bosap-maintenance-schedule

• What’s an “SAPS”?
• Hardware-independent performance unit to measure 200 business
order items
per hour
• Estimator, not analyzer
• Starting point only
• Outputs are not numbers you can blindly deploy with
• Not a replacement for expert advice!
• Tool limitations
• Test results were not linear, so such a model is only valid with
specific ranges
• Does not take into account fault-tolerance, clustering, scale out, or
topology
Importance of Sizing
Sizing portal : www.sap.com/bisizing
Apache split for BI 4.1: https://scn.sap.com/docs/DOC-51552

New in BI 4.1 – Role of Adaptive Processing Server (APS)
The APS hosts a number of services simultaneously
 Out-of-the-box installation will run all services in a single APS
 Enable an up-and-running system
 Needs to be reconfigured for systems beyond DEV
Production systems and the APS configuration
 Enable increased performance by splitting APS to dedicated tasks
 Enable stability by assigning appropriate amount of RAM for the task
 Make sure to follow best practices
APS best practices document - https://scn.sap.com/docs/DOC-31711

What about my Deski documents –
Desktop Intelligence end-of-life announcement*
Desktop Intelligence XI 3.1 is the last commercial version
 SAP BusinessObjects Business Intelligence 4.1 does not include Desktop Intelligence
Desktop Intelligence will continue to be supported on XI 3.x
 Mainstream maintenance: Until 2015
 Priority-One support: Until 2017
DCP (Desktop Compatibility Pack)
 Within BI 4.1, SAP provides the ability to “upgrade” your DeskI document into the BI 4.1 CMS
 This will not replace the need to convert DeskI into WebI, but will enable you to shorten the upgrade into BI 4.1 and
postpone the conversion for a later timeframe
The official end-of-life statement is available on SAP Service Market Place:
https://websmp201.sap-ag.de/bosap-lifecycle

Desktop Intelligence compatibility pack
• Desktop Intelligence Compatibility Pack (DCP)
• Will be delivered in FP 6.1
• The DeskI Client can now connect to an SAP BusinessObjects Business
Intelligence 4.1 CMS
• Introduce a Light Schedule functionality using the Windows scheduling
functionality
• DeskI documents will be listed only in the Central Management Console
(CMC) for administrative purposes only
• Minimum deprecation of DeskI Client functionality
• Only client-side consumption of .rep content
BI 4.1
Fix Pack 6.1
(with DCP)
DeskI
XI 3.1 SP6

Security upgrade (continuity in the security model since XI R2)
XI R2  BI 4.1
Continuity + new features have been added
since XI R2
XI 3.x  BI 4.1
Security model is the same as the one of XI
3.x
 Set up rights at the root folder
 Specify the new “owner right” for existing
products
 Specify rights with new products (WRC, IDT,
LCM, etc.)
 Simplify your security model by:
 Creating Custom Access Level
 Using selective enforcement of rights (Objects
or Sub Object)
 Specify the new “owner right” for existing products
 Specify rights with new products (IDT, LCM, etc.)
 Simplify your security model with CMC tab-
level security for delegated administration
In BI 4.1, you have to: In BI 4.1, you have to:

Migration – Upgrade Challenges & Lessons Learned
• The common challenges

Common challenges – concerns - questions
All these new features sounds nice, but I have challenges to upgrade my current BusinessObjects XI platform into BI
4.1 - WHY?
 I do not need new features, but am I running out of support?
 I have loads of Desktop Intelligence documents
 I have a lot of reports using the MDX connection to BW
 I cannot find the Import Wizard to enable my upgrade
 My XI R2/XI 3x LCMBIAR file fails to be imported in BI 4.x
 I do not want to convert my Crystal Reports 2008 into Crystal for Enterprise

Common challenges – contd.
 I have heard the new release is unstable, has product quality issues, not performing
 We don’t want to pay additional software license & maintenance fee
 Upgrade is very time consuming and expensive

Migration – Upgrade Challenges & Lessons Learned
• Lessons Learned & Customer
Success Stories

Lessons Learned & Customer Success Stories - #1
Customer:
Large CPG Customer in NA
Background:
• Leverages SAP BusinessObjects BI in all areas of the business
• The data source is SAP BW
• Upgrade driven by the customer BI Center of Excellence
• Top 10 IT innovator per InformationWeek
• Information Technology seen as a competitive advantage
• Always looking at new solutions to gain an edge on the business
• Wanted to benefit from BI4 innovations ASAP

Key drivers for upgrade - Business Drivers:
 Enhanced mobility : Marketing needed reports on iPad
 Enhanced Explorer experience with Exploration Views
 Improved overall performance: run-time reduced by half on basing our Webi reports of BICS
Technical Drivers:
 Streamlined authoring. Direct BICS access from all clients
 Auditing and usage. 3.1 had no option, to analyze usage of Dashboards/Webi
 Built-in Monitoring

Upgrade strategy used:
• Upgrade applications / projects from existing source system (BOE XI 3.1) to the target system (SAP BI 4.x)
• Start new projects with new features / functionalities in the new environment (SAP BI 4.x)
Pros & Cons:
 Great risk management
 Virtually no down time
 Two environments to manage
 Users may have to connect to two different systems
Lessons Learned:
• Iterate on small cycles - decoupling the technical upgrade from the new features was a good choice
• Installation and configuration changes / enhancements compared to BOE XI 3.x
• Need to have better patching strategy
• Working around product issues and be proactively aware of the product changes
• Weekly project meeting with SAP was helpful

Customer:
International Pharma in EMEA
Background:
• Customer deployed BOE XI 3.1 in 2010
• Upgraded 120+ projects using the shared environment (now over 200 using the new version)
• 66,000+ users, 2,500+ universes, tens of thousands of reports
• Started to evaluate BI 4 in Oct 2011
• Started testing upgrades from Sep 2012
• Incremental upgrades began in 2013 – three planned increments (Jan, Mar and Apr)
• Upgraded from XI 3.1 to BI 4.0

Upgrade constraints:
• Downtime would only be allowed during the weekend (Sat 2am till Sun 8pm)
• All environments had to have successful upgrades for a project to go-live
• There was to be no parallel running of versions for projects
• The project owners had to choose which upgrade wave they were in
• Each project has the chance to test how their content would behave after an upgrade

• Sandbox testing
• System / base security setup
• Wave / phased incremental approach
• Run reposcan in advance of first increment
Lessons Learned:
• Set up a migration test server
• Setup dedicated user on source system
• Utilize existing security model to control dependency calculations. Post upgrade, re-check security
• Get the fastest file share technology you can get for FileStores
• Disable all server processes you don’t need at the beginning of downtime and before you run reposcan
• Don’t forget to pause recurring schedules before upgrade

Customer:
CPG customer in APJ
Background:
• Upgraded from SAP BusinessObjects XI3.1 to
SAP BusinessObjects BI4.0
• Upgraded from SAP BW 7.01 to SAP BW7.30
• Estimated ROI – 207% over 5 years
• Mobile BI applications – Rolled out to Exec
• Enhanced Self-Service BI capability
Upgrade challenges:
• July 2010 Corporate Demerger (former parent
company )
• Just get it done by October 2011!
• 12 Years of shared IT systems and service
• SAP BW implemented in 2000 – Version 1.x (?)
• SAP BW 7.01 and SAP BusinessObjects XI R 3.1
• Many Legacy Issues
• Lack of confidence in BI initiatives and delivery
• Smaller BI Team
• Do more with less
• Cost-Obsessive Business
• Transition BEFORE Transformation

• Solid planning
• Estimating cost properly against the ROI
• Tools selection - choosing the right tool for right purpose / scenario
Lessons Learned:
• Beware the hidden costs of interfaces
• Sometimes less is more
• Train and engage key users (build partnership)
• Data Warehouse structures can make reporting easier
• Watch out for front-end patch levels (SAP GUI and BEx)
• Read your license agreement carefully

Customer:
Large B&FS customer in NA
Background:
• Migrating from SAP BusinessObjects Enterprise 3.1 to
SAP Business Intelligence Platform 4.1 release.
• Main data sources: Teradata, Oracle & Others
Migration Size: 0
• Number of objects in the repository: around 200,000
• Number of (user) groups: 800
• Number of users: 13,000
• File Repository Size: 450GB
Upgrade drivers – key business & technical drivers:
• Mobility
• BOE Architecture Enhancements
• Leverage Latest Innovations
• System Maintenance and Administration

Upgrade strategy used - Four steps process:
• Size and bring-up new SAP BI 4.x environment
• Migrate contents from BOE 3.1 to SAP BI 4.x (test / mock and actual migration - incremental)
• Test / validate the applications
• Promote applications to Production and release them
Lessons Learned:
• Skills issue – learn and get trained
• Beware of the product changes and known limitations ahead
• Proper planning is important (with all key factors taken into consideration)
• Proper sizing is very important
• Updating skills / training the BI / IT resources
• Upgrade strategy with clear workflow might sound simple but everyone in the team should be aware of

Key Links
 Upgrade microsite
www.sapbusinessobjectsbi.com
 BI Innovation Value Calculator
www.sap.com/BIcalculator
 BI Upgrade Value Calculator
www.sap.com/BIupgradecalc
 Web Intelligence calculation engine changes
 BI Platform Features by version matrix
http://scn.sap.com/community/bi-platform/blog/2013/02/13/bi-platform-feature-by-version-matrix

To summarize…
 Don’t miss the opportunity….understand the changing nature of BI and take advantage
the latest innovations from SAP
 Do a migration assessment and have a proper plan ready
 Be aware of the technical considerations
 Understand the common challenges in migration
 Learn how others have done it

© 2014 SAP AG or an SAP affiliate company. All rights reserved.
For Further Comments & Questions:
Sathish Rajagopal – BI Solutions GTM
Email: Sathish.rajagopal@sap.com Twitter: @srajagpl
Merlijn Ekkel – BI Solutions GTM
Email: Merlijn.Ekkel@sap.com Twitter: @MEatSAP

SAP #BOBJ #BI 4.1 Upgrade Webcast Series 2: Best Practices

Recommended

Recommended

More Related Content

More from SAP Analytics

More from SAP Analytics (20)

Recently uploaded

Recently uploaded (20)

SAP #BOBJ #BI 4.1 Upgrade Webcast Series 2: Best Practices