bw 7.3 upgrade

Upgrade to NetWeaver BW 7.30New features with ABAP Upgrade

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

Agenda

1. Technology/Roadmap facts 2. Whats 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

SAP AG 2009. All rights reserved. / Page 2

Planned Roadmap HANA & SAP NetWeaver BW

BW 7.3 / BWA 7.2Major step on Enterprise Data Warehousing scalability and flexibility BW Accelerator: additional performance Integration Improvements with SAP BusinessObjects Data Services

BW 7.3xBW running on HANA as the underlying In-Memory DB Platform In-Memory for Enterprise Data Warehousing Integrated Planning InMemory enabled

BW 7.0 EhP1 (7.01) BW 7.0 / BWA 7.0Major release BW Accelerator New features and improvements across all components Go-to release for integration with SAP Business Objects BI

2006

2009

2010

2011HANA V1.0

Future direction HANA V1.xAdditional calculation capabilities Primary persistence layer under BW; eliminates need for separate database Models for SAP business content enabling new applications

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

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

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

Major benefits of SAP NetWeaver BW 7.3 are:Enhanced Scalability & Performance for faster decision makingRemarkably accelerated data loads Next level of performance for BW Accelerator

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

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

Simplified configuration and operational managementAdmin Cockpit integrated into SAP Solution Manager Wizard based system configuration Important timelinesThis 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.

NetWeaver 7.30 including BW is GA since 30th of MAY 2011!


Upgrade to BW 7.30 - ABAPSome technology facts and updatesNetWeaver 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.30 There 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 accelerated together with BOe XI 3.1 and BI 4.x together 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.30 The 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. SAP AG 2009. All rights reserved. / Page 5

New BI 4.0 Installation for SAP BW CustomersPlatform View - ProposalSAP BW 7.0 ABAP 7.0 J2EE 7.0 BI Java SAP BW 7.01 ABAP 7.01 SAP BW 7.30 ABAP 7.30

SplitJ2EE 7.01 BEx Web BI Java BICS EP EP J2EE 7.30 BEx Web BI Java BICS BI Launch PadPhysical Server (optional) SAP NetWeaver SAP NetWeaver Functions SAP Usage Type and SAP BusinessObjects Tiers, Apps, Services

EP EP (opt)

LCM Client

BO XI 3.1 XI Reporting & Infrastruc. Services BOE XI Web Tier

BI Web Apps (*)

BI 4.x

Migr.

BI Web Tier

BI Reporting & Infrastructure 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 AG 2009. All rights reserved. / Page 6

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

SAP NetWeaver J2EE 7.30

Other J2EE (see PAM)

BI 4.0 SP? Only BICS BEx Web

BI 4.0 SP? Usage Type EP Usage Type BI Java (BICS, BEx Web) Upgrade from BW 7.0x

BI 4.0 BICS BEx Web

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

InstallBEx 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 SAP AG 2009. All rights reserved. / Page 7

Doublestack Options prior to the Upgrade BW 7.30 separation of ABAP and JAVA easies the upgrade processBW 7.0x Doublestack

Deinstall JAVA Add-In

Use Split tool

Deinstall JAVA 7.0x Stack

Single ABAP 7.0x Stack

Deinstall JAVA 7.0x Stack

Fresh Install of JAVA 7.30 (without ADS)

Upgrade to BW 7.30 ABAP

Upgrade to JAVA 7.30*

JAVA 7.30 Upgrade limitation* - no automatic file system 7.x - no automatic SAPCryptoLib - disable SNC configuration SAP AG 2009. All rights reserved. / Page 8

BW 7.30 ABAP Stack

NetWeaver 7.30 JAVA Stack (with ADS)

ADS = Adobe Document Services (obsolete with NetWeaver 7.30 BI-Java)

New authorization concept must be in placeFormer and new authorization conceptIt 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 concept New Transaction RSECADMIN, see SAP Notes 942799 and 944929


Example Project schedule for the MigrationCombined technical Upgrade & Authorization Migration1st month 2nd month 3rd month 4th month 5th month

Plan phase (6 weeks) Upgrade Authorizations DEV system (4 weeks) Upgrade & Test Authorization migration QAS system (5 weeks) Upgrade & Test Authorization Test PRD system (1 weekend) Upgrade & GoLive Cutover & GoliveLegend: Duration Milestone

KickOff

Start Upgrade

GoLive

Remark Overall 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. SAP AG 2009. All rights reserved. / Page 10

