LCM208 Best Practices For Upgrading TP SAP Netweaver BI 7.0

LCM208
Best Practices for Upgrading to

SAP NetWeaver BI 7.0
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 2007, SAP TechEd ’07 / UP350 / 2

Contributing Speakers
Roland Kramer
NetWeaver Advisory Office, BA COO EMEA, SAP AG
Ron Silberstein
Platinum Consultant, SAP NetWeaver RIG, SAP Labs

Learning Objectives
As a result of this workshop, you will be able to:

Develop an upgrade strategy that fits your organization’s needs
Understand the system landscape aspects of SAP NetWeaver BI 7.0
Perform the upgrade preparation steps (and post-upgrade steps)
using the ASU toolbox
Understand key preparation steps for the BI upgrade
Understand key post steps for the BI upgrade
Describe how the BI Accelerator fits into your system landscape and
consider it in your upgrade project plans
Understand how the new Java environment for BI-Java is planned
and implemented to run the new functions for NetWeaver 7.0 BI
Inform upgrade project planning with an understanding of key factors
influencing scope, timeline, resource requirements, and complexity of
the overall SAP NetWeaver BI upgrade process

Overview
SAP NetWeaver BI 7.0 Upgrade Project Basics
Upgrade Preparation & Post-Steps w/ the ASU Toolbox
SAP NetWeaver BI 7.0 System Landscape
SAP NetWeaver Business Intelligence Accelerator
Summary
Overview
Summary
SAP NetWeaver BI 7.0 Positioning
An enabler technology for analysis and reporting In the age of “information democracy” every employee is
against data from SAP and non-SAP applications. (potentially) a consumer of BI applications. SAP NetWeaver BI
SAP NetWeaver BI is a complete enterprise extends the reach of BI by providing business user-oriented
Business Intelligence and Analytics platform. easy-to-use UIs as well as reliable and fast response-time
performance.
SAP NetWeaver BI
provides a foundation for reporting and
analytics in business applications,
extends the reach to masses of end-
users, integrates planning into user
interfaces and services, and pushes
forward its role as a strategic data
warehousing platform
As of SAP NetWeaver BI 7.0, planning and simulation are The information provided and stored in a modern data warehouse
a natural extension of BI. This is nothing new from the must be current, complete, and represent an enterprise view of your
business process point of view, but it is currently not entire organization to ensure that decisions are accurate, strategic,
adequately reflected in most of the BI product offerings. and timely. SAP NetWeaver BI further supports strategic deployment
In SAP NetWeaver BI 7.0 integrated BI and planning as an enterprise-wide data warehouse: Easier administration and life
solution is provided: Common user interfaces, design cycle management, enhanced data transfer processes,…
tools, services, engines, persistency, meta data,…

Major Themes in Implementing SAP NetWeaver BI 7.0
The new version of BI is a MAJOR RELEASE for SAP’s

Business Intelligence solution
Some major areas of relevance: utilizing the new technology
New BEx runtime (based on Java and SAP NetWeaver Portal)
Next generation of front-end reporting and analysis tools
New dataflow concept
New analysis authorizations
BI Accelerator
New BI-integrated planning
Near-Line Storage
... many, many other new features and functionality
Important concept: the coexistence strategy – this means

that you can perform a ‘technical upgrade” project (in the
short-term) and afterwards, continue to run the system just
like your 3.x system*. In subsequent project phases, you can
migrate to and utilize the new 7.0 features, functionality and
technology!
* main exception – BI statistics content

New Technical and Functional Features (I)
New ABAP password rules: see SAP Notes 862989 and 1023437
Tip: Set the parameter login/password_downwards_compatibility >= 3
New ABAP OO programming guidelines - necessary for
enhancing new DTP and transfer rules
New RFC behavior in SM59 - Classical qRFC Version or qRFC
NetWeaver
New BI lock server: see SAP Note 928044
Tip: abap/shared_objects_size_MB >= 128 and enque/table_size = 25000
New Administrator Workbench transaction RSA1
Guide
– Tip: use RSA1OLD and lock RSA1
– Tip: InfoPackage Groups are still available with RSA1OLD
New BI Authorizations set in SPRO (maintenance in RSECADMIN)
– If you used an authorization concept in SAP BW 3.x, switch back to “obsolete
Concept with RSR Authorization Objects” during the technical upgrade
– Important! After the technical upgrade, switch back to the new concept and
see SAP Note 820183 and 923176

New Technical and Functional Features (II)
New Frontend Components (BEx Suite with SAP NetWeaver 7.0)

