Attachment 681353 Details for Bug 899361 – ch-Monitoring_with_JBoss_Operating_Network.xml

ch-Monitoring_with_JBoss_Operating_Network.xml

ch-Monitoring_with_JBoss_Operating_Network.xml (text/xml), 6.00 KB, created by Ondřej Žižka on 2011-05-23 18:03:28 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Ondřej Žižka

Created: 2011-05-23 18:03:28 UTC

Size: 6.00 KB

patch

obsolete

><?xml version='1.0'?>
><!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
>]>
><chapter id="ch-Monitoring_with_JBoss_Operating_Network">
>	<title>Monitoring Enterprise Web Server with JBoss Operating Network</title>
>	<para>To allow JBoss Operating Network to monitor <productname>JBoss Enterprise Web Server</productname>, you need to configure it to allow its JBoss ON discovery and to give JBoss ON enough access to perform the full range of management.</para>
>	
>	<procedure id="proc-Configuring_User_Permissions">
>		<title>Configuring User Permissions on a Unix OS</title>
>		<note>
>			<para>If using a Windows OS, skip these steps and proceed to <xref linkend="proc-Configuring_Monitoring"/>.</para>
>		</note>
>		<para>RHQ/JON agent needs read and write permission to the <filename>httpd</filename> and <filename>tomcat<replaceable>&lt;VERSION&gt;</replaceable>
>			</filename> directories.</para>
>		<para>Follow this procedure to handle this issue:</para>
>		<step>
>			<para>
>                    At the shell prompt, become the root user.
>                </para>
>		</step>
>		<step>
>			<para>
>                    Run the following command to add the user, under which JON Agent runs to the tomcat and apache user groups:</para>
>			<screen># useradd -G tomcat,apache <replaceable>&lt;RHQ_AGENT_USER&gt;</replaceable>
>            </screen>
>		</step>
>	</procedure>
>	<procedure id="proc-Configuring_Monitoring">
>		<title>Configuring Monitoring</title>
>		<para>
>			<productname>JBoss Enterprise Web Server</productname> servers are auto-discovered on Linux and Unix platforms. However, you need to configure the instance's JMX to allow proper handling of authentication and accurate Tomcat monitoring.
>            </para>
>		<para>
>                Follow this procedure to set up JMX to handle authentication:
>            </para>
>		<step>
>			<para>
>            Open for editing the <filename>startup</filename> file of the respective Enterprise Web Server instance:
>        </para>
>			<stepalternatives>
>				<step>
>					<para>
>                on Red Hat Enterprise Linux installed from a <emphasis>ZIP</emphasis> file open <filename>$EWS_HOME/tomcat<replaceable>&lt;VERSION&gt;</replaceable>/bin/startup.sh</filename>
>					</para>
>				</step>
>				<step>
>					<para>
>                on Red Hat Enterprise Linux installed from a <emphasis>RPM</emphasis> files open <filename>/usr/sbin/tomcat<replaceable>&lt;VERSION&gt;</replaceable>
>						</filename>
>					</para>
>				</step>
>				<step>
>					<para>
>                on Solaris open <filename>/opt/redhat/ews/tomcat<replaceable>&lt;VERSION&gt;</replaceable>/bin/startup.sh</filename>
>					</para>
>				</step>
>				<step>
>					<para>
>                on Windows open <filename>C:\Program Files\Red Hat\Enterprise Web Server\sbin\tomcat<replaceable>&lt;VERSION&gt;</replaceable>.sh
>                </filename>
>					</para>
>				</step>
>			</stepalternatives>
>		</step>
>		<step>
>			<para>
>				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>
>			<stepalternatives>
>				<step>
>					<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:</para>
>					<programlisting>
>set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=9876"
>					</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, 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>
>					
>			<note>
>				<title>Path to the HTTP Server</title>
>				<para>The JON httpd plugin needs a specific directory to monitor the HTTP Server:</para>
>           <itemizedlist>
>           	<listitem>
>            		<para>on Solaris and Red Hat Enterprise Linux: <filename>/etc/httpd</filename></para>
>						</listitem>
>						<listitem>
>							<para>on Windows: <filename>C:\apache</filename>
>							</para>
>						</listitem>
>					</itemizedlist>
>					<para>If the respective directory does not exist, create it before launching the JON agent.</para>
>			</note>
>			<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>
>		</step>
>	</procedure>
></chapter>

Actions: View

Attachments on bug 899361: 681352 | 681353