A typical upgrade process comprises of below steps-
1) Evaluate new release, and decide to or not to upgrade.
2) Plan for upgrade,
3) Install new release,
4) Perform Initial Upgrade Pass,
5) Test/Adjustments,
6) Test Move to Production,
7) Test
8) Is Result Acceptable? - if no then make adjustments and go back to step 5)
9) Schedule upgrade cutover date,
10) Perform Final Move to Production (MTP),
11) Final Acceptance Test,
12) Is ready to Go Love? if not then make final adjustments and repeat from step 9)
13) Go Live on new release
Upgrade Process - migrating objects from one database to another and/or updating other system components e.g. software and/or hardware.
Database objects as well as software determine the release level. An upgrade may or may not installing new executable files. During upgrade, one or both of below two tasks are performed in order-
1- Update software,
2- Copy any new objects into database and adjust all system components accordingly.
There are 3 main system components that can be affected by or involved in an upgrade-
1) Environment - Hardware and Software including client and server machines, client and server OS, RDBMS software and database and network software.
2) PeopleTools - Software programs, utility scripts and reports, database tables and data that provide framework for PS applications.
3) Applications - object definitions.
The major phases of an upgrade project are -
1) Initial Pass,
2) Test Move to Production Pass, and
3) Final Move to Production Pass.
1- Initial Pass - the main steps in this pass are -
1) Create a copy of production,
2) Install Demo for new release,
3) Compare and Analyse, here Demo is the source for all new release objects and system data and a copy of production is the target.
4) Once compare analysis is complete, new release is incorporated into copy of production to create first "upgraded copy of production".
2- Test Move to Production Pass - use above created "upgraded copy of production" as source and "a recent copy of production" as target and in iterations, every time and after each pass, a new updated "new copy of production" is created based on most recent production data for each pass.
3- Final Move to Production - Freeze production database. In this final move, the most recent successful output from step-2 is the source and production is the target.
The important tasks carried out during an upgrade project are -
1) Determining upgrade path - determine supported upgrade path, verify whether you can directly upgrade to target release or you need to upgrade to a previous release before moving to target release. Evaluate complexity of upgrade efforts based on number of modules implemented, number of customizations number of interfaces and number of integrations. Determine costs with each aspect of upgrade.
2) Upgrade planning - treat upgrade as a formal project, constitute an upgrade team, decide whether to change or add a business process and prepare a Go Live check list.
3) Evaluate architecture - platform, middleware, non-production hardware ? etc.
4) Calculate sizing and Identify custom code, scripts and interfaces - customizations and custom reports will require extensive testing.
5) Install new release- install verification tests, and get code current by applying the most recent tools and application patches.
6) Technical Upgrade & Retrofitting - identify data migration tasks and minimize application data to upgrade. Test with a copy of production and continue with most current data.
7) Post upgrade activities - end user trainings, functional validation of the system, UAT and Go Live.
7) Post upgrade activities - end user trainings, functional validation of the system, UAT and Go Live.
Posts
No comments:
Post a Comment