upgrade to netweaver bw 7.30[1]

Upgrade to NetWeaver BW 7.30New features with ABAP Upgrade

Roland Kramer, Solution Architect BW/BI/In-Memory

June 2011

© SAP AG 2009. All rights reserved. /

Agenda

1. Technology/Roadmap facts

2. What’s new with the Upgrade to BW 7.30

3. Usage of the ASU toolbox for BW

4. General checks prior to the Upgrade

5. Details of the Upgrade Process


Planned Roadmap HANA & SAP NetWeaver BW

Major releaseBW AcceleratorNew features and improvements across all components

BW 7.0 / BWA 7.0

200920112010

Real-time operational analytics on mass dataRapid creation of agile data martsNon disruptive deployments of HANA side by side ERP and/or BW

HANA V1.0 Additional calculation capabilitiesPrimary persistence layer under BW; eliminates need for separate databaseModels for SAP business content enabling new applications

HANA V1.x

Go-to release for integration with SAP Business Objects BI

BW 7.0 EhP1 (7.01)

Major step on Enterprise Data Warehousing scalability and flexibilityBW Accelerator: additional performanceIntegration Improvements with SAP BusinessObjects Data Services

BW 7.3 / BWA 7.2

BW running on HANA as the underlying In-Memory DB PlatformIn-Memory for Enterprise Data WarehousingIntegrated Planning In-Memory enabled

BW 7.3x

2006

SAP NetWeaver BW evolving to a fully In-Memory enabled EDW solution on top of HANA

Futuredirection

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.


BW 7.30 - Executive Summary

Enhanced Scalability & Performance for faster decision makingRemarkably accelerated data loadsNext level of performance for BW Accelerator

Increased flexibility through SAP BusinessObjects BI and EIM integrationTighter integration with SAP BusinessObjects Data ServicesEnhanced integration with SAP BusinessObjects Metadata Management

Reduced TCO and improved development efficiencyAutomated creation of Semantic Partitioned ObjectsGraphical data flow modeling and best practice data modeling patterns

Simplified configuration and operational managementAdmin Cockpit integrated into SAP Solution ManagerWizard based system configuration

Major benefits of SAP NetWeaver BW 7.3 are:

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.

Important timelinesNetWeaver 7.30 including BW is GAsince 30th of MAY 2011!


Upgrade to BW 7.30 - ABAP

NetWeaver Java 7.30 is now shipped together with BW 7.30. Optionally you can separate the Java Stack prior to the Upgrade of the ABAP Backend, if not already done. The Upgrade of a Doublestack is also supported You can do either:The new split tool for the Java Stack in SAPInst is available with EhP2 or with the SAPInst delivered with Abap 7.30There is a SEM Add-On available with BW 7.30. The SEM (6.34) Add-On is available since end of Q1/2011 for all Customers. See Notes 1545831 and 1531022 for more details.BW 7.30 and BWA 7.30 brings together some new improvements not only for the SAP usage

together with Explorer 2.0 acceleratedtogether with BOe XI 3.1 and BI 4.xtogether with DS XI 3.2 and DI 4.x accessing non-SAP Systems and data lineage

The BICS are moving to the upcoming SAP BusinessObjects Application Platform BI 4.0, which is also a prerequisite for the full usage of the BEx successor - Analysis -The Java component BW-IP modeler is redeveloped for BW 7.30 in ABAP HTTP, so the Java Server will not be used anymore for the BW-IP infrastructure in the future after BW 7.30The new BI Authorization concept is now mandantory. Despite the fact that you either create a 7.0x System beforehand to migrate the old BW Authorization, a potential Upgrade from BW 3.5 to 7.30 would be possible.

Some technology facts and updates

SYNTEL

Highlight

SYNTEL

Highlight

SYNTEL

Highlight


New BI 4.0 Installation for SAP BW Customers Platform View - Proposal

SAP BW 7.0

Physical Server(optional)

SAP NetWeaver

SAP NetWeaverFunctions

J2EE 7.0

ABAP 7.0

