Index: openacs-4/packages/acs-core-docs/www/openacs.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/openacs.html,v diff -u -r1.22 -r1.23 --- openacs-4/packages/acs-core-docs/www/openacs.html 11 Nov 2003 13:43:45 -0000 1.22 +++ openacs-4/packages/acs-core-docs/www/openacs.html 19 Nov 2003 15:44:50 -0000 1.23 @@ -1,8 +1,7 @@ -Install OpenACS 5.0.0b1

Install OpenACS 5.0.0b1

- by Vinod Kurup
+Install OpenACS 5.0.0b1

Install OpenACS 5.0.0b1

by Vinod Kurup

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

Set up the file system for one or more OpenACS Sites

For Linux Standard Base compliance and ease of backup, +

Set up the file system for one or more OpenACS Sites

For Linux Standard Base compliance and ease of backup, all of the files in each OpenACS site are stored in a subdirectory of /var/lib/aolserver, one @@ -38,7 +37,7 @@ [root@yourserver root]# useradd -g service0 -G web service0 -d /home/service0 [root@yourserver root]#

Install with automated script (EXPERIMENTAL)

Starting with OpenACS 5.0, an experimental script is available to automate all of the steps for the rest of this - section. This only works if the machine already has AOLserver and a compliant database (see previous sections), and tclwebtest. If you are not feeling lucky, skip to the section called “Install from tarball”.

Get the install script from CVS. It is located within + section. Requires tclwebtest. If you are not feeling lucky, skip to the section called “Install from tarball”.

Get the install script from CVS. It is located within the main cvs tree, at /etc/install. Use anonymous CVS checkout to get that directory in the home directory of the service's dedicated user. We put it there so that it is not @@ -224,12 +223,8 @@ in the wrong format, make sure you followed the steps outlined in the section called “Troubleshooting Oracle Dates”

  • Prepare PostgreSQL for an OpenACS Service.�

    • PostGreSQL:

      Create a user in the database matching the service - name. With default PostGreSQL authentication the name of - the user of the process will be matched to this account - automatically.

      [root@yourserver root]# su - postgres
      -[postgres@yourserver pgsql]$ createuser service0
      -Shall the new user be allowed to create databases? (y/n) y
      -Shall the new user be allowed to create more new users? (y/n) y
      +            name.  With default PostGreSQL authentication, a system user connecting locally automatically authenticates as the postgres user of the same name, if one exists.  We currently use postgres "super-users" for everything, which means that anyone with access to any of the openacs system accounts on a machine has full access to all postgresql databases on that machine.

      [root@yourserver root]# su - postgres
      +[postgres@yourserver pgsql]$ createuser -a -d service0
       CREATE USER
       [postgres@yourserver pgsql]$ exit
       logout
      @@ -239,7 +234,8 @@
       CREATE DATABASE
       [service0@yourserver service0]$
       
      su - service0
      -createdb -E UNICODE service0
    • Automate daily database Vacuuming. This is a process which cleans out discarded data from the database. A quick way to automate vacuuming is to edit the cron file for the database user.

      [service0@yourserver service0]$ export EDITOR=emacs;crontab -e

      Add this line to the file. The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day.

      0 1 * * * /usr/local/pgsql/bin/vacuumdb --analyze service0
    • Add Full Text Search Support (OPTIONAL)

    • [service0@yourserver service0]$ exit
      +createdb -E UNICODE service0
    • Automate daily database Vacuuming. This is a process which cleans out discarded data from the database. A quick way to automate vacuuming is to edit the cron file for the database user. Recommended: VACUUM ANALYZE every hour and VACUUM FULL ANALYZE every day.

      [service0@yourserver service0]$ export EDITOR=emacs;crontab -e

      Add this line to the file. The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day.

      0 1-23 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze service0
      +0 0 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze service0
    • Add Full Text Search Support (OPTIONAL)

    • [service0@yourserver service0]$ exit
       logout
       
       [root@yourserver root]# 
  • Configure an AOLserver Service for OpenACS.�

    1. @@ -249,7 +245,7 @@ need to configure a virtual server. The Reference Platform uses a configuration file included in the OpenACS tarball, /var/lib/aolserver/service0/etc/config.tcl. - Open it in an editor to adjust the parameters.

      [root@yourserver root]# su - service0
      +	   Open it in an editor to adjust the parameters.

      [root@yourserver root]# su - service0
       [service0@yourserver service0]$ cd /var/lib/aolserver/service0/etc
       [service0@yourserver etc]# emacs config.tcl
       

      @@ -295,8 +291,7 @@ [service0@yourserver service0]$ /usr/local/aolserver/bin/nsd-postgres -t /var/lib/aolserver/service0/etc/config.tcl [service0@yourserver service0]$ [08/Mar/2003:18:13:29][32131.8192][-main-] Notice: nsd.tcl: starting to read config file... [08/Mar/2003:18:13:29][32131.8192][-main-] Notice: nsd.tcl: finished reading config file.

    2. - Attempt to connect to the service from a web browser. You should specify a URL like: -

      http://yourserver.test:8000

      + Attempt to connect to the service from a web browser. You should specify a URL like: http://yourserver.test:8000

      You should see a page that looks like this. If you imported your files into cvs, now that you know it worked you can erase the temp directory with rm -rf /var/lib/aolserver/service0.orig. @@ -311,7 +306,7 @@ permissions errors or missing files. If you need to make changes, don't forget to kill any running servers with killall nsd. -

    3. Automate +

    4. Automate AOLserver keepalive (OPTIONAL)

  • Configure a Service with the OpenACS Installer.� Now that you've got AOLserver up and running, let's install OpenACS @@ -367,7 +362,7 @@ being restarted; note that unless you already set up a way for AOLServer to restart itself (ie. inittab or daemontools), you'll need to manually restart your service. -

    [service0@yourserver service0]$ /usr/local/aolserver/bin/nsd-postgres -t /var/lib/aolserver/service0/config.tcl
  • +

    [service0@yourserver service0]$ /usr/local/aolserver/bin/nsd-postgres -t /var/lib/aolserver/service0/config.tcl
  • Give the server a few minutes to start up. Then reload the final page above. You should see the front page, with an area to login near the upper right. Congratulations, OpenACS @@ -411,4 +406,4 @@ ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data

  • [service0@yourserver service0]$ exit
     logout
     
    -[root@yourserver root]#
  • Test your backup and recovery procedure.

  • ($Id$)
    View comments on this page at openacs.org
    +[root@yourserver root]#
  • Test your backup and recovery procedure.

  • Set up the section called “External uptime validation”.

  • ($Id$)
    View comments on this page at openacs.org