Thursday, November 5, 2009

Upgrade 7.6

Before starting upgrade:
  1. Patch portal to 7.3.5 on dev, qa and live (11/9 - 11/10)
  2. Test with the patch before starting upgrade (11/11 - 11/12)
  3. Change oracle driver class name in vcm config and tomcat conf to oracle.jdbc.driver.OracleDriver
Timeline for upgrade:
  1. Dev: 5 days
  2. QA: 5 days
  3. QA: migration to 64bit - 5 days (on VM and use QA hardware for Prod 64bit?)
  4. Load testing: 5 days
  5. Prod: 10 days
  6. Prod migration to 64bit - 5 days
Follow the Upgrade guide
Order of servers upgrade QA/Prod:
  1. VCM
  2. Autonomy
  3. QA1 & QA2, should be upgrade together, so requires downtime, writedown each step before continuing (Estimate downtime: 8 hrs)
Rough roadmap for VCM upgrade:
  1. Uninstall CCE
  2. Backup Autonomy
  3. Uninstall Autonomy
  4. Stop endpoints
  5. Stop services
  6. install 7.6
  7. run vgnupgrade
  8. Rename old Contnent/7_3_1 directory
  9. Upgrade Autonomy
  10. Post upgrade stuff from ch7
  11. Custom CMA and other apps deployments
  12. DPM deployments, config changes
  13. FURL config
  14. Fixes on Presentation templates and Query Components
  15. Thorough Testing
  16. Patch VCM to 7.6 SP1
  17. Another round of testing

Load Testing QA
  1. Use earlier scripts with webload
  2. Ask for the load tester desktop from Mark, that has all the scripts
  3. Will need to do it off hours


Post Upgrade:
  1. Upgrade to Portal 8.0?
Notes:
------
FURL
  1. Configure FURL
  2. Remove FURL listener in config (Events>Pre create and update)
  3. set furl.exclude.sitename=false
  4. set linkprinter.impl

DPM Menu classes customization in vgn-ext-templating generic resource, rollback component and item region menu to use pre 7.4 classes

PIOCDA
  1. Include Michael's fixes to JSPs (Product detail etc.)
  2. Checkin changes in VSS

No comments: