Index: openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html,v diff -u -r1.3 -r1.4 --- openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html 30 Mar 2003 06:04:04 -0000 1.3 +++ openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html 7 Apr 2003 16:59:26 -0000 1.4 @@ -1,13 +1,13 @@ -Upgrading OpenACS 4.5 to 4.6

Upgrading OpenACS 4.5 to 4.6

Checklist

The required platform for OpenACS 4.6 is the same as +Upgrading OpenACS 4.5 to 4.6

Upgrading OpenACS 4.5 to 4.6

Checklist

The required platform for OpenACS 4.6 is the same as 4.5, with the excepion of OpenFTS. You now need OpenFTS 0.3.2, not 0.2. - OpenACS 4.6 does not support PostGreSQL 7.3.

Overview

OpenACS consists of files and a database schema. The files + OpenACS 4.6 does not support PostGreSQL 7.3.

Overview

OpenACS consists of files and a database schema. The files in the OpenACS 4.6 tarball include database upgrade scripts. To start the upgrade, replace your existing files with the new files and then restart the server. Then, browse to the APM, which will detect the new packages and offer to run the appropriate database upgrade scripts. After restarting the server again, the upgrade is - complete.

Figure 6.1. Assumptions in this section

name of OpenACS usernsadmin
OpenACS server nameopenacs-dev
Root of OpenACS file tree/web/openacs-dev
Database backup directory/backup/openacs/

Upgrading on Linux/Unix

  1. Make a Backup.�Back up the database and file system.

    • PostGreSQL.�Create a backup file and verify that it was created and has a reasonable size (several megabytes).

      [root@localhost root]# su - nsadmin
      +    complete.

      Figure 6.1. Assumptions in this section

      name of OpenACS usernsadmin
      OpenACS server nameopenacs-dev
      Root of OpenACS file tree/web/openacs-dev
      Database backup directory/backup/openacs/

    Upgrading on Linux/Unix

    1. Make a Backup.�Back up the database and file system.

      • PostGreSQL.�Create a backup file and verify that it was created and has a reasonable size (several megabytes).

        [root@localhost root]# su - nsadmin
         [nsadmin@localhost aolserver]$ pg_dump -f /backup/openacs/openacs_dev_before_upgrade_to_4.6.dmp openacs-dev
         [nsadmin@localhost aolserver]$ ls -al /backup/openacs/openacs_dev_before_upgrade_to_4.6.dmp 
         -rw-rw-r--    1 nsadmin  nsadmin   4005995 Feb 21 18:28 /backup/openacs/openacs_dev_before_upgrade_to_4.6.dmp