Author: sabrashevich Date: 2007-08-06 05:24:42 -0400 (Mon, 06 Aug 2007) New Revision: 2910 Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/images/jbossruntime.png trunk/documentation/GettingStartedGuide/docs/userguide/en/images/newjbossserver.png trunk/documentation/GettingStartedGuide/docs/userguide/en/images/servertype.png trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml Log: http://jira.jboss.com/jira/browse/EXIN-401 updated text context, changed images Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/images/jbossruntime.png =================================================================== (Binary files differ) Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/images/newjbossserver.png =================================================================== (Binary files differ) Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/images/servertype.png =================================================================== (Binary files differ) Modified: trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml =================================================================== --- trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml 2007-08-04 07:07:44 UTC (rev 2909) +++ trunk/documentation/GettingStartedGuide/docs/userguide/en/modules/ManageJBossAS.xml 2007-08-06 09:24:42 UTC (rev 2910) @@ -11,7 +11,7 @@ </keywordset> </chapterinfo> <title>Manage JBoss AS from Red Hat Developer Studio</title> - <para>Red Hat Developer Studio ships with JBoss AS v.4.2 bundled. When you followed the default installation of Red Hat Developer Studio, you already have a JBoss 4.2 server installed and defined. To run JBoss AS 4.2 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 JBoss EAP v.4.2 bundled. When you followed the default installation of Red Hat Developer Studio, you already have a JBoss 4.2 server installed and defined. To run JBoss AS 4.2 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> @@ -111,108 +111,18 @@ <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 JBoss AS 4.2 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 JBoss 4.0.5 server. First of all you need to install it.</para> + <para>Although Red Hat Developer Studio works closely with JBoss EAP 4.2 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 JBoss 4.2.1 server. First of all you need to install it.</para> <section id="JBossInstalling"> <?dbhtml filename="JBossInstalling.html"?> <title>JBoss AS Installation</title> <orderedlist> -<listitem><para>Download the installation pack of JBoss 4.0.5 and save it on your computer: <ulink url="http://labs.jboss.com/jbossas/downloads">http://labs.jb... -<listitem><para>Double-click this file or launch the installation from terminal like this:</para></listitem> +<listitem><para>Download the binary package of JBoss 4.2.1 and save it on your computer: <ulink url="http://labs.jboss.com/jbossas/downloads">http://labs.jb... </orderedlist> -<programlisting role="JAVA"><![CDATA[java -jar jems-installer-1.2.0.GA.jar -]]></programlisting> -<para>This will start the installation wizard and in the first screen you will be proposed to choose a language for install - instructions. This screen only selects the language that the installer will display choices in and has no effect on the -language used by JBoss or the applications deployed in JBoss.</para> -<figure> -<title>The installer language selection screen</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/chooselanguage.png"/> - </imageobject> -</mediaobject> -</figure> - +<para>It does not matter where on your system you install JBoss. Note, however, that installing JBoss 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>There is no requirement for root access to run JBoss on UNIX/Linux systems because none of the default ports are within the 0-1023 privileged port range.</para> <orderedlist continuation="continues"> -<listitem><para>Choose preferred language and click OK. In the next two dialogs click the Next button.</para></listitem> -<listitem><para>In the following window accept the license agreement and press the Next button.</para></listitem> +<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> </orderedlist> -<figure> -<title>Accepting the license</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/licenseagreement.png"/> - </imageobject> -</mediaobject> -</figure> -<para>The installer will ask for the directory to use for the installation. The installer does not write the installation directory into any of the scripts or into any form of registry, so you will be free to move or rename the JBoss installation directory after installation. On Linux platform installation directories that contains spaces can cause problems, so we recommend sticking to simple directory names.</para> -<orderedlist continuation="continues"> -<listitem><para>Choose the place where JBoss server will be installed and click Next.</para></listitem> -</orderedlist> - -<figure> -<title>Selecting the installation directory</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/choosinglocation.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> -<listitem><para>On the next step you are able to select the starting server configuration set.</para></listitem> -</orderedlist> - -<figure> -<title>Selecting the installation group</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/ejbprofile.png"/> - </imageobject> -</mediaobject> -</figure> -<para>The starting configuration determines which sets of packages are available for installation. After selecting the configuration set, you have the option to further customize the installation, customizing the set of services installed. -The next screen shows the package selection screen. The installer knows the dependencies between services and will not allow - you to configure services in an incompatible way. This is much safer than the trial and error approach of configuring -services by hand from a raw ZIP install. When choosing configuration sets, be aware that you can not add packages that are -not a part of the selected configuration set. If you wanted a simple web container (the tomcat configuration) that also had -JMS support (the jms configuration), it would be necessary to go to a larger configuration, such as the default configuration, - and remove the unwanted packages. There are some combinations of JEMS components that are not supported directly through the - installer.</para> -<orderedlist continuation="continues"> -<listitem><para>Choose packs you want to be installed and click Next.</para></listitem> -</orderedlist> - -<figure> -<title>Selecting the packages to install</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/selectingpacks.png"/> - </imageobject> -</mediaobject> -</figure> -<orderedlist continuation="continues"> -<listitem><para>Then select installation type (advanced or standard):</para></listitem> -</orderedlist> - -<figure> -<title>Selecting installation type</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/installationtype.png"/> - </imageobject> -</mediaobject> -</figure> -<para>When all this is done you will be asked to confirm your installation.</para> -<orderedlist continuation="continues"> -<listitem><para>Click the Next button to start installation.</para></listitem> -</orderedlist> -<orderedlist continuation="continues"> -<listitem><para>After installation process is complete click the button Next &gt; Done.</para></listitem> -</orderedlist> -<para>That&apos;s it. JBoss server is installed. Your JBoss installation can be found in the directory that you specified at -the beginning of the install. The installer image may contain different services than the archive distribution, depending on - the type of installation performed. However, the basic structure and layout of all JBoss instances are the same.</para> -<para>Now you should add JBoss AS to server manager in Red Hat Developer Studio.</para> </section> <section id="AddingJBossServer"> @@ -222,7 +132,7 @@ <orderedlist> <listitem><para>Open the JBoss Server View by selecting Window &gt; Show View &gt; Other &gt; Server &gt; JBoss Server View. You will see JBoss Server view.</para></listitem> <listitem><para>Right click anywhere in this view and select New Server.</para></listitem> -<listitem><para>Select JBoss, a division of Red Hat &gt; JBoss AS 4.0 and press Next.</para></listitem> +<listitem><para>Select JBoss &gt; JBoss v4.2 and press Next.</para></listitem> </orderedlist> <figure> <title>Selecting server type</title> @@ -234,7 +144,7 @@ </figure> <orderedlist continuation="continues"> -<listitem><para>In the next step locate the place where you have installed the server, locate its home directory and define JRE.</para></listitem> +<listitem><para>In the next step make Red Hat Developer Studio to know where you have installed the server and define JRE.</para></listitem> </orderedlist> <figure> <title>Defining JBoss Runtime</title> @@ -249,19 +159,8 @@ <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> <orderedlist continuation="continues"> - <listitem><para>In the following window give a name to a new server. After that press Next.</para></listitem> - </orderedlist> - <figure> -<title>Defining JBoss Server Name</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/jbossname.png"/> - </imageobject> -</mediaobject> -</figure> - - -<orderedlist continuation="continues"> + <listitem><para>In the following window leave all settings default and press Next button.</para></listitem> + <listitem><para>In the last wizard&apos;s dialog modify the projects that are configured on the server and click Finish.</para></listitem> </orderedlist> <figure>