• Unzip downloaded JBoss file into c:\program files\java folder.  It will create c:\program files\java\jboss-as-7.1.1 Folder

     Domain Directory Structure

     

          

    Structure of a Web Application

       A web application is deployed in the \server\default\deploy folder. One web application will have below director structure.

       

    Steps to Deploy a Web Application

       Before you assemble the application components, you must define the directory structure for the application. To do so:

1.    Create a root directory with an appropriate name for the application, say \onlineresult inside .\jboss-4.0.4\server\default\deploy folder
   
2.     In the root directory \onlineresult, create the following directory structure.
• \onlineresult :
• Contains JSP, HTML, JavaScript, Images, Applet files
• \WEB-INF
• web.xml : application configuration file
• \classes : contains all compiled servlets and java classes
• \lib : contains library jars like database drivers
3.  Now start your JBoss server.
4.  Open a browser and enter url http://localhost:8080/onlineresult/index.html. You will see your page.

      A special directory exists within the application hierarchy named “WEB-INF”. It is important to note that the WEB-INF directory is not
      part of the public document tree of the application. A browser can not access any document from URL that exists within WEB-INF. 

        WEB-INF contains

• /WEB-INF/web.xml  deployment descriptor, configures application.
• /WEB-INF/classes/  directory for servlet and utility classes.  The classes in this directory are used by the application class loader to load classes from.
• /WEB-INF/lib/  contains library jars like database driver.  All such archive files are used by the web application class loader to load classes from.

Creating a Data Source for the External Database

JBoss AS connects to relational databases via data sources. These data source definitions can be found in the jboss-as/server/production/deploy directory. The data source definitions are deployable just like WAR and EAR files. The data source files can be recognized by looking for the XML files that end in *-ds.xml.

The data source definition files for all supported external databases can be found in the jboss-as/docs/examples/jca directory.

The following code snippet shows the mysql-ds.xml file as an example. All the other *-ds.xml files are very similiar. You will need to change the connection-url, as well as the user-name / password, to fit your own database server installation.

<datasources>
  <local-tx-datasource>
    <jndi-name>MySqlDS</jndi-name>
    <connection-url>jdbc:mysql://localhost:3306/jboss</connection-url>
    <driver-class>com.mysql.jdbc.Driver</driver-class>
    <user-name>jbossuser</user-name>
    <password>jbosspass</password>
    <exception-sorter-class-name>
			org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter
		</exception-sorter-class-name>
    <!-- should only be used on drivers after 3.22.1 with "ping" support
    <valid-connection-checker-class-name>
			org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker
		</valid-connection-checker-class-name>
    -->
    <!-- sql to call when connection is created
    <new-connection-sql>some arbitrary sql</new-connection-sql>
      -->
    <!-- sql to call on an existing pooled connection when it is obtained from pool - 
		MySQLValidConnectionChecker is preferred for newer drivers
    <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
      -->

    <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
    <metadata>
       <type-mapping>mySQL</type-mapping>
    </metadata>
  </local-tx-datasource>

</datasources>
   

Once you customized the *-ds.xml file to connect to your external database, you need to copy it to the jboss-as/server/production/deploy directory. The database connection is now available through the JNDI name specified in the *-ds.xml file.

FAQ