User: mulder
Date: 00/09/14 14:46:21
Modified: manual index.html install.html intro.html warning.html
Added: manual unix_start.html
Log:
Add installation instructions.
Revision Changes Path
1.2 +8 -5 jbossweb/manual/index.html
Index: index.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/index.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.html 2000/09/14 18:28:36 1.1
+++ index.html 2000/09/14 21:46:20 1.2
@@ -19,11 +19,13 @@
<p CLASS="tc3"><a CLASS="plain" HREF="intro.html#complete">Complete J2EE
Solutions</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="intro.html#team">The jBoss
Team</a></p>
<p CLASS="tc1"><a CLASS="plain" HREF="install.html">Installation</a></p>
- <p CLASS="tc2">Supported Java Versions</p>
- <p CLASS="tc2">Windows</p>
- <p CLASS="tc2">UNIX</p>
- <p CLASS="tc2">Macintosh</p>
- <p CLASS="tc2">Other Platforms</p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="install.html#versions">Supported Java
Versions</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="install.html#windows">Windows</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="install.html#service">Installing as
an NT Service</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="install.html#unix">UNIX</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="install.html#startup">Starting
jBoss with the Server</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="install.html#mac">Macintosh</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="install.html#other">Other
Platforms</a></p>
<p CLASS="tc1"><a CLASS="plain" HREF="config.html">Basic Configuration</a></p>
<p CLASS="tc2">Important Directories</p>
<p CLASS="tc3">Executables</p>
@@ -151,6 +153,7 @@
<p CLASS="tc3">The GPL</p>
<p CLASS="tc3">3rd Party Software</p>
<p CLASS="tc3">What It Means</p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="unix_startup.html">UNIX Startup
Scripts</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="architecture.html">jBoss
Architecture</a></p>
<p CLASS="tc3">JMX</p>
<p CLASS="tc3">Container Factory</p>
1.2 +78 -0 jbossweb/manual/install.html
Index: install.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/install.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- install.html 2000/09/14 18:28:36 1.1
+++ install.html 2000/09/14 21:46:20 1.2
@@ -5,5 +5,83 @@
</head>
<body>
<h1 ALIGN="CENTER">jBoss 2.0: Installation</h1>
+
+ <h2><a NAME="versions">Supported Java Versions</a></h2>
+ <p>jBoss requires Java 2. In particular, if you're using Sun's
+ JDK, you need 1.2.2 or greater. The default configuration
+ supports JDK 1.3 only.</p>
+ <p>If you want to run jBoss under JDK 1.2.2, you must presently
+ override the default container invoker setting in the jboss.xml
+ file for each of your EJB JARs
+ (see <a HREF="BROKENLINK">The jBoss Deployment Descriptor</a>).
+ In a future release, you will be able to change the default
+ container invoker setting instead.</p>
+ <p>The only feature that will not work under JDK 1.2 is the
+ graceful server shutdown from the jBoss console. Under JDK 1.3,
+ if you hit Ctrl-C at the console, the server will shut down
+ properly. Under 1.2, it will shut down abruptly, without
+ closing DB connections, erasing temp files, etc.). You can
+ still shut the server down gracefully via the management
+ interface (see <a HREF="managing.html">Managing a Live jBoss
+ Server</a>), but that is a more complex process.</p>
+
+ <h2><a NAME="windows">Installing on Windows</a></h2>
+ <p>You can use either the ZIP package or Installer package to
+ install on Windows.</p>
+ <p>If you use the ZIP package, create a jBoss directory (the path
+ should not have spaces in any of the directory names) and unzip
+ the jBoss package into the directory you created.</p>
+ <p>If you use the Installer package, you need to have a JVM on your
+ machine before you run it. Once you have a JVM, start the
+ installer and:</p>
+ <ol>
+ <li>View the GPL License (described in more detail in the Appendix
+ under <a HREF="license.html">License</a>). If you do not agree,
+ well, you're reading the wrong manual.</li>
+ <li>Select an installation directory. There should not be spaces
+ in the names of any of the directories in the path.</li>
+ <li>Choose whether to install shortcuts.</li>
+ </ol>
+ <p>After that, jBoss will install.</p>
+
+ <h3><a NAME="service">Installing as an NT Service</a></h3>
+ <p>Directions Forthcoming</p>
+
+ <h2><a NAME="unix">Installing on UNIX</a></h2>
+ <p>You can use either the ZIP package or Installer package to
+ install on UNIX.</p>
+ <p>If you use the ZIP package, create a jBoss directory (the path
+ should not have spaces in any of the directory names) and unzip
+ the jBoss package into the directory you created.</p>
+ <p>If you use the Installer package, you need to have a JVM on your
+ machine before you run it. Once you have a JVM, start the
+ installer and:</p>
+ <ol>
+ <li>View the GPL License (described in more detail in the Appendix
+ under <a HREF="license.html">License</a>). If you do not agree,
+ well, you're reading the wrong manual.</li>
+ <li>Select an installation directory. There should not be spaces
+ in the names of any of the directories in the path.</li>
+ </ol>
+ <p>After that, jBoss will install.</p>
+
+ <h3><a NAME="startup">Starting jBoss with the Server</a></h3>
+ <p>You can set up scripts for UNIX that will start jBoss when
+ the server starts up and shut is down when the server shuts down.
+ There are instructions in the Appendix (see
+ <a HREF="unix_start.html">UNIX Startup Scripts</a>).</p>
+
+ <h2><a NAME="mac">Macintosh</a></h2>
+ <p>The current Mac OS does not support Java 2, so you can't run
+ jBoss on it. Mac OS X will include Java 2 support, but we have
+ not yet tested jBoss with the OS X beta. If you have, please
+ let us know on the jBoss
+ <a HREF="http://www.jboss.org/mailing.htm">Mailing List</a>.</p>
+
+ <h2><a NAME="other">Other Platforms</a></h2>
+ <p>Any operating system that supports Java 2 should be able to run
+ jBoss. If you have run it on another OS, please let us know. If
+ for some reason you can't access the ZIP file on a platform, we
+ will work with you to provide the appropriate archive type.</p>
</body>
</html>
1.2 +9 -9 jbossweb/manual/intro.html
Index: intro.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/intro.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- intro.html 2000/09/14 18:28:37 1.1
+++ intro.html 2000/09/14 21:46:20 1.2
@@ -21,9 +21,9 @@
on any particular operating system, etc. The source code is
available for download as well.</p>
<p>Subject to the terms of the GPL License (see
- <a HREF="BROKENLINK">Appendix: License</a>), you are welcome to
- modify the source code for jBoss to do as you see fit. In
- general, you must make your changes available to the community
+ <a HREF="license.html">License</a> in the Appendix), you are
+ welcome to modify the source code for jBoss to do as you see fit.
+ In general, you must make your changes available to the community
under the GPL License as well. We encourage you to make any fixes
or enhancements you see fit, and let us know by describing your
changes to the jBoss
@@ -81,8 +81,8 @@
entire J2EE package. Instead, it implements an important subset
of J2EE in a flexible and modular way. You may use jBoss alone,
or you may use it in conjuntion with other products to provide a
- complete J2EE environment (see <a HREF="BROKENLINK">Third-Party
- Software</a>).
+ complete J2EE environment (see
+ <a HREF="third_party.html">Third-Party Software</a>).
<h3><A NAME="provides">What jBoss Provides</a></h3>
<dl>
@@ -130,7 +130,7 @@
or applications can use different features and techniques.</p>
<p>All together, this makes a very flexible architecture that is
easy to manage and extend. If you are interested in more detail,
- refer to <a HREF="BROKENLINK">jBoss Architecture</a> in the
+ refer to <a HREF="architecture.html">jBoss Architecture</a> in the
Appendix.</p>
<h3><a NAME="complete">Complete J2EE Soluctions</a></h3>
@@ -145,9 +145,9 @@
<p>We believe the advanced modular achitecture of jBoss makes it
easy to integrate with other software. If you would like to
use jBoss with a package that is not on our list of
- <a HREF="BROKENLINK">Third-Party Software</a>, post a messsage
- to the <A HREF="http://www.jboss.org/mailing.htm">Mailing List</a>
- and we will work with you.</p>
+ <a HREF="third_party.html">Third-Party Software</a>, post a
+ messsage to the <A HREF="http://www.jboss.org/mailing.htm">Mailing
+ List</a> and we will work with you.</p>
<h2><a NAME="team">The jBoss Team</a></h2>
<p>As an open-source project, jBoss 2.0 is the product of numerous
1.2 +32 -1 jbossweb/manual/warning.html
Index: warning.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/warning.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- warning.html 2000/09/14 18:28:38 1.1
+++ warning.html 2000/09/14 21:46:20 1.2
@@ -27,6 +27,12 @@
what advanced features does SpyderMQ provide, etc?)</li>
</ul>
</li>
+ <li>Installation
+ <ul>
+ <li>Need to try UNIX installer and get specific steps</li>
+ <li>Need instructions for NT Service</li>
+ </ul>
+ </li>
<li>Basic Configuration
<ul>
<li>This section must be written</li>
@@ -86,8 +92,33 @@
<ul>
<li>This section must be written</li>
</ul>
+ </li>
+ <li>EJX Walkthrough
+ <ul>
+ <li>This section must be written</li>
+ </ul>
+ </li>
+ <li>DTDs
+ <ul>
+ <li>This section must be written</li>
+ </ul>
+ </li>
+ <li>License
+ <ul>
+ <li>This section must be written</li>
+ </ul>
+ </li>
+ <li>UNIX Startup Scripts
+ <ul>
+ <li>Need to test and include an actual script</li>
+ </ul>
+ </li>
+ <li>jBoss Architecture
+ <ul>
+ <li>This section must be written</li>
+ </ul>
</li>
- <li>Appendix
+ <li>jBoss in Production
<ul>
<li>This section must be written</li>
</ul>
1.1 jbossweb/manual/unix_start.html
Index: unix_start.html
===================================================================
<html>
<head>
<title>jBoss 2.0: UNIX Startup Script</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
<h1 ALIGN="CENTER">jBoss 2.0: UNIX Startup Script</h1>
<p>You can use this script to start jBoss when your server starts,
and shut it down gracefully when the server shuts down. It was
written and tested on Red Hat Linux, but should operate on other
similar UNIX platforms.</p>
<p>To use this script, copy the contents into a file, and save
that in your startup script directory, which is usually
<code>/etc/rc.d/init.d</code> or <code>/etc/init.d</CODE> Then
you need to either run chkconfig or add symbolic links to the
directories for the runlevels where you want the script to run.
Those directories are usually <code>/etc/rc.d/rc#.d</code> or
<code>/etc/rc.#</code> where # is the runlevel. If you start
the name of the script with K## the system will call "script
stop" when the appropriate runlevel is entered, while if you start
the name with it with S## it will call "script start". In either
case, all the scripts to be started or stopped are called in the
order of the ## in the symlink name, so you obviously want jBoss
to start after and shut down before any networking services, at
least.</p>
<p>Here is the code for the script. Note that you can execute the
jBoss startup script as a user other than root (see the commented
out line under "start").</p>
<pre>
</pre>
</body>
</html>
