Author: mcaspers Date: 2011-01-13 17:16:26 -0500 (Thu, 13 Jan 2011) New Revision: 28205 Modified: trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/eap5runtime.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_1.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_11.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_15.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_16.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_17.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_3.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_4.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_6.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_8.png trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_9.png trunk/documentation/guides/GettingStartedGuide/en-US/manage.xml Log: Updates for JBDS 4.0 Modified: trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml =================================================================== --- trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml 2011-01-13 21:54:50 UTC (rev 28204) +++ trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml 2011-01-13 22:16:26 UTC (rev 28205) @@ -858,21 +858,12 @@ <section id="Upgrading"> <?dbhtml filename="Upgrading.html"?> <title>Upgrading</title> - <para>As opposed to upgrading your JBDS from 2.0 to 2.1 using the update site, - to upgrade your JBDS from 2.1 to 3.0 you have to uninstall your 2.1 version and install the new one - because of some platform change.</para> -<!-- - <para>Now it&apos;s possible to upgrade from JBDS 2.0 to 2.1 using the update site - which is available at <ulink url="is available at - http://devstudio.jboss.com/updates/2.1">http://devstudio.jboss.co...;. - This is described more fully in the - <ulink url="http://www.jboss.com/products/devstudio/update/">JBDS Update Guide</ulink>.</para> + <para>Because JBDS 3.0x and 4.0 use different versions of Eclipse, it is not possible to directly upgrade from an older version to JBDS 4.0.</para> <note> - <title>Note:</title> - <para>You <emphasis><property>CAN NOT</property></emphasis> upgrade from 2.1 to 3.0 using update site because of some platform change. - Full installation is required.</para> - </note> ---> + <title>Tip</title> + <para>It is possible to run JBDS 3.0x and 4.0 side by side, as long as they have been installed into separate directories.</para> + </note> + </section> <section id="Uninstalling"> @@ -901,7 +892,7 @@ <caption>Usage plug-in pop-up</caption> </mediaobject> <para> - Once enabled, the plug-in will remain active until turned off. To turn the active plug-in off, navigate to <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>JBoss Tools</guimenuitem><guimenuitem>Usage Reporting Preferences</guimenuitem></menuchoice>. + Once enabled, the plug-in will remain active until turned off. To turn the active plug-in off, navigate to <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>JBoss Tools</guimenuitem><guimenuitem>Usage Reporting</guimenuitem></menuchoice>. </para> <para> The gathered data allows JBoss to see how the tools are being used and where they are being used geographically. Currently we are looking into the operating systems being used, screen resolution and how often the tooling environment is started. In the future geographic information will assist in focussing translation resources to areas where the developer environment is most used. Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/eap5runtime.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_1.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_11.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_15.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_16.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_17.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_3.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_4.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_6.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_8.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/images/manage/manage_9.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/GettingStartedGuide/en-US/manage.xml =================================================================== --- trunk/documentation/guides/GettingStartedGuide/en-US/manage.xml 2011-01-13 21:54:50 UTC (rev 28204) +++ trunk/documentation/guides/GettingStartedGuide/en-US/manage.xml 2011-01-13 22:16:26 UTC (rev 28205) @@ -1,98 +1,99 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="manage"> - <?dbhtml filename="manage.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Developer Studio</keyword> - <keyword>Eclipse</keyword> - <keyword>Deploy</keyword> - <keyword>Deployment</keyword> - <keyword>JBoss</keyword> - </keywordset> - </chapterinfo> + <?dbhtml filename="manage.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>Deploy</keyword> + <keyword>Deployment</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> - <title>Manage JBoss AS from JBoss Developer Studio</title> + <title>Manage JBoss AS from JBoss Developer Studio</title> - <para>In this chapter we&apos;ll focus more on how to operate the <property>JBoss + <para>In this chapter we&apos;ll focus more on how to operate the <property>JBoss AS</property> from <property>JBoss Developer Studio</property>.</para> - <para><property>JBoss Developer Studio 3.0.0.GA</property> is shipped with <property>JBoss EAP 5 - </property>. When you followed the default installation of <property>JBoss - Developer Studio</property>, you should already have a JBoss EAP 5 Server installed and - defined. To run JBoss AS you need preinstalled JDK 6.</para> - <note> - <title>Note:</title> - <para>You can leave <property>JDK 1.5</property> configuration for <property>JBDS</property> and set <property>JDK 6</property> as <property>JRE</property> only for <property>JBoss EAP Server</property>. For this you need on <emphasis><property>Windows > Preferences</property></emphasis> menu click <emphasis><property>Server > Runtime Enviroments</property></emphasis>. On the opened preference page you should select <property>JBoss EAP Runtime</property> and click <property>Edit</property>. In <property>Edit Server Runtime Enviroment</property> dialog you can configure <property>Jave Runtime Enviroment</property> by clicking <property>JRE</property> button. </para> - </note> + <para> + <property>JBoss Developer Studio 4.0.0.GA</property> is shipped with <property>JBoss EAP 5.1</property>. When you followed the default installation of <property>JBoss + Developer Studio</property>, you should already have a JBoss EAP 5.1 Server installed and defined. To run JBoss AS you need you will need to have JDK 6 installed.</para> + <note> + <title>Note:</title> + <para>You can leave <property>JDK 1.5</property> configuration for <property>JBDS</property> and set <property>JDK 6</property> as <property>JRE</property> only for <property>JBoss EAP Server</property>. For this you need on <emphasis><property>Windows > Preferences</property> + </emphasis> menu click <menuchoice><guimenuitem>Server</guimenuitem><guimenuitem>Runtime Environments</guimenuitem></menuchoice>. On the opened preference page you should select <property>JBoss EAP Runtime</property> and click <property>Edit</property>. In <property>Edit Server Runtime Environment</property> dialog you can configure <property>Jave Runtime Environment</property> by clicking <property>JRE</property> button. </para> + </note> - <section id="JBossbundled"> - <?dbhtml filename="JBossbundled.html"?> - <title>How to Manage the JBoss AS Bundled in JBDS</title> - <para>This section covers the basics of working with the <property>JBoss Server</property> + <section id="JBossbundled"> + <?dbhtml filename="JBossbundled.html"?> + <title>How to Manage the JBoss AS Bundled in JBDS</title> + <para>This section covers the basics of working with the <property>JBoss Server</property> supported directly by <property>JBDS</property> via bundled AS plug-in. The server points to - the JBoss Enterprise Application Platform 5.0 Runtime shipped with <property>JBDS</property>.</para> + the JBoss Enterprise Application Platform 5.1 Runtime shipped with <property>JBDS</property>.</para> - <figure> - <title>JBoss EAP 5.0 Runtime</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/eap5runtime.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>To read more about AS plug-in, refer to the Server Manager guide.</para> - <section id="StartingServer"> - <?dbhtml filename="StartingServer.html"?> - <title>Starting JBoss Server</title> - <para>Starting <property>JBoss Server</property> is quite simple. <property>JBoss - Developer Studio</property> allows you to control its behaviour with the help of + <figure> + <title>JBoss EAP 5.1 Runtime</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/eap5runtime.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>To read more about AS plug-in, refer to the Server Manager guide.</para> + <section id="StartingServer"> + <?dbhtml filename="StartingServer.html"?> + <title>Starting JBoss Server</title> + <para>Starting <property>JBoss Server</property> is quite simple. <property>JBoss + Developer Studio</property> allows you to control its behavior 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 + <itemizedlist> + <listitem> + <para>To launch the server click the green-with-white-arrow icon on the <property>Servers</property> or right click server name in this view and select <emphasis> <property>Start</property> - </emphasis>. If this view is not open, select <emphasis> + </emphasis>. If this view is not open, select <emphasis> <property>Window &gt; Show View &gt; Other &gt; Server &gt; Servers</property> - </emphasis></para> - </listitem> - </itemizedlist> - <figure> - <title>Starting from Icon</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_1.png"/> - </imageobject> - </mediaobject> - </figure> + </emphasis> + </para> + </listitem> + </itemizedlist> + <figure> + <title>Starting from Icon</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_1.png"/> + </imageobject> + </mediaobject> + </figure> - <para>While launching, server output is written to the <property>Console + <para>While launching, server output is written to the <property>Console view</property>:</para> - <figure> - <title>Console Output</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_3.png"/> - </imageobject> - </mediaobject> - </figure> - <para>When the server is started you should see <emphasis> + <figure> + <title>Console Output</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>When the server is started you should see <emphasis> <property>Started</property> - </emphasis> in the square brackets right next its name in <property>Servers</property>.</para> + </emphasis> in the square brackets right next its name in <property>Servers</property>.</para> - <figure> - <title>Server is Started</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_4.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Server is Started</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_4.png"/> + </imageobject> + </mediaobject> + </figure> <!--para>To see event log after the server is started, expand <property>Event Log</property> branch beneath <property>Servers</property>:</para> <figure> @@ -103,207 +104,210 @@ </imageobject> </mediaobject> </figure--> - </section> + </section> - <section id="StoppingJBoss"> - <?dbhtml filename="StoppingJBoss.html"?> - <title>Stopping JBoss Server</title> - <para>To stop the server, click the <emphasis> + <section id="StoppingJBoss"> + <?dbhtml filename="StoppingJBoss.html"?> + <title>Stopping JBoss Server</title> + <para>To stop the server, click the <emphasis> <property>Stop</property> - </emphasis> icon in <property>Servers</property> or right click the server + </emphasis> icon in <property>Servers</property> or right click the server name and press <emphasis> - <property>Stop</property>. </emphasis></para> + <property>Stop</property>. </emphasis> + </para> - <figure> - <title>Stopping Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_6.png"/> - </imageobject> - </mediaobject> - </figure> - <para>When the server is stopped you will see <emphasis> + <figure> + <title>Stopping Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_6.png"/> + </imageobject> + </mediaobject> + </figure> + <para>When the server is stopped you will see <emphasis> <property>Stopped</property> - </emphasis> in the square brackets next to its name.</para> - </section> - <section id="ServerPreferences"> - <?dbhtml filename="ServerPreferences.html"?> - <title>Server Container Preferences</title> - <para>You can control how <property>JBoss Developer Studio</property> interacts with + </emphasis> in the square brackets next to its name.</para> + </section> + <section id="ServerPreferences"> + <?dbhtml filename="ServerPreferences.html"?> + <title>Server Container Preferences</title> + <para>You can control how <property>JBoss Developer Studio</property> interacts with server containers in the <property>Server editor</property>. Double-click the server to open it in the editor.</para> - <figure> - <title>Server Overview</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_8.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Server Overview</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_8.png"/> + </imageobject> + </mediaobject> + </figure> - <para>Here you can specify some common settings: host name, server name, runtime as well + <para>Here you can specify some common settings: host name, server name, runtime as well as settings related to the publishing, timeouts and server ports.</para> - </section> - </section> + </section> + </section> - <section id="JBossInstances"> - <?dbhtml filename="JBossInstances.html"?> - <title>How to Use Your Own JBoss AS Instance with JBDS</title> - <para>Although <property>JBoss Developer Studio</property> works closely with + <section id="JBossInstances"> + <?dbhtml filename="JBossInstances.html"?> + <title>How to Use Your Own JBoss AS Instance with JBDS</title> + <para>Although <property>JBoss Developer Studio</property> works closely with <property>JBoss EAP 5</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). In this section we discuss how to manage self-installed JBoss AS. Suppose you want to deploy the application to <property>JBoss 4.2.3 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 JBoss AS, e.g. <property>JBoss 4.2.3</property> and save - it on your computer: <ulink url="http://labs.jboss.com/jbossas/downloads" - >http://labs.jboss.com/jbossas/downloads</ulink></para> - </listitem> - </itemizedlist> - <para>It does not matter where on your system you install JBoss server.</para> + <section id="JBossInstalling"> + <?dbhtml filename="JBossInstalling.html"?> + <title>JBoss AS Installation</title> + <itemizedlist> + <listitem> + <para>Download the binary package of JBoss AS, e.g. <property>JBoss 4.2.3</property> and save + it on your computer: <ulink url="http://labs.jboss.com/jbossas/downloads">http://labs.jb... + </para> + </listitem> + </itemizedlist> + <para>It does not matter where on your system you install JBoss server.</para> - <note> - <title>Note:</title> - <para>The installation of JBoss server into a directory that has a name containing + <note> + <title>Note:</title> + <para>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.</para> - </note> + </note> - <para>There is no requirement for root access to run JBoss Server on UNIX/Linux systems + <para>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.</para> - <itemizedlist> - <listitem> - <para>After you have the binary archive you want to install, use the JDK jar + <itemizedlist> + <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.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. </para> - </listitem> - </itemizedlist> - </section> + </listitem> + </itemizedlist> + </section> - <section id="AddingJBossServer"> - <?dbhtml filename="AddingJBossServer.html"?> - <title>Adding and Configuring JBoss Server</title> - <para>Now we should add just installed server into server manager in <property>JBoss + <section id="AddingJBossServer"> + <?dbhtml filename="AddingJBossServer.html"?> + <title>Adding and Configuring JBoss Server</title> + <para>Now we should add just installed server into server manager in <property>JBoss Developer Studio</property>.</para> - <itemizedlist> - <listitem> - <para>Open the <property>Servers</property> by selecting <emphasis> - <property>Window &gt; Show View &gt; Other &gt; Server - &gt; Servers</property> - </emphasis></para> - </listitem> - <listitem> - <para>Right click anywhere in this view and select <emphasis> - <property>New Server</property> - </emphasis></para> - </listitem> - <listitem> - <para>Select <emphasis> + <itemizedlist> + <listitem> + <para>Select <property>Servers</property> by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>Server</guimenuitem><guimenuitem>Servers</guimenuitem></menuchoice>. + </emphasis> + </para> + </listitem> + <listitem> + <para>Right click anywhere in this view and select <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>Server</guimenuitem></menuchoice>. + </emphasis> + </para> + </listitem> + <listitem> + <para>Select <emphasis> <property>JBoss Community &gt; JBoss 4.2 Server</property> - </emphasis></para> - </listitem> - </itemizedlist> - <figure> - <title>Selecting Server Name and Server Type</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_9.png"/> - </imageobject> - </mediaobject> - </figure> + </emphasis> + </para> + </listitem> + </itemizedlist> + <figure> + <title>Selecting Server Name and Server Type</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_9.png"/> + </imageobject> + </mediaobject> + </figure> - <note> - <title>Note:</title> + <note> + <title>Note:</title> - <para>Now in the <property>New Server wizard</property> there is a separation + <para>Now in the <property>New Server wizard</property> there is a separation between the .org servers (the <emphasis> <property>JBoss Community</property> - </emphasis> category) and product server that comes bundled with JBoss EAP (the + </emphasis> category) and product server that comes bundled with JBoss EAP (the <emphasis> - <property>JBoss Enterprise Middleware</property></emphasis> category).</para> - </note> + <property>JBoss Enterprise Middleware</property> + </emphasis> category).</para> + </note> - <itemizedlist> - <listitem> - <para>To create a new runtime, which Jboss AS 4.2 matches to, click <emphasis> + <itemizedlist> + <listitem> + <para>To create a new runtime, which Jboss AS 4.2 matches to, click <emphasis> <property>Next</property> - </emphasis></para> - </listitem> - </itemizedlist> + </emphasis> + </para> + </listitem> + </itemizedlist> - <itemizedlist> - <listitem> - <para>In the next step make <property>JBoss Developer Studio</property> to know + <itemizedlist> + <listitem> + <para>In the next step make <property>JBoss Developer Studio</property> to know where you have installed the Server and define JRE.</para> - </listitem> - </itemizedlist> - <figure> - <title>Defining JBoss Runtime</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_11.png"/> - </imageobject> - </mediaobject> - </figure> - <note> - <title>Note:</title> - <para>When adding a new server you will need to specify what JRE to use. It is + </listitem> + </itemizedlist> + <figure> + <title>Defining JBoss Runtime</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_11.png"/> + </imageobject> + </mediaobject> + </figure> + <note> + <title>Note:</title> + <para>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.</para> - </note> + </note> - <itemizedlist> - <listitem> - <para>In the next dialog verify the specified information and if something is + <itemizedlist> + <listitem> + <para>In the next dialog verify the specified information and if something is unfair go back and correct it</para> - </listitem> - </itemizedlist> - <figure> - <title>JBoss Runtime Summary</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_15.png"/> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>In the last wizard&apos;s dialog modify the projects that are + </listitem> + </itemizedlist> + <figure> + <title>JBoss Runtime Summary</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_15.png"/> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>In the last wizard&apos;s dialog modify the projects that are configured on the server and click <emphasis> <property>Finish</property> - </emphasis>.</para> - </listitem> - </itemizedlist> - <figure> - <title>Configuring Projects</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_16.png"/> - </imageobject> - </mediaobject> - </figure> - <para>A new <property>JBoss Server</property> should now appear in the <property>Servers</property> view.</para> - <figure> - <title>New JBoss Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/manage/manage_17.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Now, we are ready to create the first web application.</para> - </section> + </emphasis>.</para> + </listitem> + </itemizedlist> + <figure> + <title>Configuring Projects</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_16.png"/> + </imageobject> + </mediaobject> + </figure> + <para>A new <property>JBoss Server</property> should now appear in the <property>Servers</property> view.</para> + <figure> + <title>New JBoss Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/manage/manage_17.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Now, we are ready to create the first web application.</para> + </section> - </section> + </section> </chapter>