1 Reply Latest reply on Jan 14, 2010 3:14 PM by heavywriter

    Review/Input Requested on Upgrade Plan (from RHv7 to RHv8).


      Hi folks!  Hopefully by my asking this and having others review it, it will help others in their upgrade efforts!


      I'm the only "real" technical writer at my company (full-time/titled) and need some support from the community on my grand(iose?) plans.  We're upgrading our KB's from RH7 to RH8 to allow more "authors" to come on board to support me - their basic responsibility is content editing and updating.


      I'd like some input on this plan and see if I'm missing anything BIG or if there's a "gotcha" I didn't mention.  I didn't see anything else on this particular type of upgrade... I think mainly because I dove into the multi-author environment head first and never looked back.


      Current Environment:  Running a front-line support KB in RH7, 4 authors and myself, RSC 3.1 running source control on a database server as project "X".

      Project size and characteristics:  2300 topics; 480 variable, 120 snippets.  Four SSL's for different audiences.  Output is WebHelp on DFS based servers (replicated to remote sites for business continuity - think "mirror" if on web);

      Usage:  60-100 users daily;

      Generation/Publishing: daily when updates occur.

      End State:  RH8, 6 authors, RSC 3.1 running source control on database server as project "Y" (this is to allow us to parallel the RH7 and RH8 releases and retire the bloated RH7 database (two years of changes).


      Procedure(I will perform these steps unless otherwise noted).

      1. Copy source files onto separate machine with RH8 installed (with 8.0.2 update).
      2. Lockdown (partial) database (no changes except emergent).
      3. Open and convert project - denying access to RSC for the project.  (We must still keep RH7 up and running to do emergent updates and backout in case of failure at the end).
      4. Tweak project files (known design changes, templates/master pages, snippets, variables, etc.).
      5. Customize SSL's for testing
      6. Save project as new name and create/rename starting page,
      7. Test Generate and publish all SSLs.
      8. Check publishing.  Repeat above until correct.
      9. Place project into version control.
      10. Test Check In/check out.
      11. Update SSLs to PROD servers.
      12. Update content changes since "partial lockdown".
      13. Generate/Publish/Check content
      14. Announce to users (will have new URLs).
      15. Upgrade existing authors in series.  including:  Deleting old project from hard drive, uninstalling RH7, installing RH8, installing 8.0.2 update, retrieving new project (always a fun time!).
      16. Upgraded authors test check in/check out.
      17. Unfreeze content changes - all changes in RH8 - no changes in RH7 version.
      18. Parallel content for one week.
      19. Remove RH7 generated WebHelp system from PROD.  Replace landing page with redirect.
      20. Archive RH7 database and remove from RSC server.
      21. Bring new authors on individually.


      One additional note.  There is a strong push to add about 3,000 new items to the KB.  I say items because I have not evaluated content and do not know if "items" corresponds to topics.  Could be a 1:1; likely a 1:3 (i.e., 9,000 new items).  These items would probably be limited to only one SSL (group).  Should I put these additional items in a separate project (start afresh) for performance sake?


      Thanks in advance.