lcm208 best practices for upgrading to sap netweaver bi 7 · pdf fileconsider it in your...

LCM208Best Practices for Upgrading to SAP NetWeaver BI 7.0

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

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.


Contributing Speakers

Roland KramerNetWeaver Advisory Office, BA COO EMEA, SAP AG

Ron SilbersteinPlatinum 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 needsUnderstand the system landscape aspects of SAP NetWeaver BI 7.0Perform the upgrade preparation steps (and post-upgrade steps) using the ASU toolboxUnderstand key preparation steps for the BI upgradeUnderstand key post steps for the BI upgradeDescribe how the BI Accelerator fits into your system landscape and consider it in your upgrade project plansUnderstand how the new Java environment for BI-Java is planned and implemented to run the new functions for NetWeaver 7.0 BIInform upgrade project planning with an understanding of key factors influencing scope, timeline, resource requirements, and complexity of the overall SAP NetWeaver BI upgrade process

OverviewSAP NetWeaver BI 7.0 Upgrade Project BasicsUpgrade Preparation & Post-Steps w/ the ASU ToolboxSAP NetWeaver BI 7.0 System Landscape SAP NetWeaver Business Intelligence AcceleratorSummary


SAP NetWeaver BI 7.0 Positioning

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

An enabler technology for analysis and reporting against data from SAP and non-SAP applications. SAP NetWeaver BI is a complete enterprise Business Intelligence and Analytics platform.

In the age of “information democracy” every employee is (potentially) a consumer of BI applications. SAP NetWeaver BI extends the reach of BI by providing business user-oriented easy-to-use UIs as well as reliable and fast response-time performance.

The information provided and stored in a modern data warehouse must be current, complete, and represent an enterprise view of your entire organization to ensure that decisions are accurate, strategic, and timely. SAP NetWeaver BI further supports strategic deployment as an enterprise-wide data warehouse: Easier administration and life cycle management, enhanced data transfer processes,…

As of SAP NetWeaver BI 7.0, planning and simulation are a natural extension of BI. This is nothing new from the business process point of view, but it is currently not adequately reflected in most of the BI product offerings. In SAP NetWeaver BI 7.0 integrated BI and planning solution is provided: Common user interfaces, design 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 technologyNew BEx runtime (based on Java and SAP NetWeaver Portal)Next generation of front-end reporting and analysis toolsNew dataflow conceptNew analysis authorizationsBI AcceleratorNew BI-integrated planningNear-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 1023437Tip: Set the parameter login/password_downwards_compatibility >= 3

New ABAP OO programming guidelines - necessary for enhancing new DTP and transfer rulesNew RFC behavior in SM59 - Classical qRFC Version or qRFC NetWeaverNew BI lock server: see SAP Note 928044Tip: abap/shared_objects_size_MB >= 128 and enque/table_size = 25000

New Administrator Workbench transaction RSA1 – 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

Guide


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 1005772Improving performance for MDX and DataStore object: see SAP Note 1016067New 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.0Tip: 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

End MainstreamMaintenance

End ExtendedMaintenanceVersion

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


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

Core technical upgrade project steps

Project Preparation Steps

Technical Preparation Steps

Technical Upgrade Procedure: PREPARE

Technical Upgrade Procedure: SAPup

Post-Upgrade Technical Activities

BI Statistics Technical Content Installation

BI Accelerator Implementation

Migrate to Analysis Authorizations

Incremental Migration: New Dataflow Concept

System Landscape: Portal / Java Integration

Roll Out New BEx Tools (Including BEx web)

Use of Other New Features (BI-IP, Near-Line, etc)

Project phases necessary to implement new features, functionality, technology


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


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


Review Technical Requirements

Technical Requirements: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

Check hardware sizing requirements: See SAP Service Marketplace alias “sizing”. Utilize the Quicksizer as needed, and consider Portal / Java requirements

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


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.

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!


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)

PREPAREPREPARE can be run well in advance of SAPup (i.e. a week), to give time to resolve issues that may ariseRe-running PREPARE directly before SAPup is a good final check

SAPup: downtime minimizedProductive 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 phaseBalance of system resources allocated to productive system use and SAPup processingLonger 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 minimizedNo productive use of SAP NetWeaver BI possible while some SAPup phases are running: no query nor data load possible during entire SAPup procedureAll system resources dedicated to SAPup processingShorter end-to-end time for total upgrade procedure (outage may be 24 hours or more)


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 shipmentAutomated 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

Initial Screen of ASU Toolbox – Easy Access to: Create a new task listAutomatically jump to preliminary steps (prior to PREPARE)Automatically jump to post steps (after SAPUP)Go into task listImplement SAP notes

