Author: smukhina Date: 2007-10-04 11:35:17 -0400 (Thu, 04 Oct 2007) New Revision: 4008 Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml Log: http://jira.jboss.com/jira/browse/RHDS-160 language correction Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml =================================================================== --- trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml 2007-10-04 14:50:59 UTC (rev 4007) +++ trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml 2007-10-04 15:35:17 UTC (rev 4008) @@ -11,20 +11,20 @@ </keywordset> </chapterinfo> <title>Manage JBoss AS from Red Hat Developer Studio</title> - <para>Red Hat Developer Studio ships with <property>JBoss EAP v.4.2</property> bundled. When you followed the default installation of Red Hat Developer Studio, you already have a <property>JBoss 4.2 server</property> installed and defined. To run <property>JBoss AS 4.2</property> you need JDK 1.5. JDK 6 is not formally supported yet, although you may be able to start the server with it.</para> + <para>Red Hat Developer Studio ships with <property>JBoss EAP v.4.2</property> bundled. When you followed the default installation of Red Hat Developer Studio, you should already have a <property>JBoss 4.2 server</property> installed and defined. To run <property>JBoss AS 4.2</property> you need JDK 1.5., JDK 6 is not formally supported yet, although you may be able to start the server with it.</para> <section id="JBossbundled"> <?dbhtml filename="JBossbundled.html"?> - <title>How to manage the JBoss AS bundled in RHDS</title> + <title>How to Manage the JBoss AS Mundled in RHDS</title> <para></para> <section id="StartingServer"> <?dbhtml filename="StartingServer.html"?> <title>Starting JBoss server</title> - <para>Starting <property>JBoss server</property> 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.</para> + <para>Starting <property>JBoss server</property> is quite simple. Red Hat 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.</para> <itemizedlist> - <listitem><para>To launch the server click the green-with-white-arrow icon on the <property>JBoss Server</property> View or right click server name in this view and select &quot;Start&quot;. If this view is not open select <emphasis>Window &gt; Show View &gt; Other &gt; Server &gt; JBoss Server View</emphasis></para></listitem> + <listitem><para>To launch the server click the green-with-white-arrow icon on the <property>JBoss Server View </property>or right click server name in this view and select <emphasis><property>Start</property></emphasis>. If this view is not open, select <emphasis>Window &gt; Show View &gt; Other &gt; Server &gt; JBoss Server View</emphasis></para></listitem> </itemizedlist> <figure> -<title>Starting from icon</title> +<title>Starting From Icon</title> <mediaobject> <imageobject> <imagedata fileref="images/startingfromicon.png"/> @@ -33,7 +33,7 @@ </figure> <figure> -<title>Starting from JBoss Server view</title> +<title>Starting from JBoss Server View</title> <mediaobject> <imageobject> <imagedata fileref="images/startingfromserversview.png"/> @@ -41,7 +41,7 @@ </mediaobject> </figure> -<para>While launching Server output will be written to the Console view:</para> +<para>While launching, Server output is written to the Console view:</para> <figure> <title>Console output</title> @@ -51,16 +51,16 @@ </imageobject> </mediaobject> </figure> -<para>When server has started you should see &quot;Started&quot; right to its name in <property>JBoss Server</property> view (column &quot;Status&quot;).</para> +<para>When the server is started you should see &quot;Started&quot; right to its name in <property>JBoss Server</property> view (column &quot;Status&quot;).</para> <figure> -<title>Server is started</title> +<title>Server is Started</title> <mediaobject> <imageobject> <imagedata fileref="images/serverstarted.png"/> </imageobject> </mediaobject> </figure> -<para>To see event log after the server is started expand &quot;Event Log&quot; branch beneath <property>JBoss Server</property> View:</para> +<para>To see event log after the server is started, expand &quot;Event Log&quot; branch beneath <property>JBoss Server</property> View:</para> <figure> <title>Event Log</title> <mediaobject> @@ -73,7 +73,7 @@ <section id="StoppingJBoss"> <?dbhtml filename="StoppingJBoss.html"?> <title>Stopping JBoss server</title> - <para>To stop the server click the Stop icon in <property>JBoss Server</property> View or right click the server name and press Stop.</para> + <para>To stop the server, click the <emphasis><property>Stop</property></emphasis> icon in <property>JBoss Server View </property> or right click the server name and press <emphasis><property>Stop</property></emphasis>.</para> <figure> <title>Stopping server</title> <mediaobject> @@ -82,12 +82,12 @@ </imageobject> </mediaobject> </figure> -<para>When the server is stopped you will see &quot;Stopped&quot; next to its name in Status column.</para> +<para>When the server is stopped you will see &quot;Stopped&quot; next to its name in the Status column.</para> </section> <section id="ServerPreferences"> <?dbhtml filename="ServerPreferences.html"?> <title>Server Container Preferences</title> - <para>You can control how Red Hat Developer Studio interacts with servlet containers in Preferences. Select <emphasis>Window &gt; Preferences &gt; JBoss Tools &gt; JBoss Servers</emphasis> and switch to the desired server:</para> + <para>You can control how Red Hat Developer Studio interacts with servlet containers in Preferences. In order to do this, select <emphasis>Window &gt; Preferences &gt; JBoss Tools &gt; JBoss Servers</emphasis> and switch to the desired server:</para> <figure> <title>Server preferences</title> <mediaobject> @@ -96,7 +96,7 @@ </imageobject> </mediaobject> </figure> -<para>Also you can double click the server name in <property>JBoss Server</property> view and open an Overview of the server. Here you can specify some common settings: host name, server name, runtime and so on.</para> +<para>Also you can double click the server name in <property>JBoss Server</property> view and open an overview of the server. Here you can specify some common settings: host name, server name, runtime and so on.</para> <figure> <title>Server overview</title> <mediaobject> @@ -111,15 +111,15 @@ <section id="JBossInstances"> <?dbhtml filename="JBossInstances.html"?> - <title>How to manage JBoss AS instances in RHDS</title> - <para>Although Red Hat Developer Studio works closely with <property>JBoss EAP 4.2</property> 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 <property>JBoss 4.2.1 server</property>. First of all you need to install it.</para> + <title>How to Manage JBoss AS Instances in RHDS</title> + <para>Although Red Hat Developer Studio works closely with <property>JBoss EAP 4.2</property> 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). Suppose you want to deploy the application to <property>JBoss 4.2.1 server</property>. First of all you need to install it.</para> <section id="JBossInstalling"> <?dbhtml filename="JBossInstalling.html"?> <title>JBoss AS Installation</title> <itemizedlist> <listitem><para>Download the binary package of <property>JBoss 4.2.1</property> and save it on your computer: <ulink url="http://labs.jboss.com/jbossas/downloads">http://labs.jb... </itemizedlist> -<para>It does not matter where on your system you install <property>JBoss</property>. Note, however, that installing <property>JBoss</property> 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.</para> +<para>It does not matter where on your system you install <property>JBoss</property>. Note, however, that installing <property>JBoss</property> into a directory that has a name containing spaces causes problems in some situations with Sun-based VMs. Thus, try to avoid using installation folders that have spaces in their names.</para> <para>There is no requirement for root access to run <property>JBoss</property> on UNIX/Linux systems because none of the default ports are within the 0-1023 privileged port range.</para> <itemizedlist continuation="continues"> <listitem><para>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. </para></listitem>