diff --git a/LDP/howto/docbook/MMBase-Inst-HOWTO/ApacheTomcat-600x420.png b/LDP/howto/docbook/MMBase-Inst-HOWTO/ApacheTomcat-600x420.png new file mode 100644 index 00000000..8b21e3ad Binary files /dev/null and b/LDP/howto/docbook/MMBase-Inst-HOWTO/ApacheTomcat-600x420.png differ diff --git a/LDP/howto/docbook/MMBase-Inst-HOWTO/CreativeCommons-SomeRightsReserved.gif b/LDP/howto/docbook/MMBase-Inst-HOWTO/CreativeCommons-SomeRightsReserved.gif new file mode 100644 index 00000000..0c018405 Binary files /dev/null and b/LDP/howto/docbook/MMBase-Inst-HOWTO/CreativeCommons-SomeRightsReserved.gif differ diff --git a/LDP/howto/docbook/MMBase-Inst-HOWTO/MMBase-600x415.png b/LDP/howto/docbook/MMBase-Inst-HOWTO/MMBase-600x415.png new file mode 100644 index 00000000..3b7d7ffe Binary files /dev/null and b/LDP/howto/docbook/MMBase-Inst-HOWTO/MMBase-600x415.png differ diff --git a/LDP/howto/docbook/MMBase-Inst-HOWTO/MMBase-Inst-HOWTO.xml b/LDP/howto/docbook/MMBase-Inst-HOWTO/MMBase-Inst-HOWTO.xml new file mode 100644 index 00000000..fc751e23 --- /dev/null +++ b/LDP/howto/docbook/MMBase-Inst-HOWTO/MMBase-Inst-HOWTO.xml @@ -0,0 +1,2316 @@ + + + + +
+ + + + + + <application class="software">MMBase</application> Installation HOWTO + + + Adrian + Offerman + +
+ tldp@NOSPAM.offerman.net +
+ + + + 2003, 2004 + Adrian Offerman + +December 20, 2003 + + + + 1.0 + 2004-02-02 + AO + Initial Release, reviewed by LDP. + + + + + This document describes the installation of the + MMBase + content management system + on a Red Hat Linux distribution, + using the Tomcat application + server, + and integrating it with MySQL + and Apache. + + + + + +This document describes the installation of the +MMBase content management system +on a Red Hat Linux distribution, +using the Tomcat application +server, +and integrating it with MySQL +and Apache. + + + +Version: 0.2.4, January 22, 2004. + + + +Author: Adrian Offerman + + + +The latest version of this document can be found at: + + http://www.offerman.net/MMBase-Installation-HOWTO/ + + + + + + +Feedback is welcome at: + + http://www.offerman.net/MMBase-Installation-HOWTO/feedback.html + + + + +For questions, check out the +MMBase website: + + http://www.mmbase.org/ + + + + +You can find the +MMBase documentation at: + + http://www.mmbase.org/docs/ + + + + +Good luck! + + + + +Introduction + + +>From the MMBase website +(www.mmbase.org): +
+ +MMBase +is a Web Content Management System +with strong multimedia features. +MMBase +has a large installed base in The Netherlands, +and is used by major Dutch broadcasters, publishers, educational institutes, +national and local governments. +MMBase +is written in Java, +it is Open Source Software (MPL) +and all standards used are as 'open' as possible. +The system can be used with all major operating systems, application servers +and databases. + +
+ + + +Unfortunately, the installation of +MMBase +is not well documented. +Furthermore, when searching the internet looking for installation clues +and trying out tips, +it turns out that the details of the installation have changed frequently. + + + +This document describes the installation of the +MMBase content management system +on a Red Hat Linux distribution, +using the Tomcat application +server, +and the integration with MySQL +and Apache. + + + +It is based on our own experience +and compiled to the benefit of the community. + + + +These are the ingredients we used to cook up this recipe ourselves: + + + +Red Hat 8.0 distribution +running a 2.4.20 kernel, +with Alan Cox 2 +and +EA/ACL +extensions. + + + + +Java 2 Software Developers Kit (SDK) +and Java 2 Run-time Engine (J2RE) +from the Blackdown Java 2 JDK version v1.4.1-01, + + + + +Apache Jakarta Tomcat 4.1.27, + + + + +ImageMagick 5.4.7-5, + + + + +MMBase 1.6.5 for JDK 1.4, + + + + +MySQL Connector/J 3.0.8. + + + + + + + + +Installation + + +Although we installed MMBase +on a kernel with the Alan Cox +and +EA/ACL +extensions, +these features are no prerequisites. + + + +We assume that you have already installed and configured +Apache +and MySQL +on your server. + + + + + +Installing <application class="software">Java</application> + + +Find yourself a mirror for the +BlackDown Java Development Kit +at: + + http://www.blackdown.org/java-linux/mirrors.html + + + + +There you can download the latest versions of the +J2 Software Development Kit (SDK) +and +Run-time Engine (RE). + + + +Make sure you pick out the right version for the +gcc library installed on your system. +You can find out the version currently installed by typing: + + + + + + +Installation instructions for the +Java Development Kit +are available as +INSTALL-j2sdk +and INSTALL-j2re. + + + +Make the binary distribution of the +SDK +executable +and extract in a new directory: + + + + + + +Change the ownership of the +J2SDK +directory +and make it available as +/usr/local/j2sdk/: + + + + + + +Do the same for the +RE: + + + + + + +Since we didn't install the +JDK +and RE +in our path, +we have to add the bin/ directories +to our $PATH environment variable. +To make sure the Java +distributions and classes can be found, +we set the $JAVA_HOME +and $CLASSPATH variables as well. + + + +For the Bourne shells, +create a file /etc/profile.d/java.sh: + + + + + + +Set its ownership and access rights: + + + + + + +Do the same for C shells, +by creating the file +/etc/profile.d/java.csh: + + + + + + +and setting its ownership and access rights: + + + + + + +Now the JDK +should be available to everyone on your system. + + + + + +You can test the Java engine +by typing: + + + + + + +or create a file Test.java: + + + + + + +and test the compiler: + + + + + + + + + + + +Installing <application class="software">Tomcat</application> + + +Download a binary distribution of +Tomcat +from the Apache Jakarta website: + + http://jakarta.apache.org/tomcat/ + + + + +If you don't want to run the +Tomcat daemon as +root, +create a new user/group tomcat +(first make sure that the +UID and GID +you use +are still available +by checking the files /etc/passwd +and /etc/group): + + + + + + + + +You really should not use the +root account +to run the Tomcat daemon; +we found out that this allows the +MMBase +admin user +to write backup dumps of his sites anywhere on the system. + + + + + +<TODO: better solution available?> + + + +Extract the Tomcat distribution +in a new directory: + + + + + + +Version 4.1.27 came with a hot-fix: + + + + + + +Change the ownership of the +Tomcat directory +and make it available as +/usr/local/tomcat/: + + + + + + +Open up the firewall for web access +to the Tomcat server +by adding to the file +/etc/sysconfig/iptables: + + + + + + +You need to reboot your system to make this rule effective +or restart the iptables firewall: + + + + + + + + +Since (for some odd reason) some network managers allow outgoing web +connections only to +TCP port 80, +there might be people around that cannot access your +Tomcat +(and MMBase) server +through port 8080. +Further below +we will explain how to install +a JK 2 mapping or a reverse proxy +in Apache, +so Tomcat +and MMBase +can be accessed through the +Apache web server +at port 80. +Apart from the port issue, +this has the advantage that you can use +Apache +to manage you SSL connections +and use your existing +Apache +logs and statistics facilities +for Tomcat +and MMBase as well. + + + +If you decide to use +Apache +as a front-end to your +Tomcat +and MMBase server, +there's no need to open up +port 8080 +in your firewall. + + + + + +To run Tomcat, +set the $CATALINA_HOME environment variable: + + + + + + +and fire it up: + + + + + + +Now you can access +Tomcat's home page through +(replace <hostname> with your hostname): + + :8080/ + ]]> + + + + +which should give you the Tomcat +welcome screen. + +600x420x256 + + + + + +To shutdown again: + + + + + + +Since we want to automate the starting up and shutting down of the +Tomcat server, +we create a file +/etc/rc.d/init.d/tomcat +to do this for us: + + + + + + +Set its ownership and access rights: + + + + + + +And add this init script to +chkconfig: + + + + + + + + + + +Replacing <application class="software">Tomcat</application>'s +default <acronym>JSP</acronym> compiler +<application class="software">Jasper</application> +with <acronym>IBM</acronym>'s +<application class="software">Jikes</application> compiler + + + +Since IBM's +Java compiler +Jikes +is performing better than +Tomcat's own +JSP compiler +Jasper, +it's recommended to install +Jikes instead. + + + +Download the sources of Jikes +from IBM's Research website: + + http://www.research.ibm.com/jikes/ + + + + +Extract and compile Jikes: + + + + + + +Check support for the option: + + + + + + +To have Jikes +output its error messages in a +Jasper compatible way, +add this $CATALINA_OPTS environment variable +to /etc/rc.d/init.d/tomcat: + + + + + + + + +If you get an error message saying +Jikes can not use +UTF8 encoding, +add the following option as well: + + + + + + + + +Make Jikes +your JSP compiler +for Tomcat +by adding to +/usr/local/tomcat/conf/web.xml: + + + compiler + jikes + + ]]> + + + + +Since entering the full path to +Jikes +in /usr/local/tomcat/conf/web.xml +doesn't seem to work, +make the jikes program available in your path: + + + + + + + + + + + + + +Installing <application class="software">ImageMagick</application> + + + +MMBase +uses ImageMagick's +convert tool +to build and convert its images. + + + +ImageMagick +is already part of the +Red Hat distribution. +Check its availability using: + + + + + + +If ImageMagick +is not available on your system, +install it +using up2date: + + + + + + +or download it from the Red Hat Network: + + https://rhn.redhat.com/ + + + + +and install it by hand: + + + + + + + + + +Installing <application class="software">MMBase</application> + + +Download the binary distribution of +MMBase +from: + + http://www.mmbase.org/ --> download + + + + +Make sure you pick out the right version for the +Java 2 JDK +installed on your system. +You can find out the version currently installed by typing: + + + + + + +Extract the binary distribution of +MMBase, +copy it into the +Tomcat directory, +and change the ownership of the +MMBase directory: + + + + + + +Replace the Tomcat +Xerces libraries +by those coming with MMBase: + + + + + + + + +If you will not be using an +Apache +JK 2 mapping or reverse proxy +(see further below) +as a front-end to your +MMBase server, +you can add to the file +/usr/local/tomcat/conf/server.xml: + + + + + + ]]> + + + + +This will allow you to access your +MMBase server +using +(replace <hostname> with your hostname): + + :8080/mmbase + ]]> + + + + +instead of: + + :8080/mmbase-webapp + ]]> + + + + + + +Check if the ImageMagick +convert tool +is in your path: + + + + + + +If not, add it to +/usr/local/tomcat/webapps/mmbase-webapp/WEB-INF/config/applications/Resources/builders/images.xml. +For example: + + /usr/bin/X11/convert + ]]> + + + + +Make sure that the directory +/usr/local/tomcat/webapps/mmbase-webapp/WEB-INF/config/builders/applications +is writable by the servlet engine user +(for auto-installing builders): + + + + + + + + + + +Connecting <application class="software">MMBase</application> +to <application class="software">MySQL</application> +using <systemitem class="library">MySQL Connector/J</systemitem> + + + +We can connect +MMBase +to our MySQL database server +using MySQL Connector/J. +This JDBC driver +for MySQL +can be downloaded from: + + http://www.mysql.com/downloads/api-jdbc.html + + + + +Copy the JDBC driver +to the MMBase +lib/ directory: + + + + + + +Make this your JDBC driver +for MMBase +by editing +/usr/local/tomcat/webapps/mmbase-webapp/WEB-INF/config/modules/jdbc.xml. +Substitute the database name +(mmbase), +user (mmuser) +and password (mmpass) +with the database settings you'd like +MMBase to use. + + jdbc:mysql://$HOST:$PORT/$DBM + mmuser + mmpass + org.mmbase.module.database.DatabaseSupportShim + mmbase + 20 + localhost + com.mysql.jdbc.Driver + 3306 + 256 + 30 + ]]> + + + + +Set the ownership and access rights of this configuration file. +Since it contains your database name, user name and password, +make sure other users can not read this file. + + + + + + +Now create the MySQL database +you've just defined for +MMBase: + + + + + + + + ; + USE ; + GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP ON .* TO + @'%' IDENTIFIED BY ''; + GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP ON .* TO + @localhost IDENTIFIED BY ''; + GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP ON .* TO + @localhost. IDENTIFIED BY ''; + # RH bug fix + GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP ON .* TO + @ IDENTIFIED BY ''; + flush privileges; + exit; + ]]> + + + + +Substitute the hostname (<hostname>) +and domain name (<domainname>) +with your own hostname and domain name, +and the database name (<mmbase>), +user (<mmuser>) +and password (<password>) +with the values you just entered in the JBDC driver configuration file. + + + + + +If you are already using quite some +MySQL connections +(for example for authentication by and as a back-end to your mail daemons +and Apache servers), +the MySQL server +might run out of connections (its maximum number defaults to 100). +Then Tomcat +could simply refuse to start or give an error message +when initiating the +MySQL connection pool, +or your IMAP +or POP servers will have +problems authenticating their clients. + + + +You can increase the maximum number of connections +to MySQL +by adding to the configuration file +/etc/my.cnf: + + + + + + + + + + + + +Configuring initial +<application class="software">MMBase</application> settings + + + +Here are some initial configuration settings +for MMBase. + + + +Change the default password +admin2k +for the administrator admin +by editing +/usr/local/tomcat/webapps/mmbase-webapp/WEB-INF/config/security/context/config.xml: + + + admin2k + + ]]> + + + + +Also, outcomment or remove the user +foo/bar. + + + +Since this file contains your administrators password, +make sure other users can not read it: + + + + + + +To use the MMBase +builder mmbaseuser +(using the mmbaseuser table +in your MySQL database) +for user authentication, +set the authentication class +in the configuration file +/usr/local/tomcat/webapps/mmbase-webapp/WEB-INF/config/security/security.xml +to: + + + ]]> + + + + +and set the authorization class to: + + + ]]> + + + + +In the same file change the shared secret used to communicate with remote +builders +(on other MMBase servers): + + yoursharedsecret + ]]> + + + + + + +You can set the language +for MMBase +by editing +/usr/local/tomcat/webapps/mmbase-webapp/WEB-INF/config/modules/mmbaseroot.xml: + + en + ]]> + + + + + + + + + +Running <application class="software">MMBase</application> + + +Now you are ready to start Tomcat: + + + + + + +and access your new MMBase server +through +(replace <hostname> with your hostname): + + :8080/mmbase-webapp/ + ]]> + + + + +If everything you just did worked out, +you should get the +MMBase welcome screen +where you can change the settings, look at the demos, and install the +samples. + +600x415x256 + + + + + +When asked for a login use the name +admin +and the password +you just set in the security configuration file +/usr/local/tomcat/webapps/mmbase-webapp/WEB-INF/config/security/context/config.xml. + + + + + +Tomcat +consumes far more CPU and memory resources +than Apache. +Make sure the dimensions of your +Tomcat/MMBase server system meet these requirements. + + + + + + + +Shutting down (or restarting) the +Tomcat server +in our case always left a last process running. +If you experience this same problem, +kill the process by hand before starting it up again: + + + + + + + + + + +You can save the original index.jsp file +by renaming it to mmbase.jsp: + + + + + + +This will allow you to always access the original MMBase home page through +(replace <hostname> with your hostname): + + :8080/mmbase-webapp/mmbase.jsp + ]]> + + + + + + +In case of any problems, +check the Tomcat +and MMBase log files +in the directory +/usr/local/tomcat/logs/ +for hints. + + + +>From here, we refer to the documentation +on the MMbase website +to complete your configuration +and start using MMBase: + + http://www.mmbase.org/docs/ + + + + + + + + + + +Connecting <application class="software">Apache</application> +and <application class="software">Tomcat</application> +using <systemitem class="library">mod_jk2</systemitem> + + + +Since (for some odd reason) some network managers allow outgoing web +connections only to TCP port 80, +there might be people around that cannot access your +Tomcat +(and MMBase) server +through port 8080. +You can install a JK 2 mapping or a reverse proxy +in Apache, +so Tomcat +and MMBase +can be accessed through the +Apache web server +at port 80. +Apart from the port issue, +this has the advantage that you can use +Apache +to manage you SSL connections +and use your existing +Apache +logs and statistics facilities +for Tomcat +and MMBase as well. + + + +Here we describe the installation and configuration of +the JK 2 Connector +connecting Apache +and Tomcat. +In this way, +Tomcat paths can be mapped +into Apache. + + + +>From the +JK 2 Connector +website +(http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/jk2.html): +
+ + +The JK 2 Connector +element represents +a Connector component that communicates +with a web connector via the AJP protocol. +This is used for cases where you wish +to invisibly integrate Tomcat 4 +into an existing (or new) +Apache installation, +and you want Apache to handle +the static content contained in the web application, +and/or utilize Apache's +SSL processing. +In many application environments, +this will result in better overall performance +than running your applications +under Tomcat stand-alone +using the +HTTP/1.1 Connector. +However, the only way to know for sure +whether it will provide better performance for your application +is to try it both ways. + + +
+ + + +If you will only be needing a simple configuration-- +typically a single Tomcat server +sitting on the same system as +your Apache server-- +Apache reverse proxies might be +an easier solution for you. +Although these are simpler in terms of the interconnection features, +reverse proxies provide more flexibility +in fiddling with your paths and other options. +The configuration of +Apache reverse proxies is +described in the next section. + + + +However, if you plan to build or grow to +a farm of several Tomcat servers +behind an Apache front-end +or build a high-performance system +deploying +the JK 2 Connector +is the way to go. + + + +Download the sources of +the JK 2 Connector +from the Apache Jakarta website: + + http://jakarta.apache.org/site/sourceindex.cgi + + + + +Extract and compile +the JK 2 Connector: + + + + + + +Make sure your $JAVA_HOME environment variable is set +and the Java binaries are +in your $PATH +or add this option to your ./configure command: + + + + + + +Copy the module files mod_jk2.so and +jkjni.so +to the modules/ directory +of Apache: + + + + + + +Copy the sample configuration file +workers2.properties +to the configuration directory +of Apache: + + + + + + +and adjust it to your own needs. + + + +Here is a simple configuration that should get you up and running: + + /jkstatus/*] + info=Display status information and checks the config file for changes. + group=status: + + [channel.socket:localhost:8009] + info=Ajp13 forwarding over socket + + # Define the worker + [ajp13:localhost:8009] + channel=channel.socket:localhost:8009 + + [uri:/mmbase-webapp/*] + info=MMBase + ]]> + + + + +Most of this configuration is pretty standard. +The last uri declaration +(replace <hostname> with your hostname) +is what this is all about; +it maps all client requests starting with +/mmbase-webapp/ +from Apache +to your Tomcat server. + + + + + +When we made a virtual host mapping, +somehow the general mappings no longer worked for this virtual host +(other virtual hosts on the same +IP address had no problem at all). +We had to explicitly add the general mappings for this virtual host +to make these work again. +A bug? +Or a consequence of the way +Apache +implements name based virtual hosts? + + + + + +So now, the same application you accessed +through Tomcat as +(replace <hostname> with your hostname): + + :8080/mmbase-webapp/ + ]]> + + + + +will be available through +Apache as: + + /mmbase-webapp/ + ]]> + + + + + + +Only name based virtual hosts are supported this way. +Make sure you add the virtual host name +(pointing to this very same (web) server) +to the /etc/hosts file +(replace <hostname> with your hostname): + + + ]]> + + + + +or things will not work +(running DNS is not sufficient here!). + + + + + +If your Apache installation +is serving only a single website, +you can leave out the hostname: + + + + + + +which will serve the +mapped /mmbase-webapp/ directory +on every address and site +of your Apache installation. + + + + + +Using +JK Connector +version 2, +all configuration settings will be in the +workers2.properties file. +Even though Tomcat +comes with its own +JK 2 configuration file +/usr/local/tomcat/conf/jk2.properties, +there's no need to edit this +as long as you stick with the standard +port 8009. + + + +If you do have to edit this file +(for example when changing the port), +make sure that you do it +when your Tomcat server +is not running; +the file is auto-edited +by Tomcat itself. + + + + + +After adding the mod_jk2 module +to your Apache configuration +(in the file +/etc/httpd/conf/httpd.conf +or in a new file jk2.conf +in the Apache +configuration directory +/etc/httpd/conf.d): + + + + + + + + + + + + +you can now restart Apache +and give your new entrance a try: +(replace <hostname> with your hostname): + + /mmbase-webapp/ + ]]> + + + + +To check the status of +the JK 2 Connector +(replace <hostname> with your hostname): + + /jkstatus/ + ]]> + + + + + + +You can reread the configuration in +/usr/local/apache/conf/workers2.properties +by (re)loading the JK Status page. +This allows you to add new mappings +without restarting Apache +or having it reload its configuration. +However, existing mappings can not be removed this way +and require Apache te reconfigure. + + + +Although it's also possible to place the JK 2 configurations +(in a slightly different form) +in your Apache configuration file, +this is a good reason to stick with the +workers2.properties setup. + + + + + + + +To protect access to the JK Status page, +add an authentication declaration +to the Apache configuration. +For example: + + + AuthType Basic + AuthName "JK 2 Connector Status" + AuthUserFile /etc/httpd/conf/users + AuthGroupFile /etc/httpd/conf/groups + Require group admin + + ]]> + + + + +This will prompt for a login from a user +from the admin group. + + + + + +In case of any problems, +check +the JK 2 Connector +log messages +that will be written to your Apache +error_log. + + + + + +In case the +JK 2 Connector +has difficulties connecting to +Tomcat, +check whether Tomcat is indeed +available on +port 8009: + + + + + + + + +Access requests mapping to Tomcat +will be logged in the access_log's +and error_log's +of Apache. + + + +For more information on the +workers2.properties configuration, +check the documentation at: + + http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebcom.html + + + + +There you will read about +setting up more (remote) +Tomcat workers, +grouping these together in load-balancing pools, +setting up RPC channels, +using Unix sockets, +using the +Java Native Interface (JNI) +to interconnect with +Tomcat directly (in-process), +setting up alternative loggers, +and optimizing your time-outs. + + + + + +Apache is far more efficient +than Tomcat +in serving ordinary content files. +You could have both the Apache +and Tomcat document directories +point to the same directory on your filesystem +and only forward requests for JSP pages +and Java Servlets. +For example (in workers2.conf): + + + + + + +However, now you need to protect +Tomcat's +WEB-INF/ directories +(and other directories and files you don't want visitors to have access to) +from being served by Apache. +For example (in Apache's +httpd.conf): + + + AllowOverride None + deny from all + + ]]> + + + + +Also, realize that a setup like this bypasses +any security constraints you may have configured +in the file +/usr/local/tomcat/webapps/examples/WEB-INF/web.xml. + + + + + +You can find more general information about +the JK 2 Connector +at: + + http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/ + + + + + + + + +Installing an <application class="software">Apache</application> +reverse proxy +as a front-end +to your <application class="software">MMBase</application> server + + + +Installing an Apache reverse proxy +is an easy alternative to the +JK 2 Connector +to use Apache as a front-end +to your Tomcat server. + + + +Add to your Apache +(virtual) server configuration +(replace <hostname> with your hostname): + + :8080/ + ProxyPassReverse /tomcat/ http://:8080/ + ProxyPass /mmbase/ http://:8080/mmbase-webapp/ + ProxyPassReverse /mmbase/ http://:8080/mmbase-webapp/ + ]]> + + + + +This allows you to access your +Tomcat server +as +(replace <hostname> with your hostname): + + /tomcat/ + ]]> + + + + +and your MMBase server as +(replace <hostname> with your hostname): + + /mmbase/ + ]]> + + + + + + + + +Installing more <application class="software">MMBase</application> servers +under the same <application class="software">Tomcat</application> server + + + +If you want to support +more instances of MMBase, +for example if you would like +to make MMBase +available to more or all of your users, +you can create several +MMBase installations +and have these all run under the same +Tomcat server. + + + +Install MMBase +in the home directory +of the user <user> +performing all steps before: + + + +create a directory mmbase/ +in the users home directory, + + + + +copy all MMBase files +into the directory +/home/<user>/mmbase/, + + + + +build the directory structure and configuration files +in the very same way we did before, + + + + +remove the Xerces libraries +in MMBase +(after you have copied these +from MMBase +to Tomcat +the first time), + + + + +install the MySQL +JDBC driver +and create a new MySQL database +for this user. + + + + + + +Make sure both the user +and the Tomcat server +have access to the +MMBase installation: + + :tomcat /home//mmbase/ + ]]> + + + + +Make sure that the directory +/home/<user>/mmbase/WEB-INF/config/builders/applications +is writable and accessible by the servlet engine user +(for auto-installing builders): + + /mmbase/WEB-INF/config/builders/applications + chmod 750 /home//mmbase/WEB-INF/config/builders/ + chmod 750 /home//mmbase/WEB-INF/config/ + chmod 750 /home//mmbase/WEB-INF/ + chmod 750 /home//mmbase/ + ]]> + + + + +Now the home directory of this user has to be accessible +to the Tomcat server +as well. +You can change the group owner of the users home directory +to the tomcat user group: + + / + ]]> + + + + +Or, if you don't want this, +use the Access Control Lists (ACL's) +to accomplish the same: + + / + ]]> + + + + +Finally, link the new +MMBase installation +to the Tomcat server: + + /mmbase /usr/local/tomcat/webapps/mmbase- + ]]> + + + + +and restart Tomcat: + + + + + + +which will make +this users MMBase installation +available through: + + :8080/mmbase-/ + ]]> + + + + +Again, you can set up a JK 2 mapping or a reverse proxy +in Apache +like we did before. + + + + + + +Acknowledgements + + +This document is a follow-up on the +MMBase Mini-HOWTO: +Installation on Debian Woody, +by Casper Joost Eyckelhof, University of Twente, The Netherlands. + + + + + + +Contributers + + + + + + +André van Elst, +Finalist, +The Netherlands. + + + + + + + + + +Revision history + + + + + + +Version 0.2.4, January 22, 2004: Creative Commons copyright license, minor additions and corrections, + + + + +version 0.2.3, December 26, 2003: minor additions and corrections, + + + + +version 0.2.2, December 20, 2003: copyright adjusted, + + + + +version 0.2.1, December 18, 2003: minor corrections, + + + + +version 0.2, December 15, 2003: JK 2 Connector setup added, + + + + +version 0.1, December 10, 2003: initial draft. + + + + + + + + + +Disclaimer + + +This document is provided as is, +without any expressed or implied warranties. +Use the ideas, concepts, scripts, examples, helping hands and other +information at your own risk. + + + +The specific products and their respective manufacturers are not to be taken +as endorsements of, nor commercials for, the manufacturer. + + + + + + +Copyright + + +Compiled, Copyright 2003, 2004, by +Adrian Offerman. + + + + +This document is licensed under the +Creative Commons Attribution-NonCommercial-ShareAlike copyright license. + + + +This allows you to copy, distribute, display, and print this work, +and make derivative works, +under the conditions that you give the original author credit, +you do not use this work for commercial purposes, +and if you alter, transform, or build upon this work, +you may distribute the resulting work only under a license +identical to this one. +For any reuse or distribution, +you must make clear to others the license terms of this work. +Any of these conditions can be waived if you get permission from the author. +Your fair use and other rights are in no way affected by the above. + + + + + +