– Tip: Block new frontend components in transaction RS_FRONTEND_INIT in
the field QD_EXCLUSIVE_USER (see SAP Note 962530).
– Tip: Which BEx Analyzer version is called by RRMX?
Transaction RRMX_CUST (see SAP Note 970002)
In SAP BW 3.x a formula variable is replaced before the
aggregation. In BI 7.0 it is replace afterwards. This causes
changes in queries:
see SAP Note 1005772
Improving performance for MDX and DataStore object:
see SAP Note 1016067
New Handling of dialog and batch processes with RSBATCH
– Tip: Change to always run in batch mode (can be switched)
– Tip: All other are jobs only available in batch mode, apart from
ODSACTIVAT, ODSSID, and ODSREQUDEL
– Tip: New DTP Processes in batch mode only

New Technical and Functional Features (III)
Convert the data sources and the PSA to the new DTP process:
– run report RSSM_CREATE_REQDONE_FROM_SEL
– run report RSSM_HASH_ENTRIES_CREATE for all requests
– run report RSSTATMAN_CHECK_CONVERT_DTA
– run report RSSTATMAN_CHECK_CONVERT_PSA
Redefine BI statistics new with SAP NetWeaver 7.0: see SAP
Notes 934848 and 964418
– convert to the new structure according Notes 1005238 and 1006116
Implement usage type AS Java for SAP NetWeaver 7.0
Tip: Apply usage types EP, BI Java, DI (optional) for the following software
components: Integrated Planning, EP with BI Java, Visual Composer (xApps
Analytics)
Implement the BI Accelerator (on separate hardware, only
ABAP needed): see SAP Note 883726
– estimate the memory of an BIA Index according Notre 917803 and use the
sizing spreadsheet from Note 1010267

Upgrade Drivers: SAP NetWeaver BI Release Strategy
Information from Service Marketplace alias releasestrategy

End Mainstream End Extended
Version
Maintenance Maintenance
SAP BW 2.0B Dec 2005 Dec 2005
SAP BW 2.1C Dec 2005 Dec 2005
SAP BW 3.0B Dec 2006 Dec 2006
SAP BW 3.1C Dec 2006 Dec 2006
SAP BW 3.5 (NetWeaver 2004) Mar 2010 Mar 2013
SAP NetWeaver BI 7.0 Mar 2013 Mar 2016

Overview
Summary
Key Upgrade Project Preparation Steps
Review new features of SAP NetWeaver BI 7.0

Define primary upgrade drivers, build a strong business
case, secure executive sponsorship
Determine the project’s scope (i.e. “technical upgrade” first,
BIA, analysis authorizations, etc)
Formulate plan for short, medium and long-term upgrade
project phases
Build a project team comprised of the right skill-set, and
secure the budget
Plan your system landscape, consider any sizing
implications, review platform requirements
Define your change management process (deploy
developments, transport strategy: break fix path, etc)
Define testing strategy - includes testing upgrade procedure
itself, validation testing, potentially stress / volume testing
Make moving to analysis authorizations a priority
Determine your front end roll-out strategy

“Technical Upgrade” Project Basics
Upgrade project focuses mainly on basis procedures and

necessary testing
Following the upgrade, the user experience is unchanged –
system functions the same as 3.x
Only significant exception to “coexistence strategy” – BI
statistics content (old BW statistics obsolete after upgrade)
Enables quick adoptions of BI Accelerator
No user training needed for go-live
Phased project plan – short term, medium, long term makes
sense to exploit new features, functionality
Plan to migrate to analysis authorizations in “next steps”
(highly recommended)
Develop phased project plan for migrating high priority data
load scenarios to new dataflow concept “one at a time”
System landscape must be properly in place before for front-
end rollout (and use of BI Integrated planning)
Develop a sensible front-end rollout strategy (new generation
of BEx reporting and analysis tools)
Utilize other new features and functionality in phased project
plan approach

Typical Milestones: Upgrade to SAP NetWeaver BI 7.0
Project Preparation Steps
Technical Preparation Steps

Core technical
Technical Upgrade Procedure: PREPARE
upgrade project
Technical Upgrade Procedure: SAPup steps
Post-Upgrade Technical Activities
BI Statistics Technical Content Installation
BI Accelerator Implementation
Migrate to Analysis Authorizations Project phases

Incremental Migration: New Dataflow Concept necessary to
implement new
System Landscape: Portal / Java Integration features,
functionality,
Roll Out New BEx Tools (Including BEx web)
technology
Use of Other New Features (BI-IP, Near-Line, etc)

Example Project Timeline: Technical Upgrade & Implement BIA -1-

Example Project Timeline: Technical Upgrade & Implement BIA -2-

