berg - upgrade strategy v8

8/17/2019 Berg - Upgrade Strategy v8

1/42

© 2005 Wellesley Information Services. All rights reserved.

Creating an upgrade planand strategy for SAP BWand NetWeaver

Bjarne BergMyITgroupLtd.


2/42

2

What We’ll Cover …

• Why upgrade

End of supportNew support strategy NetWeaver

New features and !apa"#l#t#es

• Creat#ng an upgrade strategy for the future

Content $s. Te!hn#!al upgrades%pgrades w#th NetWeaver

• &lann#ng and E'e!ut#ng the upgradeThe upgrade plan

The "us#ness !ase (taff#ng) durat#on and s!ope

• *uest#ons and +nswers


3/42

3

Why %pgrade , end of support…

Many upgrades are dr#ven "y end of support for a !erta#n release.

(+& has now !reated a -/0 1a#ntenan!e syste1 that !ons#sts of2 1a#nstrea1 1a#ntenan!e

e'tended 1a#ntenan!e

!usto1erspe!#f#! 1a#ntenan!e

BW

Version

Release

date

End of mainstream

maintenance2.0B 8/14/00 12/31/2005

2.1C 12/18/00 12/31/2005

3.0A 11/15/01 12/31/2005

3.0B 5/13/02 12/31/2006

3.1C 11/11/02 12/31/2006

3.2 3/31/03 12/31/2006

3.3 8/30/03 12/31/2006

3.5 3/31/04 3/31/2010

#1 r e a s o n f o

r u p g r a d e :

“Because I had to

!”


4/42

4

3o#ng forward) (+& w#ll prov#de f#ve years of 1a#nstrea1 4standard5

1a#ntenan!e) w#th the opt#on to e'tend the#r 1a#ntenan!e !overage for aper#od of up to three years for s1all pre1#u1s over the standard

1a#ntenan!e rate.

/. 6#ve years of 1a#nstrea1 1a#ntenan!e at the standard 1a#ntenan!e fee.

0. 7ne year of e'tended 1a#ntenan!e at an add#t#onal two per!ent 1a#ntenan!e fee.

8. Two 1ore years of e'tended 1a#ntenan!e at an add#t#onal four per!ent 1a#ntenan!e

fee per year. +fter these e#ght years) !usto1erspe!#f#! 1a#ntenan!e "eg#ns) prov#d#ng

a progra1 of support and serv#!es un#9uely ta#lored to #nd#v#dual !usto1erre9u#re1ents.

The plan covers SAP solutions based on the SAP NetWeaver platform

including mySAP SCM, SRM, PM, CRM, and industry add!ons"

The -/0 1a#ntenan!e strategy


5/42

5

The B#gger !ture

(top loo:#ng at #nfrastru!ture

and te!hnology…

(tart loo:#ng at the "#g

p#!ture…

;ow are you go#ng to 1a:e #t all

wor: together<

+nd).. how w#ll you plan your

upgrades to 1a:e sure #t does

so #n the future<

Source: SAP, Léo Apotheker


6/42


7/42

7

The B#g!ture NetWeaver

=+ (+& survey of 0>> !usto1ers found

that (+& deploy1ent redu!ed !osts #n

three areas2 #ntegrat#on through the useof NetWeaver !o1ponents)

!onsol#dat#on of the IT lands!ape and

the #1ple1entat#on of "est pra!t#!es

us#ng produ!t fun!t#onal#ty.?

on NetWeaver and TCO…

(he leaders

NetWeaver cae fro1no#here2 to the top34

position in less than oneyear after launch555

'f SAP is you strategicchoice, it is hard toignore NetWeaver!


8/42

8

What should I !ons#der f#rst<

N7TE2 Most !o1ponents are 1ature and well proven4#.e. BW has "een ava#la"le for over @ years5.


9/42

9

The B#gger !ture

(+& now offers (+& NetWeaver solut#ons and !o1ponents #n a syn!hron#Aed release !y!le. +ll !o1ponents are del#vered #n a s#ngle pa!:age.

The e'!ept#on #s Master ata Manage1ent) the newest 1e1"er of NetWeaver. MM 0.> #s a"le to use NetWeaver >D 4#t !an use I 8.>5) "ut #s st#ll "ased on W+( F.0>.

NetWeaver useWAS 6!7 and

therefore share a

coon technicalfoundation!


10/42

10

The B#gger !ture

• BW 4!8 is part of the NetWeaver 97 standard availa"ility

#as given in Sept! /997

'ncluded in NetWeaver397 is: BW 4!8

Portal 6!9 Service Pack 4 )change 'nfrastructure 4!9 &' /!8 We" Application Server 6!7

(+& Co1pos#te +ppl#!at#on 6ra1ewor: 4C+6 /.>5 #s a tool for

"u#ld#ng appl#!at#ons ontop of NetWeaver w#thout us#ng lowlevel

progra11#ng #nterfa!es 4+&Is5. It has "een ava#la"le as an addon

s#n!e +ug.>D. C+6 0.> w#ll "e ava#la"le w#th the ne't release of

NetWeaver 1#dyear 0>>-.


11/42

11

Today !o1pan#es use a var#ety of syste1s) hardware) operat#ng

syste1s) data"ases to host the#r 1any (+& !o1ponents. NetWeaverprov#des a un#f#ed #nfrastru!ture to redu!#ng Total Cost of 7wnersh#p.

NetWeaver #s sh#pped as one produ!t

+ll !o1ponents of NetWeaver !o1e as one sh#p1ent. It !an "e #nstalled #n onepro!edure) and !an run together #n one syste1 4e'!ept MM 0.>.5

Gou !an upgrade (+& NetWeaver 0>>D !o1ponents #nd#v#dually as long as

the !o1ponents are #nstalled on separate syste1s.

Gou !an gradually "r#ng !urrent !o1ponents to NetWeaver level to 1a:e use of

new features of a !o1ponent or to rea!h the !o11on IT #nfrastru!ture #n several

steps.

Why %pgrade , (#1pl#f#ed 1a#ntenan!e

More details at# SAP NetWeaver Master $uide

% NetWeaver Solution Management $uide"

Note


12/42

12

What #s New #n the Helease<

7ne of the 1ajor reasons for upgrad#ng your BW env#ron1ent

#s the ava#la"#l#ty of new !ontent and features #n the ne'trelease. Let us ta:e a loo: at what #s new #n vers#on 8.-2

Bus#ness &lann#ng and (#1ulat#on

Infor1at#on Broad!aster ata warehous#ng and Bus#ness Intell#gen!e

%n#versal ata Integrat#on

%n#!ode (upport

Be &ortfol#o #n Enterpr#se &ortals

We &ill no& ta'e a (uic'

loo' at these features


13/42

13

What #s New Bus#ness &lann#ng and (#1ulat#on

BW version 4!8 and higher has BPS included and you also get

additional functionality

&a;or ne# features of BPS in BW 4!8:

/! +eove outliers fro the plan =unusual data points>!

4! Work #ith incoplete tie3series


14/42

14

What #s New Infor1at#on Broad!aster

%sers or developers !an s!hedule reports to "e del#vered to the1

through e1a#l) portal roles) A#p f#les) or we" "ased reports 4"rowser handhelds5.

We !an tr#gger the reports to run at2 Certa#n t#1es

When data #s loaded to the syste1

7r we !an 1a#l #t to the users ad

ho! when we want to.

Core feature# Push )s" Pull Strategy


15/42

15

What #s New<

(he We" Application -esigner has ore features:

(he navigational state can "e stored in ?&L forat

.avaScript can "e used to custoi@e #e" navigation

Corporate #e" teplates can "e reused

Ne# chart designer #ith cool charts and a developent#i@ard


16/42

16

%n#versal ata Integrat#on #n BW 8.-

niversal -ata Connect

SAP Non3SAP

BW

B' .ava S- SAP uery .-BC %-B% ?&L3A

Custo

Applications

/! .avaconnect3tors

4! .ava

*+%N(3)N-:


17/42

17

%n#versal ata Conne!t

niversal -ata Connect

+*C, BAP', AP' .-BC -river %-B% provider +LD((P

SAP uery .-BC %-B% ?&L3A

+4 4rd PartyBW+-B&S

.ava / )nterprise )dition 6!7

BW 4!8

WAS 6!7

+)LA('%NAL -A(ABAS)S


18/42

18

What #s New %n#!ode (upport

%n#!ode support for (+& B) 7ra!le .0) IBM B0 +(D>>

%B) and (*L (erver2

BW 8.- (upports 1ult#ple languages through a un#!ode ena"led

server 4"a!:end5 and a un#!ode ena"led we" frontend

6or M#!rosoft "ased !o1ponents the =logon language? #s

supported

FGHIJK M N O

P Q R S

T U VXYZ[

\ ] ̂ _


19/42

19

What is Ne# ` Be? Portfolio in the Portal

BW ueries can "e pu"lished to the Portal Content Catalog!

(he Be? Portfolio consists of applications that include colla"orative inforation such as:

(echnical etadata =run ties, descriptions, priority etc> Su"scriptions of a report *eed"ack of a report =i!e! coents> +ating of report ="y users> +eport details = descriptions and use inforation> &ailing of a report to others

-B and %S A"straction

"N*T WebSphere+

People Integration

C o m p o s i t e A p p l i c a t i o n F

r a m e w o r k

Process Integration

'ntegrationBroker

Business Process&anageent

Information Integration

Business'ntelligence no#ledge&anageent

Li f e C y cl eM an a g em en t

Portal Colla"oration

./)) ABAP

Application Platform

&ulti3Channel Access

SAPSAP NetWeaver ™™


&aster -ata &anageent


"N*T WebSphere+

People Integration

C o m p o s i t e A p p l i c a t i o n F

r a m e w o r k

Process Integration

'ntegrationBroker



Business'ntelligence no#ledge&anageent

Li f e C y cl eM an a g em en t


./)) ABAP






N E !

: B

" e #

a p p $ % &

a ' % o n s

a r e ( )

* # + e &

' s


20/42

20

What is Ne# ` BW Content in the Portal

We can pu"lish anapplication to the Portalas:

A no#ledgeanageent o";ect to acolla"oration roo

A no#ledgeanageent =&>o";ect to a & folder

An ibie# to the Portal+ole

An ibie# to the PortalContent -irectory

Source: SAP A$


"N*T WebSphere+

People Integration

C o m p o s i t e A p p l i c a t i o n F r a m e w o r

k

Process Integration

'ntegrationBroker



Business'ntelligence

no#ledge&anageent

L i f e C y cl eM an a g em en t


./)) ABAP







"N*T WebSphere+

People Integration

C o m p o s i t e A p p l i c a t i o n F r a m e w o r

k

Process Integration

'ntegrationBroker



Business'ntelligence

no#ledge&anageent

L i f e C y cl eM an a g em en t


./)) ABAP






Better #ntegrat#on of BW !ontent #n the portal2

you don’t have to upload #$#ew f#les any1oreJJ


21/42

21

BW !ontent #n the Colla"orat#on Hoo1


"N*T WebSphere+

People Integration

C o m

p o s i t e A p p l i c a t i o n F r a m

e w o r k

Process Integration

'ntegrationBroker


Information IntegrationBusiness

'ntelligenceno#ledge

&anageent

L

i f e C y cl eM an a g em en t


./)) ABAP







"N*T WebSphere+

People Integration

C o m

p o s i t e A p p l i c a t i o n F r a m

e w o r k

Process Integration

'ntegrationBroker


Information IntegrationBusiness

'ntelligenceno#ledge

&anageent

L

i f e C y cl eM an a g em en t


./)) ABAP






KEG IE+2 Bu#ld BW !ontent on!e

and pu"l#sh 1any d#fferent waysJJ

$ood reason to upgrade:

"etter functionality555


22/42

22


• Why upgrade






The "us#ness !ase(taff#ng) durat#on and s!ope



23/42

23

BW Content %pgrades

Apply content &hen you need it, to the technical release you have

(he ne# upgrade strategy fro SAP is to provide BW technicalreleases as part of NetWeaver and B' content add3ons,

0ou do not need to perfor a technical upgrade to update the"usiness content! '!e! content releases such as the older 4!/, 4!4 and4!8< contains ore "usiness content and can "e applied via deltaupgrade!

(he content upgrade can occur in as little as and are shipped on suppleent C-s!

Any ne# upgrade should no# plan to use content provided in 4!8!4!

*0': the content delivered in add3on 4!8!< is the sae as the contentin release 4!


24/42

24

BW Helease %pgrades

Plan a periodic revie& of

ne& content before you

build custom solutions

(he (echnical upgrades are called BW releases!

(his include changes andor additions to technical capa"ilities suchas iproved %-Ss =ver /!> and Process Chains =ver 4!>!

(he release 4!8 is a technical release #ith initial 4!8!< add3on!

4!8 content add3onsinclude:

*uture upgrade strategies needs to

include "oth content as #ell as release

upgrade plans for BW

Warning

4!8!4

(B-

4!8!//nd #eek

of .une

4!8!<

4!8!4*all /997

4!8!/.une /997

4!8!<&arch /997


25/42

25

+n %pgrade (trategy

(hink "igger than BW!!

Apply content as soon as feasi"le! )specially if you have on3goingdevelopent #ork! (his #ay you can avoid any 1#ork3arounds2!

0ou should seriously consider having all NetWeaver coponentson the sae upgrade strategy instead of selecting each coponentfor upgrade! (his #ill help in the shared etractors and alsosu"stantially siplify the upgrade planning and landscape!

Look at SAPs release strategy for eachcoponent you are using and plan ahead,

instead of last3inute 1ust3do2 pro;ects!

Tip


26/42

26


• Why upgrade






The "us#ness !ase(taff#ng) durat#on and s!ope



27/42

27

%pgrade paths

+ d#re!t release upgrade fro1 0.>B) 0./C and 8.>B to 8.- #s poss#"le.

;owever an upgrade fro1 8./C needs to apply 8.0 and 8.8 !ontentaddons "efore upgrad#ng to 8.-.

He1e1"er the ne't release of NetWeaver #s s!heduled for 1#d0>>-.

BW

Version

Release

date

End of mainstream

maintenance

Can be upgraded to

2.0B 8/14/00 12/31/2005 2.1C, 3.0B, 3.1C, 3.50/3.51

2.1C 12/18/00 12/31/2005 3.0B, 3.1C, 3.50/3.51

3.0A 11/15/01 12/31/2005 3.0B, 3.1C, 3.50/3.51

3.0B 5/13/02 12/31/2006 3.1C, 3.50/3.51

3.1C 11/11/02 12/31/2006 3.2 and 3.3 -us' #e app$%ed #efore 3.5

3.2 3/31/03 12/31/2006 3.3 -us' #e app$%ed #efore 3.5

3.3 8/30/03 12/31/2006 3.5

3.5 3/31/04 3/31/2010


28/42

28

%pgrade &replann#ng

It #s #1portant to !o11un#!ate the goals and t#1#ngs to the te!hn#!altea1 to help the1 pr#or#t#Ae the#r resear!h and a!t#v#ty or hardware setup

Co11un#!ate goal of hav#ng e'#st#ng !ontent !ont#nue to wor: to

fun!t#onal test tea1) so they do not get hung up #n test#ng new features

"efore the upgrade #s #n produ!t#on

Hesear!h !hanges to BW or the &lugIN that 1ay affe!t your e'#st#ng

=l#ve? !ontent and use th#s #nfor1at#on to outl#ne a planned =upgrade

regress#on and !orre!t#on test !y!le?

The regress#on test should "e s#1#lar to a large support pa!:

#1ple1entat#on


29/42

29

eter1#ne your upgrade =read#ness?

(+& 3%I , New 3%I roll out) &at!hes< 4e.g. BW 8.>B8./C F.0> B%T…

BW 8.- F.0>F.D>5

&C He9u#re1ents , Need upgrade to ta:e advantage of new features< BW

8.>8./! (a1e &C re9u#re1ents , "ut the dev#l #s #n the deta#ls 4see 7((

/F/8) FF@/5

B7( , +re they supported on the new release< Ta:e the opportun#ty to

apply pat!hes as needed.

'$S ` 'f need rendering of charts and graphs in

BW 4! We" Applications you need '$S B( it

no# only runs under N( and W/! =BW 4!8 #ill

support N'? until '$S 6!79>


30/42

30

&lan the ar!h#te!ture

Cons#derat#ons

3%I upgrade to FD>) or ;ardware !hanges needed I3( and THE "e!o1e part of the FD>BW8- :ernel !an "e on the

sa1e host "o' The old I3( 1ust "e #n pla!e unt#l after graph#! !onvers#on L#ve sour!e syste1 !onne!t#ons 1ust "e refreshed) "ut not re"u#ltJ

Te!hn#!al approa!h Hev#ew Install %pgrade 3u#des as well as upgrade notes &lan when ea!h syste1 #n lands!ape #s upgraded) or an upgraded

syste1 #s !op#ed

)valuate ipact to transport flo# ` duysystes ay "e needed for a sooth transition


31/42

31

Key 6a!tors for you env#ron1ent s#A#ng2

New !ontent 1ore users 1ore app servers<

I3( 1ay re9u#re new hardware

&arallel Load 1ore 1e1ory

7( Layer 1ore spa!e

Crystal Heports new hardware

+r!h#v#ng 1ay redu!e need for spa!e

Ma:e sure the new software #s

ordered and #n handJ


32/42

32

&lann#ng Gour %pgrade

Production


33/42

33

(o1e re9u#re1ents

• If you use (EM) and #t res#des on sa1e #nfrastru!ture w#th BW you

need (EM D.>.

• &lugIn &IOB+(I( 0>>D./OFD> +ll off#!#ally supported &IOB+(I( &I releases !an "e used to !onne!t (+& BW

8.- to a (+& sour!e syste1 4see 7(( note /-8F@5

E'tra!tors are del#vered w#th &IP for uptodate vers#ons of e'tra!tors) #t #sre!o11ended to apply the latest &I #n the sour!e syste1

• No add#t#onal hardware 1ay "e needed

+nother syste1 !an "e used as a te1porary "o' needed to support upgrade May need - , />Q te1porary add#t#onal d#s: spa!e for the produ!t#on sta!:

Need 1#n#1u1 d#s: spa!e 4appro'#1ately /R0> 35 for any new env#ron1ents

Plan for regression test glitches ` and production cut3over!


34/42

34

Hesour!es

• + ed#!ated tea1 w#th a te!hn#!al tea1 lead 4/>>Q5) a Bas#s resour!e

4/>>Q5 and a te!hn#!al rev#ewer 4/>>Q #s re9u#red5.

• In add#t#on) a ded#!ated =goto? resour!e for te!hn#!al #ssues #sre!o11ended. Th#s should "e an #nd#v#dual that have sol#d :nowledgea"out the upgrade and have done h#s "efore. (+& resour!es should "e

!ons#dered) due to the#r !onta!t networ: w#th#n the (+& organ#Aat#on.

• Hegress#on test#ng #s re9u#red on "ehalf or the user !o11un#ty. Th#sshould "e !oord#nated w#th the &ower %sers or e'#st#ng developers.

(ea Lead

Basis

resource

(echnical revie#er pgrade Support

)ternal

+egression (esters

(ea Lead

Basis (echnical revie#er

BW -eveloper

pgrade Support

)ternal

+egression (esters


35/42

35

(a1ple T#1el#ne !o1plete lands!ape for large BW #1ple1entat#on

W< W/ W4 W7 W8 W6 W W WE W

/! (he ne# functionality your are rolling out

4! (he support technology needed ='!e! app servers, $'>


36/42

36

M#n#1u1 T#1el#ne

• Bas#! events2 o #n#t#al upgrade gu#de and note resear!h S/0 days

%pgrade BW sand"o' and do !ursory #ssues !he!: S/D days

%pgrade a !opy of BW produ!t#on , have :ey develop1ent leads

regress#on test all l#ve !ontent 4"oth syste1s 1ust "e !onne!ted

to other lands!ape env#ron1ents , test#ng e'tra!tors tooJ5 S0-

days 4s#Ae!opyhw depend#ng

•

+t a 1#n#1u1) the t#1el#ne w#ll !ons#st of a test upgrade of2 + !opy of the BW evelop1ent syste1 4new !ontent gl#t!hes5

+ !opy of the produ!t#on or produ!t#on support syste1 4BW

&rodu!t#on dryrun and =l#ve !ontent? regress#on test#ng


37/42

37

T#1el#ne 4!ont#nued5

• 7n!e the #n#t#al regress#on test #s !o1plete) !reate any

!orre!t#onal transports. BW 8' to 8- , th#s should "e 1#n#1aldepend#ng on a!t#ve !ontent.S8- days


38/42

38

Move #nto Lands!ape

• +t th#s po#nt you have a te1porary BW ev to test pat!h) and

perhaps stat#! tra#n#ng) produ!t#on and produ!t#on supportsyste1s.

• Ideally) you’d 1#grate the upgrade to these as soon as poss#"le)"ut th#s #s a sta"le po#nt. Gou w#ll have to de!#de) "ased on

!ontent) whether !opy#ng a test "o' to tra#n#ng 1a:es sense 4!anpreserve user 1aster5

• 6or produ!t#on and produ!t#on support) you’ve already done a dryrun , just do produ!t#on and !opy "a!: to produ!t#on supportunless the s#Ae 1a:es th#s #1pra!t#!al SU ->>3B

3%I needs to "e F0> or FD>) w#th

BW 8.- front end pat!h

/on0t

1orget

h #


39/42

39

I1pa!ts to other env#ron1ents

The BW upgrade adds to the &I and +LE !onne!t#on) wh#!h #s "a!:wards

!o1pat#"le. (our!e syste1 !onne!t#ons should re1a#n #nta!t) w#th

1#n#1al adjust1ent) and a repl#!at#on vs. restore

(o1e areas w#ll need to !hange and are "ased on your lo!al !ontent) and

!usto1#Aat#on) "ut you !an !ont#nue to use e'#st#ng 1ethodology unt#l

you de!#de to !hange , see the notesJ

If your end users are we" users) they w#ll see no effe!t#ve !hanges

There should "e no #1pa!t to portal or H8 or other BI syste1 !onne!t#ons

, all dependent on the &lugIn levelownstrea1 data feeds should re1a#n unaffe!ted

-ata #ill not have to "e reloaded or deltas reinitiali@ed in

ore than E8 of cases ` its there already5


40/42

40

@ Key &o#nts to Ta:e ;o1e

• Is #t !heaper to upgrade to new !ontent or r#s: re#nvent#ng the wheel<

• + BW ar!h#te!ture #s part of a larger de!#s#on support lands!ape

• +n upgrade strategy should !onta#n other NetWeaver !o1ponents

• Gou upgrade strategy 1ust #n!lude "oth release and !ontent upgrades

• Gour upgrade t#1e #s largely a fun!t#on of s!ope) your regress#on test

strategy and the a1ount of !ontent #n your BW

•

The BW 8.- upgrade #s pa#nless , no 7( or B upgrades) only a we"9uery graph#!s !onvers#on

• Cross referen!e new features fun!t#onal#ty w#th your organ#Aat#on’s

pa#n po#nts…and ensure the upgrade !osts do not e'!eed the "us#ness

"enef#ts

H


41/42

41

The do!u1ent =;ow to… (+& BW 8.- upgrade preparat#on and post

upgrade !he!:l#st? v/./> Nov. V>D #s ava#la"le at www.sdn.sap.!o1

The do!u1ent !alled =(+&’s Helease (trategy , 6or all Major

(h#p1ents fro1 0>>- on? ava#la"le at www.(+&.!o1

The presentat#on !alled NetWeaver V>D ;#ghl#ghts sess#on I NW0>/

ava#la"le fro1 the s#te www.sapte!hed.!o1

Hesour!es

G T J

http://www.sap.com/index.epxhttp://www.sap.com/index.epx


42/42

Gour TurnJ

How to Contact Me

Bjarne BergDirector Business Intelligence

[email protected]

berg - upgrade strategy v8

Documents