Author: prabhat.jha(a)jboss.com Date: 2009-01-21 14:41:46 -0500 (Wed, 21 Jan 2009) New Revision: 12597 Added: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/clustering.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/hibernate.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/identity.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/jbossweb.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/jvm.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/overview.xml Removed: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/clustering.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/hibernate.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/identity.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jbossweb.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jvm.xml docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/overview.xml Modified: docs/enterprise/branches/prabhat/Tuning_Guide/ Log: Property changes on: docs/enterprise/branches/prabhat/Tuning_Guide ___________________________________________________________________ Name: svn:externals - docbook-support http://anonsvn.jboss.org/repos/portal/tools/docbook/support/ docbook-support/styles http://anonsvn.jboss.org/repos/portal/tools/docbook/styles/renaissance/ + Copied: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/clustering.xml (from rev 12596, docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/clustering.xml) =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/clustering.xml (rev 0) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/clustering.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -0,0 +1,95 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="clustering"> + + <title>Clustering Tuning</title> + + <sect1> + <title> + Enable Buddy Replication for Portal and Portlet Session + Clustering + </title> + Portal and Portlet Session are merely wrappers around + HttpSession so most of HTTP session clustering optimization + applies to JBPP as well. EPP uses clustering configuration of + JBoss Web so changes go to + <filename> + jboss-web-cluster.sar/META-INF/jboss-service.xml + </filename> + . To enable buddy replication, change the value of + <emphasis>buddyReplicationEnabled</emphasis> + to true. + + </sect1> + + <sect1> + <title>Hibernate and JBoss Cache Configuration</title> + + EPP uses JBoss Cache as a second level cache for Hibernate and + this configuration is not defined in JBoss Cache definition used + for Portal and Portlet Session. Instead the configuration is + defined at + <filename> + jboss-portal-ha.sar/META-INF/jboss-service.xml + </filename> + + <sect2> + <title>Optimistic Locking (OL)</title> + Our tests have shown that optimistic locking performs better + under heavy load and it scales (horizontally) better as + well. However, your use case may not show the same behavior + and for you pessimistic locking may be a better + configuration. To enable optimistic locking, modify + TreeCache mbean definition as follows: + <programlisting role="XML"> + <![CDATA[ + <attribute name="NodeLockingScheme">OPTIMISTIC</attribute> + <attribute name="CacheMode">INVALIDATION_SYNC</attribute> + ]]> + </programlisting> + + <note> + If you have not disabled query cache, then you should + not use INVALIATION_SYNC as CACHE_MODE. Use REPL_SYNC + instead. + </note> + + </sect2> + <sect2> + <title>Pessimistic Locking (PL)</title> + When using Pessimistic Locking (PL), change isolation level + to READ_COMMITTED (RC). Please see <ulink url="http://lists.jboss.org/pipermail/jbosscache-dev/2008-July/00240... + to see why it is okay to relax the isolation level from + REPEATABLE_READ (RR). As expected, RC has better performance than RR. + </sect2> + + <sect2> + <title>Cache Eviction Policy</title> + If you disabled lazy loading, then you can control number of + objects and time they can reside in memory by configuring + EvictionPolicyConfig attribute of TreeCache at + <filename> + jboss-portal- ha.sar/META-INF/jboss-service.xml + </filename> + + <programlisting role="XML"> + <![CDATA[ + <attribute name="EvictionPolicyConfig"> + <config> + <attribute name="wakeUpIntervalSeconds">5</attribute> + <region name="/_default_"> + <attribute name="maxNodes">5000</attribute> + <attribute name="timeToLiveSeconds">1000</attribute> + </region> + </config> + </attribute> + ]]> + </programlisting> + </sect2> + + </sect1> +</chapter> + + + + + Copied: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/hibernate.xml (from rev 12596, docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/hibernate.xml) =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/hibernate.xml (rev 0) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/hibernate.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -0,0 +1,97 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="hibernate"> + + <title>Hibernate Tuning</title> + + <sect1> + <title>Enable/Disable Lazy Loading</title> + EPP assumes that number of portal pages and portlets window will + be large and hence does not cache these objects. As a result, + there could be many direct DB connection. But depending on use + case, lazy loading should be turned on and off partially or in + its entirety. Modify + <filename> + deploy/jboss-portal[-ha].sar/conf/hibernate/*/domain.hbm.xml + </filename> + and change + <emphasis>lazy=”extra”</emphasis> + to + <emphasis>lazy=”true”</emphasis> + or + <emphasis>lazy=”false”</emphasis> + <orderedlist numeration="upperroman"> + <listitem> + Modify attribute for the class + org.jboss.portal.core.impl.model.portal.ObjectNode + <programlisting role="XML"> + <![CDATA[ + <map name="children" inverse="true" cascade="none" fetch="select" lazy="true"> + <cache usage="transactional" /> //[“read-write” in non clustered] + <key column="PARENT_KEY" /> + <map-key type="org.jboss.portal.jems.hibernate.MagicString" column="NAME" /> + <one-to-many class="org.jboss.portal.core.impl.model.portal.ObjectNode" /> + </map> + ]]> + </programlisting> + </listitem> + <listitem> + Enable caching for displayNames for the class + org.jboss.portal.core.impl.model.portal.PortalObjectImpl + <programlisting role="XML"> + <![CDATA[ + <map name="displayNames" cascade="none" fetch="select" lazy="true" + table="JBP_PORTAL_OBJECT_DNAMES"> + <cache usage="transactional" /> <!-- [“read-write” in non clustered]--> + <key column="INSTANCE_PK" /> + <map-key type="locale" column="LOCALE" /> + <element type="string" column="TEXT" /> + </map> + ]]> + </programlisting> + </listitem> + <listitem> + Same as above for + <filename>hibernate/instance/domain.hbm.xml</filename> + for displayNames map. + </listitem> + <listitem> + Enable/disable lazy loading for set “users” in + <filename>hibernate/user/domain.hbm.xml</filename> + </listitem> + <listitem> + Disabling lazy loading implies there will be many + objects in memory. You can control how many objects + would need to reside in memory at a time and for how + long before they are evicted by modifying values at + <filename>conf/hibernate/*/ehcache.xml</filename> + in non clustered configuration. These parameters would + need to be changed as per the use case. For clustered + configuration, see the chapter on <xref linkend="clustering"> clustering + configuration.</xref> + </listitem> + </orderedlist> + </sect1> + + <sect1> + <title>Enable/Disable Query Cache</title> + EPP no longer uses query cache. Unless EPP is customized to use + query cache, it should be disabled by turning the value of + property "cache.use_query_cache" to false in following files: + + <itemizedlist> + <listitem><filename>hibernate/instance/hibernate.cfg.xml </filename></listitem> + <listitem><filename>hibernate/portal/hibernate.cfg.xml </filename></listitem> + <listitem><filename>hibernate/portlet/hibernate.cfg.xml</filename></listitem> + <listitem><filename>hibernate/user/hibernate.cfg.xml</filename></listitem> + </itemizedlist> + + Disabling query cache also allows to use<emphasis>INVALIDATION_SYNC</emphasis> as + CACHE_MODE when using optimistic locking with JBoss Cache and + Hibernate as explained in the clustering section. + </sect1> +</chapter> + + + + + Copied: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/identity.xml (from rev 12596, docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/identity.xml) =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/identity.xml (rev 0) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/identity.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="identity"> + + <title>Identity</title> + + <sect1> + <title>Cache Login Credentials</title> + EPP uses JaasSecurityManagerService to obtain current users + roles that are cached by JAAS during authentication. So altering + cache invalidation can affect performance. Please see the details at + <ulink + url="http://wiki.jboss.org/wiki/CachingLoginCredentials"> + </ulink>. + </sect1> + + <sect1> + <title>Miscellaneous</title> + + </sect1> +</chapter> Copied: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/jbossweb.xml (from rev 12596, docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jbossweb.xml) =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/jbossweb.xml (rev 0) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/jbossweb.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -0,0 +1,39 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="jbossweb"> + + <title>JBoss Web Tuning</title> + + <sect1> + <title> HTTP/AJP connector threads </title> + Increase number of HTTP/AJP connector threads. It's recommended + to set this value to <emphasis> 250 * n </emphasis> where n is number of CPU in your + server. Depending on nature of your application, this can be set + higher or lower. Modify value of maxThreads in in + <filename>deploy/jboss-web.deployer/server.xml</filename> + + <programlisting role="XML"> + <![CDATA[ + <Connector port="8009" address="${jboss.bind.address}" + protocol="AJP/1.3" emptySessionPath="true" enableLookups="false" + redirectPort="8443" maxThreads="1500" /> + ]]> + + </programlisting> + </sect1> + + <sect1> + <title> Global Session Timeout </title> + Reduce global session timeout to your need. The default value of + 30 min is too high for most use cases. A lower session timeout + results into a more consistent memory footprint and more + consistent throughput. Modify + <filename>deploy/jboss-web.deployer/conf/web.xml</filename> + <programlisting role="XML"> + <![CDATA[ + <session-config> + <session-timeout>15</session-timeout> + </session-config> + ]]> + </programlisting> + </sect1> +</chapter> Copied: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/jvm.xml (from rev 12596, docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jvm.xml) =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/jvm.xml (rev 0) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/jvm.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -0,0 +1,25 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="jvm"> + + <title>JVM Tuning</title> + + <sect1> + <title>Use Large Pages</title> + When using 64 bit Linux systems , use Linux's large memory page + support. Without large page support, increasing heap size may + not increase your performance. Modify JAVA_OPTS under + <filename>$JBOSS_HOME/bin/run.conf</filename> + to add -XX:+ UseLargePages. Please see EAP tuning guide or the + description at + <ulink + url="http://jbossworld.com/downloads/pdf/thursday/JBOSS_10-1050am_JB... + </ulink> + for the details. + </sect1> + + <sect1> + <title>Garbage Collection (GC) Tuning</title> + Depending on nature of your application, adding <emphasis> XX:+UseConcMarkSweepGC -XX:+UseParNewGC </emphasis> + may optimize GC collection behavior. + </sect1> +</chapter> Deleted: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/clustering.xml =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/clustering.xml 2009-01-21 19:25:46 UTC (rev 12596) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/clustering.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -1,95 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="clustering"> - - <title>Clustering Tuning</title> - - <sect1> - <title> - Enable Buddy Replication for Portal and Portlet Session - Clustering - </title> - Portal and Portlet Session are merely wrappers around - HttpSession so most of HTTP session clustering optimization - applies to JBPP as well. EPP uses clustering configuration of - JBoss Web so changes go to - <filename> - jboss-web-cluster.sar/META-INF/jboss-service.xml - </filename> - . To enable buddy replication, change the value of - <emphasis>buddyReplicationEnabled</emphasis> - to true. - - </sect1> - - <sect1> - <title>Hibernate and JBoss Cache Configuration</title> - - EPP uses JBoss Cache as a second level cache for Hibernate and - this configuration is not defined in JBoss Cache definition used - for Portal and Portlet Session. Instead the configuration is - defined at - <filename> - jboss-portal-ha.sar/META-INF/jboss-service.xml - </filename> - - <sect2> - <title>Optimistic Locking (OL)</title> - Our tests have shown that optimistic locking performs better - under heavy load and it scales (horizontally) better as - well. However, your use case may not show the same behavior - and for you pessimistic locking may be a better - configuration. To enable optimistic locking, modify - TreeCache mbean definition as follows: - <programlisting role="XML"> - <![CDATA[ - <attribute name="NodeLockingScheme">OPTIMISTIC</attribute> - <attribute name="CacheMode">INVALIDATION_SYNC</attribute> - ]]> - </programlisting> - - <note> - If you have not disabled query cache, then you should - not use INVALIATION_SYNC as CACHE_MODE. Use REPL_SYNC - instead. - </note> - - </sect2> - <sect2> - <title>Pessimistic Locking (PL)</title> - When using Pessimistic Locking (PL), change isolation level - to READ_COMMITTED (RC). Please see <ulink url="http://lists.jboss.org/pipermail/jbosscache-dev/2008-July/00240... - to see why it is okay to relax the isolation level from - REPEATABLE_READ (RR). As expected, RC has better performance than RR. - </sect2> - - <sect2> - <title>Cache Eviction Policy</title> - If you disabled lazy loading, then you can control number of - objects and time they can reside in memory by configuring - EvictionPolicyConfig attribute of TreeCache at - <filename> - jboss-portal- ha.sar/META-INF/jboss-service.xml - </filename> - - <programlisting role="XML"> - <![CDATA[ - <attribute name="EvictionPolicyConfig"> - <config> - <attribute name="wakeUpIntervalSeconds">5</attribute> - <region name="/_default_"> - <attribute name="maxNodes">5000</attribute> - <attribute name="timeToLiveSeconds">1000</attribute> - </region> - </config> - </attribute> - ]]> - </programlisting> - </sect2> - - </sect1> -</chapter> - - - - - Deleted: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/hibernate.xml =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/hibernate.xml 2009-01-21 19:25:46 UTC (rev 12596) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/hibernate.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -1,97 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="hibernate"> - - <title>Hibernate Tuning</title> - - <sect1> - <title>Enable/Disable Lazy Loading</title> - EPP assumes that number of portal pages and portlets window will - be large and hence does not cache these objects. As a result, - there could be many direct DB connection. But depending on use - case, lazy loading should be turned on and off partially or in - its entirety. Modify - <filename> - deploy/jboss-portal[-ha].sar/conf/hibernate/*/domain.hbm.xml - </filename> - and change - <emphasis>lazy=”extra”</emphasis> - to - <emphasis>lazy=”true”</emphasis> - or - <emphasis>lazy=”false”</emphasis> - <orderedlist numeration="upperroman"> - <listitem> - Modify attribute for the class - org.jboss.portal.core.impl.model.portal.ObjectNode - <programlisting role="XML"> - <![CDATA[ - <map name="children" inverse="true" cascade="none" fetch="select" lazy="true"> - <cache usage="transactional" /> //[“read-write” in non clustered] - <key column="PARENT_KEY" /> - <map-key type="org.jboss.portal.jems.hibernate.MagicString" column="NAME" /> - <one-to-many class="org.jboss.portal.core.impl.model.portal.ObjectNode" /> - </map> - ]]> - </programlisting> - </listitem> - <listitem> - Enable caching for displayNames for the class - org.jboss.portal.core.impl.model.portal.PortalObjectImpl - <programlisting role="XML"> - <![CDATA[ - <map name="displayNames" cascade="none" fetch="select" lazy="true" - table="JBP_PORTAL_OBJECT_DNAMES"> - <cache usage="transactional" /> <!-- [“read-write” in non clustered]--> - <key column="INSTANCE_PK" /> - <map-key type="locale" column="LOCALE" /> - <element type="string" column="TEXT" /> - </map> - ]]> - </programlisting> - </listitem> - <listitem> - Same as above for - <filename>hibernate/instance/domain.hbm.xml</filename> - for displayNames map. - </listitem> - <listitem> - Enable/disable lazy loading for set “users” in - <filename>hibernate/user/domain.hbm.xml</filename> - </listitem> - <listitem> - Disabling lazy loading implies there will be many - objects in memory. You can control how many objects - would need to reside in memory at a time and for how - long before they are evicted by modifying values at - <filename>conf/hibernate/*/ehcache.xml</filename> - in non clustered configuration. These parameters would - need to be changed as per the use case. For clustered - configuration, see the chapter on <xref linkend="clustering"> clustering - configuration.</xref> - </listitem> - </orderedlist> - </sect1> - - <sect1> - <title>Enable/Disable Query Cache</title> - EPP no longer uses query cache. Unless EPP is customized to use - query cache, it should be disabled by turning the value of - property "cache.use_query_cache" to false in following files: - - <itemizedlist> - <listitem><filename>hibernate/instance/hibernate.cfg.xml </filename></listitem> - <listitem><filename>hibernate/portal/hibernate.cfg.xml </filename></listitem> - <listitem><filename>hibernate/portlet/hibernate.cfg.xml</filename></listitem> - <listitem><filename>hibernate/user/hibernate.cfg.xml</filename></listitem> - </itemizedlist> - - Disabling query cache also allows to use<emphasis>INVALIDATION_SYNC</emphasis> as - CACHE_MODE when using optimistic locking with JBoss Cache and - Hibernate as explained in the clustering section. - </sect1> -</chapter> - - - - - Deleted: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/identity.xml =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/identity.xml 2009-01-21 19:25:46 UTC (rev 12596) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/identity.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -1,20 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="identity"> - - <title>Identity</title> - - <sect1> - <title>Cache Login Credentials</title> - EPP uses JaasSecurityManagerService to obtain current users - roles that are cached by JAAS during authentication. So altering - cache invalidation can affect performance. Please see the details at - <ulink - url="http://wiki.jboss.org/wiki/CachingLoginCredentials"> - </ulink>. - </sect1> - - <sect1> - <title>Miscellaneous</title> - - </sect1> -</chapter> Deleted: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jbossweb.xml =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jbossweb.xml 2009-01-21 19:25:46 UTC (rev 12596) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jbossweb.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -1,39 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="jbossweb"> - - <title>JBoss Web Tuning</title> - - <sect1> - <title> HTTP/AJP connector threads </title> - Increase number of HTTP/AJP connector threads. It's recommended - to set this value to <emphasis> 250 * n </emphasis> where n is number of CPU in your - server. Depending on nature of your application, this can be set - higher or lower. Modify value of maxThreads in in - <filename>deploy/jboss-web.deployer/server.xml</filename> - - <programlisting role="XML"> - <![CDATA[ - <Connector port="8009" address="${jboss.bind.address}" - protocol="AJP/1.3" emptySessionPath="true" enableLookups="false" - redirectPort="8443" maxThreads="1500" /> - ]]> - - </programlisting> - </sect1> - - <sect1> - <title> Global Session Timeout </title> - Reduce global session timeout to your need. The default value of - 30 min is too high for most use cases. A lower session timeout - results into a more consistent memory footprint and more - consistent throughput. Modify - <filename>deploy/jboss-web.deployer/conf/web.xml</filename> - <programlisting role="XML"> - <![CDATA[ - <session-config> - <session-timeout>15</session-timeout> - </session-config> - ]]> - </programlisting> - </sect1> -</chapter> Deleted: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jvm.xml =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jvm.xml 2009-01-21 19:25:46 UTC (rev 12596) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/jvm.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -1,25 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="jvm"> - - <title>JVM Tuning</title> - - <sect1> - <title>Use Large Pages</title> - When using 64 bit Linux systems , use Linux's large memory page - support. Without large page support, increasing heap size may - not increase your performance. Modify JAVA_OPTS under - <filename>$JBOSS_HOME/bin/run.conf</filename> - to add -XX:+ UseLargePages. Please see EAP tuning guide or the - description at - <ulink - url="http://jbossworld.com/downloads/pdf/thursday/JBOSS_10-1050am_JB... - </ulink> - for the details. - </sect1> - - <sect1> - <title>Garbage Collection (GC) Tuning</title> - Depending on nature of your application, adding <emphasis> XX:+UseConcMarkSweepGC -XX:+UseParNewGC </emphasis> - may optimize GC collection behavior. - </sect1> -</chapter> Deleted: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/overview.xml =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/overview.xml 2009-01-21 19:25:46 UTC (rev 12596) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/overview.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -1,19 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="overview"> - <title>Overview</title> - <para> - Since JBoss Enterprise Portal Platform (EPP) uses many services - of JBoss Enterprise Application Platform (EAP), all tunings and - configurations that are recommended for EAP apply to EPP as well - hence most of those tunings will not be covered here. Following - is a guideline that may help achieve best out of EPP. - </para> - - <para> - This document is intended for Portlet Developers, Portal - administrators, and those wishing to implement/extend the JBoss - Portal framework. - </para> - - -</chapter> Copied: docs/enterprise/branches/prabhat/Tuning_Guide/en-US/overview.xml (from rev 12596, docs/enterprise/branches/prabhat/Tuning_Guide/en-US/modules/overview.xml) =================================================================== --- docs/enterprise/branches/prabhat/Tuning_Guide/en-US/overview.xml (rev 0) +++ docs/enterprise/branches/prabhat/Tuning_Guide/en-US/overview.xml 2009-01-21 19:41:46 UTC (rev 12597) @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="overview"> + <title>Overview</title> + <para> + Since JBoss Enterprise Portal Platform (EPP) uses many services + of JBoss Enterprise Application Platform (EAP), all tunings and + configurations that are recommended for EAP apply to EPP as well + hence most of those tunings will not be covered here. Following + is a guideline that may help achieve best out of EPP. + </para> + + <para> + This document is intended for Portlet Developers, Portal + administrators, and those wishing to implement/extend the JBoss + Portal framework. + </para> + + +</chapter>