Chapter 2. The JBoss Server - A Quick Tour

Chapter 2. The JBoss Server - A Quick Tour

2.1. Directory Structure
2.1.1. JBoss Top Level Directory Structure
2.1.2. JBOSS_DIST/jboss-as Directory Structure
2.2. Server Configurations
2.2.1. Server Configuration Directory Structure
2.2.2. The "default" Server Configuration File Set
2.2.3. The "all" Server Configuration File Set
2.2.4. EJB3 Services
2.2.5. Adding Your Own Configuration
2.3. Starting and Stopping the Server
2.3.1. Start the Server
2.3.2. Start the Server With Alternate Configuration
2.3.3. Using run.sh
2.3.4. Stopping the Server
2.3.5. Running as a Service under Microsoft Windows
2.4. The JMX Console
2.5. Hot-deployment of services in JBoss
2.6. Basic Configuration Issues
2.6.1. Core Services
2.6.2. Logging Service
2.6.3. Security Service
2.6.4. Additional Services
2.7. The Web Container - Tomcat

Let's explore the JBoss Enterprise Application Platform directory structure and help you understand how the installation is laid out and what goes where. It’s worth familiarizing yourself with the layout, locations of the key configuration files, log files, deployment and so on. It will help you understand the JBoss service architecture so that you’ll be able to find your way around when it comes to deploying your own applications.


[1] The Java Authentication and Authorization Service. JBoss uses JAAS to provide pluggable authentication modules. You can use the ones that are provided or write your own if you have more specific requirements.

[2] If you installed JBoss using the Graphical Installer and set the JMX Security up, then you will not have to uncomment the sections, because they are already uncommented. Additionally, the admin password will be set up to whatever you had specified.

[3] Since the username and password are session variables in the web browser you may need to shut down your browser and come back in to see the login dialog come back up.