SAP Usage Type andSAP BusinessObjectsTiers, Apps, Services

The XI 3.1/BI 4.0 Java apps can deployed either on an existing SAP J2EE 7.0x or 7.30 Engine, or ideally capsulated with BI with Tomcat. Consider the SAPJVM 4.1. A JVM switch toll is available as well

SAP BW 7.01

J2EE 7.01BEx Web

BICS

EP

ABAP 7.01

Split

J2EE 7.30

BEx Web

BICS

EP (opt)

SAP BW 7.30

ABAP 7.30

BI Java

EP

BI Java

EP

BI Java EP

LCM ClientBI Launch Pad

… (*)

BI 4.x

BI Reporting & Infrastructure Services

BI Web Apps

BI Web Tier

BO XI 3.1

BOE XI Web Tier

XI Reporting & Infrastruc. Services Migr.

SYNTEL

Highlight

SYNTEL

Sticky Note

Marked set by SYNTEL

SYNTEL

Highlight


J2EE Options for BI 4.0 together with BW 7.30use the recommendation with the BI 4.0 inbuilt Java Server

BI 4.0

SAP NetWeaver J2EE 7.30

Other J2EE (see PAM)

BI 4.0BICS

BEx Web

BI 4.0 SP? OnlyBICS

BEx Web

BI 4.0 SP?Usage Type EP

Usage Type BI Java(BICS, BEx Web)

BEx Web Limitations*- No Broadcasting (Portal/KM)- No Documents (Portal/KM)- No Xcelsius BW Connection

InstallUpgrade from BW 7.0xInstall

BEx Web Limitations*- No Broadcasting (Portal/KM)- No Documents (Portal/KM)- No Xcelsius BW Connection

*Broadcasting is either a direct ABAP process (Excel) or an ABAP HTTP process publishing in a separate SAP EPDistinguish between 3.x and 7.x Web templates. 3.x Web template to not require BI - JAVA 7.x


Single ABAP 7.0x Stack

Doublestack Options prior to the Upgrade BW 7.30separation of ABAP and JAVA easies the upgrade process

BW 7.0x Doublestack

Deinstall JAVA Add-In Use Split tool

Upgrade to JAVA 7.30*

Upgradeto BW 7.30 ABAP

Fresh Install of JAVA 7.30 (without ADS)

BW 7.30ABAP Stack

NetWeaver 7.30JAVA Stack (with ADS)JAVA 7.30 Upgrade limitation*

- no automatic file system 7.x- no automatic SAPCryptoLib- disable SNC configuration ADS = Adobe Document Services (obsolete with NetWeaver 7.30 BI-Java)

Deinstall JAVA 7.0x Stack Deinstall JAVA 7.0x Stack


New authorization concept must be in placeFormer and new authorization concept

It is mandatory to setup/migrate to the new concept prior to the upgrade The former authorization concept is no longer supported with BW 7.30 You cannot switch back to the former conceptNew Transaction RSECADMIN, see SAP Notes 942799 and 944929


Example Project schedule for the MigrationCombined technical Upgrade & Authorization Migration

Plan phase (6 weeks)UpgradeAuthorizations

DEV system (4 weeks)Upgrade & TestAuthorization migration

QAS system (5 weeks)Upgrade & TestAuthorization Test

PRD system (1 weekend)Upgrade & GoLiveCutover & Golive

KickOffLegend: Duration MilestoneStart Upgrade

1st month 2nd month 3rd month 4th month 5th month <month>

GoLive

RemarkOverall project duration dependents on the system complexity.Given example is based on a higher complexity.To match with typical technical Upgrade Plan, start two month in advance.


General Guidelines and Notes

Managing your Upgrade with Innovative Toolshttp://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/b039ebc5-304f-2b10-499e-97dabda45e48

New Features with BW 7.30http://www.sdn.sap.com/irj/sdn/bw-73

Links to Guides (Master and Upgrade)http://service.sap.com/instguides

NetWeaver BW 7.30 Online Helphttp://help.sap.com/saphelp_nw73/helpdata/en/ca/6fbd35746dbd2de10000009b38f889/frameset.htm