Review Technical Requirements
Technical Requirements:
9 Check the Product Availability Matrix at SAP Service Marketplace alias “PAM” early in the
upgrade planning process
Note: For Oracle customers, Oracle 10g is required for SAP NetWeaver 2004s BI; for MS-SQL
either MS-SQL 2000 or 2005 can be utilized
9 Check hardware sizing requirements: See SAP Service Marketplace alias “sizing”. Utilize the
Quicksizer as needed, and consider Portal / Java requirements
9 Check the software requirements in the Upgrade Guide (recent example):

Plug-in Information: SAP ERP Source Systems
Caution: Never upgrade your Plug-in when you have data in SM13 or in the Delta Queue!
SM13 and RSA7 have ALWAYS to be EMPTY BEFORE you apply any changes to communication
structures, extract structures or any referenced Data Dictionary object or BEFORE you upgrade
your Plug-in!!! SM13 and RSA7 have to be EMPTY also when you apply Plug-In Support Packages!
NOTE: New and extended interfaces for integrating SAP R/3, SAP R/3 Enterprise, and SAP ERP
Central Component (SAP ECC) are no longer delivered with their own add-on (SAP R/3 Plug-In). As
of SAP ECC 6.0, they are contained directly in SAP ECC. PI 2004.1 is the final separate delivered
SAP R/3 Plug-In release. See SAP Service Marketplace alias “r3-plug-in”. Note PI 2003.1 is out of
maintenance as of June 2005.
SAPup Strategies Downtime Minimized / Resource Minimized
Data load and the upgrade: data load is available without restriction PREPARE and up
to the beginning of SAPup (and possibly during the first part of SAPup depending on
strategy selected)
PREPARE
PREPARE can be run well in advance of SAPup (i.e. a week), to give time to resolve issues that may arise
Re-running PREPARE directly before SAPup is a good final check
SAPup: downtime minimized

Productive use of SAP NetWeaver BI possible while some SAPup phases are running,
including data load and query (up to MODPROF_TRANS). Outage begins at EU_IMPORT phase
Balance of system resources allocated to productive system use and SAPup processing
Longer end-to-end time for total upgrade procedure (as little as 6 hours, dependant upon
various factors i.e. CPU speeds, etc)
Cessation of data load at beginning of SAPup generally recommended, however
SAPup: resource minimized

No productive use of SAP NetWeaver BI possible while some SAPup phases are running: no
query nor data load possible during entire SAPup procedure
All system resources dedicated to SAPup processing
Shorter end-to-end time for total upgrade procedure (outage may be 24 hours or more)

Overview
Summary
ASU Toolbox: Manual Actions Processes, Automation Processes
Goal: Change operations are either automated or guided manual

actions
Manual actions are described for end users
– Attributes allow precise determination of relevance.
Establish an ongoing process to collect the manual steps, guarantee quality.
Establish a process to automate the manual steps
– KPI definition and progress monitoring
– Framework by NetWeaver Software Logistics
– Content by component owners
– Governance and consulting process
Goal: Improve upgrade procedure even after shipment

Automated data gathering and feedback to SAP:
– Î Know performance + problems
Automated integration of upgrade fixes into shipped procedures:
– Î Continuous improvements
Continuous update of the content for the manual step wizard
“Up-to-date” upgrade:
– Integration of SPs (including application automation features)
– Tool update

New ASU (Application Specific Upgrade) Toolbox for BI
Less then
1MB coding!
Initial Screen of ASU Toolbox – Easy Access to:

Create a new task list
Automatically jump to preliminary steps (prior to PREPARE)
Automatically jump to post steps (after SAPUP)
Go into task list
Implement SAP notes
Example Details of the ASU Toolbox Task List – PRE -
Example of PRE
upgrade steps in
task list
select row, hit
execute to jump
to screen to
execute step or
relevant
information
Add UserRemark and update Status Change
can set status
easy to jump to
associated note
Ability to set
some tasks for
fully automated
in batch

Example Details of the ASU Toolbox Task List – POST -
Example of POST
upgrade steps in
task list

ASU XML Maintenance -1-
Here you can add,

change, or
remove steps
from the task list
of the selected
ASU scenario

ASU XML Maintenance - 2 - Example
Example of
details when
changing a step
from the task list
– in this case the
details for a note
are updated
You can change

other step types
too, i.e.
transactions,
program calls,
etc

ASU toolboxSearch
Enterprise for BI
Example PRE Steps: SE14 - Invalid (Temp) Tables & Clean Up
sap_drop_tmptables
DBDIFF
nametab
Example PRE Steps: RSUPGRCHECK - Note 1032367

Example PRE Steps: ANALYZE_RSZ_TABLE - Note 1020826

