Return-Path: Delivered-To: apmail-maven-archiva-commits-archive@locus.apache.org Received: (qmail 16112 invoked from network); 14 Jan 2008 04:30:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jan 2008 04:30:36 -0000 Received: (qmail 56170 invoked by uid 500); 14 Jan 2008 04:30:26 -0000 Delivered-To: apmail-maven-archiva-commits-archive@maven.apache.org Received: (qmail 56128 invoked by uid 500); 14 Jan 2008 04:30:26 -0000 Mailing-List: contact archiva-commits-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: archiva-dev@maven.apache.org Delivered-To: mailing list archiva-commits@maven.apache.org Received: (qmail 56116 invoked by uid 99); 14 Jan 2008 04:30:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Jan 2008 20:30:26 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2008 04:30:09 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 825D11A9832; Sun, 13 Jan 2008 20:30:15 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r611707 - /maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt Date: Mon, 14 Jan 2008 04:30:15 -0000 To: archiva-commits@maven.apache.org From: oching@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20080114043015.825D11A9832@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: oching Date: Sun Jan 13 20:30:14 2008 New Revision: 611707 URL: http://svn.apache.org/viewvc?rev=611707&view=rev Log: [MRM-646] -added instructions for deploying archiva to tomcat 6.0.x -mail-1.4.jar should also be added to common/lib Modified: maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt Modified: maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt URL: http://svn.apache.org/viewvc/maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt?rev=611707&r1=611706&r2=611707&view=diff ============================================================================== --- maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt (original) +++ maven/archiva/trunk/archiva-docs/src/site/apt/adminguide/webapp.apt Sun Jan 13 20:30:14 2008 @@ -7,7 +7,12 @@ ~~TODO: link to wiki location for other application servers Archiva can be deployed as a web application into any Java EE application server. This document will show an - example of doing so with Tomcat 5.5. + example of doing so with Tomcat 5.5 and Tomcat 6.0.x. + + <>: When you first start Archiva, you will see an Exception that schema SA does not exist - however it doesn't + cause a problem. If you use a username other than 'sa', such as 'archiva', then you seem to get the same error but + Tomcat fails to start the context and you have to shutdown and restart again. + To deploy Archiva on Tomcat 5.5 @@ -40,17 +45,27 @@ +-------------------------------------------------------------------------+ - * <>: Tomcat 5.5.20 and 5.5.23 are missing MailSessionFactory and a + * Install <<>> and <<>> into the Tomcat <<>>. This is required since the data sources are + instantiated before the web application. + + <>: Tomcat 5.5.20 and 5.5.23 are missing MailSessionFactory and a few other classes. JNDI mail sessions will work. Use Tomcat 5.5.17 instead, or see {{{http://issues.apache.org/bugzilla/show_bug.cgi?id=40668} Bug 40668}} for a workaround. - * Install <<>> into the Tomcat <<>>. This is required since the data sources are - instantiated before the web application. +To deploy Archiva on Tomcat 6.0.x: + + * Do the same steps specified above when deploying to Tomcat 5.5. - When you first start Archiva, you will see an Exception that schema SA does not exist - however it doesn't - cause a problem. If you use a username other than 'sa', such as 'archiva', then you seem to get the same error but - Tomcat fails to start the context and you have to shutdown and restart again. + * The ${appserver.base} java property is used by the Archiva internal logging configuration to determine where to output its logs to. + It is important to define this property either in the $CATALINA_OPTS system environment variable (if Tomcat is being launched via the + command line) or the service properties (if being launched as a service or daemon). The format typically expected is + -Dappserver.base=. In this example, we'll put the logs in Tomcat's <<>> directory so we need to set appserver.base + property to where Tomcat is installed: + ++-----------+ +export CATALINA_OPTS="-Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME" ++-----------+ Archiva Configuration @@ -68,4 +83,4 @@ Configuring and Running Archiva Once Archiva is running, it is configured in the same way as the standalone instance. See the {{{../quick-start.html#Setting%20up%20your%20Archiva%20instance} quick start}} guide for more information. - + \ No newline at end of file