Hi,
I just went through installing turbine on NT and Solaris and though I would
feed back on the areas that I had difficulty and where I felt the
documentation could be beefed up. I'm a total newbie to turbine, mysql, etc.
so I figure other people might have similar issues. I've included a modified
install.txt in case you are interested.
The first strange thing is that the .tar file, untarring on Solaris, had
directory checksum errors. I suppressed these and had to rename some files
by hand that were not extracted correctly. Maybe double check the procedure
that makes the .tar.gz file snapshot. This did not happen on NT.
For me it was not that clear how to install the db tables. The .sql files
are in the src/sql directory not the "docs" directory as stated. I would
include the a specific example and get rid of mentioning the non-existent
"schema.sql" file.
mysql turbine < MySQL_users_roles_permissions.sql
mysql turbine < MySQL_id_table.sql
mysql turbine < default_roles_permissions.sql
The provided TurbineResources.properties should have the following
"out of the box" or an addition to the documentation saying to add the line
module.packages=org.apache.turbine.samples,org.apache.turbine.modules
Otherwise it does not find the Login Screen. It took a while to figure this
out.
After the login screen, the link to the screen admin.FindUser was not found.
Maybe this is expected, I'm note sure, but it doesn't give me a warm fuzzy
after an install....
Some other small things I changed as well.
Ok, hope this helps....
Mark
----------------------------------------------------------------------------
---
-- INSTALLATION
----------------------------------------------------------------------------
---
Necessary Packages
------------------
All of the necessary packages required to build/use Turbine (except the
JDBC)
drivers now come with Turbine in the /lib directory. The build scripts are
all
configured to know about the files in the lib directory. If you have build
errors where javac cannot find certain classes or packages, please make sure
that the paths to the lib directory is correctly set.
(JDBC Database Drivers)
MM MySQL JDBC Drivers (if you use MySQL as your database)
<http://www.worldserver.com/mm.mysql/>
Oracle JDBC Drivers (if you use Oracle as your database)
*Note, you need to register to access this URL. It is free.*
<http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm>
Postgres JDBC Drivers (if you use Postgres as your database)
They come with the download.
<http://www.postgresql.org/>
InstantDB JDBC Drivers (if you use InstantDB as your database)
They come with the download.
<http://instantdb.enhydra.org/>
If your database is not listed here, please subscribe to the Turbine mailing
list and send us the link to the drivers so that we can add it here.
<http://java.apache.org/main/mail.html>
----------------------------------------------------------------------------
---
To Compile
----------------------------------------------------------------------------
---
For Win32:
In the "build" directory is a script called "build-turbine.bat". Edit
this script and specify the locations of all the necessary packages
outlined above. After you have done this, you can double click this
file and it will build Turbine into the "bin" directory.
For Unix:
In the "build" directory is a script called "build-turbine.sh". Edit
this script and specify the locations of all the necessary packages
outlined above. After you have done this, you should cd into the build
directory and execute the script by typing "sh ./build-turbine.sh".
Executing the above script will create a "bin" directory within the Turbine
distribution directory. In there will be the compiled class files (inside a
"classes" directory) as well as a "turbine.jar" file. You can either use
the .jar file directly or copy the org directory into your classpath ( see
below for more information on installation ).
If you get compiler error about not being able to find some package, then
it means that you have not edited the scripts to properly specify the paths
to each of the packages.
------------------------------
Database Related Installation.
------------------------------
#1. Run the appropriate SQL script for your database. If a script for your
specific database is not present, the SQL can easily be adapted. We
appreciate your contributions here. If your database is not supported by
the connection pooling code, please subscribe to the mailing list and ask
for help there. Include the type of database and the driver information in
your posting.
You will need to choose the appropriate .sql file for your needs according
to
what database you are using. The various schema files exist in the src/sql
directory.
For the case of the mysql database, the following lines do the trick
mysqladmin create turbine
mysql turbine < MySQL_users_roles_permissions.sql
mysql turbine < MySQL_id_table.sql
mysql turbine < default_roles_permissions.sql
Similary named files exists for other database types. We currently have
.sql files
for Oracle, MySQL and Postgres. The ones that are the most tested and
reliable
are the MySQL files because this is our database of choice. Contributions
for
more databases is most appreciated.
#2. Edit TurbineResources.properties file (in the conf directory), define
your database types and make sure that the database adaptor for your
database is uncommented, and place this file in a directory accessible to
your servlet engine.
----------------------------------------------------------------------------
---
INSTALLATION WITH Apache JServ 1.1 or higher
----------------------------------------------------------------------------
---
#1. Specify the path to the necessary packages
Place the packages that you will not be changing into the wrapper.classpath
(in jserv.properties). Please see this FAQ entry (line wrapped) for more
information on determining what will change and what won't change:
<http://java.apache.org/jyve-faq/Turbine/screen/DisplayQuestionAnswer/actio
n/SetAll/project_id/1/faq_id/2/topic_id/69/question_id/322>
Here is an example:
wrapper.classpath=<path to>/ECS.jar
wrapper.classpath=<path to>/Village.jar
wrapper.classpath=<path to>/jndi.jar
wrapper.classpath=<path to>/mail.jar
wrapper.classpath=<path to>/activation.jar
Place the rest of the classes that you will be using, such as your Turbine
classes into the repositories path that is defined in your zone.properties
file.
#2. Specify an initial parameter named "properties" (without the quotes)
with the pathname to the TurbineResources.properties file as its value.
This can be accomplished by placing the following line in your
<zone>.properties file:
servlet.Turbine.initArgs=properties=/path/to/TurbineResources.properties
----------------------------------------------------------------------------
---
-- Specific Servlet Engine Installation Instructions
----------------------------------------------------------------------------
---
----------------------------------------------------------------------------
---
INSTALLATION WITH TOMCAT
----------------------------------------------------------------------------
---
The following instructions assume that you have followed the above
instructions for either source compilation or release distribution. It
also assumes that you have working Tomcat installation which can be
found at http://jakarta.apache.org.
TOMCAT_HOME=/path/to/tomcat
#1. Put all necessary Turbine-related jars (Turbine, ECS, Village,
JNDI) into $TOMCAT_HOME/lib.
#2. Add the path to the jars to the existing Tomcat CLASSPATH found in
$TOMCAT_HOME/bin/tomcat.sh
#3. Make necessary adjustments to TurbineResources.properties and copy into
a location where Tomcat will be able to read this file. This is most
likely
1) $TOMCAT_HOME/conf
or
2) The default distribution of TOMCAT creates the docBase in the
directory webapps/ROOT. Place the .properties file there. Look
in tomcat's server.xml for this information.
Include the sample modules by changing the module.packages line to
module.packages=org.apache.turbine.samples,org.apache.turbine.modules
#4. Add the following xml to $TOMCAT_HOME/conf/web.xml. It
will be a child of the <web-app> element.
<servlet>
<servlet-name>Turbine</servlet-name>
<servlet-class>Turbine</servlet-class>
<init-param>
<param-name>properties</param-name>
<param-value>/path/to/$TOMCAT_HOME/conf/TurbineResources.properties</param-v
alue>
</init-param>
</servlet>
If your docBase is webapps/ROOT then you don't need to put a full path to
the .properties file.
#5. Restart Tomcat
----------------------------------------------------------------------------
---
-- TESTING YOUR INSTALLATION
----------------------------------------------------------------------------
---
The following examples assume your servlet zone is configured at
http://your.host.com/servlets. If this is not the case, please substitute
your
zone name for /servlets (Tomcat uses /servlet for its default servlet zone).
#1. Point your web browser at http://your.host.com/servlets/Turbine
#2. Login using username 'turbine' and password 'turbine'
#3. You should see a Welcome screen with basic request information.
If you have problems or receive exceptions when following these steps,
please
subscribe to the mailing list and ask for help. Be sure to include the
specific steps you followed, where the error occurred, and what the exact
text
of the error message is.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
