Installing the Server


Installing JBoss is so easy that new users often think they are missing something. But don't mistake this simplicity for lack of power or configurability. Before we get started, you'll need to make sure you have either Java 1.4 or Java 1.5 installed on your machine. That's the only prerequisite for JBoss 4, so if you are all set we'll get started.

How do I do that?

You can download the latest JBoss version, currently 4.0.2, from the JBoss download page at http://www.jboss.org/downloads/index. Once you choose the version of the JBoss application server you want, you'll be taken to the SourceForge.net page to do the actual download. When you get there select one of the prebuilt binary distributions. For JBoss 4.0.2 look for a file named jboss-4.0.2.zip. You'll also see jboss-.4.0.2.tar.gz and jboss-4.0.2.tar.bz2 archives. If either of those formats works better for your platform, feel free to use it instead.


Note: We use Java 1.4 in most examples, but there should be no differences if you use Java 1.5. JRE install.

Before JBoss 4.0.2, JBoss required a full JDK installation to compile JSP files. As of Version 4.0.2, Tomcat ships with its own Java compiler, so JBoss only requires a JRE install.

Many of the releases have service packs, which are marked with the sp designation. Always choose the latest service pack release for the version you are downloading. You might also see source code releases marked with the -src suffix, as well as RC (release candidate) and DR (developer release) versions of the server. Ignore those for now and stick to the production binaries. In this book we will work from the jboss-4.0.2.tar.gz release.


Note: If you are on a Unix machine, we suggest sticking with the .tar.gz release to make sure file permissions are preserved accurately.

Uncompress the download into the directory where you want JBoss installed, using the appropriate tool for your platform. We put the server into /Users/samjr/jboss-4.0.2; here's the bin directory of the installed server:

     [bin]$ pwd     /Users/samjr/jboss-4.0.2/bin     [bin]$ ls     classpath.sh          jboss_init_suse.sh     run.sh              twiddle.bat     deployer.bat          run.bat                shutdown.bat        twiddle.jar     deployer.sh           run.conf               shutdown.jar        twiddle.sh     jboss_init_redhat.sh  run.jar                shutdown.sh 


Note: If you don't have a good zip tool, you can always use the Java jar program to expand the zip archive.

What just happened?

You just installed one of the most powerful application servers available today. Really powerful tools usually need much more setup and configuration, but not JBoss. Now, you're ready to start it up.

What about...

...if I installed JBoss on another box on my network?

You will want to check the firewall settings on that machine. Specifically, you'll want to make sure that port 8080 is open so that you'll be able to access the JBoss web server to test it out. If you installed JBoss locally you shouldn't have to worry about this.

Be careful about installing JBoss on a machine that might be visible from the Internet. JBoss ships in an insecure state that allows external access to server management features.




JBoss. A Developer's Notebook
JBoss: A Developers Notebook
ISBN: 0596100078
EAN: 2147483647
Year: 2003
Pages: 106

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net