Key Post Activities Following SAPUP - 1 -
Check note 563201 in advance and use SAP_FACTVIEWS_RECREATE

to create dropped fact views again.
Activate the source systems again (see note 538052 for details).
Choose RSA1 Î source systems Î right mouse click on the source
system Î activate.
If needed: Run RSD1Î repair Info Objects.
Run SE38 Î RS_TRANSTRU_ACTIVATE_ALL to activate all transfer
structures again. See also Note 1027827.
Run SE38 Î RSAU_UPDR_REACTIVATE_ALL to reactivate all active
update rules. See Note 631601 for details.
If needed: run report RSDG_MPRO_ACTIVATE for the activation of
MultiProvider. See Note 897735 for details.
Filling the repository cache for delivered Objects is obsolete from
SPS10 onwards.
Activate the BEx history with transaction RS_PERS_ACTIVATE.

Key Post Activities Following SAPUP - 2 -
Run the Report RRINCLTAB_REBUILD according Note 922467.

Please make sure that you also have the corrections applied before
starting the Report.
Urgently check Note 906789: Upgrade to 7.X BW - NetWeaver 2004s
and follow the described Procedure. See also Note 1020303!
– run RSSM_CREATE_REQDONE_FROM_SEL
– run the RSSM_HASH_ENTRIES_CREATE report for all requests
– run the report RSSTATMAN_CHECK_CONVERT_DTA
– run the report RSSTATMAN_CHECK_CONVERT_PSA
Run the Report COM_PRODUCT_UPGRADE (from SPS10 no errors)
Run Report RSR_VARIANT_XPRA for the Query Variants (Note 953346)
and check also with Report ANALYZE_MISSING_ELEMENTS.
Run Report RSR_MIGRATE_VARIANTS for variants created in BW 3.x
See Note 1003481 for Details.
Note 996602 - Modificat. for time characteristics disappear after upgrade
In case of errors with technical characteristics run Report
RSDG_XPRA_IOBJ_TO_NW05, see Note 939484 for Details.

Key (Web-Specific) Post Activities Following SAPUP
Check the WDEBU7 unit “Web AS 7.0 Settings for BI“

If you still use a 2.x system, firstly you must carry out the migration
steps from 2.x to 3.x. You must consider all information and the
enhancements or restrictions that are mentioned there. Due to the large
conceptional differences between 2.x and 7.0 systems, you must decide
if it is effective to migrate by the different releases that occur between
these two releases - in most cases it is advisable to create new
corresponding elements with 7.0 tools.
Run report RSZW_CHART_MIGRATION_35 to convert first from 3.0B/3.1
BW system to convert the Objects to BW 3.5. You must install a
Windows based IGS 6.40 which held's the chart migrator in it. See Note
818240 for more details.
See also Note 959358 for new IGS settings after IGS >= 5 (currently 10)
After you migrated the Objects to BW 3.5, you must run report
RSZW_ITEM_MIGRATION_3X_TO_70 to convert the Objects into BW 7.0
representation in your system. See Note 832712 (library items) and
832713 (web templates) for more Details. This step is mandatory to use
the existing Objects with the new frontend tools. The complete BI-Java
customizing must be in place, like EP and BI-Java.

Key Post Activities Following SAPUP: BI Technical Content
Configuration of the
BI Administration Cockpit in
the IMG (Transaction SPRO)
This activity starts transaction
RSTCC_INST_BIAC
which links a report for automatic
installation of the Technical Content
activating all the Technical

Content objects that are assigned to
role SAP_BW_BI_ADMINISTRATOR,
including the relevant data flows.
Prerequisite:
Software component BI_CONT 7.0.3,
Support Package 4 or
Software component BI_CONT 7.0.2,
Support Package 7
It is recommended to install
BI_CONT 7.0.3 as BI_CONT 7.0.2 is
out of maintenance!
BI Monitoring with SAP NetWeaver Administration

Upgrade Project Considerations: New Analysis Authorizations
Analysis Authorizations: Migration Support

For security and clarity reasons make a „clean“ new setup „from the
scratch“ (much easier, less complex than in 3.x)
Otherwise:
ABAP program RSEC_MIGRATION (use transaction SA38)
No complete, automatic migration, but support
– The more complex the existing authorization concept, the more
manual migration work might be necessary
– Customer exits variables on nodes are migrated
– Customer-exit variables for 0TCTAUTHH cannot be migrated; the
respective hierarchy nodes must be assigned manually
– Intensive tests are highly recommended
– Runtime (10000 users roughly 1h)
Singular event, not for scheduling
During migration to the new authorization concept, the existing concept
won‘t be changed
Always check the latest corrections of the program RSEC_MIGRATION

