It is a well know fact that JBoss is the most popular open source application server for enterprise applications. The system resource required for JBoss AS is comparatively very less compared to BEA Weblogic Application server or Websphere Server.
Hotdeploy features(which means applications can be deployed in a real time without affecting other running applications),Copy and Paste feature of the application server( Other application servers need to install in the operating systems), Shorter start time, all these makes JBoss a favorite environment for application developers and software testers.
Path settings and starting a JBoss Server.
Previous versions of JBoss can be start just by clicking run.bat file inside JBoss/bin folder on windows servers and executing run.sh on linux. A path setting to javadevelopment home like set java_home=c:\jdk1.6 in the top of run.bat files avoids all confusion relating to jdk settings. For a basic start no other settings are required.
For a fresher the jsp files can be put inside jboss(extension can be there like 3.2.3, 4.0.3, 4.0.5, 4.2.3, 5.1.0)/server/default/deploy as a folder with an extension test.war , the bean or servlet files can be put by creating folder test.war/web-inf/classes folder. Double click run.bat and the application starts in approximate 20 seconds. In previous versions like JBoss 3, the default ports are specified in the file jboss/server/default/conf/jboss-service.xml , you can see ports like 8083 for webservice, 1099 for Naming Service, 1198 for BindAddress , 4444 for rmi etc and jboss/server/default/deploy/jbossweb-tomcat.sar\meta-inf\jboss-service.xml ports like 8080 which is the http port and 8443 which is the https port.
If any of these ports are used by your other existing applications like IIS or a proxy , jboss will not run. You can find see the error on the console or you can check server.log inside jboss/server/default/log . If these ports are already bind to some other application , just increment the port values and start run.bat again. The server can be stopped by executing shutdown command like shutdown –S , the dos path should be jboss/bin to execute shutdown.bat. Anyway don’t bother you can shutdown jboss server by pressing ctrl+C or by just closing the application, no error will happen to jboss configuration !, that is the other advantage. If you are running a JBoss in remote machines you may not be able to find the console, in that case you can stop the server by executing the shutdown command.
If you are using the default porst, you can run the application like http://localhost:8080/test/index.jsp ( Note that you need not to specify as test.war in the browser url ) . If your machine name is mypc you can run the application as http://mypc:8080/test/index.jsp or with your IP address http://192.168.1.1:8080/test/index.jsp
Path settings and starting a latest version of JBoss Server.
In latest version like JBoss 5 , the binding ports are specified in jboss/server/default/conf/bindingservice.beans/meta-inf/bindings-jboss-beans.xml
And http , https ports are specified in jboss/server/default/deploy/jbossweb.sar/server.xml
For JBoss 4 the binding paths are same like JBoss 3.
On executing the run.bat you can access the application like http://localhost:8080/test/index.jsp , but unlike previous versions you may not be able execute with IP address or like http://mypc:8080/test/index.jsp due to JBoss security settings.
If you want to access with machine url or IP you have to execute run.bat with command run –b mypc or run –b 192.168.1.1 or like run –b 0.0.0.0 ( which works with all urls )