portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wea...@apache.org
Subject cvs commit: jakarta-jetspeed-2/docs GETTING-STARTED.html
Date Thu, 08 Jan 2004 14:42:43 GMT
weaver      2004/01/08 06:42:43

  Added:       .        GETTING-STARTED.html
  Removed:     docs     GETTING-STARTED.html
  I moved the GETTING-STARTED.html doc to the project root in hopes
  of making the process of building Jetspeed 2 more apparent.  Maybe the higher
  visiblity will actually prompt people to read it ;) (sorry, that was the cynical developer
in me
  rearing it's ugly head)
  Revision  Changes    Path
  1.1                  jakarta-jetspeed-2/GETTING-STARTED.html
  <title>Untitled Document</title>
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  <style type="text/css">
  body, body td {  font-family: Arial, Helvetica, sans-serif; font-size: 10pt}
  h1 {font-size: 18pt}
  h2 {font-size: 16pt}
  h3 {font-size: 14pt}
  h3 {font-size: 12pt}
  strong {color: red;}
  code {font-size: 10pt;}
  .border-1 {border: solid 1px;}
  <body bgcolor="#FFFFFF" text="#000000">
  <h1>Getting Started with Jetspeed 2</h1>
  <p>It is expected that the user is familiar with both the <a href="http://maven.apache.org">Apache

    Maven</a> project tool and the <a href="http://ant.apache.org">Apache Ant</a>

    build tool.</p>
    <li><a href="http://ant.apache.org/bindownload.cgi">Ant 1.5</a> or higher</li>
    <li><a href="http://maven.apache.org/start/download.html">Maven 1.0-beta-10</a>

      or higher</li>
    <li>Java 1.3 or higher</li>
    <li>Servlet 2.3:<br>
      Tomcat 4.1.18-LE w/JDK 1.4<br>
      <b>or</b> <br>
      Tomcat 4.1.24 w/ JDK 1.3</li>
  <h2>1. Get Maven Ready</h2>
  <p>If you have not already done so, download and install Maven.</p>
  <p><strong>NOTE!</strong>: There are 2 jars required by Jetspeed that
are <b>NOT 
    </b>available direct through Maven which you will have to download manually.<br>
  <table width="650" border="1" cellspacing="0" cellpadding="3" style="margin-left: 20px">
      <th width="34%" >Jar</th>
      <th width="66%" >Instructions</th>
      <td width="34%" ><a href="http://java.sun.com/products/jdbc/download.html#spec">JDBC

        Standard Extensions 2.0</a></td>
      <td width="66%" >Once downloaded it needs to be renamed to <code>jdbc-se2.0.jar

        </code>and copied to your ${MAVEN_REPOSITORY}/jdbc-se/jars directory.</td>
      <td width="34%"><a href="http://java.sun.com/products/jta/">JTA 1.0.1</a></td>
      <td width="66%">Once downloaded it needs to be renamed to jta1.0.1.jar and 
        copied to your ${MAVEN_REPOSITORY}/jta/jars directory.</td>
      <td width="34%"> 
        <p><a href="http://jakarta.apache.org/pluto">Pluto Container</a></p>
        <p><strong>NOTE!</strong> You will need to check out the latest
CVS build 
          of Pluto, build the driver and copy it to your maven repository.</p>
      <td width="66%">The pluto jar needs to be named to pluto-1.0.jar 
        and copied to your ${MAVEN_REPOSITORY}/Pluto-container/jars directory.</td>
      <td width="34%"><a href="http://java.sun.com/products/JavaManagement/download.html">jxmri

        and jmxtools</a></td>
      <td width="66%"> 
          <li> Unzip the jmxri and jmxtools jars into${MAVEN_REPOSITORY}/jmx/jars</li>
          <li>Rename jmxri.jar to jmxri-1.2.1.jar</li>
          <li>Rename jmxtools.jar to jmxtools-1.2.1.jar</li>
  <p><strong>NOTE!</strong>: <b>Maven Beta 0.9:</b> eation section</p>
    &lt;j:set var=&quot;extensionList&quot; value=&quot;&quot;/&gt;
    &lt;j:forEach var=&quot;artifact&quot; items=&quot;${pom.artifacts}&quot;&gt;
      &lt;j:set var=&quot;dep&quot; value=&quot;${artifact.dependency}&quot;/&gt;
      &lt;j:set var=&quot;extensionList&quot; value=&quot;${extensionList},${dep.artifactId}&quot;/&gt;
    &lt;j:if test=&quot;${extensionList.length() != 0}&quot;&gt;
      &lt;j:set var=&quot;extensionList&quot; value=&quot;${extensionList.substring(1)}&quot;/&gt;
      &lt;ant:attribute name=&quot;Extension-List&quot; value=&quot;${extensionList}&quot;/&gt;
    &lt;j:forEach var=&quot;artifact&quot; items=&quot;${pom.artifacts}&quot;&gt;
      &lt;j:set var=&quot;dep&quot; value=&quot;${artifact.dependency}&quot;/&gt;
      &lt;ant:attribute name=&quot;${dep.artifactId}-Extension-Name&quot; value=&quot;${dep.artifactId}&quot;/&gt;
      &lt;ant:attribute name=&quot;${dep.artifactId}-Implementation-Version&quot;
      &lt;ant:attribute name=&quot;${dep.artifactId}-Implementation-URL&quot;
  <p><strong>NOTE!</strong>: <b>Maven Beta 0.9 and greater:</b>
  <p>In ${jetspeed-2-home}/portal:<br>
    <li> Rename the existing <code>maven.xml </code>file to <code>maven-0.8.xml</code></li>
    <li>Rename <code>maven-0.9-and-up.xml </code>to <code>maven.xml</code></li>
  <h2>2. build.properties settings:</h2>
  <p>Please set these values in your ${USER_HOME}/b<code>uild.properties</code>

  <table width="650" border="1" cellspacing="0" cellpadding="3">
      <th width="134">property</th>
      <th width="229">example</th>
      <th width="261">what is it?</th>
      <td width="134">catalina.shared.lib</td>
      <td width="229">${CATALINA_HOME}/shared/lib/</td>
      <td width="261">The location of the jars in your Tomcat installation.</td>
      <td width="134">deploy.war.dir</td>
      <td width="229">${CATALINA_BASE}/webapps/</td>
      <td width="261">The location to deploy web application in Tomcat.</td>
      <td width="134">deployment.db.alias</td>
      <td width="229">${CATALINA_BASE}/webapps/jetspeed/WEB-INF/db/hsql/Registry</td>
      <td width="261">The location of HypersonicSQL database file that will contain

        Jetspeed information like registries and user info.</td>
  <h2>Step 3 is no longer required as we are accomplishing this with an additional 
    jetspeed.xml file copied to the webapps directory at deploy time.<br>
    <s>3. Changes to Tomcat's server.xml</s></h2>
  <p><s><font color='red'> <b>NOTE:</b> This step is no longer
necessary if you 
    use the "deploy" goal from the portal project. The "deploy" goal handles adding 
    the cross context property.</font></s></p>
  <p><s>Edit ${CATALINA_BASE}/conf/server.xml, add this line:<br>
    (this only needs to be done once)</s></p>
  <p> <s><code>&lt;Context path=&quot;/jetspeed&quot; docBase=&quot;jetspeed&quot;

  <p><s>This will allow the jetspeed app to load your deployed portlet applications.</s></p>
  <h2>4. Build .jar and .war files</h2>
  <p>There are two procedures you can follow that will yeild the same results which

    are to build and install the required jetspeed jars into Maven (for build purposes).</p>
  <table width="650" border="1" cellspacing="0" cellpadding="3" valign="top">
      <th>procedure 1 (short and sweet)</th>
      <th>procedure 2 (long and boring)</th>
      <td rowspan="5" valign="top"> 
        <p><b>Build all jars and wars:</b><br>
          cd ${jetspeed-2-home}<br>
          maven allBuild</p>
      <td><b>Build Portlet-API</b><br>
        cd ${jetspeed-2-home}/portlet-api<br>
        maven jar:install</td>
      <td><b>Build Jetspeed Commons</b><br>
        cd ${jetspeed-2-home}/commons<br>
        maven jar:install</td>
      <td> <b>Build the demo web application </b><br>
        cd ${jetspeed-2-home}/applications/demo<br>
        maven war</td>
      <td><b>Build Jetspeed Portal</b><br>
        cd ${jetspeed-2-home}/portal<br>
        maven war</td>
      <td><b>Install into Catalina Shared</b><br>
        cd ${jetspeed-2-home}<br>
        maven catalina:base-shared<br>
        maven catalina:shared</td>
    5. Deploying Jetspeed 2</h2>
  <p><b>Deploy Jetspeed Portal WAR into Catalina</b></p>
    <li>cd ${jetspeed-2-home}/portal</li>
    <li>maven deploy</li>
  <p>This will unpack the newly created jetspeed.war file into Tomcat/Catalina</p>
  <h2>6. Deploying the demo application</h2>
  <p><b>Install the demo web application into Catalina</b></p>
    <li>cd ${jetspeed-2-home}/portal</li>
    <li>maven pam.register </li>
    <li>The console will stay open with [done] message, at this point you can ctrl-c

      to close the deployment tool.</li>
    <li>maven pam.deploy </li>
    <li>The console will stay open with [done] message, at this point you can ctrl-c

      to close the deployment tool.</li>
  <h2>7. Start Tomcat</h2>
  <p>Run Tomcat, go to http://localhost:8080/jetspeed.</p>
  <h2>(Optional) How to undeploy the demo application</h2>
  <p><b>To undeploy the demo app</b></p>
    <li>cd ${jetspeed-2-home}/portal</li>
    <li>maven pam.undeploy </li>
    <li>The console witll stay open with [done] message, at this point you can ctrl-c

      to close the deployment tool.</li>
  <p>Some users have experienced a problem where the portlet-container jar isn't 
    the latest one copied into the HW_APP webapp<br>
    this causes HelloPortlet to not display any info<br>
    Its easily fixed by manually copying <br>
    ${MAVEN_REPOSITORY}/jetspeed2/jars/jetspeed-container-2.0-a1-dev.jar ${catalina.home}/webapps/HW_APP/WEB-INF/lib/</p>

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message