Overview
Summary
System Landscape: The New BEx Suite with NetWeaver 7.0
SAP NetWeaver BI 7.0 features where Portal / Java /

BI-Java is required as technical foundation

Business Explorer Suite with NetWeaver 7.0
Enterprise Portal
KM
Visual
Composer BI
Kit Business Explorer Suite (BEx)
Information Broadcasting
BEx Web BEx Analyzer
BI Pattern
Web
Web Report MS Excel
Application
Analyzer Designer Add-in
Designer
BI Consumer Services
BEx Query Designer
BI Platform Analytic Engine Meta Data Mgr
UDI
SAP DB Service
JDBC XMLA ODBO Data Warehouse BAPI File XML/A
Query Connect API

Overview: Usage Types, Standalone Engines, Clients
Clients
Standalone Engines /
Usage Types Appliances
BI
accelerator
Key
Usage Type based

Usage Type based
on AS-ABAP and Standalone Engine
on AS-ABAP
AS-Java Physical
Optional Usage Optional Usage host
Optional
Type based on Type based on AS-
Standalone Engine
AS-ABAP ABAP and AS-Java
Usage Type based Third-Party

Tool/Client
on AS-Java Component Physical database
A+J with ABAP and/or
Optional Usage
Optional Java schema
Type based on System
Tool/Client
AS-Java
Usage Types AS ABAP, AS Java, and EP
AS ABAP
Contains all ABAP-based SAP Web AS functionality (software components
SAP_ABA, SAP_BASIS and SAP_BW)
– Data Warehouse Management
– OLAP processor
– Existing SAP BW 3.5 Web Runtime
– …
Internet Graphics Service (IGS) comprised
AS Java
Contains all Java-based SAP Web AS functionality (J2EE)
Universal Data Integration (UDI) and Metadata Model Repository (MMR)
comprised
– Universal Data Integration (UDI) is an independent component that is used for
data retrieval and does not require Usage Type BI Java
EP
Contains Portal
Requires Usage Type AS Java

Usage Types BI and BI Java
BI
Contains BI Content Add-On (software component BI_CONT)
Requires Usage Type AS ABAP
BI Java
Contains all Java- and Web Dynpro-based BI functionality
– New SAP NetWeaver 7.0 BI Web Runtime (including Analysis Item,
Formatted Reporting, Web Printing, PDF Export, …)
– New Planning Modeler for BI Integrated Planning
Requires Usage Type EP and AS Java
Adobe Document Services comprised
See Release Notes under http://help.sap.com/saphelp_nw04s

– IT Scenario Enterprise Reporting, Query, and Analysis
– IT Scenario Business Planning and Analysis Services

Business Explorer and Usage Type BI Java
How does Business Explorer relate to Usage Type BI

Java?
BEx Web and BI Integrated Planning require Usage Type BI Java
Usage Type BI Java is based on Usage Type EP and AS Java
How does BEx Web and BI Integrated Planning relate to

Portal and Java?
BEx Web runtime generates output for Web Browser
BEx Web requires Java-based Portal runtime functionality (for rendering
as iView, for System integration, etc.)
BI Integrated Planning requires Web Dynpro-based Planning Modeler
Î Functionality: BEx Web is using Portal as infrastructure and

platform (visible if desired, hidden if not)
Î Project considerations: BEx Web requires Java technology and not an
Enterprise Portal project
Î System Landscape: BEx Web requires Usage Type EP and AS Java

Installation Sequence of the AS-Java 7.00 Add-In (DS)
NetWeaver 7.0
Selected Java
Operating System Applications:
01
CI ABAP/JAVA (BIx) SLD
BI 7.00 JAVA 7.00 3 SLM
000, 001, xxx, 066 000
JAVA NWA
JDBC
ABAP 02 Selected
DBSL SCS Manager 1 usage types:
BI-Java
DI ABAP/JAVA
EP
Schema Schema (core)
ABAP JAVA 2
SAPBIx SAPBIxDB

MCOD Scenario with ABAP and JAVA on separate Instance
NetWeaver 7.0
Selected Java
Operating System Applications:
01 03
CI ABAP (BIx) CI Java (BJx) SLD
BI 7.00 JAVA 7.00 SLM
000, 001, xxx, 066 000
JAVA NWA
JDBC
ABAP 02 Selected
DBSL SCS Manager usage types:
BI-Java
DI ABAP DI Java
EP
Schema Schema (core)
ABAP JAVA
SAPBIx SAPBJxDB

Federated Portal Strategy with NetWeaver 7.0
Single Central Portal Content Federation