Less then 1MB coding!


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 informationcan set statuseasy to jump to associated noteAbility to set some tasks for fully automated in batch

Add UserRemark and update Status Change


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


Enterprise SearchASU toolbox for BI


Example PRE Steps: SE14 - Invalid (Temp) Tables & Clean Up

sap_drop_tmptablesDBDIFFnametab


Example PRE Steps: RSUPGRCHECK - Note 1032367


Example PRE Steps: ANALYZE_RSZ_TABLE - Note 1020826


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 - 1 -


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 2004sand 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 upgradeIn case of errors with technical characteristics run Report RSDG_XPRA_IOBJ_TO_NW05, see Note 939484 for Details.

Key Post Activities Following SAPUP - 2 -


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 theenhancements 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 orSoftware component BI_CONT 7.0.2, Support Package 7It 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 SupportFor 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 schedulingDuring migration to the new authorization concept, the existing concept won‘t be changedAlways check the latest corrections of the program RSEC_MIGRATION


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

Visual Composer BI

Kit

UDI

XMLASAPQuery JDBC ODBO

Business Explorer Suite (BEx)

BEx Query Designer

Information Broadcasting

Web Analyzer

WebApplication

Designer

MS Excel Add-in

ReportDesigner

BEx Web

DB Connect BAPI Service

API File XML/A

BEx AnalyzerBI Pattern

BI Consumer Services

BI Platform

Data Warehouse

Enterprise Portal

Analytic Engine Meta Data Mgr

KM


Overview: Usage Types, Standalone Engines, Clients

Optional Usage Type based on

AS-ABAP

Tool/Client

Usage Type based on AS-ABAP

Optional Usage Type based on AS-ABAP and AS-Java

Usage Type based on AS-ABAP and

AS-Java

Optional Usage Type based on

AS-Java

Usage Type based on AS-Java

Optional Tool/Client

Standalone Engine

Optional Standalone Engine

Third-Party Component

SystemA+J

Physicalhost

Physical database with ABAP and/or Java schema

Key

BI accelerator

Usage TypesStandalone Engines /

Appliances

Clients


Usage Types AS ABAP, AS Java, and EP

AS ABAPContains 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 JavaContains 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

EPContains PortalRequires Usage Type AS Java


Usage Types BI and BI Java

BIContains BI Content Add-On (software component BI_CONT)Requires Usage Type AS ABAP

BI JavaContains 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 JavaAdobe 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 JavaUsage 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 BrowserBEx 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 andplatform (visible if desired, hidden if not)Project considerations: BEx Web requires Java technology and not an Enterprise Portal projectSystem Landscape: BEx Web requires Usage Type EP and AS Java


Installation Sequence of the AS-Java 7.00 Add-In (DS)

NetWeaver 7.0

Operating System

DI ABAP/JAVA

000JAVAJDBC

JAVA 7.00

CI ABAP/JAVA (BIx)

000, 001, xxx, 066

ABAPDBSL

BI 7.00

SchemaABAP

SAPBIx

Schema JAVA

SAPBIxDB

SCS Manager

01

02

2

1

3

SLD

SLM

NWA

BI-Java

EP (core)

Selected JavaApplications:

Selected usage types:


MCOD Scenario with ABAP and JAVA on separate Instance

SLD

SLM

NWA

BI-Java

Selected JavaApplications:

Selected usage types:

NetWeaver 7.0

Operating System

DI ABAP DI Java

CI Java (BJx)

000JAVAJDBC

JAVA 7.00

CI ABAP (BIx)

000, 001, xxx, 066

ABAPDBSL

BI 7.00

SchemaABAP

SAPBIx

Schema JAVA

SAPBJxDB

SCS Manager

01 03

02

EP (core)


Federated Portal Strategy with NetWeaver 7.0

Central Portal

ERP

BI

ApplicationApplication

Application

Single Central Portal(1 portal)

Enabled using the Federated Portal Network

Producer Portal

BI

Producer Portal

Producer Portal

ApplicationApplication

ApplicationERP

Consumer Portal

Content Federation (2 .. n portals)


Federated Portal Network and BI: Architecture

Example SAP NetWeaver 7.0 BI System Landscape with Federated Portal Network

(*) Remote Role Assignment only supported with Federated Portal in SAP NetWeaver 7.0

ProducerEP Portal

Content

BI

KMContent

ProducerEP Portal

Content

BI

KMContent

SAP BW 3.x

ConsumerEP

PortalContent

KMContent

(1) Remote Role Assignment (*)(2) Information Broadcasting(3) Producer BI iView in Portal

Content Studio(4) BW iView in Portal Content

Studio

(1) and (3) (4)(1) and (3)

(2)(2)

SAP NetWeaver 7.0 SAP NetWeaver 7.0


