Red Hat Developer Studio ships with JBoss EAP v.4.2 bundled. When you followed the default installation of Red Hat Developer Studio, you already have a JBoss 4.2 server installed and defined. To run JBoss AS 4.2 you need JDK 1.5. JDK 6 is not formally supported yet, although you may be able to start the server with it.
Starting JBoss server is quite simple. Red Hat Developer Studio allows you control its behaviour through a special toolbar: start it in a regular or debug mode, stop it, or restart it.
To launch the server click the green-with-white-arrow icon on the JBoss Server View or right click server name in this view and select "Start". If this view is not open select Window > Show View > Other > Server > JBoss Server View:
While launching Server output will be written to the Console view:
When server has started you should see "Started" right to its name in JBoss Server view (column "Status").
To see event log after the server is started expand "Event Log" branch beneath JBoss Servers View:
To stop the server click the Stop icon in JBoss Server View or right click the server name and press Stop.
When the server is stopped you will see "Stopped" next to its name in Status column.
You can control how Red Hat Developer Studio interacts with servlet containers in Preferences. Select Window > Preferences > JBoss Tools > JBoss Servers and switch to the desired server:
Also you can double click the server name in JBoss Server view and open an Overview of the server. Here you can specify some common settings: host name, server name, runtime and so on.
Although Red Hat Developer Studio works closely with JBoss EAP 4.2 we do not ultimately tie you to any particular server for deployment. There are some servers that Studio supports directly (through the bundled Eclipse WTP plug-ins). Suppose you want to deploy the application to JBoss 4.2.1 server. First of all you need to install it.
Download the binary package of JBoss 4.2.1 and save it on your computer: http://labs.jboss.com/jbossas/downloads
It does not matter where on your system you install JBoss. Note, however, that installing JBoss into a directory that has a name containing spaces causes problems in some situations with Sun-based VMs. So try to avoid using installation folders that have spaces in their names.
There is no requirement for root access to run JBoss on UNIX/Linux systems because none of the default ports are within the 0-1023 privileged port range.
After you have the binary archive you want to install, use the JDK jar tool (or any other ZIP extraction tool) to extract the jboss-4.2.1.zip archive contents into a location of your choice. The jboss-4.2.1.tgz archive is a gzipped tar file that requires a gnutar compatible tar which can handle the long pathnames in the archive. The extraction process will create a jboss-4.2.1 directory.
Now we should add just installed server into server manager in Red Hat Developer Studio.
Open the JBoss Server View by selecting Window > Show View > Other > Server > JBoss Server View. You will see JBoss Server view.
Right click anywhere in this view and select New Server.
Select JBoss, a division of Red Hat > JBoss v4.2 and click the "Installed Runtimes" button to select a new installed runtime.
Click "Add" button to add a new jboss runtime.
Select JBoss, a division of Red Hat > JBoss v4.2 and press Next.
In the next step make Red Hat Developer Studio to know where you have installed the server and define JRE.
Note:
When adding a new server you will need to specify what JRE to use. It is important to set this value to a full JDK, not JRE. Again, you need a full JDK to run Web applications, JRE will not be enough.
In the following window leave all settings default or give your name to a new jboss server and press Finish.
A new runtime will now appear in the Preferences > Server > Installed Runtimes dialog.
Click OK. Then select a new added runtime in Server runtime drop down list and click Next button twice.
In the last wizard's dialog modify the projects that are configured on the server and click Finish.
A new JBoss server should now appear in JBoss Server View.