General Guidelines and NotesManaging 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/SIOBJNM Note 1403832 - Central Note: Upgrade Systems on SAP NetWeaver 7.3 Note 1390477 - Additional info for upgrade to SAP NetWeaver 7.3 (using SUM) Note 1484437 - BI_CONT 7.35: Information about installation and upgrade Hinweis 1022704 - Upgrade Phase EHP_INCLUSION und SPSTACK_REQUEST Hinweis 1171648 - [INTERN] Solution Manager: PPMS Produktdaten fehlen Note 1405878 - SAP Solution Manager - Basic functions SP22 and higher Note 1088717 - Active services for Web Dynpro ABAP in transaction SICF Note 1476239 - SAP system migration to Windows 2008/2008 R2 Note 1503599 - SQL Server: wrong compatibility level in system copy Note 1543092 - BI Administration Cockpit: Upgraded from 7.00 to 7.30 release SAP AG 2009. All rights reserved. / Page 11

Agenda



System Switch UpgradeNew with NetWeaver EhP1 onwards

New upgrade directory now located at \\sapmnt\\upg


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 SAPup STARTUP JCE_POLICY_ZIP = " 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-Ons as SAINT packagesAll Add-Ons/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

Lower your TCO and time efforts by Managing your Upgrade with innovative toolsComplete 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

2. CTC for BW-Javaautomatic connection between Abap and Java (Note 983156)

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

Use the predefined content for:upgrade to NetWeaver 7.x BW upgrade 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)

Check out the success story from the German Customer Karcher:

https://websmp204.sap-ag.de/~sapidp/011000358700000162292010E/ SAP AG 2009. All rights reserved. / Page 21

Upgrade Process with the ASU toolbox for BWin average 3 days per systems1 day 1 day 1 day 1 Week

Pre Upgrade StepsApplication checks/ cleansing and Upgrade Preparation Technical checks and Upgrade preparation Agree on result

PREPARE/ UPGRADELast checks PREPARE UPGRADE

Post Upgrade StepsApplication Post checks and functional tests Technical post Steps and Go-Live Preparation

TestingApplication testing New 7.0 EDW features Technical testing BI-Java CTC and testing of new 7.0 features

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

Note: Elapsed time may be longer due to scheduling and lags, etc. SAP AG 2009. All rights reserved. / Page 22

Typical Scenario for an UpgradeSee Details in SAP Note 1000009SAP Solution ManagerStart Upgrade RoadMap

SAP UP

SAP System

ASU-Upgrade-Note-Display Start Prepare Start ASU-Toolbox before Upgrade Phase(download Content from Marketplace)

Running Prepare-Jobs

Prepare finished Running ASU-Reports via Schedule Manager

ASU-Toolbox before Upgrade Phase finished

Start technical Upgrade Running technical Upgrade Technical Upgrade finished

Start ASU-Toolbox after Upgrade Phase Running ASU-Reports via Schedule Manager ASU-Toolbox after Upgrade Phase finished Monitoring of all started ASU-Reports via Solution Manager


Typical Upgrade Project Plantypical duration 6-8 weeks for a 3-System LandscapeUpgrade TasksUpgrade Planning Upgrade of Development Upgrade of Test Additional testing Upgrade of Production SAP Java Server/EP Setup of BOe/Explorer/BWA BU Requirements/BWA Start after first Upgrade (2d/Sys.) Start after first comp. Stack (2d/Sys) 2w

Steps/Milestones3d 3d + 1w Test 3d + 1w Test Ongoing (several weeks)

3d

Legend:

Duration

Milestonetoday

6 weeks

8 weeks

Time in total: 9d Upgrade, 10+d testing, 6d Java Inst, 6d BOe/Explorer, 5+d SBO Explorer Implementation SAP AG 2009. All rights reserved. / Page 24

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

Depending on timing/after Post Steps

IT/SAP Basis

Application Owner


Post Steps of ASU toolbox for BW - 2Depending on Project/existing App.

Application Owner


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

XML can now be changed within the same screen, e.g. new or changed items/checks can be added immediate.


Agenda



New with NetWeaver 7.0x

Daemon process

Stop 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 onwards2EETG013 "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 FileUse the Maintenance Optimizer from your Solution Manger


Create the Stack XML FileThe 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 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. SAP AG 2009. All rights reserved. / Page 42

Upgrade UI Start Pagehttp://..: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-Ons 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 962955modify /etc/hosts

check with Page 88 of the Upgrade Guide


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-OnsAdd 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-OnsUPG 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

version 7.35

3800300


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 structures InfoPackages definitions Process Chains This behavior didnt 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/recapD:\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 locksys 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 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 lock_eu 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


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 DowntimeUpgrade is already over the top

backup of DB


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 - existingCheck the generic post upgrade steps from here

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 52

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60ecc07d-3a4b-2b10-ef83-c988e6ecabf6


Thank you!Solution Architect BW/BI/In-Memory

Roland Kramer

Mobil +49 (151) 4260 3219 [email protected] http://www.sdn.sap.com/irj/sdn/edw-ops


Copyright 2011 SAP AG All Rights ReservedNo 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.
