User: tcoleman
  Date: 01/03/02 14:30:58

  Modified:    documentation petstore-1.1.1-01.html
  Log:
  Add Cloudscape information from README.CLOUDSCAPE
  
  Revision  Changes    Path
  1.5       +40 -52    newsite/documentation/petstore-1.1.1-01.html
  
  Index: petstore-1.1.1-01.html
  ===================================================================
  RCS file: /products/cvs/ejboss/newsite/documentation/petstore-1.1.1-01.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- petstore-1.1.1-01.html    2001/02/15 21:29:50     1.4
  +++ petstore-1.1.1-01.html    2001/03/02 22:30:58     1.5
  @@ -8,16 +8,15 @@
   <p>The Pet Store demo can allow developers to gain familiarity with J2EE 
   concepts including application portability, a key J2EE design objective.
   
  -<p>The Pet Store demo has been tested with JBoss configured with integrated Tomcat.
  +<p>The Pet Store has been successfully deployed in JBoss PRE 2.1 configured to use 
Embedded Tomcat using the following JDK's:
  +<pre>
  +    1.3 Sun Linux  Tomcat 3.2.1
  +</pre>
   
   <p><h3>Outstanding Deployment Issues:</h3>
  -
  -<p>This is preliminary documentation of a work in progress.  There are 
  -technical issues that need to be addressed before the Pet Store demo can be 
  -considered completely operational in JBoss.  
   
  -<p>This document describes how to deploy Pet Store 1.1.1 in JBoss, providing
  -a framework which will allow developers to address these issues.
  +<p>Please note that Pet Store in JBoss is a Work in Progress.  
  +<p>Please post your experiences with deploying the Pet Store in JBoss to the 
jboss-user mailing list.
   
   <ol>
   <p> 
  @@ -29,19 +28,20 @@
   this class with a JBoss security module that implements the 
   <code>SecurityAdapter</code> interface. 
   <p>
  -You then need to change the value for <code>securityAdapterClassName</code> in
  -the Pet Store <code>web.xml</code> file to the name of the JBoss Security 
  -Adapter.
  +The steps below change the value for <code>securityAdapterClassName</code> in
  +the Pet Store <code>web.xml</code> file to use <code>JBossSecurityAdapter</code>.
   <p>
   See the <code>/docs/security.html</code> page in the Pet Store demo for details.
   <p>
   <li>
  -<h3><a NAME="petstore00">Inventory</a></h3>
  -<p>The Inventory Bean complains that it is "unable to locate invetory." (sic).
  +<h3><a NAME="petstore00">Adding New Users</a></h3>
  +<p>The JBossSecurityAdapter needs to be modified in order to add new users.
   </ol>
   
  -<h2>Original contributor</h2>
  +<h2>Original contributors</h2>
   Mike Leuders, Richard Gyger - Focus Technologies
  +<br>Scott Stark
  +<br>Anatoly Ackerman
   <br>Aaron Mulder
   
   <h2>Doc writer</h2>
  @@ -70,48 +70,20 @@
   <a HREF="petstore-1.1.1-patch.zip">
   www.jboss.org/newsite/documentation/petstore-1.1.1-patch.zip</a>.
   <p>Copy the patch file to a temporary directory and unzip it.  The patch
  -contains two (2) zip files; one to patch JBoss, and another to patch the
  -Pet Store demo. 
  +contains a zip file that patches the Pet Store demo. 
   
   <p>
   <li>
  -<h3><a NAME="petstore3">Rebuild JBoss</a></h3>
  +<h3><a NAME="petstore3">Configure JBoss to use Embedded Tomcat</a></h3>
   
  -<p>Currently, three (3) JBoss java files have to be replaced, and JBoss rebuilt.  
  -It is expected that these modifications will be added to the PRE-2.1 CVS 
  -tree within several days of this patch becoming generally available.  This 
  -documentation and the patch file will be changed at that time.
  -
  -<p>Copy the <code>petstore-jboss.zip</code> file to the root directory ($JBOSS) of 
  -your JBoss distribution. Change to this directory and unzip the file.
  -<pre>
  -    cd $JBOSS
  -    unzip petstore-jboss.zip
  +<p>Follow the instructions on the <a HREF="../business/jboss-tomcat.html">JBoss 
