[jboss-cvs] JBossAS SVN: r97571 - in projects/docs/enterprise/5.0/mod_cluster: en-US and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Dec 8 19:11:06 EST 2009
Author: gmeintjes
Date: 2009-12-08 19:11:05 -0500 (Tue, 08 Dec 2009)
New Revision: 97571
Added:
projects/docs/enterprise/5.0/mod_cluster/en-US/
projects/docs/enterprise/5.0/mod_cluster/en-US/Author_Group.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Chapter.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Preface.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml
projects/docs/enterprise/5.0/mod_cluster/en-US/images/
projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.ent
projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml
Log:
Format the documentation in xml for EAP 5.0 iaw RT3 Ticket 54522
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/Author_Group.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Author_Group.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Author_Group.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,15 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<authorgroup>
+ <editor>
+ <firstname>Gary</firstname>
+ <surname>Meintjes</surname>
+ <affiliation>
+ <orgname>Red Hat Inc</orgname>
+ <orgdiv>Engineering Content Services</orgdiv>
+ </affiliation>
+ <email>gmeintje at redhat.com</email>
+ </editor>
+</authorgroup>
\ No newline at end of file
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Book_Info.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,28 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<bookinfo id="book-mod_cluster-mod_cluster">
+ <title>mod_cluster</title>
+ <subtitle>for Use with JBoss Enterprise Application Platform 5</subtitle>
+ <productname>JBoss Enterprise Application Platform</productname>
+ <productnumber>0.1</productnumber>
+ <edition>0</edition>
+ <pubsnumber>0</pubsnumber>
+ <abstract>
+ <para>
+mod_cluster is an httpd-based load balancer that uses a
+communication channel to forward requests from httpd to one of a
+set of application server nodes.
+</para>
+ </abstract>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" />
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</bookinfo>
+
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/Chapter.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Chapter.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Chapter.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,31 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<chapter id="chap-mod_cluster-Test_Chapter">
+ <title>Test Chapter</title>
+ <para>
+ This is a test paragraph
+ </para>
+ <section id="sect-mod_cluster-Test_Chapter-Test_Section_1">
+ <title>Test Section 1</title>
+ <para>
+ This is a test paragraph in a section
+ </para>
+ </section>
+
+ <section id="sect-mod_cluster-Test_Chapter-Test_Section_2">
+ <title>Test Section 2</title>
+ <para>
+ This is a test paragraph in Section 2
+ <orderedlist>
+ <listitem>
+ <para>
+ listitem text
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </section>
+
+</chapter>
+
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/ConfigurationForJBossAS.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,264 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<chapter id="chap-mod_cluster-Configuring_for_JBoss_AS">
+ <title>Configuring for JBoss AS</title>
+ <note>
+ <para>
+ mod_cluster currently works with <application>JBoss AS 5.0</application>.
+ </para>
+ </note>
+ <section id="sect-mod_cluster-Configuring_for_JBoss_AS-Common_Configuration">
+ <title>Common Configuration</title>
+ <para>
+ To begin configuring for JBoss AS, edit the following file:
+ </para>
+
+<programlisting>
+<filename>$JBOSS_HOME/server/<replaceable>profile/deploy</replaceable>/jbossweb.sar/server.xml</filename>
+</programlisting>
+ <formalpara id="form-mod_cluster-Common_Configuration-Add_a_lifecycle_listener.">
+ <title>Add a lifecycle listener.</title>
+ <para>
+ This listener informs mod_cluster of lifecycle events such as server start/stop and context start/stop. For each relevant event, a corresponding set of messages is sent to the mod_cluster httpd module informing it how to configure or reconfigure itself. For details, refer to the appropriate server section below.
+ </para>
+ </formalpara>
+ <formalpara id="form-mod_cluster-Common_Configuration-Define_a_jvmRoute_for_each_server.">
+ <title>Define a <parameter>jvmRoute</parameter> for each server.</title>
+ <para>
+ mod_cluster requires the Catalina engine of each node to define a unique <parameter>jvmRoute</parameter> attribute. The <parameter>jvmRoute</parameter> uniquely identifies the engine instance in httpd.
+ </para>
+ </formalpara>
+ <formalpara id="form-mod_cluster-Common_Configuration-Adjust_load_balance_factor_calculation_period.">
+ <title>Adjust load balance factor calculation period.</title>
+ <para>
+ mod_cluster utilizes the background processing thread of the Catalina engine to trigger load balance factor calculations. The frequency of the load balance factor calculation is controlled via the <property>backgroundProcessorDelay</property> attribute of the engine. In general, <property>backgroundProcessorDelay</property> indicates the number of seconds between processing thread executions. In the context of mod_cluster, <property>backgroundProcessorDelay</property> determines how frequently the load balance factor should be recalculated. The default period is <literal>10 seconds</literal>.
+ </para>
+ </formalpara>
+ <para>
+ Sample server.xml:
+ </para>
+
+<screen>
+ <Server>
+ <!-- ... -->
+ <Listener className="..."/>
+ <!-- ... -->
+ <Service name="jboss.web">
+ <Connector protocol="HTTP/1.1" port="8080" address="${jboss.bind.address}" redirectPort="8443"/>
+ <Connector protocol="AJP/1.3" port="8009" address="${jboss.bind.address}" redirectPort="8443"/>
+ <Engine name="jboss.web" defaultHost="localhost" jvmRoute="${jboss.jvmRoute}" backgroundProcessorDelay="10">
+ <!-- ... -->
+ </Engine>
+ </Service>
+ </Server>
+</screen>
+ </section>
+
+ <section id="sect-mod_cluster-Configuring_for_JBoss_AS-JBoss_AS_Integration">
+ <title>JBoss AS Integration</title>
+ <para>
+ The server.xml lifecycle listener used by mod_cluster in JBoss AS functions as a simple bridge delegating all lifecycle events to a bean deployed in the JBoss microcontainer.
+ </para>
+
+<programlisting>
+<Listener className="org.jboss.web.tomcat.service.deployers.MicrocontainerIntegrationLifecycleListener"
+ delegateBeanName="InsertBeanNameHere"/>
+</programlisting>
+ <para>
+ The implementation of this delegate bean determines how mod_cluster should operate:
+ <orderedlist>
+ <listitem>
+ <para>
+ Non-clustered mode
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Clustered mode
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <para>
+ To ensure that this delegate bean exists before JBoss Web is started, and does not get destroyed until JBoss Web shuts down, add an explicit microcontainer dependency. Update the WebServer bean contained in <filename>$JBOSS_HOME/server/<literal>profile</literal>/deploy/jbossweb.sar/META-INF/jboss-beans.xml</filename> with an appropriate dependency:
+ </para>
+
+<programlisting>
+<depends>InsertBeanNameHere</depends>
+</programlisting>
+ </section>
+
+ <section id="sect-mod_cluster-Configuring_for_JBoss_AS-Non_clustered_mode">
+ <title>Non-clustered mode</title>
+ <para>
+ In non-clustered mode, each JBoss server node communicates with each httpd proxy directly. The nodes do not communicate with each other.
+ </para>
+
+<programlisting>
+<Listener lassName="org.jboss.web.tomcat.service.deployers.MicrocontainerIntegrationLifecycleListener" delegateBeanName="ModClusterService"/>
+</programlisting>
+ <para>
+ The ModClusterService bean descriptor is found in the following file: <filename>$JBOSS_HOME/server/profile/deploy/mod-cluster.sar/META-INF/mod-cluster-jboss-beans.xml</filename>
+ </para>
+
+<programlisting>
+<bean name="ModClusterService" mode="On Demand"
+ class="org.jboss.modcluster.ModClusterService">
+ <constructor>
+ <parameter><inject bean="DynamicLoadBalanceFactorProvider"/></parameter>
+ </constructor>
+ <!-- Configuration properties go here -->
+ <property name="advertise">true</property>
+ </bean>
+</programlisting>
+ <para>
+ The ModClusterService bean defines:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>A load balance factor provider </term>
+ <listitem>
+ <para>
+ This bean, implementing org.jboss.load.LoadBalanceFactorProvider, defines the load metrics used to calculate this node's load balance factor.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Configuration properties</term>
+ <listitem>
+ <para>
+ For the complete list of configuration properties available to ModClusterService, refer to the following sections:
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Proxy Discovery configuration
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Proxy configuration
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ SSL configuration
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="sect-mod_cluster-Configuring_for_JBoss_AS-Clustered_Mode">
+ <title>Clustered Mode</title>
+ <para>
+ In clustered mode, a single JBoss Web instance of a cluster communicates with each httpd proxy on behalf of the other nodes of the cluster.
+ </para>
+
+<programlisting>
+<Listener className="org.jboss.web.tomcat.service.deployers.MicrocontainerIntegrationLifecycleListener"
+ delegateBeanName="HAModClusterService"/>
+</programlisting>
+ <para>
+ This configuration mode has the following advantages over the non-clustered mode:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The state of each proxy will be kept in sync on each node in the cluster.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Proxies will be proactively notified of view changes - specifically crashed members, allowing the proxy to gracefully reconfigure itself potentially avoiding failover processing.
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>
+ If your application server already uses other clustering services (e.g. session replication), then you should consider running mod_cluster in clustered-mode. If your application server is stateless (i.e. no sessions), or you are not using other clustering services, then non-clustered mode may be more appropriate.
+ </para>
+ <para>
+ The HAModClusterService bean descriptor is found in the following file:
+ </para>
+ <para>
+ $JBOSS_HOME/server/profile/deploy/mod-cluster.sar/META-INF/mod-cluster-jboss-beans.xml
+ </para>
+
+<programlisting>
+<bean name="HAModClusterService" mode="On Demand"
+ class="org.jboss.modcluster.ha.HAModClusterService">
+ <constructor>
+ <parameter><inject bean="HAPartition"/></parameter>
+ <parameter><inject bean="HAModClusterConfig"/></parameter>
+ <parameter><inject bean="DynamicLoadBalanceFactorProvider"/></parameter>
+ <parameter><bean class="org.jboss.ha.singleton.HASingletonElectionPolicySimple"/></parameter>
+ </constructor>
+ </bean>
+ <bean name="HAModClusterConfig" mode="On Demand" class="org.jboss.modcluster.config.ha.HAModClusterConfig">
+ <!-- Configuration properties go here -->
+ <parameter name="advertise">true</parameter>
+ </bean>
+</programlisting>
+ <para>
+ The <classname>HAModClusterService</classname> bean defines:
+ </para>
+ <!-- <variablelist>
+ <varlistentry><term>An <classname>HAPartition</classname> instance</term>
+ <listitem>
+ <para>
+An <classname>HAPartition</classname> is an abstraction defining the nodes a singleton master will manage. The default <classname>HAPartition</classname> is defined in:
+<filename>$JBOSS_HOME/server/profile/deploy/cluster/cluster-jboss-beans.xml</filename>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term>An <object>HAModClusterConfig</object> bean, defining containing the configuration properties.</term>
+ <listitem>
+ <para>
+For the complete list of configuration properties available to ModClusterService, refer to the following sections:
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist> --><!-- <itemizedlist>
+ <listitem>
+ <para>
+Proxy Discovery configuration
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+Proxy configuration
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+SSL configuration
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+HA configuration
+ </para>
+ </listitem>
+ </itemizedlist> --><!-- <variablelist>
+ <varlistentry><term>A load balance factor provider</term>
+ <listitem>
+ <para>
+This bean, implementing <filename>org.jboss.load.LoadBalanceFactorProvider</filename>, defines the load metrics used to calculate the load balance factor of this node.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term>An HA singleton election policy</term>
+ <listitem>
+ <para>
+This bean, implementing <filename>org.jboss.ha.singleton.HASingletonElectionPolicy</filename>, defines the policy for choosing a singleton master from the set of partition members.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist> -->
+ </section>
+
+</chapter>
+
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/MigratingFromModJK.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,318 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<chapter id="chap-mod_cluster-Migration_from_mod_jk">
+ <title>Migration from mod_jk</title>
+ <section id="sect-mod_cluster-Migration_from_mod_jk-Migration_from_mod_jk_to_mod_cluster">
+ <title>Migration from mod_jk to mod_cluster</title>
+ <para>
+ <application>mod_cluster</application> only supports <application>Apache</application> httpd, there are no plans to support <application>IIS</application> or <application>Iplanet</application>.
+ </para>
+ <para>
+ The migration from <application>mod_jk</application> to mod_cluster is not very complex. There are only a few worker properties that cannot be mapped to mod_cluster parameters.
+ </para>
+ <para>
+ The table of worker properties and how to transfer them to the <classname>ClusterListener</classname> parameters follows:
+ </para>
+ <table frame="all" id="tabl-mod_cluster-Migration_from_mod_jk_to_mod_cluster-Worker_Property_Transfer">
+ <title>Worker Property Transfer</title>
+ <tgroup align="left" cols="3" colsep="1" rowsep="1">
+ <colspec colname="c1"></colspec>
+ <colspec colname="c2"></colspec>
+ <colspec colname="c3"></colspec>
+ <thead>
+ <row>
+ <entry>
+ mod_jk worker property
+ </entry>
+ <entry>
+ <classname>ClusterListener</classname> Parameter
+ </entry>
+ <entry>
+ Remarks
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ host
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ It is read from the <Connector/> Address information
+ </entry>
+ </row>
+ <row>
+ <entry>
+ port
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ It is read from the <Connector/> Port information
+ </entry>
+ </row>
+ <row>
+ <entry>
+ type
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ It is read from the <Connector/> Protocol information
+ </entry>
+ </row>
+ <row>
+ <entry>
+ route
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ It is read from the <Engine/> JVMRoute information
+ </entry>
+ </row>
+ <row>
+ <entry>
+ domain
+ </entry>
+ <entry>
+ domain
+ </entry>
+ <entry>
+ Not supported in this version
+ </entry>
+ </row>
+ <row>
+ <entry>
+ redirect
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ The nodes with <literal>loadfactor = 0</literal> are standby nodes that will be used when there are no other nodes available
+ </entry>
+ </row>
+ <row>
+ <entry>
+ socket_timeout
+ </entry>
+ <entry>
+ nodeTimeout
+ </entry>
+ <entry>
+ Default: 10 seconds
+ </entry>
+ </row>
+ <row>
+ <entry>
+ socket_keepalive
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ <classname>KEEP_ALIVE</classname> os is always on in mod_cluster
+ </entry>
+ </row>
+ <row>
+ <entry>
+ connection_pool_size
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ The max size is calculated to be <literal>AP_MPMQ_MAX_THREADS+1</literal> (max)
+ </entry>
+ </row>
+ <row>
+ <entry>
+ connection_pool_minsize
+ </entry>
+ <entry>
+ smax
+ </entry>
+ <entry>
+ The default is max
+ </entry>
+ </row>
+ <row>
+ <entry>
+ connection_pool_timeout
+ </entry>
+ <entry>
+ ttl
+ </entry>
+ <entry>
+ Time-to-live when over smax connections. Default: 60 seconds
+ </entry>
+ </row>
+ <row>
+ <entry>
+ -
+ </entry>
+ <entry>
+ workerTimeout
+ </entry>
+ <entry>
+ Max time to wait for a free worker. Default: 1 second
+ </entry>
+ </row>
+ <row>
+ <entry>
+ retries
+ </entry>
+ <entry>
+ maxAttempts
+ </entry>
+ <entry>
+ Max retries before returning an error. Default: 3
+ </entry>
+ </row>
+ <row>
+ <entry>
+ recovery_options
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ mod_cluster behaves like mod_jk with value <varname>7</varname>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ fail_on_status
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported
+ </entry>
+ </row>
+ <row>
+ <entry>
+ max_packet_size
+ </entry>
+ <entry>
+ iobuffersize/receivebuffersize
+ </entry>
+ <entry>
+ Not supported in this version. Use <varname>ProxyIOBufferSize</varname>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ max_reply_timeouts
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported
+ </entry>
+ </row>
+ <row>
+ <entry>
+ recovery_time
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ The <literal>ClusterListener</literal> will tell (via a <varname>STATUS</varname> message) mod_cluster that the node is up again
+ </entry>
+ </row>
+ <row>
+ <entry>
+ activation
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ mod_cluster receives this information via <varname>ENABLE/DISABLE/STOP</varname> messages
+ </entry>
+ </row>
+ <row>
+ <entry>
+ distance
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ mod_cluster handles this via the <varname>loadfactor</varname> logic
+ </entry>
+ </row>
+ <row>
+ <entry>
+ mount
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ The context mounted automatically via the <varname>ENABLE-APP</varname> messages. <varname>ProxyPass</varname> could also be used
+ </entry>
+ </row>
+ <row>
+ <entry>
+ secret
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported
+ </entry>
+ </row>
+ <row>
+ <entry>
+ connect_timeout
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported. Use <varname>ProxyTimeout</varname> or server <varname>TimeOut</varname> (Default: 300 seconds)
+ </entry>
+ </row>
+ <row>
+ <entry>
+ prepost_timeout
+ </entry>
+ <entry>
+ ping
+ </entry>
+ <entry>
+ Default: 10 seconds
+ </entry>
+ </row>
+ <row>
+ <entry>
+ reply_timeout
+ </entry>
+ <entry>
+ -
+ </entry>
+ <entry>
+ Not supported. Use <varname>ProxyTimeout</varname> or server <varname>TimeOut?</varname> directive (Default: 300 seconds)
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+</chapter>
+
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Overview.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,146 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<chapter id="chap-mod_cluster-Overview">
+ <title>Overview</title>
+ <!-- <para>This is a test paragraph</para> -->
+ <section id="sect-mod_cluster-Overview-Introducton">
+ <title>Introducton</title>
+ <para>
+ <classname>JBoss mod_cluster</classname> is an httpd-based load balancer. Like <application>mod_jk</application> and <application>mod_proxy</application>, mod_cluster uses a communication channel to forward requests from httpd to one of a set of application server nodes.
+ </para>
+ <para>
+ Unlike mod_jk and mod_proxy, mod_cluster leverages an additional connection between the application server nodes and httpd. The application server nodes use this connection to transmit server-side load balance factors and lifecycle events back to httpd via a custom set of HTTP methods, called the <application>Mod-Cluster Management Protocol (MCMP)</application>. This additional feedback channel allows mod_cluster to offer a level of intelligence and granularity not found in other load balancing solutions.
+ </para>
+ <para>
+ Within httpd, mod_cluster is implemented as a set of modules for httpd with mod_proxy enabled. Much of the logic comes from mod_proxy, e.g. mod_proxy_ajp provides all the AJP logic needed by mod_cluster.
+ </para>
+ <para>
+ <application>JBoss</application> already prepares binary packages with httpd and mod_cluster so you can quickly try mod_cluster on the following platforms:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <application>Linux x86, x64, ia64</application>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>Solaris x86, SPARC</application>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>Windows x86, x64, ia64</application>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>HP-UX PA-RISC, ia64</application>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="sect-mod_cluster-Overview-Advantages">
+ <title>Advantages</title>
+ <para>
+ mod_cluster currently holds the following advantages over other httpd-based load balancers:
+ </para>
+ <formalpara id="form-mod_cluster-Advantages-Dynamic_configuration_of_httpd_workers">
+ <title>Dynamic configuration of httpd workers</title>
+ <para>
+ Traditional httpd-based load balancers require explicit configuration of the workers available to a proxy. In mod_cluster, the bulk of the proxy's configuration resides on the application servers. The set of proxies to which an application server will communicate is determined either by a static list or using dynamic discovery via the advertise mechanism. The application server relays lifecycle events (e.g. server startup/shutdown) to the proxies allowing them to effectively auto-configure themselves. Notably, the graceful shutdown of a server will not result in a failover response by a proxy, as is the case with traditional httpd-based load balancers.
+ </para>
+ </formalpara>
+ <formalpara id="form-mod_cluster-Advantages-Server_side_load_balance_factor_calculation">
+ <title>Server-side load balance factor calculation</title>
+ <para>
+ Traditional httpd-based load balancers require explicit configuration of the workers available to a proxy. In mod_cluster, the bulk of the proxy's configuration resides on the application servers. The set of proxies to which an application server will communicate is determined either by a static list or using dynamic discovery via the advertise mechanism. The application server relays lifecycle events (e.g. server startup/shutdown) to the proxies allowing them to effectively auto-configure themselves. Notably, the graceful shutdown of a server will not result in a failover response by a proxy, as is the case with traditional httpd-based load balancers.
+ </para>
+ </formalpara>
+ <formalpara id="form-mod_cluster-Advantages-Fine_grained_web_app_lifecycle_control">
+ <title>Fine grained web-app lifecycle control</title>
+ <para>
+ Traditional httpd-based load balancers do not handle web application undeployments particularly well. From the proxy's perspective requests to an undeployed web application are indistinguishable from a request for an non-existent resource, and will result in <literal>404</literal> errors. In mod_cluster, each server forwards any web application context lifecycle events (e.g. web-app deploy/undeploy) to the proxy informing it to start/stop routing requests for a given context to that server.
+ </para>
+ </formalpara>
+ <formalpara id="form-mod_cluster-Advantages-AJP_is_optional">
+ <title>AJP is optional</title>
+ <para>
+ Unlike mod_jk, mod_cluster does not require <application>AJP</application>. httpd connections to application server nodes can use HTTP, HTTPS, or AJP.
+ </para>
+ </formalpara>
+ </section>
+
+ <section id="sect-mod_cluster-Overview-Requirements">
+ <title>Requirements</title>
+ <para>
+ The following are required for the installation:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ httpd-2.2.8+
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <application>JBossAS 5.0.0+</application>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <para>
+ Note: httpd-2.2.8+ is already in the bundles, so if you use the bundle you don't need to download <application>Apache</application> httpd.
+ </para>
+ </note>
+ </section>
+
+ <section id="sect-mod_cluster-Overview-Configuration">
+ <title>Configuration</title>
+ <para>
+ To configure for JBossAS, refer to the relavant chapter in this publication.
+ </para>
+ </section>
+
+ <section id="sect-mod_cluster-Overview-Migration_from_mod_jk">
+ <title>Migration from mod_jk</title>
+ <para>
+ In general, much of the configuration previously found in <filename>httpd.conf</filename> is now defined in the application server nodes. Refer to the relavant chapter in this publication.
+ </para>
+ </section>
+
+ <section id="sect-mod_cluster-Overview-Load_Balancing_Demo_Application">
+ <title>Load Balancing Demo Application</title>
+ <para>
+ The mod_cluster binary distribution for JBoss AS includes a demo application that helps demonstrate how different server-side scenarios affect the routing of client requests by the load balancer. The demo application is located in the mod_cluster distribution's demo directory.
+ </para>
+ </section>
+
+ <section id="sect-mod_cluster-Overview-Current_Limitations">
+ <title>Current Limitations</title>
+ <para>
+ The mod_cluster install currently has the following limitations:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Dynamic load balance factor calculation support is currently limited to the JBoss AS integration.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Clustered-mode support is currently limited to the JBoss AS integration
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Checksum verification of proxy advertisements (if advertise is enabled) will never fail.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+</chapter>
+
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/Preface.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Preface.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Preface.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<preface id="pref-mod_cluster-Preface">
+ <title>Preface</title>
+ <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ </xi:fallback>
+ </xi:include>
+</preface>
+
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/QuickStartGuide.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,306 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<chapter id="chap-mod_cluster-Quick_Start_Guide">
+ <title>Quick Start Guide</title>
+ <para>
+ The following steps are required to set up a minimal working installation of mod_cluster on a single httpd server and a single back end server, either <application>JBoss AS</application>, <application>JBossWeb</application> or <application>Tomcat</application>. The steps can be repeated to add as many httpd servers or back end servers to your cluster as desired.
+ </para>
+ <para>
+ The steps shown here are not intended to demonstrate how to set up a production install of mod_cluster; for example using <application>SSL</application> to secure access to the httpd-side mod_manager component is not covered. See the <citetitle>httpd-side</citetitle> and <citetitle>java-side configuration documentation</citetitle> for the full set of configuration options.
+ </para>
+ <section id="sect-mod_cluster-Quick_Start_Guide-Download_mod_cluster_components">
+ <title>Download mod-cluster components</title>
+ <para>
+ Download the latest httpd and java release bundles. If there is no pre-built httpd bundle appropriate for your OS or system architecture, you can build the binary from source.
+ </para>
+ </section>
+
+ <section id="sect-mod_cluster-Quick_Start_Guide-Install_the_httpd_binary">
+ <title>Install the httpd binary</title>
+ <formalpara id="form-mod_cluster-Install_the_httpd_binary-Install_the_entire_httpd">
+ <title>Install the entire httpd</title>
+ <para>
+ The httpd-side bundles are <application>gzipped tars</application> and include a full httpd install. As they already contain an <application>Apache httpd</application> install, you do not need to download Apache httpd. Extract them in root, e.g.
+ </para>
+ </formalpara>
+
+<programlisting>
+cd /
+tar xvf mod_cluster-1.0.0.CR2-linux2-x86-so.tar.gz
+</programlisting>
+ <para>
+ That will provide you with a full httpd install in the <filename>/opt/jboss directory</filename>.
+ </para>
+ <formalpara id="form-mod_cluster-Install_the_httpd_binary-Install_only_the_modules">
+ <title>Install only the modules</title>
+ <para>
+ If you already have a working httpd install that you would prefer to use, you'll need to download the bundle named <package>mod_cluster httpd dynamic libraries</package> corresponding to your platform. Extract the modules and copy them directly to the module directory of your httpd install.
+ </para>
+ </formalpara>
+
+<programlisting>
+cd /tmp
+tar xvf mod_cluster-1.0.0.CR2-linux2-x86-so.tar.gz
+</programlisting>
+ <para>
+ Then copy the following files to the module directory.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>mod_proxy.so</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>mod_proxy_ajp.so</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>mod_slotmem.so</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>mod_manager.so</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>mod_proxy_cluster.so</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>mod_advertise.so</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="sect-mod_cluster-Quick_Start_Guide-Configure_httpd">
+ <title>Configure httpd</title>
+ <para>
+ Add the following to <filename>httpd.conf</filename>. If you have extracted the download bundle to root, as shown above, and are using that extract as your httpd install, <filename>httpd.conf</filename> is located in <filename>opt/jboss/httpd/httpd/conf/</filename>.
+ </para>
+
+<programlisting>
+LoadModule proxy_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy.so
+LoadModule proxy_ajp_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_ajp.so
+LoadModule slotmem_module /opt/jboss/httpd/lib/httpd/modules/mod_slotmem.so
+LoadModule manager_module /opt/jboss/httpd/lib/httpd/modules/mod_manager.so
+LoadModule proxy_cluster_module /opt/jboss/httpd/lib/httpd/modules/mod_proxy_cluster.so
+LoadModule advertise_module /opt/jboss/httpd/lib/httpd/modules/mod_advertise.so
+
+Listen 10.33.144.3:6666
+<VirtualHost 10.33.144.3:6666>
+
+ <Directory />
+ Order deny,allow
+ Deny from all
+ Allow from 10.33.144.
+ </Directory>
+
+KeepAliveTimeout 60
+MaxKeepAliveRequests 0
+
+ManagerBalancerName mycluster
+AdvertiseFrequency 5
+
+</VirtualHost>
+</programlisting>
+ <para>
+ If you are using your own install of httpd, <filename>httpd.conf</filename> is found in the install <filename>conf</filename> directory. The content to add to <filename>httpd.conf</filename> is slightly different from the above (different path to the various <filename>.so</filename> files):
+ </para>
+
+<programlisting>
+LoadModule proxy_module modules/mod_proxy.so
+LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
+LoadModule slotmem_module modules/mod_slotmem.so
+LoadModule manager_module modules/mod_manager.so
+LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
+LoadModule advertise_module modules/mod_advertise.so
+
+Listen 10.33.144.3:6666
+<VirtualHost 10.33.144.3:6666>
+
+ <Directory />
+ Order deny,allow
+ Deny from all
+ Allow from 10.33.144.
+ </Directory>
+
+KeepAliveTimeout 60
+MaxKeepAliveRequests 0
+
+ManagerBalancerName mycluster
+AdvertiseFrequency 5
+
+</VirtualHost>
+</programlisting>
+ </section>
+
+ <section id="sect-mod_cluster-Quick_Start_Guide-Install_the_Java_side_binaries">
+ <title>Install the Java-side binaries</title>
+ <para>
+ Extract the java-side binary to a temporary directory. The following assumes it was extracted to <filename>/tmp/mod-cluster</filename>.
+ </para>
+ <para>
+ The next step depends on whether your target server is JBoss AS or JBossWeb/Tomcat.
+ </para>
+ <formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_AS_5.x_and_up">
+ <title>Installing in JBoss AS 5.x and up</title>
+ <para>
+ Assume that <filename>$JBOSS_HOME </filename> indicates the root of your JBoss AS install and that you want to use mod_cluster in the AS <literal>all</literal> config:
+ </para>
+ </formalpara>
+
+<programlisting>
+cp -r /tmp/mod-cluster/mod-cluster.sar $JBOSS_HOME/server/all/deploy
+</programlisting>
+ <formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_Web_or_Tomcat">
+ <title>Installing in JBoss Web or Tomcat</title>
+ <para>
+ Assume <filename>$CATALINA_HOME</filename> indicates the root of your JBossWeb or Tomcat install:
+ </para>
+ </formalpara>
+
+<programlisting>
+cp -r /tmp/mod-cluster/JBossWeb-Tomcat/lib/* $CATALINA_HOME/lib/
+</programlisting>
+ <formalpara id="form-mod_cluster-Install_the_Java_side_binaries-Installing_in_JBoss_AS_4.2.x_or_4.3.x">
+ <title>Installing in JBoss AS 4.2.x or 4.3.x</title>
+ <para>
+ Assuming <filename>$JBOSS_HOME</filename> indicates the root of your JBoss AS install and that you want to use mod_cluster in the AS <literal>all</literal> config:
+ </para>
+ </formalpara>
+
+<programlisting>
+cp -r /tmp/mod-cluster/JBossWeb-Tomcat/lib/mod-cluster.jar $JBOSS_HOME/server/all/deploy/jboss-web.deployer
+</programlisting>
+ </section>
+
+ <section id="sect-mod_cluster-Quick_Start_Guide-Configuring_JBoss_AS_JBoss_Web_or_Tomcat">
+ <title>Configuring JBoss AS, JBoss Web or Tomcat</title>
+ <para>
+ mod_cluster is integrated into the web server by adding an implementation of the <application>Tomcat LifecycleListener</application> interface to the server's configuration, and by giving each node a unique name.
+ </para>
+ <formalpara id="form-mod_cluster-Configuring_JBoss_AS_JBoss_Web_or_Tomcat-Integrate_mod_cluster_with_JBoss_ASs_embedded_JBossWeb">
+ <title>Integrate mod_cluster with JBoss AS's embedded JBossWeb</title>
+ <para>
+ Assuming <filename>$JBOSS_HOME</filename> indicates the root of your JBoss AS install and that you want to use mod_cluster in the AS's <literal>all</literal> config:
+ <orderedlist>
+ <listitem>
+ <para>
+ Edit the <filename>$JBOSS_HOME/server/all/deploy/jbossweb.sar/server.xml</filename> file, adding the following next to the other <application>LifecycleListener</application> elements:
+ </para>
+
+<screen>
+ <Listener className="org.jboss.web.tomcat.service.deployers.MicrocontainerIntegrationLifecycleListener"
+ delegateBeanName="ModClusterService"/>
+</screen>
+ </listitem>
+ <listitem>
+ <para>
+ Edit the <filename>$JBOSS_HOME/server/all/deploy/jbossweb.sar/META-INF/jboss-beans.xml</filename> file, adding the following next to the other <application>depends</application> elements:
+ </para>
+
+<screen>
+ <depends>ModClusterService</depends/>
+</screen>
+ </listitem>
+ </orderedlist>
+ </para>
+ </formalpara>
+ <formalpara id="form-mod_cluster-Configuring_JBoss_AS_JBoss_Web_or_Tomcat-Integrate_mod_cluster_with_standalone_JBossWeb_or_Tomcat">
+ <title>Integrate mod_cluster with standalone JBossWeb or Tomcat</title>
+ <para>
+ Edit the <filename>$CATALINA_HOME/conf/server.xml</filename> file, adding the following next to the other <application>LifecycleListener</application> elements:
+ </para>
+ </formalpara>
+
+<programlisting>
+ <Listener className="org.jboss.modcluster.ModClusterListener"
+ advertise="true"/>
+</programlisting>
+ <formalpara id="form-mod_cluster-Configuring_JBoss_AS_JBoss_Web_or_Tomcat-Integrate_mod_cluster_with_JBoss_AS_4.2.x_and_4.3.x">
+ <title>Integrate mod_cluster with JBoss AS 4.2.x and 4.3.x</title>
+ <para>
+ Edit the <filename>$JBOSS_HOME/server/all/deploy/jboss-web.deployer/server.xml</filename> file, adding the following next to the other <application>LifecycleListener</application> elements:
+ </para>
+ </formalpara>
+
+<programlisting>
+ <Listener className="org.jboss.modcluster.ModClusterListener"
+ advertise="true"/>
+</programlisting>
+ <formalpara id="form-mod_cluster-Configuring_JBoss_AS_JBoss_Web_or_Tomcat-Configure_a_jvmRoute">
+ <title>Configure a jvmRoute</title>
+ <para>
+ Each back end server in the cluster needs to have a unique name, known as a "jvmRoute". This is configured by adding an attribute to the <application>Engine</application> element in <filename>server.xml</filename>.
+ </para>
+ </formalpara>
+
+<programlisting>
+ <Engine name="jboss.web" defaultHost="localhost" jvmRoute="node01">
+</programlisting>
+ <para>
+ If your cluster includes multiple back-end servers, you must assign a different jvmRoute to each server.
+ </para>
+ </section>
+
+ <section id="sect-mod_cluster-Quick_Start_Guide-Start_httpd">
+ <title>Start httpd</title>
+ <para>
+ To start httpd enter the following:
+ </para>
+
+<programlisting>
+/opt/jboss/httpd/sbin/apachectl start
+</programlisting>
+ </section>
+
+ <section id="sect-mod_cluster-Quick_Start_Guide-Start_the_back_end_server">
+ <title>Start the back end server</title>
+ <formalpara id="form-mod_cluster-Start_the_back_end_server-Starting_JBoss_AS">
+ <title>Starting JBoss AS</title>
+ <para>
+ To start <application>JBoss AS</application> enter the following:
+ </para>
+ </formalpara>
+
+<programlisting>
+cd $JBOSS_HOME/bin
+./run.sh -c all
+</programlisting>
+ <formalpara id="form-mod_cluster-Start_the_back_end_server-Starting_JBossWeb_or_Tomcat">
+ <title>Starting JBossWeb or Tomcat</title>
+ <para>
+ To start <application>JBossWEB</application> or <application>Tomcat</application> enter the following:
+ </para>
+ </formalpara>
+
+<programlisting>
+cd $CATALINA_HOME
+./startup.sh
+</programlisting>
+ </section>
+
+ <section id="sect-mod_cluster-Quick_Start_Guide-Set_up_more_back_end_servers">
+ <title>Set up more back end servers</title>
+ <para>
+ Repeat the back end server install and configuration steps; just be sure to use a different jvmRoute for each server.
+ </para>
+ </section>
+
+ <section id="sect-mod_cluster-Quick_Start_Guide-Experiment_with_the_Load_Balancing_Demo_Application">
+ <title>Experiment with the Load Balancing Demo Application</title>
+ <para>
+ The load balancing demo application is a good way to learn about mod_cluster's capabilities.
+ </para>
+ </section>
+
+</chapter>
+
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/Revision_History.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,25 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<appendix id="appe-mod_cluster-Revision_History">
+ <title>Revision History</title>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>0</revnumber>
+ <date>Wed Dec 08 2009</date>
+ <author>
+ <firstname>Gary</firstname>
+ <surname>Meintjes</surname>
+ <email>gmeintje at redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Initial formatting of book for publishing with Publican</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ </revhistory>
+ </simpara>
+</appendix>
+
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.ent
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.ent (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.ent 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "Documentation">
+<!ENTITY BOOKID "mod_cluster">
+<!ENTITY YEAR "2009">
+<!ENTITY HOLDER "Red Hat Inc.">
Added: projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml
===================================================================
--- projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml (rev 0)
+++ projects/docs/enterprise/5.0/mod_cluster/en-US/mod_cluster.xml 2009-12-09 00:11:05 UTC (rev 97571)
@@ -0,0 +1,15 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<book>
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <!-- <xi:include href="Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+ <xi:include href="Overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="QuickStartGuide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ConfigurationForJBossAS.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="MigratingFromModJK.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <index />
+</book>
+
More information about the jboss-cvs-commits
mailing list