User: tobias
Date: 01/02/23 08:22:19
Modified: src/docs jbossintro.xml
Log:
added some instructions for Windows and adjusted paths and
packages to actual distribution
Revision Changes Path
1.4 +35 -27 manual/src/docs/jbossintro.xml
Index: jbossintro.xml
===================================================================
RCS file: /products/cvs/ejboss/manual/src/docs/jbossintro.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- jbossintro.xml 2001/02/11 16:07:23 1.3
+++ jbossintro.xml 2001/02/23 16:22:19 1.4
@@ -100,8 +100,7 @@
to.</para>
<para>The next step will be to download, install and test the JBoss server. At
-the time of writing the most recent version of JBoss is 2.0. You can get JBoss
-from www.jboss.org</para>
+the time of writing the most recent version of JBoss is 2.0.</para>
<para>It doesn't matter very much where you install JBoss; my preference is to
use /usr/local/jboss. If you don't have root access, or would rather not run
@@ -110,40 +109,48 @@
that you are installing in /usr/local/jboss. If you haven't, change the paths
as appropriate.</para>
-<para>JBoss is distributed using Install Anywhere which isn't a natural format
-for Linux users. If you're running the X Window System on your Linux machine
-and you have Netscape installed with Java enabled, this might work for you.
-Otherwise, your best bet right now is to download from CVS or to install from
-the Zip file like this:</para>
-
-<literallayout><command>su
-mkdir /usr/local/jboss
-cd /usr/local/jboss
-lynx -source \
- http://jboss.org/JBoss2/InstData/Other/install.zip \
- > install.zip
-mkdir installer
-cd installer
-unzip ../install.zip
-mv c:/jboss2/* ..
-cd ..
-rm -rf installer
-rm -f install.zip
+<para>JBoss is distributed as a ZIP file. You can download the binary
+distribution which contains the latest offical release (which was 2.0
+FINAL at the time of writing) or a source snapshot with the latest
+version from CVS (called PRE2.1). This documentation mainly is written
+for the 2.0
+version. You can get all the mentioned packages from http://www.jboss.org .
+</para>
+
+<formalpara><title>Installation of binary package for Windows:</title>
+<para>Download the binary package from http://www.jboss.org from the
+Download - Binary section. Place it in a temporary directory and use your
+favorite unziper to decompress it to the place where you want JBoss
+installed. Start the "command line" from "Accessories" menu and change to
+the directory to which you just decompressed the binary package.
+</para></formalpara>
+
+<formalpara><title>Installation of binary package for Linux:</title>
+<para><literallayout><command>cd /tmp/
+lynx -source http://www.jboss.org/newsite/bin/jBoss-2.0_FINAL.zip >
jBoss-2.0_FINAL.zip
+su
+cd /usr/local/
+unzip /tmp/jBoss-2.0_FINAL.zip
+mv jBoss-2.0_FINAL jboss
+cd jboss
</command></literallayout>
+</para></formalpara>
-<para>You could try running the server now. Change to the bin directory, and
+<para>Now change to the user as which you want to run the
+server. Please make sure, that this user has the JDK binaries in his
+command path and that he has write access to the JBoss directory
+(needed for log files and deployment).
+You are now ready to change to the bin directory, and
run the program like this: </para>
-
<literallayout><command>cd bin
-java -jar run.jar
-</command>
+java -jar run.jar</command>
</literallayout>
-
<para>In a proper installation, the server should start without any error
-messages or exceptions being thrown. It will produce about three pages of
+messages or exceptions being thrown. It will produce several pages of
output on startup.</para>
+<!-- outdated, no test included in binary distro
<para>The JBoss distribution is supplied with one test Bean, packaged as
bank.jar. This is supplied in the `deploy' subdirectory, which is where Beans
are placed to deploy them. The effect of this is to deploy the `bank' bean
@@ -151,6 +158,7 @@
SQL server is working, but you can usefully move bank.jar out of the deploy
directory when you are sure that everything's OK, and the server will start up
more quickly.</para>
+-->
</section>
