Create new JBDS Documentation Jira issue
This will launch the JBDS Jira page - to complete your feedback please login if needed, and submit the Jira.
JBoss.comEnterprise Documentation
In this chapter we'll focus more on how to operate the JBoss AS from JBoss Developer Studio.
JBoss Developer Studio 2.1.0.GA is shipped with JBoss EAP 5 . When you followed the default installation of JBoss Developer Studio, you should already have a JBoss EAP 5 Server installed and defined. To run JBoss AS you need JDK 1.5, JDK 6 is not formally supported yet, although you may be able to start the server with it.
This section covers the basics of working with the JBoss Server supported directly by JBDS via bundled AS plug-in. The server points to the JBoss Enterprise Application Platform 5.0 Runtime shipped with JBDS.
To read more about AS plug-in, refer to the Server Manager guide.
Starting JBoss Server is quite simple. JBoss Developer Studio allows you to control its behaviour with the help of a special toolbar, where you could 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 is written to the Console view:
When the server is started you should see Started in the square brackets right next its name in JBoss Server 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 in the square brackets next to its name.
You can control how JBoss Developer Studio interacts with server containers in the Server editor. Double-click the server to open it in the editor.
Here you can specify some common settings: host name, server name, runtime as well as settings related to the publishing, timeouts and server ports.
Although JBoss Developer Studio works closely with JBoss EAP 5 we do not ultimately tie you to any particular server for deployment. There are some servers that Studio supports directly (via the bundled Eclipse WTP plug-ins). In this section we discuss how to manage self-installed JBoss AS. Suppose you want to deploy the application to JBoss 4.2.3 server. First of all you need to install it.
Download the binary package of JBoss AS, e.g. JBoss 4.2.3 and save it on your computer: http://labs.jboss.com/jbossas/downloads
It does not matter where on your system you install JBoss server.
The installation of JBoss server into a directory that has a name containing spaces provokes problems in some situations with Sun-based VMs. Try to avoid using installation folders that have spaces in their names.
There is no requirement for root access to run JBoss Server 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.3.GA.zip archive contents into a location of your choice. The jboss-4.2.3.GA.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.3.GA directory.
Now we should add just installed server into server manager in JBoss Developer Studio.
Open the JBoss Server View by selecting Window > Show View > Other > Server > JBoss Server View
Right click anywhere in this view and select New Server
Select JBoss Community > JBoss 4.2 Server
Now in the New Server wizard there is a separation between the .org servers (the JBoss Community category) and product server that comes bundled with JBoss EAP (the JBoss Enterprise Middleware category).
To create a new runtime, which Jboss AS 4.2 matches to, click Next
In the next step make JBoss Developer Studio to know where you have installed the Server and define JRE.
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 next dialog verify the specified information and if something is unfair go back and correct it
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 the JBoss Server view.
Now, we are ready to create the first web application.
