[portal-commits] JBoss Portal SVN: r12336 - docs/enterprise/trunk/Installation_Guide/en-US.

Author: prabhat.jha(a)jboss.com Date: 2008-12-03 10:40:41 -0500 (Wed, 03 Dec 2008) New Revision: 12336 Modified: docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml Log: testing my commit right Modified: docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2008-12-03 15:37:38 UTC (rev 12335) +++ docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2008-12-03 15:40:41 UTC (rev 12336) @@ -5,7 +5,7 @@ <chapter id="Test_your_Installation"> <title>Test your Installation</title> <para> - After you have installed the JBoss Enterprise Application Platform, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> envirnoment variables as explained in <ulink url="Post_Installation_Configuration"/>. To test your installation, move to <filename>JBOSS_DIST/jboss-as/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system. Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages: + After you have installed the JBoss Enterprise Portal Platform, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> envirnoment variables as explained in <ulink url="Post_Installation_Configuration"/>. To test your installation, move to <filename>JBOSS_DIST/jboss-as/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system. Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages: </para> <programlisting> [vrenish@vinux bin]$ ./run.sh