Filtered by category Subsystems Documentation, 1 - 10 of 78 Postings (all
Created by Maurizio Martignano, last modified by Maurizio Martignano 11 hours 37 minutes ago
Windows-OpenACS (vers. 3.1.8 - Ocotber 2016) is a Windows 64 port of OpenACS 5.9.0 and the latest snapshot of NaviServer and is available here.
This port installs and runs on the following systems:
- Windows 8.1,
- Windows 10,
- Windows Server 2012 R2, and
- Windows Server 2016 TP.
Created by Gustaf Neumann, last modified by Gustaf Neumann 20 Sep 2016, at 02:06 PM
The probably easiest way to upgrade between PostgreSQL versions is as follows (described here from 9.4 to 9.5, based on the directory structure as provided by Mac Ports)
# Dump all databases from pg 9.4
sudo -u postgres $PGBIN/pg_dumpall | gzip -9 > ~/pg-dump-all-$DATE.gz
Then stop pg 9.4, start pg 9.5, then reload the dump:
# Restore all databases and roles from dump into pg 9.5
gunzip < ~/pg-dump-all-$DATE.gz | $PGBIN/psql -U postgres
voilà, start OpenACS, and everything works fine.
In case there is a problem with restoring the dump in PostgreSQL 9.5 due to the "=>" operator of hstore, one has to update the version of hstore at least to 1.1 before dump/restore (the current version of hstore is 1.4; for details see hstore-upgrade ).
In case, you want to upgrade your legacy OpenACS installation from PostgreSQL 8.* to 9, read upgrade-oacs-5-8.
Created by Gustaf Neumann, last modified by Gustaf Neumann 10 Sep 2016, at 10:27 AM
OpenACS (5.8) works with PostgreSQL 9.1 or newer out of the box, no special configurations in postgresql.conf are needed like with previous versions.
To work with PostgreSQL 9, one has to use an actual postgres driver:
OpenACS core + commonly used packages (search, forums, xowiki, ...) have been tested with PostgreSQL 9.2.4
For new installs, OpenACS 5.8 works without further considerations. When upgrading the database to PostgreSQL 9.*, one has to keep in mind, that not only the sql-install scripts have to be SQL 9.* compatible, but as well the update scripts (migration scripts). During the work for making OpenACS compatible with PostgreSQL 9.*, we did not update (all) of the migration scripts (e.g. kernel upgrades) of earlier versions, therefore one should run the upgrade scripts to OpenACS 5.7 with an PostgresSQL 8.* database.
Therefore, the following upgrade steps are recommended for upgrading from OpenACS 5.5 to 5.7 to OpenACS 5.8:
- For users of PostgreSQL versions earlier than 8.4: In case you run a version of OpenACS earlier than 5.5 then upgrade first your code to OpenACS 5.5 (oacs-5-5 branch from the CVS Repository), then dump your database and reload it into pg 8.4 (e.g. into pg 8.4.17, which is the oldest still supported version from postgres, end-of-life July 2014). Then continue with the next step below.
- For users of PostgreSQL version 8.4 (or newer before 9): Make sure, you are running Tcl 8.5, then get OpenACS 5.8.0 (or newer) and upgrade OpenACS and your used packages (e.g. via acs-admin/apm + "install packages"). Then dump the database and restore it in pg 9.*.
Created by Rocael Hernández Rizzardini, last modified by Gustaf Neumann 08 Jul 2016, at 02:25 PM
PostgreSQL 8.x (e.g. 8.1.* and later up to 9.1) require a few changes in the configuration file for backward compatibility (see below).
Note that OpenACS 5.8 or newer works with PostgreSQL 9.1 (or newer) out of the box, the special configurations for postgresql.conf described below are not needed anymore.
1. Configure postgres8 with all compatibility ON in postgresql.conf:
add_missing_from = on
regex_flavor = extended
default_with_oids = on
2. If you are upgrading an OpenACS site between versions 4.5.2 to 5.2 and not continuing to 5.3, then: After the createdb step to create the OpenACS database, generate the next function before you import the pre-existing OpenACS database.
From your shell prompt enter:
From the psql prompt enter the follow plpgsql code to create the bitfromint4 function:
create or replace function bitfromint4 (integer)
returns bit varying as '
end;' language 'plpgsql' immutable strict;
This is the original thread
For a full script on how to install PG 8.2 with ltree and tsearch2 look at Malte's install script
Created by OpenACS community, last modified by Gustaf Neumann 07 Jul 2016, at 02:34 PM
Documentation Requirements for Developer Tutorials
By the OpenACS Community. This section is a collection of documentation requirements that have been expressed in the OpenACS forums to 4th July 2003.
OpenACS developer tutorial documentation should meet the following requirements. No significance has been given to the order presented, topic breadth or depth here.
list learning prerequisites to customize, fix, and improve OACS modules, and create new ones. You are expected to have read and understand the information [minimum requirements similar to adept at Using OpenACS Administrating Guide] before reading this guide.
Refer to development documentation instead of duplicating here
List suggestions for installing and setting up a development environment; these can be annotated links to the installation documentation
Provide working examples that highlight the various subsystems, tcl environment, OpenACS protocols, aolserver template and ns_* commands, OpenACS templating, sql queries, db triggers, scheduling protocols, how to use the page contract, how to get the accessing user_id etc
Show how to construct basic SQL queries using the db API,
The life of an http request to a dynamic, templated page
General rules to follow for stability, scalability
Show the step by step customizing of an existing package that meets current recommended coding styles of OpenACS package development, by referring to developer resources.
Use the ArsDigita problem sets and "what Lars produced for ACS Java" as inspiration for a PostgreSQL equivalent tutorial about developing a new OpenACS package including discussion of the significance of the package documentation templates
Include a summary of important links used by developers
Note any deprecated tools and methods by linking to prior versions instead of describing them in current docs
Created by roc@, last modified by Gustaf Neumann 17 Jun 2016, at 11:52 AM
This are instructions to obtain OpenACS, either as a released distribution (a .tar.gz file) or from CVS.
Obtain a released version of OpenACS via .tar file:
Download from OpenACS.org: http://openacs.org/projects/openacs/download/
Unpack the OpenACS tarball. Usually something like this works:
tar zxvf openacs-5.9.0.tgz
Obtain OpenACS from CVS (a certain release with potential patches, or the HEAD version):
If you want to track fresh code developments between releases, or you are an OpenACS core developer, you may want to install from CVS. This is identical to downloading a distribution, except that you get the files from CVS instead of the tarball. The following commands are used to obtain the newest version of the OpenACS 5.9 branch from CVS:
cvs -d:pserver:firstname.lastname@example.org:/cvsroot login
# press enter for password
cvs -d:pserver:email@example.com:/cvsroot checkout -r oacs-5-9 acs-core
The command above checks out the core packages of OpenACS in a directory named openacs-4. For the entire OpenACS version 5.9 branch you can use the following commands (adjust as required going forward):
cvs -d:pserver:firstname.lastname@example.org:/cvsroot checkout -r oacs-5-9 openacs-4
If the the branch name (like oacs-5-9) is omitted, the the leading edge developer version (the HEAD release) is obtained
cvs -d:pserver:email@example.com:/cvsroot checkout openacs-4
In order to check out a single package (e.g. the package cronjob) from e.g. the leading edge developer version (HEAD), use
cvs -d:pserver:firstname.lastname@example.org:/cvsroot checkout openacs-4/packages/cronjob
For most OpenACS packages, CVS aliases are defined. In order to checkout e.g. the forums package from OpenACS 5.5, just use:
cvs -d:pserver:email@example.com:/cvsroot checkout -r oacs-5-9 forums
More info here: http://www.openacs.org/test-doc/using-cvs-with-openacs
Looking for README instructions or installers? View the OpenACS Installation instructions: en:openacs-system-install, otherwise continue by setting up the OpenACS distribution:
Set up the file system for one or more OpenACS sites
For Linux Standard Base compliance and ease of backup, all of the files in each OpenACS site are stored in a subdirectory of /var/lib/aolserver, one subdirectory (SERVERROOT) per site (see: en:openacs-reference-platform). The first time you install an OpenACS site on a server, you must create the parent directory and set its permissions:
While logged in as root:
mkdir -p /var/lib/aolserver
chgrp web /var/lib/aolserver
chmod 770 /var/lib/aolserver
Move the uncompressed code to SERVERROOT and rename the directory to $OPENACS_SERVICE_NAME:
mv openacs-4 /var/lib/aolserver/$OPENACS_SERVICE_NAME
Created by OpenACS community, last modified by maria katosvich 13 Jun 2016, at 01:24 PM
These are the defaults we create and use during the standard installation process, in helper scripts and other places. None of these locations are set in stone - they're simply the values that we've chosen.
Default directories for a standard install
|Fully qualified domain name of your server
|name of administrative access account
|OpenACS service account
|OpenACS database name
|SERVERROOT - base of the OpenACS service file tree
|Location of source code tarballs for new software
|The OpenACS tarball contains some files which are useful while setting up other software. Those files are located at:
|Database backup directory
|Service config files
|Service log files
|Base compile directory
Some instructions provide cut and paste conveniences
In order for some copy and paste instructions to work in your bash shell, you must set the environment variable $OPENACS_SERVICE_NAME. Add this line to your .bashrc or .profile_bash file to set the environment variable for a specific user:
To set it globally so that it works for any new users or special service users you may create, add the above line to the file /etc/profile
$OPENACS_SERVICE_NAME is set to the value of service0 on a default install. Change service0 to a word that better represents your project. The other values we recommend you leave unchanged unless you have a reason to change them.
A service name ($OPENACS_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 "$OPENACS_SERVICE_NAME" might be the service name for the OPENACS_SERVICE_NAME.net website.
Some discussion that lead to these default values: http://openacs.org/forums/message-view?message_id=82934
Created by Byron Linares, last modified by Gustaf Neumann 20 Apr 2016, at 10:52 AM
NOTE: Currently (04/2016), the best option to get OpenACS 5.9.* running on Windows is to use the native windows installation Windows-OpenACS by Spazio IT (Maurizio Martignano).
This page describes the installation of (quite old) components based on cygwin, but might still be useful for people, that can't use Maurizio's implementation for whatever reason:
- OpenACS 5.2.3
- DotLRN 2.2.0
- AOLServer 4.0.beta10_2003
- PostgresSQL 7.4.3
- OpenACS 5.2.3
- DotLrn 2.2.0
Installer Download :
The installer is available in openacs community page.
- OpenACS/dotLRN installer
- OpenACS 5.2.0 installer
Run the "OpenACS/DotLRN Installer" called setup.exe, read the license document before continuing, the installer will ask for some information, this will be used to make the automatic installation.
There are to ways to install the components; manually or automatic
- dotLRN Manual and openACS Manual:
- In this modality the entered personal data in the installer will be omitted and will be necessary to retake the installation from a browser window and enter the necessary data to continue the creation of the data modeling.
- dotLRN Automatic and openACS Automatic
- In this modality the installer its in charge of all the work, when finishing creating the data model the following step would be to reinitiate the service and continue with the use of the platform.
- Source Code:
- The installer will put in the installation folder the source code of the same one.
Select what you want to install and click next. After the installer places all the files, a browser window will be opened and the installation have to be continued from here, if the automatic mode has been selected wait to the installation finishes. When the installation finishes restart the server and type in a web browser "http://localhost"
- OpenACS on the web: access to http://localhost/
- Start Server: Bach file to initiate the server (aolserver, postgresql, cygwim)
- Stop Server: Bach file to stop the server (aolserver, postgresql, cygwin)
- Unistall OpenACS: Uninstall all
- Check if CygWin: Please execute the file server/cygwin/cygwin.bat. You should get a black screen with some green text saying: "yourusername@yourcomputer" and the "$".
- Check PostgreSQL: in the cygwin window typy psql -l , You should get the names of all data base.
- Check AOLServer: ps -alW | grep nsd , You should get some thing like this
- 2312 0 0 2312 ? 0 07:52:20 C:\OpenACS\nsd4\bin\nsd.exe
developed at the Galileo University (www.galileo.edu) by Byron Haroldo Linares Roman firstname.lastname@example.org as part of the E-LANE project (www.e-lane.org)
related forum threads
OpenACS/dotLRN installer for MSWindows
Created by Michael Aram, last modified by Gustaf Neumann 12 Apr 2016, at 10:39 AM
hstore is a postgresql module, which is used optionally by newer versions of xowiki and xowf (xowiki content flow ) to provide quick access to the "instance_attributes" (the per-form or per-workflow attributes not part of the native content repository data model). The supporting functions (creating indices, etc) are currently mostly part of the xowiki sources (earlier: xowf).
Under Ubuntu, you can install hstore via:
psql -d <yourdb> -tAc "create extension hstore"
You can then verify the successful installation on the ds/shell using:
Created by Malte Sussdorff, last modified by Monika Andergassen 11 Apr 2016, at 10:28 AM
To monitor your server with Nagios you can use the check_http command.
check_http -h <yourip> -u /SYSTEM/dbtest -s "success"
To obtain the HTTP critical status if OpenACS can't return success, which can be either because the server isn't running or the database connection has failed.