Useful NotesNote 586648 - Invalid SID entries in /BI 0/SIOBJNMNote 1403832 - Central Note: Upgrade Systems on SAP NetWeaver 7.3Note 1390477 - Additional info for upgrade to SAP NetWeaver 7.3 (using SUM)Note 1484437 - BI_CONT 7.35: Information about installation and upgradeHinweis 1022704 - Upgrade Phase EHP_INCLUSION und SPSTACK_REQUESTHinweis 1171648 - [INTERN] Solution Manager: PPMS Produktdaten fehlenNote 1405878 - SAP Solution Manager - Basic functions SP22 and higherNote 1088717 - Active services for Web Dynpro ABAP in transaction SICFNote 1476239 - SAP system migration to Windows 2008/2008 R2Note 1503599 - SQL Server: wrong compatibility level in system copyNote 1543092 - BI Administration Cockpit: Upgraded from 7.00 to 7.30 release


Agenda







System Switch Upgrade

New upgrade directory now located at \\sapmnt\<SID>\upg

New with NetWeaver EhP1 onwards


New Upgrade UIfollowing the EhP development guidelines


New Upgrade UIProviding the JCE Jurisdiction Policy Files beforehand

New Security Concept used:See Notes 1240081 and 1238121

Start of SAPupSTARTUP „JCE_POLICY_ZIP = <jce policy zip file>" If JCE_POLICY_ZIP already set in the Environment you can directly use STARTUP without Parameter


Put all components/patches/updates to one directory and all Add-On‘s as SAINT packages

All Add-On’s/Patches will be found automatically in the EPS inbox

Create your XML Files for ABAP Support Packages on SMP


New Preconfiguration Modes availableOr manual selection see Upgrade Guide Page 46


Upgrade Planningworking until Downtime is possible now


Changeability of BW Objects during Upgrade


Agenda







Accelerated Upgrade to NetWeaver BW 7.30Your single source for all pre and post upgrade steps

Use the predefined content for:upgrade to NetWeaver 7.x BWupgrade to ERP 6.0 EhPx (upcoming)upgrade to any SAP Product based on the NetWeaver 7.x Platform (upcoming)create/modify own content (XML based)

Complete Business Suite 7 connectivity (with EhP1):

abap - java connection (available) for connection BW-IP, EP, ESS/MSS, etc.abap - abap (with EhP1) for backend connection e.g. ERP, CRM, BW, PI, etc.java - java (upcoming) for frontend connection e.g. FPM, etc.Note 1178800

Lower your TCO and time efforts by Managing your Upgrade with innovative tools

1. ASU toolbox (incl. BW Content)one single truth for all pre/post Upgrade Steps(Note 1000009)

2. CTC for BW-Javaautomatic connection between Abap and Java

(Note 983156)

Check out the success story from the German Customer Karcher: https://websmp204.sap-ag.de/~sapidp/011000358700000162292010E/


Application Post checks and functional testsTechnical post Steps and Go-Live Preparation

Application testingNew 7.0 EDW featuresTechnical testingBI-Java CTC and testing of new 7.0 features

Application checks/ cleansing and Upgrade PreparationTechnical checks and Upgrade preparationAgree on result

Last checksPREPAREUPGRADE

Pre Upgrade Steps

PREPARE/UPGRADE

Post UpgradeSteps Testing

Upgrade Process with the ASU toolbox for BWin average 3 days per systems

1 day 1 day 1 day 1 Week

Note: Elapsed time may be longer due to scheduling and lags, etc.

Key Highlights of the ASU toolbox for BWOne single source of all pre and post steps for a successful upgradeClear distribution of tasks between SAP Basis Administration and the Application DevelopmentAdditions, Remarks, Documentation can be added immediately as wellXML editor makes adoptions to other SAP upgrades easy.


Typical Scenario for an UpgradeSee Details in SAP Note 1000009

SAP Solution Manager SAP UP SAP System

Start Upgrade RoadMap

Start ASU-Toolboxbefore Upgrade Phase(download Content from Marketplace)

