Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/acs.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/Attic/acs.xml,v diff -u -N --- openacs-4/packages/acs-core-docs/www/xml/install-guide/acs.xml 13 Mar 2001 22:59:26 -0000 1.1 +++ /dev/null 1 Jan 1970 00:00:00 -0000 @@ -1,863 +0,0 @@ - -Installing the ArsDigita Community System v 4.0 - - -Downloading the ACS - - - - - Download the following from the ArsDigita download page to the - /tmp directory: - - - - - - ArsDigita Community System v 4.0. - - - - - - - - Login as nsadmin and uncompress the downloaded components into - /web. Substitute the correct file name into the line - below. Tip: If you type acs- and then press the - TAB key, your shell should complete the file name - for you. - - - -$ su - nsadmin -; Enter nsadmin's password. -$ cd /tmp -$ tar -xzvf acs-4.0.tar.gz --directory=/web - -; Stay logged in as nsadmin. - - - - - - You should now have an acs/ directory tree in - /web. Rename this directory to whatever you want - your web service to be identified as. The name of your web service is - referred to as the service_name. This identification is used - internally by AOLserver to differentiate your services from one - another. A service name should be a single word, letters and - numbers only. If the name of your site is one word, that would - be a good choice. For example "arfdigita" is the service - name for the ArfDigita.org - community. - -$ cd /web -$ mv acs service_name - - - - - - - - -Prepare Oracle for ACS - - - You should be logged on as nsadmin for this step and - you should make sure that nsadmin is in the - dba group. - - - - Verify nsadmin membership by typing groups when you - login: - -$ groups -nsadmin dba web - - - If you do not see these groups, take the following action: - -$ su - # Enter root password -# usermod -g nsadmin -G dba,web nsadmin - - - If you get an error about an undefined group, then add that group - manually: - -# groupadd dba -# groupadd nsadmin -# groupadd web - - - Make sure to logout as root when you are finished with - this step and log back in as nsadmin. - - - - - - Connect to Oracle using svrmgrl and login: - - - -$ svrmgrl - -SVRMGR> connect internal -Connected. - - - - - - Determine where the system tablespaces are stored: - -SVRMGR> select file_name from dba_data_files; - - - Example results: - -/ora8/m01/app/oracle/oradata/ora8/system01.dbf -/ora8/m01/app/oracle/oradata/ora8/tools01.dbf -/ora8/m01/app/oracle/oradata/ora8/rbs01.dbf -/ora8/m01/app/oracle/oradata/ora8/temp01.dbf -/ora8/m01/app/oracle/oradata/ora8/users01.dbf -/ora8/m01/app/oracle/oradata/ora8/indx01.dbf -/ora8/m01/app/oracle/oradata/ora8/drsys01.dbf - - - - - - Using the above output, you should determine where to store your - tablespace. As a general rule, you'll want to store your - tablespace on a mount point under the /ora8 directory - that is separate from the Oracle system data files. By default, the - Oracle system is on m01, so we will use - m02. This enables your Oracle system and database files - to be on separate disks for optimized performance. For more - information on such a configuration, see Chapter - 12 of Philip's book. - For this example, we'll use /ora8/m02/oradata/ora8/. - - - - - - - Create the directory for the datafile; to do this, exit from - svrmgrl and login as root for this - step: - -SVRMGR> exit -$ su - -; Enter root password. -# mkdir -p /ora8/m02/oradata/ora8/ -# chown nsadmin.web /ora8/m02/oradata/ora8 -# chmod 775 /ora8/m02/oradata/ora8 -# exit -$ - - - - - - As nsadmin, create a tablespace for the service. It - is important that the tablespace can autoextend. This - allows the tablespace's storage capacity to grow as the size of - the data grows. We set the pctincrease to be a very low value so that - our extents won't grow geometrically. We do not set it to 0 at - the tablespace level because this would affect Oracle's ability - to automatically coalesce free space in the tablespace. - -$ svrmgrl - -SVRMGR> connect internal; -SVRMGR> create tablespace service_name datafile '/ora8/m02/oradata/ora8/service_name01.dbf' size 50m autoextend on default storage (pctincrease 1); - - - - - - Create a database user for this service. Give the user access to the - tablespace and rights to connect. (Substitute - database_password with the appropriate password.) - - Write down what you specify as service_name and - database_password. You will need this information - for configuring exports and AOLserver. - -SVRMGR> create user service_name identified by database_password default tablespace service_name -temporary tablespace temp quota unlimited on service_name; -SVRMGR> grant connect, resource, ctxapp, javasyspriv, query rewrite to service_name; -SVRMGR> revoke unlimited tablespace from service_name; -SVRMGR> alter user service_name quota unlimited on service_name; -SVRMGR> exit; - - - - Your table space is now ready. In case you are trying to delete a - previous ACS installation, consult these commands in below. - - - - Make sure that you can login to Oracle using your - service_name account: - -$ sqlplus service_name/database_password -SQL> select sysdate from dual; - -SYSDATE ----------- -2000-06-11 - -SQL> exit - - - - You should see today's date in a format 'YYYY-MM-DD.' - 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 Oracle documentation. - - - - - - - -Configuring AOLserver - - - The AOLserver architecture lets you run an arbitrary number of virtual - servers. A virtual server is an HTTP service running on a specific port, - e.g. port 80. In order for the ACS to work, you need to configure a - virtual server. Because the process is involved, we have prepared a - sample virtual server configuration file. - - - - Allot an IP address: You must know what IP address has been assigned - to your web service. If you don't know, contact your system - administrator and find out. If you do not have a network connection, - use localhost 127.0.0.1 Once you have installed a - virtual server as described below, you should notify your sysadmin - that you have claimed this IP. - - - - - - Save the template configuration file template-ini.ini into - /tmp. - - - - - - Login as nsadmin: - -$ cp /tmp/template-ini.ini /home/aol31/service_name.ini - - - - - - - - Replace the following variables in the file as dictated below using a - text editor. You must specify a service port for your web server to - run. The standard HTTP port number is port 80. If you are already - running a web server (such as Apache, then port 80 is likely no - longer available. We recommend setting the service port to - 8080 for a first time installation. No other service - uses this port and special access is not required to use it. If you - want to use port 80, please read . - - - - - - - - - Variable to replace - - Target Valuee - - - - service_database_username - - service_name - - - - service_database_password - - database_password - - - - AOL_HOME - - /home/aol31 - - - - service_short_name - - service_name - - - - service_short_description - - a description of your service - - - - service_email - - the email address of the maintainer - - - - ACS_HOME - - /web/service_name - - - - service_ip_address - - your ip address - - - - service_ip_name - - your dns name - - - - service_port - - what port to use (80 is standard HTTP port) - - - - service_ip_address_ssl - - disabled by default - - - - service_ip_name_ssl - - disabled by default - - - - service_port_ssl} - - disabled by default - - - - - - - - Copy this nsd-oracle script into - /tmp/nsd-oracle.txt: - -$ cd /usr/local/aolserver/bin -$ cp /tmp/nsd-oracle.txt ./nsd-oracle -$ chmod 700 /usr/local/aolserver/bin/nsd-oracle - - - - If you deviated from the Oracle - installation defaults we specified, edit nsd-oracle - as necessary. - - - - Kill any current running AOLserver processes and start a new one: - -$ killall -9 nsd -; Should probably see: -nsd: no process killed -$ /usr/local/aolserver/bin/nsd-oracle -c /home/aol31/servername.ini - - - - Attempt to connect to the service from a web browser as you did in - the AOLserver documentation. You - should specify a URL like: - -http://ip_name:ip_port/ - - - - You should see a page that looks like this - if so, go on to the next - section. - - If you don't see the login page, view your error log - (/home/aol31/log/servername-error.log) to make sure - the service is starting without any problems. If you need to make - changes, don't forget to kill any running servers. - -$ killall -9 nsd - - - - - - - - -Using the ACS Installer - - - Assuming you got your AOLserver up and running previously, - - - - You should see a page from the webserver titled ACS - Installation: Welcome. You will be warned if your version of - the Oracle driver is out of date, if AOLserver cannot connect to the - database, or if there are any problems with filesystem permissions on - the server side. But if everything is fine, you can click - Next to proceed to load the ACS Kernel data model. - - - - - - The next page shows the results of loading the ACS Kernel data model - - be prepared to wait 20-30 seconds as it works. You should see a - string of "No errors." as the tables are created in Oracle. - Finally, another Next button will appear at the - bottom - click it. - - - - - - The following page shows the results of loading the package data - models. You should see positive results for each of the previously - selected packages, but watch out for any errors. Eventually, the page - will display "Done installing packages." - click - Create Administrator. - - - - - - You should see a page, "ACS Installation: Create - Administrator" with form fields to define the ACS site - administrator. Fill out the fields as appropriate, and click - Create User. - - - - - - You should see a page, "ACS Installation: Set System - Information" allowing you to essentially name your service. Fill - out the fields as appropriate, and click Set System - Information - - - - - - You'll see the final Installer page, "ACS Installation: - Complete." It will tell you that the server is being restarted; - note that unless you already added your AOLserver entry to the - inittab, you'll need to manually restart your service. - - - - - After the server restarts and you reload the final page above, you - should see a login screen, asking for your email address and password. - Congratulations, ACS 4 is now up and running. - - - - - - -Troubleshooting - - - If you can't get to the login page, check for one of the below - errors: - - - - If you don't see a page at all. - - Check the log file. Make sure there is a line like: - -Notice: nssock: listening on http://localhost.localdomain:8000 - - - - If you can't find this line, look for a line specifying an error - listening to a port. Such errors are caused if another process is - listening to that port or if you don't have permission to access - the port. Try using another port, perhaps 8086. You specify the port - in /home/aol30/service_name.ini under - [ns/server/service_name/module/nssock] Here is a sample - for a computer programmed to listen to 127.0.0.1:8080. Try replacing - the entries in your file with this one. - -[ns/server/service_name/module/nssock] -timeout=120 -Address=127.0.0.1 -Hostname=127.0.0.1 -Port=8080 - - - - Carefully scan the error log file for other entries flagged as - errors. If you can't figure out what is wrong, try posting to the - web/db - bboard. - - - - - - - -Ensure that Your Service Automatically Starts on Boot (or any other - time the service dies) - - - This step should be completed as root. This can break every service on - your machine, so proceed with caution. - - - - - - Copy this restart-aolserver into - /tmp/restart-aolserver.txt. - - - - - - This script needs to be SUID-root, which means that the script will - run as root. This is necessary to ensure that the aolserver processes - are killed regardless of who owns them. However the script should be - executable by the web group to ensure that the users - updating the web page can use the script, but that general system - users cannot run the script. You also need to have Perl installed and - also a symbolic link to it in /usr/local/bin. - -$ su - -; Enter root password. -# cp /tmp/restart-aolserver.txt /usr/local/bin/restart-aolserver -# chown root.web /usr/local/bin/restart-aolserver -# chmod 4750 /usr/local/bin/restart-aolserver -# ln -s /usr/bin/perl /usr/local/bin/perl -# su - nsadmin - - - - - Test the restart-aolserver script by making sure all - servers are dead, starting a new server, and then killing it. You - should see the following lines. - -$ killall -9 nsd -nsd: no process killed -$ /usr/local/aolserver/bin/nsd-oracle -c /home/aol31/service_name.ini -$ restart-aolserver service_name -Killing 23727 23728 23729 23730 -$ killall -9 nsd -nsd: no process killed - - The numbers indicate the process ids (PIDs) of the processes being - killed. It is important that no processes are killed by the second - call to killall. If there are processes being killed, it - means that the script is not working. - - - - - - Assuming that the restart-aolserver script worked, - login as root and open /etc/inittab for editing. - -$ su - -; Enter root password -# emacs -nw /etc/inittab - - - - - Copy this line into the bottom of the file as a template, making sure - that the first field nss is unique. - -nss:2345:respawn:/usr/local/aolserver/bin/nsd-oracle -i -c /home/aol31/service_name.ini - - - - Important: Make sure there is a newline at - the end of the file. If there is not a newline at the end of the file, - the system may suffer catastrophic failures. - - - Still as root, enter the following command to re-initialize - /etc/inittab. - -# killall -9 nsd -# /sbin/init q - - - - - - - Important: See if it worked by running the - restart-aolserver script again. - -# restart-aolserver service_name -Killing 23750 23753 23754 23756 - - - - If the processes were killed, congratulations, your server is now - automated for startup and shutdown. On to the Acceptance Tests! - - - - - -How to Transfer Data - - If you are moving the service from one location to another, export code - for the old database and import into the new. If your database has been - hosed and you want to restore a backup, use the imp command. - These commands can be run from the shell, you don't need to use - sqlplus. To export: - -exp service_name/database_password file=foo.dmp consistent=y full=y - - - To import: - -imp service_name/database_password file=foo.dmp [fromuser=olduser touser=service_name] - - - - - - -Running AOLserver on Port 80 - - If you want to run the service on port 80 (the default HTTP port), you - need to add some additional settings to your - service_name.ini file in /home/aol30. Under the - [ns/parameters] section, ensure that there is an entry - -User=nsadmin - - Moreover, you will need to start the service as root. If - you follow the instructions above for automating - startup, this will be taken care of, but if you ever start the server - from the command line, be sure to su - first. - - These steps are required because port 80 is a privileged - port. Only certain users can claim it. When you start - nsd as root, it obtains the port, and then changes to - run as whatever user you specify in the server configuration file. This - ensures a high level of security, as the server, once started, is not - running as root. This mean that if someone was able to - exploit your web server to execute a command on your server, they would - not be able to gain root access. - - - - - - -Deleting a tablespace - - Should it become necessary to rebuild a tablespace from scratch, you can - use the drop user command with the cascade - option. This command will drop the user and every database object the - user owns. - -drop user -service_name cascade; - - - If this does not work because svrmgrl "cannot drop a user that is - currently connected", make sure to kill the AOLserver using this - user. If it still does not work, do: - - select username, sid, serial# from v$session where username='service_name'; - - - and then - -alter system kill session 'sid,serial#'; - - - where sid and serial# are replaced with the - corresponding values for the open session. - - Use with caution! - - If you feel the need to delete everything related to the - service, you can also issue the following: - -drop tablespace service_name including contents cascade constraints; - - - - - - -Set Up Nightly Oracle Exports - - - While you're working with Oracle, you should configure it to do - automatic exports. An export is a separate backup copy of the database. - This copy includes all of the database's state at the time that the - export was initiated. If your database is corrupted, you can restore from - one of these backups (see ). You should - do this step as root. - - - - Download the backup script. Save the file export-oracle.txt as - /tmp/export-oracle.txt. - - - - - - Login as root. The following commands will install the export script: - - -$ su - -; Enter root password -# cp /tmp/export-oracle.txt /usr/sbin/export-oracle -# chmod 700 /usr/sbin/export-oracle - - - - - - Setup the export directory; this is the directory where backups will - be stored. We recommend the directory - /ora8/m02/oracle-exports. - -# mkdir /ora8/m02/oracle-exports -# chown oracle.dba /ora8/m02/oracle-exports -# chmod 770 /ora8/m02/oracle-exports - - - - - - Now edit /usr/sbin/export-oracle and change the - SERVICE_NAME and DATABASE_PASSWORD fields - to their correct values. If you want to use a directory other than - /ora8/m02/oracle-exports, you also need to change the - exportdir setting. - - Test the export procedure by running the command: - -# /usr/sbin/export-oracle -mv: /ora8/m02/oracle-exports/oraexport-service_name.dmp.gz: No such file or directory - -Export: Release 8.1.6.1.0 - Production on Sun Jun 11 18:07:45 2000 - -(c) Copyright 1999 Oracle Corporation. All rights reserved. - - -Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production -With the Partitioning option -JServer Release 8.1.6.0.0 - Production -Export done in US7ASCII character set and US7ASCII NCHAR character set -. exporting pre-schema procedural objects and actions -. exporting foreign function library names for user SERVICE_NAME -. exporting object type definitions for user SERVICE_NAME -About to export SERVICE_NAME's objects ... -. exporting database links -. exporting sequence numbers -. exporting cluster definitions -. about to export SERVICE_NAME's tables via Conventional Path ... -. exporting synonyms -. exporting views -. exporting stored procedures -. exporting operators -. exporting referential integrity constraints -. exporting triggers -. exporting indextypes -. exporting bitmap, functional and extensible indexes -. exporting posttables actions -. exporting snapshots -. exporting snapshot logs -. exporting job queues -. exporting refresh groups and children -. exporting dimensions -. exporting post-schema procedural objects and actions -. exporting statistics -Export terminated successfully without warnings. - - - - If you don't have any warnings, proceed to automate the - backups. - - - - Automating backups is accomplished using the UNIX - crontab facility. - - While still root, run the following command. You - can replace the EDITOR="emacs -nw" portion - with whatever editor your prefer, such as EDITOR=vi. - -# export EDITOR="emacs -nw" -# crontab -e - - - Now add the following line on a line by itself - -0 23 * * * /usr/sbin/export-oracle - - - - Save the file, exit the editor. Verify that the addition succeeded - by checking the output of the following command. - -# crontab -l | grep export-oracle -0 23 * * * /usr/sbin/export-oracle -# exit -; Logout - - - If you see the line, go ahead and log out. - - - - - - -($Id: acs.xml,v 1.1 2001/03/13 22:59:26 ben Exp $) - - - Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/getting-started.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/Attic/getting-started.xml,v diff -u -N --- openacs-4/packages/acs-core-docs/www/xml/install-guide/getting-started.xml 13 Mar 2001 22:59:26 -0000 1.1 +++ /dev/null 1 Jan 1970 00:00:00 -0000 @@ -1,59 +0,0 @@ - -Getting Started and Getting Help - - -This document will guide you through the process of configuring an -ArsDigita Community System web server from scratch, beginning -with a blank computer system and finishing with a fully functional web -site ready to serve your users. Below are time estimates for each -stage of the installation: - - - - - - - - Stage - Time Estimate - - - - Red Hat 6.2 - 30 - 60 minutes - - - - Oracle 8.1.6 - 4 hours - - - - AOLServer 3.1 - 30 minutes - - - - ArsDigita Community System 4.x - 30 minutes - - - - Total - 6 hours - - - - - -Aim to understand as much as possible at each step of these -instructions. If you get stuck, try to backtrack to a point where you -knew what to do. If you need help, it is available - check for -messages about your problem at the web/db -Q&A forum. If you can't find your answer there, feel free to post -a message. ArsDigita also offers support contracts. -Please see the ArsDigita services page for -more information. - -($Id: getting-started.xml,v 1.1 2001/03/13 22:59:26 ben Exp $) - \ No newline at end of file Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/redhat.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/Attic/redhat.xml,v diff -u -N --- openacs-4/packages/acs-core-docs/www/xml/install-guide/redhat.xml 13 Mar 2001 22:59:26 -0000 1.1 +++ /dev/null 1 Jan 1970 00:00:00 -0000 @@ -1,616 +0,0 @@ - -Installing Red Hat Linux 6.2 - - -NOTE: -This document is no longer maintained but should still guide you to -a successful installation of Red Hat Linux. For further assistance, -consult the official Red Hat -Web site. - - - - -Linux Requirements - - -Red Hat Linux is our preferred Linux distribution. With Red Hat, -we can get both Oracle and -ACS to work out of the box with no trouble. However, you can install -the ArsDigita Community System (ACS) to run on any recent version of -Linux. Here are some of the key requirements that we have identified: - - - - - - - - Requirement - Reason - - - - recent kernel - A recent 2.2.x kernel is required. - - - - bash - Bash is the standard Linux shell. We assume you are - using bash for these instructions. If you're not using bash, then - you will need to substitute your shell's conventions for setting - environment variables when appropriate. - - - - glib 2.1 (or greater) - You need recent versions of these libraries for Oracle to - work properly. - - - - perl - A few parts of the ACS require perl to work correctly. If you're - doing serious web work, you'll want support for this language - anyway. If not following these instructions, you should ensure - that there is a symbolic link to your perl executable at - /usr/local/bin/perl - - - - egcs (recent version) - - Without egcs, you don't have gcc and will be unable to - compile the necessary software. - - - - - -This document is not intended to be a full set of information on the -installation of Red Hat Linux. -For full information, consult the Red Hat documentation. - - - -Caution: Before you begin, keep in mind that your hard -drive(s) will be formatted and all data will be erased. Be sure to -have backups of all of the drives in your system (not just the ones -you are formatting) before beginning. - - - - - -Getting the Red Hat Distribution for the Installation - -You have the following options: - - - - Install from CDROM. - - You can order an installation CDROM from Red Hat or download an - ISO image and burn one yourself. Once you have the CDROM, you - need to boot the computer. If you have a recent BIOS and CDROM, - you should be able to boot directly to the CDROM. Check your - system's BIOS to see if this is an option and make sure the - CDROM is set to boot before the primary hard drive. Then insert - the CDROM, boot the computer and Red Hat should start. - Otherwise, you will need a boot disk. If you bought a - commercial Red Hat package, the boot disk is included. - Otherwise, you can easily create one using one of the standard - Red Hat images. Red Hat offers more information. - - - Install over the Network. - - You can run the Red Hat install over the network if you have a - fast enough connection. You'll need to copy roughly 300-600 MB - of data, so be prepared. You need to prepare a bootdisk with - the network image. Instructions for downloading the image is here. - Read this section of the Red - Hat FAQ for further information on creating the bootdisk. - Make sure you use the bootnet.img to create your boot - disk. - - - -During the install, you will need to configure your computer's -network. Find out the following before you begin: - - - - The brand and model number of your network card. - Whether or not your network supports DHCP. If it does not, determine your - - Your IP Address - Your subnet mask - Your gateway address - Your DNS Server IP address - - - If you're doing the network install, also determine a server - name and a Red Hat FTP directory path to do the install - from. Make sure you can login to that server using - ftp and verify that the path is correct. - - - - - - -Boot Your Computer - - - -Before proceeding, ensure that you have either: - - - A bootdisk with the boot.img and a Red Hat CDROM. - A bootdisk with the bootnet.img. - - - - To begin the installation process, insert your boot media and boot - your computer. Red Hat should load and will present you with a - LILO prompt. Read the instructions, but it should be - safe to press enter. The Red Hat kernel will then load and the - installation program will start. You will see a series of dialogs. - Make your selection using the arrow keys on your keyboard and press - <ENTER> to proceed. - - - - What language should be used during the installation process? - - Select your preferred language, the default is English. - - What type of keyboard do you have? - - Unless you know otherwise, you're probably typing at a us keyboard, - the default selection. - - What type of media contains the packages to be installed? - - If you are installing from the CDROM, then ensure that the CDROM - is in your drive and select CDROM. If you are doing a net - install, select FTP and skip ahead to on network configuration. - - Come back to the next section when you are done. - - - - - - - -Select Installation Type - - - - If you all has gone well, you should now see a Welcome - screen. Press enter and move on the next dialog. You will be - prompted to select an installation type. You need to specify a - Custom installation type in order to ensure you get - all of the necessary packages. - - - - - -Partition Your Drives - - - - You need to partition your system;s hard drives before you can - install the operating system. Changing your partition table often - entails wiping out all data on the disk, so be sure to have a backup - before proceeding. - - - - We specify a minimal partitioning scheme to simplify the - installation. If you have a single drive, you should create these - partitions on /dev/hda (if you have IDE) or /dev/sda (if you have - SCSI). If you have multiple drives, you will need to configure your - system more carefully. Production Linux servers require careful - configuration of partitions in order to optimize performance. See - this HOWTO - for more information. Our simple configuration for a single large - (> 3 GB) drive follows. - - - - - - - - - - Partition Name - Size - Partition Type - Description - - - - /boot - 15 MB - Linux native - Stores the kernel and basic boot configuration. - - - - / - 3000 MB+ - Linux native - Stores the major part of the file system. - - - - <swap> - 2x RAM or 400 MB (whichever is greater) - Linux swap - Virtual memory - - - - - -After specifying a partitioning scheme, press OK to continue. -You will be asked to confirm writing the partition table to disk, -again select OK. You will be asked to confirm the formatting -of your disks. On this screen, do not enable a check for bad blocks. -Although a bad block check can identify some defects in your hard -drive, it will significantly increase the amount of time it takes to -perform the format. Press OK to continue and wait while your -drives are completely formatted. - - - - - -Configure Boot Device - - - -In order to boot your workstation, you either need to install LILO or -have a bootdisk. The LILO option is recommended. LILO -(LInuxLOader) writes some data to your hard drive's -master boot record (MBR) which allows the computer to find the -operating system. It is possible to configure LILO to boot multiple -OSes. Check the LILO -documentation for more information. We recommend creating an -emergency boot disk and installing LILO on the master boot record -(MBR) of the first hard drive (usually /dev/hda). Select it and -press enter. - - - - - -Select Packages for Installation - - - -The following packages, at a minimum, should be installed. Feel free -to install above and beyond this. Also, you may choose to -individually select packages. It is not necessary to do this, but you -may do this to add files to the distribution. You should not -remove any of these packages. You can also install RPMs post -installation, so don't feel too concerned about this phase. - - - - - - - - - Package - Description - Why You Need This - - - -Printer Support -Allows you to print -If you ever want to print anything. - - - - -X Windows -Graphical system for UNIX -Needed for Oracle installation. - - - -GNOME -X Window Manager and GUI -Needed to run X properly. - - - -Mail/WWW/Tools -Tools for checking mail, accessing the web -Basic user programs. - - - -Networked Workstation -Basic tools for configuring networking - Necessary for server programs. - - - -Anonymous FTP -A FTP server -Useful for serving files to the world. - - - -Emacs -The Ultimate Text Editor -Necessary for anything. - - - -Development -Basic compilers and scripting languages - Needed to compile AOLServer and various other programs. - - - -Kernel Development -Source for the Linux kernel -Necessary for recompiling. - - - -Utilities -Basic utilities for Linux -Necessary for accessing the system. - - - - - - -Configure Users - - - -Set a password for root. You do not need to add any more users at -this time. When asked to configure authentication information, -enable Shadow Passwords and MD5 Passwords. This will -increase the security of your system. - - - - -Configure Networking - - -You may be asked to configure networking. If your network uses DHCP, -simply select that. Otherwise, see . - - - - - -X Configuration - - - -Red Hat should automatically detect your graphics card. You can -configure your system to use a graphical login, but this is not -necessary for a production system. If your monitor is not listed, -select a "Generic" or "Generic Multisync monitor." - - - -We recommend not enabling GUI startup automatically. X requires an -enormous amount of RAM and this will reduce the amount of memory -available to Oracle. You will need to install X in order to install -Oracle and to use some of its tools, but you will not need it to run -the ArsDigita Community System. - - - - - -Copy Files - - - -At this point, sit back while Red Hat copies itself over. This -usually takes from between 10 to 30 minutes. Following this you will -be asked to reboot your computer. Take out the boot disk and eject -the CDROM and then do so. You should see a LILO: prompt. -Press enter and Red Hat Linux should start to boot! - - - - - -Acceptance Test - - - -After bootup, you should see a screen resembling this: - - - -Red Hat Linux release 6.2 (Zoot) -Kernel 2.2.14-5.0 on an i586 - -localhost login: - - - - -If you don't see a screen that offers a login, then something has gone -wrong. Consult the Red Hat support -documentation for further information. - - - -Make sure you can do the following: - - - - Switch virtual consoles - - Press CTRL-ALT-F2 to switch to virtual console number - 2. Each virtual console allows you to login and enter commands to - the Linux system. There should be 6 virtual consoles, accessible - with F1-F6. After you start X, you can switch to it - using CTRL-ALT-F7. - - Login as root - - Type root, press enter, - and then enter the password, followed by enter. - - The prompt will change from $ to #; now add a regular user to login as: - - # useradd <username> - # passwd <username> - # exit ; This will log you out. - - - - Login as the new user you created. - - Start X - - - Type startx and a graphical environment should start. If you get some - errors and X dies, login as root and type - - $ /usr/X11R6/bin/Xconfigurator - - - Follow the instructions to configure your X server. - - - Remember, you can switch between virtual consoles using CTRL-ALT-F[1-6]. - - - Open a terminal in X - - If you installed GNOME, try right-clicking on the desktop to get a pop-up menu. Then - left click "New Terminal." You should see an additional terminal. - Click on its title bar and you should be able to type in it. - - Verify that you can launch X programs - - - At the prompt, type the following: - - $ emacs ; This will load the emacs editor, our favorite program for just about anything. - ; Quit emacs by doing CTRL-X CTRL-C - - - - If emacs does not start, try the following commands. In general, if any X program does not start, please try this procedure. - - - - ; Open a new terminal window: - $ xhost +localhost - - ; Switch back to the original terminal window: - $ export DISPLAY=localhost:0.0 - $ emacs - - - - - -If all of this worked, congratulations - you now have a Red Hat Linux -server at your disposal. On to Oracle 8.1.6. - - - - - -Advanced Network Configuration - - - -At some point during the install process, depending on whether you are -installing from the CDROM or from the network, you will need to -configure your network. - - - -This screen is identified as TCP/IP Configuration. If your -network is configured to use DHCP, simply enable DHCP and proceed. -Contact your network administrator or ISP provider to determine if -DHCP is available. Otherwise, you will need to configure your network -manually. Enter the following information: - - - - - - -FieldExplanation - -IP Address -The primary address for your computer. If your network uses static IPs, -you must contact your network administrator to determine your IP address. - - -Netmask Usually, this is 255.255.255.0. However, only your network -administrator can confirm this. - - -Default gateway (IP) -The gateway address is the address of the network hardware -that enables your computer to leave its local network and access the Internet. - - -Primary Nameserver - The domain name server (DNS) is used to map between human -readable names (such as www.redhat.com) to IP addresses (such as 127.0.0.1). - - - - -Be absolutely certain these values are correct before proceeding with -the installation. When you are ready, select OK and press enter to -continue. The install program will inform you if there is an error in -the configuration and allow you to fix it. - - - -If you are doing a net install, you will be presented with a new -screen, FTP Setup. Enter the FTP site name and the path to the -Red Hat directory on that server and press OK to continue. You -should see a message: - - - -Loading second stage ramdisk - - - -If you don't see this message, either you have an incorrect FTP site -name and/or Red Hat path, or the server is unreachable. Make sure -that you have the correct path or consult the official Red Hat mirror list. - - - -($Id: redhat.xml,v 1.1 2001/03/13 22:59:26 ben Exp $) - - - - - Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/requirements.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/Attic/requirements.xml,v diff -u -N --- openacs-4/packages/acs-core-docs/www/xml/install-guide/requirements.xml 13 Mar 2001 22:59:26 -0000 1.1 +++ /dev/null 1 Jan 1970 00:00:00 -0000 @@ -1,184 +0,0 @@ - -Requirements - - -Hardware Requirements - - - -At a minimum, you need a hardware platform that allows you to run the -Oracle RDBMS comfortably. You -can do this on a wide variety of hardware platforms. At ArsDigita, we -are most familiar with running ACS production servers using Sun and HP -hardware. However, the software can also be run comfortably on Linux -and even Windows 2000. - - - -The emphasis of this document is on a Linux installation. Installing -this software on other UNIX systems, such as Solaris, is much the -same, but you will need to substitute commands native to your UNIX -system if the Red Hat Linux commands here don't work. For example, -there is a standard tool for creating new users under Solaris and Red -Hat, useradd. If your system does not support this, you -will need to substitute the appropriate command. - - - -Installing the ArsDigita Community System under Windows 2000 is a -different matter that this document does not address. Please see the -Windows 2000 installation guide -for instructions. - - -
- -Minimum Hardware Requirements for Installing onto Linux - - - A PC with a Pentium processor or better - 128 MB RAM (256 MB recommended) with 400 MB swap file - 3.5 GB hard drive space - A network connection - have your network configuration information - (such as IP address) handy when following this guide - -
- - - - - -Software Requirements - - - -The ArsDigita Community System requires: - - - - A UNIX operating system (e.g. Solaris, Linux, HP-UX), or Windows 2000 - The Oracle 8i RDBMS - The open-source AOLServer 3.0 Web Server running with the 8.3 Tcl interpreter (nsd8x) - - - -There are also initiatives to create versions of ACS that work with -other databases (see the OpenACS -project) and with other web servers (see the mod_aolserver package for Apache). However, this guide presumes a UNIX operating system, -specifically Red Hat Linux, with Oracle 8.1.6 and AOLServer 3.0. This -information may apply and be useful for other platforms, but please -exercise careful judgment in following any of the instructions. - - - - - - -Experience with UNIX - - - -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. You should be comfortable with the following tasks before -attempting an installation: - - - - Adding users, groups, setting passwords - Starting an X server and running an X program remotely - Basic file management using cp, rm, mv, and cd - Compiling a program using a makefile - - - -If you've never done these things before, consider exploring UNIX in -greater depth before installing the ArsDigita Community System. Some -useful resources for doing this taken from Philip Greenspun's bookshelf -are listed below. - - - -An excellent introduction to the command line tools and basic programs -of UNIX is UNIX -Power Tools. An excellent online resource is The UNIX Reference Desk. -However, you need to read further to get a firm grasp on -System Administration. - - - -For System Administration: - - - - UNIX - System Administration Handbook (the "red book"; a classic but dated) - - Essential - System Administration (typical O'Reilly book; also dated) - - UNIX - System Administrator's Bible (LePage and Iarerra 1998; IDG) - - - -For Solaris: - - - - Sun - Performance and Tuning - - Configuration - and Capacity Planning for Solaris Servers - - Solaris - 2.X for Managers and Administrators - - - - - -For HP-UX: - - - - Jay - Shah's HP-UX System and Administration Guide - - - -For Linux: - - - - The Linux Documentation Project - Running - Linux - Linux - in a Nutshell - - - -Above basic system administration, you need a good text editor. While -vi is functional, Emacs offers more features and is -arguably more extensive than any other text editor available today. -These two books are excellent: - - - - Learning - Gnu Emacs - - Writing - Gnu Emacs Extensions - - - - -($Id: requirements.xml,v 1.1 2001/03/13 22:59:26 ben Exp $) - - - - Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/tests.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/Attic/tests.xml,v diff -u -N --- openacs-4/packages/acs-core-docs/www/xml/install-guide/tests.xml 13 Mar 2001 22:59:26 -0000 1.1 +++ /dev/null 1 Jan 1970 00:00:00 -0000 @@ -1,204 +0,0 @@ - -Acceptance Tests - - By running through the acceptance tests below, you'll verify that - your new ACS 4 instance is running nominally, and get acquainted with the - major administration features of the system. - - - - -Installation - - - - - You should have followed the steps for installing - ACS 4; assuming the installation proceeded correctly, your server - instance should be up and running, and the root URL (http://foo.com/) - should show a login page asking for your email address and password. - Proceed to test registration below. - - - - - -Registration - - - You should test basic registration and the login process. Suggested - method: - - - Go to the index page for the Main Site; typically the URL is simply - yourserver.com/ - - Login with a new email address, and walk through registering as a - new user. - - Assuming new accounts are approved immediately, after registration - you'll be on the Workspace page for the user, where you can see and - edit personal data. - - Click the "Log out" link on the Workspace page. - - Try going back to /pvt/home.tcl again; you'll be redirected. - Login as the same user just created. - - - - - - -User Administration - - - You should test adding a user, searching for users, modifying user - data, banning or deleting a user, and spamming a class of users. - Suggested method: - - - Use the email/password combo you created during the installation - process, and login as an administrator. Go to /acs-admin/users - - Once you're at /acs-admin/users, click on "Add a - user." Create a test user. Return to user administration, - /acs-admin/users, when done. - - Do a quick search for the newly created user, and verify that - entering part of the test user's name returns the user. - - View the list of matching users and edit the user data for the new - test user. - - Delete the test user. - - Ban the test user. - - - - - - -Install and Enable a Package - - - The ACS Package Management system (APM) is central to operating your - ACS server, allowing you to manage ACS Applications and Services. - Applications are typically user-driven web systems such as Bboard or - News, while ACS Services are fundamental components such as the Object - System, Permissions, and the APM itself. Let's verify the - functionality of the APM by installing and enabling the Bboard - application, which your site will almost certainly need. - - - Logged in as an administrator, go to /acs-admin/apm - - You'll see the "ACS Package Manager Administration" - page; this is where you can view and manage all packages on your - server. Assuming Bboard is not already installed (make sure you're - looking at Package Type: Applications), click on "Load a new - package from a URL or local directory" - - You will see the "Load a New Package" page, and a form - field where you can enter a package URL. In a separate browser window, - go to the ArsDigita Package Repository, http://www.arsdigita.com/acs-repository/, and - look for ACS 4.x packages. You should see the Bboard package available - - note the directions in the Help section as to the correct URL to - enter in the "Load a New Package" page. Enter the URL and - edit it as needed, and click on "Load." - - On the following page, the APM will visit the URL you supplied, - grab the package file, and extract it on your server's filesystem. - There should be a message saying the package is now extracted into your - filesystem. You should then follow the "install" link at the - bottom of the page to continue. - - On the "Package Installation" page, you should both - install and enable the Bboard package - ensure the checkboxes to do so - are selected , and click on the "Check Dependencies" - button. - - The next page deals with installing the data model for the package; - you should see one or more SQL files with checkboxes next to each one - slated for installation. Make sure they're all checked and click on - the "Install Packages" button. - - On the final page of installation sequence, you should see - "Installing Packages," followed by messages saying the - package was enabled and installation finished. Restart the server as - directed. - - - - - - -Using the Site Map - - - One of the most flexible and powerful new features of ACS 4 is the - Site Map facility that exists for every subsite in the system. The Site - Map allows you to arbitrarily associate user-visible URLs with packages - instances, instead of having to change the underlying filesystem - directory structure. Applications can thus be deployed as an - administrator sees fit; to have a new bboard instance mapped to - foo.com/bar/bboard in addition to foo.com/fnord/bboard, she would not - need shell access to the server, nor need to copy directory trees. For - the next acceptance test, we'll "mount" an instance of the - bboard package under the Main Site (the default subsite). - - - Assuming you've installed and enabled the bboard package, and - restarted the server as directed, go to the admin page again, - /acs-admin/ - - We'll be working with the default subsite, Main Site, so click - on the "Main Site Administration" link. - - On the Main Site Administration page, click on the "Site - Map" link. - - You'll now see the principal Site Map page; notice how three - subfolders of the site root "/" are preinstalled: - "/acs-admin" which you've been using thus far, - "/api-doc" where developers can get detailed information on - API calls, and "/doc" which is probably where you're - reading this Acceptance Test document from. - - To keep things simple, let's have our bboard instance be mapped - to a sub-folder of the root "/" level. On the first row which - starts with "/" click on the "new sub folder" - link. - - You'll see a form field asking for the name of the sub folder. - Type in "test-bboard" and click the "New" - button. - - You should now see "test-bboard" in the list of URLs for - the Main Site. Click on the "new application" link in the - same row to begin creating an instance of the bboard package on - "test-bboard" - - You'll now see a field where the package instance can be named, - and a drop-down menu of packages. Call the instance "Test - Bboard" and select bboard from the list of packages, and click - "New" to continue. - - A Bboard instance is now running on the URL - "/test-bboard" on your site! To go there, just click on the - link "Test Bboard" under the Application column on the Site - Map page, or visit the URL directly in your browser. - - - This covers the basics of getting a user-visible application up on ACS - 4 - you can now install and deploy more packages, drop mappings, and - otherwise configure the functionality and organization of your site as - you see fit. - - -($Id: tests.xml,v 1.1 2001/03/13 22:59:26 ben Exp $) - - - Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/top.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/Attic/top.xml,v diff -u -N --- openacs-4/packages/acs-core-docs/www/xml/install-guide/top.xml 13 Mar 2001 22:59:26 -0000 1.1 +++ /dev/null 1 Jan 1970 00:00:00 -0000 @@ -1,138 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - -]> - - -ACS Documentation - - - - - - - - ACS core team - - - - - -For ACS Developers - -This is the place to look if you want to extend the ACS and build on top -of what's already here. Here you can find out about the guts of the system. - - - -ACS Developer's Guide - - - Overview - The Developer's Guide tells you what you need to know in order to extend the ACS. - - - &objects; - &packages; - &rp; - &api; - &templates; - &permissions; - &subsites; - - - - -Engineering Standards - - - Overview - How to behave - - - &dbprimer; - &design-template; - &requirements-template; - &versioning; - &constraint-naming; - &filenaming; - &plsql-standards; - - - - - - - - - \ No newline at end of file