JBoss, all secrets!!

JBoss Application Server is a Java EE server written in Java entirely free in the GNU LGPL license application. JBoss application server written in Java and can be offered in June, the Java Virtual Machine (JVM) for all operating systems.

The development has been used JBoss services company called heart "JBoss". Creation of the first version of JBoss designer Marc Fleury, the summer movie. Project is a global network of partners to use the United Nations and the service-based. in April 2006 February 2007 Red Hat economy acquired JBoss Marc Fleury leaves Red Hat group.

JBoss Application Server applications all fully Java EE services. stereotyped:

        Tomcat web server and JSP servlet execution flow of the application server to deploy third-party agents;
        JBoss Portal (en): portal framework;
        JBoss Seam (en): Web Framework;
        Hibernate persistence framework;
        jBPM workflow engine;
        Rules: business rules management system.

The steps of the installationthe prerequisites
JBoss is a Java application server, so you must have a JDK installed on your machine (version 5.0 or 6.0).unzip
After downloading this product http://www.jboss.org/download/ simply unzip it to the correct directory (eg / opt/jboss-4.2.2 / ) .
The environmentIt is always very simple you need to set two environment variables JAVA_HOME and JBOSS_HOME pointing to their respective installation directories.
export JAVA_HOME = / opt/jdk1.5.0_15 /export JBOSS_HOME = / opt/jboss-4.2.2 /
Now you can start the application
$ JBOSS_HOME / bin / run.sh

desired personalization
I am a regular Tomcat and Websphere with which I easily customize my setup . I wanted to do the same with JBoss and after some research I came to make the adjustments you want (almost) .

    Change and move the $ JBOSS_HOME / server / default directory
    Set a specific directory for webapps common to all libraries (eg jdbc drivers , ... )
    Define new deployment directory
    Outsource jndi binding (do not use jboss- web.xml) : Here, I 'm still looking , if you know a solution for this I'm interested
modifications
It is possible to specify a JBoss properties file to configure its execution environment . This is simply done with the parameter -properties ( pass command line or changing the variable in JBOSS_CONF run scripts ) .
example:

# configuration to use Benthic, usually one of ' minimal ', ' default', 'all'= $ { # JBOSS_CONF JBOSS_CONF : - " default"}JBOSS_CONF = "production - properties = file :/ www / jboss / jboss_startup.properties "
This gives for example

$ JBOSS_HOME / bin / run.sh - properties = file :/ www / jboss / jboss_startup.properties
The configuration file jboss_startup.properties
jboss.server.name = Productionjboss.server.base.dir = / www / jbossjboss.server.base.url = file :/ www / jbossjboss.patch.url = file :/ www / jboss / mylib
This setting allows you to:

    use a configuration that I call "production" (the name of the directory / www / jboss / Production )
    jboss.patch.url a property to define the repertoire of common libraries .
To define new deployment directory you must edit the jboss-service.xml file and change the value of the URL attribute to specify these directories

  <attribute name="URLs">
     deploy / , appli_paul / , appli_bernard / , datasource /
  </ attribute>
In my example I continue to deploy / directory ( for backgrounds included with the JBoss application server) and defined two new listed for isolating applications and those paul bernard . The datasource lists / allows me to centralize my JNDI configuration files .