You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by vg...@apache.org on 2002/03/02 05:56:42 UTC
cvs commit: xml-cocoon2/src/documentation/xdocs/installing index.xml
vgritsenko 02/03/01 20:56:42
Modified: src/documentation/xdocs faq.xml
src/documentation/xdocs/installing index.xml
Log:
Update installation guide: addressed JDK1.4, PJA, WebLogic 6.0 installation
issues. Added patch from jls.apache@doppke.com (James Scott) with JBoss 2.4.4
instructions.
Revision Changes Path
1.6 +4 -0 xml-cocoon2/src/documentation/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/faq.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- faq.xml 17 Feb 2002 05:45:25 -0000 1.5
+++ faq.xml 2 Mar 2002 04:56:42 -0000 1.6
@@ -617,6 +617,10 @@
$> $TOMCAT_HOME/bin/startup.sh -f server.xml
]]>
</source>
+ <p>
+ Another solution is to use PJA library. Read 'Linux/Headless/Batik'
+ section in the <link href="installing/index.html">Cocoon installation guide</link>.
+ </p>
</answer>
</faq>
<faq>
1.9 +255 -132 xml-cocoon2/src/documentation/xdocs/installing/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/installing/index.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- index.xml 18 Feb 2002 09:25:16 -0000 1.8
+++ index.xml 2 Mar 2002 04:56:42 -0000 1.9
@@ -16,25 +16,24 @@
</header>
<body>
-
<s1 title="System Requirements">
<p>
Apache Cocoon requires the following systems to be already installed in your system:
</p>
-
+
<p><strong>Java Virtual Machine</strong>
A Java 1.2 or later compatible virtual machine must be present for both
command line and servlet type usage of Apache Cocoon. Note that all servlet engines
require a JVM to run so if you are already using servlets you already have
one installed.
</p>
-
+
<p><strong>Servlet Engine</strong>
A Servlet 2.2 compliant servlet engine must be present in order to support
servlet operation and dynamic request handling. Note that this requirement
is optional for command line operation.
</p>
-
+
<p>If you don't have a servlet engine installed, well, stop right here and
go to the Apache Tomcat project
<link href="http://jakarta.apache.org/tomcat/">http://jakarta.apache.org/tomcat/</link>
@@ -44,9 +43,9 @@
<s1 title="Getting Apache Cocoon">
<p>
You have three choices for getting Cocoon: you can either download
- a stable relese, or you can download development snapshot, or you can
+ a stable relese, or you can download development snapshot, or you can
get the latest development version directly from the cvs repository.
- </p>
+ </p>
<s2 title="Download a distribution">
<p>
You can simply download the latest official release from the
@@ -99,7 +98,7 @@
<li>Enter "cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login".</li>
<li>When asked for the password: answer "anoncvs".</li>
<li>Enter "cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic -z3 checkout
- -r HEAD xml-cocoon2". This will create a directory called "xml-cocoon2" where the
+ -r HEAD xml-cocoon2". This will create a directory called "xml-cocoon2" where the
Cocoon2 source will be stored.</li>
<li>Wait until cvs has finished.</li>
<li>The Cocoon source is now on your harddrive.</li>
@@ -110,10 +109,8 @@
</s2>
</s1>
- <s1 title="Building Cocoon">
-
+ <s1 title="Building Cocoon">
<s2 title="Set JAVA_HOME environment variable">
-
<p>Set the JAVA_HOME environment variable to point to the root directory of
the Java Development Kit installed on your machine. To do this simply type:</p>
@@ -123,10 +120,27 @@
</source>
<p>Your mileage may vary, but you know how to setup environments, right?</p>
+ </s2>
+ <s2 title="Java 1.4 configuration">
+ <p>Cocoon requires more recent versions of the Xerces and Xalan libraries
+ than those shipped with j2se 1.4. To override bundled libraries, follow
+ these steps:
+ </p>
+ <ol>
+ <li>
+ Create <code>%JAVA_HOME%\jre\lib\endorsed</code> directory.
+ </li>
+ <li>
+ Copy <code>xerces-XXX.jar</code>, <code>xalan-XXX.jar</code>,
+ and the <code>xml-apis.jar</code> from the
+ <code>xml-cocoon2\lib\core\</code> to the
+ <code>%JAVA_HOME%\jre\lib\endorsed\</code> directory.
+ </li>
+ </ol>
</s2>
-<!--
+<!-- TODO: Replacing HSQLDB with other SQL DB
<s2 title="Making the sql examples work out of the box">
<p>
The sample web application delivered with Cocoon contains some
@@ -151,9 +165,9 @@
</s2>
-->
- <s2 title="Adding additional components">
+ <s2 title="Adding optional components">
<p>
- Some of the components delivered with Cocoon required additional libraries,
+ Some of the components delivered with Cocoon require additional libraries,
e.g. the Php generator or the FOP serializer (for more information about
these components, refer to their documentation).
</p>
@@ -165,51 +179,65 @@
</p>
<p>
A library/package is available to the build process when it is located
- in the <code>./lib</code> directory.
+ in the <code>./lib/optional</code> directory.
</p>
<p>
The following table contains a list of the optional components,
their needed libraries and if they are already included or not.
</p>
- <table>
- <tr>
- <th>Component</th>
- <th>Required Library</th>
- <th>Library Included</th>
- </tr>
- <tr>
- <td>HTML Generator</td>
- <td><link href="http://sourceforge.net/projects/jtidy">JTidy</link></td>
- <td>Yes</td>
- </tr>
- <tr>
- <td>Php Generator</td>
- <td><link href="http://www.php.net">Php Servlet</link></td>
- <td>No</td>
- </tr>
- <tr>
- <td>XT Transformer</td>
- <td><link href="http://www.jclark.com/xml/xt.html">XT Processor</link></td>
- <td>Yes</td>
- </tr>
- <tr>
- <td>LDAP Transformer</td>
- <td><link href="http://java.sun.com/products/jndi">JNDI</link></td>
- <td>No</td>
- </tr>
- <tr>
- <td>PDF Serializer</td>
- <td><link href="http://xml.apache.org/fop/index.html">FOP</link></td>
- <td>Yes</td>
- </tr>
- </table>
+ <!-- TODO: Update -->
+ <table>
+ <tr>
+ <th>Component</th>
+ <th>Required Library</th>
+ <th>Library Included</th>
+ </tr>
+ <tr>
+ <td>HTML Generator</td>
+ <td><link href="http://sourceforge.net/projects/jtidy">JTidy</link></td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td>Php Generator</td>
+ <td><link href="http://www.php.net">Php Servlet</link></td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>XT Transformer</td>
+ <td><link href="http://www.jclark.com/xml/xt.html">XT Processor</link></td>
+ <td>Yes</td>
+ </tr>
+ <tr>
+ <td>LDAP Transformer</td>
+ <td><link href="http://java.sun.com/products/jndi">JNDI</link></td>
+ <td>No</td>
+ </tr>
+ <tr>
+ <td>PDF Serializer</td>
+ <td><link href="http://xml.apache.org/fop/index.html">FOP</link></td>
+ <td>Yes</td>
+ </tr>
+ </table>
<p><strong>Note:</strong> If you added a library/package, you
need to rebuild Cocoon as described in 'Create the Cocoon WAR package'.
</p>
</s2>
- <s2 title="Create the Cocoon WAR package">
+ <s2 title="Cleanup previous files">
+ <p>
+ If you perform Cocoon upgrade, it is advised to cleanup build and working
+ Cocoon directory before building and deploying new version. To cleanup build
+ directory, simply type:
+ </p>
+
+ <source>
+[unix] ./build.sh clean
+[win32] .\build.bat clean
+ </source>
+
+ </s2>
+ <s2 title="Create the Cocoon WAR package">
<p>To do this you simply have to type:</p>
<source>
@@ -219,7 +247,6 @@
<p>this will create the "cocoon.war" file in the
'./build/cocoon' directory.</p>
-
</s2>
</s1>
@@ -230,7 +257,7 @@
care of installing it when restarted.</p>
<s2 title="Installing on Tomcat 3.X">
- <note>Cocoon requires Tomcat version 3.2 or greater. It wouldn't work
+ <note>Cocoon requires Tomcat version 3.2 or greater. It wouldn't work
with Tomcat 3.1.X</note>
<p>Tomcat currently uses a different version of the XML parser
@@ -316,77 +343,102 @@
</ol>
<s3 title="Linux/Headless/Batik">
- <p>If you are using unix with the sun jdk, it's awt implementation requires you to use X
- even if you aren't actually displaying anything. One simple solution is to use a different
- implementation of the awt.</p>
+ <p>If you are using unix with the Sun JDK, it's awt implementation requires you to use X
+ even if you aren't actually displaying anything. One simple solution is to use a different
+ implementation of the awt.</p>
<ol>
- <li>From www.eteks.com you can get an awt replacement that doesn't need X:
- <link href="http://www.eteks.com/pja/en/">http://www.eteks.com/pja/en</link>.</li>
-
- <li>Unpack the jars into a place where your jdk will be able to use them--
- $JAVAHOME/jre/classes works for j2sdk1.3</li>
+ <li>From www.eteks.com you can get an awt replacement that doesn't need X:
+ <link href="http://www.eteks.com/pja/en/">http://www.eteks.com/pja/en/</link>.</li>
- <li>Then add the following to your Tomcat startup script
- (using CATALINA_OPTS if it is 4.x, TOMCAT_OPTS if it is 3.x)
- </li>
+ <li>Then add the following to your Tomcat startup script
+ (using CATALINA_OPTS if it is 4.x, TOMCAT_OPTS if it is 3.x):
+ </li>
</ol>
<source>
-export CATALINA_OPTS='-Dawt.toolkit=com.eteks.awt.PJAToolkit \
- -Djava.awt.graphicsenv=com.eteks.java2d.PJAGraphicsEnvironment \
- -Djava.awt.fonts=/usr/local/jdk/jre/lib/fonts/'
+export CATALINA_OPTS='-Xbootclasspath/a:/path/to/pja.jar \
+ -Dawt.toolkit=com.eteks.awt.PJAToolkit \
+ -Djava.awt.graphicsenv=com.eteks.java2d.PJAGraphicsEnvironment \
+ -Djava.awt.fonts=/usr/local/jdk/jre/lib/fonts/'
</source>
<p><strong>(Re)start Tomcat and enjoy!</strong></p>
</s3>
</s2>
<s2 title="Installing on BEA Weblogic 6.0">
-
- <p>This installs Cocoon using the cocoon.war file.
- This was successfully installed under Windows 2000.
- Unix users will need to adjust appropriately. If you haven't done so already,
- build a domain and a server. In this discussion, the name of the domain
- is 'mydomain' and the name of the server is 'myserver'.
- These are the BEA default names.
+ <p>This installs Cocoon using the cocoon.war file.
+ This was successfully installed under Windows 2000 with WebLogic 6.0sp2.
+ Unix users will need to adjust appropriately. If you haven't done so already,
+ build a domain and a server. In this discussion, the name of the domain
+ is 'mydomain', the name of the server is 'myserver', and WebLogic installation
+ directory is <code>c:\bea\wlserver6.0sp2\</code>. These are the BEA defaults.
</p>
<ol>
- <li>Copy <code>cocoon.war</code> into <code>c:\bea\wlserver6.0sp1\config\mydomain\applications</code></li>
- <li>Create a new directory named <code>ext</code> under <code>c:\bea\jdk130\jre\lib</code></li>
- <li>Copy the <code>xerces-XXX.jar</code> JAR file from <code>xml-cocoon2/lib</code> to
- <code>c:\bea\jdk130\jre\lib</code> directory
+ <li>Compile and build Cocoon. Launch <code>build compile</code>,
+ <code>build -Dinclude.webapp.libs=yes webapp</code>.
+ </li>
+ <li>You should have a webapp directory in
+ <code>xml-cocoon2\build\cocoon\webapp</code>.
</li>
<li>
- Run weblogic using <code>startWebLogic.cmd</code> file in <code>c:\bea\wlserver6.0sp1\config\mydomain</code> directory
+ Copy Cocoon webapp directory into the <code>c:\bea\wlserver6.0sp2\config\mydomain\applications\</code>
+ directory of your WebLogic server.
</li>
<li>
- Using a browser, link to your web site's cocoon page:
- <br/>
- http://<your machine name>:<port number>/cocoon/
- <br/>
- (Don't forget the final / in the link.)
+ Copy the <code>xerces-XXX.jar</code> and <code>xml-apis.jar</code> JAR files from the
+ <code>xml-cocoon2\lib\core\</code> to the directory of your choice, say <code>c:\bea\</code>.
</li>
-
<li>
- Congratulations! (hopefully) you should see the Cocoon welcome page.
+ Add to the config.xml of the WebLogic server following snippet:
+ </li>
+ </ol>
+<source><![CDATA[
+<Application Deployed="true" Name="Cocoon"
+ Path="./config/mydomain/applications">
+ <WebAppComponent Name="cocoon"
+ Targets="myserver"
+ URI="cocoon"/>
+</Application>
+]]></source>
+ <ol>
+ <li>
+ Edit <code>c:\bea\wlserver6.0sp2\config\mydomain\startWebLogic.cmd</code> file,
+ add xerces and xml-apis JAR files to the classpath:
+ </li>
+ </ol>
+<source>
+set CLASSPATH=c:\bea\xerces-XXX.jar;c:\bea\xml-apis.jar
+set CLASSPATH=%CLASSPATH%;.;.\lib\weblogic_sp.jar
+set CLASSPATH=%CLASSPATH%;.\lib\weblogic.jar
+</source>
+ <ol>
+ <li>
+ Start WebLogic server using <code>startWebLogic.cmd</code>.
+ </li>
+ <li>
+ Using a browser, you might want to check WebLogic configuration using console:
+ <link href="http://localhost:7001/console/">http://localhost:7001/console/</link>.
+ </li>
+ <li>
+ Access cocoon page:
+ <link href="http://localhost:7001/cocoon/">http://localhost:7001/cocoon/</link>
+ (Don't forget the final / in the link.)
+ </li>
+ <li>
+ Congratulations! (hopefully) you should see the Cocoon welcome page.
</li>
</ol>
- <note>If you have problems with starting up Cocoon, you can modify the CLASSPATH in the .cmd files and
- ensure that xerces-XXX.jar is picked up before any other jars.
- <br/>
- <code>set CLASSPATH=.;c:\bea\jdk130\jre\lib\xerces-XXX.jar;.\lib\weblogic_sp.jar;.\lib\weblogic.jar</code>
- <br/>
- </note>
</s2>
-
- <s2 title="Installing on BEA WLS6.1sp1, WLS6.1sp2">
-
+<!-- FIXME: WebLogic 6.1sp2 hangs trying to create sitemap
+ <s2 title="Installing on BEA WebLogic 6.1sp1, 6.1sp2">
+
<p>This section describes installing Cocoon in a "directory configuration".
This was successfully installed under Windows 2000.
- Unix users will need to adjust appropriately. If you haven't done so already,
- build a domain and a server. In this discussion, the name of the domain
- is 'mydomain' and the name of the server is 'myserver'.
+ Unix users will need to adjust appropriately. If you haven't done so already,
+ build a domain and a server. In this discussion, the name of the domain
+ is 'mydomain' and the name of the server is 'myserver'.
These are the BEA default names; you may want to download
<link href="http://www.weblogic.com">WLS6.1</link>.
</p>
@@ -394,7 +446,7 @@
<li>Compile and build Cocoon. Launch <code>build compile</code>,
<code>build -Dinclude.webapp.libs webapp webapp-local</code>.
</li>
- <li>You should have a webapplication directory in
+ <li>You should have a webapplication directory in
<code>{cocoon-dir}/build/cocoon/webapp</code>.
</li>
<li>Modify <code>{cocoon-dir}/build/cocoon/webapp/cocoon.xconf</code>.
@@ -404,17 +456,17 @@
</li>
<li>
Configure your WebLogic server, launch your WebLogic console.
- Use <code>Configure a new Web Application...</code>,
- and enter in field "Path URI" full path name of Cocoon
+ Use <code>Configure a new Web Application...</code>,
+ and enter in field "Path URI" full path name of Cocoon
webapplication directory,
- like <code>d:\xml-cocoon2\build\cocoon\webapp</code>,
- enter in field "Name" the servlet name
- eg. <code>cocoon</code>.
- Check the "Deployed" checkbox, and click "Apply".
+ like <code>d:\xml-cocoon2\build\cocoon\webapp</code>,
+ enter in field "Name" the servlet name
+ eg. <code>cocoon</code>.
+ Check the "Deployed" checkbox, and click "Apply".
At last be sure that you assign the servlet to a target server.
</li>
<li>
- You might try to avoid the configuration step by copying
+ You might try to avoid the configuration step by copying
the whole Cocoon webapp directory into the <code>applications</code>
directory of your WLS6.1 server. In this case you might have
to restart your WLS6.1 server in order to activate Cococoon servlet in WLS 6.1.
@@ -434,24 +486,24 @@
</li>
</ol>
<p>
- Snippet of modified <code>cocoon.xconf</code>. The effect of this
+ Snippet of modified <code>cocoon.xconf</code>. The effect of this
change is that Cocoon will not try to use a TRAX XSLT transformer factory.
Using the TRAX XSLT transformer factory under WLS6.1sp1 lead to empty
- <code>sitemap_xmap.java</code> files, indicating that the XSLT processor
+ <code>sitemap_xmap.java</code> files, indicating that the XSLT processor
used did not work properly. WLS6.1 has a built-in TRAX XSLT which seems
not to work properly for Cocoon.
</p>
<p>
The code snippet below configures the xslt processor to use the XALAN transformer
factory explictly.
- Forcing Cocoon using Xalan XSLT lead to correct <code>sitemap_xmap.java</code>
+ Forcing Cocoon using Xalan XSLT lead to correct <code>sitemap_xmap.java</code>
files.
</p>
<source><![CDATA[
-<xslt-processor class="org.apache.cocoon.components.xslt.XSLTProcessorImpl"
+<xslt-processor class="org.apache.cocoon.components.xslt.XSLTProcessorImpl"
logger="root.xslt">
<parameter name="use-store" value="true"/>
- <parameter name="transformer-factory"
+ <parameter name="transformer-factory"
value="org.apache.xalan.processor.TransformerFactoryImpl"/>
</xslt-processor>]]></source>
<note>
@@ -460,7 +512,7 @@
All changes described above are locally to the Cocoon webapplication.
</note>
</s2>
-
+-->
<s2 title="Installing on ServletExec 3.1 (In Process with IIS)">
<p>This installs Cocoon in a "war" configuration. This was successfully
@@ -474,7 +526,7 @@
<li>Install ServletExec (default paths will be used throughout), but
don't start it.</li>
<li>Build Cocoon's war file (include lib's)</li>
- <li>Copy <em>cocoon.war</em> into
+ <li>Copy <em>cocoon.war</em> into
<em>C:\Program Files\New Atlanta\ServletExec ISAPI\webapps\default</em>,
creating the directory default if required.</li>
<li>Start IIS.</li>
@@ -484,12 +536,83 @@
</li>
</ol>
</s2>
+ <s2 title="Installing on JBoss 2.4.4 with Tomcat 4.0.1 (Catalina)">
+ <p>
+ This section describes the deployment of the Cocoon sample WAR with
+ the JBoss-2.4.4_Tomcat-4.0.1 package. It assumes that you built Cocoon as
+ described above or downloaded the binary Cocoon distribution. All steps have
+ been tested with a fresh JBoss 2.4.4 installation on Linux and Windows 2000.
+ </p>
+ <note>The JBoss/Tomcat bundle is available from the
+ <link href="http://sourceforge.net/projects/jboss/">JBoss project page</link>
+ </note>
+ <p>
+ The JBoss/Tomcat package has the following directory structure
+ </p>
+<source>
+[path]/JBoss-2.4.4_Tomcat-4.0.1/jboss
+[path]/JBoss-2.4.4_Tomcat-4.0.1/catalina
+</source>
+ <p>
+ Subsequently,
+ </p>
+ <ul>
+ <li><code>jboss</code> denotes the <code>JBoss-2.4.4_Tomcat-4.0.1/jboss</code> directory
+ </li>
+ <li><code>catalina</code> is short for <code>JBoss-2.4.4_Tomcat-4.0.1/catalina</code></li>
+ <li>and <code>cocoon</code> is the base directory of your Cocoon distribution or CVS checkout.</li>
+ </ul>
+
+ <p>In order to get Cocoon running you have to install Xerces as default XML parser for JBoss.</p>
+ <ul>
+ <li>Stop JBoss if it is running.</li>
+ <li>Remove the following files from the <code>jboss/lib</code> directory
+ <ul>
+ <li>crimson.jar</li>
+ <li>jaxp.jar</li>
+ </ul>
+ </li>
+ <li>Copy <code>xml-apis.jar</code> from <code>cocoon/lib</code> to <code>jboss/lib</code></li>
+ <li>Change <code>jboss/bin/run.sh</code></li>
+ </ul>
+<source>
+[...]
+# Add the XML parser jar and set the JAXP factory names
+# Crimson parser JAXP setup(default)
+<strong># Change it to Xerces for C2</strong>
+JBOSS_CLASSPATH=$JBOSS_CLASSPATH:<strong>../lib/xml-apis.jar</strong>
+<strong># Remove the following two lines</strong>
+JAXP=-Djavax.xml.parsers.DocumentBuilderFactory=\
+ org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
+JAXP="$JAXP -Djavax.xml.parsers.SAXParserFactory=\
+ org.apache.crimson.jaxp.SAXParserFactoryImpl"
+[...]
+</source>
+ <note>Windows users have to change <code>run.bat</code> accordingly.
+ </note>
+ <ul>
+ <li>Start JBoss with <code>run_with_catalina.sh</code> or <code>run_with_catalina.bat</code></li>
+ <li>Copy <code>cocoon/build/cocoon/cocoon.war</code> to <code>jboss/deploy</code></li>
+ <li>Check the server log to make sure that <code>J2EE application: [...]/cocoon.war is deployed.</code></li>
+ <li>Open the Cocoon welcome page (http://localhost:8080/cocoon/)</li>
+ <li>You should see the Cocoon welcome page.</li>
+ </ul>
+ <note>As both JBoss and Cocoon ship with a Hypersonic database installed,
+ these two conflict and you won't be able to use Cocoon database (SQL) samples.
+ Then again, you probably use JBoss for EJB persistence anyway, so this shouldn't
+ bother you too much ;-)
+ </note>
+ </s2>
+
<s2 title="Installing on JBoss 2.2.2 with Tomcat 3.2.2">
- <p>This section describes the deployment of the Cocoon sample WAR with
- the JBoss 2.2.2/Tomcat-3.2.2 package. It assumes that you built Cocoon as described above. All steps have been tested with a fresh JBoss 2.2.2 installation on Linux and Windows ME(sic).</p>
- <note>The JBoss/Tomcat bundle is available from the <link href="http://sourceforge.net/projects/jboss/">JBoss project page</link></note>
- <p>The JBoss/Tomcat package has the following directory
- structure</p>
+ <p>This section describes the deployment of the Cocoon sample WAR with
+ the JBoss 2.2.2/Tomcat-3.2.2 package. It assumes that you built Cocoon as described above.
+ All steps have been tested with a fresh JBoss 2.2.2 installation on Linux and Windows ME(sic).</p>
+ <note>The JBoss/Tomcat bundle is available from the
+ <link href="http://sourceforge.net/projects/jboss/">JBoss project page</link>
+ </note>
+
+ <p>The JBoss/Tomcat package has the following directory structure</p>
<source>
[path]/JBoss-2.2.2_Tomcat-3.2.2/jboss
[path]/JBoss-2.2.2_Tomcat-3.2.2/tomcat
@@ -507,7 +630,7 @@
<li>xml.jar</li>
</ul>
</li>
- <li>Remove the following files from the <code>tomcat/lib</code>
+ <li>Remove the following files from the <code>tomcat/lib</code>
directory
<ul>
<li>jaxp.jar</li>
@@ -546,9 +669,9 @@
</s2>
<s2 title="Installing on Resin 2.0.x">
<p>
- This section describes the deployment of the Cocoon sample WAR with Resin 2.0.x.
- It assumes that you built Cocoon as described above. All steps have been tested
- with a fresh Resin 2.0.0, 2.0.1 and 2.0.4 installations (the package is available from
+ This section describes the deployment of the Cocoon sample WAR with Resin 2.0.x.
+ It assumes that you built Cocoon as described above. All steps have been tested
+ with a fresh Resin 2.0.0, 2.0.1 and 2.0.4 installations (the package is available from
<link href="http://www.caucho.com/download/">Resin's download page</link>)
</p>
<p>After unpacking the Resin package you get the following directory structure</p>
@@ -569,7 +692,7 @@
<li>sax.jar</li>
</ul>
</li>
- <li>Copy the <code>xerces-XXX.jar</code> JAR file from <code>xml-cocoon2/lib</code> to
+ <li>Copy the <code>xerces-XXX.jar</code> JAR file from <code>xml-cocoon2/lib</code> to
<code>resin-2.0.x/lib</code> directory</li>
</ul>
</li>
@@ -590,22 +713,22 @@
<p>HP-AS is J2EE application server available from the Hewlett-Packard website.
<link href="http://www.hpmiddleware.com/download">Download and install HP-AS 8.X</link>
</p>
- <note>Cocoon cannot be deployed as a .war file in HP-AS.
+ <note>Cocoon cannot be deployed as a .war file in HP-AS.
Use the following steps to deploy cocoon.war:
</note>
<ol>
- <li>Extract the <code>cocoon.war</code> file to some directory, using <code>WinZIP</code>
+ <li>Extract the <code>cocoon.war</code> file to some directory, using <code>WinZIP</code>
or a similar utility to extract the files.</li>
<li>To run HP-AS, go to<strong><code>( Start | Programs | HP Middleware | HP Application Server | System Console).</code></strong>
<br/>
- The HP-AS Console appears with a Log browser.
- As the HP-AS kernel starts and initializes, messages will appear in the
- status bar of the console.
- Wait for the message 'Kernel started' to appear in the Log browser.
+ The HP-AS Console appears with a Log browser.
+ As the HP-AS kernel starts and initializes, messages will appear in the
+ status bar of the console.
+ Wait for the message 'Kernel started' to appear in the Log browser.
The following message should display:<br/><br/>
<code>[10/16/01 16:03:50][localhost_][S]:Kernel "kernel" started.</code><br/><br/>
</li>
- <li>To verify that an instance of HP-AS is running,
+ <li>To verify that an instance of HP-AS is running,
open a web browser and go to <code>:http://localhost:9090/helloservlet/hello.</code>
<br/>
An HTML page should appear containing the following message:
@@ -617,18 +740,18 @@
<strong><code>This test is valid only if you've performed a full install of HP-AS</code></strong>
<br/><br/>
</li>
- <li>In the HP-AS console, select <strong>View | Deployment Window</strong>.
- In the <strong>Available Files</strong> pane on the right,
+ <li>In the HP-AS console, select <strong>View | Deployment Window</strong>.
+ In the <strong>Available Files</strong> pane on the right,
browse to the the directory you extracted the <code>cocoon.war</code> file to.
<br/>
- Expand this directory, and then drag and drop the
- <code>cocoon</code> sub-directory node to the <strong>kernel.j2ee-partition</strong> icon
+ Expand this directory, and then drag and drop the
+ <code>cocoon</code> sub-directory node to the <strong>kernel.j2ee-partition</strong> icon
in the left pane.
</li>
<li>When prompted, answer <strong>Yes</strong> to the deployment question.<br/>
This should create an appropriate entry in the HP-AS j2ee partition configuration file.<br/>
- <strong><code>In the current version of the console,
- there is no indication that the operation succeeded.
+ <strong><code>In the current version of the console,
+ there is no indication that the operation succeeded.
If you see a parser error in the Log browser, ignore it.</code></strong>
</li>
<li>To test the deployment, open a web browser and go to the following URL:<br/><br/>
----------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org