[jboss-cvs] JBossAS SVN: r103559 - projects/docs/enterprise/5.0.1/Getting_Started_Guide/en-US.

Tue Apr 6 02:21:21 EDT 2010

Author: laubai
Date: 2010-04-06 02:21:21 -0400 (Tue, 06 Apr 2010)
New Revision: 103559

Modified:
   projects/docs/enterprise/5.0.1/Getting_Started_Guide/en-US/Start_Stop_Server.xml
Log:
JBPAPP-3784 Removed mentions of run.bat, since this is not included in EAP5 distribution.

Modified: projects/docs/enterprise/5.0.1/Getting_Started_Guide/en-US/Start_Stop_Server.xml
===================================================================

--- projects/docs/enterprise/5.0.1/Getting_Started_Guide/en-US/Start_Stop_Server.xml	2010-04-06 05:52:25 UTC (rev 103558)
+++ projects/docs/enterprise/5.0.1/Getting_Started_Guide/en-US/Start_Stop_Server.xml	2010-04-06 06:21:21 UTC (rev 103559)
@@ -4,14 +4,14 @@
 	<title>Starting and Stopping the Server</title>
 	<section id="Starting_and_Stopping_the_Server-Start_the_Server">
 		<title>Start the Server</title>
-		<para>
-			Move to <filename class="directory">JBOSS_DIST/jboss-as/bin</filename> directory and execute the <literal>run.bat</literal> (for Windows) or <literal>run.sh</literal> (for Linux) script, as appropriate for your operating system. 
+		<para><!--Commenting out run.bat related sections for JBPAPP-3784-->
+			Move to <filename class="directory">JBOSS_DIST/jboss-as/bin</filename> directory and execute the <!-- <literal>run.bat</literal> (for Windows) or --><literal>run.sh</literal> (for Linux) script<!--, as appropriate for your operating system-->. 
 		</para>
 		<para>
 			There is no <literal>Server Started</literal> message shown at the console when the server is started using the <literal>production</literal> profile. This message can be found in the <filename>server.log</filename> file located in the <filename>JBOSS_DIST/jboss-as/server/production/log</filename> subdirectory.
 		</para>
 <important><title>Remote connection to the JBoss Enterprise Application Platform server</title>
-	<para>the JBoss JBoss Enterprise Application Platform now binds its services to localhost (127.0.0.1) by default, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers correctly. To enable remote access by binding JBoss services to a particular interface, simply run jboss with the <command>-b</command> option. To bind to all available interfaces and re-enable the legacy behaviour use <command>./run.sh -b 0.0.0.0</command> on Linux or <command>run.bat -b 0.0.0.0</command> on Windows. In any case, be aware you still need to secure your server properly.
+	<para>the JBoss JBoss Enterprise Application Platform now binds its services to localhost (127.0.0.1) by default, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers correctly. To enable remote access by binding JBoss services to a particular interface, simply run jboss with the <command>-b</command> option. To bind to all available interfaces and re-enable the legacy behaviour use <command>./run.sh -b 0.0.0.0</command> on Linux<!--or <command>run.bat -b 0.0.0.0</command> on Windows-->. In any case, be aware you still need to secure your server properly.
 	</para>
 	<para>
 		Using <command>-b</command> as part of the JBoss Server's command line is equivalent to setting these individual properties: <property>-Djboss.bind.address</property>, <property>-Djava.rmi.server.hostname</property>, <property>-Djgroups.bind_addr</property> and <property>-Dbind.address</property>. Passing <property>-Djboss.bind.address</property> to the Java process as part of the <varname>JAVA_OPTS</varname> variable in the run scripts will not work as it is a JBoss property not a JVM property.
@@ -125,7 +125,7 @@
 		</para>
 	</section>
 	
-	<section id="Starting_and_Stopping_the_Server-Running_as_a_Service_under_Microsoft_Windows">
+	<!--<section id="Starting_and_Stopping_the_Server-Running_as_a_Service_under_Microsoft_Windows">
 		<title> Running as a Service under Microsoft Windows </title>
 		<para>
 			The JBoss Enterprise Application Platform 5 comes with the necessary files to configure the server to run as a service under windows. Distributed with JBoss Native, this enables the JBoss Enterprise Application Platform 5 to be run as a service on Windows operating system. To install the service navigate to <filename>JBOSS_DIST/jboss-as/bin</filename> and locate the <filename>service.bat</filename> file. Run the following command in a command prompt:
@@ -133,7 +133,6 @@
 <programlisting>
 ./service.bat install
 </programlisting>
-		<!-- JBoss Application Server in this instance should be left as is and not changed to the EAP name -->
 		<para>
 			This commands installs the JBoss Enterprise Application Platform as a service. Under the Windows services list you will find this listed by the short name <filename>JBAS50SVC</filename> and the long name <filename>JBoss Application Server 5.1</filename>.
 		</para>
@@ -151,6 +150,6 @@
 				Add these parameters at both places where <filename>run.bat</filename> appears in the <filename>service.bat</filename> file.
 			</para>
 		</important>
-	</section>
+	</section>-->
 </section>
 