Tomcat</a> product page to configure JBoss to use Embedded Tomcat.
   
  -    cd src/build
  -    sh build.sh
  -</pre>
  -<p>The $JBOSS/<code>dist</code> directory is your new $JBOSS_HOME.
  -
   <p>
   <li>
   <h3><a NAME="petstore4">Select a Database</a></h3>
   <p>The Pet Store demo uses the <b>Cloudscape</b> database by default.
  -To avoid problems with SQL syntax, use Cloudscape if at all possible.
   <p>
  -It also includes SQL scripts for building databases in 
  -<b>Oracle</b> and <b>Sybase</b>, (though you may need to comment out the 
  -<code>drop table</code> statements at the top for them to run the first time).
  -<p>
  -<p>The Pet Store demo is being tested with 
  -<a HREF="http://firebird.sourceforge.net/fb_download.html">Firebird/InterBase 
6.0.</a>
  -The JBoss Pet Store patch file includes a Firebird/InterBase script.
  -In order to use Firebird/Interbase, you will also need to install Interclient 
  -2.0, which provides the JDBC inteface.  Using the Reference J2EE server, the 
  -Pet Store demo did not work correctly with Interclient 1.6.  (Installing 
  -Firebird/InterBase and Interclient is beyond the scope of this document.)
  -<p>
  -The Pet Store demo theoretically should work with just about any JDBC compliant 
database.  
  +The Pet Store demo theoretically should work with just about any JDBC compliant 
database.  However, to avoid problems with SQL syntax, use Cloudscape if at all 
possible.
   
   <p>
   <li>
  @@ -147,11 +119,10 @@
   <li>
   <h3><a NAME="petstore6">Add DB Pools to JBoss</a></h3>
       <p>The JBoss Petstore patch file includes the file
  -      <code>jboss.jcml.</code> This file has Pet Store DB Pools for 
  -      Cloudscape and Firebird/InterBase.  You will have to comment
  -      out or remove the unused Pool.
  -<p>  Cloudscape mappings are included in the <code>standardjaws.xml</code> file
  -     included in the Pet Store patch.
  +      <code>jboss.jcml.</code> This file defines Pet Store DB Pools for 
  +      Cloudscape using port 1098.
  +<p>
  +  Cloudscape uses port 1099 by default.  JBoss uses port 1099 for JNDI.
   <p>  If you will be using a
          different database, you will need to define DB pools appropriate
        for your database.  See the
  @@ -160,9 +131,17 @@
   <p>
   <li>   
   <h3><a NAME="petstore7">Prepare the Database</a></h3>
  +<p>Modify the Cloudscape startup command to use port 1098.
  +<p>You do this by adding <b>-port &lt;port_number&gt;</b>.
  +<p>
  +     for example:
  +<pre>
  +     java ... RmiJdbc.RJJdbcServer <b>-port 1098</b> COM.cloudscape.core.JDBCDriver
  +</pre>
       <p>Whichever product you're using, create a database or instance
         or schema (the terminology varies) and then run the appropriate
  -      script to populate it.  Make sure your DB is running.</p>
  +      script to populate it.  
  +<p>Start Cloudscape.</p>
        
   <p> 
   <li>
  @@ -171,8 +150,17 @@
   JBoss installation ($JBOSS_HOME).
   <p>Copy <code>tools.jar</code> from the J2 SDK to the <code>lib/ext</code>
   directory of your JBoss installation ($JBOSS_HOME).
  +<p>For Cloudscape, copy <code>cloudscape.jar</code> and <code>RmiJdbc.jar</code> to 
the <code>lib/ext</code> directory.
   
  -<p> 
  +<p>
  +<li>
  +<h3><a NAME="petstore9a">Modify the Tomcat Users file</a></h3>
  +<p>The patch contains a tomcat-users.xml file that adds the default Pet Store user. 
 You can copy this file to your <code>$TOMCAT_HOME/conf</code> directory, or
  +add the following line to your existing tomcat-users.xml file.
  +<pre>
  +  &lt;user name = "j2ee"  password = "j2ee"  roles = "customer" /&gt;
  +</pre> 
  +
   <li>
   <h3><a NAME="petstore9">Start JBoss</a></h3>
   <p>Start JBoss and copy the new <code>petstore.ear</code> to the 
  
  
  

Reply via email to