You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by ta...@apache.org on 2005/04/27 23:19:47 UTC

cvs commit: jakarta-jetspeed/xdocs fusion.xml

taylor      2005/04/27 14:19:47

  Modified:    xdocs    fusion.xml
  Log:
  more fusion documentation, getting closer
  
  Revision  Changes    Path
  1.3       +72 -4     jakarta-jetspeed/xdocs/fusion.xml
  
  Index: fusion.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-jetspeed/xdocs/fusion.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- fusion.xml	27 Apr 2005 19:46:44 -0000	1.2
  +++ fusion.xml	27 Apr 2005 21:19:47 -0000	1.3
  @@ -41,7 +41,65 @@
           </p>
       </subsection>
   </section>
  -<section name="Running Jetspeed Fusion">
  +<section name="Deploying and Running Jetspeed Fusion Distributions">
  +        <p>The distribution of Fusion is made up of:
  +        <ul>
  +            <li>A WAR file: jetspeed.war</li>
  +            <li>Common jars, see table below</li>
  +            <li>Database configuration</li>
  +        </ul>    
  +        </p>
  +<subsection name='Fusion Distributions'>
  +    <p>
  +    Jetspeed is downloaded from the <a href='http://www.apache.org/dyn/closer.cgi'>Apache distributions site</a>.
  +    Jetspeed and Jetspeed Fusion are available in several distribution formats:
  +    </p>    
  +    <table>
  +        <tr>
  +            <th>Distribution</th>
  +            <th>Type</th>            
  +            <th>Package</th>
  +            <th>Description</th>
  +        </tr>
  +        <tr>
  +            <td>Jetspeed 1.6</td>
  +            <td>War</td>
  +            <td>jetspeed.war</td>
  +            <td>Jetspeed 1.6 without Fusion. Standalone, ready to run as is against Hypersonic DB. Just drop it in your app server.</td>
  +        </tr>        
  +        <tr>
  +            <td>Jetspeed 1.6 + Fusion</td>
  +            <td>War</td>
  +            <td>jetspeed.war</td>
  +            <td>Jetspeed 1.6 with Fusion. Configured against Hypersonic DB. Requires database and supporting jars.</td>
  +        </tr>        
  +        <tr>
  +            <td>Jetspeed 1.6 + Tomcat</td>
  +            <td>Zip</td>
  +            <td>jetspeed-1.6.zip, jetspeed-1.6.tar.gz</td>
  +            <td>Jetspeed 1.6 with Tomcat, No Fusion. Comes with a configured Hypersonic DB, Tomcat, ready to run.</td>
  +        </tr>        
  +        <tr>
  +            <td>Jetspeed 1.6 + Tomcat + Fusion</td>
  +            <td>Zip</td>
  +            <td>jetspeed-fusion-1.6.zip, jetspeed-fusion-1.6.tar.gz</td>
  +            <td>Jetspeed 1.6 with Tomcat, Fusion. Comes with a configured Hypersonic DB, Fusion, Tomcat, ready to run.</td>
  +        </tr>                
  +        <tr>
  +            <td>Fusion 1.6 Support Jars</td>
  +            <td>Zip</td>
  +            <td>jetspeed-fusion-support-1.6.zip, jetspeed-fusion-support-1.6.tar.gz</td>
  +            <td>Fusion 1.6 support jars. See table below.</td>
  +        </tr>        
  +        <tr>
  +            <td>Fusion 1.6 Database Configuration</td>
  +            <td>Zip</td>
  +            <td>jetspeed-fusion-db-1.6.zip, jetspeed-fusion-db-1.6.tar.gz</td>
  +            <td>Fusion 1.6 database configuration.</td>
  +        </tr>                
  +    </table>    
  +</subsection>        
  +<subsection name="Fusion Common Jars">
           <p>Jetspeed Fusion does require more configuration than a standard Jetspeed 1.6 installation.
               This is because of the nature of the Portlet API: portlet applications are deployed as WAR files
               and run in their web application, separate from the portal. With Fusion, we need to install several
  @@ -81,9 +139,19 @@
               </tr>
               
           </table>
  -        <i>The <b>*</b> denotes a particular version, such as 2.0-M3 with Jetspeed 1.6.</i>
  -        <p>See the section on building from <a href="#Building Fusion">source</a> below for details on how to automate the process.</p>
  -        <p>If you are using Hypersonic, Fusion requires a second database instance to be running.</p>
  +        <i>The <b>*</b> denotes a particular version, such as 2.0-M3 with Jetspeed 1.6.</i>        
  +        <p>See the section on building from <a href="#Building Fusion">source</a> below for details on how to automate the process.</p>   
  +</subsection>      
  +<subsection name="Database">
  +<p>
  +Fusion has its own set of database tables in addition to Jetspeed-1 database tables.
  +This means you have two sets of database scripts to run: one set for Jetspeed-1, one set for Fusion.
  +If you are using Hypersonic, Fusion requires a second database instance to be running.
  +With the Jetspeed Fusion 1.6 Database Configuration distribution, there are scripts for configuring your Fusion
  +database for several database backends. If you are using Hypersonic, the fusion database distribution comes
  +with a pre-built database ready to run. Just start the database using the provided script.    
  +</p>    
  +</subsection>
   </section>    
   <section name="Deploying Portlet Applications">
           <p>
  
  
  

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