Performance and Sizing Considerations

Moving Workload from AS-ABAP to AS-JavaIn SAP NetWeaver 2004s, load is moved from AS-ABAP to AS-JavaBEx 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 systemsUsage 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.)

Sample SizingBefore 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)

(*) 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)

BeforeBefore After

See SAP Note 927530 – BI Java sizing


Recommendation

Use existing BI serverBased 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) configurationReduce administrator effort by using combined user persistenceAutomatic 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 Steps needed? …don’t hesitate to contact us for more

suggestions!


Improved/simplified Input screen with SPS13/14

Highly recommended by leading SAP consultants:

“…I think the checking time is over, let the

Template Installer BI-Java do the work!”

Less then 1MB coding!


Enterprise SearchCTC Installer for BI-Java


SAP NetWeaver BI Accelerator Value Proposition

SAP NetWeaver BI Accelerator

Very fast queryresponse time

Stable queryresponse time

High scalability Low maintenance

Performanceimprovements

by factor 10 – 100

Independent ofDB optimizer,aggregates, ...

No aggregatemaintenance, minimized

roll-up/change run

Implemented for latestblade server hardware

platforms

Increasedquality of

information/ExtendedBI reach

Significantreduction of

operationcosts


SAP NetWeaver BI Accelerator Architecture

SAP NetWeaver BI SAP NetWeaver BI Accelerator

Data Acquisition

InfoCubes

BI AnalyticEngine

BusinessExplorer

Any Tool

AnySource

Query &Response

Indexing

BI Accelerator responds to queries: joins and aggregates in run time

… indexes loadedinto memory

… creates and storesindexes for InfoCubes


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 rackBlade servers with 64-bit Intel Xeon CPUsOperating System (as of today)

– SUSE Linux SLES, 64-bit – No support for other OS planned

Optimized storage includedHardware Partners (as of today)

– Hewlett-Packard– IBM– Fujitsu-Siemens

Note: no restriction for the platform for the SAP NetWeaver implementation (no concern about incompatibilities)


Appliance

SAP NetWeaver BI Accelerator Appliance

Integration

Reduced Costof Operation

Rapid Deployment

Instantaneous operation– Pre-Installed by

hardware vendor– Minimal

configuration requirements

Simple purchase– Off-shelf hardware

Quick setup for rapid implementation

Minimized maintenance– Centralized

monitoring through CCMS

Easy scalability through blade server architectureAffordable commodity hardwareReduced license costsMinimized upgrade risk

Optimized hardware/software efficiency– Combination of hardware

components and configuration optimized for high-end performance


Business Intelligence Accelerator Information to the masses

10x faster queries

10x less expensive to acquire

20x less expensive to operate

Changing the way users interact with enterprise information

Enterprise Search

Deep search and controlled access to business objects

Self administration

BIAccelerator

EnterpriseSearch

A New Experience For Information Worker

Improvement20061990

216Addressable Memory

250x5MB/$

0.02MB/$

Memory

143x7.15MIPS/$

0.05MIPS/$

CPU

130MBPS

5MBPS

Disk TransferSpeed

25x

100 x10Gbs

100Mbs

Network Speed

264 248x


SAP NetWeaver BI Accelerator Sizing

SizingFor 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


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/bihttp://www.sdn.sap.com/sdn/forums

Business Intelligence BI in SAP NetWeaver 7.0

SAP Service Marketplace: http://service.sap.com/upgrade-bihttp://service.sap.com/bi Media Library Technical Documents

Related SAP Education and Certification Opportunitieshttp://www.sap.com/education/ search:WDEBU7 - Upgrade to NetWeaver 7.0 BITBW70D - BI - Delta Enterprise Data Warehousing & Reporting SAP NetWeaver 7.0DBW70E - BI - Delta Enterprise Data Warehousing SAP NetWeaver 7.0DBW70R - BI - Delta Reporting SAP NetWeaver 7.0


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


Roland KramerNetWeaver Advisory Office EMEASAP (Switzerland) Inc.Althardstrasse 80CH-8105 Regensdorft +41 58 871 66 02f +41 58 871 61 12m +41 79 215 84 18@ [email protected] http://service.sap.com/upgrade-bi

http://service.sap.com/bi => Media Library => Technical Documents

Contact


THANK YOU FOR YOURATTENTION !

QUESTIONS – SUGGESTIONS – DISCUSSION

Q & A


Please complete your session evaluation.

Be courteous — deposit your trash, and do not take the handouts for the following session.

Feedback

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 updatesDevelopment license for SAP NetWeaver to evaluate, develop and test Standard software maintenanceOnline sessions from SAP TechEdAccess to SAP Enterprise Services Workplace for testingPremium 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/devsubVisit 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.”