Start Prepare Running Prepare-Jobs

Running ASU-Reports viaSchedule Manager

Start technical UpgradeASU-Toolboxbefore Upgrade Phase finished

Prepare finished

Running technical Upgrade

Start ASU-Toolboxafter Upgrade Phase

Technical Upgrade finished

Running ASU-Reports viaSchedule Manager

ASU-Toolboxafter Upgrade Phase finished

Monitoring of all started ASU-Reports via Solution Manager

ASU-Upgrade-Note-Display


Typical Upgrade Project Plantypical duration 6-8 weeks for a 3-System Landscape

Start after first comp. Stack (2d/Sys)

3d

3d + 1w Test

Ongoing (several weeks)

Steps/Milestones

3d + 1w Test

3d

Start after first Upgrade (2d/Sys.)

2w

Upgrade Tasks

Upgrade Planning

Upgrade of Development

Additional testing

Setup of BOe/Explorer/BWA

Upgrade of Test

Upgrade of Production

SAP Java Server/EP

BU Requirements/BWA

todayLegend: Duration Milestone 6 weeks 8 weeks

Time in total: 9d Upgrade, 10+d testing, 6d Java Inst, 6d BOe/Explorer, 5+d SBO Explorer Implementation


Pre Steps of ASU toolbox for BW - 1

IT/SAP Basis/Application Owner

Application Owner

IT/SAP Basis


Pre Steps of ASU toolbox for BW - 2

Application Owner


Post Steps of ASU toolbox for BW - 1

IT/SAP Basis

Application Owner

Depending on timing/after Post Steps


Post Steps of ASU toolbox for BW - 2

Depending on Project/existing App.

Application Owner


ASU toolbox – BW specificInstall latest ST-PI 2008 Add-On

XML can now be changed within thesame screen, e.g. new or changeditems/checks can be added immediate.


Agenda







New with NetWeaver 7.0x Daemon processStop all Deamon Process with Transaction RSRDA


Activate all DataStore ObjectsValid for all BW Releases 3.x and 7.0x


Further general Upgrade ChecksSAP_DROP_TMPTABLES and RSUPGRCHECK


Check the Secure Storage with SECSTOREe.g. if System is a copy from Test/Production


Transaction SECSTORE


Check for missing TLIBG entryNew check from NetWeaver BW 7.0x onwards

2EETG013 "Function group frame program" "CRM_BUPA_FRG0060_BAPI" "exists without TLIBG entry"2EETG013 "Function group frame program" "LXE_SE63_Z_EDITOR" "exists without TLIBG entry"


Create the Stack XML File Use the Maintenance Optimizer from your Solution Manger


The upgraded System must appear here for selection

Example: http://sptmain.wdf.sap.corp:1080/sap/bc/webdynpro/sap/wda_mopz_plan?sap-language=EN

Create the Stack XML File


Create the Stack XML FileChoose the Option Maintenance for the Upgrade


Create the Stack XML FileConfirm the Major Target


Create the Stack XML FileThe XML File is created and available for download or in the EPS inbox


Agenda






Please Note: Some of the screenshots might contain 7.20 as release, this has no impact on the shown steps, as the technical Upgrade Procedure for 7.30 is the same.


Upgrade UI – Start Pagehttp://<server>.<domain>.<ext>:4239


Start the Software Upgrade Manager (SUM)startup.bat jce_policy_zip=c:\java\SAPJVM6_crypto.zip


SAP JVM location/environment variablesstart DSUGui.bat separately


Upgrade UIDetails for Step Initialization


Upgrade Password provided in Note 1390477Put all updates from SMP into the download directory

startup.bat "jce_policy_zip=SAPJVM6_crypto.zip"Password:KEYWORD: 6782622


Add all main DVD hereRemove empty lines in advance Add-On’s as SAINT packages


Include the Stack XML from Solution ManagerA correct configured Maintenance Optimizer is a prerequisite now


Solution Manger Upgrade Key readySolution Manager – MOPZ connection later necessary


