


Loading in 2 Seconds...
Loading in 2 Seconds...
Creating an upgrade plan and strategy for SAP BW and NetWeaver. Bjarne Berg MyITgroup Ltd. What We’ll Cover …. Why upgrade End of support New support strategy & NetWeaver New features and capabilities Creating an upgrade strategy for the future Content Vs. Technical upgrades
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
SAP has now created a 5-1-2 maintenance system that consists of:
- mainstream maintenance
- extended maintenance
- customer-specific maintenance
Why Upgrade – end of support…#1 reason for upgrade:
“Because I had to!”
The 5-1-2 maintenance strategy
Going forward, SAP will provide five years of mainstream (standard) maintenance, with the option to extend their maintenance coverage for a period of up to three years for small premiums over the standard maintenance rate.
Five years of mainstream maintenance at the standard maintenance fee.
One year of extended maintenance at an additional two percent maintenance fee.
Two more years of extended maintenance at an additional four percent maintenance fee per year. After these eight years, customer-specific maintenance begins, providing a program of support and services uniquely tailored to individual customer requirements.
The plan covers SAP solutions based on the SAP NetWeaver platform including mySAP SCM, SRM, PLM, CRM, and industry add-ons.
Stop looking at infrastructure and technology…
Start looking at the big picture…
How are you going to make it all work together?
And,.. how will you plan your upgrades to make sure it does so in the future?
Source: SAP, Léo Apotheker
PEOPLE INTEGRATION
PEOPLE INTEGRATION
Multichannel
Multichannel
Multichannel
access
access
access
Portal
Portal
Portal
Collaboration
Collaboration
Collaboration
INFORMATION INTEGRATION
INFORMATION INTEGRATION
INFORMATION INTEGRATION
Bus. Intelligence
Knowledge Mgmt
Bus. Intelligence
Bus. Intelligence
Knowledge Mgmt
Knowledge Mgmt
Master Data Management
Master Data Management
Master Data Management
COMPOSITE APPLICATION FRAMEWORK
COMPOSITE APPLICATION FRAMEWORK
COMPOSITE APPLICATION FRAMEWORK
LIFE CYCLE MANAGEMENT
LIFE CYCLE MANAGEMENT
LIFE CYCLE MANAGEMENT
PROCESS INTEGRATION
PROCESS INTEGRATION
PROCESS INTEGRATION
Integration
Integration
Integration
Bus. Process
Bus. Process
Bus. Process
Broker
Broker
Broker
Mgmt
Mgmt
Mgmt
APPLICATION PLATFORM
APPLICATION PLATFORM
APPLICATION PLATFORM
J2EE
J2EE
J2EE
ABAP
ABAP
ABAP
...
...
DB and OS Abstraction
DB and OS Abstraction
DB and OS Abstraction
Source: SAP AG
The Bigger Picture – NetWeaver ??NetWeaver is a set of solution components that provides a comprehensive architecture.
All components of NetWeaver can use the same operating system release, and the same database release.
All components can be run within a single physical server if it is a small configuration, thereby reducing the number of systems and databases to be managed.
“A SAP survey of 200 customers found that SAP deployment reduced costs in three areas: integration through the use of NetWeaver components, consolidation of the IT landscape and the implementation of best practices using product functionality.”
The Big-Picture - NetWeaverThe leaders
If SAP is you strategic choice, it is hard to ignore NetWeaver.
SAP now offers SAP NetWeaver solutions and components in a synchronized release cycle. All components are delivered in a single package.
The exception is Master Data Management, the newest member of NetWeaver. MDM 2.0 is able to use NetWeaver ‘04 (it can use XI 3.0), but is still based on WAS 6.20.
NetWeaver use WAS 6.4 and therefore share a common technical foundation.
Included in NetWeaver-04 is:
SAP Composite Application Framework (CAF 1.0) is a tool for building applications on-top of NetWeaver without using low-level programming interfaces (APIs). It has been available as an add-on since Aug.-04. CAF 2.0 will be available with the next release of NetWeaver mid-year 2005.
Why Upgrade – Simplified maintenance
More details at: SAP NetWeaver Master Guide & NetWeaver Solution Management Guide.
One of the major reasons for upgrading your BW environment is the availability of new content and features in the next release. Let us take a look at what is new in version 3.5:
We will now take a quick look at these features
BW version 3.5 and higher has BPS included and you also get additional functionality
Major new features of BPS in BW 3.5:
Users or developers can schedule reports to be delivered to them through email, portal roles, zip files, or web based reports (browser & handhelds).
We can trigger the reports to run at:
Core feature: Push Vs. Pull Strategy
The Web Application Designer has more features:
Applications
BW
3. Java
1. Universal Data Connect
BI Java SDK
Universal Data Connect
2. Java connect-
tors
SAP Query JDBC ODBO XML-A
SAP
Non-SAP
Universal Data Integration in BW 3.5FRONT-END:
WAS 6.4
Java 2 Enterprise Edition 6.4
Universal Data Connect
SAP Query JDBC ODBO XML-A
RFC, BAPI, API
JDBC Driver
ODBO provider
URL/HTTP
R/3
BW
3rd Party
RDBMS
Universal Data ConnectBACK-END:
RELATIONAL DATABASES
1. Over 190 JDBC drivers for database connectivity
2. BI SAP Query connector for R/3, SAP CRM ad-hoc connectivity
OLAP
1. BI OLE connector a Microsoft standard
2. BI XMLA connector for web based OLAP sources
Unicode support for SAP DB, Oracle 9.2, IBM DB2 AS400 UDB, and SQL Server:
яьфдФњщ
Ệẁ
ǻǼǽǿ
תשרחפא
ﻲﻶﻺﻕﻒﻏﻎ
BW queries can be published to the Portal Content Catalog.
The BeX Portfolio consists of applications that include collaborative information such as:
NEWS: BW web applications are KM Objects
We can publish an application to the Portal as:
Source: SAP AG
Better integration of BW content in the portal: you don’t have to upload iView files anymore!!
BW content in the Collaboration Room
KEY IDEA: Build BW content once and publish many different ways!!
Good reason to upgrade:
better functionality!!!
The new upgrade strategy from SAP is to provide BW technical releases as part of NetWeaver and BI content add-ons,
You do not need to perform a technical upgrade to update the business content. I.e. content releases such as the older 3.2, 3.3 and 3.51 contains more business content and can be applied via delta upgrade.
The content upgrade can occur in as little as 1-2 hours (per system) and are shipped on supplement CDs.
Any new upgrade should now plan to use content provided in 3.5.3.
FYI: the content delivered in add-on 3.5.1 is the same as the content in release 3.1c with 3.3. content.
Apply content when you need it, to the technical release you have!!
3.5.1
March 2004
3.5.2
3.5.2
3.5.3
3.5.3
nd
2
week
June 2004
Fall 2004
TBD
of June
BW Release UpgradesThe Technical upgrades are called BW releases.
This include changes and/or additions to technical capabilities such as improved ODSs (ver 2.x) and Process Chains (ver 3.x).
The release 3.5 is a technical release with initial 3.5.1 add-on.
3.5 content add-ons include:
Future upgrade strategies needs to
include both content as well as release
upgrade plans for BW
Plan a periodic review of new content before you build custom solutions
Think bigger than BW..
Apply content as soon as feasible. Especially if you have on-going development work. This way you can avoid many “work-arounds”.
You should seriously consider having all NetWeaver components on the same upgrade strategy instead of selecting each component for upgrade. This will help in the shared extractors and also substantially simplify the upgrade planning and landscape.
Look at SAP’s release strategy for each
component you are using and plan ahead,
instead of last-minute “must-do” projects.
A direct release upgrade from 2.0B, 2.1C and 3.0B to 3.5 is possible.
However an upgrade from 3.1C needs to apply 3.2 and 3.3 content add-ons before upgrading to 3.5.
Remember the next release of NetWeaver is scheduled for mid-2005.
It is important to communicate the goals and timings to the technical team to help them prioritize their research and activity or hardware setup
Communicate goal of having existing content continue to work to functional test team, so they do not get hung up in testing new features before the upgrade is in production
Research changes to BW or the Plug-IN that may affect your existing “live” content and use this information to outline a planned “upgrade regression and correction test cycle”
The regression test should be similar to a large support pack implementation
SAP GUI – New GUI roll out, Patches? (e.g. BW 3.0B/3.1C -> 6.20 BUT… BW 3.5 -> 6.20/6.40)
PC Requirements – Need upgrade to take advantage of new features? BW 3.0/3.1c - Same PC requirements – but the devil is in the details (see OSS 161993, 66971)
DB/OS – Are they supported on the new release? Take the opportunity to apply patches as needed.
IGS – If need rendering of charts and graphs in BW 3.x Web Applications you need IGS… BUT it now only runs under NT and W2K. (BW 3.5 will support UNIX until IGS 6.40)
Considerations
Technical approach
Evaluate impact to transport flow – dummy systems may be needed for a smooth transition
New content -> more users -> more app servers?
IGS -> may require new hardware
Parallel Load = more memory
ODS Layer = more space
Crystal Reports -> new hardware
Archiving -> may reduce need for space
Make sure the new software is ordered and in hand!
Example
This company reallocated their Sun-6800 box and plans for gigabit connectivity to the AppServer….
More memory allows them to take better advantage of the parallel load of the BW system as well as to cache many of the frequently run queries.
The hardware also allows them to have a system where performance between the boxes are comparable.
Production
12 CPU
96GB RAM
AppServer
4 CPUs
32GB RAM
Test
4 CPUs
32GB RAM
Development
4 CPUs
32GB RAM
Plan for regression test glitches – and production cut-over.
Team Lead
Basis
Basis
Technical reviewer
Technical reviewer
Upgrade Support
Upgrade Support
Regression Testers
Regression Testers
resource
BW Developer
External
External
ResourcesThe duration is driven by:
1. The number of BW systems in your landscape.
2. The new functionality your are rolling out
3. The support technology needed (I.e. app servers, GUI)
The more content you have the longer the upgrade
(the more you have to regression test)
GUI needs to be 620 or 640, with BW 3.5 front end patch
The BW upgrade adds to the PI and ALE connection, which is backwards compatible. Source system connections should remain intact, with minimal adjustment, and a replication vs. restore
Some areas will need to change and are based on your local content, and customization, but you can continue to use existing methodology until you decide to change – see the notes!
If your end users are web users, they will see no effective changes
There should be no impact to portal or R3 or other BI system connections – all dependent on the Plug-In level
Downstream data feeds should remain unaffected
Data will not have to be reloaded or deltas reinitialized in more than 95% of cases – it’s there already!
The document “How to… SAP BW 3.5 upgrade preparation and post-upgrade checklist” v1.10 Nov. '04 is available at www.sdn.sap.com
The document called “SAP’s Release Strategy – For all Major
Shipments from 2005 on” available at www.SAP.com
The presentation called "NetWeaver '04 Highlights" - session ID NW201 available from the site www.sapteched.com