(1 portal) (2 .. n portals)
Consumer
Portal
Central
Portal
Producer Producer
Portal Portal
Application
ERP Application
Application
ERP Application Producer
Application Portal
Application
BI BI
Enabled using the Federated Portal Network

Federated Portal Network and BI: Architecture
Example SAP NetWeaver 7.0 BI System Landscape with Federated

Portal Network (1) Remote Role Assignment (*)
Consumer (2) Information Broadcasting
EP (3) Producer BI iView in Portal
KM
Content Content Studio
(4) BW iView in Portal Content
Studio
Portal
Content
(1) and (3) (1) and (3) (4)
Producer (2) Producer (2)
EP Portal KM EP Portal KM
Content Content Content Content
BI BI SAP BW 3.x
SAP NetWeaver 7.0 SAP NetWeaver 7.0
(*) Remote Role Assignment only supported with Federated Portal in SAP NetWeaver 7.0

Performance and Sizing Considerations
Moving Workload from AS-ABAP to AS-Java

In SAP NetWeaver 2004s, load is moved from AS-ABAP to AS-Java
BEx Web (BI-Java) generates load on Portal (AS-Java)
BI users generate more load on Portal than normal Enterprise Portal users
– Refer back to the one portal vs. two portal discussion earlier
Sizing your AS-ABAP and AS-Java systems

Usage Types AS-Java and EP require additional CPU and memory (overhead)
Minimum requirements for Usage Type AS-Java and EP is 2 CPUs and 4 GB of
memory*
BEx Web aspect of capacity planning analysis is re-focused to AS-Java

Performance and Sizing Considerations (cont.)
See SAP Note 927530 – BI Java sizing

Sample Sizing
Before upgrade, 100% ABAP (about 25% BEx) (*)
Upgrade requires about 25% more CPU and memory for Java (Portal) (125% in
total) (**)
After upgrade, 75% ABAP (without 25% BEx) and 50% Java (25% BEx)
Before After
(*) BEx Web percentage share based on performance analysis in your system
(**) Sample BI system with 8 CPU and 16 GB memory would require additional 2 CPU and 4 GB memory for
Java (Portal)

Recommendation
Use existing BI server

Based on load and performance tests, existing BI server should be
sufficient even with Usage Types AS Java, EP, and BI Java
Upgrade SAP BW 3.x to BI in SAP NetWeaver 2004s
Perform standalone installation on one server with two

different systems
Best combination of lowest hardware requirements and highest
flexibility for scalability (dialog instances could be scaled
independently)
Choose ABAP as User Management Engine (UME) configuration
Reduce administrator effort by using combined user persistence
Automatic configuration of UME is one advantage of Add-In Installation

Improved CTC (Central Template Configuration) for BI-Java

New Interface from SPS12 onwards and additional steps
More
…don Steps
’t hesita neede
te to c
o nt
d?
sugge act
stions us for mor
! e

Improved/simplified Input screen with SPS13/14
Less then
1MB coding!
Highly
by lea recom
ding S mend
“…I th
ink th A P ed
Temp e c he c consu
late In k in ltants
staller g time is o :
B
I-Java ver, let
do the th e
work!
”

CTCEnterprise
Installer for BI-Java
Search
Overview
Summary
SAP NetWeaver BI Accelerator Value Proposition
Very fast query Increased Stable query

response time quality of response time
information/
Performance Extended Independent of
improvements BI reach DB optimizer,
by factor 10 – 100 aggregates, ...
SAP NetWeaver BI Accelerator
Implemented for latest No aggregate

blade server hardware Significant maintenance, minimized
platforms reduction of roll-up/change run
operation
High scalability costs Low maintenance

SAP NetWeaver BI Accelerator Architecture
Business Any Tool

Explorer
BI Accelerator responds to queries:

joins and aggregates in run time
BI Analytic
Engine Query &
Response
… indexes loaded
into memory
InfoCubes
Indexing
Any … creates and stores

Data Acquisition
Source indexes for InfoCubes
SAP NetWeaver BI SAP NetWeaver BI Accelerator

BI Accelerator Installation
BI Accelerator Shipment
The BI Accelerator is only be available as an appliance (“in a box”)

Complete BI Accelerator pre-installed (!)
Standalone or fit into an existing customer rack
Blade servers with 64-bit Intel Xeon CPUs
Operating System (as of today)
– SUSE Linux SLES, 64-bit
– No support for other OS planned
Optimized storage included
Hardware Partners (as of today)
– Hewlett-Packard
– IBM
– Fujitsu-Siemens
Note: no restriction for the platform for the SAP NetWeaver
implementation (no concern about incompatibilities)

