This chapter describes how to install and run JBoss, how to set environment variables, how to bind IP addresses, and the directory structure of Jboss.
Because JBoss is an application that is certified by the Java EE 6 Standard, JDK 1.6 to later must be installed to use JBoss.
JDK 1.7 was used in the test environment.
To install JBoss, download the package of the corresponding version from the JBoss homepage. (http://www.jboss.org/jbossas/downloads)
After downloading the package, unzip it using a compression tool in the Windows environment, and unzip command in the Unix environment.
In this document, jboss-6.1.0.Final directory created by unpacking is named JBOSS_HOME. JBoss installs is completed by unzipping the package, and it can be run after configuring the JDK.
Windows environment JDK setting
How to set JDK in Windows environment is as follows, and select one of two methods to set it.
- Add the JAVA_HOME variable to the system environment variable.
- Add to the JOBSS_HOME/bin/run.bat file, which is a BJoss running script.
Unix environment JDK setting
How to set JDK in the Unix environment is as follows, and select one of four methods to set it.
Add the JAVA_HOME variable to the system environment variable
Add to the JBOSS_HOME/bin/run.sh file, which is a JBoss startup script
JBoss directory structure
When JBoss is installed, the following directories are created.
- bin: JBOSS related shell script directory
- common: Libraries commonly used in all server configurations
- client: JAR file directory required for client operation
- docs: XML schema and example configuration files directory
- lib: JAR file directory required to run JBOSS
- server: JBOSS server configuration directory
- all: Configuration that supports HA, clustering, and CORBA including Java EE
- default: Configuration that provides Web, EJB, web and additional services
- standard: Configuration that supports Web, EJB, jCA, JMS, Seam, Webservice, Console
- web: Configuration supporting Web, EJB, Security, Console
- minimal: Configuration that supports only minimal functions
- conf: Directory containing basic configuration information for security, logging, Boostrap, and JBOSS
- data: Data directory required for JBOSS operation
- deploy: JBOSS Service and application distribution directory
- deployers: Deployer directory based on the JBOSS Microcontainer
- lib: JAR file directory required for the JBOSS operation
- log: Logging directory
- tmp: JBOSS temporary directory Ex.) JSP file of WAR file
- work: JBOSS working directory Ex.) Java file for JSP
JBoss can be started by installing JBoss and configuring JDK.
In the Unix environment, it can be run by executing JBOSS_HOME/bin/run.sh script, and in the Windows environment, it can be run by executing JBOSS_HOME/bin/run bat batch file.
When JBoss is running normally, "Started" is displayed in the last log message, and the user can check whether JBoss is running normally by accessing the web console (http://server_ip:port number).
By accessing the Administration Console with an admin account (password: admin), the user can operate the currently running JBoss.
Shutting JBoss Down
To shut down JBoss, execute the JBOSS_HOME/bin/shutdown.sh or shutdown.bat script.
Considerations when running and shutting down JBoss
When starting JBoss and shutting it down, these are some of the considerations.
Error due to port duplication while running
In JBoss, the default port is "8080".
However, if this port is being used by another program, the following error occurs when starting JBoss, so it is necessary to change the port.
To change the JBoss default port, modify the connector port in the JBOSS_HOME/server/default/deploy/jbossweb.sar/server.xml file.