| Prev | Chapter 2. Installing on Unix/Linux | Next |
|---|
+
- According to Philip Greenspun: -
- “The ArsDigita Community System (ACS) is a toolkit of software - that will help you build Web services with a collaborative dimension, - ranging from knowledge management within companies to B2C ecommerce - to product support and community among the customers. The software is - free and open-source and has been tested in heavy use since - 1995.” -
- What's OpenACS? OpenACS was born when Don Baccus, Ben Adida, - et al decided to port ACS from Oracle to PostgreSQL, thus making it a fully open-source solution.
- OpenACS 4.6 is the next generation of the web toolkit. It's based on - ACS 4, but no longer follows ArsDigita development. Unlike both ACS - (which required Oracle) and OpenACS 3.x (which required PostgreSQL), - OpenACS 4.6 allows you to use either database. It's also built in such - a way to allow enterprising hackers (in the good sense of - the word) to extend it to other databases. Don Baccus leads - the development and numerous developers (and non-developers) - contribute from around the world. -
- This document will describe how to install an operating - system, OpenACS 4.6, and all supporting software, from - scratch. -
+ + This document will describe how to install, configure, and + maintain an installation of OpenACS 5.0.0 on a Unix-like + system, including all supporting software. All examples + in this chapter are part of the OpenACS 5.0.0-P or + OpenACS 5.0.0-O Reference Platform, which use Red + Hat 8.0. Differences between the Reference Platform + and common alternate platforms are noted where known. +
You will need a PC (or equivalent) with at least these minimum requirements:
Pentium processor
128 MB RAM - (much more if you want Oracle)
4 GB hard drive
+ (much more if you want Oracle)
4 GB hard drive
You will need all of the the section called “Individual Programs” marked REQUIRED.
If you want to serve pages to people outside of your machine, you'll need a network connection of some type.
- Note that these are minimum requirements to get a development system - up and running. For a large production system, we recommend you read about - the (now slightly obsolete) ArsDigita - Server Architecture article. -
Running a reliable database-backed web server requires experience with the server's environment, in this case UNIX. UNIX is not always an intuitive environment and this guide cannot hope to explain every - nuance. If you follow the reference implementation, all of - the unix commands you need will be in the text. However, - you will have trouble indentifying typos or other problems. - Ideally, you should be comfortable with the following tasks before + nuance. You should be comfortable with the following tasks before attempting an installation:
Adding users, groups, setting passwords @@ -58,39 +35,34 @@
Compiling a program using ./config and make.
- If you've never done these things before, consider exploring UNIX in - greater depth before installing OpenACS. Some useful resources for - doing this are described in the Resources - section. + You can complete this install without the above knowledge, + but if anything goes wrong it may take extra time to + understand and correct the problem. Some useful UNIX resources.
All of the software that you will need is free and open-source, except for Oracle. You can obtain a free copy of Oracle for development purposes. This is described in the Acquire Oracle section. -
The basic steps to getting OpenACS up and running are: -
Install an OS and supporting software
Install a webserver (AOLServer)
Install a database (Oracle or - PostgreSQL)
Install a database driver (allows the webserver to talk to the database) -
Start the OpenACS - installer, which will configure a database.
This is text that - tells you to do something, like click a - or -
This is an option you will see - on screen, such as in a radio button list or menu.
This is text that you will type.
This is text from a program or file which you may need to +
Install an OS
Install a webserver (AOLServer)
Install a database (Oracle or + PostgreSQL)
Copy the OpenACS files into place and start the OpenACS installer, which will configure a database instance.
This is text you will see on + screen, such as a or link + in a radio button list or menu.
This is text that you will type.
This is text from a program or file which you may need to examine or edit:
if {$database == "oracle"} {
set db_password "mysitepassword"
}This is text that you will see and type in a command shell, including text you may have to change. It is followed by a list of just the commands, which you can copy and paste.
[root@localhost root]# su - nsadmin -[nsadmin@localhost aolserver]$ svc -d /service/openacs-dev -[nsadmin@localhost aolserver]$ dropdb openacs-dev +[nsadmin@localhost aolserver]$ svc -d /service/server1 +[nsadmin@localhost aolserver]$ dropdb server1 DROP DATABASE -[nsadmin@localhost aolserver]$ createdb openacs-dev +[nsadmin@localhost aolserver]$ createdb server1 CREATE DATABASE -su - nsadmin -svc -d /service/openacs-dev -dropdb openacs-dev -createdb openacs-dev
We'll do our best to assure that following our instructions will get you to the promised land. If something goes wrong, don't panic. There are plenty of ways to get help. Here are some tips: @@ -106,59 +78,109 @@ worry if you feel overwhelmed by all the information in the error logs. Over time, you'll find that they make more and more sense. Soon, you'll actually look forward to errors so that you - can find the problem in the log. + can run to the log and diagnose the problem.
Search the bboards at openacs.org - you'll often find many people who have struggled through the same spot that you're in.
+ The bottom of each page has a link to OpenACS.org, where you can post + comments and read other users comments about the + contents of the page. +
Ask questions at the irc channel on openprojects.net - (#openacs). They're knowledgeable and quite friendly if you can - keep them on topic. + (#openacs). They're knowledgeable and quite friendly + if you can keep them on topic.
Post a question on the bboards. Make sure you've done a search first. When you do post, be sure to include your setup information (OS, etc) as well as the exact commands - that are failing with the accompanying error. If you want to post - stuff from your logs (please do!), be sure to enclose them in - <PRE></PRE> tags so that they don't get all jumbled - together. + that are failing with the accompanying error. If + there's a SQL error in the TCL error or in the log, + post that too.
If you find errors in this document or if you have ideas about making it better, please post them in our BugTracker. -
After reading through this tome, you may ask yourself if there is a better way. Well, not quite. Jonathan Marsden has created RPMs (at http://www.xc.org) for OpenACS 4.5 but there are not yet any for version - 4.6. There has been talk about automating the install process, + 5.0.0. There has been talk about automating the install process, but that hasn't happened yet. Stay tuned! -
This document was created by Vinod Kurup, but it's really just plagiarism from a number of documents that came before it. If I've used something that you've written without proper credit, let me know and I'll fix it right away. -
These are a few of my sources:
+
Versions 4.6.2 to present were edited by Joel Aufrecht. +
These are a few of my sources:
Joel Aufrecht's OpenACS 4.5 Quick Guide. -
</listitem>+
Please also see the Credits section for more acknowledgements. -
+ Here's a list of some helpful documentation for various OS's +
+ Painless Debian + GNU/Linux by Stephen van Egmond +
+ + Official + Debian Guide + +
+ + RedHat + +
+ + Mandrake + +
+ + SuSE + +
+ Once you get your OS installed, it's imperative that you secure your + installation. As Jon Griffin repeatedly warns us, "No distribution is + secure out of the box." The Reference Platform implements + some basic precautions, but security is a process, not a + condition. If you are responsible for a computer hooked to the + internet, you are responsible for learning some rudiments of + security, such as monitoring the state of a computer, + maintaining patch levels, and keeping backups. We recommend + these resources: +
Here are some resources that OpenACS users have found useful. -
+
Philip and Alex's Guide to Web Publishing - A very readable @@ -191,7 +213,7 @@ Linux in a Nutshell -
The UNIX Reference Desk @@ -208,4 +230,4 @@ IBM developerworks on basic and intermediate Linux skills (requires registration) -