| Prev | Next |
Table of Contents
Table of Contents
Oracle
[root aolserver]#cd /usr/local/aolserver/bin-[root bin]#cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/nsd-oracle.txt ./nsd-oracle+[root bin]#cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/nsd-oracle.txt ./nsd-oracle[root bin]#chmod 750 nsd-oracle[root bin]# cd /usr/local/aolserver/bin -cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/nsd-oracle.txt ./nsd-oracle +cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/nsd-oracle.txt ./nsd-oracle chmod 750 nsd-oracle
PostgreSQL
[root aolserver]#cd /usr/local/aolserver/bin-[root bin]#cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/nsd-postgres.txt ./nsd-postgres+[root bin]#cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/nsd-postgres.txt ./nsd-postgres[root bin]#chmod 755 nsd-postgres[root bin]# cd /usr/local/aolserver/bin -cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/nsd-postgres.txt ./nsd-postgres +cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/nsd-postgres.txt ./nsd-postgres chmod 755 nsd-postgres
Install tDOM.�Download the tDOM tarball, unpack it, adjust the configuration file to match our patched distribution of aolserver, and compile it.
[root root]#cd /usr/local/srcIndex: openacs-4/packages/acs-core-docs/www/aolserver4.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/aolserver4.html,v diff -u -N -r1.17.2.7 -r1.17.2.8 --- openacs-4/packages/acs-core-docs/www/aolserver4.html 16 Jan 2006 18:59:43 -0000 1.17.2.7 +++ openacs-4/packages/acs-core-docs/www/aolserver4.html 17 Jan 2006 03:44:38 -0000 1.17.2.8 @@ -1,4 +1,4 @@ -Install AOLserver 4 +Install AOLserver 4
Check suitability of previously installed TCL.�Start tcl (type
tclshor find it usingwhich tclsh). @@ -94,16 +94,16 @@ maintainers: this should be moved to the next page and integrated into the text there)
Oracle
[root aolserver]#cd /usr/local/aolserver/bin-[root bin]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/nsd-oracle.txt ./nsd-oracle+[root bin]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/nsd-oracle.txt ./nsd-oracle[root bin]#chmod 750 nsd-oracle[root bin]# cd /usr/local/aolserver/bin -cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/nsd-oracle.txt ./nsd-oracle +cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/nsd-oracle.txt ./nsd-oracle chmod 750 nsd-oraclePostgreSQL
[root aolserver]#cd /usr/local/aolserver/bin-[root bin]#cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/nsd-postgres.txt ./nsd-postgres+[root bin]#cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/nsd-postgres.txt ./nsd-postgres[root bin]#chmod 755 nsd-postgres[root bin]# cd /usr/local/aolserver/bin -cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/nsd-postgres.txt ./nsd-postgres +cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/nsd-postgres.txt ./nsd-postgres chmod 755 nsd-postgresYou may need to edit these scripts if you are not using - /usr/local/aolserver as the directory of Aolserver4.
Change startup script (optional).�If you want to run AOLserver on a port below 1024 (normally, for a webserver you will use 80), you will have to change the
/var/lib/aolserver/service0/etc/daemontools/runscript according to the documentation found there (namely: Add the -b yourip:yourport switch)($Id$)View comments on this page at openacs.org + /usr/local/aolserver as the directory of Aolserver4.Change startup script (optional).�If you want to run AOLserver on a port below 1024 (normally, for a webserver you will use 80), you will have to change the
/var/lib/aolserver/service0/etc/daemontools/runscript according to the documentation found there (namely: Add the -b yourip:yourport switch)($Id$)View comments on this page at openacs.org Index: openacs-4/packages/acs-core-docs/www/complete-install.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/complete-install.html,v diff -u -N -r1.16.2.4 -r1.16.2.5 --- openacs-4/packages/acs-core-docs/www/complete-install.html 15 Dec 2005 19:27:47 -0000 1.16.2.4 +++ openacs-4/packages/acs-core-docs/www/complete-install.html 17 Jan 2006 03:44:38 -0000 1.16.2.5 @@ -1 +1 @@ -Chapter�3.�Complete Installation View comments on this page at openacs.org +Chapter�3.�Complete Installation View comments on this page at openacs.org Index: openacs-4/packages/acs-core-docs/www/filename.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/filename.html,v diff -u -N -r1.40.2.7 -r1.40.2.8 --- openacs-4/packages/acs-core-docs/www/filename.html 16 Jan 2006 18:59:43 -0000 1.40.2.7 +++ openacs-4/packages/acs-core-docs/www/filename.html 17 Jan 2006 03:44:38 -0000 1.40.2.8 @@ -114,7 +114,7 @@ within the OpenACS, this section's details are likely to shift from UI specifics to template interface specifics.- Under OpenACS 5.2.0, parameters are set at two levels: at the global level by + Under OpenACS 5.2.2, parameters are set at two levels: at the global level by the OpenACS-admin, and at the subsite level by a sub-admin. In this section, list and discuss both levels of parameters.
Index: openacs-4/packages/acs-core-docs/www/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/index.html,v diff -u -N -r1.44.2.6 -r1.44.2.7 --- openacs-4/packages/acs-core-docs/www/index.html 9 Jan 2006 01:28:53 -0000 1.44.2.6 +++ openacs-4/packages/acs-core-docs/www/index.html 17 Jan 2006 03:44:38 -0000 1.44.2.7 @@ -1,3 +1,3 @@ -
OpenACS Core Documentation Table of Contents
- I. OpenACS For Everyone
- II. Administrator's Guide
- 2. Installation Overview
- 3. Complete Installation
- 4. Configuring a new OpenACS Site
- 5. Upgrading
- 6. Production Environments
- Starting and Stopping an OpenACS instance.
- AOLserver keepalive with inittab
- Running multiple services on one machine
- High Availability/High Performance Configurations
- Staged Deployment for Production Networks
- Installing SSL Support for an OpenACS service
- Set up Log Analysis Reports
- External uptime validation
- Diagnosing Performance Problems
- 7. Database Management
- 8. Backup and Recovery
- A. Install Red Hat 8/9
- B. Install additional supporting software
- Unpack the OpenACS tarball
- Initialize CVS (OPTIONAL)
- Add PSGML commands to emacs init file (OPTIONAL)
- Install Daemontools (OPTIONAL)
- Install qmail (OPTIONAL)
- Install Analog web file analyzer
- Install nspam
- Install Full Text Search using Tsearch2
- Install Full Text Search using OpenFTS (deprecated see tsearch2)
- Install nsopenssl
- Install tclwebtest.
- Install PHP for use in AOLserver
- Install Squirrelmail for use as a webmail system for OpenACS
- Install PAM Radius for use as external authentication
- Install LDAP for use as external authentication
- Install AOLserver 3.3oacs1
- C. Credits
- III. For OpenACS Package Developers
- 9. Development Tutorial
- 10. Advanced Topics
- Write the Requirements and Design Specs
- Add the new package to CVS
- OpenACS Edit This Page Templates
- Adding Comments
- Admin Pages
- Categories
- Profile your code
- Prepare the package for distribution.
- Distributing upgrades of your package
- Notifications
- Hierarchical data
- Using .vuh files for pretty urls
- Laying out a page with CSS instead of tables
- Sending HTML email from your application
- Basic Caching
- Scheduled Procedures
- Enabling WYSIWYG
- Adding in parameters for your package
- Writing upgrade scripts
- Connect to a second database
- Future Topics
- 11. Development Reference
- OpenACS Packages
- OpenACS Data Models and the Object System
- The Request Processor
- The OpenACS Database Access API
- Using Templates in OpenACS
- Groups, Context, Permissions
- Writing OpenACS Application Pages
- Parties in OpenACS
- OpenACS Permissions Tediously Explained
- Object Identity
- Programming with AOLserver
- Using HTML Forms
- 12. Engineering Standards
- 14. +
OpenACS Core Documentation Table of Contents
- I. OpenACS For Everyone
- II. Administrator's Guide
- 2. Installation Overview
- 3. Complete Installation
- 4. Configuring a new OpenACS Site
- 5. Upgrading
- 6. Production Environments
- Starting and Stopping an OpenACS instance.
- AOLserver keepalive with inittab
- Running multiple services on one machine
- High Availability/High Performance Configurations
- Staged Deployment for Production Networks
- Installing SSL Support for an OpenACS service
- Set up Log Analysis Reports
- External uptime validation
- Diagnosing Performance Problems
- 7. Database Management
- 8. Backup and Recovery
- A. Install Red Hat 8/9
- B. Install additional supporting software
- Unpack the OpenACS tarball
- Initialize CVS (OPTIONAL)
- Add PSGML commands to emacs init file (OPTIONAL)
- Install Daemontools (OPTIONAL)
- Install qmail (OPTIONAL)
- Install Analog web file analyzer
- Install nspam
- Install Full Text Search using Tsearch2
- Install Full Text Search using OpenFTS (deprecated see tsearch2)
- Install nsopenssl
- Install tclwebtest.
- Install PHP for use in AOLserver
- Install Squirrelmail for use as a webmail system for OpenACS
- Install PAM Radius for use as external authentication
- Install LDAP for use as external authentication
- Install AOLserver 3.3oacs1
- C. Credits
- III. For OpenACS Package Developers
- 9. Development Tutorial
- 10. Advanced Topics
- Write the Requirements and Design Specs
- Add the new package to CVS
- OpenACS Edit This Page Templates
- Adding Comments
- Admin Pages
- Categories
- Profile your code
- Prepare the package for distribution.
- Distributing upgrades of your package
- Notifications
- Hierarchical data
- Using .vuh files for pretty urls
- Laying out a page with CSS instead of tables
- Sending HTML email from your application
- Basic Caching
- Scheduled Procedures
- Enabling WYSIWYG
- Adding in parameters for your package
- Writing upgrade scripts
- Connect to a second database
- Future Topics
- 11. Development Reference
- OpenACS Packages
- OpenACS Data Models and the Object System
- The Request Processor
- The OpenACS Database Access API
- Using Templates in OpenACS
- Groups, Context, Permissions
- Writing OpenACS Application Pages
- Parties in OpenACS
- OpenACS Permissions Tediously Explained
- Object Identity
- Programming with AOLserver
- Using HTML Forms
- 12. Engineering Standards
- 14. CVS Guidelines
- 15. Documentation Standards
- 16. Internationalization
- D. Using CVS with an OpenACS Site
- IV. For OpenACS Platform Developers
- 17. Kernel Documentation
- Overview
- Object Model Requirements
- Object Model Design
- Permissions Requirements
- Permissions Design
- Groups Requirements
- Groups Design
- Subsites Requirements
- Subsites Design Document
- Package Manager Requirements
- Package Manager Design
- Database Access API
- OpenACS Internationalization Requirements
- Security Requirements
- Security Design
- Security Notes
- Request Processor Requirements
- Request Processor Design
- Documenting Tcl Files: Page Contracts and Libraries
- Bootstrapping OpenACS
- External Authentication Requirements
- 18. Releasing OpenACS
- Index
List of Figures
- 4.1. Site Templates
- 4.2. Granting Permissions
- 4.3. Granting Permissions in 5.0
- 5.1. Upgrading with the APM
- 5.2. Upgrading a local CVS repository
- 6.1. Multiple-server configuration
- 6.2. Simple A/B Deployment - Step 1
- 6.3. Simple A/B Deployment - Step 2
- 6.4. Simple A/B Deployment - Step 3
- 6.5. Complex A/B Deployment - Step 1
- 6.6. Complex A/B Deployment - Step 2
- 6.7. Complex A/B Deployment - Step 3
- 6.8. Query Analysis example
- 8.1. Backup and Recovery Strategy
- 9.1. Assumptions in this section
- 9.2. Tutorial Data Model
- 9.3. The Database Creation Script
- 9.4. Database Deletion Script
- 9.5. Page Map
- 10.1. Upgrading a local CVS repository
- 11.1. Server file layout diagram
- 11.2. Package file layout diagram
List of Tables
List of Examples
View comments on this page at openacs.org Index: openacs-4/packages/acs-core-docs/www/individual-programs.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/individual-programs.html,v diff -u -N -r1.24.2.7 -r1.24.2.8 --- openacs-4/packages/acs-core-docs/www/individual-programs.html 16 Jan 2006 18:59:43 -0000 1.24.2.7 +++ openacs-4/packages/acs-core-docs/www/individual-programs.html 17 Jan 2006 03:44:38 -0000 1.24.2.8 @@ -9,7 +9,7 @@Table�2.2.�Version Compatibility Matrix
OpenACS Version 3.2.5 4.5 4.6 4.6.1 4.6.2 4.6.3 5.0 5.1 5.2 AOLserver 3 Yes No 3.3+ad13 Maybe Yes No 3.3oacs1 Maybe Yes No 3.4.2 No 3.4.2oacs1 Maybe Yes No 3.5.5 Maybe Yes No 4.0 Maybe Yes PostgreSQL 7.0 Yes No 7.2 Maybe Yes No 7.3.2 - 7.3.x No Yes 7.4 No Yes 8.0 No Maybe Yes Oracle 8.1.6 Maybe Yes 8.1.7 Maybe Yes 9i No Yes 10g � No Maybe The OpenACS installation instructions assume the operating system and build environment are installed. The instructions explain installation of TCL, tDOM, tclwebtest, a Web Server, a Database, a Process Controller, and Source Control software. The following external links are for reference only. -
OpenACS 5.2.0.�The OpenACS tarball comprises the core packages and +
OpenACS 5.2.2.�The OpenACS tarball comprises the core packages and many useful additional packages. This includes a full set of documentation. The tarball works with both PostgreSQL and Oracle. Some scripts require bash shell.
Operating System.�OpenACS is designed for a Unix-like system. It is @@ -41,7 +41,7 @@ distributions may not be thread safe.
TCL 8.4.x development headers and libraries, OPTIONAL.� The site-wide-search service, OpenFTS, requires these to compile. (Debian users:
apt-get install tcl8.4-dev). You need this - to install OpenFTS.tDOM, REQUIRED.�OpenACS 5.2.0 stores + to install OpenFTS.
tDOM, REQUIRED.�OpenACS 5.2.2 stores queries in XML files, so we use an AOLserver module called tDOM to parse these files. (This replaces libxml2, which was used prior to 4.6.4.)
tclwebtest, OPTIONAL.�tclwebtest is a tool for testing web interfaces via tcl scripts.
Web Server.�The web server handles incoming HTTP requests, provides @@ -50,7 +50,7 @@ errors. OpenACS uses AOLserver; some people have had success running Apache with mod_nsd.
AOLserver 4.x, REQUIRED.�Provides the base HTTP server
Mat Kovach is graciously maintaining an AOLserver distribution that - includes all the patches and modules needed to run OpenACS 5.2.0. These + includes all the patches and modules needed to run OpenACS 5.2.2. These instructions will describe how to install using his source distribution. He also has binaries for SuSE 7.3 and OpenBSD 2.8 (and perhaps more to come), currently located at uptime.openacs.org. Index: openacs-4/packages/acs-core-docs/www/install-daemontools.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-daemontools.html,v diff -u -N -r1.32.2.6 -r1.32.2.7 --- openacs-4/packages/acs-core-docs/www/install-daemontools.html 9 Jan 2006 01:28:53 -0000 1.32.2.6 +++ openacs-4/packages/acs-core-docs/www/install-daemontools.html 17 Jan 2006 03:44:38 -0000 1.32.2.7 @@ -79,7 +79,7 @@ root 13294 0.0 0.1 1352 272 ? S 09:51 0:00 svscan /service root 13295 0.0 0.0 1304 208 ? S 09:51 0:00 readproctitle service errors: ....................................... [root root]#
Install a script to grant non-root users permission to - control daemontools services.
[root root]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/svgroup.txt /usr/local/bin/svgroup+ control daemontools services.[root root]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/svgroup.txt /usr/local/bin/svgroup[root root]#chmod 755 /usr/local/bin/svgroup-cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/svgroup.txt /usr/local/bin/svgroup +cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/svgroup.txt /usr/local/bin/svgroup chmod 755 /usr/local/bin/svgroupView comments on this page at openacs.org Index: openacs-4/packages/acs-core-docs/www/install-next-add-server.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-next-add-server.html,v diff -u -N -r1.8.2.4 -r1.8.2.5 --- openacs-4/packages/acs-core-docs/www/install-next-add-server.html 15 Dec 2005 19:27:48 -0000 1.8.2.4 +++ openacs-4/packages/acs-core-docs/www/install-next-add-server.html 17 Jan 2006 03:44:38 -0000 1.8.2.5 @@ -1,5 +1,5 @@Running multiple services on one machine Services on different ports.�To run a different service on another port but the same - ip, simply repeat Install OpenACS 5.2.0 replacing + ip, simply repeat Install OpenACS 5.2.2 replacing $OPENACS_SERVICE_NAME, and change the
set httpport 8000 set httpsport 8443Index: openacs-4/packages/acs-core-docs/www/install-qmail.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-qmail.html,v diff -u -N -r1.32.2.6 -r1.32.2.7 --- openacs-4/packages/acs-core-docs/www/install-qmail.html 9 Jan 2006 01:28:53 -0000 1.32.2.6 +++ openacs-4/packages/acs-core-docs/www/install-qmail.html 17 Jan 2006 03:44:38 -0000 1.32.2.7 @@ -40,9 +40,9 @@ Unless this mail is addressed to the same machine, qmail thinks that it's an attempt to relay mail, and rejects it. So these two commands set up an exception so that any mail sent from 127.0.0.1 is allowed to -send outgoing mail.
[root ucspi-tcp-0.88]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/tcp.smtp.txt /etc/tcp.smtp+send outgoing mail.[root ucspi-tcp-0.88]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/tcp.smtp.txt /etc/tcp.smtp[root ucspi-tcp-0.88]#tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp-cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/tcp.smtp.txt /etc/tcp.smtp +cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/tcp.smtp.txt /etc/tcp.smtp tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtpDownload qmail, set up the standard supporting users and build the binaries:
[root root]#cd /usr/local/src[root src]#wget http://www.qmail.org/netqmail-1.04.tar.gz@@ -126,11 +126,11 @@ /var/qmail/bin/maildirmake ~alias/Maildir/ chown -R alias.nofiles /var/qmail/alias/MaildirConfigure qmail to use the Maildir delivery format (instead of mbox), and install a version of the qmail startup script modified to use Maildir.
[root alias]#echo "./Maildir" > /var/qmail/bin/.qmail-[root alias]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail.rc.txt /var/qmail/rc+[root alias]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail.rc.txt /var/qmail/rc[root alias]#chmod 755 /var/qmail/rc[root alias]# echo "./Maildir" > /var/qmail/bin/.qmail -cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail.rc.txt /var/qmail/rc +cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail.rc.txt /var/qmail/rc chmod 755 /var/qmail/rcSet up the skeleton directory so that new users will be configured for qmail.
[root root]#/var/qmail/bin/maildirmake /etc/skel/Maildir@@ -142,13 +142,13 @@ [root root]#mkdir -p /var/qmail/supervise/qmail-smtpd/log[root root]#mkdir /var/log/qmail[root root]#chown qmaill /var/log/qmail-[root root]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmailctl.txt /var/qmail/bin/qmailctl+[root root]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmailctl.txt /var/qmail/bin/qmailctl[root root]#chmod 755 /var/qmail/bin/qmailctl[root root]#ln -s /var/qmail/bin/qmailctl /usr/bin-[root root]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail-send-run.txt /var/qmail/supervise/qmail-send/run-[root root]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail-send-log-run.txt /var/qmail/supervise/qmail-send/log/run-[root root]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail-smtpd-run.txt /var/qmail/supervise/qmail-smtpd/run-[root root]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail-smtpd-log-run.txt /var/qmail/supervise/qmail-smtpd/log/run+[root root]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail-send-run.txt /var/qmail/supervise/qmail-send/run+[root root]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail-send-log-run.txt /var/qmail/supervise/qmail-send/log/run+[root root]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail-smtpd-run.txt /var/qmail/supervise/qmail-smtpd/run+[root root]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail-smtpd-log-run.txt /var/qmail/supervise/qmail-smtpd/log/run[root root]#chmod 755 /var/qmail/supervise/qmail-send/run[root root]#chmod 755 /var/qmail/supervise/qmail-send/log/run[root root]#chmod 755 /var/qmail/supervise/qmail-smtpd/run@@ -159,13 +159,13 @@ mkdir -p /var/qmail/supervise/qmail-smtpd/log mkdir /var/log/qmail chown qmaill /var/log/qmail -cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmailctl.txt /var/qmail/bin/qmailctl +cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmailctl.txt /var/qmail/bin/qmailctl chmod 755 /var/qmail/bin/qmailctl ln -s /var/qmail/bin/qmailctl /usr/bin -cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail-send-run.txt /var/qmail/supervise/qmail-send/run -cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail-send-log-run.txt /var/qmail/supervise/qmail-send/log/run -cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail-smtpd-run.txt /var/qmail/supervise/qmail-smtpd/run -cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/qmail-smtpd-log-run.txt /var/qmail/supervise/qmail-smtpd/log/run +cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail-send-run.txt /var/qmail/supervise/qmail-send/run +cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail-send-log-run.txt /var/qmail/supervise/qmail-send/log/run +cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail-smtpd-run.txt /var/qmail/supervise/qmail-smtpd/run +cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/qmail-smtpd-log-run.txt /var/qmail/supervise/qmail-smtpd/log/run chmod 755 /var/qmail/supervise/qmail-send/run chmod 755 /var/qmail/supervise/qmail-send/log/run chmod 755 /var/qmail/supervise/qmail-smtpd/run Index: openacs-4/packages/acs-core-docs/www/install-steps.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-steps.html,v diff -u -N -r1.26.2.7 -r1.26.2.8 --- openacs-4/packages/acs-core-docs/www/install-steps.html 16 Jan 2006 18:59:43 -0000 1.26.2.7 +++ openacs-4/packages/acs-core-docs/www/install-steps.html 17 Jan 2006 03:44:38 -0000 1.26.2.8 @@ -4,7 +4,7 @@ Install PostgreSQL).Install AOLserver (Install AOLserver 4) .
Create a unique database and system user. Install the OpenACS tarball, start and AOLserver instance, and use the OpenACS web pages to complete installation - (see Install OpenACS 5.2.0).
Specific instructions are available for Mac OS X and + (see Install OpenACS 5.2.2).
Specific instructions are available for Mac OS X and Windows2000 (see the section called “OpenACS Installation Guide for Mac OS X” or the section called “OpenACS Installation Guide for Windows2000”).
You can try out OpenACS using some binary installers. In general, they are not yet supported by the community, so they are @@ -43,7 +43,7 @@ createdb $OPENACS_SERVICE_NAME
Setting a global shell variable for cut and paste.�In order to cut and paste the instructions into your shell, you must set the environment variable $OPENACS_SERVICE_NAME. In order to set it globally so that it works for any new users or special service users you may create, edit the file
/etc/profile(/etc/share/skel/dot.profilefor FreeBSD) and add this line:export OPENACS_SERVICE_NAME=service0Table�2.1.�Default directories for a standard install
+ files are located at:
/var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files Database backup directory /var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup Service config files /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc Service log files /var/lib/aolserver/$OPENACS_SERVICE_NAME/log Compile directory /usr/local/src PostgreSQL directory /usr/local/pgsql AOLserver directory /usr/local/aolserver None of these locations are set in stone - they're simply the values that we've chosen. The values that you'll probably want to change, such as service name, are Index: openacs-4/packages/acs-core-docs/www/object-identity.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/object-identity.html,v diff -u -N -r1.40.2.7 -r1.40.2.8 --- openacs-4/packages/acs-core-docs/www/object-identity.html 16 Jan 2006 18:59:43 -0000 1.40.2.7 +++ openacs-4/packages/acs-core-docs/www/object-identity.html 17 Jan 2006 03:44:39 -0000 1.40.2.8 @@ -1,18 +1,18 @@
Object Identity One of the major design features of OpenACS 5.2.2 is the explicit representation of object identity. The reason I say "explicit representation" is because the concept of object identity has been around forever. It is inherent to our problem domain. Consider the example of 3.x style scoping. The 3.x data models use the triple (user_id, group_id, -scope) to identify an object. In the 5.2.0 data model this +scope) to identify an object. In the 5.2.2 data model this object is explicitly represented by a single party_id.
Another good example of this is can be found in the user groups data model. The 3.x user groups data model contains another example of an implied identity. Every mapping between a user and a group could have an arbitrary number of attached values (user_group_member_fields, etc.). In this case it is the pair (group_id, user_id) that implicitly refers to an -object (the person's membership in a group). In the 5.2.0 data model this +object (the person's membership in a group). In the 5.2.2 data model this object identity is made explicit by adding an integer primary key to the table that maps users to groups.
Coming from a purely relational world, this might seem slightly weird at first. The pair (group_id, user_id) is sufficient to uniquely identify the Index: openacs-4/packages/acs-core-docs/www/objects.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/objects.html,v diff -u -N -r1.43.2.7 -r1.43.2.8 --- openacs-4/packages/acs-core-docs/www/objects.html 16 Jan 2006 18:59:43 -0000 1.43.2.7 +++ openacs-4/packages/acs-core-docs/www/objects.html 17 Jan 2006 03:44:39 -0000 1.43.2.8 @@ -2,7 +2,7 @@ OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.
-Developing data models in OpenACS 5.2.0 is much like developing data models +Developing data models in OpenACS 5.2.2 is much like developing data models for OpenACS 3, save for the implementation. As usual, you need to examine how to model the information that the application must store and manipulate, and define a suitable set of SQL tables. In our Notes @@ -314,7 +314,7 @@ models that are meant to be integrated with the OpenACS object system.
-There are two basic rules you should follow when designing OpenACS 5.2.0 data +There are two basic rules you should follow when designing OpenACS 5.2.2 data models: @@ -369,7 +369,7 @@ requires a good amount of thought at design time even for simple applications.
-Hooking into the OpenACS 5.2.0 object system brings the application developer +Hooking into the OpenACS 5.2.2 object system brings the application developer numerous benefits, and doing it involves only four easy steps: Index: openacs-4/packages/acs-core-docs/www/openacs-unpack.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/openacs-unpack.html,v diff -u -N -r1.20.2.4 -r1.20.2.5 --- openacs-4/packages/acs-core-docs/www/openacs-unpack.html 15 Dec 2005 19:27:48 -0000 1.20.2.4 +++ openacs-4/packages/acs-core-docs/www/openacs-unpack.html 17 Jan 2006 03:44:39 -0000 1.20.2.5 @@ -1,17 +1,17 @@
Unpack the OpenACS tarball The OpenACS tarball contains sample configuration files for some of the packages listed below. In order to access those files, unpack the tarball now.
[root root]#cd /tmp-[root tmp]#tar xzf openacs-5.2.0.tgz+[root tmp]#tar xzf openacs-5.2.2.tgzcd /tmp -tar xzf openacs-5.2.0.tgzIf you are installing from a different method and just need the configuration files, you can instead get them from CVS:
[root root]#cd /tmp+tar xzf openacs-5.2.2.tgzIf you are installing from a different method and just need the configuration files, you can instead get them from CVS:
[root root]#cd /tmp[root tmp]#cvs -d :pserver:anonymous@cvs.openacs.org:/cvsroot co openacs-4/packages/acs-core-docs/www/files/cvs checkout: warning: failed to open /root/.cvspass for reading: No such file or directory cvs server: Updating openacs-4/packages/acs-core-docs/www/files U openacs-4/packages/acs-core-docs/www/files/README.TXT (many lines omitted) U openacs-4/packages/acs-core-docs/www/files/template-ini.ini U openacs-4/packages/acs-core-docs/www/files/winnsd.txt -[root tmp]#mv openacs-4 openacs-5.2.0+[root tmp]#mv openacs-4 openacs-5.2.2cd /tmp cvs -d :pserver:anonymous@cvs.openacs.org:/cvsroot co openacs-4/packages/acs-core-docs/www/files/ mv openacs-4 openacs-5.0.0a4View comments on this page at openacs.org 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 -N -r1.42.2.7 -r1.42.2.8 --- openacs-4/packages/acs-core-docs/www/openacs.html 16 Jan 2006 18:59:43 -0000 1.42.2.7 +++ openacs-4/packages/acs-core-docs/www/openacs.html 17 Jan 2006 03:44:39 -0000 1.42.2.8 @@ -1,4 +1,4 @@ -Install OpenACS 5.2.0 by Vinod Kurup
+Install OpenACS 5.2.2 @@ -86,8 +86,8 @@
/var/tmpand proceed:
Unpack the OpenACS tarball and rename it to
$OPENACS_SERVICE_NAME. Secure the directory so that only the owner can access it. Check the permissions by listing the directory.FreeBSD note: Change the period in
chown -R $OPENACS_SERVICE_NAME.$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAMEto a colon:chown -R $OPENACS_SERVICE_NAME:$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME[root root]#su - $OPENACS_SERVICE_NAME[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$cd /var/lib/aolserver-[$OPENACS_SERVICE_NAME aolserver]$tar xzf /var/tmp/openacs-5.2.0.tgz-[$OPENACS_SERVICE_NAME aolserver]$mv openacs-5.2.0 $OPENACS_SERVICE_NAME+[$OPENACS_SERVICE_NAME aolserver]$tar xzf /var/tmp/openacs-5.2.2.tgz+[$OPENACS_SERVICE_NAME aolserver]$mv openacs-5.2.2 $OPENACS_SERVICE_NAME[$OPENACS_SERVICE_NAME aolserver]$chmod -R 775 $OPENACS_SERVICE_NAME[$OPENACS_SERVICE_NAME aolserver]$chown -R $OPENACS_SERVICE_NAME.$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME[$OPENACS_SERVICE_NAME aolserver]$ls -al@@ -100,8 +100,8 @@ [root root]# su - $OPENACS_SERVICE_NAME cd /var/lib/aolserver -tar xzf /var/tmp/openacs-5.2.0.tgz -mv openacs-5.2.0 $OPENACS_SERVICE_NAME +tar xzf /var/tmp/openacs-5.2.2.tgz +mv openacs-5.2.2 $OPENACS_SERVICE_NAME chmod -R 755 $OPENACS_SERVICE_NAME chown -R $OPENACS_SERVICE_NAME.$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME exitAdd the Service to CVS (OPTIONAL)
Prepare the database
Prepare Oracle for OpenACS.�If you won't be using Oracle, skip to Prepare PostgreSQL for an OpenACS Service
@@ -311,7 +311,7 @@ AOLserver keepalive (OPTIONAL)
Configure a Service with the OpenACS Installer.� Now that you've got AOLserver up and running, let's install OpenACS - 5.2.0. + 5.2.2.
You should see a page from the webserver titled
OpenACS Installation: @@ -367,8 +367,8 @@ 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 - 5.2.0 is now up and running! -If you want to track fresh code developments inbetween releases, or you are an OpenACS core developer, you may want to install from CVS. This is identical to Option 2 except that you get the files from CVS instead of the tarball: CVS Checkout Instructions. So, instead of
,tar xzf /var/tmp/openacs-5.2.0.tgz.cvs -z3 -d :pserver:anonymous@openacs.org:/cvsroot co acs-core
Use daemontools
superviseandsvc, orinittab, to automate server startup and shutdown.Install Full Text Search (OPTIONAL). If you have installed OpenFTS and enabled + 5.2.2 is now up and running! +
If you want to track fresh code developments inbetween releases, or you are an OpenACS core developer, you may want to install from CVS. This is identical to Option 2 except that you get the files from CVS instead of the tarball: CVS Checkout Instructions. So, instead of
,tar xzf /var/tmp/openacs-5.2.2.tgz.cvs -z3 -d :pserver:anonymous@openacs.org:/cvsroot co acs-core
Use daemontools
superviseandsvc, orinittab, to automate server startup and shutdown.Install Full Text Search (OPTIONAL). If you have installed OpenFTS and enabled OpenFTS, you can now install the OpenFTS Driver package and Full Text Search Engine package in the OpenACS service.
This is a good time to make a backup of your service. If this is a production site, you should set up automatic nightly backups.
If you want traffic reports, set up analog or another log Index: openacs-4/packages/acs-core-docs/www/oracle.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/oracle.html,v diff -u -N -r1.40.2.7 -r1.40.2.8 --- openacs-4/packages/acs-core-docs/www/oracle.html 16 Jan 2006 18:59:43 -0000 1.40.2.7 +++ openacs-4/packages/acs-core-docs/www/oracle.html 17 Jan 2006 03:44:39 -0000 1.40.2.8 @@ -4,7 +4,7 @@
If you are installing PostGreSQL instead of Oracle, skip this section.
- OpenACS 5.2.0 will install with Oracle 9i but has not been extensively tested so may still have bugs or tuning issues. See Andrew Piskorski's Oracle 9i notes for guidance. + OpenACS 5.2.2 will install with Oracle 9i but has not been extensively tested so may still have bugs or tuning issues. See Andrew Piskorski's Oracle 9i notes for guidance.
This installation guide attempts to present all of the information necessary to complete an OpenACS installation. We try hard to make all of the steps possible in one pass, rather than having a step which amounts to "go away and develop a profound understanding of software X and then come back and, in 99% of all cases, type these two lines." The exception to our rule is Oracle production systems. This page describes a set of steps to get a working Oracle development server, but it is unsuitable for production systems. If you will be using OpenACS on Oracle in a production environment, you will experience many problems unless you develop a basic understanding of Oracle which is outside the scope of this document. T
Index: openacs-4/packages/acs-core-docs/www/permissions.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/permissions.html,v diff -u -N -r1.40.2.7 -r1.40.2.8 --- openacs-4/packages/acs-core-docs/www/permissions.html 16 Jan 2006 18:59:43 -0000 1.40.2.7 +++ openacs-4/packages/acs-core-docs/www/permissions.html 17 Jan 2006 03:44:39 -0000 1.40.2.8 @@ -2,7 +2,7 @@ OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.
-The OpenACS 5.2.0 Permissions system allows developers and administrators to +The OpenACS 5.2.2 Permissions system allows developers and administrators to set access control policies at the object level, that is, any application or system object represented by a row in the
acs_objectstable can be access-controlled via a simple @@ -13,7 +13,7 @@ Although this may all sound easy and wonderful, no developer or administrator would want to explicitly set access control rights for every user and every object on a -site. Therefore, OpenACS 5.2.0 has two auxiliary mechanisms for making this +site. Therefore, OpenACS 5.2.2 has two auxiliary mechanisms for making this easier: First, the Groups system allows users to be grouped together in flexible ways. Second, the object model defines a notion of object context, which allows applications to group objects @@ -25,7 +25,7 @@ define simple groupings of users. Each group had a human readable name and unique ID, and there was a single mapping table that mapped users to groups. (The actual data model was more complicated because it -contained a meta-data system much like the OpenACS 5.2.0 object type system, +contained a meta-data system much like the OpenACS 5.2.2 object type system, but that's not relevant right now.)The 3.x groups system, while very useful, was limited in few ways. The @@ -47,7 +47,7 @@ member of Greenpeace, its members are not necessarily members of Greenpeace.
-OpenACS 5.2.0 solves both of these modeling problems by introducing a new +OpenACS 5.2.2 solves both of these modeling problems by introducing a new abstraction called a party. Parties have a recursive definition, and we can illustrate how it works with the following simplified data model. First, we define the
parties@@ -113,18 +113,18 @@ already know what parties and objects are, but we don't know what privileges are.-In OpenACS 5.2.0, a privilege models the right to perform some operation on +In OpenACS 5.2.2, a privilege models the right to perform some operation on some object. They are the basic units out of which we build access control policies. For example, in the Unix filesystem we typically implement access control by granting users some combination of -read. write or execute privileges on files and directories. In OpenACS 5.2.0, +read. write or execute privileges on files and directories. In OpenACS 5.2.2, the table of privileges is organized hierarchically so that developers can define privileges that aggregate some set of privileges together. For example, if we have read, write, create and delete privileges, it might be convenient to combine them into a new privilege called "admin". Then if we grant a user this privilege she is automatically granted all the child privileges that the privilege -contains. The OpenACS 5.2.0 kernel data model actually defines these +contains. The OpenACS 5.2.2 kernel data model actually defines these privileges as follows:
@@ -164,7 +164,7 @@ permissions to large groups of objects in the site, all at once. We use contexts to achieve this goal.-In OpenACS 5.2.0, an object context is a generalization of the scoping +In OpenACS 5.2.2, an object context is a generalization of the scoping mechanism introduced in OpenACS 3.x. "Scoping" and "scope" are terms best explained by example: consider some hypothetical rows in the
address_booktable: @@ -179,7 +179,7 @@ person or a group of people or the general public (itself a group of people).-In OpenACS 5.2.0, rather than breaking the world into a limited set of scopes, +In OpenACS 5.2.2, rather than breaking the world into a limited set of scopes, every object lives in a single context. A context is just an another object that represents the security domain to which the object belongs. By convention, if an object A doesn't have any permissions @@ -196,7 +196,7 @@ application. With only row-level permissions it is not obvious how to reasonably initialize the access control list when creating a message. At best, we have to explicitly grant various read and write -privileges whenever we create a message, which is tedious. In OpenACS 5.2.0, +privileges whenever we create a message, which is tedious. In OpenACS 5.2.2, a reasonable thing to do is to create an object representing a forum, and point the
context_idfield of a new message at the forum. Then, suppose we grant every user in the system read-access to @@ -329,7 +329,7 @@This displays the title of the note as either a link or plain text depending on whether or not we have write privileges on the object. -The
iftag is something that the OpenACS 5.2.0 template system +Theiftag is something that the OpenACS 5.2.2 template system defines for you to support conditional presentation. The templates developer guide provides more information about this.If you study the rest of the system, you will also notice that the @@ -343,7 +343,7 @@ permissions to notes that she wanted to make public or whatever. But that's beyond the scope of this example.
-OpenACS 5.2.0 defines three separate mechanisms for specifying access control +OpenACS 5.2.2 defines three separate mechanisms for specifying access control in applications. The Groups data model allows you to define hierarchical organizations of users and groups of users. The Permissions data model allows you to define a hierarchy of user rights. Finally, Index: openacs-4/packages/acs-core-docs/www/postgres.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/postgres.html,v diff -u -N -r1.41.2.7 -r1.41.2.8 --- openacs-4/packages/acs-core-docs/www/postgres.html 16 Jan 2006 18:59:43 -0000 1.41.2.7 +++ openacs-4/packages/acs-core-docs/www/postgres.html 17 Jan 2006 03:44:39 -0000 1.41.2.8 @@ -1,7 +1,7 @@
Install PostgreSQL Skip this section if you will run only Oracle.
OpenACS 5.2.0 will run with PostgreSQL 7.3.2, 7.3.3, and 7.3.4 and 7.4.x. 7.4.7 is the recommended version of PostgreSQL.
Skip this section if you will run only Oracle.
OpenACS 5.2.2 will run with PostgreSQL 7.3.2, 7.3.3, and 7.3.4 and 7.4.x. 7.4.7 is the recommended version of PostgreSQL.
Special notes for Mac OS X.�If you are running Mac OS X prior to 10.3, you should be able to install and use PostGreSQL 7.3.x. Mac OS X 10.3 requires PostGreSQL 7.4.
Debian stable user should install PostGreSQL from source as detailed below, or they should use the www.backports.org backport for Postgres to get a more current version. Debian unstable users: the following process has been known to work @@ -212,11 +212,11 @@ state. Red Hat and Debian and SuSE each work a little differently. If you haven't untarred the OpenACS tarball, you will need to do so now to access the postgresql.txt file.
Red Hat RPM:
The init script is already installed; just turn it on for the appropriate run levels.
[root root]#chkconfig --level 345 postgresql on-[root root]#Red Hat from source:
[root src]#cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/postgresql.txt /etc/init.d/postgresql+[root root]#Red Hat from source:
[root src]#cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/postgresql.txt /etc/init.d/postgresql[root src]#chown root.root /etc/rc.d/init.d/postgresql[root src]#chmod 755 /etc/rc.d/init.d/postgresql[root src]# -cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/postgresql.txt /etc/init.d/postgresql +cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/postgresql.txt /etc/init.d/postgresql chown root.root /etc/rc.d/init.d/postgresql chmod 755 /etc/rc.d/init.d/postgresqlTest the script.
[root root]#service postgresql stopStopping PostgreSQL: ok @@ -239,7 +239,7 @@ [root ~]#chown root.root /etc/init.d/postgresql[root ~]#chmod 755 /etc/init.d/postgresql[root ~]# -cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/postgresql.txt /etc/init.d/postgresql +cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/postgresql.txt /etc/init.d/postgresql chown root.root /etc/init.d/postgresql chmod 755 /etc/init.d/postgresqlTest the script
[root ~]#/etc/init.d/postgresql stopStopping PostgreSQL: ok @@ -257,11 +257,11 @@ /etc/rc5.d/S20postgresql -> ../init.d/postgresql [root ~]#/etc/init.d/postgresql startStarting PostgreSQL: ok -[root ~]#FreeBSD:
[root ~]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/postgresql.txt /usr/local/etc/rc.d/postgresql.sh+[root ~]#FreeBSD:
[root ~]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/postgresql.txt /usr/local/etc/rc.d/postgresql.sh[root ~]#chown root:wheel /usr/local/etc/rc.d/postgresql.sh[root ~]#chmod 755 /usr/local/etc/rc.d/postgresql.sh[root ~]# -cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/postgresql.txt /usr/local/etc/rc.d/postgresql.sh +cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/postgresql.txt /usr/local/etc/rc.d/postgresql.sh chown root:wheel /usr/local/etc/rc.d/postgresql.sh chmod 755 /usr/local/etc/rc.d/postgresql.shTest the script
[root ~]#/usr/local/etc/rc.d/postgresql.sh stopStopping PostgreSQL: ok @@ -279,7 +279,7 @@rc.d/part in each of the following commands. -[root ~]#cp /var/tmp/openacs-5.2.0/packages/acs-core-docs/www/files/postgresql.txt /etc/rc.d/init.d/postgresql+[root ~]#cp /var/tmp/openacs-5.2.2/packages/acs-core-docs/www/files/postgresql.txt /etc/rc.d/init.d/postgresql[root ~]#chown root.root /etc/rc.d/init.d/postgresql[root ~]#chmod 755 /etc/rc.d/init.d/postgresqlIndex: openacs-4/packages/acs-core-docs/www/psgml-for-emacs.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/psgml-for-emacs.html,v diff -u -N -r1.32.2.6 -r1.32.2.7 --- openacs-4/packages/acs-core-docs/www/psgml-for-emacs.html 9 Jan 2006 01:28:53 -0000 1.32.2.6 +++ openacs-4/packages/acs-core-docs/www/psgml-for-emacs.html 17 Jan 2006 03:44:39 -0000 1.32.2.7 @@ -3,6 +3,6 @@ customized emacs configuration file with DocBook commands in the skeleton directory, so it will be used for all new users. The file also fixes the backspace -> help mis-mapping that often occurs in - terminals.
[root tmp]#cp /tmp/openacs-5.2.0/packages/acs-core-docs/www/files/emacs.txt /etc/skel/.emacs+ terminals.[root tmp]#cp /tmp/openacs-5.2.2/packages/acs-core-docs/www/files/emacs.txt /etc/skel/.emacscp: overwrite `/etc/skel/.emacs'?y[root tmp]#Debian users:
apt-get install psgmlNote: The new nxml mode for emacs, when used in combination with psgml, provides a pretty good set of functionality that makes DocBook editing much less painless. In particular, nxml does syntax testing in real-time so that you can see syntax errors immediately instead of in the output of the xsltproc hours or days later. For debian,
apt-get install nxml.View comments on this page at openacs.org Index: openacs-4/packages/acs-core-docs/www/release-notes.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/release-notes.html,v diff -u -N -r1.46.2.7 -r1.46.2.8 --- openacs-4/packages/acs-core-docs/www/release-notes.html 16 Jan 2006 18:59:44 -0000 1.46.2.7 +++ openacs-4/packages/acs-core-docs/www/release-notes.html 17 Jan 2006 03:44:39 -0000 1.46.2.8 @@ -23,7 +23,7 @@You may want to begin by reading our installation documentation for the section called “a Unix-like system”. Note that the Windows documentation is - not current for OpenACS 5.2.0, but an alternative is to use John + not current for OpenACS 5.2.2, but an alternative is to use John Sequeira's Oasis VM project.
Index: openacs-4/packages/acs-core-docs/www/request-processor.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/request-processor.html,v diff -u -N -r1.40.2.7 -r1.40.2.8 --- openacs-4/packages/acs-core-docs/www/request-processor.html 16 Jan 2006 18:59:44 -0000 1.40.2.7 +++ openacs-4/packages/acs-core-docs/www/request-processor.html 17 Jan 2006 03:44:39 -0000 1.40.2.8 @@ -2,11 +2,11 @@ OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.
-This document is a brief introduction to the OpenACS 5.2.0 Request Processor; +This document is a brief introduction to the OpenACS 5.2.2 Request Processor; more details can be found in the OpenACS 4 Request Processor Design. Here we cover the high level concepts behind the system, and implications and usage for the application developer.
-The 5.2.0 Request Processor is a global filter and set of Tcl procs that +The 5.2.2 Request Processor is a global filter and set of Tcl procs that respond to every incoming URL reaching the server. The following diagram summarizes the stages of the request processor assuming a URL request like
http://someserver.com/notes/somepage.adp. @@ -35,7 +35,7 @@ extracts or sets up new session tokens for the user.Stage 3: Authorization Next, the Request Processor checks if the user has appropriate access -privileges to the requested part of the site. In OpenACS 5.2.0, access control +privileges to the requested part of the site. In OpenACS 5.2.2, access control is dictated by the permissions system. In this case, the RP checks if the user has "read" priviledges on the object in the site map specified by the URL. This object is typically Index: openacs-4/packages/acs-core-docs/www/subsites.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/subsites.html,v diff -u -N -r1.40.2.7 -r1.40.2.8 --- openacs-4/packages/acs-core-docs/www/subsites.html 16 Jan 2006 18:59:44 -0000 1.40.2.7 +++ openacs-4/packages/acs-core-docs/www/subsites.html 17 Jan 2006 03:44:39 -0000 1.40.2.8 @@ -253,15 +253,15 @@ visible to that user. The end result is a site where users can come and write notes to themselves.
-This is a good example of the leverage available in the OpenACS 5.2.0 +This is a good example of the leverage available in the OpenACS 5.2.2 system. The code that we have written for Notes is not at all more complex than a similar application without access control or site map awareness. By adding a small amount of code, we have taken a small, simple, and special purpose application to something that has the potential to be a very useful, general-purpose tool, complete with multi-user features, access control, and centralized administration.
-In OpenACS 5.2.0, application pages and scripts can be aware of the package +In OpenACS 5.2.2, application pages and scripts can be aware of the package instance, or subsite in which they are executing. This is a powerful general purpose mechanism that can be used to structure web services in very flexible ways. Index: openacs-4/packages/acs-core-docs/www/tutorial-newpackage.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-newpackage.html,v diff -u -N -r1.35.2.6 -r1.35.2.7 --- openacs-4/packages/acs-core-docs/www/tutorial-newpackage.html 9 Jan 2006 01:28:54 -0000 1.35.2.6 +++ openacs-4/packages/acs-core-docs/www/tutorial-newpackage.html 17 Jan 2006 03:44:39 -0000 1.35.2.7 @@ -20,7 +20,7 @@
You will need:
A computer with a working installation of OpenACS. If you don't have this, see Chapter�2, Installation Overview.
Example files, which are included in the -standard OpenACS 5.2.0 distribution. +standard OpenACS 5.2.2 distribution.
We use the ACS Package Manager (APM) to add, remove, and upgrade packages. It handles package meta-data, such as lists of files that belong in the package. Each package is uniquely 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 -N -r1.18.2.6 -r1.18.2.7 --- openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html 9 Jan 2006 01:28:54 -0000 1.18.2.6 +++ openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html 17 Jan 2006 03:44:39 -0000 1.18.2.7 @@ -8,4 +8,4 @@
upgrade, plus any new packages you want. It's safest to upgrade the kernel by itself, and then come back and upgrade the rest of the - desired packages in a second pass.On the next screen, click
When prompted, restart the server:
[root root]#restart-aolserver $OPENACS_SERVICE_NAMEWait a minute, then browse to the package manager,
http://yourserver/acs-admin/apm.Check that the kernel upgrade worked by clicking
Alland making sure thatacs-kernelversion is 5.2.0.Rollback.�If anything goes wrong, roll back to the backup snapshot.
View comments on this page at openacs.org + desired packages in a second pass.On the next screen, click
When prompted, restart the server:
[root root]#restart-aolserver $OPENACS_SERVICE_NAMEWait a minute, then browse to the package manager,
http://yourserver/acs-admin/apm.Check that the kernel upgrade worked by clicking
Alland making sure thatacs-kernelversion is 5.2.2.
Rollback.�If anything goes wrong, roll back to the backup snapshot.
by Matthew Burke and Curtis Galloway
+NOTE: These instructions were valid for ACS v4, but have not been tested with OpenACS and the ArsDigita binary distributions are no longer available. Currently - (10/2003), the best option to get OpenACS 5.2.0 running on Windows + (10/2003), the best option to get OpenACS 5.2.2 running on Windows is to use VMware and John Sequeira's Oasis VM distribution @@ -249,4 +249,4 @@
In the services control panel you should see two services:
AOLserver-lintcollectors and
AOLserver-iguanasdirect.
-