Check for missing ABAP correctionsThis will also appear even if you on the right SP Stack Level


Upgrade UI Note 96317 and 962955check with Page 88 of the Upgrade Guide modify /etc/hosts


New Upgrade pre configuration optionsHigh resource use (minimal downtime, fast import, archiving off)


Overview of upgrade configurationAccept choice


Overview of manual upgrade configurationManual selection will not apply maximum values


Procedure with further Add-On’sAdd additional packages as SAINT packages into EPS/in


Mandantory connection to MOPZ neededAs alternative create a Stack XML for BW 7.30 (no EhP included)


Decision about EhP1 during Upgrade to 7.30Note 1022704 EHP_INCLUSION and SPSTACK_REQUEST


Further descission about Add-On’sUPG WITH SAINT PACK or DELETE (for ST-PI possible)


Decision about included Support Packages


Decision about included SPAM update


Optional: include SPDD and/or SPAU request


ASU toolbox for BWEven that ASU toolbox is optional, it contains ALL pre and post steps


Installing BI_CONT on SAP NetWeaver 7.3

3800300version „7.35“


Development is locked after this PhaseDepending on your Upgrade preconfiguration

Please Note:from BW Perspective is is now not possible anymore to change the following objects, even that you are not jet in the downtime phase

Query structuresInfoPackages definitionsProcess Chains

This behavior didn’t changed from former BW Upgrades prior to EhP1 (7.01)


Decision about SPDD prior the ACT phaseFor BW type system you can continue without adjustments


Unlock/Lock the shadow system is necessaryA friendly reminder/recap

D:\usr\sap\trans\bin>tp unlocksys FBM pf=TP_DOMAIN_FBM.PFL

This is tp version 372.04.65 (release 700, unicode enabled)

tp finished with return code: 0

meaning:

Everything OK

D:\usr\sap\trans\bin>tp unlock_eu FBM pf=TP_DOMAIN_FBM.PFL



meaning:

Everything OK

D:\usr\sap\trans\bin>tp locksys FBM pf=TP_DOMAIN_FBM.PFL



meaning:

Everything OK

D:\usr\sap\trans\bin>tp lock_eu FBM pf=TP_DOMAIN_FBM.PFL



meaning:

Everything OK


Reset the Upgrade with report RSUPGRESAnother friendly reminder/recap

Note 417670 - Additional information on resetting upgrade as of Release 6.10


Decision about ACT phaseAccept non-severe errors will be solved in a later phase


Old “PREPARE” is now finishedUntil this phase working with the system was possible


End of phase PreprocessingTo ensure the recovering please backup the upgrade directory


End of phase Downtime backup of DBUpgrade is already over the top


End of phase PostprocessingThink about the start of BTCTRNS2 after the post work is finished


End of phase PostprocessingThink about the start of SGEN after the post work is finished


End of phase PostprocessingMight not occure with higher support package


End of phase PostprocessingDecision about SPAU create transport for further upgrades


End of phase PostprocessingYour technical Upgrade is finished


Technical Upgrade has endedEnd of phase Finalization


Example runtime for BW 7.30 upgradeRunning at the end of the technical upgrade


Postwork after 7.30 upgrade - newNote 1165059 - ALE: Generating and reading change pointers after upgrade


Migrate the BI Authorization to 7.30

More Details:http://help.sap.com/saphelp_nw73/helpdata/en/45/5ae49cee142a50e10000000a11466f/frameset.htm


Postwork after 7.30 upgrade - existing

Get everything which is needed here:Managing your Upgrade with Innovative Toolshttp://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/b039ebc5-304f-2b10-499e-97dabda45e48

The „upgrade Bible“ from page 52http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60ecc07d-3a4b-2b10-ef83-c988e6ecabf6

Check the generic post upgrade steps from here


Thank you!

Roland Kramer Solution Architect BW/BI/In-Memory

Mobil +49 (151) 4260 [email protected]

http://www.sdn.sap.com/irj/sdn/edw-ops


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, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

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.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warrant.

© Copyright 2011 SAP AGAll Rights Reserved