Installation

PageSeeder installation and upgrade instructions

Upgrading (to version 5.7)

Warning!

Before installing any upgrade, make a backup of the PageSeeder install folder and the PageSeeder database. To preserve the PageSeeder cache, stop the PageSeeder service before doing the backup.

Warning!

Before upgrading, read the NOTE sections in any release notes after the current version to ensure the project customizations are compatible with the new version.

For information on upgrading to a previous version see Upgrading (to version 5.6 or earlier).

Windows

To upgrade to version 5.7 from version 5.6 or earlier follow these steps:

  1. Upgrade MySQL to version 5.5.3 or later.
  2. Ensure mysql-connector-java-5.1.32.jar or later is in the pageseeder/webapp/WEB-INF/drivers and lib folders and remove older mysql connector .jar files.
  3. Modify the \ProgramData\MySQL\MySQL Server 5.6\my.ini file by changing all instances of utf8 to utf8mb4 and then restart the MySQL service.
  4. Check for duplicate MEMBER_FOR_DGROUP records via the MySQL command line using the SQL below and then delete one row in each duplicate pair, so that this SQL returns no results.
    USE pageseeder;
    SELECT DISTINCT t1.* from MEMBER_FOR_DGROUP t1, MEMBER_FOR_DGROUP t2
    WHERE t1.groupid = t2.groupid AND t1.memberid=t2.memberid AND
    t1.memberforgroupid<>t2.memberforgroupid;
    
  5. Stop the PageSeeder windows service.
  6. Double click on the new pageseeder-x.exe installer.

Note

It may take a few minutes to update the database after PageSeeder starts. To see the progress, or if PageSeeder fails to start, view the pageseeder/webapp/WEB-INF/logs/general/general.log file.

Linux

To upgrade to version 5.7 from version 5.6 or earlier follow these steps:

  1. Upgrade MySQL to version 5.5.3 or later.
  2. Ensure mysql-connector-java-5.1.32.jar or later is in the pageseeder/webapp/WEB-INF/drivers and lib folders and remove older mysql connector .jar files.
  3. Modify the /etc/my.cnf file by changing all instances of utf8 to utf8mb4 and then restart the MySQL service.
  4. Check for duplicate MEMBER_FOR_DGROUP records via the MySQL command line using the SQL below and then delete one row in each duplicate pair so that this SQL returns no results.
    USE pageseeder;
    SELECT DISTINCT t1.* from MEMBER_FOR_DGROUP t1, MEMBER_FOR_DGROUP t2
    WHERE t1.groupid = t2.groupid AND t1.memberid=t2.memberid AND
    t1.memberforgroupid<>t2.memberforgroupid;
    
  5. If not installed already, install Java 7 or later (see which version of java)
  6. Disable any existing SMTP servers as follows:

    service sendmail stop
    chkconfig --del sendmail
    service postfix stop
    chkconfig --del postfix
    
  7. Stop your existing PageSeeder by entering:

    service pageseeder stop
    
  8. Install the latest PageSeeder 5.7 production version as follows:

    rpm -Uvh http://download.pageseeder.com/pub/rpm/pageseeder-repository-1.0-1.noarch.rpm
    yum install pageseeder
    

    or to install a beta version use the following:

    yum install xinetd
    rpm -Uvh http://download.pageseeder.com/pub/rpm/beta/pageseeder-x.y-z.noarch.rpm
    
  9. Migrate the existing PageSeeder data as shown below. Press Enter to accept the default values which should be carried over from the existing PageSeeder.
    sudo service pageseeder migrate
    

    Note

    The Java Options will default back to "-Xmx512m -XX:MaxPermSize=128m". If there were different options or memory settings, enter them when prompted.

  10. If you chose a website port less the 1024 (e.g. 80 or 443 for SSL), configure a proxy from this port to the API port (e.g. 8282). To do this see Configuring a proxy.
  11. Start the PageSeeder service as follows:
    sudo service pageseeder start
    

    Note

    If error "This account is currently not available." is displayed, use the following command but be sure either no password or a secure password are set for the pageseeder user: sudo usermod -s /bin/bash pageseeder

  12. It may take a few minutes to update the database after starting. To see the progress, or if PageSeeder fails to start, view the /opt/pageseeder/webapp/WEB-INF/logs/general/general.log file.
  13. Check that editing documents, adding comments, email notification and replying to emails works, and if everything is OK, delete the old database.properties files as follows:
    rm /usr/old.pageseeder/webapp/WEB-INF/config/*database*
    

Created on , last edited on