Author: mmcallis Date: 2008-06-17 22:31:40 -0400 (Tue, 17 Jun 2008) New Revision: 11073 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/clustering.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/sso.xml Log: adding "Apache" to "Tomcat" references... Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/clustering.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/clustering.xml 2008-06-18 02:12:37 UTC (rev 11072) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/clustering.xml 2008-06-18 02:31:40 UTC (rev 11073) @@ -201,11 +201,11 @@ <sect1> <title>Setup</title> <para>We are going to outline how to setup a two node cluster on the same machine in order to test JBoss Portal HA. The only - missing part from the full fledged setup is the addition of a load balancer in front of Tomcat. However a lot of documentation + missing part from the full fledged setup is the addition of a load balancer in front of Apache Tomcat. However a lot of documentation exist on the subject. A detailed step by step setup of Apache and mod_jk is available from the <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingMod_jk1.2WithJBos... Wiki</ulink>.</para> <para>As we need two application servers running at the same time, we must avoid any conflict. For instance we will - need Tomcat to bind its socket on two different ports otherwise a network conflict will occur. We will leverage + need Apache Tomcat to bind its socket on two different ports otherwise a network conflict will occur. We will leverage the service binding manager <ulink url="http://docs.jboss.org/jbossas/jboss4guide/r3/html/ch10.html&quo... chapter</ulink> of the JBoss AS documentation.</para> <para>The first step is to copy the <emphasis>all</emphasis> configuration of JBoss into two separate Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-06-18 02:12:37 UTC (rev 11072) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-06-18 02:31:40 UTC (rev 11073) @@ -19,7 +19,7 @@ <sect1> <title>Changing the Port</title> <para> - It is common for web services to run on port 80. By default, JBoss EAP and JBoss AS use port 8080. If you can not use <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingPortForwardingWit... forwarding</ulink>, it is recommended to change the port JBoss EAP or JBoss AS listens on. To change the default port, open the <filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml</filename> file, and edit the <computeroutput>Connector port</computeroutput> value for the <computeroutput>jboss.web</computeroutput> service; however, this configuration only applies to Tomcat: + It is common for web services to run on port 80. By default, JBoss EAP and JBoss AS use port 8080. If you can not use <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingPortForwardingWit... forwarding</ulink>, it is recommended to change the port JBoss EAP or JBoss AS listens on. To change the default port, open the <filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml</filename> file, and edit the <computeroutput>Connector port</computeroutput> value for the <computeroutput>jboss.web</computeroutput> service; however, this configuration only applies to Apache Tomcat: </para> <para> <screen> @@ -31,7 +31,7 @@ This example changes the default port to port 8088. The JBoss EAP or JBoss AS server must be restarted before the new port settings take affect. </para> <para> - The default SSL port is 8843. To enable HTTPS support, refer to the <ulink url="http://docs.jboss.org/jbossas/jboss4guide/r4/html/ch9.chapt.htm... AS Guide</ulink>. For further information, refer to <ulink url="http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html">... SSL configuration how-to</ulink>. + The default SSL port is 8843. To enable HTTPS support, refer to the <ulink url="http://docs.jboss.org/jbossas/jboss4guide/r4/html/ch9.chapt.htm... AS Guide</ulink>. For further information, refer to the <ulink url="http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html">... Tomcat SSL configuration how-to</ulink>. </para> <para> Please refer to <xref linkend="wsrp-ports"/> to update the WSRP service after having changed the port. @@ -126,9 +126,9 @@ <note> <title>Changing the context-root</title> <para> - By default, Tomcat holds on to the root context, <emphasis>/</emphasis>. You may need to remove the <filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/ROOT.war/</filename> directory, + By default, Apache Tomcat holds on to the root context, <emphasis>/</emphasis>. You may need to remove the <filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/ROOT.war/</filename> directory, or add a <filename>jboss-web.xml</filename> file, which declares another - context-root other than <emphasis>/</emphasis>, under the <filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/</filename> directory, for the above changes to take affect. The following is an example <filename>jboss-web.xml</filename> file, which changes the Tomcat context path to <computeroutput>/tomcat-root</computeroutput>: + context-root other than <emphasis>/</emphasis>, under the <filename>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/</filename> directory, for the above changes to take affect. The following is an example <filename>jboss-web.xml</filename> file, which changes the Apache Tomcat context path to <computeroutput>/tomcat-root</computeroutput>: </para> <para> <screen><![CDATA[ Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/sso.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/sso.xml 2008-06-18 02:12:37 UTC (rev 11072) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/sso.xml 2008-06-18 02:31:40 UTC (rev 11073) @@ -24,15 +24,15 @@ mechanisms.</para> </sect1> <sect1> - <title>Using Tomcat Valve</title> + <title>Using Apache Tomcat Valve</title> <para>JBoss Application Server embeds Apache Tomcat as the default servlet container. Tomcat provides a builtin SSO support using a valve. The Single Sign On Valve caches credentials on the server side, and then invisibly authenticate users when they reach different web applications. Credentials are stored in a host-wide session which means that SSO will be effective throughout the session. </para> <sect2> - <title>Enabling Tomcat SSO Valve</title> + <title>Enabling Apache Tomcat SSO Valve</title> <para> - To enable SSO valve in Tomcat you should uncomment the following line + To enable SSO valve in Apache Tomcat you should uncomment the following line <programlisting><![CDATA[<Valve className=’org.apache.catalina.authenticator.SingleSignOn’/>]]></programlisting> in the <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml</literal> file. More information can be found <ulink url="http://www.jboss.org/wiki/Wiki.jsp?page=SingleSignOn">h...;. @@ -168,7 +168,7 @@ <emphasis>$JBOSS_HOME/server/default/deploy/cas.war/WEB-INF/lib</emphasis>. </listitem> <listitem> - Edit <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-server.war/WEB-INF/context.xml</emphasis> file and enable proper tomcat valve + Edit <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-server.war/WEB-INF/context.xml</emphasis> file and enable proper Apache Tomcat Valve by uncommenting following lines: <programlisting> <![CDATA[ @@ -278,7 +278,7 @@ slightly different for other deployment scenarios. Both JBoss Portal and JOSSO will need to be configured to authenticate against same database or LDAP server. Please see JOSSO documentation to learn how to setup it up against proper identity store.</note> <note>Configuration below assumes that JOSSO is already installed and deployed in the JBoss Application Server. This involves adding proper jar files - into the classpath and altering several configuration files (adding tomcat valves, security realm and specific JOSSO configuration files). + into the classpath and altering several configuration files (adding Apache Tomcat Valves, security realm and specific JOSSO configuration files). For JBoss setup please refer to JOSSO <ulink url="http://www.josso.org/jboss4-howto.html">documentation&l... <sect2> <title>Integration steps</title> @@ -291,7 +291,7 @@ <emphasis>$JBOSS_HOME/server/default/deploy/josso.ear/josso.war/WEB-INF/lib</emphasis>. </listitem> <listitem> - Edit <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-server.war/WEB-INF/context.xml</emphasis> file and enable proper tomcat valve + Edit <emphasis>$JBOSS_HOME/server/default/deploy/jboss-portal.sar/portal-server.war/WEB-INF/context.xml</emphasis> file and enable proper Apache Tomcat Valve by uncommenting following lines: <programlisting> <![CDATA[