SAP NetWeaver BI Accelerator Appliance
Rapid Deployment Appliance Reduced Cost

of Operation
Instantaneous
operation Minimized
– Pre-Installed by maintenance
hardware vendor – Centralized
– Minimal monitoring through
configuration CCMS
requirements Easy scalability
Simple purchase through blade server
– Off-shelf hardware
Integration architecture
Quick setup for rapid Optimized hardware/software Affordable
implementation efficiency commodity hardware
– Combination of hardware Reduced license
components and
costs
configuration optimized for
high-end performance Minimized upgrade
risk

A New Experience For Information Worker
Business Intelligence Accelerator

Information to the masses
10x faster queries
Enterprise
Search
10x less expensive to acquire BI
Accelerator
20x less expensive to operate

1990 2006 Improvement
Changing the way users interact with
CPU 0.05 7.15 143x
MIPS/$ MIPS/$
enterprise information
Memory 0.02 5 250x
MB/$ MB/$
Addressable
Enterprise Search Memory 216 264 248x
Deep search and controlled access to

Network 100 10 100 x
Speed Mbs Gbs
business objects Disk

Transfer
5 130 25x
Self administration
MBPS MBPS
Speed

SAP NetWeaver BI Accelerator Sizing
Sizing
For existing installation
– SAP note 917803
– Report computes memory
requirements and disk
space (also runs on SAP
BW 3.x)
For new customer projects
– Enhancement of SAP
QuickSizer in progress
Hardware partners
– Translate the results into
concrete hardware set-up
– High availability setup:
Extra blade(s) required as
backup for automatic
failover

Overview
Summary
Key Points to Take Home
New SAP NetWeaver BI 7.0 front-end tools and BI-IP require the new
Java-based runtime as a technical foundation and is based on the
usage types BI, EP (EPC) and BI-Java
Use the new capabilities of the ASU (application specific upgrade)
toolbox with best practice content for BI
You can perform a ‘technical upgrade” project (in the short-term) and
afterwards, continue to run the system just like your NetWeaver
system without the usage of Java
If you utilize the “technical upgrade” approach, in subsequent project
phases migrate to and utilize the new 7.0 features, functionality and
technology to exploit the full benefits and potential
The improved CTC (central template configuration) for BI-Java
automates the complete connection process between Abap and Java.
Migrate to the new dataflow concept in a phased approach
Migrate to the new front-end tools in a phased approach
Setup the new analysis authorizations in an early project phase

Further Information
Î SAP Public Web:

SAP Developer Network (SDN):
http://www.sdn.sap.com/irj/sdn/bi
http://www.sdn.sap.com/sdn/forums
Î Business Intelligence Î BI in SAP NetWeaver 7.0
SAP Service Marketplace:

http://service.sap.com/upgrade-bi
http://service.sap.com/bi Î Media Library Î Technical Documents
Î Related SAP Education and Certification Opportunities

http://www.sap.com/education/ Î search:
WDEBU7 - Upgrade to NetWeaver 7.0 BI
TBW70D - BI - Delta Enterprise Data Warehousing & Reporting SAP NetWeaver 7.0
DBW70E - BI - Delta Enterprise Data Warehousing SAP NetWeaver 7.0
DBW70R - BI - Delta Reporting SAP NetWeaver 7.0

Latest Information at http://service.sap.com/upgrade-bi

Contact
Roland Kramer
NetWeaver Advisory Office EMEA
SAP (Switzerland) Inc.
Althardstrasse 80
CH-8105 Regensdorf
t +41 58 871 66 02
f +41 58 871 61 12
m +41 79 215 84 18
@ roland.kramer@sap.com
w http://service.sap.com/upgrade-bi
http://service.sap.com/bi =>
Media Library => Technical Documents

Q&A
THANK YOU FOR YOUR

ATTENTION !
QUESTIONS – SUGGESTIONS – DISCUSSION

Feedback
Please complete your session evaluation.
Be courteous — deposit your trash,

and do not take the handouts for the following session.
Thank You !

SDN Subscriptions Program
The SDN Subscriptions Program introduces the SAP
NetWeaver, Development Subscription for individual
developers. Available for purchase in Germany and the
United States.
Subscription gives you one year access to …
SAP NetWeaver platform software, patches, and updates
Development license for SAP NetWeaver to evaluate, develop and test
Standard software maintenance
Online sessions from SAP TechEd
Access to SAP Enterprise Services Workplace for testing
Premium presence in forums
Purchase the SAP NetWeaver, Development Subscription today

at the SAP Community Clubhouse, or online at
https://www.sdn.sap.com/irj/sdn/devsub
Visit us at the Community Clubhouse, show us you are a
subscriber, and get a gift!

