Progress
Installation and Configuration Guide
Version 9
for Windows


Saving an Existing Progress Installation

If you have an existing Progress installation, you might want to save certain pieces of it to make configuring your new installation simpler. If you want to continue using any templates, customized procedure or code files, or a progress.ini file, you must copy them to another location before you begin a new installation. Follow these steps:

  1. If you have any Version 8 templates that you want to continue using, copy them to another location before installing Version 9. See Table 2–1 for a complete list of Version 8 templates.
  2. Table 2–1 lists the Version 8 templates located in %DLC%\src\template that are no longer supplied with Version 9. (%DLC% represents the Progress installation path.)

    Table 2–1: Version 8 Templates
    childwin.w
    detail.w
    menu-bar.w
    navuprec.w
    custdemo.txt 
    
    dlgclose.w
    navicons.wx
    order.wx
    custom.txt
    dlgokcan.w
    navigate.wx
    orderlin.wx
    dbopsupp.i
    dlgrecup.w
    navread.w
    templdef.i
    defbrupd.i
    doaction.i
    navreadi.w
    winbrows.w
    deffrupd.i
    mainwin.w
    navupd.w

    NOTE: The custom.txt file, which is delivered with Version 9, is a subset of install-path\src\template\progress.cst.

  3. If you have information in a progress.ini file that you want to continue using, copy the current progress.ini file to a directory other than where you are installing Progress.
  4. If you have any customized procedure or code files in the directory where you are installing Progress, copy them into a different directory.
  5. For more information on saving previous versions of your progress.ini, customized procedures, or code files, see the "Finishing the Installation" section.

  6. If you have an earlier version of Progress and the PROMSGS environment variable is set in the autoexec.bat file on Window 98, or on the Environment tab of the System settings in the Windows NT or Windows 2000 Control Panel, you must remove the PROMSGS environment variable before installing Progress Version 9. If PROMSGS points to an old or nonexistent PROMSGS file, the InstallShield utility will not write all the necessary data to the Windows registry.
  7. Truncate the before-image (.bi) file using the PROUTIL TRUNCATE BI utility and back up your Version 8.x database using the PROBKUP utility. For more information on these utilities, see the “Administration Utilities” chapter in the Progress Database Administration Guide and Reference .
  8. NOTE: Progress Version 9 requires that your databases be converted to a multi-volume structure. If you are using single-volume databases with Progress Version 8, you must convert your Version 8 databases to a multi-volume structure before converting the databases to Version 9. (Note that you must truncate your BI file in Version 8 before converting to Version 9.) If you plan to replace Progress Version 8 files with Version 9 files, complete this step before installing Version 9 and avoid erasing your Progress Version 8 files.

  9. Make copies of your ubroker.properties, conmgr.properties, and proxygen.preferences files to another directory. The new installation automatically upgrades the files in the install-path\properties directory. After you have finished your new installation, replace the newly installed versions of these files with your copies. When you start the AdminServer, your older files will be updated to match the current standards for these files.
  10. When you uninstall an existing Progress Version 9 product, the process copies ubroker.properties, conmgr.properties, and proxygen.preferences, the three files in the install-path\properties directory, to \TEMP. After installing a new Progress Version 9 product, you can manually copy back the files from \TEMP.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095