From portal-commits at lists.jboss.org Tue Jul 5 21:54:21 2011 Content-Type: multipart/mixed; boundary="===============6367112664271417273==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r14001 - docs/enterprise/tags. Date: Tue, 05 Jul 2011 21:54:20 -0400 Message-ID: <201107060154.p661sKO5020341@svn01.web.mwc.hst.phx2.redhat.com> --===============6367112664271417273== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: smumford Date: 2011-07-05 21:54:19 -0400 (Tue, 05 Jul 2011) New Revision: 14001 Added: docs/enterprise/tags/Enterprise_Portal_Platform_4_3_GA_CP06/ Log: Tagging CP06 Release Notes --===============6367112664271417273==-- From portal-commits at lists.jboss.org Tue Jul 12 01:57:12 2011 Content-Type: multipart/mixed; boundary="===============4904471342614563726==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r14002 - docs/enterprise/trunk/PortletBridge/en-US. Date: Tue, 12 Jul 2011 01:57:12 -0400 Message-ID: <201107120557.p6C5vC2l017490@svn01.web.mwc.hst.phx2.redhat.com> --===============4904471342614563726== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: smumford Date: 2011-07-12 01:57:11 -0400 (Tue, 12 Jul 2011) New Revision: 14002 Modified: docs/enterprise/trunk/PortletBridge/en-US/configuration.xml Log: JBEPP-943: Corrected javax.portlet.faces.RENDER_POLICY Modified: docs/enterprise/trunk/PortletBridge/en-US/configuration.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/enterprise/trunk/PortletBridge/en-US/configuration.xml 2011-07-06 = 01:54:19 UTC (rev 14001) +++ docs/enterprise/trunk/PortletBridge/en-US/configuration.xml 2011-07-12 = 05:57:11 UTC (rev 14002) @@ -4,21 +4,21 @@ %BOOK_ENTITIES; ]> - Bridge Configuration - - The 329 specification is aimed at making the developer's life as easy as= possible with JSF+Portlet development. You will see below that there are m= inimal settings to getting any JSF web application up and running in the Po= rtal environment. - - - If you are new to these concepts, we highly recommend you refer to . - -
- Core Setup and Configuration -
- portlet.xml - - The basic JSR-329 portlet configuration. - - = + Bridge Configuration + + The 329 specification is aimed at making the developer's life as e= asy as possible with JSF+Portlet development. You will see below that there= are minimal settings to getting any JSF web application up and running in = the Portal environment. + + + If you are new to these concepts, we highly recommend you refer to= . + +
+ Core Setup and Configuration +
+ portlet.xml + + The basic JSR-329 portlet configuration. + + = yourPortletName @@ -41,27 +41,27 @@ /jsf/help.xhtml ]]> - - When preserveActionParams is set to = TRUE, the bridge must maintain any request parameters assigned = during the portlet's action request. - - - The request parameters are maintained in the"bridge request = scope". When this attribute is not present or is FALS= E the action's request parameters are only maintained for the d= uration of the portlet request scope. - - = + + When preserveActionParams is set to= TRUE, the bridge must maintain any request paramete= rs assigned during the portlet's action request. + + + The request parameters are maintained in the"bri= dge request scope". When this attribute is not present or is FALSE the action's request parameters are only maintain= ed for the duration of the portlet request scope. + + = javax.portlet.faces.preserveActionParams true ]]> -
- = -
- faces-config.xml - - The PortletViewHandler ensures that each JSF po= rtlet instance is properly namespaced. - - = +
+ = +
+ faces-config.xml + + The PortletViewHandler ensures that= each JSF portlet instance is properly namespaced. + + = @@ -72,15 +72,15 @@ ... ]]> -
- = -
- Facelets Configuration - - The following web.xml setting is only for Facelets based applications - -
- web.xml +
+ = +
+ Facelets Configuration + + The following web.xml setting is only= for Facelets based applications + +
+ web.xml org.jboss.portletbridge.application.FaceletPo= rtletViewHandler ]]> - = + = javax.portlet.faces.RENDER_POLICY @@ -105,45 +105,45 @@ ]]> = - - RenderPolicy Options - - ALWAYS_DELEGATE - - - Indicates the bridge should not render the view itself but rather al= ways delegate the rendering. - - - - - NEVER_DELEGATE - - - Indicates the bridge should always render the view itself and never = delegate. - - - - - DEFAULT - - - Directs the bridge to first delegate the render and if and only if a= n Exception is thrown then render the view based on its own logic. If the c= onfiguration parameter is not present or has an invalid value the bridge re= nders using default behavior. I.e. as if DEFAULT is set. - - - - -
+ + RenderPolicy Options + + ALWAYS_DELEGATE + + + Indicates the bridge should not render the view it= self but rather always delegate the rendering. + + + + + NEVER_DELEGATE + + + Indicates the bridge should always render the view= itself and never delegate. + + + + + DEFAULT + + + Directs the bridge to first delegate the render an= d if and only if an Exception is thrown then render the view based on its o= wn logic. If the configuration parameter is not present or has an invalid v= alue the bridge renders using default behavior. I.e. as if DEFAULT is set. + + + + +
= -
- = -
- JSP Only Configuration - - The following web.xml setting is only for JSP bas= ed applications. Download the demonstration application h= ere. - -
- web.xml - = +
+ = +
+ JSP Only Configuration + + The following web.xml setting is only= for JSP based applications. Download the demonstration application here. + +
+ web.xml + = = - javax.portlet.faces.renderPolicy + javax.portlet.faces.RENDER_POLICY NEVER_DELEGATE @@ -160,40 +160,40 @@ ]]> = -
+
= -
- = -
- JSR-329 - - The Jboss Portlet Bridge can be used with a any compatible implementat= ion (for example, MyFaces implementation). Simply put th= e following into web.xml: - - = +
+ = +
+ JSR-329 + + The Jboss Portlet Bridge can be used with a any compatible= implementation (for example, MyFaces implementation). S= imply put the following into web.xml: + + = javax.portlet.faces.BridgeImplClass org.apache.myfaces.portlet.faces.bridge.BridgeImpl ]]> -
+
= -
- = - -
- RichFaces Setup and Configuration Options -
- web.xml - - The following configuration is designated for portlets using the RichFaces library. These settings will vary based on = your individual needs. - - - See this section of the RichFaces= documentation for more details. - - - Sometimes it is better to use the "ALL" load st= rategy in portlets so you do not need to worry about loading the "framework= .pack.js" and "ui.pack.js" files manually in your portlet header. - +
+ = + +
+ RichFaces Setup and Configuration Options +
+ web.xml + + The following configuration is designated for portlets usi= ng the RichFaces library. These settings will va= ry based on your individual needs. + + + See this section of the RichFaces documentation for more details. + + + Sometimes it is better to use the "ALL" load strategy in portlets so you do not need to worry about loading th= e "framework.pack.js" and "ui.pack.js" files manually in your portlet heade= r. + = @@ -205,23 +205,23 @@ ALL ]]> - - - If you use the "NONE" strategy, you must inclu= de the following scripts in your portlet or portal page header. If you are = using JBoss Portal, you can add this to the jboss-portlet.xml file. - - - - The org.ajax4jsf.RESOURCE_URI_PREFIX configuration = cross-references the path to your scripts below. These settings are require= d for RichFaces using the "NONE" strategy. - - = + + + If you use the "NONE" strategy,= you must include the following scripts in your portlet or portal page head= er. If you are using JBoss Portal, you can add t= his to the jboss-portlet.xml file. + + + + The org.ajax4jsf.RESOURCE_URI_PREFIX co= nfiguration cross-references the path to your scripts below. These settings= are required for RichFaces using the "NONE" strategy. + + = ]]> - - Seam automatically configures your Ajax4JSF= Filter, so if you are running a Seam portlet, y= ou do not need the following Filter configuration (however, you do need the= RESOURCE_URI_PREFIX no matter what). - + + Seam automatically configures y= our Ajax4JSF Filter, so if you are running a Seam portlet, you do not need the following Filter configuration (however, you= do need the RESOURCE_URI_PREFIX no matter what). + = @@ -246,9 +246,9 @@ ]]> = -
- = - = -
- = -
- Seam Setup and Configuration Options -
- Configuration - - The ExceptionHandler is used to clean = Seam contexts and transactions after errors. - - = +
+ = +
+ Seam Setup and Configuration Options +
+ Configuration + + The ExceptionHandler is used to clean <= application>Seam contexts and transactions after errors. + + = org.jboss.portletbridge.ExceptionHandler @@ -284,29 +284,29 @@ ]]> - - If you are using this bridge version from 2.0.0.BETA through 2.0.0.CR1, you must define the following web.xml parameter to use the JBoss Portlet Bridge provided = Seam Phase Listener. This is done by the bridge automatically (if needed) i= n 2.0.0.FINAL. - - = + + If you are using this bridge version from 2.0.0.B= ETA through 2.0.0.CR1, you must define the fol= lowing web.xml parameter to use the JBoss Portlet Brid= ge provided Seam Phase Listener. This is done by the bridge automatically (= if needed) in 2.0.0.FINAL. + + = javax.faces.LIFECYCLE_ID SEAM_PORTLET ]]> -
+
= -
- = -
- Portlet 2.0 Coordination - - Schema and XSD Definitions - - It is important to ensure, before using either of the following mecha= nisms, that the proper 2.0 schema and xsd are defined at the top of your portlet.xml. - - - = +
+ = +
+ Portlet 2.0 Coordination + + Schema and XSD Definitions + + It is important to ensure, before using either of the = following mechanisms, that the proper 2.0 schema and xsd are defined at the= top of your portlet.xml. + + + = ]]> = -
- Sending and Receiving Events -
- Configuration - - Just like with any portlet 2.0 event consumer and receiver, you must = define them in the portlet.xml. - +
+ Sending and Receiving Events +
+ Configuration + + Just like with any portlet 2.0 event consumer and rece= iver, you must define them in the portlet.xml. + - - You must also define the following init params i= n your portlet.xml. - - = - - javax.portlet.faces.autoDispatchEvents - true - - - javax.portlet.faces.bridgeEventHandler - org.foo.eventhandler - + + To see a working example, checkout the Seam Booking De= mo portlet. + --> + + You must also define the following init para= ms in your portlet.xml. + + = + + javax.portlet.faces.autoDispatchEvents + true + + + javax.portlet.faces.bridgeEventHandler + org.foo.eventhandler + ]]> - - While future versions on the 2.0 bridge will automate the dispatching= and consuming of events, at the moments you must dispatch the event in the= JSF or Seam backing bean. - - = + + While future versions on the 2.0 bridge will automate = the dispatching and consuming of events, at the moments you must dispatch t= he event in the JSF or Seam backing bean. + + = - - You must also create the event handler class by implementing the BridgeEventHandler interface to process the event payload. - - = + + You must also create the event handler class by implem= enting the BridgeEventHandler interface to process the e= vent payload. + + = -
+
= -
- = -
- Public Render Parameters -
- Configuration - - Public Render Parameters (or PRPs) are one of the most powerful and s= imple Portlet 2.0 features. Several portlets (JSF or otherwise) can share t= he same render parameters. This feature can be use to present a cohesive UI= to the user across all portlets on the page. An example would be using an = employee ID to display relative data. - - - The bridge maps a render parameter to a backing bean using settings i= n your faces-config.xml and portlet.xml. - - - A clear and working example can be found in the Seam Booking Demo por= tlet. - - - You must define the following init params in you= r portlet.xml. - - = +
+ = +
+ Public Render Parameters +
+ Configuration + + Public Render Parameters (or PRPs) are one of the most= powerful and simple Portlet 2.0 features. Several portlets (JSF or otherwi= se) can share the same render parameters. This feature can be use to presen= t a cohesive UI to the user across all portlets on the page. An example wou= ld be using an employee ID to display relative data. + + + The bridge maps a render parameter to a backing bean u= sing settings in your faces-config.xml and p= ortlet.xml. + + + A clear and working example can be found in the Seam B= ooking Demo portlet. + + + You must define the following init params in your portlet.xml. + + = javax.portlet.faces.bridgePublicRenderParameterHandler @@ -391,10 +391,10 @@ ... myCoolPRP ]]> - - Create a managed bean and public-parameter-mappings in your faces-config.xml. This should be a basic bea= n that you can bind the passed parameter to a string with getter<= /emphasis> and setter. - - = + + Create a managed bean and public-parameter-ma= ppings in your faces-config.xml. This should= be a basic bean that you can bind the passed parameter to a string with getter and setter. + + = bookingPRP @@ -413,20 +413,20 @@ ]]> - - You must set the parameter in the JSF or Seam backing bean, if you ar= e providing one from your portlet. - - = + + You must set the parameter in the JSF or Seam backing = bean, if you are providing one from your portlet. + + = - - Then you must also implement the BridgePublicRenderParameter= Handler interface to process any updates from the received parame= ter. - - = + + Then you must also implement the BridgePublic= RenderParameterHandler interface to process any updates from the = received parameter. + + = -
+
= -
- = -
- Serving Your JSF Resources in a Portlet -
- Configuration - - We have setup a few examples to show you how to use EL and a simple bean that will allow you to use the portlet resource serv= ing mechanism within a JSF portlet. - - - In ResourceBean.java, you can see a very sim= ple implementations of a Map object that uses the bridge to get and encode = a resource url served from the portlets web application. - - - So, when you have the normal "/images", "/styles" and other resource folders in your web application, = you can use the following EL expression to serve them in= your JSF application. - - = +
+ = +
+ Serving Your JSF Resources in a Portlet +
+ Configuration + + We have setup a few examples to show you how to use EL and a simple bean that will allow you to use the portle= t resource serving mechanism within a JSF portlet. + + + In ResourceBean.java, you can= see a very simple implementations of a Map object that uses the bridge to = get and encode a resource url served from the portlets web application. + + + So, when you have the normal "/images", "/styles" and other resource folders in your we= b application, you can use the following EL expression t= o serve them in your JSF application. + + = #{resource['/img/the-path-to-my-image.png']} - - Just copy the ResourceBean.java code above, and ad= d an entry to your faces-config.xml for the bean: - - = + + Just copy the ResourceBean.java cod= e above, and add an entry to your faces-config.xml for= the bean: + + = resource @@ -472,11 +472,11 @@ application ]]> -
+
= -
+
= -
+
= = --===============4904471342614563726==-- From portal-commits at lists.jboss.org Thu Jul 14 01:09:13 2011 Content-Type: multipart/mixed; boundary="===============3664702045610956843==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r14003 - in docs/enterprise/trunk/Release_Notes: en-US and 1 other directory. Date: Thu, 14 Jul 2011 01:09:12 -0400 Message-ID: <201107140509.p6E59CJZ007529@svn01.web.mwc.hst.phx2.redhat.com> --===============3664702045610956843== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: smumford Date: 2011-07-14 01:09:12 -0400 (Thu, 14 Jul 2011) New Revision: 14003 Added: docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml docs/enterprise/trunk/Release_Notes/en-US/need_info.xml docs/enterprise/trunk/Release_Notes/en-US/not_documented.xml docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml Removed: docs/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes.ent docs/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes.xml Modified: docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml docs/enterprise/trunk/Release_Notes/publican.cfg Log: Updated for CP07 release and streamlined JIRA export process Modified: docs/enterprise/trunk/Release_Notes/en-US/Book_Info.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/enterprise/trunk/Release_Notes/en-US/Book_Info.xml 2011-07-12 05:5= 7:11 UTC (rev 14002) +++ docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml 2011-07-14 05:0= 9:12 UTC (rev 14003) @@ -4,30 +4,30 @@ %BOOK_ENTITIES; ]> - CP06 Release Notes - For use with JBoss Enterprise Portal Platform 4.3 CP06 - 1 - 1.2 - JBoss Enterprise Portal Platform - 4.3 - - - These release notes contain important information related to &PRODUCT; = &VERSION_MICRO; that may not be currently available in the Product Manuals.= You should read these Release Notes in their entirety before installing &P= RODUCT; &VERSION_MICRO;. - - - N/A - - - - - - - - - &YEAR; - &HOLDER; - - - + CP07 Release Notes + For use with JBoss Enterprise Portal Platform 4.3 CP07 + 1 + 1.2 + JBoss Enterprise Portal Platform + 4.3 + + + These release notes contain important information related to J= Boss Enterprise Portal Platform &VZ; that may not be currently available in= the Product Manuals. You should read these Release Notes in their entirety= before installing JBoss Enterprise Portal Platform &VZ;. + + + N/A + + + + + + + + + &YEAR; + &HOLDER; + + + = Deleted: docs/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes.ent =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/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes.ent 2011-0= 7-12 05:57:11 UTC (rev 14002) +++ docs/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes.ent 2011-0= 7-14 05:09:12 UTC (rev 14003) @@ -1,20 +0,0 @@ - - - - - - - - - - - - - - - - - - - - Deleted: docs/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes.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/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes.xml 2011-0= 7-12 05:57:11 UTC (rev 14002) +++ docs/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes.xml 2011-0= 7-14 05:09:12 UTC (rev 14003) @@ -1,170 +0,0 @@ - - -%BOOK_ENTITIES; -]> -
- -
- Introduction - - These release notes contain important information related to &PRODUCT; = &VERSION_MICRO;. New features, known problems, resources, and other current= issues are addressed here. - -
- Overview - - JBoss Enterprise Portal Platform facilitates the delivery of web-based= composite applications and high-performance web presences. Through its agi= le, reusable framework, customers can minimize the cost and complexity of t= heir web infrastructures. Its use of open standards mitigates the risk of v= endor lock-in, ensuring compatibility. As an integral component of JBoss En= terprise Middleware, the large and vibrant JBoss.org developer community fo= sters its continued innovation and enterprise quality. And it's deployed on= JBoss Enterprise Application Platform=E2=80=94the industry=E2=80=99s #1 J2= EE-certified application platform ensuring performance, scalability, and a = reliable and straightforward path to implementation. - -
= -
- -
- Component Versions - - This section details the versions of the components which create &PRODU= CT; &VERSION_MICRO; (not including the components delivered by the Enterpri= se Application Platform 4.3). - - - - - Identity Module 1.1.3 - - - - - Common Module 1.2.5 - - - - - Portlet Module 2.0.9 - - - - - Web Module 1.2.4 - - - - - CMS Module 1.2.8 - - - - - JBoss Portlet Bridge 2.0.1.FINAL.EPP43CP06 - - - -
- = -
- Issues resolved in the 4.3 CP06 release - - - - - - - CAS integration experienced problems with incorrect character = encoding. These have been resolved by upgrading the PicketLink component to= version 1.1.3. - - - - - - - - - - Portlet Bridge 2.0 introduced a new Seam component (P= ortalIdentity) with the same name and same precedence as the Seam= identity component, RuleBasedIdentity, defined in 2.0.2= .FP. This conflict caused Seam to fail deployment. A patch has been applied= to this release to correct this issue. - - - - - - - - - - Exceptions thrown by the handleFaceletNotFound method (when a facelet file was not found) were being obscured by FaceletViewHandler as the response object was not a subtype o= f HttpServletResponse (it is a instance of Port= letResponse). = - - - FaceletPortletViewHandler.java has been u= pdated to handle instances of both HttpServletResponse a= nd PortletResponse response objects. - - - - - - - - - - Error resources needed to be placed into /portal-core= with the default Error policies. This functionality has been mad= e configurable by modifying jboss-service.xml. - - - - - - - - - - In Internet Explorer 7, the Richfaces scrollableDataT= able's header disappeared after sending ajax request and re-rende= ring the scrollableDataTable. The cause was identified t= o as an problematic prefix character in the client view id ("_"). = - - - This issue only presented in the IE7 browser and a patch has b= een incorporated to correct it. = - - - - - -
- -
- Product Support and License Website Links - - Support Processes - - http://www.redha= t.com/support/process/ - - - - Production Support Scope of Coverage - - htt= p://www.redhat.com/support/policy/soc/production - - - - Production Support Service Level Agreement - - ht= tp://www.redhat.com/support/policy/sla/production/ - - - - Developer Support Scope of Coverage - - htt= p://www.redhat.com/support/policy/soc/developer/ - - - - Developer Support Service Level Agreement - - htt= p://www.redhat.com/support/policy/sla/developer/ - - - - Product Update and Support Policy by Product - - htt= p://www.redhat.com/security/updates/jboss_notes/ - - - - JBoss End User License Agreement - - http://w= ww.redhat.com/licenses/jboss_eula.html - - -
- - -
- Copied: docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent (f= rom rev 14001, docs/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes= .ent) =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/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent = (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent 2011-0= 7-14 05:09:12 UTC (rev 14003) @@ -0,0 +1,15 @@ + + + + + + + + + + + + + + + Copied: docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml (f= rom rev 14001, docs/enterprise/trunk/Release_Notes/en-US/CP06_Release_Notes= .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/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml = (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml 2011-0= 7-14 05:09:12 UTC (rev 14003) @@ -0,0 +1,146 @@ + + +%BOOK_ENTITIES; +]> +
+ +
+ Introduction + + These release notes contain important information related to J= Boss Enterprise Portal Platform &VZ;. New features, known problems, resourc= es, and other current issues are addressed here. + +
+ Overview + + JBoss Enterprise Portal Platform facilitates the delivery = of web-based composite applications and high-performance web presences. Thr= ough its agile, reusable framework, customers can minimize the cost and com= plexity of their web infrastructures. Its use of open standards mitigates t= he risk of vendor lock-in, ensuring compatibility. As an integral component= of JBoss Enterprise Middleware, the large and vibrant JBoss.org developer = community fosters its continued innovation and enterprise quality. And it's= deployed on JBoss Enterprise Application Platform=E2=80=94the industry=E2= =80=99s #1 J2EE-certified application platform ensuring performance, scalab= ility, and a reliable and straightforward path to implementation. + +
+
+ +
+ Component Versions + + This section details the versions of the components which crea= te JBoss Enterprise Portal Platform &VZ; (not including the components deli= vered by the Enterprise Application Platform 4.3). + + + + + Identity Module 1.1.3 + + + + + Common Module 1.2.5 + + + + + Portlet Module 2.0.9 + + + + + Web Module 1.2.4 + + + + + CMS Module 1.2.8 + + + + + JBoss Portlet Bridge 2.0.1.FINAL.EPP43CP06 + + + +
+ +
+ Resolved Issues + +
+ +
+ Known Issues + +
+ = +
+ Security Issues + + + + + + + Not Public Yet - RHT only + + = + + + + + +
+ = +
+ <remark>NEEDINFO Issues</remark> + +
+ = +
+ <remark>Not Yet Documented Issues</remark> + +
+ +
+ Product Support and License Website Links + + Support Processes + + http= ://www.redhat.com/support/process/ + + + + Production Support Scope of Coverage + + http://www.redhat.com/support/policy/soc/production + + + + Production Support Service Level Agreement + + http://www.redhat.com/support/policy/sla/production/ + + + + Developer Support Scope of Coverage + + http://www.redhat.com/support/policy/soc/developer/ + + + + Developer Support Service Level Agreement + + http://www.redhat.com/support/policy/sla/developer/ + + + + Product Update and Support Policy by Product + + http://www.redhat.com/security/updates/jboss_notes/ + + + + JBoss End User License Agreement + + http://www.redhat.com/licenses/jboss_eula.html + + +
+ + +
+ Added: docs/enterprise/trunk/Release_Notes/en-US/known_issues.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/enterprise/trunk/Release_Notes/en-US/known_issues.xml = (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml 2011-07-14 0= 5:09:12 UTC (rev 14003) @@ -0,0 +1,4 @@ + + +There are no known issues in this release. + Added: docs/enterprise/trunk/Release_Notes/en-US/need_info.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/enterprise/trunk/Release_Notes/en-US/need_info.xml = (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/need_info.xml 2011-07-14 05:0= 9:12 UTC (rev 14003) @@ -0,0 +1,4 @@ + + +There are no issues that require more information at this time. + Added: docs/enterprise/trunk/Release_Notes/en-US/not_documented.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/enterprise/trunk/Release_Notes/en-US/not_documented.xml = (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/not_documented.xml 2011-07-14= 05:09:12 UTC (rev 14003) @@ -0,0 +1,59 @@ + + + + + + = + + + + + = + + = + + = + + + + + + + + = + + = + + = + + + + + + + + = + + = + + = + + + + + + + + = + + Not Public Yet - RHT only + + = + + + = + + + + Added: docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.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/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml = (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml 2011-07-1= 4 05:09:12 UTC (rev 14003) @@ -0,0 +1,4 @@ + + +There are no resolved issues in this release. + Modified: docs/enterprise/trunk/Release_Notes/publican.cfg =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/enterprise/trunk/Release_Notes/publican.cfg 2011-07-12 05:57:11 UT= C (rev 14002) +++ docs/enterprise/trunk/Release_Notes/publican.cfg 2011-07-14 05:09:12 UT= C (rev 14003) @@ -4,4 +4,7 @@ debug: 1 xml_lang: en-US brand: JBoss - +show_remarks: 1 +cvs_branch: DOCS-RHEL-6 +cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist +cvs_pkg: JBoss_Enterprise_Portal_Platform-CP07_Release_Notes-4.3-web-__LAN= G__ \ No newline at end of file --===============3664702045610956843==-- From portal-commits at lists.jboss.org Mon Jul 25 20:37:05 2011 Content-Type: multipart/mixed; boundary="===============5742501566288364965==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r14005 - in docs/enterprise/trunk/Installation_Guide: en-US and 1 other directory. Date: Mon, 25 Jul 2011 20:37:04 -0400 Message-ID: <201107260037.p6Q0b445013899@svn01.web.mwc.hst.phx2.redhat.com> --===============5742501566288364965== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: smumford Date: 2011-07-25 20:37:04 -0400 (Mon, 25 Jul 2011) New Revision: 14005 Modified: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml docs/enterprise/trunk/Installation_Guide/publican.cfg Log: Update old or broken URLs in hyperlinks. Modified: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.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/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2011-07-14= 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2011-07-26= 00:37:04 UTC (rev 14005) @@ -3,29 +3,28 @@ ]> = - Installation Guide - An Installation Guide for &PRODUCT; - 1 - 1.3 - JBoss Enterprise Portal Platform - 4.3 - Jan, 2009 - N/A - This Installation Guide documents relevant information re= garding + Installation Guide + An Installation Guide for &PRODUCT; + JBoss Enterprise Portal Platform + 4.3 + 1 + 1.4 + + This Installation Guide documents relevant information= regarding the installation of JBoss Enterprise Portal Platform - - - - - - - - - - &YEAR; - &HOLDER; - - - + + + + + + + + + + &YEAR; + &HOLDER; + + + = Modified: docs/enterprise/trunk/Installation_Guide/en-US/Configuration.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/enterprise/trunk/Installation_Guide/en-US/Configuration.xml 2011-0= 7-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml 2011-0= 7-26 00:37:04 UTC (rev 14005) @@ -2,46 +2,46 @@ - Database Configuration + Database Configuration = -
- Installing an RDBMS JDBC connector - - A relational database management system (RDBMS) Java Database Connectiv= ity (JDBC) connector is required for &JBEPP; to communicate with a database. - &JBEPP; comes bundled with Hypersonic SQL (HSQL) database so that users= can get started up and running quickly without having to setup = - database initially. However, HSQL should not be used in production en= vironment. Removing HSQL is simply a matter of removing = - JBOSS_DIST/jboss-as/server/$CONFIG/deploy/portal-hsql-ds.xm= l. Test suites have been run against = - the Oracle 9, Oracle 10, Microsoft SQL Server, = - MySQL 4, MySQL 5, and PostgreSQL 8 databases - these databases are re= commended for production use. Please refer to your database documentation f= or the correct = - RDBMS JDBC connector. The MySQL RDBMS JDBC connector can be downloade= d from , = and the - PostgreSQL RDBMS JDBC connector can be downloaded from . - - - Refer to the help files in each download for installation instructions.= In most cases, the RDBMS JDBC connector comes as a .jar file. Copy this file into the $JBOSS_HOME/server/<= replaceable>configuration/lib/ directory. - -
- = -
- Datasource Descriptors - - A Datasource descriptor is required for JBoss Portal to communicate wit= h a database. Sample Datasource descriptor files are provided for the Hyper= sonic SQL, Microsoft SQL Server= , MySQL, Oracle, and PostgreSQL= databases. These can be found in the /jboss-as/docs/portal/setup= / subdirectory where the EPP x.x.x<= /replaceable> binary distribution file was extracted to. F= or example, if EPP was extracted into the /jboss/ dire= ctory, the sample Datasource descriptors would be in the /jboss/j= boss-epp-x.x.x/jboss-as/docs/portal/setup directory. - - - The sample Datasource descriptors will work with default installations = of external databases; however, you may need to configure the correct usern= ame and password. As well, the sample MySQL and PostgreSQL Datasource descr= iptors assume the name of the database to be jbossportal. - - - When copying a Datasource descriptor for MySQL, Microsoft SQL Server, PostgreSQL, or Oracle databases, change the &l= t;user-name>portal</user-name> and <password>portalpassword</password> sections to reflect the corre= ct username and password for the user who has access to the jbossportal dat= abase. - - - Different Datasource Descriptors - - Only have one Datasource descriptor in the $JBOSS_HOME/serve= r/configuration/deploy/ directory. Fo= r example, if you want to use a MySQL database, remove the portal= -hsqldb-ds.xml file, and other descriptors, if they exists. - - - - The following is an example Datasource descriptor file for MySQL 5: - - +
+ Installing an RDBMS JDBC connector + + A relational database management system (RDBMS) Java Database = Connectivity (JDBC) connector is required for JBoss Enterprise Portal Platf= orm to communicate with a database. + JBoss Enterprise Portal Platform comes bundled with Hypersonic= SQL (HSQL) database so that users can get started up and running quickly w= ithout having to setup = + database initially. However, HSQL should not be used in product= ion environment. Removing HSQL is simply a matter of removing = + JBOSS_DIST/jboss-as/server/$CONFIG/deploy/portal-hsql= -ds.xml. Test suites have been run against = + the Oracle 9, Oracle 10, Microsoft SQL Server, = + MySQL 4, MySQL 5, and PostgreSQL 8 databases - these databases = are recommended for production use. Please refer to your database documenta= tion for the correct = + RDBMS JDBC connector. The MySQL RDBMS JDBC connector can be dow= nloaded from , and the + PostgreSQL RDBMS JDBC connector can be downloaded from . + + + Refer to the help files in each download for installation inst= ructions. In most cases, the RDBMS JDBC connector comes as a .jar file. Copy this file into the $JBOSS_HOME= /server/configuration/lib/ directory. + +
+ = +
+ Datasource Descriptors + + A Datasource descriptor is required for JBoss Portal to commun= icate with a database. Sample Datasource descriptor files are provided for = the Hypersonic SQL, Microsoft SQL Server, MySQL, Oracle, and P= ostgreSQL databases. These can be found in the /jboss-as/docs/por= tal/setup/ subdirectory where the EPP x.x.x binary distribution file was extrac= ted to. For example, if EPP was extracted into the /jboss/ directory, the sample Datasource descriptors would be in the /jboss/jboss-epp-x.x.x/jboss-as/docs/portal/set= up directory. + + + The sample Datasource descriptors will work with default insta= llations of external databases; however, you may need to configure the corr= ect username and password. As well, the sample MySQL and PostgreSQL Datasou= rce descriptors assume the name of the database to be jboss= portal. + + + When copying a Datasource descriptor for MySQL, Microsoft SQL Server, PostgreSQL, or Oracle databases, change the <user-name>portal</user-name><= /computeroutput> and <password>portalpas= sword</password> sections to reflect t= he correct username and password for the user who has access to the jbosspo= rtal database. + + + Different Datasource Descriptors + + Only have one Datasource descriptor in the $JBOS= S_HOME/server/configuration/deploy/ d= irectory. For example, if you want to use a MySQL database, remove the portal-hsqldb-ds.xml file, and other descriptors, if they = exists. + + + + The following is an example Datasource descriptor file for MyS= QL 5: + + <?xml version=3D"1.0" encoding=3D"UTF-8"?> <datasources> @@ -55,8 +55,8 @@ </local-tx-datasource> </datasources> - -
+ +
= = Modified: docs/enterprise/trunk/Installation_Guide/en-US/Databases.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/enterprise/trunk/Installation_Guide/en-US/Databases.xml 2011-07-14= 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml 2011-07-26= 00:37:04 UTC (rev 14005) @@ -151,7 +151,7 @@ MySQL Table Errors - Tables are set up automatically when JBoss Portal first st= arts. Initially, two users will be stored in the jbossportal MySQL database= : a standard user with the username user, and the password user, and an adm= inistrative user with the username admin, and the password admin. Since the= database tables are created during initial startup, errors such as the fol= lowing may occur, but are safe to ignore: + Tables are set up automatically when JBoss Portal first st= arts. Initially, two users will be stored in the jbossportal MySQL database= : a standard user with the username user, and the password user, and an adm= inistrative user with the username admin, and the password admin. Since the= database tables are created during initial start up, errors such as the fo= llowing may occur, but are safe to ignore: Modified: docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.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/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml 2011= -07-14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml 2011= -07-26 00:37:04 UTC (rev 14005) @@ -3,354 +3,354 @@ ]> = - Getting Started -
- Pre-Requisites - - You must have adequate disk space to install JDK a= nd &JBEPP; while also allowing enough space for your applications. Before i= nstalling &JBEPP; you must have a working installation of Java. Since JBoss= is 100% pure Java you can have it working on any Operating System / Platfo= rm that supports Java. However, there are a few Operating System-specific i= ssues that you should be aware of. Refer to for more information. - -
- Hardware and Operating System Requirements - = - For the latest information on supported Operating System / JVM co= mbinations and supported Database platforms, please refer to h= ttp://www.jboss.com/products/platforms/application/testedconfigurations. - - to inst= all JDK and JBoss Enterprise Portal Platform while also allowing enough spa= ce for your applications. Before installing JBoss Enterprise Portal Platfor= m you must have a working installation of Java. Since JBoss is 100% pure Ja= va you can have it working on any Operating System / Platform that supports= Java. However, there are a few Operating System-specific issues that you s= hould be aware of. Refer to for more information. + +
+ Hardware and Operating System Requirements + = + For the latest information on supported Operating System= / JVM combinations and supported Database platforms, please refer to http://www.jboss.com/products/platforms/application/testedconfigura= tions. + + -
- = -
- Configuring Your Java Environment - - You must have a working installation of JDK 1.= 5 before you install &JBEPP;. You can install the 32-bit or 64-b= it JVM as per your requirements. In this guide we will show you how to inst= all a 32-bit Sun JDK 5.0 using RHN, on a generic Linux Platform and Microso= ft Windows Platform. But before we do that let's take a look at some of the= benefits of using a 64-bit JVM. - - Benefits of 64-bit JVM on 64-bit OS and Hardware: - - - Wider datapath: The pipe between RAM and CPU is doubled, which impr= oves the performance of memory-bound applications. - - - - - 64-bit memory addressing gives virtually unlimited (1 exabyte) heap= allocation. However large heaps affect garbage collection. - - - - - Applications that run with more than 1.5GB of RAM (including free s= pace for garbage collection optimization) should utilize the 64-bit JVM. - - - - - Applications that run on a 32-bit JVM and do not require more than = minimal heap sizes will gain nothing from a 64-bit JVM. Barring memory issu= es, 64-bit hardware with the same relative clock speed and architecture is = not likely to run Java applications faster than their 32-bit cousin. - - - - - Installing and Configuring 32-bit Sun JDK 5.0 using RHN - - - Java SDKs are provided by the Red Hat Enterprise Linux 5 Supplemen= tary channel for your Linux variant and architecture. Depending on the arch= itecture, the channel names are: - - - rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementa= ry-5 - - - The java-1.5.0-bea, - java-1.5.0-ibm and - java-1.5.0-sun SDKs are availa= ble from - these channels. Make sure you also install the - -devel subpackages. - - - = - - - Selecting alternatives for java, javac and java_sdk_1.5.0 (setting java_sdk_1.5.0 is optional). = - - = - - This is only needed if you want to use the SysV service script - and/or want this installed SDK to be the default java and javac - in the system. This choice can often be overridden by setting - the JAVA_HOME environment vari= able. - - = - - The alternatives system allows= different versions of Java, from different sources, to co-exist on your sy= stem. You should make sure the desired one is selected so that the service = script uses the one you want. - - = - - As root, issue the following command: - - - /usr/sbin/alternatives --config java - - - and make sure the desired one is selected (marked with a '+'), or s= elect it by entering its number as prompted. - - = - - Make sure you do the same for javac and java_sdk_1.5.0. We recommend= that all point to the same manufacturer and version. - - - - - Installing and Configuring 32-bit Sun JDK 5.0 on a generic Lin= ux platform - - - Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's we= bsite: <= /ulink>. Choose "JDK 5.0 Update <x>" (where x is the latest update nu= mber) for download and then select "RPM in self-extracting" file for Linux<= footnote>Make sure you choose the appropriate file for your platform.= . Read the instructions on Sun's website for installi= ng the JDK. - - - - - If you don't want to use SysV service scripts you can install t= he "self-extracting file" for Linux instead of choosing the "RPM in self-ex= tracting" file. In that case you can skip the next step mentioned here. But= it is recommended to use the SysV service scripts for production servers. - - - - - Download and install the appropriate -compat RPM= from JPackage here. + + <= /colspec> + + + + + Database + + + Database driver + + + + + Oracle 9i + + + Oracle thin driver + + + + + Oracle 10g R2 + + + Oracle thin driver + + + + + Microsoft SQL Server 2005 + + + Microsoft JDBC Driver + + = + + + MySQL 5.0 + + + MySQL Driver + + + + + Postgres SQL 8.1 + + + Postgres Driver + + + + + + = + + JBoss uses an embedded Tomcat and does not require a s= tand-alone Tomcat. + + --> +
+ = +
+ Configuring Your Java Environment + + You must have a working installation of JDK 1.5 before you install JBoss Enterprise Portal Platfor= m. You can install the 32-bit or 64-bit JVM as per your requirements. In th= is guide we will show you how to install a 32-bit Sun JDK 5.0 using RHN, on= a generic Linux Platform and Microsoft Windows Platform. But before we do = that let's take a look at some of the benefits of using a 64-bit JVM. + + Benefits of 64-bit JVM on 64-bit OS and Hardwar= e: + + + Wider datapath: The pipe between RAM and CPU i= s doubled, which improves the performance of memory-bound applications. + + + + + 64-bit memory addressing gives virtually unlim= ited (1 exabyte) heap allocation. However large heaps affect garbage collec= tion. + + + + + Applications that run with more than 1.5GB of = RAM (including free space for garbage collection optimization) should utili= ze the 64-bit JVM. + + + + + Applications that run on a 32-bit JVM and do n= ot require more than minimal heap sizes will gain nothing from a 64-bit JVM= . Barring memory issues, 64-bit hardware with the same relative clock speed= and architecture is not likely to run Java applications faster than their = 32-bit cousin. + + + + + Installing and Configuring 32-bit Sun JDK 5.0 u= sing RHN + + + Java SDKs are provided by the Red Hat Enterpri= se Linux 5 Supplementary channel for your Linux variant and architecture. = Depending on the architecture, the channel names are: + + + rhel-i386-server-supplementary-5 and rhel-x86_= 64-server-supplementary-5 + + + The java-1.5.0-bea<= /command>, + java-1.5.0-ibm and + java-1.5.0-sun SDKs are available from + these channels. Make sure you also install the + -devel su= b-packages. + + + = + + + Selecting alternati= ves for java, javac and java_sdk_1.5.0<= /command> (setting java_sdk_1.5.0 is o= ptional). = + + = + + This is only needed if you want to use the Sys= V service script + and/or want this installed SDK to be the defau= lt java and javac + in the system. This choice can often be overri= dden by setting + the JAVA_HOME environment variable. + + = + + The alternatives system allows different versions of Java, from different sources, t= o co-exist on your system. You should make sure the desired one is selected= so that the service script uses the one you want. + + = + + As root, issue the following command: + + + /usr/sbin/alternati= ves --config java + + + and make sure the desired one is selected (mar= ked with a '+'), or select it by entering its number as prompted. + + = + + Make sure you do the same for javac and java_sdk_1.5.0. We recommend that all point to the same manufacturer and version. + + + + + Installing and Configuring 32-bit Sun JDK 5.0 o= n a generic Linux platform + + + Download the Sun JDK 5.0 (Java 2 Development K= it) from Sun's website: . Choose "JDK 5.0 Update <x>" (where x is= the latest update number) for download and then select "RPM in self-extrac= ting" file for LinuxMake sure you choose the appropriate fi= le for your platform.. Read the instructions on Sun's= website for installing the JDK. + + + + + If you don't want to use SysV service scri= pts you can install the "self-extracting file" for Linux instead of choosin= g the "RPM in self-extracting" file. In that case you can skip the next ste= p mentioned here. But it is recommended to use the SysV service scripts for= production servers. + + + + + Download and install the appropriate = -compat RPM from JPackage here. = Please ensure you choose a matching version of the -compat package to the JDK you installed. = - - - - - Create an environment variable that points to the JDK installation = directory and call it JAVA_HOME. Add $JAVA_HOME= /bin to the system path to be able to run java= from the command line. You can do this by adding the following lines to th= e .bashrc file in your home directory. + + + + + Create an environment variable that points to = the JDK installation directory and call it JAVA_HOME. Ad= d $JAVA_HOME/bin to the system path to be able to run java from the command line. You can do this by adding the = following lines to the .bashrc file in your home direc= tory. #In this example /usr/java/jdk1.5.0_11 is the JDK installation directory. export JAVA_HOME=3D/usr/java/jdk1.5.0_11 export PATH=3D$PATH:$JAVA_HOME/bin - Set this variable for the user account doing the installation and = also for the user account that will run the server. - - - - - If you have more than one version of JVM installed in your machine,= make sure you are using the JDK1.5 installation as the default ja= va and javac. You can do this using the altern= atives system. The alternatives system allows different versions of Java, f= rom different sources to co-exist on your system. - - Select alternatives for java, javac and java_sdk_1.5.0</tit= le> - <listitem> - <para> - As root, type the following command at the shell prompt and you = should see something like this: <programlisting> + Set this variable for the user account doing = the installation and also for the user account that will run the server. + </para> + </listitem> + <listitem> + <para> + If you have more than one version of JVM insta= lled in your machine, make sure you are using the JDK1.5 installation as th= e default <literal>java</literal> and <literal>javac</literal>. You can do = this using the alternatives system. The alternatives system allows differen= t versions of Java, from different sources to co-exist on your system. + <itemizedlist> + <title>Select alternatives for java, javac= and java_sdk_1.5.0 + + + As root, type the following comman= d at the shell prompt and you should see something like this: [root(a)vsr ~]$ /usr/sbin/alternatives --config java There are 2 programs which provide 'java'. Selection Command @@ -359,15 +359,15 @@ *+ 2 /usr/lib/jvm/jre-1.5.0-sun/bin/java Enter to keep the current selection[+], or type selection number: - Make sure the Sun version [jre-1.5.0-sun in = this case] is selected (marked with a '+' in the output), or select= it by entering its number as prompted. - - - - - Repeat the same for javac and java_sdk_1.5.0. + Make sure the Sun version [jre-1.5.0-sun in this case] is selected (marked with a '+&= #39; in the output), or select it by entering its number as prompted. + + + + + Repeat the same for javac and java= _sdk_1.5.0. [root(a)vsr ~]$ /usr/sbin/alternatives --config javac There are 1 programs which provide 'javac'. - Selection Command + Selection Command ----------------------------------------------- *+ 1 /usr/lib/jvm/java-1.5.0-sun/bin/javac Enter to keep the current selection[+], or type selection number: @@ -375,220 +375,220 @@ [root(a)vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.5.0 There are 1 programs which provide 'java_sdk_1.5.0'. - Selection Command + Selection Command ----------------------------------------------- *+ 1 /usr/lib/jvm/java-1.5.0-sun Enter to keep the current selection[+], or type selection number: - You should verify that java, javac and java_sdk_1.5.0 all point= to the same manufacturer and version. - - - - - - - You can always override this step by setting the JAVA_HOM= E environment variable as explained in the previous step. - - - - - - Make sure that the java executable is in your pa= th and that you are using an appropriate version. To verify your Java envir= onment, type java -version at the shell prompt and you s= hould see something like this: + You should verify that java, java= c and java_sdk_1.5.0 all point to the same manufacturer and version. + + + + + + + You can always override this step by setti= ng the JAVA_HOME environment variable as explained in th= e previous step. + + + + + + Make sure that the java exe= cutable is in your path and that you are using an appropriate version. To v= erify your Java environment, type java -version at the s= hell prompt and you should see something like this: [root(a)vsr ~]$ java -version java version "1.5.0_11" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing) - - - - - Installing and Configuring 32-bit Sun JDK 5.0 on Microsoft Win= dows - - - Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's we= bsite: <= /ulink>. Choose "JDK 5.0 Update <x>" (where x is the latest update nu= mber) for download and then select your Windows Platform options to perform= the installation. - - - - - Create an environment variable called JAVA_HOME = that points to the JDK installation directory, for example: C:\Pro= gram Files\Java\jdk1.5.0_11\. In order to run java from the comma= nd line add the jre\bin directory to your path, for exam= ple: C:\Program Files\Java\jdk1.5.0_11\jre\bin. To do th= is, open the Control Panel from the Start Menu, switch to Classic View if n= ecessary, open the System Control Panel applet, select the Advanced Tab, an= d click on the Environment Variables button. - - - - -
+ + + + + Installing and Configuring 32-bit Sun JDK 5.0 o= n Microsoft Windows + + + Download the Sun JDK 5.0 (Java 2 Development K= it) from Sun's website: . Choose "JDK 5.0 Update <x>" (where x is= the latest update number) for download and then select your Windows Platfo= rm options to perform the installation. + + + + + Create an environment variable called JAVA_HOME that points to the JDK installation directory, for exa= mple: C:\Program Files\Java\jdk1.5.0_11\. In order to ru= n java from the command line add the jre\bin directory t= o your path, for example: C:\Program Files\Java\jdk1.5.0_11\jre\bi= n. To do this, open the Control Panel from the Start Menu, switch= to Classic View if necessary, open the System Control Panel applet, select= the Advanced Tab, and click on the Environment Variables button. + + + + +
= -
- = - - = + + = Modified: docs/enterprise/trunk/Installation_Guide/en-US/Installation.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/enterprise/trunk/Installation_Guide/en-US/Installation.xml 2011-07= -14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml 2011-07= -26 00:37:04 UTC (rev 14005) @@ -9,7 +9,7 @@ Download = - You can download the zip file from the JBoss Customer Service Portal (CSP= ). = + You can download the zip file from the JBoss Customer Service Portal = (CSP). =
= @@ -18,7 +18,7 @@ = To install from a zip file, simply unzip the downloaded file = to a directory of your choice. You can unzip the platform on any operating = system that supports the zip format. Four types of server configurations wi= ll be included in your installation - minimal, default, production and all. = - The Getting Started Guide of &JBEAP; as well as http://www.jbo= ss.org/community/docs/DOC-12942 explain in detail the different server conf= iguration file sets. = + The JBoss Enterprise Application Platform Getting Started Guide= explains, in detail, the different server configuration file sets. = = @@ -45,7 +45,7 @@ - minimal server configuration ha= s no Portal bits. It's there for the sake of consistency with &JBEAP; + minimal server configuration ha= s no Portal bits. It is included for the sake of consistency with JBoss Ent= erprise Application Platform. Modified: docs/enterprise/trunk/Installation_Guide/en-US/Introduction.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/enterprise/trunk/Installation_Guide/en-US/Introduction.xml 2011-07= -14 05:10:56 UTC (rev 14004) +++ docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml 2011-07= -26 00:37:04 UTC (rev 14005) @@ -5,18 +5,18 @@ Introduction = - &JBEPP; is the open source implementation of the Java EE suite of = services and Portal services running atop &JBEAP;. It comprises a set of of= ferings = + JBoss Enterprise Portal Platform is the open source implementation= of the Java EE suite of services and Portal services running atop JBoss En= terprise Application Platform. It comprises a set of offerings = for enterprise customers who are looking for preconfigured profile= s of JBoss Enterprise Middleware components that have been tested and certi= fied together to provide an integrated experience. Its easy-to-use server archi= tecture and high flexibility makes JBoss the ideal choice for users just st= arting out with J2EE, as well as senior architects looking for a customizab= le middleware platform. - Because it is Java-based, &JBEPP; is cross-platform and easy to in= stall and use on any operating system that supports Java. The readily avail= able source code is a powerful learning tool to debug the server and unders= tand it. It also gives you the flexibility to create customized versions fo= r your personal or business use. + Because it is Java-based, JBoss Enterprise Portal Platform is cros= s-platform and easy to install and use on any operating system that support= s Java. The readily available source code is a powerful learning tool to de= bug the server and understand it. It also gives you the flexibility to crea= te customized versions for your personal or business use. - Installing &JBEPP; is simple and easy. You can have it installed a= nd running in no time. This guide will teach you to install and uninstall J= Boss. Error Handling Configuration - The JBoss Portal request pipeline allows fine-grained, dynamic configu= ration of how JBoss Portal behaves when errors occur during runtime. + The JBoss Portal request pipeline allows fine-grained, dynamic conf= iguration of how JBoss Portal behaves when errors occur during runtime.
Error Types There are several types of errors that can occur during a requ= est: - - Access denied: the user does not have the requ= ired permissions to access the resource. - - + + Access denied: the user does not have= the required permissions to access the resource. + + - - Error: an anticipated error, such as when a po= rtlet throws an exception. - - + + Error: an anticipated error, such as = when a portlet throws an exception. + + - - Internal error: an unexpected error. - - + + Internal error: an unexpected error. + + - - Resource not found: the resource was not found. - - + + Resource not found: the resource was = not found. + + - - Resource unavailable: the resource was found, = but was not serviceable. - - + + Resource unavailable: the resource wa= s found, but was not serviceable. + +
@@ -52,33 +52,33 @@
Policy Delegation and Cascading - When a control policy is invoked, the response sent by the control flow= can be changed. If the control policy ignores the error, the error is hand= led by the next policy. If the control policy provides a new response, the = next policy is not invoked, since the new response is not an error. - - - If a portlet in a page produces an exception, the following reactions a= re possible: - - + When a control policy is invoked, the response sent by the contro= l flow can be changed. If the control policy ignores the error, the error i= s handled by the next policy. If the control policy provides a new response= , the next policy is not invoked, since the new response is not an error. + + + If a portlet in a page produces an exception, the following react= ions are possible: + + - - the error is displayed in the window. - - + + the error is displayed in the window. + + - - the window is removed from the aggregation. - - + + the window is removed from the aggregation. + + - - a portal error page is displayed. - - + + a portal error page is displayed. + + - - a HTTP 500 error response is sent to the Web browser. - - + + a HTTP 500 error response is sent to the Web browser. + +
@@ -86,60 +86,60 @@ Default Policy The default policy applies when errors are not handled by a= nother level. By default, errors are translated into the most appropriate HTTP response: - - + + - - Access denied: HTTP 403 Forbidden - - + + Access denied: HTTP 403 Forbidden + + - - Error: HTTP 500 Internal Server Error - - + + Error: HTTP 500 Internal Server Error + + - - Internal error: HTTP 500 Internal Server Error - - + + Internal error: HTTP 500 Internal Serve= r Error + + - - Resource not found: HTTP 404 Not Found - - + + Resource not found: HTTP 404 Not Found<= /computeroutput> + + - - Resource unavailable: HTTP 404 Not Found - - + + Resource unavailable: HTTP 404 Not Foun= d + +
Portal Policy - The portal error-policy controls the response sent to the Web browser w= hen an error occurs. A default error policy exists, which can be configured= per portal. If an error occurs, the policy can either handle a redirect to= a JSP page, or ignore it. If the error is ignored, it is handled by the de= fault policy, otherwise a JSP page is invoked with the appropriate request = attributes, allowing page customization. - + The portal error-policy controls the response sent to the Web bro= wser when an error occurs. A default error policy exists, which can be conf= igured per portal. If an error occurs, the policy can either handle a redir= ect to a JSP page, or ignore it. If the error is ignored, it is handled by = the default policy, otherwise a JSP page is invoked with the appropriate re= quest attributes, allowing page customization. +
Page Policy - The window error-policy controls how pages react to aggregation errors.= Most of the time pages are an aggregation of several portlet windows, and = the action to take when an error occurs differs from other policies. When a= n error occurs, the policy can either handle it, or ignore it. If the error= is ignored, it is handled by the portal policy. Possible actions taken aft= er such errors are: - - + The window error-policy controls how pages react to aggregation e= rrors. Most of the time pages are an aggregation of several portlet windows= , and the action to take when an error occurs differs from other policies. = When an error occurs, the policy can either handle it, or ignore it. If the= error is ignored, it is handled by the portal policy. Possible actions tak= en after such errors are: + + - - remove the window from the aggregation. - - + + remove the window from the aggregation. + + - - replace the markup of the window using a redirect to a JSP page. - - + + replace the markup of the window using a redirect to a = JSP page. + +
@@ -147,13 +147,13 @@
Configuration using XML Descriptors - Different policies are configured using portal object properties, a= llowing the error-handling policy for objects to be configured in XML descr= iptors -- the *-object.xml files -- for a portal deplo= yment. + Different policies are configured using portal object properties= , allowing the error-handling policy for objects to be configured in XML de= scriptors -- the *-object.xml files -- for a portal de= ployment.
Portal Policy Properties - A set of properties configure the the behavior of the portal policy. Th= ese properties are only taken into account for objects that use the portal type. The following table represents possible portal-p= olicy properties: - + A set of properties configure the behavior of the portal policy. = These properties are only taken into account for objects that use the portal type. The following table represents possible portal= -policy properties: + = @@ -169,44 +169,44 @@ - control.portal.access_deni= ed + control.portal.ac= cess_denied when access is denied - ignore and jsp - + ignore and jsp + - control.portal.unavailable= + control.portal.un= available when a resource is unavail= able - ignore and jsp + ignore and jsp - - control.portal.not_found - when a resource is not found - ignore an= d jsp + + control.portal.no= t_found + when a resource is not found + ignore and jsp - - control.portal.internal_er= ror - when an unexpected error occurs - ignore an= d jsp + + control.portal.in= ternal_error + when an unexpected error occurs + ignore and jsp - control.portal.error + control.portal.er= ror when an expected erro= r occurs - ignore a= nd jsp + ignore and jsp - control.portal.resource_ur= i + control.portal.re= source_uri the path to the JSP u= sed for redirections a valid path to a JSP= located in the portal-core.war/ directory
- = + = = - The following portal configuration demonstrates the use of portal-polic= y properties: - - + The following portal configuration demonstrates the use of portal= -policy properties: + + MyPortal @@ -245,9 +245,9 @@
Page Policy Properties - - A set of properties configure the behavior of the page policy. These pr= operties are only taken into account for objects that use the por= tal type. The following table represents possible page-policy pr= operties: - + + A set of properties configure the behavior of the page policy. Th= ese properties are only taken into account for objects that use the portal type. The following table represents possible page-pol= icy properties: + @@ -263,43 +263,43 @@ - control.page.access_denied= + control.page.acce= ss_denied when access is denied - ignore, jsp and hide + ignore, jsp and hide - control.page.unavailable + control.page.unav= ailable when a resource is unavail= able - ignore, jsp and hide + ignore, jsp and hide - - control.page.not_found - when a resource is not found - ignore, <= computeroutput>jsp and hide + + control.page.not_= found + when a resource is not found + ignore, jsp and hide - - control.page.internal_erro= r - when an unexpected error occurs - ignore, <= computeroutput>jsp and hide + + control.page.inte= rnal_error + when an unexpected error occurs + ignore, jsp and hide - control.page.error + control.page.erro= r when an expected erro= r occurs - ignore, <= computeroutput>jsp and hide + ignore, jsp and hide - - control.page.resource_uri<= /computeroutput> - the path to the JSP used for redirections<= /entry> - ignore, <= computeroutput>jsp and hide + + control.page.reso= urce_uri + the path to the JSP used for redi= rections + ignore, jsp and hide
= - - The following page configuration demonstrates the use of page-policy pr= operties: - - + + The following page configuration demonstrates the use of page-pol= icy properties: + + MyPortal @@ -335,20 +335,20 @@ ]]> - + - Page Property Inheritance for Objects - - When page properties are configured for objects that use the portal type, the properties are inherited by pages in that port= al. - - + Page Property Inheritance for Objects + + When page properties are configured for objects that use the = portal type, the properties are inherited by pages in = that portal. + +
- Using <trademark class=3D"trade">JSP</trademark> to Handle Erro= rs + Using <trademark class=3D"trade">JSP</trademark> to Handle E= rrors - As described in previous sections, error handling can be redirected= to a JSP page. Two pages can be cre= ated to handle errors: one for the portal level, and the other for the page= level. Portal level error-handling requires a page that produces a full pa= ge, and page-level handling requires a page that produces markup, but only = for a window. When the page is invoked, a set of request attributes are pas= sed. The following table represents possible request attributes: + As described in previous sections, error handling can be redirec= ted to a JSP page. Two pages can be = created to handle errors: one for the portal level, and the other for the p= age level. Portal level error-handling requires a page that produces a full= page, and page-level handling requires a page that produces markup, but on= ly for a window. When the page is invoked, a set of request attributes are = passed. The following table represents possible request attributes: @@ -367,7 +367,7 @@ org.jboss.por= tal.control.ERROR_TYPE the error type - possible values are ACCESS_= DENIED, UNAVAILABLE, ERROR, INTERNAL_ERROR, and NOT_FOUND + possible values are A= CCESS_DENIED, UNAVAILABLE= , ERROR, INTERNAL_ERROR, and NOT_FOUND org.jboss.por= tal.control.CAUSE @@ -384,10 +384,10 @@
- - <trademark class=3D"trade">JSP</trademark> Location= - The JavaServer Pages must be located in the jboss-portal= .sar/portal-core.war/ web application. - + + <trademark class=3D"trade">JSP</trademark> Location</= title><para> + The JavaServer Pages must be located in the <filename>jboss-= portal.sar/portal-core.war/</filename> web application.</para> + </note> </para> </section> <section> @@ -396,51 +396,51 @@ The error handling policy can be configured via the portal manage= ment application. To access the portal management application: </para> <para> - <orderedlist> - <listitem> - <para> - Use a Web browser to navigate to <ulink url=3D"http://localhost:= 8080/portal" />. - </para> - </listitem> - <listitem> - <para> - Click the <guibutton>Login</guibutton> button on the top right-h= and of the welcome page, and log in as the <option>admin</option> user. - </para> - </listitem> - <listitem> - <para> - Click the <guibutton>Admin</guibutton> tab on the top right-hand= of the welcome page. Four tabs will appear on the left-hand side of the pa= ge. - </para> - </listitem> - <listitem> - <para> - Click the <guibutton>Admin</guibutton> tab to open the portal ma= nagement application, and then click the <guibutton>Portal Objects</guibutt= on> tab to display available portals. - </para> - </listitem> - </orderedlist> + <orderedlist> + <listitem> + <para> + Use a Web browser to navigate to <ulink url=3D"http:= //localhost:8080/portal" />. + </para> + </listitem> + <listitem> + <para> + Click the <guibutton>Login</guibutton> button on the= top right-hand of the welcome page, and log in as the <option>admin</optio= n> user. + </para> + </listitem> + <listitem> + <para> + Click the <guibutton>Admin</guibutton> tab on the to= p right-hand of the welcome page. Four tabs will appear on the left-hand si= de of the page. + </para> + </listitem> + <listitem> + <para> + Click the <guibutton>Admin</guibutton> tab to open t= he portal management application, and then click the <guibutton>Portal Obje= cts</guibutton> tab to display available portals. + </para> + </listitem> + </orderedlist> </para> <para> - Configuration options are available as part of the properties for e= ach configuration level. You can specify the default error handling policy = (at the root of the portal object hierarchy) for each portal, or each page,= by clicking on the <guibutton>Properties</guibutton> button for each page = or portal: + Configuration options are available as part of the properties fo= r each configuration level. You can specify the default error handling poli= cy (at the root of the portal object hierarchy) for each portal, or each pa= ge, by clicking on the <guibutton>Properties</guibutton> button for each pa= ge or portal: </para> <para> - <mediaobject> - <imageobject> - <imagedata fileref=3D"images/errorhandling/errorHandling_manageme= nt.png" scalefit=3D"1" /> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref=3D"images/errorhandling/errorHandling= _management.png" scalefit=3D"1" /> + </imageobject> + </mediaobject> </para> <para> - As well, you can specify how dashboards should behave with respect = to error handling, by clicking on the <guibutton>Dashboards</guibutton> tab= in the portal management application: + As well, you can specify how dashboards should behave with respe= ct to error handling, by clicking on the <guibutton>Dashboards</guibutton> = tab in the portal management application: </para> <para> - <mediaobject> + <mediaobject> <imageobject> - <imagedata fileref=3D"images/errorhandling/errorHandlingUI.png" align= =3D"center" scalefit=3D"1" /> + <imagedata fileref=3D"images/errorhandling/errorHandlingUI.png" = align=3D"center" scalefit=3D"1" /> </imageobject> - </mediaobject> + </mediaobject> </para> <para> - The page specified with <computeroutput>On error redirect to this r= esource</computeroutput> is used when the <option>Redirect to the specified= resource</option> action is selected for an error type, such as <computero= utput>When access to the page is denied</computeroutput>. After making chan= ges, click the <guibutton>Update</guibutton> button for settings to take ef= fect. + The page specified with <computeroutput>On error redirect to thi= s resource</computeroutput> is used when the <option>Redirect to the specif= ied resource</option> action is selected for an error type, such as <comput= eroutput>When access to the page is denied</computeroutput>. After making c= hanges, click the <guibutton>Update</guibutton> button for settings to take= effect. </para> </section> </chapter> \ No newline at end of file Modified: docs/enterprise/trunk/Reference_Guide/en-US/Identity.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/enterprise/trunk/Reference_Guide/en-US/Identity.xml 2011-07-26 00:= 56:11 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/Identity.xml 2011-07-26 01:= 16:27 UTC (rev 14007) @@ -39,9 +39,9 @@ public boolean validatePassword(String password); ]]></programlisting> <warning> - <para> - Important Note! The proper usage of getId() method is: - </para> + <para> + Important Note! The proper usage of getId() method is: + </para> <programlisting><![CDATA[ // Always use it like this: user.getId().toString(); @@ -54,9 +54,9 @@ // We would get a String with an LDAP server (String)user.getId(); ]]></programlisting> - <para> - This is because the ID value depends on the User implementation. = It'll probably be String object with the LDAP implementation and a Long obj= ect with the database implementation but it could be something else if one = has chosen to make its own implementation. - </para> + <para> + This is because the ID value depends on the User implementa= tion. It'll probably be String object with the LDAP implementation and a Lo= ng object with the database implementation but it could be something else i= f one has chosen to make its own implementation. + </para> </warning> </para> </listitem> @@ -161,7 +161,7 @@ <listitem> <para> The <emphasis role=3D"bold">MembershipModule</emphasis> - interface exposes operations for obtaining or managing rela= tionships beetween users and roles. + interface exposes operations for obtaining or managing rela= tionships between users and roles. The role of this service is to decouple relationship inform= ation from user and roles. Indeed while user role relationship is pretty straightforwa= rd with a relational database (using a many to many relationship with an intermediary table), wi= th an LDAP server there a different @@ -191,7 +191,7 @@ <listitem> <para> The <emphasis role=3D"bold">UserProfileModule</emphasis> - interface exposes operations to access and manage informati= ons stored in User profile: + interface exposes operations to access and manage informati= on stored in User profile: = <programlisting><![CDATA[ public Object getProperty(User user, String propertyName) @@ -207,10 +207,10 @@ throws IdentityException; ]]></programlisting> <warning> - <para> + <para> UserProfileModule.getProperty() method returns an Object. In most cases with DB backend it will always be String obje= ct. But normally you should check what - object will be retrieved using getProfileInfo() method.</para> + object will be retrieved using getProfileInfo() method.</para> </warning> </para> </listitem> @@ -287,7 +287,7 @@ (MembershipModule)new InitialContext().lookup("java:portal/MembershipModul= e"); (UserProfileModule)new InitialContext().lookup("java:portal/UserProfileMod= ule");</programlisting> <para> - Another way to do this is, if you are fimiliar with JBoss Micr= okernel architecture is to + Another way to do this is, if you are familiar with JBoss Micr= okernel architecture is to get the <emphasis role=3D"bold">IdentityServiceController</em= phasis> mbean. You may want to inject it into your services like this: </para> @@ -327,8 +327,8 @@ <emphasis role=3D"bold">User</emphasis> and <emphasis role=3D"bold">Role</emphasis> - interfaces some API usages changed. Here are the most importan= t changes you will need to aply to your - code while migrating your aplication to 2.6: + interfaces some API usages changed. Here are the most importan= t changes you will need to apply to your + code while migrating your application to 2.6: </para> <itemizedlist> <listitem> @@ -406,21 +406,21 @@ by the portal. So an *example* of UserModule service could be a p= lain Java bean object that would be: </para> <itemizedlist> - <listitem> - <para><emphasis role=3D"bold">Instantiated</emphasis> using reflection= </para> - </listitem> - <listitem> - <para><emphasis role=3D"bold">Initialized/Started</emphasis> by invoki= ng some methods</para> - </listitem> - <listitem> - <para><emphasis role=3D"bold">Registered/Exposed</emphasis> using JNDI= and/or mbeans (JBoss Microkernel) services, so other services of the porta= l can use it</para> - </listitem> - <listitem> - <para><emphasis role=3D"bold">Managed</emphasis> in the matter of life= cycle - so it'll be stopped and unregistered during portal shutdown</para> - </listitem> + <listitem> + <para><emphasis role=3D"bold">Instantiated</emphasis> using r= eflection</para> + </listitem> + <listitem> + <para><emphasis role=3D"bold">Initialized/Started</emphasis> = by invoking some methods</para> + </listitem> + <listitem> + <para><emphasis role=3D"bold">Registered/Exposed</emphasis> u= sing JNDI and/or mbeans (JBoss Microkernel) services, so other services of = the portal can use it</para> + </listitem> + <listitem> + <para><emphasis role=3D"bold">Managed</emphasis> in the matte= r of lifecycle - so it'll be stopped and unregistered during portal shutdow= n</para> + </listitem> </itemizedlist> <para> - As you see from this point of view, configuration just specifies what Ja= va class will be used and how it should be used by portal as a service. + As you see from this point of view, configuration just specifies what= Java class will be used and how it should be used by portal as a service. </para> <note><title>NoteWe use JBoss Microcontainer intern= ally to manage the sub system made of those components so if you are intere= sted in implementing custom services - look on the methods that are used by this frame= work. @@ -507,7 +507,7 @@ Module section, so they wil= l be ready to serve them. = Note - This section isn't used with Database configuration as in JBoss= Portal services exposing Hibernate + This section isn't used with Database configuration as in JB= oss Portal services exposing Hibernate are defined separately. It is used by LDAP configuration and w= e will use it as an example ]]> - Note - If you look into JBoss Portal configuration files you will find tha= t and ]]> + Note + If you look into JBoss Portal configuration files you will find = that and ]]> are specified in DefaultConfigFile and not in ConfigFile. So here is how it works: those two will be picked up from defa= ult configuration. The same rule is effective for the options - additional options will be picked up from de= fault configuration. What is linking configuration in those two files - is the ]]> tag. + is the ]]> tag.<= /para>
@@ -604,8 +604,8 @@ - Note - Here you can easily see the whole idea about having two config files= - main one and the one with default values. + Note + Here you can easily see the whole idea about having two config= files - main one and the one with default values. The above code snippet with User module comes from standardidentity-config.xml, so the file that defines default configuration values. Because of this in = the main configuration file the definition of User module will be as short as: @@ -618,7 +618,7 @@ ]]> As you can see we specify only the type and the implementat= ion - all the other values (service-name, class and set of options) are read from default configuration. But remember that you = can still overwrite any of those values in the - main config simply by overriding them. + main config simply by overriding them. =
@@ -684,12 +684,12 @@ ]]> - Note - In this section we use the same inheritance mechanism. When an optio= n is not set, its value will be read + Note + In this section we use the same inheritance mechanism. When an= option is not set, its value will be read from the default config file. But this also means that you may= need to overwrite some values that are specific to your LDAP architecture. All the options will b= e described along with module implementations - that use them. - + that use them. + @@ -786,40 +786,40 @@ = - name - property name. This value= will be used to refer to the property in UserProfileModule + name - property name. T= his value will be used to refer to the property in UserProfileMod= ule - + type - Java type of prop= erty. This type will be checked when in UserProfileModule - methods invocation. + methods invocation. - - access-mode - possible values ar= e read-write and read-only + + access-mode - possible = values are read-write and read-only = - usage - property usage can = be mandatory or optional. + usage - property usag= e can be mandatory or optional. = - display-name - property dis= play name. + display-name - proper= ty display name. = - description - description o= f property. + description - descrip= tion of property. = - - mapping - defines how property i= s mapped in the underlaying storage mechanism. It can be mapped in database + + mapping - defines how p= roperty is mapped in the underlying storage mechanism. It can be mapped in = database either as a column or dynami= c value. It can also be mapped as ldap attr= ibute. = - NoteIn current implementation column and dynamic mappings have the same = effect, as database mappings are defined in hibernate configuration.= + NoteIn current implementation column and dynamic mappings have the sa= me effect, as database mappings are defined in hibernate configuration. = - Note - Property can have both ldap and database mappings. In such situation when LDAP support is en= abled ldap mapping will take precedense. Also even whe= n using LDAP some properties will be mapped to LDAP and some to database. I= ts because LDAP schema doesn't support all attributes proper to for portal = properties. To solve this we have DelegatingUserPro= fileModuleImpl that will delegate method invocation to - ldap or database relat= ed UserProfile module. When LDAP = support is enabled and property need to be stored in database user will be = synchronized into database when needed. This behavior can be configured. - - + Note + Property can have both ldap and = database mappings. In such situation when LDAP support= is enabled ldap mapping will take precedence. Also ev= en when using LDAP some properties will be mapped to LDAP and some to datab= ase. Its because LDAP schema doesn't support all attributes proper to for p= ortal properties. To solve this we have DelegatingU= serProfileModuleImpl that will delegate method invocation to + ldap or database related UserProfile module. When LDAP support is enabled and property need to be stored in database user= will be synchronized into database when needed. This behavior can be confi= gured. + + = @@ -830,7 +830,7 @@ Identity modules implementations = NoteIdentity modules implementations rela= ted to LDAP are described in . - +
Database modules JBoss portal comes with a set of database related identity = modules implementations done using Hibernate - those are configured @@ -842,27 +842,27 @@ Classes implementing identity modules: - - org.jboss.portal.identity.db.HibernateUserM= oduleImpl - implementaing UserModule interf= ace + + org.jboss.portal.identity.db.Hiber= nateUserModuleImpl - implementing UserModule interface - - org.jboss.portal.identity.db.HibernateRoleM= oduleImpl - implementaing RoleModule interf= ace + + org.jboss.portal.identity.db.Hiber= nateRoleModuleImpl - implementing RoleModule interface - - org.jboss.portal.identity.db.HibernateMembe= rshipModuleImpl - implementaing MembershipModule interface + + org.jboss.portal.identity.db.Hiber= nateMembershipModuleImpl - implementing MembershipModu= le interface - - org.jboss.portal.identity.db.HibernateUserP= rofileModuleImpl - implementing UserProfileModule interface + + org.jboss.portal.identity.db.Hiber= nateUserProfileModuleImpl - implementing UserProfileMo= dule interface For each of those modules you can alter two config options: - - sessionFactoryJNDIName - JNDI name under whic= h hibernate SessionFactory object is registered + + sessionFactoryJNDIName - JNDI nam= e under which hibernate SessionFactory object is registered - jNDIName - JNDI name under which this = module should be registered + jNDIName - JNDI name under which= this module should be registered @@ -870,7 +870,7 @@
Delegating UserProfile module - Delegating UserProfileModule implementation has very specific role. Whe= n we use a storage mechanism like LDAP we may not be able to map all + Delegating UserProfileModule implementation has very specific rol= e. When we use a storage mechanism like LDAP we may not be able to map all user properties into LDAP attributes because of schema limitation= s. To solve this problem we still can use the database to store user proper= ties that do not exist in the LDAP schema. The Delegating user profile module will recognize if a property i= s mapped as ldap or database @@ -909,14 +909,14 @@ Module options are: - - dbModuleJNDIName - JNDI name un= der which database implementation of UserProfileModule is registered. + + dbModuleJNDIName - = JNDI name under which database implementation of UserProfileModule is regis= tered. - - ldapModuleJNDIName - JNDI nam= e under which ldap implementation of UserProfileModule is registered. + + ldapModuleJNDIName -= JNDI name under which ldap implementation of UserProfileModule is register= ed. - - profileConfigFile - configura= tion file for user properties. + + profileConfigFile - = configuration file for user properties. @@ -930,26 +930,26 @@ Here are the options: = - + synchronizeNonExistingUsers - when set to "true" if the user subject to the operation does not exis= t, then it will - created it in database. By default it is "true". + created it in database. By default it is "true". - + acceptOtherImplementations - if set to "true" module will accept user objects other than org.jboss.portal.identity.db.HibernateUserImpl. This is needed to enable cooperation with UserModule implementati= ons other - than org.jboss.portal.identity.db.HibernateUserModuleImp= l. The default value is set "true". + than org.jboss.portal.identity.db.HibernateUserModule= Impl. The default value is set "true". - defaultSynchronizePassword = - if this option is set, the value will be used as a password for synchroni= zed user. + defaultSynchronizePassword - if this option is set, the value will be used as a password for syn= chronized user. - randomSynchronizePassword -= if this option is set to "true" synchronized user will have random generat= ed password. This is mostly used for the security reasons. Default value is= "false". + randomSynchronizePassword - if this option is set to "true" synchronized user will have random g= enerated password. This is mostly used for the security reasons. Default va= lue is "false". - sessionFactoryJNDIName - JN= DI name under which this user will be registered. + sessionFactoryJNDIName - JNDI name under which this user will be registered. - profileConfigFile - file wi= th user profile configuration. If this option is not set, and we use delega= ting UserProfileModule, profile configuration will be obtained from it. + profileConfigFile - f= ile with user profile configuration. If this option is not set, and we use = delegating UserProfileModule, profile configuration will be obtained from i= t. = Modified: docs/enterprise/trunk/Reference_Guide/en-US/Identity_Portlets.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/enterprise/trunk/Reference_Guide/en-US/Identity_Portlets.xml 2011-= 07-26 00:56:11 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/Identity_Portlets.xml 2011-= 07-26 01:16:27 UTC (rev 14007) @@ -786,7 +786,7 @@ ]]> = - For more details about jBPM please read the appropriate = JBPM Reference Guide from the SOA Platform documentation suite; . + For more details about jBPM please read the appropriate JBPM R= eference Guide from the SOA Platform documentation suite; .
Modified: docs/enterprise/trunk/Reference_Guide/en-US/Ldap.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/enterprise/trunk/Reference_Guide/en-US/Ldap.xml 2011-07-26 00:56:1= 1 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/Ldap.xml 2011-07-26 01:16:2= 7 UTC (rev 14007) @@ -232,7 +232,7 @@ UserModule - Comparision of UserModule implementations + Comparison of UserModule implementations @@ -552,7 +552,7 @@ ]]> Pagination support is not widely implemented in LDAP servers. = Because UserModule - implementations rely on JNDI and are targetted to be LDAP serv= er agnostic those methods aren't very effecient. + implementations rely on JNDI and are targeted to be LDAP serve= r agnostic those methods are not very efficient. As long as you don't rely on portal user management and use de= dicated tools for user provisioning it shouldn't bother you. Otherwise you should consider extending = the implementation and providing solution dedicated to your LDAP server. @@ -665,7 +665,7 @@ UserProfileModule
LDAPUserProfileModuleImpl - This is standard implementation that enables to retrieve= user properties from atributes in LDAP entries. + This is standard implementation that enables to retrieve= user properties from attributes in LDAP entries. To enable it in your configuration you should have: @@ -1156,7 +1156,7 @@ which means that if this single LoginModule return fail from authentication request whole process will fail. SynchronizingLoginModule has flag=3D"optional". Such combinatio= n is critical as - SynchronizingLoginModule always authen= ticates user sucessfully no matter what + SynchronizingLoginModule always authen= ticates user successfully no matter what credentials were provided. You always must have at least on= e LoginModule that you will rely on. Modified: docs/enterprise/trunk/Reference_Guide/en-US/Portal_API.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/enterprise/trunk/Reference_Guide/en-US/Portal_API.xml 2011-07-26 0= 0:56:11 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/Portal_API.xml 2011-07-26 0= 1:16:27 UTC (rev 14007) @@ -174,7 +174,7 @@ ... } ]]> - The interface offers methods to retrieve informations for a gi= ven node such as the node type, the node name + The interface offers methods to retrieve information for a giv= en node such as the node type, the node name or the properties of the node. The noticeable node types are: PortalNode.TYPE_PORTAL : the node represents a po= rtal @@ -274,12 +274,12 @@ - The portal node event class hierarchy + The portal node event class hierarchy = - The org.jboss.portal.api.node.event.PortalNodeEvent class extends the + The org.jboss.portal.api.node.event.PortalNodeEvent class extends the org.jboss.portal.api.node.PortalEvent class = and is the base class for all events of portal nodes. It defines a single method PortalNode = getNode() which can be - used to retrieve the node targetted by the event. + used to retrieve the node targeted by the event. The org.jboss.portal.api.node.event.WindowEvent is an extension for portal nodes of type window. It provides access to the mode and window state o= f the window. It has 3 subclasses which represent different kind of event that can target windows. @@ -308,9 +308,9 @@ - The portal node event propagation model + The portal node event propagation model = - = + =
Portal node event listener @@ -332,9 +332,9 @@ - The PortalNodeEventContext interface + The PortalNodeEventContext interface = - The org.jboss.portal.api.node.event.PortalNodeEventCo= ntext interface extends + The org.jboss.portal.api.node.event.PortalNodeEven= tContext interface extends the PortalEventContext interface and play= s an important role in the event delivery model explained in the previous section.= That interface gives full control over the delivery of the event to ascendant nodes in the hierarchy, eve= n more it gives the possibility to replace @@ -363,9 +363,9 @@ - The PortalSessionEvent class + The PortalSessionEvent class = - There are two different types of events: + There are two different types of events: org.jboss.portal.api.session.event.PortalSe= ssionEvent.SESSION_CREATED, fired when a new portal session is created org.jboss.portal.api.session.event.PortalSe= ssionEvent.SESSION_DESTROYED, fired when a new portal session is destroyed<= /para> @@ -383,9 +383,9 @@ = - The UserEvent class and UserAuthenticationEvent sub-classes - = - The UserAuthenticationEvent triggers two events that can be catche= d: + The UserEvent class and UserAuthenticationEvent sub-classes + = + The UserAuthenticationEvent triggers two events that can be cau= ght: org.jboss.portal.api.session.event.UserAuth= enticationEvent.SIGN_IN, fired when a portal user signs in org.jboss.portal.api.session.event.UserAuth= enticationEvent.SIGN_OUT, fired when a portal user signs out @@ -459,7 +459,7 @@ proxy-type=3D"attribute">portal:service=3DListenerRegistry counter_listener - org.jboss.portal.core.portlet.test.event.UserCounterListener + org.jboss.portal.core.portlet.test.event.UserCounterListener Modified: docs/enterprise/trunk/Reference_Guide/en-US/Revision_History.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/enterprise/trunk/Reference_Guide/en-US/Revision_History.xml 2011-0= 7-26 00:56:11 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/Revision_History.xml 2011-0= 7-26 01:16:27 UTC (rev 14007) @@ -3,9 +3,23 @@ ]> = - Revision History - - + Revision History + + + + 1-1.10 + Fri Jul 15 2011 + + Scott + Mumford + + + + + Updated old and broken hyperlinks. + + + 1-1.9 Fri Apr 08 2011 @@ -20,79 +34,79 @@ - - 1-1.8 - Tue Oct 26 2010 - - Scott - Mumford - smumford(a)redhat.com - - - - Rebuilt for new Publican version features. - - - + + 1-1.8 + Tue Oct 26 2010 + + Scott + Mumford + smumford(a)redhat.com + + + + Rebuilt for new Publican version features.= + + + = - - 1-1.7 - Thu Oct 21 2010 - - Scott - Mumford - smumford(a)redhat.com - - - - Add Revision History. - - - + + 1-1.7 + Thu Oct 21 2010 + + Scott + Mumford + smumford(a)redhat.com + + + + Add Revision History. + + + = - - 1-1.6 - Mon Oct 11 2010 - - Scott - Mumford - smumford(a)redhat.com - - - - Edit Product version number for publishing restructure. - - - - - 1-1.5 - Wed Nov 14 2009 - - - - - - - - Updated for 4.3 CP05 release. - - - + + 1-1.6 + Mon Oct 11 2010 + + Scott + Mumford + smumford(a)redhat.com + + + + Edit Product version number for publishing= restructure. + + + + + 1-1.5 + Wed Nov 14 2009 + + + + + + + + Updated for 4.3 CP05 release. + + + - 1-1.0 - Wed Nov 05 2008 - - - - - - - - Initial Creation of book. - - - - - + 1-1.0 + Wed Nov 05 2008 + + + + + + + + Initial Creation of book. + + + + + = Modified: docs/enterprise/trunk/Reference_Guide/en-US/Security.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/enterprise/trunk/Reference_Guide/en-US/Security.xml 2011-07-26 00:= 56:11 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/Security.xml 2011-07-26 01:= 16:27 UTC (rev 14007) @@ -78,34 +78,34 @@ - <unchecked/> - Anyone can view this page. + <unchecked/> + Anyone can view this page. - <role-name>SOMEROLE</role= -name> - Access to this page is limited to the defined role. + <role-name>SOMEROLE<= ;/role-name> + Access to this page is limited to the defined role. - + Access Rights: You must define the access rights given to the role defined. P= ossible values are: - view - Users can view the page. + view + Users can view the page. - viewrecursive - Users can view the page and child pages. + viewrecursive + Users can view the page and child pages. - personalize - Users are able to personalize the page's theme. + personalize + Users are able to personalize the page's theme. - personalizerecursive - Users are able to personalize the page AND its children's pages = themes. + personalizerecursive + Users are able to personalize the page AND its children= 's pages themes. = @@ -116,7 +116,7 @@ must be changed from viewrecursive to view, and viewrecursive = security constraints must be added to its children so that they can be viewed except the one you want to restrict= access to. - + We provide three live samples of this descriptor, here , @@ -133,19 +133,19 @@ considered to be CMS resources that can be secured based on portal R= oles and/or Users. - The following features are supported by the fine grained security s= ystem of Portal CMS: - - - You can associate "Read", "Write", and "Manage" Permissions at the CMS= node level. (Both Files and Folders are treated as CMS nodes) + The following features are supported by the fine grained security = system of Portal CMS: + + + You can associate "Read", "Write", and "Manage" Permission= s at the CMS node level. (Both Files and Folders are treated as CMS nodes)<= /para> - The Permissions are propagated recursively down a folder hi= erarchy + The Permissions are propagated recursively down a fol= der hierarchy - Any Permissions specified explicitly on the CMS Node overr= ides the policy inherited via recursive propagation + Any Permissions specified explicitly on the CMS Node= overrides the policy inherited via recursive propagation - You can manage the Permissions using the CMS Admin GUI tool= via the newly added "Secure Node" feature + You can manage the Permissions using the CMS Admin GU= I tool via the newly added "Secure Node" feature @@ -153,156 +153,156 @@
Portal CMS Permission Matrix: - = - - - Permissions - Allowed Actions - Implies - - - - - Read - Read Contents of Folder, File and its versions - N/A - - - Write - Create and Update new Folder and File - Read Access - - - Manage - Delete/Copy/Move/Rename Folders and Files - Read and Write Access - - - -
- + = + + + Permissions + Allowed Actions + Implies + + + + + Read + Read Contents of Folder, File and its versions + N/A + + + Write + Create and Update new Folder and File + Read Access + + + Manage + Delete/Copy/Move/Rename Folders and Files + Read and Write Access + + + + +
CMS Security Configuration The configuration for the CMS Security service is specified = in the jboss-portal.sar/portal-cms.sar/META-INF/jboss-serv= ice.xml file. The portion of the configuration relevant for securing= the CMS service is listed as follows: - - - - - java:portal/cms/AuthorizationManager= = - - portal:service=3DAuthorizationProvider,type=3Dcms - = - = - - = - - admin = - portal:service=3DModule,type=3DIdentityServiceContro= ller = - = - - - - java:/portal/cms/ACLInterceptor - java:/portal/cms/CMSSession= Factory - java:/portal/IdentityS= essionFactory - - - = - - - - - - - - - - - - = - - - - - - - - - - - = - - - - - - - - - - portal:service=3DAuthorizationManager,type=3Dcms - = - portal:service=3DHibernate,type=3DCMS - portal:service=3DModule,type=3DIdentityServiceController= = - ]]> - - -
- CMS Super User - - A CMS Super User is a designated Portal User Account that has acc= ess to all resources/functions in the CMS. It is a concept similar to the - super user concept in a Linux and UNIX security systems. This acc= ount should be carefully used and properly protected. By default, JBoss Por= tal designates the = - built-in 'admin' user account as a CMS Super User. This can be ch= anged by modifying the cmsRootUserName value in the = - jboss-portal.sar/portal-cms.sar/META-INF/jboss-service.x= ml configuration. - - - = - - admin = - portal:service=3DModule,type=3DIdentityServiceContro= ller = - = - ]]> - - -
-
- CMS Security Console - - The CMS Security Console is used to assign proper permissions to = all the nodes/content in the CMS. Besides protection on CMS content, this c= onsole itself = - needs to be secured against unauthorized acceess. Currently, the = console can be accessed only by Portal users that are members of the specif= ied Role. By default, - JBoss Portal uses the built-in Admin role to= allow access to this security console. This can be customized by modifying= the value of - defaultAdminRole option specified in jboss-portal.sar/conf/identity/standardidentity-config.xml - -
+ + + + + java:portal/cms/Authorizati= onManager = + + portal:service=3DAuthorizationProvider,type=3Dcms + = + = + + = + + admin = + portal:service=3DModule,type=3DIdentityServ= iceController = + = + + + + java:/portal/cms/ACLInterce= ptor + java:/portal/cms/C= MSSessionFactory + java:/portal/= IdentitySessionFactory + + + = = + + + + + + + + + + + + = = + + + + + + + + + + + = + + + + + + + + + + portal:service=3DAuthorizationManager,type=3Dcms + = + portal:service=3DHibernate,type=3DCMS + portal:service=3DModule,type=3DIdentityServiceC= ontroller = + ]]> + + +
+ CMS Super User + + A CMS Super User is a designated Portal User Account that = has access to all resources/functions in the CMS. It is a concept similar t= o the + super user concept in a Linux and UNIX security systems. T= his account should be carefully used and properly protected. By default, JB= oss Portal designates the = + built-in 'admin' user account as a CMS Super User. This ca= n be changed by modifying the cmsRootUserName value in= the = + jboss-portal.sar/portal-cms.sar/META-INF/jboss-se= rvice.xml configuration. + + + = + + admin = + portal:service=3DModule,type=3DIdentityServ= iceController = + = + ]]> + + +
+
+ CMS Security Console + + The CMS Security Console is used to assign proper permissi= ons to all the nodes/content in the CMS. Besides protection on CMS content,= this console itself = + needs to be secured against unauthorized access. Currently= , the console can be accessed only by Portal users that are members of the = specified Role. By default, + JBoss Portal uses the built-in Admin = role to allow access to this security console. This can be customized by mo= difying the value of + defaultAdminRole option specified in = jboss-portal.sar/conf/identity/standardidentity-config.xml + +
= = @@ -315,19 +315,19 @@ related to web applications. The main entry point of the whole po= rtal is the jboss-portal.sar/portal-server.war deployment which is the web application that defines and maps the= portal servlet. Here you can configure various things - In the WEB-INF/web.xml you can = change the authentication mode. The default + In the WEB-INF/web.xml yo= u can change the authentication mode. The default authentication mechanism uses the form based authentication= , however you can change it to any of the - mechanism provided by the servlet specification. + mechanism provided by the servlet specification. In the WEB-INF/jboss-web.xml you can = change the security domain used by the portal. The default security domain used by the portal is java:/jaas/portal. That setting is specific to the JBoss Application Server and how it binds the Java E= E security to the operational environment. A security domain is a scope defined at the Application Server Level and defi= nes usually a JAAS authentication stack. The portal security domain authentication stack is defined in the jboss-portal.sar/conf/login-config.xml and is dynamically deployed with the portal. The JBoss Appl= ication Server documentation is certainly the best - reference for that topic. + reference for that topic. - The files login.jsp and error.jsp represent the pages used - the form based authentication process. More information can be f= ound in any good servlet documentation. + The files login.jsp and error.jsp represent the pages used + the form based authentication process. More information= can be found in any good servlet documentation. @@ -335,23 +335,23 @@ The portal servlet The portal defines a single servlet to take care of all por= tal requests. The class name of that servlet is org.jboss.portal.server.servlet.PortalServlet. That servlet needs to be declared two times with different - configurations otherwise the portal would not be able to know abo= ut some request details which are importants. + configurations otherwise the portal would not be able to know abo= ut some request details which are important. - PortalServletWithPathMapping is us= ed for path mapping mappings. - PortalServletWithDefaultServletMapping is used for the default servlet mapping. + PortalServletWithPathMapping= is used for path mapping mappings. + PortalServletWithDefaultServletMapping<= /emphasis> is used for the default servlet mapping. The portal servlet is mapped four times with different semantics,= the differences between the semantics are related to the transport layer. Each one of those for mappings will have the same request meaning= for the portal beside the transport aspect. By default those mappings are - /* : the default access, does n= ot define any security constraint. This is the default - access that everybody uses. - /sec/* : the secured access, re= quires https usage. It is triggered when + /* : the default access, = does not define any security constraint. This is the default + access that everybody uses. + /sec/* : the secured acce= ss, requires https usage. It is triggered when a portlet is defined as secure or when a secure portlet lin= k is created. It requires the configuration of the https connector in JBoss Web. The JBoss Application = Server documentation provides more information - about it. + about it. /auth/* : the authenticated access, r= equires the user to be authenticated - to be used. + to be used. /authsec/* : combine the two previous= options into a single one. Usually ones should not care much about those mappings as the por= tal will by itself switch to the most appropriate mapping. @@ -372,10 +372,10 @@ class and any permission checked in the portal should extend the = PortalPermission as well. That permission adds two fields to the Permission class - uri : is a string which represents an URI of the res= ource described by the permission. - collection : an object of class org.jboss.= portal.security.PortalPermissionCollection which + uri : is a string which represents an URI of t= he resource described by the permission. + collection : an object of class org.= jboss.portal.security.PortalPermissionCollection which is used when the permission act as a container for other pe= rmissions. If that object exists then the uri field should be null - as a portal permission represents an uri or acts as a container in= an exclusive manner. + as a portal permission represents an uri or acts as a container= in an exclusive manner. @@ -393,13 +393,13 @@ } - org.jboss.portal.security.spi.provider.Dom= ainConfigurator provides configuration access - to an authorization domain. The authorization schema is very simpl= e as it consists of bindings between URI, roles and permissions. - org.jboss.portal.security.spi.provider.Per= missionRepository provides runtime access to the authorization + org.jboss.portal.security.spi.provid= er.DomainConfigurator provides configuration access + to an authorization domain. The authorization schema i= s very simple as it consists of bindings between URI, roles and permissions= . + org.jboss.portal.security.spi.provid= er.PermissionRepository provides runtime access to the authoriza= tion domain. Usually it is used to retrieve the permissions for = a specific role and URI. It is used at runtime by the framework - to take security decisions. + to take security decisions. org.jboss.portal.security.spi.provider.Permissio= nFactory is a factory to instantiate permissions - for the specific domain. It is used at runtime to create permissions obj= ects of the appropriate type by the security framework. + for the specific domain. It is used at runtime to create permissio= ns objects of the appropriate type by the security framework. @@ -417,7 +417,7 @@ - portal:service=3DPortalAuthorizationMana= gerFactory ... Modified: docs/enterprise/trunk/Reference_Guide/en-US/Theme_And_Layouts.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/enterprise/trunk/Reference_Guide/en-US/Theme_And_Layouts.xml 2011-= 07-26 00:56:11 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/Theme_And_Layouts.xml 2011-= 07-26 01:16:27 UTC (rev 14007) @@ -46,17 +46,17 @@ effectively the same for all the pages of a portal, it makes sens= e to encapsulate it in its own entity. - To implement this encapsulation there are several ways: - + To implement this encapsulation there are several ways: + = - JSP pages that get included from the layout JSP for eac= h region/portlet - a taglib that allows to place region, window, and decor= ation tags into the layout JSP + JSP pages that get included from the layout JSP f= or each region/portlet + a taglib that allows to place region, window, and= decoration tags into the layout JSP - a taglib that uses a pluggable API to delegate the ma= rkup generation to a set of classes + a taglib that uses a pluggable API to delegate the= markup generation to a set of classes - = - + = + In JBoss Portal you can currently see two out of these approaches= , namely the first and the last. Examples for the first can be found in th= e portal-core.war, implemented by the nodesk and phalanx layouts. Examples for the t= hird approach can be found @@ -64,15 +64,15 @@ markup generation for each region, window, and portlet decoration= in this last approach is what's called the RenderSet. - The RenderSet consist of four interfaces that correspond with the = four markup - containers that wrap the markup fragments of one of more portlets: + The RenderSet consist of four interfaces that correspond with t= he four markup + containers that wrap the markup fragments of one of more portlets: = - Region - Window - Decoration - Portlet Content + Region + Window + Decoration + Portlet Content = While we want to leave it open to you to decide which way to i= mplement your layouts and @@ -109,7 +109,7 @@
Overview The default header is divided into two parts, links to page= s displayed as tabs and links - to navigate between portals and dahsboards as well as loggin i= n and out. Those two parts are + to navigate between portals and dashboards as well as logging = in and out. Those two parts are included into the template thanks to the layout as defined in = . In fact, the region named, dashboardnav wil= l include the navigation links, while the region named navigation will incl= ude the navigation tabs. @@ -121,22 +121,22 @@ - Screenshot of the header with the 'renaissance' theme + Screenshot of the header with the 'renaissance' theme = NoteHere, we use split content from re= ndering by using a CSS style sheet, it allows us to change the - display by switching the CSS without affecting the content. TH= e Maple theme will display the links - on the left side with a different font for example. THis is up= to you to choose or not this approach + display by switching the CSS without affecting the content. Th= e Maple theme will display the links + on the left side with a different font for example. This is up= to you to choose or not this approach To customize the header there are several options detailed = after. - The first option would simply require to modify + The first option would simply require to modify the theme CSS, by doing this you could change the fonts,= the way tabs are rendered, colors and many - other things but not change the content. + other things but not change the content. The second option is to modify the provided JSP files, <= literal>header.jsp and tabs.jsp. It gives you more flexibili= ty than the previous solution on modifying the content. Links to legacy application could easily be= added, URLs could be arranged differently, the CSS approach could be replaced by good old HTML, CSS style n= ames could be changed... The drawback of - this method compare to the next one is the limitation in what is acces= sible from the JSP. + this method compare to the next one is the limitation in what is= accessible from the JSP. @@ -167,22 +167,22 @@ ]]> The three attributes are: - TargetContextPath: Defines the web application co= ntext where the JSP files are located - HeaderPath: Defines the location (in the web appl= ication previously defined) of the JSP in charge of writing the header link= s - TabsPath: Defines the location (in the web applic= ation previously defined) of the JSP in charge of writing the pages links (= note that it doesn't have to be renderer as tabs) + TargetContextPath: Defines the web applicat= ion context where the JSP files are located + HeaderPath: Defines the location (in the we= b application previously defined) of the JSP in charge of writing the heade= r links + TabsPath: Defines the location (in the web = application previously defined) of the JSP in charge of writing the pages l= inks (note that it doesn't have to be renderer as tabs) Writing the header JSP A couple of request attributes are set so that they can = be used by the JSP, here is the list of attributes and their meaning: - org.jboss.portal.header.USER: = A org.jboss.portal.identity.User object of the logged-in= user, null if the user is not logged-in. - org.jboss.portal.header.LOGIN_URL: URL to logging-in. - org.jboss.portal.header.DASHBOARD_URL: URL to the dashboard, null if the user is already on the dashboard= , null if the user is on the default portal already. - org.jboss.portal.header.DEFAULT_PORTAL_U= RL: URL to the default page of the portal named 'default', null i= f the user is on the default portal already. - org.jboss.portal.header.ADMIN_PORTAL_URL= : URL to the default page of the admin portal (named 'admin'), nu= ll if the user is on the admin portal already. - org.jboss.portal.header.EDIT_DASHBOARD_U= RL: URL to the page content editor of the dashboard, set only if = the user is on the dashboard, null otherwise. - org.jboss.portal.header.COPY_TO_DASHBOAR= D_URL: URL to copy a page from a portal to the personal dashboard= , null if the user is on the dashboard. - org.jboss.portal.header.SIGN_OUT_URL: URL to log out the portal. + org.jboss.portal.header.USER: A org.jboss.portal.identity.User object of the log= ged-in user, null if the user is not logged-in. + org.jboss.portal.header.LOGIN_URL<= /literal>: URL to logging-in. + org.jboss.portal.header.DASHBOARD_= URL: URL to the dashboard, null if the user is already on the das= hboard, null if the user is on the default portal already. + org.jboss.portal.header.DEFAULT_PO= RTAL_URL: URL to the default page of the portal named 'default', = null if the user is on the default portal already. + org.jboss.portal.header.ADMIN_PORT= AL_URL: URL to the default page of the admin portal (named 'admin= '), null if the user is on the admin portal already. + org.jboss.portal.header.EDIT_DASHB= OARD_URL: URL to the page content editor of the dashboard, set on= ly if the user is on the dashboard, null otherwise. + org.jboss.portal.header.COPY_TO_DA= SHBOARD_URL: URL to copy a page from a portal to the personal das= hboard, null if the user is on the dashboard. + org.jboss.portal.header.SIGN_OUT_U= RL: URL to log out the portal. Every attribute that is an URL attribute is an object imple= menting the org.jboss.portal.api.PortalURL interface. Therefore it is possible to generate the URL using the toString() method and change various things related @@ -215,9 +215,9 @@ Writing the tabs JSP A couple of request attributes are set so that they can = be used by the JSP, here is the list of attributes and their meaning: - org.jboss.portal.api.PORTAL_NODE: A org.jboss.portal.api.node.PortalNode object of the= root Portal node. Authorized children and siblings - of this object are accessible. - org.jboss.portal.api.PORTAL_RUNTIME_CONT= EXT: A org.jboss.portal.api.PortalRuntimeContext object that can be used to render URLs. + org.jboss.portal.api.PORTAL_NODE: A org.jboss.portal.api.node.PortalNode object = of the root Portal node. Authorized children and siblings + of this object are accessible. + org.jboss.portal.api.PORTAL_RUNTIM= E_CONTEXT: A org.jboss.portal.api.PortalRuntimeContext object that can be used to render URLs. The default file in charge of displaying the tabs can be= found in: portal-core.war/WEB-INF/jsp/header/ @@ -372,13 +372,13 @@ The portal comes with a set of J= SP tags that allow the layout developer faster development. - There are currently two taglibs, containing tags for different = approaches to - layouts: + There are currently two taglibs, containing tags for differe= nt approaches to + layouts: = - portal-layout.tld - theme-basic-lib.tld + portal-layout.tld + theme-basic-lib.tld = The theme-basic-lib.tld contains a list of tags that allow = a JSP writer to access @@ -638,15 +638,15 @@ A RenderSet consists of the implementations of four interfa= ces. Each of those interfaces corresponds to a markup container on the page. - Here are the four markup containers and their interface represe= ntation: - + Here are the four markup containers and their interface repr= esentation: + = - Region - RegionRenderer - Window - WindowRenderer - Decoration - DecorationRenderer - Portlet Content - PortletRenderer + Region - RegionRenderer + Window - WindowRenderer + Decoration - DecorationRenderer= + Portlet Content - PortletRenderer<= /para> - + All the renderer interfaces are specified in the org.jboss.portal.theme.render package. @@ -1090,39 +1090,39 @@ Overview NoteThis section to be updated soon wi= th new CSS selectors found in JBoss Portal 2.6. The current definitions remain, but the newer additions with regards to da= shboards/drag-n-drop have not been - documented as of yet. + documented as of yet. This document outlines the different selectors used to hand= le the layout and look/feel of the Industrial theme included in the JBoss portal. - A couple of things to know about the theming approach discussed= below: - = - + A couple of things to know about the theming approach discus= sed below: + = + = - Main premise behind this approach was to provide a c= lean separation between + Main premise behind this approach was to provi= de a clean separation between the business and presentation layer of the portal. As we= go through each selector and explain the relation to the visual presentation on t= he page, this will become - more apparent. + more apparent. - The flexibility of the selectors used in the theme= stylesheet allow a + The flexibility of the selectors used in the th= eme stylesheet allow a designer to very easily customize the visual aspects of = the portal, thereby taking the responsibility off of the developers hands through a= llowing the designer to quickly achieve the desired effect w/out the need to div= e down into code and/or having to deploy changes to the portal. This saves time = and allows both developers - and designers to focus on what they do best. + and designers to focus on what they do best. - This theme incorporates a liquid layout approach w= hich allows elements on a + This theme incorporates a liquid layout approac= h which allows elements on a page to expand/contract based on screen resolution and p= rovides a consistent look across varying display settings. However, the stylesheet= is adaptable to facilitate a fixed layout and/or combination approach wh= ere elements are pixel - based and completely independent of viewport. + based and completely independent of viewport. - The pieces that make up the portal theme consist o= f at least one stylesheet + The pieces that make up the portal theme consis= t of at least one stylesheet and any associated images. Having a consolidated set of = files to control the portal look and feel allows administrators to effortless= ly swap themes on the fly. In addition, this clean separation of the pieces that ma= ke up a specific theme will enable sharing and collaboration of different theme= s by those looking to get - involved or contribute to the open source initiative. + involved or contribute to the open source initiative. = @@ -1131,7 +1131,7 @@ Main Screen Shot Screen shot using color outline of main ID selectors used t= o control presentation and layout: - + @@ -1139,19 +1139,19 @@ = - Red Border - portal-container - Yellow Border - header-container - Orange Border - content-container - Blue Border - regionA/regionB - Green Border - portlet-container + Red Border - portal-container + Yellow Border - header-container= + Orange Border - content-container + Blue Border - regionA/regionB + Green Border - portlet-cont= ainer =
List of CSS Selectors = - The following is a list of the selectors used in the theme styles= heet, - including a brief explanation of how each selector is used in the port= al: + The following is a list of the selectors used in the theme = stylesheet, + including a brief explanation of how each selector is used in= the portal: = @@ -1202,11 +1202,11 @@ bottom and left sides of the header. Screenshot: = - + - + = #header { height: 65px; @@ -1255,12 +1255,12 @@ of the portal, or a full width look as illustrated in= the Industrial theme). Screenshot: = - + - - = + + = /* min width for IE */ #expander { position: relative; @@ -1344,12 +1344,12 @@ controls the width of the region as well as its locat= ion on the page. Screenshot: = - + - - = + + = hr.cleaner { clear:both; @@ -1419,7 +1419,7 @@ - + .portlet-titlebar-center { background-image: url( images/portlet-top-middle.gif ); background-repeat: repeat-x; @@ -1567,7 +1567,7 @@ background-image: url( images/portlet-bottom-middle.gif ); height: 4px; background-repeat: repeat-x; - /* background-color:#FFFFFF; + /* background-color:#FFFFFF; border-bottom: 1px solid #98b7c6; height:5px; */ @@ -1846,7 +1846,7 @@ = } Usage: Text that appears beside a "standard" icon (e.g - Ok, or Cancel). + OK, or Cancel). .portlet-form-field-label { font-family: Verdana, Arial, Helvetica, Sans-Serif, sans-serif; font-size: 10px; @@ -2087,39 +2087,39 @@ those CSS styles are provided by ajaxified layouts but it may not fi= t with some themes. It is possible to redefine them in the stylesheet of the themes. - + .dyna-region {} = Usage: - Denotes a dynamic region which can be subject to ajax capabilities. + Denotes a dynamic region which can be subject to ajax capabilities= . - + .dyna-window {} = Usage: - Denotes a dynamic window which can be subject to ajax capabilities. + Denotes a dynamic window which can be subject to ajax capabilities= . - + .dyna-decoration {} = Usage: - Denotes a dynamic decorator which can be subject to ajax capabilities= . + Denotes a dynamic decorator which can be subject to ajax capabilit= ies. - + .dyna-portlet {} = Usage: - Denotes a dynamic content which can be subject to ajax capabilities.<= /para> + Denotes a dynamic content which can be subject to ajax capabilitie= s. - + .dnd-handle { cursor: move; @@ -2128,9 +2128,9 @@ = Usage: Denotes the handle offered by draggable windows. By default it= changes the mouse shape to indicate - to the user that his mouse is hovering a draggable window. + to the user that his mouse is hovering a draggable window. - + .dnd-droppable { border: red 1px dashed; @@ -2140,7 +2140,7 @@ = Usage: Denotes a zone where a user can drop a window during drag and = drop operations. This selector is added - and removed dynamically at runtime by the ajax framework and is not p= resent in the generated markup. + and removed dynamically at runtime by the ajax framework and is no= t present in the generated markup.
Modified: docs/enterprise/trunk/Reference_Guide/en-US/Troubleshooting.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/enterprise/trunk/Reference_Guide/en-US/Troubleshooting.xml 2011-07= -26 00:56:11 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/Troubleshooting.xml 2011-07= -26 01:16:27 UTC (rev 14007) @@ -19,20 +19,20 @@ I am seeing "ERROR [JDBCException= Reporter] Table not found in statement" in the logfile - on first boot. What is this? + on first boot. What is this? - + I want to do a clean install/upgr= ade over my existing one. What are the - steps? + steps? - - Is my database vendor/version combination= supported? + + Is my database vendor/version co= mbination supported? - How do I force the Hibernate Dialect= used for my database? + How do I force the Hibernate D= ialect used for my database? - How do I change the context-root of= the portal to http://localhost:8080/? + How do I change the context-r= oot of the portal to http://localhost:8080/? @@ -40,13 +40,13 @@ CMS - . How do I change the CMS repository = configuration? + . How do I change the CMS repos= itory configuration? - .On reboot, the CMS is complaining ab= out a locked repository. + .On reboot, the CMS is complain= ing about a locked repository. - . I created a file in the CMSAdmin. H= ow do I view it? + . I created a file in the CMSAd= min. How do I view it? @@ -54,11 +54,11 @@ Errors - . When I access a specific portal-i= nstance or page, I keep seeing "401 - not - authorized" error in my browser. + . When I access a specific po= rtal-instance or page, I keep seeing "401 - not + authorized" error in my browser. - . How do I disable development-mod= e errors on the presentation layer? + . How do I disable developme= nt-mode errors on the presentation layer? @@ -66,9 +66,9 @@ Miscellaneous - Is there a sample portlet I can look= at to learn about portlet development and + Is there a sample portlet I ca= n look at to learn about portlet development and JBoss - Portal deployments? + Portal deployments? @@ -89,10 +89,10 @@ I want to do a clean install/upgrade over= my existing one. What are the steps? - Shut down JBoss AS - Delete JBOSS_HOME/server/default/data/portal - Delete all JBoss Portal tables from your database - Start JBoss AS. + Shut down JBoss AS + Delete JBOSS_HOME/server/default/data/portal + Delete all JBoss Portal tables from your database= + Start JBoss AS. @@ -134,7 +134,7 @@ On reboot, the CMS is complaining about a= locked repository. = - This occurs when JBoss AS is improperly shutdown or the CMS Servi= ce errors on startup. To remove the lock, + This occurs when JBoss AS is improperly shutdown or the CMS Servi= ce errors on start up. To remove the lock, shutdown JBoss, and then remove the file under JBOSS_HOME/server/= default/data/portal/cms/conf/.lock. @@ -143,14 +143,14 @@ I created a file in the CMSAdmin. How do = I view it? = - Using the default configuration, the path to the file in the browser wou= ld be: + Using the default configuration, the path to the file in the browser = would be: http://localhost:8080/portal/content/path/to/file.ext. Note that all requests for cms content must be prepended with /co= ntent and then followed by the path/to/the/file.gif as it is in your directory structure. = -
"401 - not authorised" +
"401 - not authorized" When I access a specific portal-instance = or page, I keep seeing "401 - not authorized" error in my browser. @@ -174,12 +174,12 @@ = = - Sample portlets with tutorials can be found here, - + Sample portlets with tutorials can be found here, + - Additional Portlets can be found at + Additional Portlets can be found at PortletSwap.com - . + .
Modified: docs/enterprise/trunk/Reference_Guide/en-US/Tutorials.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/enterprise/trunk/Reference_Guide/en-US/Tutorials.xml 2011-07-26 00= :56:11 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/Tutorials.xml 2011-07-26 01= :16:27 UTC (rev 14007) @@ -159,8 +159,8 @@ - = - SimplestHelloWorldPortlet deployed on a new page. + = + SimplestHelloWorldPortlet deployed on a new page. =
@@ -323,7 +323,7 @@ method needs to be implemented, and the GenericPortlet render - implemention calls our implementation when the + implementation calls our implementation when the view mode is requested. @@ -703,8 +703,8 @@ element being the path to the file in the CMS. This behavio= r is pluggable: you can plug in almost any type of content. - - Beware of context-path change + + Beware of context-path change If the context-path change the portal may not be able to= find a reference on your portlets anymore. For that reason it's= recommended to @@ -919,7 +919,7 @@ If you have read the portlet specification carefully you sh= ould have notice that portlet calls happen in one or two phases. One when th= e portlet is - just rendered, two when the portlet is actionned then rende= red. An action + just rendered, two when the portlet is actioned then render= ed. An action phase is a phase where some state change. The render phase = will have access to render parameters that will be passed each time the port= let is refreshed (with the exception of caching capabilities). @@ -984,7 +984,7 @@ edit.jsp files are very simple, they simply display some text. Note = that we used CSS styles as defined in the portlet specification. It ensures = that the portlet - will look "good" within the theme and accross portal vendor= s. + will look "good" within the theme and across portal vendors. Help mode
This is the help mode, a convenient pl= ace to give the user some help information.
]]> @@ -1108,7 +1108,7 @@ lets us write a portlet application as if it was a JSF applica= tion, the bridge takes care of the interactions between the two layers. Such an example is available in jboss-epp-4.3/jboss-as/d= ocs/portal/examples/JSFHelloUser, it uses the JBoss Portlet Bridge. - The configuration is slightly different from a JSP application= , since it is a bit tricky it is usally a good + The configuration is slightly different from a JSP application= , since it is a bit tricky it is usually a good idea to copy an existing application that starting from scratc= h. First, as any JSF application, the file faces-c= onfig.xml is required. It includes the following required information in it: Modified: docs/enterprise/trunk/Reference_Guide/en-US/WSRP.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/enterprise/trunk/Reference_Guide/en-US/WSRP.xml 2011-07-26 00:56:1= 1 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/WSRP.xml 2011-07-26 01:16:2= 7 UTC (rev 14007) @@ -50,7 +50,7 @@ = As far as caching goes, we have Level 1 Producer and Consumer.= We support Cookie handling properly on the - Consumer and our Producer requires initialization of cookies (as = we have found that it improved interoperabilty + Consumer and our Producer requires initialization of cookies (as = we have found that it improved interoperability with some consumers). We don't support custom window states or mo= des, as Portal doesn't either. We do, however, support CSS on both the Producer (though it's more a function of = the portlets than inherent Producer capability) and Consumer. @@ -238,7 +238,7 @@ Using the configuration portlet As of Portal 2.6, a configuration portlet is provided to co= nfigure access to remote WSRP Producers - grahically. You can access it at + graphically. You can access it at http://{hostname}:{port}/portal/auth/portal/admin= /WSRP or by logging in as a Portal administrator and clicking on = the WSRP tab in the Admin portal. If all went well, you should see something similar to this: @@ -483,7 +483,7 @@ =
Optional configuration - It is also possible to provide addtional configuration, = which, in some cases, might be important to + It is also possible to provide additional configuration,= which, in some cases, might be important to establish a proper connection to the remote producer. = Modified: docs/enterprise/trunk/Reference_Guide/en-US/XML_Descriptors.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/enterprise/trunk/Reference_Guide/en-US/XML_Descriptors.xml 2011-07= -26 00:56:11 UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/en-US/XML_Descriptors.xml 2011-07= -26 01:16:27 UTC (rev 14007) @@ -542,7 +542,7 @@ (display-name* | (resource-bundle, supported-locale+)))>]]> - A portal object that uses the page type. A pa= ge type represents a page, and can only have children that use the page and window types. The children windo= ws are the windows of the page, and the children pages are the subpages of = the page. + A portal object that uses the page type. A pa= ge type represents a page, and can only have children that use the page and window types. The children windo= ws are the windows of the page, and the children pages are the sub-pages of= the page. ]]> @@ -1551,7 +1551,7 @@ - A depoloyment is composed of a <deployments>= ; element, which is a container for <de= ployment> elements. In the previous example, a page is = defined, the portlet is placed as a window on a page, and an instance of th= e portlet is created. The Mangement portlet (bundled with JBoss Portal) can= modify portal instances, page position, and so on. + A deployment is composed of a <deployments>= element, which is a container for <dep= loyment> elements. In the previous example, a page is d= efined, the portlet is placed as a window on a page, and an instance of the= portlet is created. The Management portlet (bundled with JBoss Portal) can= modify portal instances, page position, and so on. The following list describes elements in a *-object.xml= file: @@ -1563,7 +1563,7 @@ <if-exists> - The <if-exists> ele= ment defines the action to take if an instance with the same name already e= xists. Accepted values are overwrite and <= computeroutput>keep. The overwrite option destroys the existing object, and creates a new one based = on the content of the deployment. The keep= option matains the existing object deployment, or creates a new one if it = does not exist. + The <if-exists> ele= ment defines the action to take if an instance with the same name already e= xists. Accepted values are overwrite and <= computeroutput>keep. The overwrite option destroys the existing object, and creates a new one based = on the content of the deployment. The keep= option maintains the existing object deployment, or creates a new one if i= t does not exist. Modified: docs/enterprise/trunk/Reference_Guide/publican.cfg =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/enterprise/trunk/Reference_Guide/publican.cfg 2011-07-26 00:56:11 = UTC (rev 14006) +++ docs/enterprise/trunk/Reference_Guide/publican.cfg 2011-07-26 01:16:27 = UTC (rev 14007) @@ -5,3 +5,6 @@ xml_lang: en-US brand: JBoss = +cvs_branch: DOCS-RHEL-6 +cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist +cvs_pkg: JBoss_Enterprise_Portal_Platform-Reference_Guide-4.3-web-__LANG__ \ No newline at end of file --===============0175169058357478622==-- From portal-commits at lists.jboss.org Mon Jul 25 21:27:27 2011 Content-Type: multipart/mixed; boundary="===============2202105367601312032==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r14008 - in docs/enterprise/trunk/Tuning_Guide: en-US and 1 other directory. Date: Mon, 25 Jul 2011 21:27:26 -0400 Message-ID: <201107260127.p6Q1RQWq025148@svn01.web.mwc.hst.phx2.redhat.com> --===============2202105367601312032== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: smumford Date: 2011-07-25 21:27:26 -0400 (Mon, 25 Jul 2011) New Revision: 14008 Modified: docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml docs/enterprise/trunk/Tuning_Guide/en-US/Revision_History.xml docs/enterprise/trunk/Tuning_Guide/en-US/clustering.xml docs/enterprise/trunk/Tuning_Guide/en-US/jbossweb.xml docs/enterprise/trunk/Tuning_Guide/en-US/jvm.xml docs/enterprise/trunk/Tuning_Guide/publican.cfg Log: Updated old and broken hyperlinks. Modified: docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.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/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml 2011-07-26 01:16= :27 UTC (rev 14007) +++ docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml 2011-07-26 01:27= :26 UTC (rev 14008) @@ -4,35 +4,33 @@ %BOOK_ENTITIES; ]> - Tuning Guide - A guide to tuning the performance of JBoss Enterprise Portal Pl= atform 4.3. - 1 - 1.4 - JBoss Enterprise Portal Platform - 4.3 - Jan, 2009 - N/A - - - This Installation Guide documents tuning of JBoss Enterprise Portal Pla= tform - + Tuning Guide + A guide to tuning the performance of JBoss Enterprise Portal= Platform 4.3. + JBoss Enterprise Portal Platform + 4.3 + 1 + 1.5 + + + This Installation Guide documents tuning of JBoss Enterprise P= ortal Platform. + = - - - - - - + + + + + + = - + = - - - &YEAR; - &HOLDER; + + + &YEAR; + &HOLDER; = - - - + + + = Modified: docs/enterprise/trunk/Tuning_Guide/en-US/Revision_History.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/enterprise/trunk/Tuning_Guide/en-US/Revision_History.xml 2011-07-2= 6 01:16:27 UTC (rev 14007) +++ docs/enterprise/trunk/Tuning_Guide/en-US/Revision_History.xml 2011-07-2= 6 01:27:26 UTC (rev 14008) @@ -4,9 +4,23 @@ %BOOK_ENTITIES; ]> - Revision History - - + Revision History + + + + 1-1.5 + Fri Jul 15 2011 + + Scott + Mumford + + + + + Updated old and broken hyperlinks. + + + 1-1.4 Fri Apr 08 2011 @@ -21,60 +35,60 @@ - - 1-1.3 - Tue Oct 26 2010 - - Scott - Mumford - smumford(a)redhat.com - - - - Rebuilt for new Publican version features. - - - + + 1-1.3 + Tue Oct 26 2010 + + Scott + Mumford + smumford(a)redhat.com + + + + Rebuilt for new Publican version features.= + + + = - - 1-1.2 - Thu 21 Oct 2010 - - Scott - Mumford - smumford(a)redhat.com + + 1-1.2 + Thu 21 Oct 2010 + + Scott + Mumford + smumford(a)redhat.com = - - - - Added syntax highlighting and updated for new Publican versi= on. + + + + Added syntax highlighting and updated for = new Publican version. = - + = - + = - - - 1-1.0 - Thu 22 Jan 2009 - - - - + + + 1-1.0 + Thu 22 Jan 2009 + + + + = - - - - Initial creation of book in Publican. + + + + Initial creation of book in Publican. = - + = - + = - + = - + = - + = Modified: docs/enterprise/trunk/Tuning_Guide/en-US/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/enterprise/trunk/Tuning_Guide/en-US/clustering.xml 2011-07-26 01:1= 6:27 UTC (rev 14007) +++ docs/enterprise/trunk/Tuning_Guide/en-US/clustering.xml 2011-07-26 01:2= 7:26 UTC (rev 14008) @@ -4,53 +4,53 @@ %BOOK_ENTITIES; ]> - Clustering Tuning -
- Enable Buddy Replication for Portal and Portlet Session Clusteri= ng - - Portal and Portlet Session are merely wrappers around HttpSession so mo= st of HTTP session clustering optimization applies to JBPP as well. EPP use= s clustering configuration of JBoss Web so changes go to jboss-w= eb-cluster.sar/META-INF/jboss-service.xml . To enable buddy rep= lication, change the value of buddyReplicationEnabled = to true. - + Clustering Tuning +
+ Enable Buddy Replication for Portal and Portlet Session Cl= ustering + + Portal and Portlet Session are merely wrappers around HttpSess= ion so most of HTTP session clustering optimization applies to JBoss Enterp= rise Portal Platform as well. JBoss Enterprise Portal Platform uses cluster= ing configuration of JBoss Web so changes go to jboss-web-cluste= r.sar/META-INF/jboss-service.xml . To enable buddy replication,= change the value of buddyReplicationEnabled to true. + = -
- = -
- Hibernate and JBoss Cache Configuration - - EPP uses JBoss Cache as a second level cache for Hibernate and this con= figuration is not defined in JBoss Cache definition used for Portal and Por= tlet Session. Instead the configuration is defined at jboss-port= al-ha.sar/META-INF/jboss-service.xml - +
+ = +
+ Hibernate and JBoss Cache Configuration + + EPP uses JBoss Cache as a second level cache for Hibernate and= this configuration is not defined in JBoss Cache definition used for Porta= l and Portlet Session. Instead the configuration is defined at j= boss-portal-ha.sar/META-INF/jboss-service.xml + = -
- = -
- Optimistic Locking (OL) - - Our tests have shown that optimistic locking performs better under heav= y 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 bet= ter configuration. To enable optimistic locking, modify TreeCache mbean def= inition as follows: = +
+ = +
+ Optimistic Locking (OL) + + Our tests have shown that optimistic locking performs better u= nder 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: = <attribute name=3D"NodeLo= ckingScheme">OPTIMISTIC</attribute> <attribute name=3D"CacheMode">INVALIDATION_SYNC</attribute> - - - If you have not disabled query cache, then you should not use INVALIA= TION_SYNC as CACHE_MODE. Use REPL_SYNC instead. - + + + If you have not disabled query cache, then you should = not use INVALIDATION_SYNC as CACHE_MODE. Use REPL_SYNC instead. + = - + = - + = -
- = -
- Pessimistic Locking (PL) - - When using Pessimistic Locking (PL), change isolation level to READ_COM= MITTED (RC). Please see to see why it is okay to relax the iso= lation level from REPEATABLE_READ (RR). As expected, RC has better performa= nce than RR. - +
+ = +
+ Pessimistic Locking (PL) + + When using Pessimistic Locking (PL), change isolation level to= READ_COMMITTED (RC). Please see to see why it is okay to rela= x the isolation level from REPEATABLE_READ (RR). As expected, RC has better= performance than RR. + = -
- = -
- Cache Eviction Policy - - If you disabled lazy loading, then you can control number of objects an= d time they can reside in memory by configuring EvictionPolicyConfig attrib= ute of TreeCache at jboss-portal- ha.sar/META-INF/jboss-service.= xml = +
+ = +
+ Cache Eviction Policy + + If you disabled lazy loading, then you can control number of o= bjects and time they can reside in memory by configuring EvictionPolicyConf= ig attribute of TreeCache at jboss-portal- ha.sar/META-INF/jboss= -service.xml = <attribute name=3D"Evicti= onPolicyConfig"> <config> <attribute name=3D"wakeUpIntervalSeconds">5</attribute> @@ -59,12 +59,12 @@ <attribute name=3D"timeToLiveSeconds">1000</attribute> </region> </config> -</attribute> = +</attribute> = = - + = -
+
= = Modified: docs/enterprise/trunk/Tuning_Guide/en-US/jbossweb.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/enterprise/trunk/Tuning_Guide/en-US/jbossweb.xml 2011-07-26 01:16:= 27 UTC (rev 14007) +++ docs/enterprise/trunk/Tuning_Guide/en-US/jbossweb.xml 2011-07-26 01:27:= 26 UTC (rev 14008) @@ -4,32 +4,32 @@ %BOOK_ENTITIES; ]> - JBoss Web Tuning -
- HTTP/AJP connector threads - - Increase number of HTTP/AJP connector threads. It's recommended to set = this value to 250 * n where n is number of CPU in yo= ur server. Depending on nature of your application, this can be set higher = or lower. Modify value of maxThreads in in deploy/jboss-web.deplo= yer/server.xml = + JBoss Web Tuning +
+ HTTP/AJP connector threads + + Increase number of HTTP/AJP connector threads. It's recommende= d to set this value to 250 * n where n is number of = CPU in your server. Depending on nature of your application, this can be se= t higher or lower. Modify value of maxThreads in deploy/jboss-web= .deployer/server.xml = <Connector port=3D"8009" = address=3D"${jboss.bind.address}" protocol=3D"AJP/1.3" emptySessionPath=3D"true" enableLookups=3D"false" -redirectPort=3D"8443" maxThreads=3D"1500" /> = +redirectPort=3D"8443" maxThreads=3D"1500" /> = = - + = -
- = -
- Global Session Timeout - - 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 mor= e consistent memory footprint and more consistent throughput. Modify deploy/jboss-web.deployer/conf/web.xml = +
+ = +
+ Global Session Timeout + + 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 i= nto a more consistent memory footprint and more consistent throughput. Modi= fy deploy/jboss-web.deployer/conf/web.xml = <session-config> <session-timeout>15</session-timeout> -</session-config> = +</session-config> = = - + = -
+
= = Modified: docs/enterprise/trunk/Tuning_Guide/en-US/jvm.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/enterprise/trunk/Tuning_Guide/en-US/jvm.xml 2011-07-26 01:16:27 UT= C (rev 14007) +++ docs/enterprise/trunk/Tuning_Guide/en-US/jvm.xml 2011-07-26 01:27:26 UT= C (rev 14008) @@ -8,7 +8,7 @@
Use Large Pages - When using 64 bit Linux systems , use Linux's large memory pag= e support. Without large page support, increasing heap size may not increas= e your performance. Modify JAVA_OPTS under $JBOSS_HOME/bin/run.co= nf to add -XX:+ UseLargePages. + 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 $JBOSS_HOME/bin/run.con= f to add -XX:+ UseLargePages. =
Modified: docs/enterprise/trunk/Tuning_Guide/publican.cfg =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/enterprise/trunk/Tuning_Guide/publican.cfg 2011-07-26 01:16:27 UTC= (rev 14007) +++ docs/enterprise/trunk/Tuning_Guide/publican.cfg 2011-07-26 01:27:26 UTC= (rev 14008) @@ -5,3 +5,6 @@ xml_lang: en-US brand: JBoss = +cvs_branch: DOCS-RHEL-6 +cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist +cvs_pkg: JBoss_Enterprise_Portal_Platform-Tuning_Guide-4.3-web-__LANG__ \ No newline at end of file --===============2202105367601312032==-- From portal-commits at lists.jboss.org Mon Jul 25 21:47:32 2011 Content-Type: multipart/mixed; boundary="===============3786980525731107255==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r14009 - in docs/enterprise/trunk/PortletBridge: en-US and 1 other directory. Date: Mon, 25 Jul 2011 21:47:32 -0400 Message-ID: <201107260147.p6Q1lWBf026794@svn01.web.mwc.hst.phx2.redhat.com> --===============3786980525731107255== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: smumford Date: 2011-07-25 21:47:32 -0400 (Mon, 25 Jul 2011) New Revision: 14009 Modified: docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml docs/enterprise/trunk/PortletBridge/en-US/Revision_History.xml docs/enterprise/trunk/PortletBridge/en-US/overview.xml docs/enterprise/trunk/PortletBridge/publican.cfg Log: Updated old and broken hyperlinks. Modified: docs/enterprise/trunk/PortletBridge/en-US/Book_Info.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/enterprise/trunk/PortletBridge/en-US/Book_Info.xml 2011-07-26 01:2= 7:26 UTC (rev 14008) +++ docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml 2011-07-26 01:4= 7:32 UTC (rev 14009) @@ -2,37 +2,37 @@ - Portlet Bridge Overview - For use with JBoss Enterprise Portal Platform 4.3 - JBoss Enterprise Portal Platform - 4.3 - 1 - 2.0 - Jul, 2010 - - - The JBoss Portlet Bridge is an implementation of the JSR-301 specificat= ion to support JSF within a portlet and with added enhancements to support = other web frameworks. Currently the bridge supports any combination of JSF,= Seam, and RichFaces to run inside a portlet. - - - - - - - - - Logo - + Portlet Bridge Overview + For use with JBoss Enterprise Portal Platform 4.3 + JBoss Enterprise Portal Platform + 4.3 + = + 1 + 2.1 + + + The JBoss Portlet Bridge is an implementation of the JSR-301 s= pecification to support JSF within a portlet and with added enhancements to= support other web frameworks. Currently the bridge supports any combinatio= n of JSF, Seam, and RichFaces to run inside a portlet. + + + + + + + + + Logo + = - + = - - - &YEAR; - &HOLDER; + + + &YEAR; + &HOLDER; = - - - + + + = = Modified: docs/enterprise/trunk/PortletBridge/en-US/Revision_History.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/enterprise/trunk/PortletBridge/en-US/Revision_History.xml 2011-07-= 26 01:27:26 UTC (rev 14008) +++ docs/enterprise/trunk/PortletBridge/en-US/Revision_History.xml 2011-07-= 26 01:47:32 UTC (rev 14009) @@ -2,9 +2,23 @@ - Revision History - - + Revision History + + + + 1-2.1 + Fri Jul 15 2011 + + Scott + Mumford + + + + + Updated old and broken hyperlinks. + + + 1-2.0 Fri Apr 08 2011 @@ -19,98 +33,98 @@ - - 1-1.9 - Tue Oct 26 2010 - - Scott - Mumford - smumford(a)redhat.com - - - - Rebuilt for new Publican version features. - - - - - 1-1.8 - Mon Oct 11 2010 - - Scott - Mumford - smumford(a)redhat.com - - - - Edit Product version number for publishing restructure. - - - - - 1-1.7 - Wed 18 Aug 2010 - - Scott - Mumford - smumford(a)redhat.com - - - - Renamed to integrate more closely with Enterprise Portal P= latform documentation suite. - - - - - 1-1.6 - Fri 16 Jul 2010 - - Scott - Mumford - smumford(a)redhat.com - - - - Corrected version number error. - - - - - 1-1.5 - Thu 15 Jul 2010 - - Thomas - Heute - theute(a)redhat.com + + 1-1.9 + Tue Oct 26 2010 + + Scott + Mumford + smumford(a)redhat.com + + + + Rebuilt for new Publican version features.= + + + + + 1-1.8 + Mon Oct 11 2010 + + Scott + Mumford + smumford(a)redhat.com + + + + Edit Product version number for publishing= restructure. + + + + + 1-1.7 + Wed 18 Aug 2010 + + Scott + Mumford + smumford(a)redhat.com + + + + Renamed to integrate more closely = with Enterprise Portal Platform documentation suite. + + + + + 1-1.6 + Fri 16 Jul 2010 + + Scott + Mumford + smumford(a)redhat.com + + + + Corrected version number error. + + + + + 1-1.5 + Thu 15 Jul 2010 + + Thomas + Heute + theute(a)redhat.com = - - - - Updated for PortletBridge 2.0 - - - - - 1-1.1 - Wed 14 Jul 2010 - - Scott - Mumford - smumford(a)redhat.com + + + + Updated for PortletBridge 2.0 + + + + + 1-1.1 + Wed 14 Jul 2010 + + Scott + Mumford + smumford(a)redhat.com = - - - - Updated for EPP 4.3 CP05 Release + + + + Updated for EPP 4.3 CP05 Release = - + = - + = - + = - + = - + = Modified: docs/enterprise/trunk/PortletBridge/en-US/overview.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/enterprise/trunk/PortletBridge/en-US/overview.xml 2011-07-26 01:27= :26 UTC (rev 14008) +++ docs/enterprise/trunk/PortletBridge/en-US/overview.xml 2011-07-26 01:47= :32 UTC (rev 14009) @@ -36,7 +36,7 @@ Part of this implementation acts as a Faces= controller much as the FacesServlet does in the direct client request envi= ronment. - The other part of this implementation is provided by implement= ating a variety of (standard) Faces extensions. + The other part of this implementation is provided by a variety= of (standard) Faces extensions. Disclaimer Modified: docs/enterprise/trunk/PortletBridge/publican.cfg =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/enterprise/trunk/PortletBridge/publican.cfg 2011-07-26 01:27:26 UT= C (rev 14008) +++ docs/enterprise/trunk/PortletBridge/publican.cfg 2011-07-26 01:47:32 UT= C (rev 14009) @@ -5,3 +5,6 @@ xml_lang: en-US brand: JBoss = +cvs_branch: DOCS-RHEL-6 +cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist +cvs_pkg: JBoss_Enterprise_Portal_Platform-Portlet_Bridge_Overview-4.3-web-= __LANG__ \ No newline at end of file --===============3786980525731107255==-- From portal-commits at lists.jboss.org Tue Jul 26 00:30:10 2011 Content-Type: multipart/mixed; boundary="===============1577363168242712165==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r14010 - docs/enterprise/trunk/Release_Notes/en-US. Date: Tue, 26 Jul 2011 00:30:10 -0400 Message-ID: <201107260430.p6Q4UARM028835@svn01.web.mwc.hst.phx2.redhat.com> --===============1577363168242712165== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: smumford Date: 2011-07-26 00:30:10 -0400 (Tue, 26 Jul 2011) New Revision: 14010 Modified: docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml Log: Created by Publican. Modified: docs/enterprise/trunk/Release_Notes/en-US/Book_Info.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/enterprise/trunk/Release_Notes/en-US/Book_Info.xml 2011-07-26 01:4= 7:32 UTC (rev 14009) +++ docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml 2011-07-26 04:3= 0:10 UTC (rev 14010) @@ -6,10 +6,10 @@ CP07 Release Notes For use with JBoss Enterprise Portal Platform 4.3 CP07 - 1 - 1.2 JBoss Enterprise Portal Platform 4.3 + 1 + 1.0 These release notes contain important information related to J= Boss Enterprise Portal Platform &VZ; that may not be currently available in= the Product Manuals. You should read these Release Notes in their entirety= before installing JBoss Enterprise Portal Platform &VZ;. Modified: docs/enterprise/trunk/Release_Notes/en-US/Revision_History.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/enterprise/trunk/Release_Notes/en-US/Revision_History.xml 2011-07-= 26 01:47:32 UTC (rev 14009) +++ docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml 2011-07-= 26 04:30:10 UTC (rev 14010) @@ -4,52 +4,24 @@ %BOOK_ENTITIES; ]> - Revision History - - - - 1-1.2 - Thu Jan 20 2011 - - Scott - Mumford - smumford(a)redhat.com - - - - Publication push. - - - - - - 1-1.0 - Tue Jan 11 2011 - - Scott - Mumford - smumford(a)redhat.com - - - - Created by Publican. - - - - - + Revision History + + + + 1-1.0 + Fri Jul 15 2011 + + Scott + Mumford + smumford(a)redhat.com + + + + Created by Publican. + + + + + = --===============1577363168242712165==--