Attachment 681352 Details for Bug 899361 – JBPAPP-6089-reworded.patch

JBPAPP-6089-reworded.patch

JBPAPP-6089-reworded.patch (text/x-diff), 5.02 KB, created by Ondřej Žižka on 2011-05-20 16:00:59 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Ondřej Žižka

Created: 2011-05-20 16:00:59 UTC

Size: 5.02 KB

patch

obsolete

>Index: en-US/ch-Monitoring_with_JBoss_Operating_Network.xml
>===================================================================
>--- en-US/ch-Monitoring_with_JBoss_Operating_Network.xml	(revision 62316)
>+++ en-US/ch-Monitoring_with_JBoss_Operating_Network.xml	(working copy)
>@@ -64,46 +64,55 @@
> 		</step>
> 		<step>
> 			<para>
>-        		Select an available port to use for JMX monitoring. Make sure it is not blocked by a firewall.
>-        		<programlisting language="XML">JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.port=9876"</programlisting>
>+				Select an available port to use for JMX monitoring (9876 in the example below). Make sure it is not blocked by a firewall.
>+				Then append it to the JAVA_OPTS variable:
> 			</para>
>-		</step>
>-		<step>
>-			<para> 
>-                To make sure that both authentication and SSL are disabled, set the following options in the file:
>-                
>-            </para>
> 			<stepalternatives>
> 				<step>
>-					<para>
>-                on Red Hat Enterprise Linux and Solaris:
>-            </para>
>-					<programlisting># Define an available port to use for JMX monitoring (make sure it is not blocked by a firewall):
>-JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.port=9876" 
>-JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.access.file=/opt/redhat/ews/jmx/jmxremote.access"
>-JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.password.file=/opt/redhat/ews/jmx/jmxremote.password"
>-JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.ssl=false"
>-JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.authenticate=false"</programlisting>
>+					<para>on Red Hat Enterprise Linux and Solaris:</para>
>+					<programlisting>
>+JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.port=9876"
>+					</programlisting>
> 				</step>
> 				<step>
>-					<para>
>-                    on Windows:
>-<programlisting>
>-rem Define an available port to use for JMX monitoring (make sure it is not blocked by a firewall):
>+					<para>on Windows:</para>
>+					<programlisting>
> set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=9876"
>-set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.access.file=c:\jmx\jmxremote.access"
>-set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.password.file=c:\jmx\jmxremote.password"
>-set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.ssl=false"
>-set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.authenticate=false"
>-</programlisting>
>-					</para>
>+					</programlisting>
>+				</step>
>+			</stepalternatives>
>+
>+			<para>For development purposes, you might want to disable authentication and SSL. To do so, add these lines:</para>
>+				<programlisting>
>+JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.ssl=false"
>+JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.authenticate=false"
>+				</programlisting>
>+			<para>
>+			
>+		</step>
>+
> 					<important>
> 						<para>
>-                          In production environments, secure jmx with ssl and restrict the access with a firewall (refer to  <ulink url="http://download.oracle.com/javase/1.5.0/docs/guide/management/agent.html">http://download.oracle.com/javase/1.5.0/docs/guide/management/agent.html</ulink>).
>-                        </para>
>+							In production environments, be sure to set up access credentials, secure JMX with SSL
>+							(refer to <ulink url="http://download.oracle.com/javase/1.5.0/docs/guide/management/agent.html"
>+												  >http://download.oracle.com/javase/1.5.0/docs/guide/management/agent.html</ulink>)
>+							and restrict the access with a firewall. Example additonal lines:
>+
>+							Linux and Solaris:
>+							<programlisting>
>+JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.access.file=$EWS_HOME/jmxremote.access"
>+JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.password.file=$EWS_HOME/jmxremote.password"
>+							</programlisting>
>+							
>+							Windows:
>+							<programlisting>
>+set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.access.file=c:\Program Files\Red Hat\Enterprise Web Server\jmxremote.access"
>+set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.password.file=c:\Program Files\Red Hat\Enterprise Web Server\jmxremote.password"
>+							</programlisting>
>+
>+						</para>
> 					</important>
>-				</step>
>-			</stepalternatives>
>+					
> 			<note>
> 				<title>Path to the HTTP Server</title>
> 				<para>The JON httpd plugin needs a specific directory to monitor the HTTP Server:</para>
>@@ -121,7 +130,7 @@
> 			<para>
>             For further information about JBoss Operating Network refer to its <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/2.4/html-single/Basic_Admin_Guide/index.html#configuring-tomcat-for-discovery">Discovery chapter of the Basic Administration Guide</ulink>
>          .
>-            </para>
>+			</para>
> 		</step>
> 	</procedure>
> </chapter>

Actions: View

Attachments on bug 899361: 681352 | 681353