Razor(R) Copyright 1992 - 2002 Visible Systems Corporation www.visible.com ************************************************************************** ************************************************************************** ** ** ** UPGRADE NOTES ** ** ** -------------------------------------------------------------------------- Refer to Chapter 2 of the manual, "Installing product upgrades", for general upgrade instructions. If upgrading an NT Server installation, refer to Appendix G, "Doing the install". Please refer to the following notes for specific instructions. -------------------------------------------------------------------------- ** ** ** !!!! IF UPGRADING FROM v3.4 to v4.x !!!! ** ** ======================================== ** NOTE=> Existing users must use the script 'update_db_3.5' to bring their database up to date. To use this script, make sure that you have sourced the rz_prep file to set the proper Razor environment parameters and then simply execute update_db_3.5. The files in the Info directory for each group in the database will be udpdated. The original Info directory will be preserved as a backup and may be removed when you are satisfied that the changes were implemented. The name of the backup directory will be output when the script completes. NOTE=> You must also follow the 3.5 to 4.x instructions as well as the pre-4.1d to 4.x instructions. -------------------------------------------------------------------------- ** ** ** !!!! IF UPGRADING FROM v3.5 to v4.x !!!! ** ** ======================================== ** ** ** NOTE=> You must run the script update_state_dates in order to convert your Issues STATE entries to 4-digit year values. This script will only need to be run one time and will update your Info files. Backup copies of all Info files will be made by the script as a precaution. NOTE=> In order to support file renames, the Thread_script_template.sh has been modified. Users MUST place this file (located in $RAZOR_HOME/templates/Threads_tables_templates) into the Tables directory of each Threads group. NOTE=> The name flag MUST be added to the file: $RAZOR_UNIVERSE_DIR/DOMAIN_01/++ISSUES++/Tables/Reports for each entry which references one of these scripts: rz_issue_summarize rz_issue_display_titles rz_issue_print_titles rz_issue_summarize_short rz_issue_print rz_issue_print_short rz_issue_status.rpt NOTE=> You must also follow the pre-4.1d to 4.x instructions. -------------------------------------------------------------------------- ** ** ** !!!! IF UPGRADING FROM pre-4.1d TO 4.1x !!!! ** ** ============================================= ** ** ** NOTE=> If you are currently using a release of Razor prior to 4.0, you must FIRST follow the appropriate instructions (3.4 to 4.x and/or 3.5 to 4.x). ** The following steps should be followed PRIOR to starting the upgrade process: o Review these RELEASE_NOTES in their entirety. o All files must be checked in. This step is MANDATORY due to major changes to the archival scheme introduced with 4.1d. Also, please make sure that all Archive directories are owned by the owner of the database and have write permission for the owner of the database. We don't normally require that all files be checked in prior to upgrading, however, due to the nature of the changes to the version control system for this release users MUST have all files checked in. o Make sure that you have a backup of all Razor databases. o Exit all Razor tools (issues, versions and threads) o Take down all database servers o "kill" the Razor license manager (razor_lm) ** Invoke the upgrade script: o Upgrade your current release by invoking the script Razor_/scripts/rz_install ** Invoke the following scripts as appropriate: o For EACH database, the owner of the database must run Razor_/scripts/update_db_vcs The following updates will be made to your existing database(s): - $RAZOR_UNIVERSE_DIR/rz_db_exec will be replaced by $RAZOR_UNIVERSE_DIR/bin//rz_db_exec. This change easily accommodates multi-platform access to the same database. - Current threads groups will be renamed from ::Threads to ##Threads. - This script will determine which archive engine is currently in use for each database. If an empty folder (subdirectory) is encountered, the script will query the user for which archival engine to use. The response will be used for ALL subsequent empty folders. o For EACH database that is using remote database synchronization, the owner of the database must update the primary (master) and ALL secondary (slave) sites by running Razor_/scripts/rz_install_remotes. o If you are submitting new issues via e-mail and have customized the rz_mail_issue_catcher script, we recommend that you save a copy of your current script (rename to rz_mail_issue_catcher.orig) prior to executing the next step. o For EACH database and EACH issues group within that database where new issues are submitted via e-mail, the owner of the database must run Razor/scripts/rz_install_email_catcher. o For EACH database that is using the remote e-mail checkout/checkin capability, the owner of the database must run Razor/scripts/rz_install_email_query. ** Update your current IssueWeaver installation by invoking the script Razor_/scripts/rz_iw_install. o If you are currently using a release of IssueWeaver prior to 4.1c.04, we encourage you to review the Release Changes in the document RELEASE_NOTES.old for an overview of the enhancements made to this product. This document is located in the directory 'doc' within the Razor installation. ** Ready to run... o Restart the Razor license manager ( razor_lm & ) ************************************************************************** Detailed release notes may be found in the file RELEASE_NOTES. This file is included in the distribution and may also be downloaded directly from our web site, www.razor.visible.com. Visible Systems Corporation www.visible.com