Install OpenACS 5.0.0b1

+Install OpenACS 5.0.0b4

Prev	Chapter�3.�Complete Installation	Next

Install OpenACS 5.0.0b4

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, @@ -10,9 +10,9 @@ [root@yourserver root]# chgrp web /var/lib/aolserver [root@yourserver root]# chmod 770 /var/lib/aolserver [root@yourserver root]# -

mkdir /var/lib/aolserver
+mkdir /var/lib/aolserver
 chgrp web /var/lib/aolserver
-chmod 770 /var/lib/aolserver

Set up a user account for each site.

+chmod 770 /var/lib/aolserver

Set up a user account for each site.

AOLserver needs to be started as the root user if you want to use port 80. Once it starts, though, it will drop the root privileges and run as another user, which you must specify on the command line. It's @@ -71,8 +71,8 @@ tarball and save it in /tmp and proceed:

Unpack the OpenACS tarball and rename it to service0. Secure the directory so that only the owner can access it. Check the permissions by listing the directory.

[root@yourserver root]# su - service0
 [service0@yourserver service0]$ cd /var/lib/aolserver
-[service0@yourserver aolserver]$ tar xzf /tmp/openacs-5.0.0b1.tgz
-[service0@yourserver aolserver]$ mv openacs-5.0.0b1 service0
+[service0@yourserver aolserver]$ tar xzf /tmp/openacs-5.0.0b4.tgz
+[service0@yourserver aolserver]$ mv openacs-5.0.0b4 service0
 [service0@yourserver aolserver]$ chmod -R 700 service0
 [service0@yourserver aolserver]$ ls -al
 total 3
@@ -83,12 +83,12 @@
 logout
 
 [root@yourserver root]#
-su - service0
+su - service0
 cd /var/lib/aolserver
-tar xzf /tmp/openacs-5.0.0b1.tgz
-mv openacs-5.0.0b1 service0
+tar xzf /tmp/openacs-5.0.0b4.tgz
+mv openacs-5.0.0b4 service0
 chmod -R 700 service0/
-exit

Add 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
  +exit
- Add 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
    You should be sure that your user account (e.g. service0) is in the dba group. @@ -222,8 +222,8 @@ If you can't login, try redoing step 1 again. If the date is 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, 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
+		  
```

Prepare PostgreSQL for an OpenACS Service.�

PostgreSQL:
Create a user in the database matching the service + 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
@@ -233,9 +233,9 @@
 [service0@yourserver service0]$ createdb -E UNICODE service0
 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. 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
+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. 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.�

@@ -245,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
 

@@ -266,19 +266,19 @@
 		  servername - This is just a *pretty* name for your server.

user_account - The account that will both own OpenACS files and connect to the database (for Postgresql).
debug - Set to true for a very verbose error log, including many lines for every page view, success or failure.

- AOLServer is very configurable. These settings should get you - started, but for more options, read the AOLServer + AOLserver is very configurable. These settings should get you + started, but for more options, read the AOLserver docs.

Enable OpenFTS Full Text Search (OPTIONAL)

Install nsopenssl for SSL support. (OPTIONAL)

Verify AOLserver startup.�

Kill any current running AOLserver processes and start a new one. If you are using Oracle, rather than PostgreSQL, replace nsd-postgres with nsd-oracle).
If you want to use port 80, there are complications. - First, Aolserver must be root to use system ports such as + First, AOLserver must be root to use system ports such as 80, but refuses to run as root for security reasons. Thus you must start as root and specify a non-root user ID and - Group ID which Aolserver will switch to after claiming the + Group ID which AOLserver will switch to after claiming the port. To do so, find the UID and GID of the service0 user via grep service0 @@ -292,7 +292,7 @@ [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.
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 + 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.
@@ -306,11 +306,11 @@ permissions errors or missing files. If you need to make changes, don't forget to kill any running servers with killall nsd. -
Automate +
Automate AOLserver keepalive (OPTIONAL)

Configure a Service with the OpenACS Installer.� Now that you've got AOLserver up and running, let's install OpenACS - 5.0.0b1. + 5.0.0b4. You should see a page from the webserver titled OpenACS Installation: @@ -360,16 +360,16 @@ You'll see the final Installer page, "OpenACS Installation: Complete." It will tell you that the server is being restarted; note that unless you already set up a way for - AOLServer to restart itself (ie. inittab or daemontools), + 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 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.0.0b1 is now up and running! + 5.0.0b4 is now up and running!

`Next Steps`

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 + 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 processing program.
Follow the instruction on the home page to change the appearance of your service or add more @@ -379,7 +379,7 @@ directly affect the service's run-time connection with the database, because those environmental variables are set by the wrapper scripts nsd-postgres and nsd-oracle.
```
[root@yourserver root]# su - service0
-[service0@yourserver service0]$ emacs .bashrc
```
Put in the appropriate lines for the database you are running. If you will use both databases, put in both sets of lines.
- PostGreSQL:
```
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/pgsql/lib
+[service0@yourserver service0]$ emacs .bashrc
```
  Put in the appropriate lines for the database you are running. If you will use both databases, put in both sets of lines.
  - PostgreSQL:
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/pgsql/lib export PATH=$PATH:/usr/local/pgsql/bin
  - Oracle. These environment variables are specific for a local Oracle installation communicating via IPC. If you are connecting to a remote Oracle installation, you'll need to adjust these appropriately. Also, @@ -395,7 +395,7 @@ logout [root@yourserver src]# su - service0 [postgres@yourserver pgsql]$ env | grep PATH -
    For PostGreSQL, you should see:
    +
    For PostgreSQL, you should see:
    LD_LIBRARY_PATH=LD_LIBRARY_PATH=:/usr/local/pgsql/lib PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin/X11:/usr/X11R6/bin:/root/bin:/usr/local/pgsql/bin:/usr/local/pgsql/bin
    For Oracle:
    ORACLE_BASE=/ora8/m01/app/oracle ORACLE_HOME=/ora8/m01/app/oracle/product/8.1.7