Author: ochikvina Date: 2009-02-13 09:22:50 -0500 (Fri, 13 Feb 2009) New Revision: 13613 Modified: trunk/as/docs/reference/en/modules/runtimes_servers.xml Log: https://jira.jboss.org/jira/browse/JBDS-616 - adding the info on separation of .org and product styles; Modified: trunk/as/docs/reference/en/modules/runtimes_servers.xml =================================================================== --- trunk/as/docs/reference/en/modules/runtimes_servers.xml 2009-02-13 14:21:40 UTC (rev 13612) +++ trunk/as/docs/reference/en/modules/runtimes_servers.xml 2009-02-13 14:22:50 UTC (rev 13613) @@ -17,15 +17,16 @@ <para>First of all it&apos;s 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&apos;s classpath properly.</para> + proper jars from a specific server are added to the project&apos;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 JBoss Tools, 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> + <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> @@ -38,12 +39,12 @@ </itemizedlist> <section id="InstNewRuntime"> - <title>Installing a new Runtime</title> + <title>Installing a New Runtime</title> <para>You can install runtimes into eclipse from the <emphasis> - <property>Window &gt; Preferences... </property> + <property>Window &gt; Preferences </property> </emphasis> menu, and then select <emphasis> - <property>Server &gt; Installed Runtimes</property> - </emphasis> from the categories available.</para> + <property>Server &gt; Runtime Environments</property> + </emphasis> from the categories available on the left.</para> <figure> <title>Installed Runtimes</title> <mediaobject> @@ -53,12 +54,14 @@ </mediaobject> </figure> <para>From this preference page you can see all declared runtimes and their types as well. - Figure above shows two declared runtimes that include a JBoss 4.2 instance. Here, - it&apos;s possible to edit or remove existing runtimes as well as add a new one.</para> + Here, it&apos;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 appeared dialog. </para> + </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> @@ -69,12 +72,22 @@ </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 4.2 server adapter.</para> @@ -94,7 +107,8 @@ </mediaobject> </figure> - <para>The following table describes all the available options of the wizard.</para> + <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"> @@ -167,7 +181,8 @@ <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&apos;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 remember which is which.</para> + and later your servers, are given descriptive names that help you remember which is + which.</para> <para>Press <emphasis> <property>Finish</property> @@ -182,14 +197,14 @@ 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> + 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> - + 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 use the old standard <emphasis> <property>File &gt; New &gt; Other... </property> </emphasis> and then <emphasis> @@ -209,24 +224,16 @@ <para>From the list of already declared runtimes in the combo box below the view it&apos;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 <emphasis> - <property>Installed Runtimes... </property> - </emphasis> to bring up the familiar preference page like in <link linkend="InstNewRuntime"> - the previous section</link>. Here, it becomes possible to edit already existing runtime or - add a new one with necessary configuration.</para> + 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">previous 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> - <figure> - <title>Installed Server Runtime Environments</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_5.png"/> - </imageobject> - </mediaobject> - </figure> + <para>If the server you want to create doesn&apos;t have any installed runtime yet, the combo box + and the links are absent.</para> - <para>If the server you want to create doesn't have any installed runtime yet, the combo box - and button will disappear.</para> - <figure> <title>Installed Server Runtime Environments</title> <mediaobject>