Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/win2kinstall.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/win2kinstall.xml,v diff -u -r1.1 -r1.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/win2kinstall.xml 13 Mar 2001 22:59:26 -0000 1.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/win2kinstall.xml 3 Mar 2002 01:27:08 -0000 1.2 @@ -1,5 +1,5 @@ - -How to install ACS on Windows2000 + +How to install OpenACS on Windows2000 By Matthew Burke and Curtis Galloway @@ -24,12 +24,12 @@ Overview With the recent release of a win32 version of AOLserver, it is now - possible to run the ACS on Windows2000 and Windows98. This document - explains the steps necessary to get the ACS installed and running on your + possible to run the OpenACS on Windows2000 and Windows98. This document + explains the steps necessary to get the OpenACS installed and running on your machine. Note: We do not recommend running a production server on Windows98. But the platform is more than sufficient for working the problem sets and - for getting a feel for the ACS. + for getting a feel for the OpenACS. You'll need to use the ArsDigita binary distribution of AOLserver for the Win32 platform, which contains patches for several problems we @@ -70,21 +70,21 @@ available free from http://www.pls.com. Although the zsh shell is the only command-line tool - required to install the ACS, if you are a UNIX person used to typing + required to install the OpenACS, if you are a UNIX person used to typing ls instead of dir you'll get along much better with the Cygwin toolkit from RedHat (available at http://sourceware.cygnus.com/cygwin). This is a development library and set of tools that gives you a very UNIX-like environment under Windows. In particular, it includes bash, gzip and tar, which you can - use to perform the ACS installation instead of WinZip and zsh. + use to perform the OpenACS installation instead of WinZip and zsh. Your Oracle installation When you install Oracle, a good rule of thumb is "every default setting is wrong." We will not discuss Oracle configuration here - except to mention that the ACS requires Oracle's NLS_DATE_FORMAT + except to mention that the OpenACS requires Oracle's NLS_DATE_FORMAT parameter be set to 'YYYY-MM-DD'. Fixing this depends on whether Oracle Administration Assistant for Windows NT (yes, that's Windows NT) will run on your @@ -123,7 +123,7 @@ If you are an Oracle achiever and have more than one Oracle installation on your machine, you will see HOME0, HOME1, HOME2, etc. Choose the subtree that corresponds to the - Oracle installtion you wish to use with the ACS. + Oracle installtion you wish to use with the OpenACS. @@ -158,13 +158,13 @@ Extract the ArsDigita AOLserver distribution onto the C: drive into the default aol30 directory. You can install it on any drive, but it will make your life easier if you keep the AOLserver - binary and your ACS instance on the same drive. For the rest of these + binary and your OpenACS instance on the same drive. For the rest of these instructions, we'll assume that you used drive C:. -Untar the ACS +Untar the OpenACS We recommend rooting webserver content in c:\web. Since most servers these days are expected to run multiple services from multiple IP @@ -182,7 +182,7 @@ "yourdomain.com". - download the ACS (see above) into + download the OpenACS (see above) into c:\temp\acs.tar.gz use WinZip (or equivalent) to extract the files to @@ -258,7 +258,7 @@ configuration information for AOLserver. This should be called yourdomain and should be located in c:\aolserve3_0. The second is an .ini file that configures - the ACS and is discussed below. Note that pathnames in + the OpenACS and is discussed below. Note that pathnames in yourdomain must use forward slashes rather than the Windows back slashes. This is also true for the .ini file. @@ -285,7 +285,7 @@ -Configuring ACS itself +Configuring OpenACS itself If you want a system that works, go to c:\web\yourdomain\parameters and copy ad.ini to @@ -295,7 +295,7 @@ Each section of yourdomain.ini has a hardcoded "yourservername" in the name (e.g. - [ns/server/yourservername/acs]). This means that the ACS + [ns/server/yourservername/acs]). This means that the OpenACS will ignore your configuration settings unless your AOLserver name happens to be "yourservername". Therefore you must go through yourdomain.ini and change "yourservername" to @@ -349,7 +349,7 @@ Configuring Permissions Now, you need to protect the proper administration directories of the - ACS. You decide the policy although we recommend requiring the admin + OpenACS. You decide the policy although we recommend requiring the admin directories be accessible only via an SSL connection. Here are the directories to consider protecting: @@ -389,10 +389,10 @@ Closing Down Access - The ACS ships with a user named "anonymous" (email + The OpenACS ships with a user named "anonymous" (email "anonymous") to serve as a content owner. If you're operating a restricted-access site, make sure to change the anonymous - user's password. In recent versions of the ACS you cannot log into + user's password. In recent versions of the OpenACS you cannot log into "anonymous" because the account does not have a valid user state. Log in as a sysadmin and change the anonymous user's password from https://yourservername/admin/users. You should read the @@ -426,16 +426,16 @@ -Running Multiple Instances of the ACS +Running Multiple Instances of the OpenACS - You can run multiple instances of the ACS on a physical machine but they + You can run multiple instances of the OpenACS on a physical machine but they must each be set up as a separate Windows service. Each instance of the - ACS must have its own: + OpenACS must have its own: Oracle tablespace and a user account with the appropriate permissions on that tablespace. Each of these tablespaces must have the - ACS data model loaded. + OpenACS data model loaded. file with the appropriate settings including server name, auxconfig, ipaddress, and port. @@ -453,7 +453,7 @@ an Oracle tablespace, iguanasdirect with a user iguanasdirect and password secretiguanas - For each of these tablespaces/users you would load the ACS data model as + For each of these tablespaces/users you would load the OpenACS data model as described above. Then in c:\aolserver3_0 create files for each service, i.e. lintcollectors and iguanasdirect. These files would point to their respective