WHAT EVERY DEVELOPER

SHOULD KNOW ABOUT

UPGRADE
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L 1
Upgrade..............................................................................................................................................3
Overview of the Upgrade Process......................................................................................................4
The Steps.....................................................................................................................................5
Install the New Release......................................................................................................5
Preparation/lean Up........................................................................................................5
Upgrade PeopleTools.........................................................................................................!
o"pare and op# O$%ects...............................................................................................!
reate Ta$les and &lter Ta$les witho't (eletes................................................................!
(ata onversion.................................................................................................................)
o"plete (ata$ase hanges.............................................................................................)
*an'al Set'p.....................................................................................................................)
Test the Upgraded (ata$ase...............................................................................................+
T#pes of Upgrade Passes.............................................................................................................+
The Initial Upgrade Pass...................................................................................................+
The *ove to Prod'ction Upgrade Pass...........................................................................,-
.ow O$%ects /et 0ro" (e"o to op# of Prod'ction......................................................................,,
0'll Release Upgrades to +.,1..................................................................................................,,
o"para$le O$%ects.........................................................................................................,,
Non2o"para$le O$%ects opied via &pp (esigner.......................................................,,
Non2o"para$le O$%ects NOT opied via &pp (esigner..............................................,3
O$%ects NOT *O45(.....................................................................................................,3
0'll Release Upgrades to +.4....................................................................................................,3
o"para$le O$%ects in (ata$ase o"pare.....................................................................,3
o"para$le O$%ects in Pro%ect o"pare.........................................................................,3
Non2o"para$le O$%ects opied via &pp (esigner.......................................................,3
Non2o"para$le O$%ects opied via (ata *over..........................................................,3
O$%ects NOT *O45(.....................................................................................................,3
Service Pac6 Upgrades..............................................................................................................,4
.ow (ata /ets Into the op# of Prod'ction...................................................................................,4
S#ste" (ata.....................................................................................................................,4
(ata onversion..............................................................................................................,4
(oc'"entation.................................................................................................................................,4
&pplication Upgrade (evelop"ent Responsi$ilities.......................................................................,5
(evelop"ent Phase...................................................................................................................,5
S#ste" Test Phase.....................................................................................................................,!
Platfor" Test Phase...................................................................................................................,!
0'nctional Test Phase...............................................................................................................,)
5arl# S'ccess Phase..................................................................................................................,)
Upgrade &ssistant............................................................................................................................,)
2 ERROR ! NO T E X T OF S P E CI F I E D S T Y L E I N DOCUME N T . PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L
2
A DE V E L OP E R ' S GUI DE T O UP GRA DE AUGUS T 2 014
Upgrade
Upgrade is the "ethod c'sto"ers 'se to "ove their prod'ction s#ste" fro" one release to
another.
0or "ost applications7 "ore c'sto"ers will 'pgrade to #o'r new release than will i"ple"ent
fro" scratch 8and #et7 'pgrade contin'es to $e an aftertho'ght for "ost developers9. That "eans
that #o'r c'sto"ers will 'se an 'pgraded data$ase in prod'ction. .aving a perfect (*O
data$ase "eans nothing if the prod'ct fails to e1ec'te on c'sto"er:s converted data.
0ro" the c'sto"er:s point of view this is their first e1pos're to the new release. The# 6now onl#
the old release. Their first i"pression of the new PeopleSoft release will $e $ased on their
e1perience with the 'pgrade.
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L ERROR ! NO T E X T OF S P E CI F I E D S T Y L E I N DOCUME N T . 3
3
AUGUS T 2 014 A DE V E L OP E R ' S GUI DE T O UP GRA DE
Overview of te Upgrade Pro!e""
PeopleSoft 'pgrades are $ased on a standard process with specific places that #o' as the
application developer can add to the process. This section of this doc'"ent will review that
process and highlight the points where #o' can add to the process. It is i"portant to sta# within
the esta$lished process. hanges in the flow slow down and co"plicate an alread# co"plicated
and detailed process.
In order to 'se a new release of Peoplesoft o'r c'sto"ers appl# the new o$%ects onto their e1isting
data$ase. This is a 6e# concept #o' need to 'nderstand $efore starting develop"ent of a new
'pgrade.
4 ERROR ! NO T E X T OF S P E CI F I E D S T Y L E I N DOCUME N T . PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L
4
A DE V E L OP E R ' S GUI DE T O UP GRA DE AUGUS T 2 014

DMO
Target
Source
Copy o
Pro!uct"o#
The op# of Prod'ction data$ase sta#s intact.
The o$%ect changes are copied fro" (e"o 8So'rce9 onto the c'sto"er;s data$ase 8Target9.
The c'sto"er;s data is 'pdated d'ring data conversion to "a6e it wor6 with the new release.
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L ERROR ! NO T E X T OF S P E CI F I E D S T Y L E I N DOCUME N T . 5
5
AUGUS T 2 014 A DE V E L OP E R ' S GUI DE T O UP GRA DE
The St eps
<e 'se a standard set of 'pgrade steps for all prod'ct lines. =o' will $e developing the
application specific portions of this process. The following diagra" shows the steps in a
PeopleSoft Upgrade. & $rief description of each step follows the chart.
Preparation/Cleanup
Preparation/Cleanup
Install the New Release
Install the New Release
Upgrade PeopleTools
Upgrade PeopleTools
Compare and Copy Objects
Compare and Copy Objects
Create and Alter Tables without eletes
Create and Alter Tables without eletes
ata Con!ersion
ata Con!ersion
Test "our Upgraded atabase
Test "our Upgraded atabase
Complete atabase Changes
Complete atabase Changes
Copy o# Production at
Original Release
$Target%
Copy o# Production at
Original Release
$Target%
New Release
emo atabase
$&ource%
New Release
emo atabase
$&ource%
Copy o# Production at
New Release
Copy o# Production at
New Release
*ove to Prod'ction
'anual &etup
'anual &etup
I#"ta$$ te New Re$ea"e
This step will set 'p the new release environ"ent. It can $e done independentl# of
Preparation/lean Up $eca'se the Preparation/lean Up is done 'sing the old release of the
application.
,. The c'sto"er installs the new (*O data$ase 8not S=S97 which will $e 'sed as the So'rce
data$ase d'ring the 'pgrade.
3. The# install the code line for the new application.
3. The# search 'sto"er onnection for >re?'ired for 'pgrade@ fi1es7 and appl# the" to the
(*O data$ase.
Preparatio#%C$ea# Up
,. The c'sto"er creates a cop# of their prod'ction data$ase7 on which the#;ll perfor" the
'pgrade. 'sto"ers do not r'n the 'pgrade directl# on their prod'ction data$ase 8'ntil the
final *ove to Prod'ction pass9.
6 ERROR ! NO T E X T OF S P E CI F I E D S T Y L E I N DOCUME N T . PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L
6
A DE V E L OP E R ' S GUI DE T O UP GRA DE AUGUS T 2 014
3. The# r'n a'dits to "a6e s're the prior release data$ase is clean.
3. The# r'n reports to verif# that application data is clean. If the# find that there are data
pro$le"s7 the# clean it 'p at this point.
4. The c'sto"er "a6es f'nctional decisions and sets 'p the data$ase for the 'pgrade. This is
where c'sto"ers will s'ppl# infor"ation as to how the# will 'se the new release so that data
conversion can correctl# convert their data. In this step7 the c'sto"er perfor"s an# anal#sis
and decision "a6ing prior to perfor"ing the 'pgrade. This can incl'de r'nning reports to
list data that will $e deleted7 or pop'lating Aset'pA pages re?'ired for the conversion. It
re?'ires f'nctional e1perts to start $eco"ing fa"iliar with new release. Note that this
f'nctional anal#sis is not done in Service Pac6 'pgrades.
Upgrade Peop$eToo$"
This step will $ring the c'sto"er:s data$ase 'p to the c'rrent Tools release. This section is
provided $# PeopleTools.
,. Upgrade PeopleTools to new release on the op# of Prod'ction. &t this point the old
application is on new Tools. The s#ste" is not 'sea$le at all7 e1cept to do the o"pare and
op#.
Co&pare a#d Cop' O()e!t"
Now that op# of Prod'ction and (*O are on sa"e Tools7 can do a f'll data$ase co"pare7 and
cop# pro%ects fro" one data$ase to the other.
,. Rena"e scripts are r'n $efore starting the co"pare so that the rena"ed o$%ects can $e
co"pared to the o$%ect of the sa"e na"e on the (*O data$ase.
3. & o"pare is r'n on the (*O data$ase7 co"paring to the c'sto"er:s op# of Prod'ction.
.ow these co"pares are r'n is different for the vario's 'pgrades. See the section $elow on
how o$%ects get fro" (e"o to the op# of Prod'ction for "ore infor"ation on these
co"pares. The res'lt of a co"pare is a pro%ect8s9 on the (*O data$ase7 showing differences
in o$%ect definitions.
3. The c'sto"er reviews the co"pare reports to anal#Be c'sto"iBations 8where needed9. This
is a long decision "a6ing process. The "ore the# 6now a$o't their c'sto"iBations7 the
$etter. The# 'pdate the o"pare pro%ect8s9 to indicate whether the# want to 6eep each
c'sto"iBation.
4. <hen the# are read#7 the# cop# the pro%ect fro" (*O to their op# of Prod'ction
Create Ta($e" a#d *$ter Ta($e" wito+t De$ete"
In this step7 the ph#sical str'ct're of the SCD ta$les is changed.
,. &ll new ta$les are created.
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L ERROR ! NO T E X T OF S P E CI F I E D S T Y L E I N DOCUME N T .

AUGUS T 2 014 A DE V E L OP E R ' S GUI DE T O UP GRA DE

3. &ll new fields are added to the ta$les7 $'t no data or fields are deleted at this ti"e. This
"eans that all old data is still availa$le while all new str'ct'res are also availa$le. This step
is referred to as the &lter witho't (eletes step.
This &lter can ta6es "an# ho'rs7 and it will hit "an# pro$le"s with siBing and "a1
e1tents. The c'sto"er needs all the infor"ation we can give the" as to how to siBe
ta$les in order to "a6e this step easier.
3. &ll new and changed inde1es are created at this ti"e. So"e inde1es will not create at this
ti"e d'e to 'ni?'e constraint errors. This is e1pected. =o' will need to correct the data
d'ring data conversion so that these inde1es will create d'ring the &lter with (eletes step
later in the 'pgrade.
Data Co#ver"io#
The alter step in the previo's tas6 did not delete an# data fro" the old fields and records in the
c'sto"er:s data$ase. In this step7 old data will $e converted to new for"ats. =o' will spend
"ost of #o'r develop"ent effort in coding these &pplication 5ngine progra"s.
,. The c'sto"er loads all "essages and new record gro'ps at this ti"e fro" the (*O
data$ase.
3. &n# inde1es needed for data conversion progra" perfor"ance are created now.
3. &pplication 5ngine progra"s are r'n to "ove data fro" old places to new places. ('ring
the initial 'pgrade pass these progra"s fail often. These fail'res can $e d'e to the c'sto"er;s
c'sto"iBed records or siBing errors with ta$les7 ta$lespaces7 and roll$ac6 seg"ents when
these progra"s load a lot of data into ta$les. The progra"s "'st $e restarta$le so that the#
can fi1 the pro$le" and contin'e. <e s'ppl# siBing reco""endations $ased on data
conversion to help this.The c'sto"er needs all the infor"ation we can give the" as to how
to siBe ta$les in order to "a6e this step easier.
Co&p$ete Data(a"e Ca#ge"
,. Ta$les are altered to re"ove o$solete col'"ns. Now that (ata onversion is co"pleted7 the
old fields can $e deleted.
3. &ll inde1es sho'ld create witho't error now.
3. &ll views are created at this point. Note that views are not availa$le d'ring data conversionE
the# are created after data conversion.
4. &ll s#ste" data which the c'sto"er will need to r'n the new release is loaded. S#ste" data
is an# data that is s'pplied $# PeopleSoft that is needed for the s#ste" to r'n. &lso loaded at
this ti"e are 5(I definitions7 *ass hange definitions and String data.
Ma#+a$ Set+p
There are 'pdates that "'st $e done "an'all# 'sing the new application. These are steps that
%'st cannot $e a'to"aticall# done with conversion code. These steps are done $# the f'nctional
e1perts on the 'pgrade tea".
! ERROR ! NO T E X T OF S P E CI F I E D S T Y L E I N DOCUME N T . PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L
!
A DE V E L OP E R ' S GUI DE T O UP GRA DE AUGUS T 2 014
The# will r'n application processes to co"plete the s#ste" set'p.
Pages are 'pdated where the s#ste" will not wor6 correctl# 'ntil the 'pdate is done.
The c'sto"er can now reappl# an# c'sto"iBations the# want to 'se in the new release.
The# r'n S#s&'dit7 (((&'dit and &lter a'dits to verif# the s#ste" is clean.
Feep in "ind that an# "an'al steps #o' add here "'st $e repeated several ti"es d'ring Test
*oves to Prod'ction and the final *ove to Prod'ction 2 which is a $ad thingG The *ove to
Prod'ction passes sho'ld $e a'to"ated and strea"lined.
Te"t te Upgraded Data(a"e
The c'sto"er tests the 'pgraded data$ase. an the# do an#thing with the new s#ste"H
T"pes #$ Up%& '(e P'sses
There are two t#pes of 'pgrade passes that a c'sto"er will doI Initial and *ove to Prod'ction.
This section descri$es each7 and shows their differences and si"ilarities.
Te I#itia$ Upgrade Pa""
I nitial Upgrade Pass
(Source)
Copy of
Production
1. Prepare DB
2. Upgrade PT
4. Create/Alter
5. Data Conversion
6. Alter with Delete
7. an!al "et!p
#. Co$pare/
Cop%
DMO
(Target)
The steps are the ones listed a$ove.
This is the first pass thro'gh the 'pgrade process.
The c'sto"er will onl# do this once7 and it ta6es 42! wee6s.
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L ERROR ! NO T E X T OF S P E CI F I E D S T Y L E I N DOCUME N T . )
)
AUGUS T 2 014 A DE V E L OP E R ' S GUI DE T O UP GRA DE
&ll decisions are "ade d'ring the initial 'pgrade pass.
The# will set 'p new sec'rit# and new feat'res d'ring this pass7 and the changes are
a'to"aticall# "oved forward in the *ove to Prod'ction.
The# reappl# c'sto"iBations once d'ring this pass and the changes are a'to"aticall# "oved
forward in the *ove to Prod'ction.
*ost 'pgrade tro'$leshooting occ'rs here.
10 ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L
10
A DE V E L OP E R ' S GUI DE T O UP GRA DE AUGUS T 2 014
Te Move to Prod+!tio# Upgrade Pa""
&ll the previo's steps were done on a cop# of the c'sto"er:s prod'ction data$ase. This step tells
the" how to 'pgrade the real thing. It contains co"pletel# different instr'ctions7 so"e of which
are a s'$set of the previo's instr'ctions.
I nitial Upgrade Pass
Copy of
Production
Test Move to Production
NEW Copy of
Production
(Source)
(Target)
1. Prepare DB
2. Upgrade PT
#&. '$port Data
4. Create/Alter
5. Data Conversion
6. Alter with Delete
7. an!al "et!p
(epeat)
DMO
#a. *+port Data
The *ove to Prod'ction is different set of steps that shortc't the steps in initial pass.
'sto"ers will r'n test the *ove to Prod'ction "'ltiple ti"es7 'ntil the# are co"forta$le
with the process J ti"ing. 8<ill it fit in c'sto"er go2live windowH9
In order for the c'sto"er to go live in a wee6end this process sho'ld ta6e no "ore than 3
da#s.
These steps are done on go2live wee6end when the c'sto"er does their final *ove to
Prod'ction.
(ata conversion perfor"ance is the $iggest contri$'tion to shorter go2live windows.
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . 11
11
AUGUS T 2 014 A DE V E L OP E R ' S GUI DE T O UP GRA DE
,ow O()e!t" -et Fro& De&o to Cop' of Prod+!tio#
DMO
Target
Source
Copy o
Pro!uct"o#
'sto"ers create a cop# of their prod'ction data$ase and a (e"o data$ase for the new release.
The# then co"pare and cop# o$%ects fro" (e"o into the cop# of prod'ction. .ow the# do this
varies $# what t#pe of 'pgrade the# are doing 8Service Pac6 or f'll release 'pgrade9. It also
changed $etween PeopleTools +.,1 and +.4.
12 ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L
12
A DE V E L OP E R ' S GUI DE T O UP GRA DE AUGUS T 2 014
F*+ + Re+ e'se Up%& '(es t # !, 1-
Co&para($e O()e!t"
This categor# covers "ost PeopleTools o$%ects. These o$%ects are handled $# the
'pgrade process with the PeopleTools data$ase co"pare
So"e e1a"ples of these o$%ectsI
Records
Pages
Peoplecode
&pplication 5ngine
No#.Co&para($e O()e!t" Copied via *pp De"ig#er
These o$%ects do not have &pplication (esigner o"pare s'pport.
The# are copied via a pro%ect delivered in the (*O data$ase. This pro%ect is created $#
5ngineering Services d'ring final pac6aging.
The affected o$%ect t#pesI
&ccess /ro'ps
Trees 8C'er# trees onl#. Not ones 6e#ed $# setid9
No#.Co&para($e O()e!t" NOT Copied via *pp De"ig#er
These o$%ects are copied via (ata"over scripts. The# are e1ported fro" the (*O data$ase
and then i"ported into the c'sto"er;s op# of Prod'ction.
5ngineering Services delivers the scripts
The affected o$%ect t#pesI
Record /ro'ps
5(I (efinitions
*ass hange
*essage atalog
Strings
O()e!t" NOT MO/ED
These o$%ects are considered data in o'r data$ase7 and are not copied to the c'sto"er;s data$ase.
If #o' feel that #o' have an instance of one of these o$%ect t#pes that "'st $e incl'ded in the
'pgrade wor6 with 5ngineering Services to have it added to the UP/NONO*P pro%ect.
O$%ect T#pesI
Trees 86e#ed $# setid9
Roles
Per"ission Dists
*essage Nodes
'$e (efinitions
'$e Instance (efinitions
(i"ensions
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . 1 3
13
AUGUS T 2 014 A DE V E L OP E R ' S GUI DE T O UP GRA DE
F*+ + Re+ e'se Up%& '(es t # !, 4
Co&para($e O()e!t" i# Data(a"e Co&pare
This categor# covers "ost PeopleTools o$%ects. These o$%ects are handled $# the 'pgrade process
with the PeopleTools data$ase co"pare. The data$ase co"pare $'ilds the pro%ect that will $e
copied. It will detect o$%ects that are in the c'sto"er:s data$ase and not in the new release and
delete the" as well as appl#ing all new definitions to the data$ase.
&ll co"para$le o$%ect t#pes that are not on an# of the $elow lists are incl'ded in the data$ase
co"pare. So"e e1a"ples of these o$%ectsI
Records
Pages
Peoplecode
&pplication 5ngine
Pro$le" T#pes
&pplication Pac6ages
Co&para($e O()e!t" i# Pro)e!t Co&pare
So"e o$%ects are co"para$le $'t contain infor"ation that is 'ni?'e to the c'sto"er7 so that we
don;t want to delete an# of the instances that the c'sto"er has created. K't so"eti"es we want
the c'sto"er to have the PeopleSoft instances also. <e p't these o$%ects into a pro%ect. The
c'sto"er will then co"pare and cop# the" witho't r'nning the ris6 of deleting their own
instances. <or6 with the Upgrade (evelop"ent Dead to get #o'r o$%ects into this pro%ect.
O$%ects that can go into the pro%ect co"pare areI
.T*D
Per"ission Dists
URD (efinitions
*essage Nodes
No#.Co&para($e O()e!t" Copied via *pp De"ig#er
These o$%ects do not have &pplication (esigner o"pare s'pport. The# are copied via a pro%ect
delivered in the (*O data$ase. This pro%ect will $e created $# #o'r the Upgrade (evelop"ent
Dead $'t the &ccess /ro'ps and C'er# Trees will $e refreshed d'ring data$ase pac6aging.
If #o' need to deliver an# of these o$%ect t#pes d'ring the 'pgrade the# sho'ld $e p't in this
pro%ectI
(i"ensions
'$e (efinitions
'$e Instance (efinitions
&ll of the following fro" #o'r release are delivered in this pro%ectI
&ccess /ro'ps
Trees 8C'er# trees onl#. Not ones 6e#ed $# setid9
No#.Co&para($e O()e!t" Copied via Data Mover
These o$%ects are copied via (ata *over scripts. The# are e1ported fro" the (*O data$ase and
then i"ported into the c'sto"ers op# of Prod'ctions. 5ngineering Services delivers the scripts.
14 ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L
14
A DE V E L OP E R ' S GUI DE T O UP GRA DE AUGUS T 2 014
The affected o$%ect t#pesI
Record /ro'ps
5(I (efinitions
*ass hange
*essage atalog
Strings
O()e!t" NOT MO/ED
These o$%ects are considered data in o'r data$ase. If #o' feel that #o' have an instance of one of
these o$%ect t#pes that "'st $e incl'ded in the 'pgrade wor6 with 5ngineering Services to have it
added to the UP/NONO*P pro%ect.
O$%ect T#pesI
Trees 86e#ed $# setid9
Portal Registr# User .o"e Pages
Portal Registr# User 0avorites
Pro$le" T#pes
Roles&nal#sis
*odels
0ile Reference O$%ects
Se& ./ 0e P'01 Up%& '(es
0or Service Pac6 'pgrades7 5ngineering Services $'ilds a pro%ect containing all o$%ects changed
d'ring develop"ent and delivers the pro%ect in the (e"o (ata$ase for the Service Pac6. The
c'sto"er will co"pare and cop# this pro%ect and the non2co"para$le pro%ect.
,ow Data -et" I#to te Cop' of Prod+!tio#
S'"te& Data
S#ste" data is an# data that is s'pplied $# PeopleSoft that is needed for the s#ste" to r'n. It is
the onl# data in a S#ste" data$ase that a new c'sto"er installs as their prod'ction s#ste".
(evelop"ent defines the Install s#ste" data. &t the sa"e ti"e7 the# specif# whether the data
sho'ld $e copied to c'sto"er;s data$ase d'ring 'pgrade and how it sho'ld $e loaded.
(efine the appropriate action for each s#ste" data ta$le on >Pac6aging7 (efine Installation
(ata.@
5ngineering Services pac6ages appropriate (ata"over scripts to load the data d'ring the
'pgrade.
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . 1 5
15
AUGUS T 2 014 A DE V E L OP E R ' S GUI DE T O UP GRA DE
Data Co#ver"io#
(ata onversion is r'n at the point in the 'pgrade that the c'sto"er has all of the new ta$les and
col'"ns7 $'t old col'"ns have not $een deleted. (ata onversion sho'ld 'pdate all new
col'"ns that can not 'se the defa'lt val'e delivered on the Record 0ield definition.
(evelop"ent writes the data conversion progra"s.
(ata conversion is written entirel# in &pplication 5ngine progra"s
This is where "ost of the 'pgrade develop"ent effort is spent
Perfor"ance of these progra"s "'st $e good so that the *ove to Prod'ction pass can $e
done in one wee6end.
Do!+&e#tatio#
There is "ore than %'st codingG
Pre2Upgrade Preparation and Post2Upgrade *an'al steps re?'ire ver# detailed f'nctionall#
oriented doc'"entation.
*'st doc'"ent what 8and wh#GG9 #o' are doing in &pp 5ngine sections. In +.4 do this in the
o""ent field on the sections #o' will have called fro" the driver. <e deliver a report that
will print those co""ents for doc'"entation.
0or +.,17 doc'"ent #o'r application engine sections in the appendi1.
Incl'de e1tra appendi1es to e1plain the $ig pict're conversion of "a%or feat're changes.
Upgrade doc'"entation is not the sa"e doc'"entation as Release Notes. It sho'ld wor6 in
con%'nction with the".
*pp$i!atio# Upgrade Deve$op&e#t Re"po#"i(i$itie"
=o' have $een assigned to the Upgrade pro%ect for #o'r prod'ct;s latest release. =o'r
responsi$ilities as the application developer fro" #o'r prod'ct will change over the life of the
pro%ect.
De.e+ #p2e3t Ph'se
This phase starts d'ring the develop"ent c#cle of #o'r prod'ct and contin'es 'ntil the freeBe
date. =o' will have a doc'"entation freeBe date and a coding freeBe date. See #o'r Pro%ect Dead
for infor"ation a$o't these dates. =o'r responci$ilites d'ring this phase are as followsI
(esign #o'r 'pgrade
16 ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L
16
A DE V E L OP E R ' S GUI DE T O UP GRA DE AUGUS T 2 014
<or6 with #o'r Prod'ct *anager and develop"ent tea" to anal#Be and list the
wa#s in which #o'r prod'ct has changed since the last release that wo'ld affect the
c'sto"er who is 'pgrading to the new release. *ost tea"s have developed so"e
wa# for 6eeping trac6 of these 6inds of changes.
Review all &dded and (eleted Records and 0ields to deter"ine if the# have 'pgrade
i"pact. This infor"ation can $e gathered fro" the co"pare reports that are
s'pplied $# the 5nviron"ents *anage"ent Upgrade tea".
=o' will s'ppl# test data in the target data$ase that is 'sed for all testing. Part of
testing a conversion is having ade?'ate data to test the conversions. The 'nit test
data$ases that will $e s'pplied7 on which #o' will test #o'r data conversions7 will $e
$'ilt 'sing this target. &s #o' develop conversions7 chec6 the data in the 'nit test
data$ases and add an# data necessar# to co"pletel# test the 'pgrade code into the
target data$ase.
oding and (ata
<rite an# code re?'ired for rena"ing7 data conversion7 and other application
changes. =o'r code will $e e1pected to "eet all standards in the Upgrade oding
Reference /'ide. There will $e a'dits and code reviews done to verif# that #o'
have "et the standards.
Unit test #o'r co"ponents of the 'pgrade process 8fro" $eginning to end on
SCDServer9 'sing the instr'ctions and co"ponents #o' have prepared. The
5ngineering Services Upgrade tea" will s'ppl# 'nit test data$ases. These data$ases
are at the point of data conversion so that #o' can do this testing.
=o'r Pro%ect Dead 8wor6ing with the 5ngineering Services Dead9 will co"$ine #o'r
data conversion sections into 'pgrade drivers. =o' will need to "a6e s're all of
#o'r data conversion infor"ation is given to the Pro%ect Dead. The wa# we co"$ine
these is different in +., and +.4.
=o' will need to "a6e s're that the (efine Upgrade S#ste" (ata page is co"plete.
<hen S#ste" (ata is defined for Install it is not added into the 'pgrade. To add it
into the 'pgrade the (efine Upgrade S#ste" (ata page needs to $e co"pleted.
(oc'"entation
Review the developer;s drafts of the 'pgrade doc'"entation. Doo6 not onl# at the
parts #o' added7 $'t at all of the application2specific content to $e s're it is
co"plete and acc'rate.
=o' will write the Upgrade instr'ctions for all Pre2Upgrade and Post2Upgrade
*an'al hange steps of the 'pgrade.
S'ppl# doc'"entation on what #o'r data conversion progra"s are doing. .ow this
is s'pplied to c'sto"ers varies fro" +., to +.4.
=o' will need to s'ppl# a list of large ta$les7 what is $eing done to the". The
c'sto"er also needs infor"ation on new ta$les and how the# are $eing loaded. <e
s'ppl# siBing infor"ation 'sing this infor"ation.
<rite descriptions of how #o'r application has changed in areas where the 'ser
needs to ad%'st or add new set'p or processing data. This infor"ation will $e going
into the Upgrade instr'ctions so $e s're that #o' are clear and concise in #o'r
descriptions. 'sto"ers depend on this infor"ation.
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . 1
1
AUGUS T 2 014 A DE V E L OP E R ' S GUI DE T O UP GRA DE
reate doc'"entation I5s to have changes "ade to the 'pgrade doc'"entation.
S"st e2 Test Ph'se
This phase is when the 'pgrade is tested fro" $eginning to end on *icrosoft SCD Server. This
test is r'n $# the 5nviron"ent *ange"ent Upgrade tea" and test incidents will $e assigned for
an# pro$le"s fo'nd. Kefore S#ste" Test starts #o' need to have loaded all data into the target
data$ases s'pplied $# 5nviron"ents *anage"ent. &ll of #o' coding sho'ld $e co"plete $# this
phase so that the progra"s can $e co"pletel# tested.
0i1 an# reported incidents fro" S#ste" Test. &pplication tea"s are responsi$le for fi1ing
an# pro$le"s with the code.
&pplication 5ngine code will $e reviewed for perfor"ance. =o' will need to "a6e the
re?'ired changes to i"prove the 'pgrade perfor"ance.
&nswer an# ?'estions and respond to an# iss'es that arise fro" the testing effort.
P+ 't $ #& 2 Test Ph'se
This phase is when the 'pgrade is tested fro" $eginning to end on all other platfor"s. This test is
r'n $# the 5nviron"ent *ange"ent Platfor" test tea" and test incidents will $e assigned for
an# pro$le"s fo'nd. Kefore Platfor" testing can $egin there will $e several s#ste" test passes
and a red'ction of the n'"$er of incidents $eing reported needs to $e on the decline. *ost of the
pro$le"s fo'nd d'ring this test phase can $e avoided $# reviewing the >SCD (ifferences /'ild@
on the (evelopers Portal.
0i1 an# reported incidents fro" Platfor" Test. =o'r Pro%ect Dead will assign incidents as
the# co"e in and application tea"s are responsi$le for fi1ing an# pro$le"s with the code.
=o' will #ot have a 'nit test environ"ent on each platfor". =o' will need to wor6 directl#
with the platfor" testers to resolve so"e of these iss'es.
&nswer an# ?'estions and respond to an# iss'es that arise fro" the testing effort.
Review the draft 'pgrade doc'"entation. There will $e two review c#cles d'ring Platfor"
testing. =o' will have one wee6 to create I5 incidents to correct an# pro$le"s #o' find.
F*30t / #3'+ Test Ph'se
This phase is not done for Service Pac6s. The 'pgrade is r'n fro" $eginning to end on *icrosoft
SCDServer and the res'lting data$ase is s'pplied for review. This test is r'n $# the &pplication
tea"7 often $# the C& tea" $'t this can var#. This test phase verifies that the 'pgraded data$ase
will f'nction correctl# and that converted data is still 'sa$le. Test incidents will $e assigned for
an# pro$le"s fo'nd. The 'pgrade "'st $e co"plete 8no new code9 and hopef'll# sta$le $efore
this testing can $egin.
(ata is needed in the Target data$ases so that it can $e verified after the 'pgrade. This data is
needed prior to the 'pgrade. It is no good to load a data far" onto an 'pgraded data$ase.
Perfor" an# "an'al f'nctional preparation of the f'nctional test data$ases.
0i1 an# reported incidents fro" 0'nctional Test. This can $e tric6#. =o' need to anal#se
where in the process the pro$le" occ'rred. =o' will have to review the logs fro" the
1! ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L
1!
A DE V E L OP E R ' S GUI DE T O UP GRA DE AUGUS T 2 014
'pgrade pass to see that #o'r code e1ec'ted correctl#. Other co""on pro$le"s fo'nd
thro'gh this testing is that s#ste" data was not defined correctl# so the data$ase is "issing
that data.
&nswer an# ?'estions and respond to an# iss'es that arise fro" the testing effort.
E'&+ " S*00ess Ph'se
This phase is not done for Service Pac6s. 'sto"ers are chosen to do the 'pgrade $efore it is
generall# availa$le. These c'sto"ers do the 'pgrade with the assistance of PS and get
develop"ent s'pport directl#. Pro$le"s d'ring this phase are still entered as test incidents.
Pro$le"s are not called into the /S $'t at "ade directl# to a develop"ent contact. This phase
happens $etween #o'r last prod'ct $'ild and the Upgrade /& date.
0i1 an# reported incidents fro" the c'sto"res and get the" into the Upgrade $'ilds.
Ke availa$le to answer an# ?'estions and respond to an# iss'es fro" the c'sto"er.
Upgrade *""i"ta#t
Upgrade &ssistant is an a'to"ation tool 'sed $# o'r c'sto"ers to organiBe and r'n the 'pgrade.
<e deliver a te"plate that contains each tas6 and step in the 'pgrade doc'"entation. The
c'sto"er opens the te"plate and then defines their 'pgrade %o$. The %o$ contains the
infor"ation a$o't the data$ase platfor"7 prod'cts7 and lang'ages the c'sto"er is 'pgrading.
The %o$ then screens the te"plate infor"ation and gives the c'sto"er the tas6s and steps that
the# need to r'n.
The te"plates are created and "aintained $# 5ngineering Services. There is a different te"plate
for each 'pgrade path for #o'r 'pgrade 8i.e. ).5 to +.4 or +.-3 to +.49. <hen #o' add or re"ove a
step or tas6 fro" the 'pgrade7 the change "'st $e "ade to the te"plate for that 'pgrade path.
PE OP L E SOF T PROP RI E TA RY A ND CONF I DE N T I A L ERRO R ! NO T E X T OF S P E CI F I E D S T Y L E I N DOC UME NT . 1 )
1)
AUGUS T 2 014 A DE V E L OP E R ' S GUI DE T O UP GRA DE