Java Tutorial - Java Scipt : Looking at the Default Configuration

Java Tutorial - Java Scipt :

Looking at the Default Configuration

At this point, JBoss is already ready to run. Just find the batch file named run.bat ( in Linux) in the bin subdirectory of the JBoss home directory. Executing that will run the JBoss application server, including JBossMQ.

 We’ll get into configuring and securing JBoss in more detail in Chapter 11.

For the time being, the default setup will work fine. Before we run JBoss though, we will look at parts of JBoss that are pertinent to our discussion of JMS and MDB. If you look at the JBoss home directory, you’ll find the following directories: /bin. Holds various batch files and shell scripts, of which we are only interested in run.bat (or for Linux). /client. Contains library jars that are used by client applications. We will need the jbossall-client.jar and log4j.jar in this directory for our standalone JMS clients. The jbossall-client.jar file holds all the classes needed by a standalone JBoss client, including the JBossMQ client classes. The log4j.jar file holds classes that handle logging and is also required. /docs. Includes documentation and is a useful place to check whenever you need more information on JBoss. /lib. Contains various library jars required by JBoss application server. /server. This is where all the server stuff resides. There are three subdirectories under server directory, which correspond to various service level configurations for the JBoss server: /default. Includes the standard J2EE environment for a standalone
server. /minimal. This minimal environment is pretty much useless for our purposes, because it doesn’t even start up the EJB services. /all. Contains everything in default, plus RMI/IIOP and clustering. We will be sticking with the default service configuration for the purposes of this book.