[jboss-cvs] JBossAS SVN: r92045 - projects/docs/enterprise/5.0/Installation_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Aug 5 21:34:00 EDT 2009
Author: irooskov at redhat.com
Date: 2009-08-05 21:34:00 -0400 (Wed, 05 Aug 2009)
New Revision: 92045
Modified:
projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml
projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml
Log:
updated install guide with new information
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml 2009-08-06 00:52:57 UTC (rev 92044)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Getting_Started.xml 2009-08-06 01:34:00 UTC (rev 92045)
@@ -432,6 +432,19 @@
</para>
</listitem>
</itemizedlist>
+ <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_64_bit_Sun_JDK_6.0_on_Solaris">
+ <title>Installing and Configuring 64-bit Sun JDK 6.0 on Solaris</title>
+ <listitem>
+ <para>
+ Download the Sun JDK 6.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index.jsp"></ulink>. Choose "JDK 6.0 Update <x>" (where x is the latest update number) for download and then select your Solaris options to perform the installation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Solarius uses a 32-bit JVM by default. In order to use a 64-bit JVM the <code>-d64</code> parameter must be added to <literal>JAVA_OPTS</literal>.
+ </para>
+ </listitem>
+ </itemizedlist>
</para>
</section>
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml 2009-08-06 00:52:57 UTC (rev 92044)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml 2009-08-06 01:34:00 UTC (rev 92045)
@@ -35,6 +35,41 @@
</para>
</listitem>
</itemizedlist>
+ <important>
+ <para>
+ On Windows Server 2008 when installing the JBoss Enterprise Application Platform service, open Windows Explorer and right click on <filename>C:\Windows\System32\cmd.exe</filename> and select <guimenuitem>Run As Administrator</guimenuitem>. Then change directory to the root of your installation directory (<filename>%JBOSS_HOME%\bin</filename>) and install the service using the command:
+ </para>
+<programlisting>
+service install
+</programlisting>
+ <para>
+ This is needed because of the Windows UAC. On Windows 2003 the <guimenuitem>Run As Administrator</guimenuitem> step is not needed as long as the current user has the correct privileges to install the service.
+ </para>
+ </important>
+ <section>
+ <title>JBoss Native Installation Notes</title>
+ <formalpara>
+ <title>Windows Installation Notes for JBoss Native</title>
+ <para>
+ The version of the <filename>jboss-eap-native</filename> package being installed on Windows, must align with the architecture version of the isntalled JVM. If you have a 32-bit JVM installed on a 64-bit Windows system then a 32-bit JBoss Native package will need to be installed.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Solaris Installation Notes for JBoss Native</title>
+ <para>
+ Both 32-bit and 64-bit versions of <filename>jboss-eap-native</filename> can be used. The libraries for each are seperated by the directories <filename>lib</filename> and <filename>lib64</filename> respectfully and each is automatically loaded depending on the JVM version that is used.
+ </para>
+ </formalpara>
+ <para>
+ To install both 32-bit and 64-bit versions of <filename>jboss-eap-native</filename>, use the command:
+ </para>
+<programlisting>
+unzip -qo jboss-eap-native-5.0.0-solaris
+</programlisting>
+ <para>
+ The <code>-o</code> option in the command ensures that one version of the package won't replace another during the installation.
+ </para>
+ </section>
</section>
</chapter>
Modified: projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml 2009-08-06 00:52:57 UTC (rev 92044)
+++ projects/docs/enterprise/5.0/Installation_Guide/en-US/Post_Installation.xml 2009-08-06 01:34:00 UTC (rev 92045)
@@ -29,6 +29,9 @@
Create a System environment variable called <literal>JBOSS_HOME</literal> that points to the installation directory, for example: C:\EnterprisePlatform-5.0.0\jboss-as\. In order to run the server from the command line add the <filename>bin</filename> directory to your path, for example: C:\EnterprisePlatform-5.0.0\jboss-as\bin. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
</para>
</formalpara>
+ <para>
+ <literal>TMP</literal> and <literal>TEMP</literal> System environment variables also need to be added. By default these variables are User based, so you will have to change them to be System based. This will assure that the JBoss Enterprise Application Server uses the same location for temporary storage no mater which user account is used to run it.
+ </para>
<important>
<para>
On Windows there is a difference between
More information about the jboss-cvs-commits
mailing list