Author: buildbot
Date: Mon Aug 13 20:47:36 2012
New Revision: 828830
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/main.pageCache
websites/production/cxf/content/fediz-idp.html
Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/fediz-idp.html
==============================================================================
--- websites/production/cxf/content/fediz-idp.html (original)
+++ websites/production/cxf/content/fediz-idp.html Mon Aug 13 20:47:36 2012
@@ -146,7 +146,7 @@ Apache CXF -- Fediz IDP
<p>The Fediz IDP has been tested with Tomcat 6 and 7 but should be able to
work with any commercial JEE application server.</p>
-<p>It's recommended to set up a dedicated (separate) Tomcat instance for the
IDP compared to the one hosting the RP (relying party) applications. Using
one deployment of Tomcat with multiple CATALINA_BASE instances, as described <a
shape="rect" class="external-link"
href="http://www.shaunabram.com/multiple-tomcat-instances/";
rel="nofollow">here</a> is one option but note any libs in $CATALINA_HOME/lib
folder will be shared throughout each of the activated CATALINA_BASE instances.
Another probably simpler alternative is to copy your Tomcat folder into a
second location and edit its conf/server.xml file and change <a shape="rect"
class="external-link"
href="http://viralpatel.net/blogs/2009/08/running-multiple-instance-apache-tomcat-single-server.html";
rel="nofollow">these port values</a> so they don't conflict with the original
Tomcat installation. </p>
+<p>It's recommended to set up a dedicated (separate) Tomcat instance for the
IDP compared to the one hosting the RP (relying party) applications. Using
one deployment of Tomcat with multiple CATALINA_BASE instances, as described <a
shape="rect" class="external-link"
href="http://www.shaunabram.com/multiple-tomcat-instances/";
rel="nofollow">here</a> is one option but note any libs in $CATALINA_HOME/lib
folder will be shared throughout each of the activated CATALINA_BASE instances.
Another probably simpler alternative is to copy your Tomcat folder into a
second location and edit its conf/server.xml file and <a shape="rect"
class="external-link"
href="http://viralpatel.net/blogs/2009/08/running-multiple-instance-apache-tomcat-single-server.html";
rel="nofollow">change port values</a> (discussed below) so they don't conflict
with the original Tomcat installation. </p>
<p>To start and stop this second Tomcat instance, it is perhaps easiest to
create small startup.sh and shutdown.sh scripts that temporarily redefine
$CATALINA_HOME from the first to the second instance, for example:</p>
