User: user57  
  Date: 02/03/06 21:56:09

  Added:       src/docs/demo/netboot index.jsp
  Log:
   o basic netboot demo docs... still needs some work
  
  Revision  Changes    Path
  1.1                  newsite/src/docs/demo/netboot/index.jsp
  
  Index: index.jsp
  ===================================================================
  <jsp:include page="/head.jsp" flush="true" />
  <!-- $Id: index.jsp,v 1.1 2002/03/07 05:56:09 user57 Exp $ -->
  <jsp:include page="/slogan.jsp" flush="true" >
     <jsp:param name="SLOGAN" value="Demo > NetBoot"/>
  </jsp:include>
  
  <!-- ==================================================================== -->
  
  <jsp:include page="/common/picateam.jsp" flush="true"/>
  
  <p>JBoss 3.x provides the ability to boot from a network URL with only a
     tiny boot-strap installation.
  
  <p>This page will guide you through the process of downloading the minimal
     boot-strap binaries and show you how simple it is to use <em>NetBoot</em>
     to start up a JBoss server instance.
  
  <p>Unless specified otherwise, all examples given are formated for UNIX
     users and assume that the current working directory (CWD) is the project
     directory which contains the <tt>build/</tt> sub-directory.  Windows
     users can <em>probably</em> omit any preceding <tt>./</tt>, substitute 
     <tt>/</tt> for <tt>\</tt> and change <tt>.sh</tt> for <tt>.bat</tt> to 
     create runnable command examples.
  
  <p>Some of the output examples have been truncated either horizontally,
     vertically or both to preserve the layout of this page.  Truncation
     is marked by <tt>...</tt>.
  
  <br clear="all">
  
  <!-- ==================================================================== -->
  
  <h2><a name="Contents"></a>Contents</h2>
  
  <p>
  <ul>
     <li><a href="#Introduction">Introduction</a>
     <li><a href="#Requirements">Requirements</a>
     <li><a href="#Getting_the_Binary">Getting the Binary</a>
     <li><a href="#Starting_the_Server">Starting the Server</a>
     <li><a href="#Other_Configurations">Other Configurations</a>
     <li><a href="#What_Next">What Next?</a>
  </ul>
  
  <!-- ==================================================================== -->
  
  <h2><a name="Introduction"></a>Introduction</h2>
  
  <p>JBoss <em>NetBoot</em> is an administrative feature to simplify 
     deployment and configuration of JBoss servers in a distributed
     environment.
  
  <p>It works by installing a small (tiny really) binary on the target
     system.  This binary contains the required boot-strap components which
     then <em>pull</em> down the rest of the required resources from a 
     configured URL.  All that is required is the binary and free
     diskspace for some temporary files.
  
  <p>[<a href="#Contents">Contents</a>]
  
  <!-- ==================================================================== -->
  
  <h2><a name="Requirements"></a>Requirements</h2>
  
  <p>To effectivly run the examples below you will need to make sure that 
     you have:
  
     <ul>
       <li>A Java 2 Runtime Environemnt or Developer's Kit version 1.3<sup>*</sup>.
       <li>10-20 megabytes of disk space<sup>**</sup>.
       <li>A web browser (to look at the HTTP admin console).
       <li>A chair to sit in so you do not faint and hurt yourself after
           seeing how easy this is!
     </ul>
  
  <p><b>*</b> Newer versions will be supported shortly.
  
  <p><b>**</b> Disk space requirements are for local temporary and state
     data files plus the minimal boot-strap binaries.
  
  <p>[<a href="#Contents">Contents</a>]
  
  <!-- ==================================================================== -->
  
  <h2><a name="Getting_the_Binary"></a>Getting the Binary</h2>
  
  <p>Grab one of these tiny archives:
  
  <ul>
    <li><a href="jboss-netboot.zip">jboss-netboot.zip</a>
    <li><a href="jboss-netboot.tgz">jboss-netboot.tgz</a>
  </ul>
  
  <p>The extracted archive should look something like this:
  
  <pre class="output">
  README.txt
  LICENSE.txt
  bin/
  bin/run.bat
  bin/run.sh
  bin/run.jar
  bin/shutdown.bat
  bin/shutdown.sh
  bin/shutdown.jar
  </pre>
  
  <p>[<a href="#Contents">Contents</a>]
  
  <!-- ==================================================================== -->
  
  <h2><a name="Starting_the_Server"></a>Starting the Server</h2>
  
  <p>To use the <em>NetBoot</em> facility, all you need is to provide the
     base URL where the system components are available from.  This is done
     by using the <tt>--netboot</tt> flag on the command line:
  
  <pre class="command">
  ./bin/run.sh --netboot http://jboss.org/demo/netboot/base
  </pre>
  
  <p>This command should produce the following output on success.  If for
     some reason the server did not start as expected, see 
     <a href="Common_Problems">Common Problems</a> for more information.
  
  <pre class="output">
  FIXME
  FIXME
  FIXME
  FIXME
  </pre>
  
  <p>The above command starts JBoss using the configuration named <tt>default</tt>
     and is equivilent to the following:
  
  <pre class="command">
  ./bin/run.sh --netboot http://jboss.org/demo/netboot/base --config default
  </pre>
  
  <p>If you take a look at the directory structure you will find some new 
     files have been created:
  
  <pre class="output">
  server/default/log
  server/default/log/server.log
  server/default/tmp
  server/default/tmp/...
  </pre>
  
  <jsp:include page="/common/picateam.jsp" flush="true"/>
  
  <p>Finally connect to the HTML JMX Console, which should show you the 
     <em>Agent View</em> of the <em>MBeans</em> which are currently loaded in 
     the server.  To do this simple point your favorite web browser at 
     <tt>http://<em>hostname</em>:8082</tt>, where <em>hostname</em> is the 
     name of the host where you are running the server from.  If you are running 
     the server on the same machine as your browser then click 
     <a href="http://localhost:8082";>here</a>.
  
  <br clear="all">
  
  <h3><a name="Common_Problems"></a>Common Problems</h3>
  
  <p>TODO Some common problems... JAVA_HOME, URL typeo, configname typeo
  
  <p>[<a href="#Contents">Contents</a>]
  
  <!-- ==================================================================== -->
  
  <h2><a name="Other_Configurations"></a>Other Configurations</h2>
  
  <p>The previous example uses the <em>default</em> configuration, which we have
     trimmed to contain only the basic components required for server to function.
     There is nothing stopping you from deploying more advanced configurations,
     such as a full J2EE container, full blown web application or really any other
     configuration you can think of!
  
  <p>To help show how easy it is to use <em>NetBoot</em> for these advanced 
     uses, we have setup a few more configurations which provide some real world
     functionality.
  
  <p>These configurations are meant to show you the power and simplicity of 
     <em>NetBoot</em> and are not and should not be used for production systems.
  
  <p>These advanced configurations require more support resources that the 
     simple example from above.  Depending on how fast your network connection
     is it may take longer for the server to start fully.
  
  <h3>A Full J2EE Container
  
  <p>This example configuration provides a FULL J2EE container, which you can
     even deploy your Enterprise Java Beans into!
  
  <pre class="command">
  ./bin/run.sh --netboot http://jboss.org/demo/netboot/base --config j2ee
  </pre>
  
  <h3>Java Pet Store Example
  
  <p>This configuration provides the required components for Sun's Java Pet
     Store demo running inside of JBoss!
  
  <pre class="command">
  ./bin/run.sh --netboot http://jboss.org/demo/netboot/base --config petstore
  </pre>
  
  <p>[<a href="#Contents">Contents</a>]
  
  <!-- ==================================================================== -->
  
  <h2><a name="What_Next"></a>What Next?</h2>
  
  <p>You will want to take into consideration what your deployment needs
     are, what your environment restrictions are and how much effort you are
     willing to invest in configuration management.
  
  <p>If all that confused you then why not ask the experts at
     <a href="/jbossgroup/services.jsp">JBoss Group</a> for help!
  
  <p>[<a href="#Contents">Contents</a>]
  
  <br clear="all"/>
  
  <jsp:include page="/navigation.jsp" flush="true" />
  
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to