Author: mcaspers
Date: 2011-01-30 20:54:21 -0500 (Sun, 30 Jan 2011)
New Revision: 28739
Modified:
trunk/as/docs/reference/en-US/runtimes_servers.xml
Log:
General Updates
Modified: trunk/as/docs/reference/en-US/runtimes_servers.xml
===================================================================
--- trunk/as/docs/reference/en-US/runtimes_servers.xml 2011-01-31 00:43:03 UTC (rev
28738)
+++ trunk/as/docs/reference/en-US/runtimes_servers.xml 2011-01-31 01:54:21 UTC (rev
28739)
@@ -1,405 +1,372 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="runtimes_servers" xreflabel="runtimes_servers">
- <?dbhtml filename="runtimes_servers.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>JBoss Developer Studio</keyword>
- <keyword>Eclipse</keyword>
- <keyword>Deploy</keyword>
- <keyword>Deployment</keyword>
- <keyword>JBoss</keyword>
- </keywordset>
- </chapterinfo>
- <title>Runtimes and Servers in the JBoss AS plugin</title>
-
- <para>In this chapter we will discuss how to install runtimes and
servers.</para>
-
- <para>First of all it is necessary to mention that the JBoss AS plugin makes use
of WTP.
- This includes starting and stopping servers in run or debug mode. It also includes
targeting WTP
- projects, such as Dynamic Web Projects, to certain server runtimes in order to ensure
that the
- proper jars from a specific server are added to the project's classpath
- properly.</para>
- <para>In order to get started creating, running, and debugging J2EE applications,
we should create
- our <property>runtime</property> and
<property>server</property> instances.</para>
-
- <section>
- <title>Runtimes</title>
- <para>In <property>JBoss Tools</property>, the main purpose of
Server Runtimes is to point to a
- server installation somewhere on disk. In our case, this will be a JBoss
installation, and it
- can then be used for two primary purposes:</para>
- <itemizedlist>
- <listitem>
- <para>it provides classpath additions to WTP projects that require
them.</para>
- </listitem>
- <listitem>
- <para>for <property>JBoss server</property> at least, it
provides information necessary for
- the starting and stopping of the server, it tells which jars to run and which
- configuration to use.</para>
- </listitem>
- </itemizedlist>
- <section id="InstNewRuntime">
- <title>Installing a new runtime</title>
- <para>You can install runtimes into eclipse from the <emphasis>
- <property>Window > Preferences </property>
- </emphasis> menu, and then select <emphasis>
- <property>Server > Runtime Environments</property>
- </emphasis> from the categories available on the left.</para>
- <figure>
- <title>Installed Runtimes</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>From this preference page you can see all declared runtimes and their
types as well.
- Here, it's possible to edit or remove existing runtimes as well as add a
new
- one.</para>
-
- <para>To create a JBoss runtime click <emphasis>
- <property>Add</property>
- </emphasis> button and choose a necessary type of runtime from the
<emphasis>
- <property>JBoss Community</property>
- </emphasis> category.</para>
-
- <figure>
- <title>Adding a Runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_2.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <note>
- <title>Note:</title>
-
- <para>Now there is a separation between .org servers (the <emphasis>
- <property>JBoss Community</property>
- </emphasis> category) and product server that comes with JBoss EAP in
JBDS ( the <emphasis>
- <property>JBoss Enterprise Middleware</property>
- </emphasis> category).</para>
- </note>
-
- <para>As you can see, <property>JBoss Tools</property> provide
its own adapters such as JBoss
- 3.2, 4.0, 4.2 and 5.0 as well. The last one comes with its own new feature, that
is a safer
- incremental deployment, which prevents partial deployments to be picked up by the
server. It
- means that scanning for auto-deployment is suspended while files are being copied
to the
- deployment location and resumed when the copy is completed.</para>
-
- <note>
- <title>Note:</title>
- <para>Currently we recommend you to use a fully supported JBoss 5.0 server
adapter.</para>
- </note>
-
- <para>You'll also note a Deploy-Only Runtime type. This type
provides no classpath
- for WTP projects. It is used solely by its server type for the purpose of setting
up a
- deploy directory for users who don't wish to make use of starting,
stopping, or
- debugging their projects inside eclipse.</para>
-
- <figure id="add_runtime_figure">
- <title>Adding a JBoss 5.0 Runtime</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_3.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>The following table describes all the available options of the currant
wizard
- page.</para>
- <table>
- <title>Server Runtime Wizard Parameters</title>
- <tgroup cols="2">
- <colspec colnum="1" align="left"
colwidth="1*"/>
- <colspec colnum="2" colwidth="3*"/>
-
- <thead>
- <row>
- <entry align="center">
- <para>Name</para>
- </entry>
-
- <entry align="center">
- <para>Description</para>
- </entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry>
- <para>Name</para>
- </entry>
- <entry>
- <para>The name of a new Runtime for a chosen server. We suggest
that you
- don't leave a default value. It's better to give
descriptive
- names that will help to distinguish one runtime from
another.</para>
- </entry>
- </row>
-
- <row>
- <entry>
- <para>Home directory</para>
- </entry>
- <entry>
- <para>The path to a directory where the runtime is
installed.</para>
- </entry>
- </row>
-
- <row>
- <entry>
- <para>JRE</para>
- </entry>
- <entry>
- <para>The proper Java Runtime Environment. Because of the
open-source nature of
- JBoss, a user is likely to want to modify and repackage some of the
- configuration-specific jboss jars and create their own configuration.
Thus, rather
- than forcing you to copy his entire JBoss installation, the structure
of the
- wizard allows to create only a new configuration instead.</para>
- </entry>
- </row>
-
- <row>
- <entry>
- <para>Directory</para>
- </entry>
- <entry>
- <para>The path to a directory where the configurations are
installed.</para>
- </entry>
- </row>
- <row>
- <entry>
- <para>Configuration</para>
- </entry>
- <entry>
- <para>The list of configurations (all, default, minimal) that is
updated as soon as
- you browse to a valid runtime installation folder.</para>
- </entry>
- </row>
-
- </tbody>
- </tgroup>
- </table>
-
- <para>As a result of having each runtime represent a specific configuration
rather than the
- server installation as a whole, it is very likely you'll create several
different
- runtimes to test each of your configurations. It becomes important to ensure your
runtimes,
- and later your servers, are given descriptive names that help you to remember
which is
- which.</para>
-
- <para>Press <emphasis>
- <property>Finish</property>
- </emphasis> to see your new runtime in the list.</para>
- <note>
- <title>Note:</title>
- <para>If you edit the configuration of a runtime, the changes don't
affect the settings of the servers that currently use the runtime.
- To apply the changes to them also,you should double right click the server,
<emphasis>
- <property>Overview>Runtime Environment</property>
</emphasis>
- ,make sure that necessary configuration is chosen,click
<emphasis><property>Finish</property> </emphasis> and then
<emphasis><property>Save</property></emphasis>
button.</para>
- </note>
- </section>
- <section id="Detecting_an_existing_runtime">
- <title>Detecting an existing runtime</title>
- <para>
- JBoss Tools features the ability to search, detect and add existing JBoss server
runtimes installed on your system. If you don't have an existing runtime <xref
linkend="InstNewRuntime"/> will guide you through the creation process. To
begin searching for your existing JBoss runtime navigate to <menuchoice>
- <guimenuitem>Window</guimenuitem>
- <guimenuitem>Preferences</guimenuitem>
- <guimenuitem>JBoss Tools</guimenuitem>
- <guimenuitem>JBoss Runtimes</guimenuitem>
- </menuchoice>.
+ <?dbhtml filename="runtimes_servers.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Deploy</keyword>
+ <keyword>Deployment</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Runtimes and Servers in the JBoss AS plugin</title>
+
+ <para>In this chapter we will discuss how to install runtimes and
servers.</para>
+
+ <para>
+ First of all it is necessary to mention that the JBoss AS plugin makes use of WTP. This
includes starting and stopping servers in run or debug mode. It also includes targeting
WTP projects, such as Dynamic Web Projects, to certain server runtimes in order to ensure
that the proper JARs from a specific server are added to the project's classpath
properly.
+ </para>
+ <para>
+ In order to get started creating, running, and debugging J2EE applications, we should
create our <property>runtime</property> and
<property>server</property> instances.
+ </para>
+
+ <section>
+ <title>Runtimes</title>
+ <para>
+ In <property>JBoss Tools</property>, the main purpose of Server Runtimes
is to point to a server installation somewhere on disk. In our case, this will be a JBoss
installation. It can then be used for two primary purposes:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Providing classpath additions to WTP projects that require
them.</para>
+ </listitem>
+ <listitem>
+ <para>
+ For <property>JBoss server</property> at least, it provides the
necessary information to allow the server to be started and stopped, and provides
information on which JARs to run and which configuration to use.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <section id="InstNewRuntime">
+ <title>Installing a new runtime</title>
+ <para>
+ You can install runtimes into Eclipse by selecting
<menuchoice><guimenuitem>Window</guimenuitem>
+ <guimenuitem>Preferences</guimenuitem>
+ </menuchoice> menu, and then selecting
<menuchoice><guimenuitem>Server</guimenuitem>
+ <guimenuitem>Runtime Environments</guimenuitem>
+ </menuchoice> from the categories available on the left.
+ </para>
+ <figure>
+ <title>Installed Runtimes</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ From this preference page you can see all declared runtimes along with their types.
Here, it is possible to edit or remove existing runtimes, as well as add a new one.
+ </para>
+
+ <para>
+ To create a JBoss runtime click the <guibutton>Add</guibutton> button and
choose the appropriate type of runtime from the <guilabel>JBoss
Community</guilabel> category.
+ </para>
+
+ <figure>
+ <title>Adding a Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <note>
+ <title>Note:</title>
+
+ <para>
+ Now there is a separation between .org servers (the <guilabel>JBoss
Community</guilabel> category) and product server that comes with JBoss EAP in JBDS
( the <guilabel>JBoss Enterprise Middleware</guilabel> category).
+ </para>
+ </note>
+
+ <para>
+ As you can see, <productname>JBoss Tools</productname> provide its own
adapters such as JBoss 3.2, 4.0, 4.2 and 5.0 as well. The last one comes a new safer
incremental deployment feature, which prevents partial deployments to be picked up by the
server. It means that scanning for auto-deployment is suspended while files are being
copied to the deployment location and resumed when the copy is completed.
+ </para>
+
+ <note>
+ <title>Note:</title>
+ <para>Currently we recommend you to use a fully supported JBoss 5.0 server
adapter.</para>
+ </note>
+
+ <para>
+ You will also note a Deploy-Only Runtime type. This type does not provide a classpath
for WTP projects. It is used solely by its server type for the purpose of setting up a
deploy directory for users who do not wish to make use of starting, stopping, or debugging
their projects inside Eclipse.
+ </para>
+
+ <figure id="add_runtime_figure">
+ <title>Adding a JBoss 5.0 Runtime</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>The following table describes all the available options of the currant
wizard page.</para>
+ <table>
+ <title>Server Runtime Wizard Parameters</title>
+ <tgroup cols="2">
+ <colspec colnum="1" align="left"
colwidth="1*"/>
+ <colspec colnum="2" colwidth="3*"/>
+
+ <thead>
+ <row>
+ <entry align="center">
+ <para>Name</para>
+ </entry>
+
+ <entry align="center">
+ <para>Description</para>
+ </entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>
+ The name of a new Runtime for a chosen server. We suggest that you do not leave
the default value for this field. It is better to give descriptive names that will help to
distinguish one runtime from another.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Home directory</para>
+ </entry>
+ <entry>
+ <para>The path to a directory where the runtime is installed.</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>JRE</para>
+ </entry>
+ <entry>
+ <para>
+ The proper Java Runtime Environment. Because of the open-source nature of JBoss,
a user is likely to want to modify and repackage some of the configuration-specific JBoss
JARs and create their own configuration. So rather than forcing you to copy your entire
JBoss installation, the structure of the wizard allows to create a new configuration
instead.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Directory</para>
+ </entry>
+ <entry>
+ <para>The path to a directory where the configurations are
installed.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Configuration</para>
+ </entry>
+ <entry>
+ <para>The list of configurations (all, default, minimal), which is updated
as soon as you browse to a valid runtime installation folder.</para>
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>
+ As a result of having each runtime represent a specific configuration rather than the
server installation as a whole, it is very likely you will create several different
runtimes to test each of your configurations. So it becomes important to ensure your
runtimes, and later your servers, are given descriptive names that help you to remember
which is which.
+ </para>
+
+ <para>Click the <guibutton>Finish</guibutton> button to see your new
runtime in the list.</para>
+ <note>
+ <title>Note:</title>
+ <para>
+ If you edit the configuration of a runtime, the changes don't affect the
settings of the servers that currently use the runtime. To apply the changes to them also,
you should double right click the server, select
<menuchoice><guimenuitem>Overview</guimenuitem>
+ <guimenuitem>Runtime Environment</guimenuitem>
+ </menuchoice>, make sure that necessary configuration is chosen, click the
<guibutton>Finish</guibutton> button and then
<guibutton>Save</guibutton> button.
+ </para>
+ </note>
+ </section>
+ <section id="Detecting_an_existing_runtime">
+ <title>Detecting an existing runtime</title>
+ <para>
+ JBoss Tools features the ability to search, detect and add existing JBoss server
runtimes installed on your system. If you don't have an existing runtime <xref
linkend="InstNewRuntime"/> will guide you through the creation process. To
begin searching for your existing JBoss runtime select
<menuchoice><guimenuitem>Window</guimenuitem>
+ <guimenuitem>Preferences</guimenuitem>
+ <guimenuitem>JBoss Tools</guimenuitem>
+ <guimenuitem>JBoss Runtimes</guimenuitem>
+ </menuchoice>.
</para>
- <figure>
- <title>Preference page for JBoss Runtimes</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers-detecting_new_runtime_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>
+ <figure>
+ <title>Preference page for JBoss Runtimes</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers-detecting_new_runtime_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
The JBoss Runtimes preference page allows you to perform three different actions:
<guibutton>Search</guibutton> for a JBoss runtime installation,
<guibutton>Export</guibutton> a JBoss runtime configuration and
<guibutton>Import</guibutton> the configuration of a JBoss runtime.
</para>
- <para>
- The <guibutton>Search</guibutton> button opens a file system browser
window. Select a directory where you wish JBoss Tools to begin recursively searching for
JBoss runtimes and upon completion it will return all those found. From the returned list,
choose the runtimes you wish to make available to your JBoss Tools instance by clicking
the box beside each runtime and clicking the <guibutton>OK</guibutton>
button.
+ <para>
+ The <guibutton>Search</guibutton> button opens a file system browser
window. Select the directory where you wish JBoss Tools to begin recursively searching for
JBoss runtimes and upon completion it will return all those found. From the returned list,
choose the runtimes you wish to make available to your JBoss Tools instance by clicking
the box beside each runtime and clicking the <guibutton>OK</guibutton>
button.
</para>
- <figure>
- <title>JBoss Runtime search results</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers-detecting_new_runtime_2.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="Exporting_and_Importing_runtime_preferences">
- <title>Exporting and Importing runtime preferences</title>
- <para>
- The <guimenuitem>JBoss Runtimes</guimenuitem>
<guilabel>Preferences</guilabel> interface seen in <xref
linkend="Detecting_an_existing_runtime"/> also allows you to export and
import your runtime preferences. You can navigate to the page through
<menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>JBoss
Tools</guimenuitem><guimenuitem>JBoss
Runtimes</guimenuitem></menuchoice>.
+ <figure>
+ <title>JBoss Runtime search results</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers-detecting_new_runtime_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="Exporting_and_Importing_runtime_preferences">
+ <title>Exporting and Importing runtime preferences</title>
+ <para>
+ The <guimenuitem>JBoss Runtimes</guimenuitem>
+ <guilabel>Preferences</guilabel> interface seen in <xref
linkend="Detecting_an_existing_runtime"/> also allows you to export and
import your runtime preferences. You can navigate to the page by selecting
<menuchoice><guimenuitem>Window</guimenuitem>
+ <guimenuitem>Preferences</guimenuitem>
+ <guimenuitem>JBoss Tools</guimenuitem>
+ <guimenuitem>JBoss Runtimes</guimenuitem>
+ </menuchoice>.
</para>
- <para>
- The <guibutton>Export</guibutton> button opens the <guilabel>Export
Preferences</guilabel> dialog. The <guilabel>Export all</guilabel> box
will automatically be selected, however you can choose to only export specific preference
settings (such as only those related to your JBoss runtime) by selecting individual
entries from the displayed list.
+ <para>
+ The <guibutton>Export</guibutton> button opens the <guilabel>Export
Preferences</guilabel> dialog. The <guilabel>Export all</guilabel> box
will automatically be selected, however you can choose to only export specific preference
settings (such as only those related to your JBoss runtime) by selecting individual
entries from the displayed list.
</para>
- <figure>
- <title>Export Preferences dialog</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers-export_runtime_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>
- To export the preference settings you must specify a preference file that the
information will be written to. This file, once exported, can be used to reapply your
settings by clicking on the <guilabel>Import</guilabel> button.
+ <figure>
+ <title>Export Preferences dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers-export_runtime_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ To export the preference settings you must specify the preference file that the
information will be written to. This file, once exported, can be used to reapply your
settings by clicking on the <guilabel>Import</guilabel> button.
</para>
- <para>
- The <guibutton>Import</guibutton> button opens the <guilabel>Import
Preferences</guilabel> dialog. The <guilabel>Import all</guilabel> box
will automatically be selected, however you can choose to only import specific preference
settings (such as only those related to your JBoss runtime) by selecting individual
entries from the list that displays after using the
<guibutton>Browse</guibutton> button to select your exported preference file
(for example: preference_file.epf).
+ <para>
+ The <guibutton>Import</guibutton> button opens the <guilabel>Import
Preferences</guilabel> dialog. The <guilabel>Import all</guilabel> box
will automatically be selected, however you can choose to only import specific preference
settings (such as only those related to your JBoss runtime) by selecting individual
entries from the list that displays after using the
<guibutton>Browse</guibutton> button to select your exported preference file
(for example: preference_file.epf).
</para>
- <figure>
- <title>Import Preferences dialog</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers-import_runtime_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </section>
- <section id="CopyRuntime">
- <title>Duplicating a runtime configuration</title>
- <para>While installing a new runtime you can copy the configuration from the
existing one.
- To do this you should perform all the steps in the <link
linkend="InstNewRuntime">previous</link> section except pressing
<emphasis>
- <property>Finish</property></emphasis>
- in the New Server Runtime Environment menu .
+ <figure>
+ <title>Import Preferences dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers-import_runtime_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </section>
+ <section id="CopyRuntime">
+ <title>Duplicating a runtime configuration</title>
+ <para>
+ While installing a new runtime you can copy the configuration from the existing one.
To do this you should perform all the steps in <xref
linkend="InstNewRuntime"/>, with the exception of clicking the
<guibutton>Finish</guibutton> button in the New Server Runtime Environment
menu.
</para>
- <para>Make sure that you browse to a valid runtime folder and can see the
list of configurations (all, default, minimal) in the Configuration section .
- Then choose necessary Configuration from the list and click <emphasis>
- <property>Copy</property></emphasis>.The next dialog should
appear.
+ <para>
+ Make sure that you browse to a valid runtime folder and can see the list of
configurations (all, default, minimal) in the Configuration section. Then choose
appropriate Configuration from the list and click the
<guibutton>Copy</guibutton> button.The next dialog should appear.
</para>
- <figure>
- <title>Copy the existing configuration</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_4a.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>Change the name Click on <emphasis>
- <property>Browse</property></emphasis> and select your
configuration location or leave as it's if you want it to be located together with
other runtime configurations.
+ <figure>
+ <title>Copy the existing configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers_4a.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ Change the name, click the <guibutton>Browse</guibutton> button, and
select your configuration location or leave as it is if you want it to be located together
with other runtime configurations.
</para>
- <figure>
- <title>Copy the existing configuration</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_4b.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Click<emphasis>
- <property> Ok </property></emphasis>and you should see the next
wizard with the just added copied configuration.
-
+ <figure>
+ <title>Copy the existing configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers_4b.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click the <guibutton>OK</guibutton> button and you should see
the next wizard with the newly copied configuration.</para>
+ <figure>
+ <title>Runtime with copied configuration</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers_4c.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para> Click the <guibutton>Finish</guibutton> button and you will
see your new runtime in the list.
</para>
- <figure>
- <title>Runtime with copied configuration</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_4c.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para> Press <emphasis>
- <property>Finish</property>
- </emphasis> and you will see your new runtime in the list.
+ <para>
+ You can also change the configuration of existing runtime to a copied one in the same
way by selecting
<menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>Server</guimenuitem><guimenuitem>Runtime
Environments</guimenuitem></menuchoice> and clicking the
<guibutton>Edit</guibutton> button.
</para>
- <para>You can also change a configuration of existing runtime to a copied one
in the same way from the <emphasis>
- <property> Window > Preferences </property></emphasis>
- menu <emphasis>
- <property>Server > Runtime Environments
</property></emphasis>
- and clicking <emphasis>
- <property>Edit</property></emphasis>.
- </para>
- </section>
- </section>
- <section>
- <title>Servers</title>
- <para>WTP servers are eclipse-representations of a backing server installation.
They are used to
- start or stop servers, deploy to servers, or debug code that will run on the
server. They keep
- track of the modules (jars, wars, etc) you deploy to the server and also allow you
to undeploy
- those modules (see <link linkend="run_on_server_wizard">Deploying
with Run On Server
- Wizard</link> section). </para>
- <para>Servers can be started or stopped with different <link
linkend="com_line_arg">command-line
- arguments</link>. They are often backed by a runtime object representing
that server's
- location.</para>
+ </section>
+ </section>
+ <section>
+ <title>Servers</title>
+ <para>
+ WTP servers are Eclipse-representations of a back end server installation. They are
used to start or stop servers, deploy to servers, or debug code that will run on the
server. They keep track of the modules (JARs, WARs, etc) you deploy to the server, and
also allow you to undeploy those modules (see <xref
linkend="run_on_server_wizard"/>).
+ </para>
+ <para>
+ Servers can be started or stopped with different <link
linkend="com_line_arg">command-line arguments</link>. They are often
backed by a runtime object representing that server's location.
+ </para>
+
+ <section>
+ <title>Creating a New Server</title>
+
+ <para>
+ There are many ways to get to the new server wizard. One way is to select
<menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other...</guimenuitem><guimenuitem>Server</guimenuitem></menuchoice>.
This should show the wizard like below.
+ </para>
+ <figure>
+ <title>Adding a JBoss Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>
+ A server object keeps track of things like command line arguments when starting or
stopping, and the runtimes keep track of the location of the installation. Thus, each
server instance must be backed by an appropriate runtime.
+ </para>
+
+ <para>
+ The <guilabel>New server wizard</guilabel> allows you to name the server
via the <guilabel>Server name</guilabel> field, or you can use a generated
default name .If it is necessary to restore the default name, click the
<guibutton>Reset default</guibutton> button (<inlinemediaobject>
<imageobject><imagedata
fileref="images/runtimes_servers/runtimes_servers_4d.png"/></imageobject></inlinemediaobject>).
+ </para>
+ <para>
+ You can select the appropriate runtime you from the <guilabel>Server runtime
environment</guilabel> combobox. If there is no runtime that matches your needs just
press the <guilabel>Add...</guilabel> link nearby to bring up the wizard for
creating a new runtime (see <xref linkend="add_runtime_figure"/>). To
configure an existing runtimes you should go to server preferences by pressing the
<guilabel>Configure runtime environments...</guilabel> link.
+ </para>
+
+ <para>If the server you want to create does not have any installed runtime yet,
the combo box and the links are absent.</para>
+
+ <figure>
+ <title>Installed Server Runtime Environments</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ In this case the next page of the wizard which has the same form as in <link
linkend="add_runtime_figure">the previous section</link>, and will ask
you to create the associated runtime.
+ </para>
+ <para>
+ Either way, after targeting your server to a runtime, the final screen in this wizard
presents a summary of the selected options, giving you a chance to verify that you have
selected the appropriate runtime.
+ </para>
+
+ <figure>
+ <title>Installed Server Runtime Environments</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
fileref="images/runtimes_servers/runtimes_servers_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>Click the <guibutton>Finish</guibutton> button to complete the
process of the server creation.</para>
+ <para>Now that we have created our runtimes and servers, we can explore the
services and tools provided by the JBoss Server Manager.</para>
+
+ <para>
+ We hope this guide helped you to get started with the JBoss Tools server manager. For
additional information you are welcome on <ulink
url="http://www.jboss.com/index.html?module=bb&op=viewforum&...
forum</ulink>.
+ </para>
+ </section>
+ </section>
- <section>
- <title>Creating a New Server</title>
- <para>There are many ways to get to the new server wizard. One way is to use
the old standard <emphasis>
- <property>File > New > Other... </property>
- </emphasis> and then <emphasis>
- <property>Server</property>
- </emphasis>. This should show the wizard like below.</para>
- <figure>
- <title>Adding a JBoss Server</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_4.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>A server object is that keeps track of things like command line
arguments when starting
- or stopping, and runtimes keep track of the location of the installation. Thus,
each server
- instance must be backed by an appropriate runtime. </para>
-
- <para> <emphasis><property> New server wizard
</property></emphasis> allows to name the server appropriately in the
<emphasis><property>Server name field </property></emphasis >or
you can use a generated default name.If it's nessecary to restore the default
name,after you defined yours, click the Reset default button(<inlinemediaobject>
<imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_4d.png"/>
- </imageobject></inlinemediaobject>).
- From the list of already declared runtimes in the combo box below the view
it's
- possible to select which runtime you want your server to be backed by. If there
is no
- runtime that matches your needs just press the <emphasis>
- <property>Add...</property>
- </emphasis> link nearby to bring up the wizard for creating a new runtime
(see the <link
- linkend="add_runtime_figure">Installing a New Runtime
section</link>). To configure the already installed
- runtimes you should go to server preferences that you can easily do by pressing
the <emphasis>
- <property>Configure runtime
environments...</property></emphasis> link.</para>
-
- <para>If the server you want to create doesn't have any installed
runtime yet, the combo box
- and the links are absent.</para>
-
- <figure>
- <title>Installed Server Runtime Environments</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_6.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>In this case the next page in the wizard which has the same form as in
<link
- linkend="add_runtime_figure">the previous section</link>
will ask you to create the
- associated runtime.</para>
- <para>Either way, after targeting your server to a runtime, the final screen
in this wizard is
- largely confirmational, giving you a chance to verify that you've
selected the
- appropriate runtime. </para>
-
- <figure>
- <title>Installed Server Runtime Environments</title>
- <mediaobject>
- <imageobject>
- <imagedata
fileref="images/runtimes_servers/runtimes_servers_7.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>Press <emphasis>
- <property>Finish</property>
- </emphasis> to complete the process of the server creation.</para>
- <para>Now that we've created our runtimes and servers, we can dwell
on all services
- and tools that JBoss Server Manager provides.</para>
-
- <para>We hope, this guide helped you to get started with the JBoss Tools
server manager. Besides, for additional information you are welcome on <ulink
-
url="http://www.jboss.com/index.html?module=bb&op=viewforum&...
forum</ulink>.</para>
- </section>
- </section>
-
-
</chapter>