From portal-commits at lists.jboss.org Sat Oct 13 13:31:53 2007 Content-Type: multipart/mixed; boundary="===============3459883515820239334==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r8632 - in docs: trunk/referenceGuide/en/modules and 1 other directory. Date: Sat, 13 Oct 2007 13:31:51 -0400 Message-ID: --===============3459883515820239334== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: chris.laprun(a)jboss.com Date: 2007-10-13 13:31:51 -0400 (Sat, 13 Oct 2007) New Revision: 8632 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/clusteri= ng.xml docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/sso.xml docs/trunk/referenceGuide/en/modules/clustering.xml docs/trunk/referenceGuide/en/modules/sso.xml Log: - Updated to use 4.2.x information. Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/c= lustering.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/cluster= ing.xml 2007-10-13 17:12:01 UTC (rev 8631) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/cluster= ing.xml 2007-10-13 17:31:51 UTC (rev 8632) @@ -163,22 +163,29 @@ ]]> - More information can be found here. + More information can be found here. = Identity clustering - JBoss Portal leverages the servlet container authentication= for its own authentication mechanism. When the user - is authenticated on one particular node he will have to reauthent= icate again if he use another node of the cluster (during - a failover for instance). This is valid only for the FO= RM based authentication which is the default - form of authentication that JBoss Portal uses. Fortunately JBoss = provides transparent reauthentication of the user called - JBoss clustered SSO. Its configuration is in the file $= JBOSS_HOME/server/all/deploy/jbossweb-tomcat55.sar/server.xml - and the clustered sso valve shall be uncommented - -]]> - More information can be found here. + JBoss Portal leverages the servlet container authentication= for its own authentication mechanism. When + the user is authenticated on one particular node he will have = to reauthenticate again if he use another + node of the cluster (during a failover for instance). This is = valid only for the FORM + based authentication which is the default form of authenticati= on that JBoss Portal uses. Fortunately JBoss + provides transparent reauthentication of the user called JBoss= clustered SSO. Its configuration can be found + in $JBOSS_HOME/server/all/deploy/jboss-web.deployer/s= erver.xml and you will need to + uncomment the following valve: + ]]> + + + If you use JBoss 4.0.x, the files and valve are respectivel= y: + $JBOSS_HOME/server/all/deploy/jbossweb-tomcat55.sa= r/server.xml + ]]> + + + More information can be found here. = @@ -202,10 +209,12 @@ Setup 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 b= alancer in front of Tomcat. However a lot of documentation - exist on the subject. A detailed step by step setup of Apache and mo= d_jk is available from the JBoss Wiki. + exist on the subject. A detailed step by step setup of Apache and mo= d_jk is available from the JBoss Wiki. As we need two application servers running at the same time, w= e must avoid any conflict. For instance we will need Tomcat to bind its socket on two different ports otherwise a ne= twork conflict will occur. We will leverage - the service binding manager this chapter of + the service binding manager this chapter of the JBoss AS documentation. The first step is to copy the all configu= ration of JBoss into two separate configurations that we name ports-01 and ports-02 : @@ -244,9 +253,9 @@ into $JBOSS_HOME/server/ports-01/deploy and $JBOSS_HOME/server/ports-02/deploy. Copy JBoss Portal HA to the deploy directory of the two config= urations. - = + - + JBoss Cache Configuration Note : To i= mprove CMS performance JBoss Cache is leveraged to cache the content cluste= r wide. We recommend that you use the following version of JBoss C= ache for best performance: Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/s= so.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/sso.xml= 2007-10-13 17:12:01 UTC (rev 8631) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/sso.xml= 2007-10-13 17:31:51 UTC (rev 8632) @@ -19,7 +19,8 @@ the portal you gain access to many systems through portlets using a= single identity. Still in many cases you need to integrate the portal infrastructure with other SSO enabled = systems. There are many different Identity Management solutions on the market. In most cases each SSO framework provides = its own way to plug into Java EE application. For custom configurations - you need to have a good understanding of JBoss Portal Identity management and authentication + you need to have a good understanding of JBoss Portal Identity management and authentication mechanisms. @@ -32,12 +33,14 @@ Enabling Tomcat SSO Valve - To enable SSO valve in Tomcat you should edit $JBOSS= _HOME/server/default/deploy/jbossweb-tomcat55.sar/server.xml fil= e and uncomment - following line: - - ]]> - + To enable SSO valve in Tomcat you should uncomment the followi= ng line + ]]> + in the $JBOSS_HOME/server/default/deploy/jboss-web.de= ployer/server.xml file. + + On JBoss 4.0.x the configuration file is + $JBOSS_HOME/server/default/deploy/jbossweb-tomcat5= 5.sar/server.xml + + More information can be found here. @@ -45,7 +48,8 @@ Lets look a little bit closer and configure SSO between portal= and other web application. As an example we'll use jmx-console web-app that comes = with every JBoss Application Server installation. - You can find more information on how to secure jmx-c= onsole in JBoss AS wiki. + You can find more information on how to secure jmx-c= onsole in JBoss AS wiki. @@ -127,12 +131,15 @@ - Edit $JBOSS_HOME/server/default/deploy/jbosswe= b-tomcat55.sar/server.xml file and uncomment - following line: - - ]]> - + Uncomment the following line + ]]> + in the $JBOSS_HOME/server/default/deploy/jboss-= web.deployer/server.xml file. + + On JBoss 4.0.x the configuration file is + $JBOSS_HOME/server/default/deploy/jbossweb-t= omcat55.sar/server.xml + + More information can be found here. Run JBoss Application Server. Modified: docs/trunk/referenceGuide/en/modules/clustering.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- docs/trunk/referenceGuide/en/modules/clustering.xml 2007-10-13 17:12:01= UTC (rev 8631) +++ docs/trunk/referenceGuide/en/modules/clustering.xml 2007-10-13 17:31:51= UTC (rev 8632) @@ -163,22 +163,29 @@ ]]> - More information can be found here. + More information can be found here. = Identity clustering - JBoss Portal leverages the servlet container authentication= for its own authentication mechanism. When the user - is authenticated on one particular node he will have to reauthent= icate again if he use another node of the cluster (during - a failover for instance). This is valid only for the FO= RM based authentication which is the default - form of authentication that JBoss Portal uses. Fortunately JBoss = provides transparent reauthentication of the user called - JBoss clustered SSO. Its configuration is in the file $= JBOSS_HOME/server/all/deploy/jbossweb-tomcat55.sar/server.xml - and the clustered sso valve shall be uncommented - -]]> - More information can be found here. + JBoss Portal leverages the servlet container authentication= for its own authentication mechanism. When + the user is authenticated on one particular node he will have = to reauthenticate again if he use another + node of the cluster (during a failover for instance). This is = valid only for the FORM + based authentication which is the default form of authenticati= on that JBoss Portal uses. Fortunately JBoss + provides transparent reauthentication of the user called JBoss= clustered SSO. Its configuration can be found + in $JBOSS_HOME/server/all/deploy/jboss-web.deployer/s= erver.xml and you will need to + uncomment the following valve: + ]]> + + + If you use JBoss 4.0.x, the files and valve are respectivel= y: + $JBOSS_HOME/server/all/deploy/jbossweb-tomcat55.sa= r/server.xml + ]]> + + + More information can be found here. = @@ -202,10 +209,12 @@ Setup 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 b= alancer in front of Tomcat. However a lot of documentation - exist on the subject. A detailed step by step setup of Apache and mo= d_jk is available from the JBoss Wiki. + exist on the subject. A detailed step by step setup of Apache and mo= d_jk is available from the JBoss Wiki. As we need two application servers running at the same time, w= e must avoid any conflict. For instance we will need Tomcat to bind its socket on two different ports otherwise a ne= twork conflict will occur. We will leverage - the service binding manager this chapter of + the service binding manager this chapter of the JBoss AS documentation. The first step is to copy the all configu= ration of JBoss into two separate configurations that we name ports-01 and ports-02 : @@ -244,17 +253,17 @@ into $JBOSS_HOME/server/ports-01/deploy and $JBOSS_HOME/server/ports-02/deploy. Copy JBoss Portal HA to the deploy directory of the two config= urations. - = + - + JBoss Cache Configuration Note : To i= mprove CMS performance JBoss Cache is leveraged to cache the content cluste= r wide. We recommend that you use the following version of JBoss C= ache for best performance: JBoss Cache 1.4.0.SP1 and above - JGroups 2.2.7 or 2.2.8= = - = + JGroups 2.2.7 or 2.2.8= + When building from source the following command: {core}/= build.xml deploy-ha automatically upgrades your JBoss - Cache version. = + Cache version. Alternative: If upgrading your JBoss= Cache version is not an option, the following configuration @@ -295,10 +304,10 @@ false false false ]]> - = + - = - = + + Finally we can start both servers, open two shells and execute= : cd $JBOSS_HOME/bin @@ -310,9 +319,9 @@ ]]> - = - = = + + Portlet Session Replication Web containers offer the capability to replicate sessions of w= eb applications. In the context of a portal using portlets the use case is = different. The portal itself is a web application Modified: docs/trunk/referenceGuide/en/modules/sso.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- docs/trunk/referenceGuide/en/modules/sso.xml 2007-10-13 17:12:01 UTC (r= ev 8631) +++ docs/trunk/referenceGuide/en/modules/sso.xml 2007-10-13 17:31:51 UTC (r= ev 8632) @@ -19,7 +19,8 @@ the portal you gain access to many systems through portlets using a= single identity. Still in many cases you need to integrate the portal infrastructure with other SSO enabled = systems. There are many different Identity Management solutions on the market. In most cases each SSO framework provides = its own way to plug into Java EE application. For custom configurations - you need to have a good understanding of JBoss Portal Identity management and authentication + you need to have a good understanding of JBoss Portal Identity management and authentication mechanisms. @@ -32,12 +33,14 @@ Enabling Tomcat SSO Valve - To enable SSO valve in Tomcat you should edit $JBOSS= _HOME/server/default/deploy/jbossweb-tomcat55.sar/server.xml fil= e and uncomment - following line: - - ]]> - + To enable SSO valve in Tomcat you should uncomment the followi= ng line + ]]> + in the $JBOSS_HOME/server/default/deploy/jboss-web.de= ployer/server.xml file. + + On JBoss 4.0.x the configuration file is + $JBOSS_HOME/server/default/deploy/jbossweb-tomcat5= 5.sar/server.xml + + More information can be found here. @@ -45,7 +48,8 @@ Lets look a little bit closer and configure SSO between portal= and other web application. As an example we'll use jmx-console web-app that comes = with every JBoss Application Server installation. - You can find more information on how to secure jmx-c= onsole in JBoss AS wiki. + You can find more information on how to secure jmx-c= onsole in JBoss AS wiki. @@ -127,12 +131,15 @@ - Edit $JBOSS_HOME/server/default/deploy/jbosswe= b-tomcat55.sar/server.xml file and uncomment - following line: - - ]]> - + Uncomment the following line + ]]> + in the $JBOSS_HOME/server/default/deploy/jboss-= web.deployer/server.xml file. + + On JBoss 4.0.x the configuration file is + $JBOSS_HOME/server/default/deploy/jbossweb-t= omcat55.sar/server.xml + + More information can be found here. Run JBoss Application Server. @@ -369,7 +376,7 @@ ]]> This will expose special service in JBoss Portal that can b= e leveraged by JOSSO Credential and Identity Stores if the server is deploy= ed on the same - application server instance. = + application server instance. Edit $JBOSS_HOME/server/default/deploy/josso.e= ar/josso.war/WEB-INF/classes/josso-gateway-config.xml and config= ure following elements: --===============3459883515820239334==--