Copyright 2007 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System
p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are
trademarks or registered trademarks of IBM Corporation.
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.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. 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.
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.”

LCM208 Best Practices For Upgrading TP SAP Netweaver BI 7.0

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

LCM208 Best Practices For Upgrading TP SAP Netweaver BI 7.0

Enviado por

Direitos autorais:

Formatos disponíveis

LCM208

Best Practices for Upgrading to

This presentation outlines our general product direction and should

© SAP AG 2007, SAP TechEd ’07 / UP350 / 2

© SAP AG 2007, SAP TechEd ’07 / UP350 / 3

As a result of this workshop, you will be able to:

© SAP AG 2007, SAP TechEd ’07 / UP350 / 4

© SAP AG 2007, SAP TechEd ’07 / UP350 / 7

The new version of BI is a MAJOR RELEASE for SAP’s

Important concept: the coexistence strategy – this means

* main exception – BI statistics content

© SAP AG 2007, SAP TechEd ’07 / UP350 / 9

 New Frontend Components (BEx Suite with SAP NetWeaver 7.0)

© SAP AG 2007, SAP TechEd ’07 / UP350 / 10

© SAP AG 2007, SAP TechEd ’07 / UP350 / 11

Information from Service Marketplace alias releasestrategy

SAP BW 2.0B Dec 2005 Dec 2005

SAP BW 2.1C Dec 2005 Dec 2005

SAP BW 3.0B Dec 2006 Dec 2006

SAP BW 3.1C Dec 2006 Dec 2006

SAP BW 3.5 (NetWeaver 2004) Mar 2010 Mar 2013

SAP NetWeaver BI 7.0 Mar 2013 Mar 2016

© SAP AG 2007, SAP TechEd ’07 / UP350 / 12

 Review new features of SAP NetWeaver BI 7.0

© SAP AG 2007, SAP TechEd ’07 / UP350 / 14

 Upgrade project focuses mainly on basis procedures and

© SAP AG 2007, SAP TechEd ’07 / UP350 / 15

Project Preparation Steps

Technical Preparation Steps

BI Statistics Technical Content Installation

Migrate to Analysis Authorizations Project phases

© SAP AG 2007, SAP TechEd ’07 / UP350 / 16

© SAP AG 2007, SAP TechEd ’07 / UP350 / 17

© SAP AG 2007, SAP TechEd ’07 / UP350 / 18

9 Check the software requirements in the Upgrade Guide (recent example):

© SAP AG 2007, SAP TechEd ’07 / UP350 / 19

SAPup: downtime minimized

SAPup: resource minimized

© SAP AG 2007, SAP TechEd ’07 / UP350 / 21

Goal: Change operations are either automated or guided manual

Goal: Improve upgrade procedure even after shipment

© SAP AG 2007, SAP TechEd ’07 / UP350 / 23

Initial Screen of ASU Toolbox – Easy Access to:

© SAP AG 2007, SAP TechEd ’07 / UP350 / 25

© SAP AG 2007, SAP TechEd ’07 / UP350 / 26

Here you can add,

© SAP AG 2007, SAP TechEd ’07 / UP350 / 27

You can change

© SAP AG 2007, SAP TechEd ’07 / UP350 / 28

© SAP AG 2007, SAP TechEd ’07 / UP350 / 31

© SAP AG 2007, SAP TechEd ’07 / UP350 / 32

 Check note 563201 in advance and use SAP_FACTVIEWS_RECREATE

© SAP AG 2007, SAP TechEd ’07 / UP350 / 33

 Run the Report RRINCLTAB_REBUILD according Note 922467.

© SAP AG 2007, SAP TechEd ’07 / UP350 / 34

 Check the WDEBU7 unit “Web AS 7.0 Settings for BI“

© SAP AG 2007, SAP TechEd ’07 / UP350 / 35

 activating all the Technical

© SAP AG 2007, SAP TechEd ’07 / UP350 / 37

Analysis Authorizations: Migration Support

© SAP AG 2007, SAP TechEd ’07 / UP350 / 38

SAP NetWeaver BI 7.0 features where Portal / Java /

New Frontend Components (BEx Suite with SAP NetWeaver 7.0)

Review new features of SAP NetWeaver BI 7.0

Upgrade project focuses mainly on basis procedures and

Check note 563201 in advance and use SAP_FACTVIEWS_RECREATE

Run the Report RRINCLTAB_REBUILD according Note 922467.

Check the WDEBU7 unit “Web AS 7.0 Settings for BI“

activating all the Technical

20x less expensive to operate

Deep search and controlled access to