November 2011 - gatein-commits - Jboss List Archives

gatein SVN: r8140 - epp/docs/branches/5.2.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-24 19:44:45 -0500 (Thu, 24 Nov 2011) New Revision: 8140 Added: epp/docs/branches/5.2/Reference_Guide_old/ Removed: epp/docs/branches/5.2/Reference_Guide/ Log: Moving original Ref Guide to Ref Guide old

13 years, 1 month

1
0
0 / 0

gatein SVN: r8139 - in epp/docs/branches/5.2: Developer_Guide/en-US and 5 other directories.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-24 19:43:12 -0500 (Thu, 24 Nov 2011) New Revision: 8139 Added: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/RH-WSRP.xml Modified: epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.ent epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Admin_Guide/en-US/chapter-1-Introduction.xml epp/docs/branches/5.2/Admin_Guide/en-US/chapter-2-REST.xml epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml epp/docs/branches/5.2/Developer_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Developer_Guide/en-US/Preface.xml epp/docs/branches/5.2/Developer_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Author_Group.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/images/WSRP/config_self.png epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/images/WSRP/modify_reg_end.png epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/images/WSRP/modify_reg_self_end.png epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/WSRP.xml Log: WSRP ports. Admin/Dev Guide updates Modified: epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.ent =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.ent 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.ent 2011-11-25 00:43:12 UTC (rev 8139) @@ -7,7 +7,7 @@  <!ENTITY BZPRODUCT "JBoss Enterprise Portal Platform 5"> <!ENTITY BZCOMPONENT "docs-Admin_Guide"> -<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Enterpri...'>http://bugzilla.redhat.com/</ulink>"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Enterpri...'>http://bugzilla.redhat.com/</ulink>">  <!ENTITY YEAR "2011"> Modified: epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> <bookinfo id="book-Admin_Guide-Admin_Guide"> - <title>Admin Guide</title> + <title>Administration Guide</title> <subtitle>For use with JBoss Enterprise Portal Platform 5</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> Modified: epp/docs/branches/5.2/Admin_Guide/en-US/chapter-1-Introduction.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/chapter-1-Introduction.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Admin_Guide/en-US/chapter-1-Introduction.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -154,7 +154,7 @@ </entry> <entry> <para> - The read-resource operation is responsible for reading the managed resource; describing itself and listing any operations and/or sub-resources it may contain. + The read-resource operation is responsible for reading the managed resource; describing itself and listing any operations and/or sub-resources it may contain. This is the primary operation to obtain information about a managed component and it's managed resources. </para> Modified: epp/docs/branches/5.2/Admin_Guide/en-US/chapter-2-REST.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/chapter-2-REST.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Admin_Guide/en-US/chapter-2-REST.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -260,7 +260,7 @@ <para>Management attributes (which are part of a management request) are mapped by including all request parameters of the HTTP request as attributes. So if an operation supports certain attributes, query parameters can be added to the request URL to be used as attributes of the management request.</para> <example> <title>Attributes first-name and last-name as request parameters</title> - <programlisting><![CDATA[http://localhost:8080/rest/private/managed-components/foo/bar?first-name=john&last-name=doe]]></programlisting> + <programlisting>http://localhost:8080/rest/private/managed-components/foo/bar?first-name=...</programlisting> </example> <section id="sid-8094332_GateInManagement-MultivalueAttributes"> @@ -268,7 +268,7 @@ <para>Management attributes can be multi-valued (meaning more then one value associated with an attribute). This is easy as HTTP query parameters can be multi-valued as well.</para> <example> <title>Multi-valued attribute colors as request parameters</title> - <programlisting><![CDATA[http://localhost:8080/rest/private/managed-components/foo/bar?colors=red&colors=green&colors=blue]]></programlisting> + <programlisting>http://localhost:8080/rest/private/managed-components/foo/bar?colors=red&...</programlisting> </example> </section> </section> @@ -428,7 +428,7 @@ </section> <section id="sid-8094332_GateInManagement-readresource"> - <title>read-resource</title> + <title>resource</title> <para> Since the <code>read-resource</code> Modified: epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -13,257 +13,261 @@ <title>MOP Management Extension</title> <para>The MOP management extension registers the 'mop' managed component which is responsible for managing pages, navigation, and site layout. It primarily supports exporting and importing this data through the export-resource and import-resource operations. It also supports the read-config-as-xml operation to expose the portal meta data as xml.</para> - </section> - <section id="sid-8094332_GateInManagement-Operationsxx"> - - <title>Operations</title> - <section id="sid-8094332_GateInManagement-readconfigasxml"> + <section id="sid-8094332_GateInManagement-Operationsxx"> - <title>read-config-as-xml</title> + <title>Operations</title> <para> - The - <code>read-config-as-xml</code> - operation can only be executed on the site layout, pages, and navigation managed resources. The xml format returned is that of which is defined in by the - <ulink url="http://www.gatein.org/xml/ns/">gatein-objects</ulink> - xsd. This means that these resources are exposed in the same format as what a portal extension would accept for importing data into the portal. + </para> + <section id="sid-8094332_GateInManagement-readconfigasxml"> + + <title>config-as-xml</title> + <para> + The + <code>read-config-as-xml</code> + operation can only be executed on the site layout, pages, and navigation managed resources. The xml format returned is that of which is defined in by the + <ulink url="http://www.gatein.org/xml/ns/">gatein-objects</ulink> + xsd. This means that these resources are exposed in the same format as that which a portal extension would accept for importing data into the portal. + </para> + </section> + <section id="sid-8094332_GateInManagement-exportresource"> + + <title>export-resource</title> + <para> + The + <code>export-resource</code> + operation can be executed on any resource of the MOP extension (including the mop component itself). Since the management system recursively searches for all sub-resources that have export-resource defined (which they are defined at the site layout, page, and navigation level), exports can be very granular. + </para> + </section> + <section id="sid-8094332_GateInManagement-importresource"> + + <title>import-resource</title> + <para> + The + <code>import-resource</code> + operation can only be executed at the mop component (root managed resource of the mop extension). This is because the exported zip file contains the path information (like site type and site name). So executing an + <code>import-resource</code> + operation on a group site, when the zip contains data from a portal site, doesn't make sense. + </para> + <para> + The MOP + <code>import-resource</code> + operation defines the + <code>importMode</code> + attribute as follows during import. + </para> + <informaltable> + <tgroup cols="2"> + <thead> + <row> + <entry> + <para> + Mode + + </para> + </entry> + <entry> + <para> + Description + + </para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + conserve + + </para> + </entry> + <entry> + <para> + Import data only if no artifacts exist for that site. For example if one page exists for site 'classic', nothing will be imported. + + </para> + </entry> + </row> + <row> + <entry> + <para> + insert + + </para> + </entry> + <entry> + <para> + Import data when data does not exist, otherwise do nothing. + + </para> + </entry> + </row> + <row> + <entry> + <para> + merge + + </para> + </entry> + <entry> + <para> + Import when data does not exist, update data when it does exist. + + </para> + </entry> + </row> + <row> + <entry> + <para> + overwrite + + </para> + </entry> + <entry> + <para> + Delete all data for that artifact of the site, import new data. For example if the zip file only contains pages for site classic, then + + all pages for that site are deleted and imported. + + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <note> + <title>Note</title> + <para>'merge' is the default importMode.</para> + </note> + </section> </section> - <section id="sid-8094332_GateInManagement-exportresource"> + <section id="sid-8094332_GateInManagement-PathTemplatesx"> - <title>export-resource</title> - <para> - The - <code>export-resource</code> - operation can be executed on any resource of the MOP extension (including the mop component itself). Since the management system recursively searches for all sub-resources that have export-resource defined (which they are defined at the site layout, page, and navigation level), exports can be very granular. - </para> + <title>Path Templates</title> + <para>Below are the list of path template variables defined in the MOP management extension. These path template variables are used for filtering during export.</para> + <itemizedlist> + <listitem> + <para> + <code>site-type</code> + + These are the site types of the portal to include or exclude. Available values are: + <code>portal</code> + , + <code>group</code> + , and + <code>user</code> + . + </para> + </listitem> + <listitem> + <para> + <code>site-name</code> + + The sites to include or exclude. Examples could be + <code>classic</code> + and + <code>/platform/administrators</code> + . + </para> + </listitem> + <listitem> + <para> + <code>site-layout</code> + + The name of the site layout depending on the site type. Available values are: + <code>portal</code> + , + <code>group</code> + , + <code>user</code> + . + </para> + </listitem> + <listitem> + <para> + <code>page-name</code> + + The name of the page(s) to include or exclude. + </para> + </listitem> + <listitem> + <para> + <code>nav-uri</code> + + The URI of the navigation node to include or exclude. + </para> + </listitem> + </itemizedlist> </section> - <section id="sid-8094332_GateInManagement-importresource"> + <section id="sid-8094332_GateInManagement-RESTAPI"> - <title>import-resource</title> - <para> - The - <code>import-resource</code> - operation can only be executed at the mop component (root managed resource of the mop extension). This is because the exported zip file contains the path information (like site type and site name). So executing an - <code>import-resource</code> - operation on a group site, when the zip contains data from a portal site, doesn't make sense. - </para> - <para> - The MOP - <code>import-resource</code> - operation defines the - <code>importMode</code> - attribute as follows during import. - </para> - <informaltable> - <tgroup cols="2"> - <thead> - <row> - <entry> - <para> - Mode - - </para> - </entry> - <entry> - <para> - Description - - </para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para> - conserve - - </para> - </entry> - <entry> - <para> - Import data only if no artifacts exist for that site. For example if one page exists for site 'classic', nothing will be imported. - - </para> - </entry> - </row> - <row> - <entry> - <para> - insert - - </para> - </entry> - <entry> - <para> - Import data when data does not exist, otherwise do nothing. - - </para> - </entry> - </row> - <row> - <entry> - <para> - merge - - </para> - </entry> - <entry> - <para> - Import when data does not exist, update data when it does exist. - - </para> - </entry> - </row> - <row> - <entry> - <para> - overwrite - - </para> - </entry> - <entry> - <para> - Delete all data for that artifact of the site, import new data. For example if the zip file only contains pages for site classic, then - - all pages for that site are deleted and imported. - - </para> - </entry> - </row> - </tbody> - </tgroup> - </informaltable> + <title>REST API</title> <note> <title>Note</title> - <para>'merge' is the default importMode.</para> + <para>All URL's below are relative to the REST management entry point of the portal container.</para> </note> - </section> - </section> - <section id="sid-8094332_GateInManagement-PathTemplatesx"> - - <title>Path Templates</title> - <para>Below are the list of path template variables defined in the MOP management extension. These path template variables are used for filtering during export.</para> - <itemizedlist> - <listitem> + <note> + <title>Note</title> <para> - <code>site-type</code> - - These are the site types of the portal to include or exclude. Available values are: - <code>portal</code> - , - <code>group</code> - , and - <code>user</code> - . + For all read-config-as-xml refer + <ulink url="http://www.gatein.org/xml/ns/gatein_objects_1_2"/> + for the format of the XML. </para> - </listitem> - <listitem> + </note> + <section id="sid-8094332_GateInManagement-MOPComponentResource"> + + <title>MOP Component Resource</title> <para> - <code>site-name</code> - - The sites to include or exclude. Examples could be - <code>classic</code> - and - <code>/platform/administrators</code> - . + The mop managed component resource (root managed resource) is the only resource that accepts the + <code>import-resource</code> + operation. </para> - </listitem> - <listitem> - <para> - <code>site-layout</code> - - The name of the site layout depending on the site type. Available values are: - <code>portal</code> - , - <code>group</code> - , - <code>user</code> - . - </para> - </listitem> - <listitem> - <para> - <code>page-name</code> - - The name of the page(s) to include or exclude. - </para> - </listitem> - <listitem> - <para> - <code>nav-uri</code> - - The URI of the navigation node to include or exclude. - </para> - </listitem> - </itemizedlist> - </section> - <section id="sid-8094332_GateInManagement-RESTAPI"> - - <title>REST API</title> - <note> - <title>Note</title> - <para>All URL's below are relative to the REST management entry point of the portal container.</para> - </note> - <note> - <title>Note</title> - <para> - For all read-config-as-xml refer - <ulink url="http://www.gatein.org/xml/ns/gatein_objects_1_2"/> - for the format of the XML. - </para> - </note> - <section id="sid-8094332_GateInManagement-MOPComponentResource"> - - <title>MOP Component Resource</title> - <para> - The mop managed component resource (root managed resource) is the only resource that accepts the - <code>import-resource</code> - operation. - </para> - <example> - <title>HTTP Request</title> - <programlisting>PUT /mop + <example> + <title>HTTP Request</title> + <programlisting>PUT /mop Headers: Content-Type: application/zip</programlisting> - </example> - <example> - <title>HTTP Response</title> - <programlisting>HTTP/1.1 200 OK</programlisting> - </example> - </section> - <section id="sid-8094332_GateInManagement-SiteLayoutResource"> - - <title>Site Layout Resource</title> - <para> - The site layout resource represents the site layout of the portal. It's the data defined in the - <emphasis role="strong">portal.xml</emphasis> - , - <emphasis role="strong">group.xml</emphasis> - , and - <emphasis role="strong">user.xml</emphasis> - files (depending on site type) used in portal extensions to configure data. - </para> - <example> - <title>URL</title> - <programlisting>URL: /mop/{site-type}sites/{site-name}/{site-layout}</programlisting> - </example> - <section id="sid-8094332_GateInManagement-readconfigasxmlx"> + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK</programlisting> + </example> + </section> + + </section> + <section id="sid-8094332_GateInManagement-SiteLayoutResource"> - <title>read-config-as-xml</title> - <para>Example of reading the site layout as xml for site classic.</para> + <title>Site Layout Resource</title> + <para> + The site layout resource represents the site layout of the portal. It's the data defined in the + <emphasis role="strong">portal.xml</emphasis> + , + <emphasis role="strong">group.xml</emphasis> + , and + <emphasis role="strong">user.xml</emphasis> + files (depending on site type) used in portal extensions to configure data. + </para> <example> - <title>HTTP Request</title> - <programlisting>GET /mop/portalsites/classic/portal.xml + <title>URL</title> + <programlisting>URL: /mop/{site-type}sites/{site-name}/{site-layout}</programlisting> + </example> + <section id="sid-8094332_GateInManagement-readconfigasxmlx"> + + <title>config-as-xml</title> + <para>Example of reading the site layout as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/portal.xml or GET /mop/portalsites/classic/portal?op=read-config-as-xml</programlisting> - </example> - <example> - <title>HTTP Response</title> - <programlisting>HTTP/1.1 200 OK + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK Content-Type: application/xml <portal-config> @@ -273,52 +277,53 @@ <locale>en</locale> ... </portal-config></programlisting> - </example> - </section> - <section id="sid-8094332_GateInManagement-exportresourcex"> - - <title>export-resource</title> - <para>Example of exporting the site layout for site classic.</para> - <example> - <title>HTTP Request</title> - <programlisting>GET /mop/portalsites/classic/portal.zip + </example> + </section> + <section id="sid-8094332_GateInManagement-exportresourcex"> + + <title>export-resource</title> + <para>Example of exporting the site layout for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/portal.zip or GET /mop/portalsites/classic/portal?op=export-resource</programlisting> - </example> - <example> - <title>HTTP Response</title> - <programlisting>HTTP/1.1 200 OK + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK Content-Type: application/zip [binary data]</programlisting> - </example> + </example> + </section> </section> - </section> - <section id="sid-8094332_GateInManagement-PagesResource"> - - <title>Pages Resource</title> - <para>The pages resource represents the pages of the portal. It's the data defined in the pages.xml used in portal extensions to configure data.</para> - <example> - <title>URL</title> - <programlisting>URL: /mop/{site-type}sites/{site-name}/pages/{page-name}</programlisting> - </example> - <section id="sid-8094332_GateInManagement-readconfigasxmlxx"> + + <section id="sid-8094332_GateInManagement-PagesResource"> - <title>config-as-xml</title> - <para>Example of reading all pages as xml for site classic.</para> + <title>Pages Resource</title> + <para>The pages resource represents the pages of the portal. It's the data defined in the pages.xml used in portal extensions to configure data.</para> <example> - <title>HTTP Request</title> - <programlisting>GET /mop/portalsites/classic/pages.xml + <title>URL</title> + <programlisting>URL: /mop/{site-type}sites/{site-name}/pages/{page-name}</programlisting> + </example> + <section id="sid-8094332_GateInManagement-readconfigasxmlxx"> + + <title>config-as-xml</title> + <para>Example of reading all pages as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/pages.xml or GET /mop/portalsites/classic/pages?op=read-config-as-xml</programlisting> - </example> - <example> - <title>HTTP Response</title> - <programlisting>HTTP/1.1 200 OK + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK Content-Type: application/xml <page-set> @@ -331,19 +336,19 @@ <portlet-application> ... </page-set></programlisting> - </example> - <para>Example of reading the homepage as xml for site classic.</para> - <example> - <title>HTTP Request</title> - <programlisting>GET /mop/portalsites/classic/pages/homepage.xml + </example> + <para>Example of reading the homepage as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/pages/homepage.xml or GET /mop/portalsites/classic/pages/homepage?op=read-config-as-xml</programlisting> - </example> - <example> - <title>HTTP Response</title> - <programlisting>HTTP/1.1 200 OK + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK Content-Type: application/xml <page-set> @@ -356,53 +361,53 @@ <portlet-application> ... </page-set></programlisting> - </example> - </section> - <section id="sid-8094332_GateInManagement-exportresourcexx"> - - <title>export-resource</title> - <para>Example of exporting all pages of site classic.</para> - <example> - <title>HTTP Request</title> - <programlisting>GET /mop/portalsites/classic/pages.zip + </example> + </section> + <section id="sid-8094332_GateInManagement-exportresourcexx"> + + <title>export-resource</title> + <para>Example of exporting all pages of site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/pages.zip or GET /mop/portalsites/classic/pages?op=export-resource</programlisting> - </example> - <example> - <title>HTTP Response</title> - <programlisting>HTTP/1.1 200 OK + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK Content-Type: application/zip [binary data]</programlisting> - </example> + </example> + </section> </section> - </section> - <section id="sid-8094332_GateInManagement-NavigationResource"> - <title>Navigation Resource</title> - <para>The navigation resource represents the navigation of the portal. It's the data defined in the navigation.xml used in portal extensions to configure data.</para> - <example> - <title>URL</title> - <programlisting><![CDATA[ - URL: /mop/{site-type}sites/{site-name}/navigation/{nav-uri}]]></programlisting> - </example> - <section id="sid-8094332_GateInManagement-readconfigasxmlxxx"> + <section id="sid-8094332_GateInManagement-NavigationResource"> - <title>read-config-as-xml</title> - <para>Example of reading all navigation as xml for site classic.</para> + <title>Navigation Resource</title> + <para>The navigation resource represents the navigation of the portal. It's the data defined in the navigation.xml used in portal extensions to configure data.</para> <example> - <title>HTTP Request</title> - <programlisting>GET /mop/portalsites/classic/navigation.xml + <title>URL</title> + <programlisting>URL: /mop/{site-type}sites/{site-name}/navigation/{nav-uri}</programlisting> + </example> + <section id="sid-8094332_GateInManagement-readconfigasxmlxxx"> + + <title>config-as-xml</title> + <para>Example of reading all navigation as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/navigation.xml or GET /mop/portalsites/classic/navigation?op=read-config-as-xml</programlisting> - </example> - <example> - <title>HTTP Response</title> - <programlisting>HTTP/1.1 200 OK + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK Content-Type: application/xml <node-navigation> @@ -419,19 +424,19 @@ <name>sitemap</name> ... </node-navigation></programlisting> - </example> - <para>Example of reading the home node as xml for site classic.</para> - <example> - <title>HTTP Request</title> - <programlisting>GET /mop/portalsites/classic/navigation/home.xml + </example> + <para>Example of reading the home node as xml for site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/navigation/home.xml or GET /mop/portalsites/classic/navigation/home?op=read-config-as-xml</programlisting> - </example> - <example> - <title>HTTP Response</title> - <programlisting>HTTP/1.1 200 OK + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK Content-Type: application/xml <node-navigation> @@ -447,113 +452,113 @@ </node> </page-nodes> </node-navigation></programlisting> - </example> - </section> - <section id="sid-8094332_GateInManagement-exportresource_Example"> - - <title>export-resource Example</title> - <para>Example of exporting all navigation of site classic.</para> - <example> - <title>HTTP Request</title> - <programlisting>GET /mop/portalsites/classic/navigation.zip + </example> + </section> + <section id="sid-8094332_GateInManagement-exportresourcexxx"> + + <title>export-resource</title> + <para>Example of exporting all navigation of site classic.</para> + <example> + <title>HTTP Request</title> + <programlisting>GET /mop/portalsites/classic/navigation.zip or GET /mop/portalsites/classic/navigation?op=export-resource</programlisting> - </example> - <example> - <title>HTTP Response</title> - <programlisting>HTTP/1.1 200 OK + </example> + <example> + <title>HTTP Response</title> + <programlisting>HTTP/1.1 200 OK Content-Type: application/zip [binary data]</programlisting> + </example> + </section> + </section> + <section id="sid-8094332_GateInManagement-ExportandFiltering"> + + <title>Export and Filtering</title> + <para> + Filtering is activated when the + <code>filter</code> + attribute is passed to an + <code>export-resource</code> + operation. The filter attribute is a multi-value attribute that is passed as request parameters of the HTTP request. + </para> + <note> + <title>Note</title> + <para>You can either include multiple filter parameters (?filter=foo:bar&filter=baz:foo-bar) or separate via ';' character (?filter=foo:bar;baz:foo-bar)</para> + </note> + <example> + <title>Export only registry and pageManagement navigation nodes</title> + <programlisting>GET /mop/groupsites/platform/administrators/navigation.zip?filter=nav-uri:/administration/registry,/administration/pageManagement</programlisting> </example> - </section> + <example> + <title>Export all site types but user and group</title> + <programlisting>GET /mop.zip?filter=site-type:!user,group</programlisting> + </example> </section> - <section id="sid-8094332_GateInManagement-ExportandFiltering-1"> + <section id="sid-8094332_GateInManagement-CommandLineInterfacex"> - <title>Export and Filtering</title> - <para> - Filtering is activated when the - <code>filter</code> - attribute is passed to an - <code>export-resource</code> - operation. The filter attribute is a multi-value attribute that is passed as request parameters of the HTTP request. - </para> - <note> - <title>Note</title> - <para>You can either include multiple filter parameters (?filter=foo:bar&filter=baz:foo-bar) or separate via ';' character (?filter=foo:bar;baz:foo-bar)</para> - </note> - <example> - <title>Export only registry and pageManagement navigation nodes</title> - <programlisting>GET /mop/groupsites/platform/administrators/navigation.zip?filter=nav-uri:/administration/registry,/administration/pageManagement</programlisting> - </example> - <example> - <title>Export all site types but user and group</title> - <programlisting>GET /mop.zip?filter=site-type:!user,group</programlisting> - </example> - </section> - </section> - <section id="sid-8094332_GateInManagement-CommandLineInterfacex"> - - <title>Command Line Interface</title> - <para>The commands included in the management component provide us the tools to perform management operations on these MOP artifacts: site layout, pages, and navigation.</para> - <section id="sid-8094332_GateInManagement-ResourcePaths"> - - <title>Resource Paths</title> - <para>The paths of the MOP resources are exactly the same as the REST URL's (of course without the URL syntax). For example the path of the homepage for the classic site would be:</para> - <example> - <title>Example</title> - <programlisting>[ /]% cd /mop/portalsites/classic/pages/homepage + <title>Command Line Interface</title> + <para>The commands included in the management component provide us the tools to perform management operations on these MOP artifacts: site layout, pages, and navigation.</para> + <section id="sid-8094332_GateInManagement-ResourcePaths"> + + <title>Resource Paths</title> + <para>The paths of the MOP resources are exactly the same as the REST URL's (of course without the URL syntax). For example the path of the homepage for the classic site would be:</para> + <example> + <title>Example</title> + <programlisting>[ /]% cd /mop/portalsites/classic/pages/homepage [homepage]% pwd /mop/portalsites/classic/pages/homepage</programlisting> - </example> - <note> - <title>Note</title> - <para>All resources/paths can be autocompleted by hitting the tab key.</para> - </note> + </example> + <note> + <title>Note</title> + <para>All resources/paths can be autocompleted by hitting the tab key.</para> + </note> + </section> + <section id="sid-8094332_GateInManagement-ExportandFilteringx"> + + <title>Export and Filtering</title> + <para> + Filtering is activated when the + <code>filter</code> + attribute is passed to an + <code>export-resource</code> + operation. The filter attribute is a multi-value attribute that is passed to the CLI using the + <code>--filter</code> + attribute for the + <code>export</code> + command. + </para> + <example> + <title>Export all portal site types</title> + <programlisting>export --file /tmp/mop.zip --filter site-type:portal /mop</programlisting> + </example> + <example> + <title>Export all sites types but user</title> + <programlisting>export --file /tmp/mop.zip --filter site-type:!user /mop</programlisting> + </example> + <para>The option can be specified multiple times for multiple values.</para> + <example> + <title>Export only the /platform/administrators group site</title> + <programlisting>export --file /tmp/mop.zip --filter site-type:group --filter site-name:/platform/administrators /mop</programlisting> + </example> + <para> + Also as discussed in the Path Templates section in this document, the filter attribute can separate different path templates by the + <code>;</code> + character. + </para> + <example> + <title>Export only pages named homepage, navigation named home for site classic</title> + <programlisting>export --file /tmp/classic.zip --filter page-name:homepage;nav-uri:home /mop/portalsites/classic</programlisting> + </example> + <important> + <title>Important</title> + <para>All three artifacts (site layout, navigation, and pages) are included in export by default. In other words if you don't specify their path template in the filter, the data will be included.</para> + </important> + </section> </section> - <section id="sid-8094332_GateInManagement-ExportandFiltering-2"> - - <title>Export and Filtering</title> - <para> - Filtering is activated when the - <code>filter</code> - attribute is passed to an - <code>export-resource</code> - operation. The filter attribute is a multi-value attribute that is passed to the CLI using the - <code>--filter</code> - attribute for the - <code>export</code> - command. - </para> - <example> - <title>Export all portal site types</title> - <programlisting>export --file /tmp/mop.zip --filter site-type:portal /mop</programlisting> - </example> - <example> - <title>Export all sites types but user</title> - <programlisting>export --file /tmp/mop.zip --filter site-type:!user /mop</programlisting> - </example> - <para>The option can be specified multiple times for multiple values.</para> - <example> - <title>Export only the /platform/administrators group site</title> - <programlisting>export --file /tmp/mop.zip --filter site-type:group --filter site-name:/platform/administrators /mop</programlisting> - </example> - <para> - Also as discussed in the Path Templates section in this document, the filter attribute can separate different path templates by the - <code>;</code> - character. - </para> - <example> - <title>Export only pages named homepage, navigation named home for site classic</title> - <programlisting>export --file /tmp/classic.zip --filter page-name:homepage;nav-uri:home /mop/portalsites/classic</programlisting> - </example> - <important> - <title>Important</title> - <para>All three artifacts (site layout, navigation, and pages) are included in export by default. In other words if you don't specify their path template in the filter, the data will be included.</para> - </important> - </section> </section> </chapter> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/Book_Info.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Developer_Guide/en-US/Book_Info.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -1,23 +1,12 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM ".ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> <bookinfo id="book-Developer_Guide-Developer_Guide"> <title>Developer Guide</title> <subtitle>For use with JBoss Enterprise Portal Platform 5</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>4</pubsnumber> + <pubsnumber>5</pubsnumber> <abstract> <para> This guide is intended to assist developers working with JBoss Enterprise Portal Platform. It assumes a high level of technical knowledge. Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Preface.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/Preface.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Developer_Guide/en-US/Preface.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -1,21 +1,11 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM ".ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> + <preface id="pref-Developer_Guide-Preface"> - <title>Preface</title> - <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </xi:fallback> - </xi:include> + <title>Preface</title> + <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </xi:fallback> + </xi:include> </preface> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/Revision_History.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Developer_Guide/en-US/Revision_History.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -1,21 +1,25 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM ".ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> + <appendix id="appe-Developer_Guide-Revision_History"> <title>Revision History</title> <simpara> <revhistory> <revision> + <revnumber>5.2.0-5</revnumber> + <date>Friday Nov 25 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Staged with updated content.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.0-4</revnumber> <date>Tue Nov 15 2011</date> <author> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Author_Group.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Author_Group.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Author_Group.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -4,54 +4,64 @@ %BOOK_ENTITIES; ]> <authorgroup> - <editor> - <firstname>Luc</firstname> - <surname>Texier</surname> - <affiliation> - <shortaffil>Red Hat</shortaffil> - <orgdiv>JBoss Engineering</orgdiv> + <editor> + <firstname>Luc</firstname> + <surname>Texier</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>JBoss Engineering</orgdiv> - </affiliation> + </affiliation> - </editor> - <editor> - <firstname>Thomas</firstname> - <surname>Heute</surname> - <affiliation> - <shortaffil>Red Hat</shortaffil> - <orgdiv>JBoss Engineering</orgdiv> + </editor> + <editor> + <firstname>Thomas</firstname> + <surname>Heute</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>JBoss Engineering</orgdiv> - </affiliation> + </affiliation> - </editor> - <editor> - <firstname>Wesley</firstname> - <surname>Hales</surname> - <affiliation> - <shortaffil>Red Hat</shortaffil> - <orgdiv>JBoss Engineering</orgdiv> + </editor> + <editor> + <firstname>Wesley</firstname> + <surname>Hales</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>JBoss Engineering</orgdiv> - </affiliation> + </affiliation> - </editor> - <editor> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <affiliation> - <shortaffil>Red Hat</shortaffil> - <orgdiv>Engineering Content Services</orgdiv> + </editor> + <editor> + <firstname>Chris</firstname> + <surname>Laprun</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>JBoss Engineering</orgdiv> - </affiliation> + </affiliation> - </editor> - <othercredit> - <affiliation> - <orgname><emphasis role="bold"><ulink type="http" url="http://www.jboss.org/gatein/">GateIn</ulink></emphasis> and <emphasis role="bold"><ulink type="http" url="http://www.exoplatform.com">eXo Platform</ulink></emphasis></orgname> - <orgdiv>Documentation Teams</orgdiv> + </editor> + <editor> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>Engineering Content Services</orgdiv> - </affiliation> - <contrib>Based on original product documentation by:</contrib> + </affiliation> - </othercredit> + </editor> + <othercredit> + <affiliation> + <orgname><emphasis role="bold"><ulink type="http" url="http://www.jboss.org/gatein/">GateIn</ulink></emphasis> and <emphasis role="bold"><ulink type="http" url="http://www.exoplatform.com">eXo Platform</ulink></emphasis></orgname> + <orgdiv>Documentation Teams</orgdiv> + + </affiliation> + <contrib>Based on original product documentation by:</contrib> + + </othercredit> </authorgroup> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -4,30 +4,30 @@ %BOOK_ENTITIES; ]> <bookinfo id="book-Reference_Guide_eXo_JCR_1.14-Reference_Guide_eXo_JCR_1.14"> - <title>Reference Guide eXo JCR 1.14</title> - <subtitle>An in-depth guide to Enterprise Portal Platform &VZ;</subtitle> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>5.2</productnumber> - <edition>5.2.0</edition> - <pubsnumber>7</pubsnumber> - <abstract> - <para> - This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms. - </para> + <title>Reference Guide eXo JCR 1.14</title> + <subtitle>An in-depth guide to Enterprise Portal Platform &VZ;</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>5.2</productnumber> + <edition>5.2.0</edition> + <pubsnumber>9</pubsnumber> + <abstract> + <para> + This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms. + </para> - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" /> - </imageobject> + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" /> + </imageobject> - </inlinemediaobject> + </inlinemediaobject> - </corpauthor> -  <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude">  <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:include href="fallback_content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </xi:fallback> - </xi:include> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </corpauthor> +  <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude">  <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:include href="fallback_content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </xi:fallback> + </xi:include> + <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </bookinfo> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -4,138 +4,168 @@ %BOOK_ENTITIES; ]> <appendix id="appe-Reference_Guide_eXo_JCR_1.14-Revision_History"> - <title>Revision History</title> - <simpara> - <revhistory> - <revision> - <revnumber>5.2.0-6</revnumber> - <date>Thu Nov 17 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>5.2.0-9</revnumber> + <date>Fri Nov 25 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Ported latest community WSRP content.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>5.2.0-8</revnumber> + <date>Thu Nov 24 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Finalized first edit pass of eXoJCR content.</member> + <member>Moved eXoJCR section to Part IV.</member> + <member>Clean element ids and fix broken linkends.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>5.2.0-6</revnumber> + <date>Thu Nov 17 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> - </author> - <revdescription> - <simplelist> - <member>Incorporated GateIn SSO updates.</member> + </author> + <revdescription> + <simplelist> + <member>Incorporated GateIn SSO updates.</member> - </simplelist> + </simplelist> - </revdescription> + </revdescription> - </revision> - <revision> - <revnumber>5.2.0-5</revnumber> - <date>Tue Nov 15 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> + </revision> + <revision> + <revnumber>5.2.0-5</revnumber> + <date>Tue Nov 15 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> - </author> - <revdescription> - <simplelist> - <member>Staging for beta release.</member> + </author> + <revdescription> + <simplelist> + <member>Staging for beta release.</member> - </simplelist> + </simplelist> - </revdescription> + </revdescription> - </revision> - <revision> - <revnumber>5.2.0-4</revnumber> - <date>Wed Nov 9 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> + </revision> + <revision> + <revnumber>5.2.0-4</revnumber> + <date>Wed Nov 9 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> - </author> - <revdescription> - <simplelist> - <member>Republished for review/feedback.</member> + </author> + <revdescription> + <simplelist> + <member>Republished for review/feedback.</member> - </simplelist> + </simplelist> - </revdescription> + </revdescription> - </revision> - <revision> - <revnumber>5.2.0-3</revnumber> - <date>Wed Nov 2 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> + </revision> + <revision> + <revnumber>5.2.0-3</revnumber> + <date>Wed Nov 2 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> - </author> - <revdescription> - <simplelist> - <member>Staged for review of updated Foundations and eXo JCR content.</member> + </author> + <revdescription> + <simplelist> + <member>Staged for review of updated Foundations and eXo JCR content.</member> - </simplelist> + </simplelist> - </revdescription> + </revdescription> - </revision> - <revision> - <revnumber>5.2.0-2</revnumber> - <date>Tue Sep 27 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> + </revision> + <revision> + <revnumber>5.2.0-2</revnumber> + <date>Tue Sep 27 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> - </author> - <revdescription> - <simplelist> - <member>Incorporated eXo JCR 1.14 documentation.</member> + </author> + <revdescription> + <simplelist> + <member>Incorporated eXo JCR 1.14 documentation.</member> - </simplelist> + </simplelist> - </revdescription> + </revdescription> - </revision> - <revision> - <revnumber>5.2.0-5</revnumber> - <date>Wed Sep 14 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> + </revision> + <revision> + <revnumber>5.2.0-5</revnumber> + <date>Wed Sep 14 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> - </author> - <revdescription> - <simplelist> - <member>Added Global Portlet Data section.</member> + </author> + <revdescription> + <simplelist> + <member>Added Global Portlet Data section.</member> - </simplelist> + </simplelist> - </revdescription> + </revdescription> - </revision> - <revision> - <revnumber>5.2.0-1</revnumber> - <date>Mon Aug 29 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> + </revision> + <revision> + <revnumber>5.2.0-1</revnumber> + <date>Mon Aug 29 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> - </author> - <revdescription> - <simplelist> - <member>Updating version and resetting pubs/ed numbers.</member> + </author> + <revdescription> + <simplelist> + <member>Updating version and resetting pubs/ed numbers.</member> - </simplelist> + </simplelist> - </revdescription> + </revdescription> - </revision> + </revision> - </revhistory> + </revhistory> - </simpara> + </simpara> </appendix> Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/images/WSRP/config_self.png =================================================================== (Binary files differ) Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/images/WSRP/modify_reg_end.png =================================================================== (Binary files differ) Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/images/WSRP/modify_reg_self_end.png =================================================================== (Binary files differ) Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -9,13 +9,19 @@ The eXo Kernel uses dependency injection to create services based on <filename>configuration.xml</filename> configuration files. The location of the configuration files determines if services are placed into the <literal>RootContainer</literal> scope, or into the <literal>PortalContainer</literal> scope. </para> <para> - When creating a service, you also should declare its existence to the <emphasis role="bold">Container</emphasis>, therefore you create a first simple configuration file. Copy the following code to a file called "configuration.xml" and place this file in a /conf subdirectory of your service base folder. As you already know the container looks for a "/conf/configuration.xml" file in each jar-file. + When creating a service, you also should declare its existence to the <emphasis role="bold">Container</emphasis>. This fan be done by creating a simple configuration file. + </para> + <para> + Copy the following code to a <filename>configuration.xml</filename> file and save this file in a <filename>/conf</filename> subdirectory of your service base folder. The container looks for a <filename>/conf/configuration.xml</filename> file in each jar-file. </para> <para> - All <filename>configuration.xml</filename> files located at <filename>conf/configuration.xml</filename> in the classpath (any directory, or any jar in the classpath) will have their services configured in the <literal>RootContainer</literal> scope. All <filename>configuration.xml</filename> files located at <filename>conf/portal/configuration.xml</filename> in the classpath will have their services configured at the <literal>PortalContainer</literal> scope. + All <filename>configuration.xml</filename> files located at <filename>conf/configuration.xml</filename> in the classpath (any directory, or any jar in the classpath) will have their services configured in the <literal>RootContainer</literal> scope. + </para> + <para> + All <filename>configuration.xml</filename> files located at <filename>conf/portal/configuration.xml</filename> in the classpath will have their services configured at the <literal>PortalContainer</literal> scope. </para> <para> - Additionally, <emphasis role="bold">portal extensions</emphasis> can contain configuration in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml</filename>, and will also have their services configured in the <literal>PortalContainer</literal> scope. + Additionally, <emphasis role="bold">portal extensions</emphasis> can use configuration information stored in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml</filename>, and will also have their services configured in the <literal>PortalContainer</literal> scope. </para> <para> When eXo kernel reads a configuration, it loads the file from the kernel jar using the classloader and does not use an internet connection to resolve the file. @@ -45,7 +51,7 @@ <programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <para> - The configuration you find inside the jar file is considered as the default configuration. If you want to override this default configuration you can do it in different places outside the jar. When the container finds several configurations for the same service, the configuration which is found later replaces completely the one found previously. Let's call this the <emphasis>configuration override mechanism</emphasis>. + The configuration found inside the jar file is considered as the default configuration. If you want to override this default configuration you can do it in different places outside the jar. When the container finds several configurations for the same service, the configuration which is found later replaces completely the one found previously. Let's call this the <emphasis>configuration override mechanism</emphasis>. </para> <para> After deploying you find the configuration.xml file in webapps/portal/WEB-INF/conf Use component registration tags. Let's look at the key tag that defines the interface and the type tag that defines the implementation. Note that the key tag is not mandatory, but it improves performance. Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -115,7 +115,7 @@ <title>SSO Integration</title> <step> <para> - Open the <filename>/<replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jbossweb.sar/server.xml</filename> file and uncomment one of the two <parameter>Valve</parameter> entries: + Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jbossweb.sar/server.xml</filename> file and uncomment one of the two <parameter>Valve</parameter> entries: </para> <itemizedlist> <listitem> @@ -192,7 +192,7 @@ </step> <step> <para> - Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/all/deploy/jbossweb.sar/server.xml</filename> file. + Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/all/<replaceable><PROFILE></replaceable>/jbossweb.sar/server.xml</filename> file. </para> </step> @@ -239,13 +239,13 @@ </step> <step> <para> - Go to <ulink type="http" url="http://machine1.yourdomain.com:8080/portal">http://machine1.yourdomain.com:8080/portal</ulink> and login as a user. + Go to <uri>http://machine1.yourdomain.com:8080/portal</uri> and login as a user. </para> </step> <step> <para> - Access a private URL on the second host, such as <ulink type="http" url="http://machine2.yourdomain.com:8080/portal/dologin">http://machine2.yourdomain.com:8080/portal/dologin</ulink>, for example. + Access a private URL on the second host, such as <uri>http://machine2.yourdomain.com:8080/portal/dologin</uri>, for example. </para> <para> Now you should be logged directly into <literal>machine2</literal> thanks to SSO valve. @@ -327,13 +327,13 @@ </step> <step> <para> - Navigate to <ulink type="http" url="http://machine1.yourdomain.com:8080/portal/private/classic" /> and authenticate with the pre-configured user account "<systemitem>root</systemitem>" (password "<systemitem>gtn </systemitem>"). + Navigate to <uri>http://machine1.yourdomain.com:8080/portal/private/classic</uri> and authenticate with the pre-configured user account "<systemitem>root</systemitem>" (password "<systemitem>gtn </systemitem>"). </para> </step> <step> <para> - Navigate to <ulink type="http" url="http://machine1.yourdomain.com:8080/jmx-console" />. You should be automatically authenticated into the JMX Console. + Navigate to <uri>http://machine1.yourdomain.com:8080/jmx-console</uri>. You should be automatically authenticated into the JMX Console. </para> </step> @@ -849,7 +849,7 @@ OpenSSO must be purchased from <ulink type="http" url="http://www.oracle.com/technetwork/middleware/id-mgmt/overview/index.html"> Oracle </ulink> . </para> <para> - For testing purpose, use OpenSSO_80U2, which can be downloaded from <ulink type="http" url="http://download.oracle.com/otn/nt/middleware/11g/oracle_opensso_80U2.zip"> Oracle </ulink> . + For testing purposes, use OpenSSO_80U2, which can be downloaded from <ulink type="http" url="http://download.oracle.com/otn/nt/middleware/11g/oracle_opensso_80U2.zip">Oracle </ulink> . </para> </step> Added: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/RH-WSRP.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/RH-WSRP.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/RH-WSRP.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -0,0 +1,2003 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +%BOOK_ENTITIES; +]> +<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP"> + <title><remark>Web Services for Remote Portlets (WSRP)</remark></title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Introduction"> + <title>Introduction</title> + <para> + The Web Services for Remote Portlets (WSRP) specification defines a web service interface for accessing and interacting with interactive presentation-oriented web services. + </para> + <para> + It has been produced through the efforts of the Web Services for Remote Portlets (WSRP) OASIS Technical Committee. It is based on the requirements gathered and the proposals made to the committee. + </para> + <para> + Scenarios that motivate WSRP functionality include: + </para> + <itemizedlist> + <listitem> + <para> + Content hosts, such as portal servers, providing Portlets as presentation-oriented web services that can be used by aggregation engines. + </para> + + </listitem> + <listitem> + <para> + Aggregating frameworks, including portal servers, consuming presentation-oriented web services offered by content providers and integrating them into the framework. + </para> + + </listitem> + + </itemizedlist> + <para> + More information on WSRP can be found on the official <ulink url="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">website</ulink>. We suggest reading the <ulink url="http://www.oasis-open.org/committees/download.php/10539/wsrp-primer-1.0.html">primer</ulink> for a good, albeit technical, overview of WSRP. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Level_of_Support"> + <title>Level of Support</title> + <para> + The WSRP Technical Committee defined <ulink url="http://www.oasis-open.org/committees/download.php/3073">WSRP Use Profiles</ulink> to help with WSRP interoperability. Terms defined in that document will be used in this section. + </para> + <para> + JBoss Enterprise Portal Platform provides a <emphasis>Simple</emphasis> level of support for the WSRP Producer, with the exception of out-of-band registration. In-band registration and persistent local state (which are defined at the <emphasis>Complex</emphasis> level) are supported. + </para> + <para> + JBoss Enterprise Portal Platform provides a <emphasis>Medium</emphasis> level of support for the Consumer, excepting HTML markup (as JBoss Enterprise Portal Platform itself does not handle other markup types). Explicit portlet cloning and the <literal>PortletManagement</literal> interface are supported. + </para> + <para> + The WSRP component has Level 1 Producer and Consumer caching. Cookie handling is supported properly on the Consumer. The Producer requires cookie initialization (as this improves interoperability with some consumers). + </para> + <para> + JBoss Enterprise Portal Platform does not support custom window states or modes, therefore neither does the WSRP component. It does, however, support CSS on both the Producer (although this is more a function of the portlets than an inherent Producer capability) and Consumer. + </para> + <para> + JBoss Enterprise Portal Platform &VY; includes implementations of WSRP 1.0 and 2.0. + </para> + <para> + All optional features in WSRP 2 are implemented in JBoss Enterprise Portal Platform &VY; except support for lifetimes and leasing support. + </para> + <note> + <para> + As of version &VZ; of Enterprise Portal Platform, WSRP is only activated and supported when deployed on JBoss Enterprise Application Server. + </para> + + </note> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Deploying_WSRP"> + <title>Deploying WSRP</title> + <note> + <title>Notational Devices</title> + <para> + The following list of support files uses the following notational devices: + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Notations"> + <title>Notations:</title> + <varlistentry> + <term><replaceable>JBOSS_HOME</replaceable></term> + <listitem> + <para> + <replaceable>JBOSS_HOME</replaceable> refers to the directory that your instance of JBoss Enterprise Portal Platform has been extracted/installed to. For example: <filename>/home/<replaceable>USERNAME</replaceable>/jboss-epp-<replaceable><VERSION></replaceable>/</filename> + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><replaceable>WSRP_PATH</replaceable></term> + <listitem> + <para> + The WSRP files referred to in this section are found in the <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear</filename> directory. + </para> + <para> + For ease of reference this path will be represented by: <replaceable>WSRP_PATH</replaceable>. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><replaceable>WSRP_VERSION</replaceable></term> + <listitem> + <para> + <replaceable>WSRP_VERSION</replaceable> represents the version of the WSRP component in use. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><replaceable>PORTAL_VERSION</replaceable></term> + <listitem> + <para> + <replaceable>PORTAL_VERSION</replaceable> represents the version of JBoss Enterprise Portal Platform in use. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </note> + <para> + Starting with version 2.1.0-GA of the component, WSRP is packaged as a JBoss Enterprise Portal Platform extension and is now self-contained in an easy to install package named <filename>gatein-wsrp-integration.ear</filename>, deployed directly in the <filename>deploy</filename> directory of your JBoss Application Server configuration directory. + </para> + <para> + The extension itself is composed of the following components: + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-WSRP_support_files"> + <title>WSRP support files</title> + <varlistentry> + <term><filename>META-INF/</filename></term> + <listitem> + <para> + This directory contains files necessary for EAR packaging. The only file that is of interest from a user perspective is <filename>gatein-wsse-consumer.xml</filename> which allows you to configure WS-Security support for the consumer. + </para> + <para> + Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> section for more details. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>extension-component-$PORTAL_VERSION.jar</filename></term> + <listitem> + <para> + This archive which contains the components needed to integrate the WSRP component into JBoss Enterprise Portal Platform. It also includes the default configuration files for the WSRP producer and the default WSRP consumers. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>extension-config-$PORTAL_VERSION.jar</filename></term> + <listitem> + <para> + This file contains the configuration file needed by the GateIn extension mechanism to properly register this EAR as an extension. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>extension-war-$PORTAL_VERSION.war</filename></term> + <listitem> + <para> + This file contains the configuration files needed by the GateIn extension mechanism to properly setup the WSRP service. It includes <filename>wsrp-configuration.xml</filename> which, in particular, configures several options for the <code> WSRPServiceIntegration </code> component at the heart of the WSRP integration in JBoss Enterprise Portal Platform. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>lib/</filename></term> + <listitem> + <para> + This directory contains the different libraries needed by the WSRP service. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>wsrp-admin-gui-$WSRP_VERSION.war</filename></term> + <listitem> + <para> + This file contains the WSRP Configuration portlet with which you can configure consumers to access remote servers and how the WSRP producer is configured. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>wsrp-producer-jb5wsss-$WSRP_VERSION.war</filename></term> + <listitem> + <para> + This file contains the producer-side support for WS-Security. The only file of interest from a user perspective is <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for the producer. + </para> + <para> + Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> for more details. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Non_default_Ports_or_Hostnames"> + <title>Non-default Ports or Hostnames</title> + <para> + JBoss WS (the web service stack that JBoss Enterprise Portal Platform uses) should update the port and host name used in WSDL. Refer to the JBoss WS <ulink url="http://community.jboss.org/wiki/JBossWS-UserGuide#Configuration">user guide</ulink> for more information. + </para> + <para> + If the host name and port on which the server runs have been modified, the configuration for the Consumer used to consume JBoss Enterprise Portal Platform's "self" Producer will need to be updated. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" /> for directions on how to do this. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Using_WSRP_with_SSL"> + <title>Using WSRP with SSL</title> + <para> + It is possible to use WSRP over SSL for secure exchange of data. Refer to these <ulink url="http://community.jboss.org/wiki/ConfiguringWSRPforuseoverSSL">instructions</ulink> for how to do this. + </para> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-WSRP_and_WS_Security"> + <title>WSRP and WS-Security</title> + <para> + Portlets may present different data or options depending on the currently authenticated user. For remote portlets, this means having to propagate the user credentials from the consumer back to the producer in a safe and secure manner. + </para> + <para> + The WSRP specification does not directly specify how this should be accomplished, but delegates this work to the existing WS-Security standards. + </para> + <note> + <title>Web Container Compatibility</title> + <para> + WSRP and WS-Security is currently only supported on JBoss Enterprise Portal Platform when running on top of JBoss AS 5. + </para> + + </note> + <warning> + <title>Encryption</title> + <para> + <emphasis role="bold">The use of encryption is strongly recommended.</emphasis> + </para> + <para> + Credentials being sent between the consumer and producer should be encrypted or they will be sent in plain text and could be easily intercepted. + </para> + <para> + You can either configure WS-Security to encrypt and sign the SOAP messages being sent, or secure the transport layer by using an <literal>https</literal> endpoint. + </para> + <para> + Failure to encrypt the SOAP message or transport layer will result in the username and password being sent in plain text. + </para> + + </warning> + <important> + <title>Credentials</title> + <para> + When the consumer sends the user credentials to the producer, it is sending the credentials for the currently authenticated user in the consumer. This makes signing in to remote portlets transparent to end users, but also requires that the producer and consumer use the same credentials. + </para> + <para> + The username and password must be the same and valid on both servers. + </para> + <para> + The recommended approach for this situation would be to use a common LDAP configuration. Please see the User Guide at <ulink type="http" url="docs.redhat.com" /> for information on how to configure LDAP for use with JBoss Enterprise Portal Platform + </para> + + </important> + <para> + This community Wiki <ulink url="http://community.jboss.org/wiki/GateInWSRPAndWebServiceSecurity">article</ulink>, also provides a step-by-step example on how to configure WSRP with WS-Security. + </para> + <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration"> + <title>WS-Security Configuration</title> + <para> + JBoss Enterprise Portal Platform uses <application>JBossWS Native</application> to handle ws-security. + </para> + <para> + Refer to the WS-Security section of the <ulink url="http://www.jboss.org/jbossas/docs/5-x">JBoss AS 5 Administration and Configuration Guide </ulink> for in-depth configuration options. + </para> + <para> + Please note that since the consumer passes its credentials to the producer, the consumer will act at the wss client and the producer will act as the wss server. + </para> + <para> + The following are the JBossWS Native configuration files which need to be configure for WSRP: + </para> + <variablelist> + <title></title> + <varlistentry> + <term>gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</term> + <listitem> + <para> + BossWS configuration file for the consumer. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>gatein-wsrp-integration.ear/wsrp-producer-jb5wss.war/WEB-INF/conf/gatein-wsse-producer.xml</term> + <listitem> + <para> + JBossWS configuration file for the producer. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Producer_Configuration"> + <title>WS-Security Producer Configuration</title> + <para> + Other than the JBossWS configuration file mention above, no other configuration changes should be necessary for the producer. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Consumer_Configuration"> + <title>WS-Security Consumer Configuration</title> + <para> + The consumer requires some changes before it will function properly with WS-Security. + </para> + <para> + The consumer needs access to the current servlet request since this is used to retrieve the currently authenticated user. In order to access this information, the consumer needs a special servlet-filter added to the portal. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-WS_Security_Consumer_Configuration-Add_the_servlet_filter"> + <title>Add the servlet-filter</title> + <step> + <para> + Open <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add the following: + </para> + +<programlisting role="XML"> + <filter> + <filter-name>ServletAccessFilter</filter-name> + <filter-class>org.gatein.wsrp.servlet.ServletAccessFilter</filter-class> + </filter> + <filter-mapping> + <filter-name>ServletAccessFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping> +</programlisting> + + </step> + <step> + <para> + Check the <guilabel>Enable WS Security</guilabel> checkbox in the consumer configuration options of the WSRP Configuration portlet + </para> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/WSRP/config_wss_selected.png" format="PNG" scalefit="1" valign="middle" width="444" /> + </imageobject> + + </mediaobject> + </step> + </procedure> + + + </section> + + <section> + <title>WS-Security Consumer Checklist</title> + <para> + In order for the consumer to handle ws-security, the following items must be implemented: + </para> + <orderedlist> + <listitem> + <para> + The JBossWS configuration files must be configured + </para> + + </listitem> + <listitem> + <para> + The filter must be added to the portal's web.xml + </para> + + </listitem> + <listitem> + <para> + the enable wss feature must be check in the wsrp admin + </para> + + </listitem> + + </orderedlist> + <para> + The consumer will not properly handle ws-security unless all three items are correctly configured. + </para> + + </section> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Making_a_Portlet_Remotable"> + <title>Making a Portlet Remotable</title> + <note> + <para> + Only JSR-286 (Portlet 2.0) portlets can be made remotable as the mechanism to expose a portlet to WSRP relies on a JSR-286-only functionality. + </para> + + </note> + <para> + JBoss Enterprise Portal Platform does <emphasis role="bold">not</emphasis>, by default, expose local portlets for consumption by remote WSRP consumers. + </para> + <para> + In order to make a portlet remotely available, it must be made "remotable" by marking it as such in the associated <filename>portlet.xml</filename>. + </para> + <para> + A specific <code>org.gatein.pc.remotable container-runtime-option</code> is used to accomplish this. Setting its value to <code>true</code> makes the portlet available for remote consumption, while setting its value to <code>false</code> will not publish it remotely. + </para> + <para> + As specifying the remotable status for a portlet is optional, nothing need be done if portlets do not need to be remotely available. + </para> + <para> + In the following example, the "BasicPortlet" portlet is specified as being remotable. + </para> + +<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default255.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + It is also possible to specify that all the portlets declared within a given portlet application be remotable by default. + </para> + <para> + This is done by specifying the <code>container-runtime-option</code> at the <code>portlet-app</code> element level. Individual portlets can override that value to not be remotely exposed. + </para> + <para> + For example: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default256.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + This example defines two portlets. As the <code>org.gatein.pc.remotable container-runtime-option</code> is set to <code>true</code> at the <code>portlet-app</code> level, all portlets defined in this particular portlet application are exposed remotely by JBoss Enterprise Portal Platform's WSRP Producer. + </para> + <para> + It is possible to override this default behavior. Specifying a value for the <code>org.gatein.pc.remotable container-runtime-option</code> at the <code>portlet</code> level will take precedence over the default. + </para> + <para> + In the example above, the <literal>RemotelyExposedPortlet</literal> inherits the remotable status defined at the <code>portlet-app</code> level since it does not specify a value for the <code>org.gatein.pc.remotable container-runtime-option</code>. + </para> + <para> + The <literal>NotRemotelyExposedPortlet</literal>, however, overrides the default behavior and is not remotely exposed. + </para> + <note> + <title>Note</title> + <para> + Portlets are not remotely exposed if no top-level <code>org.gatein.pc.remotable container-runtime-option</code> value is set to <code>true</code>. + </para> + + </note> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_WSRP_portlets_from_a_remote_Consumer"> + <title>Consuming WSRP portlets from a remote Consumer</title> + <para> + Configuration is extremely variable between different WSRP Consumers. Most, however, require a specification of the URL for the Producer's WSDL definition. If the JBoss Enterprise Portal Platform Consumer is not being used, refer to the documentation for the Consumer that is in use for specific instructions. + </para> + <para> + For instructions on how to specify this URL in JBoss Enterprise Portal Platform, refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" />. + </para> + <para> + JBoss Enterprise Portal Platform's Producer is automatically set up when a portal instance is deployed with the WSRP service. + </para> + <para> + The WSDL file can be accessed at: + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consuming_WSRP_portlets_from_a_remote_Consumer-File_paths"> + <title>File paths:</title> + <varlistentry> + <term>WSRP 1.0:</term> + <listitem> + <para> + <filename>http://<replaceable>{hostname}</replaceable>:<replaceable>{port}</replaceable>/wsrp-producer/v1/MarkupService?wsdl</filename>. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>WSRP 2.0:</term> + <listitem> + <para> + <filename>http://<replaceable>{hostname}</replaceable>:<replaceable>{port}</replaceable>/wsrp-producer/v2/MarkupService?wsdl</filename>. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + <para> + The default hostname is <literal>localhost</literal> and the default port is <literal>8080</literal>. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets"> + <title>Consuming Remote WSRP Portlets</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Overview"> + <title>Overview</title> + <para> + To be able to consume WSRP portlets exposed by a remote producer, JBoss Enterprise Portal Platform's WSRP consumer must be configured to access that remote producer. + </para> + <para> + Access to a remote producer can be configured using the provided configuration portlet. Alternatively, it is also possible to configure access to remote producers using an XML descriptor. The configuration portlet is the recommended method. + </para> + <para> + Once a remote producer has been configured, the portlets that it exposes are then available in the Application Registry to be added to categories and then to pages. + </para> +  + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Configuring_a_Remote_Producer"> + <title>Configuring a Remote Producer</title> + <para> + Access to a remote producer needs to be defined so that portlets can be consumed within JBoss Enterprise Portal Platform. This section will show how to configure access to <emphasis role="bold">NetUnity</emphasis>'s public WSRP producer. + </para> + <para> + Firstly using the configuration portlet and then how the same result can be accomplished with a producer descriptor, though it is far easier to do so via the configuration portlet. + </para> + <important> + <title>Chunked Encoding</title> + <para> + Some WSRP producers, such as Oracle, do not support chunked encoding. If your producer does not support chunked encoding, it will not be able to properly connect to the producer. + </para> + <para> + This will manifest itself with the following error: + </para> + +<screen>Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service Unavailable. +</screen> + <para> + A workaround for this issue involves editing the <parameter>chunksize</parameter> setting in the <filename>standard-jaxws-client-config.xml</filename> file. + </para> + <para> + Refer to <ulink type="http" url="http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported">http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported</ulink> for more information. + </para> + + </important> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet"> + <title>The Configuration Portlet</title> + <para> + JBoss Enterprise Portal Platform provides a graphical portlet to assist with configuring access to, and other facets of, remote WSRP Producers. + </para> + <para> + It is available at: <ulink type="http" url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass..." />. + </para> + <para> + The portlet also is a group page for /platform/administrators + </para> + <para> + Although the Configuration Portlet is installed by default in JBoss Enterprise Portal Platform &VY;., installation instructions are included below should the portlet ever need to be re-installed: + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Installing_the_configuration_portlet"> + <title><emphasis role="bold">Installing the configuration portlet:</emphasis></title> + <step> + <para> + Log into the portal as an administrator and go to the Application Registry (Click <ulink url="http://localhost:8080/portal/private/classic/administration/registry">http://localhost:8080/portal/private/classic/administration/registry</ulink> if using the default installation). + </para> + + </step> + <step> + <para> + Add the WSRP Configuration portlet to the Administration category. If the Import Applications functionality is used, the WSRP Configuration portlet will be automatically added to the Administration category. + </para> + + </step> + <step> + <para> + Once the portlet is added to a category, it can be added to a page and used. It is recommended that it be added to the same page as the Application Registry (as other operations relating to WSRP and adding portlets to categories are somewhat related). Add the WSRP Configuration portlet to the page using the standard procedure. + </para> + + </step> + + </procedure> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet"> + <title><emphasis role="bold">Using the Configuration portlet</emphasis></title> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_init.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_init.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + This screen presents all the configured consumers associated with their status and possible actions on them. + </para> + <para> + A Consumer can be active or inactive. Activating a Consumer means that it is ready to act as a portlet provider. + </para> + <para> + Note also that a Consumer can be marked as requiring <emphasis>refresh</emphasis>, which means that the information held about it might not be up to date. Refreshing it from the remote Producer will update this information. + </para> + <para> + This can happen for several reasons: the service description for that remote Producer has not been fetched yet, the cached version has expired or modifications have been made to the configuration that could potentially invalidate it, thus requiring re-validation of the information. + </para> + <para> + To create a new Consumer: + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Using_the_Configuration_portlet-Creating_a_Consumer"> + <title><emphasis role="bold">Creating a Consumer</emphasis></title> + <step> + <para> + Type "<literal>netunity</literal>" into the "<emphasis role="bold">Create a consumer named:</emphasis>" field. + </para> + + </step> + <step> + <para> + Click on "<emphasis role="bold">Create consumer</emphasis>" to create a new Consumer called <literal>netunity</literal>. + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_create.png" format="PNG" scale="100" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_create.png" format="PNG" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + In the next form, set the cache expiration value to <parameter>300</parameter> seconds. + </para> + + </step> + <step> + <para> + Leave the default timeout value for web services (WS) operations. + </para> + + </step> + <step> + <para> + Enter the WSDL URL for the producer in the text field. + </para> + + </step> + <step> + <para> + Press the "Refresh & Save" button: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_wsdl.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_wsdl.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + <para> + This will retrieve the service description associated with the Producer which WSRP interface is described by the WSDL file found at the URL entered. + </para> + <para> + In this case, querying the service description will show that the Producer requires registration, that it requested three registration properties and that the current configuration is missing values for these properties: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_missing.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_missing.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + This particular producer requests simple <literal>Yes</literal> or <literal>No</literal> values for the three registration properties. + </para> + <para> + Enter <literal>No</literal>, <literal>Yes</literal> and <literal>No</literal> (in that order) for the values and then pressing the "Refresh & Save" button should result in: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_end.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_end.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <note> + <title>Values</title> + <para> + Unfortunately there is no automated way to learn about which possible values (if any) are expected by the remote Producer. Possible values may be indicated in the registration property description but this is not always the case. Refer to the specific Producer's documentation. + </para> + + </note> + <para> + The Consumer for the <literal>netunity</literal> Producer should now be available as a portlet provider and be ready to be used. + </para> + <para> + If the producer had required registration but did not require any registration properties, as is the case for the <literal>selfv2</literal> consumer (the consumer that accesses the portlets made remotely available by JBoss Enterprise Portal Platform's producer via WSRP 2), the following screen would have appeared after pressing the "Refresh & Save" button: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_refresh.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_refresh.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Using_XML"> + <title>Using XML</title> + <para> + Although using the WSRP Configuration portlet to configure Consumers is recommended, the WSRP component provides an alternative way to configure consumers. + </para> + <para> + This is done by editing the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/conf/gatein/wsrp-consumers-config.xml</filename> XML file. + </para> +  <note> + <title>XML Elements</title> + <para> + An XML Schema defining which elements are available to configure Consumers via XML can be found in <filename><replaceable>WSRP_PATH</replaceable>/lib/wsrp-integration-api-<replaceable>WSRP_VERSION</replaceable>.jar/xsd/gatein_wsrp_consumer_1_0.xsd </filename> + </para> + + </note> +  <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Using_XML-The_Consumer_Configuration_file"> + <title>The Consumer Configuration file</title> + <para> + It is important to understand how the XML Consumers configuration file is processed. It is read the first time the WSRP service starts and the associated information is then put under control of the JCR (Java Content Repository). + </para> + + </formalpara> + <para> + Subsequent launches of the WSRP service will use the JCR-stored information for all producers that are already known to JBoss Enterprise Portal Platform. More specifically, the <filename>wsrp-consumers-config.xml</filename> file is scanned for producer identifiers. Any identifier that is already known will be bypassed and the JCR information associated with this remote producer will be used. + </para> + <para> + The information defined at the XML level is only processed for producer definition for which no information is already present in the JCR. + </para> + <para> + Therefore, to delete a Producer configuration, the associated information in the database must be deleted (this can be accomplished using the configuration portlet as shown in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> ). + </para> + <para> + The associated information in <filename>wsrp-consumers-config.xml</filename> (if such information exists) must also be removed, otherwise the producer will be re-created the next time the WSRP is launched. + </para> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Required_Configuration_Information"> + <title>Required Configuration Information</title> + <para> + The following information needs to be provided to configure access to a remote Producer: + </para> + <orderedlist> + <listitem> + <para> + An identifier must be provided for the producer being configured so that it can be referred to later. This is done in the mandatory <literal>id</literal> attribute of the <literal><wsrp-producer></literal> element. + </para> + + </listitem> + <listitem> + <para> + JBoss Enterprise Portal Platform also needs to know about the remote Producer's endpoints to be able to connect to the remote web services and perform WSRP invocations. Use the <literal><endpoint-wsdl-url></literal> element to specify the URL for the WSDL description of the remote WSRP service. + </para> + + </listitem> + + </orderedlist> + <para> + Both the <literal>id</literal> attribute and <literal><endpoint-wsdl-url></literal> elements are required for a functional remote producer configuration. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Optional_Configuration"> + <title>Optional Configuration</title> + <para> + It is also possible to provide additional configuration, which, in some cases, might be important to establish a proper connection to the remote producer. + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Optional_Configuration-Optional_Configurations"> + <title>Optional Configurations</title> + <varlistentry> + <term>Caching</term> + <listitem> + <para> + To prevent unnecessary traffic between the local consumer and the remote producer, it is possible to cache some of the information sent by the producer (such as the list of offered portlets) for a given duration. + </para> + <para> + The rate at which the information is refreshed is defined by the <literal>expiration-cache</literal> attribute of the <literal><wsrp-producer></literal> element (in seconds). + </para> + <para> + For example; providing a value of <literal>120</literal> for expiration-cache means that the producer information will not be refreshed for 2 minutes after it has been accessed. If no value is provided, JBoss Enterprise Portal Platform will always access the remote producer regardless of whether the remote information has changed or not. + </para> + <para> + Since, in most instances, the information provided by the producer does not change often, use of this caching facility to minimize bandwidth usage is recommended. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>WS Timeout</term> + <listitem> + <para> + It is also possible to define a timeout after which WS operations are considered as failed. This is helpful to avoid blocking the WSRP service, as it waits on a service that does not answer. + </para> + <para> + Use the <literal>ws-timeout</literal> attribute of the <literal><wsrp-producer></literal> element to specify how many milliseconds the WSRP service will wait for a response from the remote producer before timing out. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Pre-registration information</term> + <listitem> + <para> + Some producers require consumers to register with them before authorizing them to access their offered portlets. If known, some registration information can be provided in the producer configuration beforehand, so that the consumer can register with the remote producer when required. + </para> + <note> + <para> + Only simple String properties are supported. It is not possible to configure complex registration data. However, this should be sufficient for most cases. + </para> + + </note> + <para> + This pre-registration configuration is done via the <literal><registration-data></literal> element. + </para> + <para> + If the remote producer does not require any registration properties, only an empty <literal><registration-data></literal> element need be provided, as JBoss Enterprise Portal Platform can generate the mandatory information. + </para> + <para> + Values for the registration properties required by the remote producer can be provided via <literal><property></literal> elements. Refer to the example below for more details. + </para> + <para> + Additionally, the default consumer name automatically provided by JBoss Enterprise Portal Platform can be overridden via the <literal><consumer-name></literal> element. When providing a consumer name, please remember that it should uniquely identify your consumer. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Examples"> + <title>Examples</title> + <para> + This is the configuration of the <literal>selfv1</literal> and <literal>selfv2</literal> consumers as found in <filename>default-wsrp.xml</filename> with a cache expiring every 500 seconds and with a 50 second timeout for web service operations: + </para> + <note> + <para> + This file contains the default configuration and should not need to be edited. If modifications are required, the recommended practice is to follow the procedure detailed in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet" />. + </para> + + </note> + +<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default258.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + This is an example of a WSRP descriptor with registration data and cache expiring every minute: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default259.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Adding_remote_portlets_to_categories"> + <title>Adding remote portlets to categories</title> + <para> + Clicking on the Portlet link in the Application Registry will now show the remote portlets in the <emphasis role="bold">REMOTE</emphasis> tab in the left column: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/remote_portlets.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/remote_portlets.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + These portlets are available to be used as regular portlets: they can be used in categories and added to pages. Using the Import Applications functionality will also automatically import them into categories based on the keywords they define. + </para> + <para> + More specifically, to add a <emphasis>WSRP</emphasis> portlet to a category, select <literal>wsrp</literal> in the Application Type drop-down menu: + </para> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/WSRP/remote_portlets_category.png" format="PNG" scalefit="1" valign="middle" /> + </imageobject> + + </mediaobject> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consumers_Maintenance"> + <title>Consumers Maintenance</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Modifying_a_Currently_Held_Registration"> + <title>Modifying a Currently Held Registration</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_for_Service_Upgrade"> + <title>Registration Modification for Service Upgrade</title> + <para> + Producers often offer several levels of service depending on consumers' subscription levels (for example). This is implemented at the WSRP level with the registration concept: producers can assert which level of service to provide to consumers based on the values of given registration properties. + </para> + <para> + There may also be cases where the registration information has changed and must be updated. For example, the producer required you to provide a valid email and the previous email address is not valid anymore and needs to be updated. + </para> + <para> + Therefore at times it may be necessary to modify the registration that sets the service agreement between a consumer and a producer. + </para> + <para> + For example; the producer requiring an email that was configured in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> . In that case the producer was requiring registration and required a value to be provided for the <literal>email</literal> property. + </para> + <para> + To update the email address that was provided, the remote producer must be informed that some registration data has been modified. + </para> + <para> + The following procedure assumes access to the producer has been configured as previously described. + </para> + <procedure> + <step> + <para> + Go to the configuration screen for the <literal>self</literal> producer and change the value of <literal>email</literal> to <literal>foo(a)example.com</literal> instead of <literal>example(a)example.com</literal>: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_start.png" format="PNG" scale="100" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_start.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + Click on "<emphasis role="bold">Update properties</emphasis>" to save the change. A "<emphasis role="bold">Modify registration</emphasis>" button should now appear to let you send this new data to the remote producer: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_modify.png" format="PNG" scale="100" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_modify.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + Click on <emphasis role="bold">Modify registration</emphasis> and, if the updated registration details have been accepted by the remote producer the following should appear: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_end.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_end.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error"> + <title>Registration Modification on Producer Error</title> + <para> + If a Producer administrator changes the requirements for registered consumers, invoking operations on the producer may fail with an <exceptionname>OperationFailedFault</exceptionname>. JBoss Enterprise Portal Platform will attempt to assist in these cases. + </para> + <para> + This section will discuss an example using the <literal>self</literal> producer. + </para> + <para> + Assuming that the registration requires a valid value for an <literal>email</literal> registration property (as has been shown) the configuration screen for this producer should show: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_self.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_self.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + If the administrator of the producer now requires an additional value to be provided for a <literal>name</literal> registration property operations with this producer will fail. + </para> + <para> + If a registration modification is required, go to the configuration screen for this remote producer and refresh the information held by the consumer by pressing "<emphasis role="bold">Refresh & Save</emphasis>": + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_self.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_self.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + The configuration screen now shows the currently held registration information and the expected information from the producer. + </para> + <para> + Enter a value for the <literal>name</literal> property and then click on "<emphasis role="bold">Modify registration</emphasis>". If the producer accepts the new registration data, the following screen will appear: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_self_end.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_self_end.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <note> + <title><emphasis role="bold">JBoss Enterprise Portal Platform &VY; and WSRP 1 Exceptions</emphasis></title> + <para> + In WSRP 1, it can be difficult to ascertain what caused an <exceptionname> OperationFailedFault </exceptionname> as it is a generic exception returned by producers during a failed method invocation. + </para> + <para> + An <exceptionname>OperationFailedFault</exceptionname> failure can be caused by several different reasons, one of them being a request to modify the registration data. + </para> + <para> + In these instances examining the log files may assist in gathering more information about the problem. + </para> + <para> + WSRP 2 introduces an exception that is specific to a request to modify registrations which reduces the ambiguity that currently exists. + </para> + + </note> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Consumer_Operations"> + <title>Consumer Operations</title> + <para> + Several operations are available from the consumer list view of the WSRP configuration portlet: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/consumer_operations.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/consumer_operations.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + The available operations are: + </para> + <variablelist> + <varlistentry> + <term>Configure</term> + <listitem> + <para> + Displays the consumer details and allows user to edit them. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Refresh</term> + <listitem> + <para> + Forces the consumer to retrieve the service description from the remote producer to refresh the local information (such as offered portlets, registration information). + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Activate/Deactivate</term> + <listitem> + <para> + Activates or deactivates a consumer, governing whether it will be available to provide portlets and receive portlet invocations. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Register/De-register</term> + <listitem> + <para> + Registers or de-registers a consumer based on whether registration is required and/or acquired. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Delete</term> + <listitem> + <para> + Destroys the consumer, after de-registering it if it was registered. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functionalities_in_WSRP_2.0"> + <title><emphasis role="bold">Additional Functionalities in WSRP 2.0</emphasis></title> + <para> + In addition to those listed above, the WSRP 2.0 implementation in JBoss Enterprise Portal Platform &VY; also includes the following functions: + </para> + + </formalpara> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functions"> + <title>Additional Functions:</title> + <varlistentry> + <term>Export</term> + <listitem> + <para> + Exports some or all of the consumer's portlets to be able to later import them in a different context + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Import</term> + <listitem> + <para> + Imports some or all of previously exported portlets. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Importing_and_Exporting_Portlets"> + <title><emphasis role="bold">Importing and Exporting Portlets</emphasis></title> + <para> + Import and export are new functionalities added in WSRP 2. + </para> + <para> + Exporting a portlet allows a consumer to get an opaque representation of the portlet which can then be use by the corresponding import operation to reconstitute it. + </para> + <para> + This is mostly used in migration scenarios during batch operations. Since JBoss Enterprise Portal Platform does not currently support automated migration of portal data, the functionality provided as part of WSRP 2 is necessarily less complete than it could be with full portal support. + </para> + <para> + The import/export implementation in JBoss Enterprise Portal Platform allows users to export portlets from a given consumer and then import them back to replace existing portlets assigned to windows on pages by the previously exported portlets. + </para> + <procedure> + <title></title> + <step> + <para> + Click on the "<guilabel>Export</guilabel>" action for a given consumer to display the list of portlets currently made available by this specific consumer. An example list is shown below: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/export_portlet_list.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_portlet_list.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + Once portlets have been selected, they can be exported by clicking on the "<guilabel>Export</guilabel>" button. This makes them available for later import: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/export_done.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_done.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + The portlets can be re-imported directly by pressing the "<guilabel>Use for import</guilabel>" button or, on the Consumers list page, using the "<guilabel>Import</guilabel>" action for a given consumer. + </para> + <para> + The example below assumes that the second option has been used and that several sets of previously exported portlets are available to import from. After clicking the action link, a screen similar to the one below should appear: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/export_list.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_list.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + This screen presents the list of available exports with available operations for each. + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Importing_and_Exporting_Portlets-Operations"> + <title>Operations:</title> + <varlistentry> + <term>View</term> + <listitem> + <para> + Displays the export details as previously seen when the export was first performed. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Delete</term> + <listitem> + <para> + Deletes the selected export, asking you for confirmation first. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Use for import</term> + <listitem> + <para> + Selects the export to import portlets from. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </step> + <step> + <para> + Once you have selected an export to import from, you will see a screen similar to the one below: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_start.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_start.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + The screen displays the list of available exported portlets for the previously selected export. You can select which portlet you want to import by checking the checkbox next to its name. + </para> + + </step> + <step> + <para> + Select the content of which window the imported portlet will replace. This process is done in three steps: + </para> + <para> + This example assumes that you have the following page called <literal>page1</literal> which contains two windows called <literal>NetUnity WSRP 2 Interop - Cache Markup (remote)</literal> and <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal>, as shown below: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_original_page.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_original_page.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + In this example, we want to replace the content of the <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> with the content of the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> portlet that was previously exported. + </para> + <procedure> + <title></title> + <step> + <para> + Check the box next to the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> portlet name to indicate that you want to import its data. + </para> + + </step> + <step> + <para> + Select <literal>page1</literal> in the list of available pages. The screen will then refresh to display the list of available windows on that page, similar to the image below: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_selected_page.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_selected_page.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <note> + <title>Note</title> + <para> + At this point, you still need to select which window content you want to replace before being able to complete the import operation + </para> + + </note> + + </step> + <step> + <para> + Select the <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> window, which enables the "<guilabel>Import</guilabel>" button. This indicates that all the necessary data to perform the import is available. + </para> + + </step> + <step> + <para> + Click the "<guilabel>Import</guilabel>" button. A screen similar to the one below will appear: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_success.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_success.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + + </step> + <step> + <para> + The <literal>page1</literal> page should now show that the content of <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> window has been replaced by the content of the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> imported portlet and that the window has been renamed appropriately. + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_modified_page.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_modified_page.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Erasing_Local_Registration_Data"> + <title>Erasing Local Registration Data</title> + <para> + In rare cases, it may be necessary to erase the local data without being able to de-register first. + </para> + <para> + This can occur when a consumer is registered with a producer that has been modified by its administrator to not require registration any longer. + </para> + <para> + In this scenario, local registration information can be erased from the consumer to allow it to resume interacting with the remote producer. + </para> + <para> + To do this click on the "<emphasis role="bold">Erase local registration</emphasis>" button next to the registration context information on the consumer configuration screen: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/erase_registration.png" format="PNG" scale="80" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/erase_registration.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <warning> + <para> + This operation is dangerous as it can result in inability to interact with the remote producer if invoked when not required. The warning message below will be displayed before any data is erased. + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/erase_registration_warning.png" format="PNG" scale="100" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/erase_registration_warning.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </warning> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Configuring_the_WSRP_Producer"> + <title>Configuring the WSRP Producer</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Overview"> + <title>Overview</title> + <para> + The behavior of the Portal's WSRP Producer can be configured using the WSRP administration interface, (this is the recommended method), or by editing the <filename><replaceable>WSRP_PATH</replaceable>/lib/gatein.portal.component.wsrp-<replaceable><VERSION></replaceable>-epp-GA.jar/conf/wsrp-producer-config.xml</filename> file. + </para> + <para> + Several aspects can be modified with respect to whether registration is required for consumers to access the Producer's services. An XML Schema for the configuration format is available at <filename><replaceable>WSRP_PATH</replaceable>/lib/wsrp-integration-api-<replaceable>WSRP_VERSION</replaceable>.jar/xsd/gatein_wsrp_producer_1_0.xsd </filename>. + </para> + <para> + An alternative to editing the default <filename>wsrp-producer-config.xml</filename> file is to make a custom copy containing the required configuration options. + </para> + <para> + If a copy is used in place of the original, however, the <filename><replaceable>WSRP_PATH</replaceable>/02portal.war/WEB-INF/conf/wsrp/wsrp-configuration.xml</filename> <emphasis role="bold">must</emphasis> be updated to reference the custom file (this file defines the component <literal>WSRPServiceIntegration</literal> and contains a producer and consumer configuration location). + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Default_Configuration"> + <title>Default Configuration</title> + <para> + The default producer configuration requires that consumers register with it before providing access to its services. However it does not require any specific registration properties (excepting those mandated by the WSRP standard). + </para> + <para> + It does, however, require consumers to be registered before sending them a full service description. This means that the WSRP producer will not provide the list of offered portlets and other capabilities to unregistered consumers. + </para> + <para> + The producer also uses the default <classname>RegistrationPolicy</classname> paired with the default <classname>RegistrationPropertyValidator</classname>. + </para> + <para> + This allows users to customize how Portal's WSRP Producer decides whether a given registration property is valid or not (however property validators are discussed in greater detail in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration" /> ). + </para> + <para> + JBoss Enterprise Portal Platform provides a web interface to configure the producer's behavior. It can be accessed by clicking on the "<emphasis role="bold">Producer Configuration</emphasis>" tab of the "<emphasis role="bold">WSRP</emphasis>" page of the "<emphasis role="bold">admin</emphasis>" portal. + </para> + <para> + The default configuration should show: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/producer_default.png" format="PNG" scale="110" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_default.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + You can specify whether or not the producer will send the full service description to unregistered consumers, and, if it requires registration, which <literal>RegistrationPolicy</literal> to use (and, if needed, which <literal>RegistrationPropertyValidator</literal>), along with required registration property description for which consumers must provide acceptable values to successfully register. + </para> + <para> + WSDL URLs to access JBoss Enterprise Portal Platform's WSRP producer are now displayed in either in WSRP 1 or WSRP 2 mode. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration"> + <title>Registration Configuration</title> + <para> + In order to have consumers register with Portal's producer the Portal's behavior with respect to registration must be configured. + </para> + <para> + Registration is optional, as are registration properties. The producer can require registration without requiring consumers to pass any registration properties as is the case in the default configuration. + </para> + <para> + The following section discusses configuring a producer's registration behavior from a blank state: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/producer_blank.png" format="PNG" width="700" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_blank.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <procedure> + <step> + <para> + To allow unregistered consumers to see the list of offered portlets, leave the first checkbox ("<emphasis role="bold">Access to full service description requires consumers to be registered.</emphasis>") unchecked. + </para> + + </step> + <step> + <para> + To specify, however, that consumers will need to be registered to be able to interact with the producer, check the second box ("<emphasis role="bold">Requires registration. Modifying this information will trigger invalidation of consumer registrations."</emphasis>). + </para> + <para> + The screen will refresh and display: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/producer_registration.png" format="PNG" width="700" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_registration.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + The fully-qualified name for the <classname>RegistrationPolicy</classname> and <classname>RegistrationPropertyValidator</classname> can be specified here. The default values are acceptable. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior" /> for more information. + </para> + + </step> + <step> + <para> + To add a registration property called <literal>email</literal> click "<emphasis role="bold">Add property</emphasis>" and enter the appropriate information in the fields, providing a description for the registration property that can be used by consumers to determine its purpose: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/producer_email.png" format="PNG" width="700" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_email.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + Press "Save" to record the modifications. + </para> + + </step> + + </procedure> + + <note> + <para> + At this time, only String (<literal>xsd:string</literal>) properties are supported. + </para> + + </note> + <note> + <para> + If consumers are already registered with the producer, modifying the configuration of required registration information will trigger the invalidation of held registrations, requiring consumers to modify their registration before being able to access the producer again. The consumer side of that process is documented in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error" />. + </para> + + </note> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior"> + <title>Customization of Registration Handling Behavior</title> + <para> + Registration handling behavior can be customized by users to suit their Producer needs. This is done with an implementation of the <classname>RegistrationPolicy</classname> interface. + </para> + <para> + This interface defines methods that are called by Portal's Registration service so that decisions can be made appropriately. A default registration policy that provides basic behavior is provided and should be enough for most user needs. + </para> + <para> + While the default registration policy provides default behavior for most registration-related aspects, one aspect requires specific configuration: whether a given value for a registration property is acceptable by the WSRP Producer. + </para> + <para> + This is done by plugging a <classname>RegistrationPropertyValidator</classname> into the default registration policy. This allows users to define their own validation mechanism. + </para> + <para> + Refer to the <trademark class="trade">Javadoc</trademark> for <classname>org.gatein.registration.RegistrationPolicy</classname> and <classname>org.gatein.registration.policies.RegistrationPropertyValidator</classname> for more details on what is expected of each method. + </para> + <para> + A defined registration policy is required for the producer to be correctly configured. Do this by specifying the qualified class name of the registration policy. + </para> + <para> + As it is anticipated that most users will use the default registration policy, it is possible to provide the class name of a custom property validator instead to customize the default registration policy behavior. Note that property validators are only used by the default policy. + </para> + <note> + <para> + Since the policy or the validator are defined via their class name and dynamically loaded, it is important to ensure that the identified class is available to the application server. + </para> + <para> + One way to accomplish that is to deploy the policy implementation as a JAR file in the AS instance deploy directory. + </para> + <para> + Note also that, since both policies and validators are dynamically instantiated, they must provide a default, no-argument constructor. + </para> + + </note> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-WSRP_Validation_Mode"> + <title>WSRP Validation Mode</title> + <para> + The lack of conformance kit and the wording of the WSRP specification leaves room for differing interpretations, resulting in interoperability issues. It is therefore possible to encounter issues when using consumers from different vendors. + </para> + <para> + Experience of these issues has produced a way to relax the validation that the WSRP producer performs on the data provided by consumers to help with interoperability by accepting data that would normally be invalid. + </para> + <para> + Note that the our validation algorithm is only relaxed on aspects of the specification that are deemed harmless such as invalid language codes. + </para> + <para> + By default, the WSRP producer is configured in strict mode. If you experience issues with a given consumer, you may attempt to relax the validation mode. Un-checking the "Use strict WSRP compliance" checkbox on the Producer configuration screen to do this. + </para> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Removing_WSRP"> + <title>Removing WSRP</title> + <para> + If you are not going to use WSRP in your JBoss Enterprise Portal Platform instance, the WSRP configuration files may be left in place. They will not adversely affect your installation. + </para> + <para> + However, if you wish to completely remove WSRP from your portal installation, remove the <filename>gatein-wsrp-integration.ear</filename> file from your application server deploy directory. + </para> +  + </section> + + +</chapter> + Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/WSRP.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/WSRP.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/WSRP.xml 2011-11-25 00:43:12 UTC (rev 8139) @@ -1,2003 +1,1370 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> -%BOOK_ENTITIES; -]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP"> - <title>Web Services for Remote Portlets (WSRP)</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Introduction"> - <title>Introduction</title> - <para> - The Web Services for Remote Portlets (WSRP) specification defines a web service interface for accessing and interacting with interactive presentation-oriented web services. - </para> - <para> - It has been produced through the efforts of the Web Services for Remote Portlets (WSRP) OASIS Technical Committee. It is based on the requirements gathered and the proposals made to the committee. - </para> - <para> - Scenarios that motivate WSRP functionality include: - </para> + <!ENTITY % BOOK_ENTITIES SYSTEM "../Reference_Guide.ent"> + %BOOK_ENTITIES; + ]> +<chapter id="wsrp"> + <title>Web Services for Remote Portlets (WSRP)</title> + + <section> + <title>Introduction</title> + <para>The Web Services for Remote Portlets specification defines a web service interface for accessing and + interacting with interactive presentation-oriented web services. It has been produced through the efforts of + the Web Services for Remote Portlets (WSRP) OASIS Technical Committee. It is based on the requirements + gathered and on the concrete proposals made to the committee. + </para> + + <para>Scenarios that motivate WSRP functionality include: <itemizedlist> <listitem> - <para> - Content hosts, such as portal servers, providing Portlets as presentation-oriented web services that can be used by aggregation engines. - </para> - + <para>Content hosts, such as portal servers, providing Portlets as presentation-oriented web services + that can be used by aggregation engines. + </para> </listitem> - <listitem> - <para> - Aggregating frameworks, including portal servers, consuming presentation-oriented web services offered by content providers and integrating them into the framework. - </para> - + <listitem> + <para>Aggregating frameworks, including portal servers, consuming presentation-oriented web services + offered by content providers and integrating them into the framework. + </para> </listitem> + </itemizedlist> + </para> - </itemizedlist> - <para> - More information on WSRP can be found on the official <ulink url="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">website</ulink>. We suggest reading the <ulink url="http://www.oasis-open.org/committees/download.php/10539/wsrp-primer-1.0.html">primer</ulink> for a good, albeit technical, overview of WSRP. - </para> + <para>More information on WSRP can be found on the + <ulink url="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">official website for WSRP</ulink>. + We suggest reading the + <ulink url="http://www.oasis-open.org/committees/download.php/10539/wsrp-primer-1.0.html">primer</ulink> + for a good, albeit technical, overview of WSRP. + </para> + </section> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Level_of_Support"> - <title>Level of Support</title> - <para> - The WSRP Technical Committee defined <ulink url="http://www.oasis-open.org/committees/download.php/3073">WSRP Use Profiles</ulink> to help with WSRP interoperability. Terms defined in that document will be used in this section. - </para> - <para> - JBoss Enterprise Portal Platform provides a <emphasis>Simple</emphasis> level of support for the WSRP Producer, with the exception of out-of-band registration. In-band registration and persistent local state (which are defined at the <emphasis>Complex</emphasis> level) are supported. - </para> - <para> - JBoss Enterprise Portal Platform provides a <emphasis>Medium</emphasis> level of support for the Consumer, excepting HTML markup (as JBoss Enterprise Portal Platform itself does not handle other markup types). Explicit portlet cloning and the <literal>PortletManagement</literal> interface are supported. - </para> - <para> - The WSRP component has Level 1 Producer and Consumer caching. Cookie handling is supported properly on the Consumer. The Producer requires cookie initialization (as this improves interoperability with some consumers). - </para> - <para> - JBoss Enterprise Portal Platform does not support custom window states or modes, therefore neither does the WSRP component. It does, however, support CSS on both the Producer (although this is more a function of the portlets than an inherent Producer capability) and Consumer. - </para> - <para> - JBoss Enterprise Portal Platform &VY; includes implementations of WSRP 1.0 and 2.0. - </para> - <para> - All optional features in WSRP 2 are implemented in JBoss Enterprise Portal Platform &VY; except support for lifetimes and leasing support. - </para> - <note> - <para> - As of version &VZ; of Enterprise Portal Platform, WSRP is only activated and supported when deployed on JBoss Enterprise Application Server. - </para> + <section id="wsrp_support"> + <title>Level of support in JBoss Enterprise Portal Platform</title> + <para>The WSRP Technical Committee defined + <ulink url="http://www.oasis-open.org/committees/download.php/3073">WSRP Use Profiles</ulink> + to help with WSRP interoperability. We will refer to terms defined in that document in + this section. + </para> - </note> + <para>JBoss Enterprise Portal Platform provides a Simple level of support for our WSRP Producer except that out-of-band registration + is not currently handled. We support in-band registration and persistent local state (which are + defined at the Complex level). + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Deploying_WSRP"> - <title>Deploying WSRP</title> - <note> - <title>Notational Devices</title> - <para> - The following list of support files uses the following notational devices: - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Notations"> - <title>Notations:</title> - <varlistentry> - <term><replaceable>JBOSS_HOME</replaceable></term> - <listitem> - <para> - <replaceable>JBOSS_HOME</replaceable> refers to the directory that your instance of JBoss Enterprise Portal Platform has been extracted/installed to. For example: <filename>/home/<replaceable>USERNAME</replaceable>/jboss-epp-<replaceable><VERSION></replaceable>/</filename> - </para> + <para>On the Consumer side, JBoss Enterprise Portal Platform provides a Medium level of support for WSRP, except that we only handle + HTML markup (as JBoss Enterprise Portal Platform itself doesn't handle other markup types). We do support explicit portlet + cloning and we fully support the PortletManagement interface. + </para> - </listitem> + <para>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 + with some consumers). We don't support custom window states or modes, as JBoss Enterprise Portal Platform 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. + </para> - </varlistentry> - <varlistentry> - <term><replaceable>WSRP_PATH</replaceable></term> - <listitem> - <para> - The WSRP files referred to in this section are found in the <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear</filename> directory. - </para> - <para> - For ease of reference this path will be represented by: <replaceable>WSRP_PATH</replaceable>. - </para> + <para>While we provide a complete implementation of WSRP 1.0, we do need to go through the + <ulink url="http://www.oasis-open.org/committees/download.php/6018">Conformance statements</ulink> + and perform more interoperability testing (an area that needs to be better supported by the WSRP Technical + Committee and Community at large). + </para> - </listitem> + <para>JBoss Enterprise Portal Platform supports WSRP 2.0 with a complete implementation of the non-optional features. The only + features that we have not implemented is support for lifetimes and leasing + support. + </para> - </varlistentry> - <varlistentry> - <term><replaceable>WSRP_VERSION</replaceable></term> - <listitem> - <para> - <replaceable>WSRP_VERSION</replaceable> represents the version of the WSRP component in use. - </para> + <note> + <para>As of version &VY; of JBoss Enterprise Portal Platform, WSRP is only activated and supported + when JBoss Enterprise Portal Platform is deployed on JBoss Application Server. + </para> + </note> + </section> - </listitem> + <section> + <title>Deploying JBoss Enterprise Portal Platform's WSRP services</title> + <para> + JBoss Enterprise Portal Platform provides a complete support of WSRP 1.0 and 2.0 standard interfaces and offers both consumer and + producer services. Starting with version 2.1.0-GA of the component, WSRP is packaged as a JBoss Enterprise Portal Platform + extension and is now self-contained in an easy to install package named + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear</filename> + where + <filename>$JBOSS_PROFILE_HOME</filename> + refers to your JBoss AS profile directory (<filename>default</filename>, for instance). + </para> + <para> + The extension itself is composed of the following components, assuming + <code>$WSRP_VERSION</code> + (at the time of the writing, it was 2.1.0-GA) is the version of the WSRP component and + <code>$PORTAL_VERSION</code> + (at the time of the writing, it was &VY;) is the current JBoss Enterprise Portal Platform version: + <itemizedlist> + <listitem> + <para> + <filename>META-INF</filename> + contains files necessary for EAR packaging. The only file that is of interest from a user perspective + is + <filename>gatein-wsse-consumer.xml</filename> + which allows you to configure WS-Security support for the consumer. Please see the + <link linkend="wss_configuration">WSRP and WS-Security</link> section for more details. + </para> + </listitem> + <listitem> + <para> + <filename>extension-component-$PORTAL_VERSION.jar</filename>, which contains the components needed to + integrate the WSRP component into JBoss Enterprise Portal Platform. It also includes the default configuration files for + the WSRP producer and the default WSRP consumers. + </para> + </listitem> + <listitem> + <para> + <filename>extension-config-$PORTAL_VERSION.jar</filename>, which contains the configuration file + needed by the GateIn extension mechanism to properly register this EAR as an extension. + </para> + </listitem> + <listitem> + <para> + <filename>extension-war-$PORTAL_VERSION.war</filename>, which contains the configuration files + needed by the GateIn extension mechanism to properly setup the WSRP service. It includes + <filename>wsrp-configuration.xml</filename> + which, in particular, configures several options for the + <code>WSRPServiceIntegration</code> + component at the heart of the WSRP integration in JBoss Enterprise Portal Platform. + </para> + </listitem> + <listitem> + <para> + <filename>lib</filename>, which contains the different libraries needed by the WSRP service. + </para> + </listitem> + <listitem> + <para> + <filename>wsrp-admin-gui-$WSRP_VERSION.war</filename>, which contains the WSRP Configuration portlet + with which you can configure consumers to access remote servers and how the WSRP producer is + configured. + </para> + </listitem> + <listitem> + <para><filename>wsrp-producer-jb5wsss-$WSRP_VERSION.war</filename>, which contains the producer-side + support for WS-Security. The only file of interest from a user perspective is + <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for + the producer. Please see the <link linkend="wss_configuration">WSRP and WS-Security</link> section + for more details. + </para> + </listitem> + </itemizedlist> + </para> + <para> + If you're not going to use WSRP in JBoss Enterprise Portal Platform, it won't adversely affect your installation to leave it + as-is. Otherwise, you can just remove the + <filename>gatein-wsrp-integration.ear</filename> + file from your AS deploy directory. + </para> - </varlistentry> - <varlistentry> - <term><replaceable>PORTAL_VERSION</replaceable></term> - <listitem> - <para> - <replaceable>PORTAL_VERSION</replaceable> represents the version of JBoss Enterprise Portal Platform in use. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - - </note> + <section id="wsrp-ports"> + <title>Considerations to use WSRP when running JBoss Enterprise Portal Platform on a non-default port or hostname</title> <para> - Starting with version 2.1.0-GA of the component, WSRP is packaged as a JBoss Enterprise Portal Platform extension and is now self-contained in an easy to install package named <filename>gatein-wsrp-integration.ear</filename>, deployed directly in the <filename>deploy</filename> directory of your JBoss Application Server configuration directory. - </para> + JBoss WS (the web service stack that JBoss Enterprise Portal Platform uses) should take care of the details of updating the + port and host name used in WSDL. See the + <ulink url="http://community.jboss.org/wiki/JBossWS-UserGuide#Configuration">JBoss WS user guide on that + subject + </ulink> + for more details. + </para> <para> - The extension itself is composed of the following components: - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-WSRP_support_files"> - <title>WSRP support files</title> - <varlistentry> - <term><filename>META-INF/</filename></term> - <listitem> - <para> - This directory contains files necessary for EAR packaging. The only file that is of interest from a user perspective is <filename>gatein-wsse-consumer.xml</filename> which allows you to configure WS-Security support for the consumer. - </para> - <para> - Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> section for more details. - </para> + Of course, if you have modified you have modified the host name and port on which your server runs, you will + need to + update the configuration for the consumer used to consume JBoss Enterprise Portal Platform's 'self' producer. Please refer to + the + <xref linkend="consumer_configuration"/> + to learn how to do so. + </para> + </section> + </section> - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>extension-component-$PORTAL_VERSION.jar</filename></term> - <listitem> - <para> - This archive which contains the components needed to integrate the WSRP component into JBoss Enterprise Portal Platform. It also includes the default configuration files for the WSRP producer and the default WSRP consumers. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>extension-config-$PORTAL_VERSION.jar</filename></term> - <listitem> - <para> - This file contains the configuration file needed by the GateIn extension mechanism to properly register this EAR as an extension. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>extension-war-$PORTAL_VERSION.war</filename></term> - <listitem> - <para> - This file contains the configuration files needed by the GateIn extension mechanism to properly setup the WSRP service. It includes <filename>wsrp-configuration.xml</filename> which, in particular, configures several options for the <code> WSRPServiceIntegration </code> component at the heart of the WSRP integration in JBoss Enterprise Portal Platform. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>lib/</filename></term> - <listitem> - <para> - This directory contains the different libraries needed by the WSRP service. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>wsrp-admin-gui-$WSRP_VERSION.war</filename></term> - <listitem> - <para> - This file contains the WSRP Configuration portlet with which you can configure consumers to access remote servers and how the WSRP producer is configured. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>wsrp-producer-jb5wsss-$WSRP_VERSION.war</filename></term> - <listitem> - <para> - This file contains the producer-side support for WS-Security. The only file of interest from a user perspective is <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for the producer. - </para> - <para> - Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> for more details. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Non_default_Ports_or_Hostnames"> - <title>Non-default Ports or Hostnames</title> - <para> - JBoss WS (the web service stack that JBoss Enterprise Portal Platform uses) should update the port and host name used in WSDL. Refer to the JBoss WS <ulink url="http://community.jboss.org/wiki/JBossWS-UserGuide#Configuration">user guide</ulink> for more information. - </para> - <para> - If the host name and port on which the server runs have been modified, the configuration for the Consumer used to consume JBoss Enterprise Portal Platform's "self" Producer will need to be updated. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" /> for directions on how to do this. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Using_WSRP_with_SSL"> - <title>Using WSRP with SSL</title> - <para> - It is possible to use WSRP over SSL for secure exchange of data. Refer to these <ulink url="http://community.jboss.org/wiki/ConfiguringWSRPforuseoverSSL">instructions</ulink> for how to do this. - </para> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-WSRP_and_WS_Security"> + <section> + <title>Securing WSRP</title> + <section> + <title>Considerations to use WSRP with SSL</title> + <para>It is possible to use WSRP over SSL for secure exchange of data. Please refer to the + <ulink url="http://community.jboss.org/wiki/ConfiguringWSRPforuseoverSSL">instructions</ulink> + on how to do so from + <ulink url="http://community.jboss.org/wiki/GateIn">GateIn's wiki</ulink>. + </para> + </section> + <section> <title>WSRP and WS-Security</title> - <para> - Portlets may present different data or options depending on the currently authenticated user. For remote portlets, this means having to propagate the user credentials from the consumer back to the producer in a safe and secure manner. + <para>Portlets may present different data or options depending on the currently authenticated user. For remote + portlets, this means having to propagate the user credentials from the consumer back to the producer in + a safe and secure manner. The WSRP specification does not directly specify how this should be + accomplished, but delegates this work to the existing WS-Security standards. </para> - <para> - The WSRP specification does not directly specify how this should be accomplished, but delegates this work to the existing WS-Security standards. - </para> - <note> - <title>Web Container Compatibility</title> - <para> - WSRP and WS-Security is currently only supported on JBoss Enterprise Portal Platform when running on top of JBoss AS 5. - </para> - + <note> + <title>Web Container Compatibility</title> + <para>WSRP and WS-Security is currently only supported on JBoss Enterprise Portal Platform when running on top of JBoss + AS 5. + </para> </note> - <warning> - <title>Encryption</title> - <para> - <emphasis role="bold">The use of encryption is strongly recommended.</emphasis> - </para> - <para> - Credentials being sent between the consumer and producer should be encrypted or they will be sent in plain text and could be easily intercepted. - </para> - <para> - You can either configure WS-Security to encrypt and sign the SOAP messages being sent, or secure the transport layer by using an <literal>https</literal> endpoint. - </para> - <para> - Failure to encrypt the SOAP message or transport layer will result in the username and password being sent in plain text. - </para> - + <warning> + <title>Encryption</title> + <para>You will want to encrypt the credentials being sent between the consumer and producer, otherwise they + will be sent in plain text and could be easily intercepted. You can either configure WS-Security to + encrypt and sign the SOAP messages being sent, or secure the transport layer by using an https endpoint. + Failure to encrypt the soap message or transport layer will result in the username and password being + sent in plain text. <emphasis role="bold">Use of encryption is strongly recommended.</emphasis> + </para> </warning> - <important> - <title>Credentials</title> - <para> - When the consumer sends the user credentials to the producer, it is sending the credentials for the currently authenticated user in the consumer. This makes signing in to remote portlets transparent to end users, but also requires that the producer and consumer use the same credentials. - </para> - <para> - The username and password must be the same and valid on both servers. - </para> - <para> - The recommended approach for this situation would be to use a common LDAP configuration. Please see the User Guide at <ulink type="http" url="docs.redhat.com" /> for information on how to configure LDAP for use with JBoss Enterprise Portal Platform - </para> - + <important> + <title>Credentials</title> + <para>When the consumer sends the user credentials to the producer, it is sending the credentials for the + currently authenticated user in the consumer. This makes signing in to remote portlets transparent + to end users, but also requires that the producer and consumer use the same credentials. This means + that the username and password must be the same and valid on both servers. + </para> + <para>The recommended approach for this situation would be to use a common ldap configuration. Please + see the user guide on how to configure ldap for use with JBoss Enterprise Portal Platform + </para> </important> - <para> - This community Wiki <ulink url="http://community.jboss.org/wiki/GateInWSRPAndWebServiceSecurity">article</ulink>, also provides a step-by-step example on how to configure WSRP with WS-Security. + <para>The GateIn Wiki article, <ulink url="http://community.jboss.org/wiki/GateInWSRPAndWebServiceSecurity"> + GateIn WSRP and Web Service Security</ulink>, also provides a step-by-step example on how to configure + WSRP with WS-Security. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration"> - <title>WS-Security Configuration</title> - <para> - JBoss Enterprise Portal Platform uses <application>JBossWS Native</application> to handle ws-security. - </para> - <para> - Refer to the WS-Security section of the <ulink url="http://www.jboss.org/jbossas/docs/5-x">JBoss AS 5 Administration and Configuration Guide </ulink> for in-depth configuration options. - </para> - <para> - Please note that since the consumer passes its credentials to the producer, the consumer will act at the wss client and the producer will act as the wss server. - </para> - <para> - The following are the JBossWS Native configuration files which need to be configure for WSRP: - </para> - <variablelist> - <title></title> - <varlistentry> - <term>gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</term> - <listitem> - <para> - BossWS configuration file for the consumer. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>gatein-wsrp-integration.ear/wsrp-producer-jb5wss.war/WEB-INF/conf/gatein-wsse-producer.xml</term> - <listitem> - <para> - JBossWS configuration file for the producer. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - + <section id="wss_configuration"> + <title>WS-Security Configuration</title> + <para>JBoss Enterprise Portal Platform uses JBossWS Native to handle ws-security. Please see the WS-Security section of the + <ulink url="http://www.jboss.org/jbossas/docs/5-x">JBoss AS 5 Administration and Configuration Guide + </ulink> for indepth configuration options. Please note that since the consumer passes its credentials + to the producer, the consumer will act at the wss client and the producer will act as the wss server. + </para> + <para> The following are the JBossWS Native configuration files which need to be configure for WSRP: + </para> + <itemizedlist> + <listitem> + <para> + <filename>gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</filename>: JBossWS + configuration file for the consumer. + </para> + </listitem> + <listitem> + <para> + <filename>gatein-wsrp-integration.ear/wsrp-producer-jb5wss.war/WEB-INF/conf/gatein-wsse-producer.xml + </filename>: JBossWS configuration file for the producer. + </para> + </listitem> + </itemizedlist> </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Producer_Configuration"> - <title>WS-Security Producer Configuration</title> - <para> - Other than the JBossWS configuration file mention above, no other configuration changes should be necessary for the producer. - </para> - + <section> + <title>WS-Security Producer Configuration</title> + <para> + Other than the JBossWS configuration file mention above, no other configuration changes should be necessary + for the producer. + </para> </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Consumer_Configuration"> - <title>WS-Security Consumer Configuration</title> - <para> - The consumer requires some changes before it will function properly with WS-Security. - </para> - <para> - The consumer needs access to the current servlet request since this is used to retrieve the currently authenticated user. In order to access this information, the consumer needs a special servlet-filter added to the portal. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-WS_Security_Consumer_Configuration-Add_the_servlet_filter"> - <title>Add the servlet-filter</title> - <step> - <para> - Open <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add the following: - </para> - -<programlisting role="XML"> - <filter> - <filter-name>ServletAccessFilter</filter-name> - <filter-class>org.gatein.wsrp.servlet.ServletAccessFilter</filter-class> - </filter> - <filter-mapping> - <filter-name>ServletAccessFilter</filter-name> - <url-pattern>/*</url-pattern> - </filter-mapping> + <section> + <title>WS-Security Consumer Configuration</title> + <para>The consumer requires a few changes before it will function properly with WS-Security. The consumer + needs access to the current servlet request since this is used to retrieve the currently authenticated + user. In order for the consumer to access this information, it needs a special servlet-filter added to + the portal. + </para> + <para>In <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> add the following information: + </para> +<programlisting role="XML"><![CDATA[ + <filter> + <filter-name>ServletAccessFilter</filter-name> + <filter-class>org.gatein.wsrp.servlet.ServletAccessFilter</filter-class> + </filter> + <filter-mapping> + <filter-name>ServletAccessFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping>]]> </programlisting> + <para> + Finally, in the WSRP Configuration portlet, in the consumer configuration options, you will need to check the 'Enable WS Security' checkbox: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_wss_selected.png" format="PNG" align="center" valign="middle" scalefit="1"/> + </imageobject> + </mediaobject> + </section> + <section> + <title>WS-Security Consumer Checklist</title> + <para> + In order for the consumer to handle ws-security, the following steps must be completed properly + </para> + <itemizedlist> + <listitem> + <para>The JBossWS configuration files must be configured</para> + </listitem> + <listitem> + <para>The filter must be added to the portal's web.xml</para> + </listitem> + <listitem> + <para>the enable wss feature must be check in the wsrp admin</para> + </listitem> + </itemizedlist> + <para>The consumer will not properly handle ws-security unless all 3 are properly configured</para> + </section> + </section> + </section> - </step> - <step> - <para> - Check the <guilabel>Enable WS Security</guilabel> checkbox in the consumer configuration options of the WSRP Configuration portlet - </para> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/WSRP/config_wss_selected.png" format="PNG" scalefit="1" valign="middle" width="444" /> - </imageobject> + <section> + <title>Making a portlet remotable</title> + <important> + <para> + Only JSR-286 (Portlet 2.0) portlets can be made remotable as the mechanism to expose a portlet to WSRP + relies on a JSR-286-only functionality. + </para> + </important> + <para>JBoss Enterprise Portal Platform does + <emphasis role="bold">NOT</emphasis>, by default, expose local portlets for consumption + by remote WSRP consumers. In order to make a portlet remotely available, it must be made "remotable" by marking + it as such in the associated + <filename>portlet.xml</filename>. This is accomplished by using a specific + <code>org.gatein.pc.remotable container-runtime-option</code>. Setting its value to + <code>true</code> + makes the portlet available for remote consumption, while setting its value to + <code>false</code> + will not publish it remotely. As specifying the remotable status for a portlet is optional, you do not need to + do anything if you don't need your portlet to be available remotely. + </para> + <para>In the following example, the "BasicPortlet" portlet is specified as being remotable. + </para> + <example> + <title>Example</title> + <para> + <programlisting><![CDATA[ +<?xml version="1.0" standalone="yes"?> +<portlet-app xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" + version="2.0"> +<portlet-app> + <portlet> + <portlet-name>BasicPortlet</portlet-name> - </mediaobject> - </step> - </procedure> - + ... - </section> - - <section> - <title>WS-Security Consumer Checklist</title> - <para> - In order for the consumer to handle ws-security, the following items must be implemented: - </para> - <orderedlist> - <listitem> - <para> - The JBossWS configuration files must be configured - </para> + <container-runtime-option> + <name>org.gatein.pc.remotable</name> + <value>true</value> + </container-runtime-option> + </portlet> +</portlet-app>]]></programlisting> + </para> - </listitem> - <listitem> - <para> - The filter must be added to the portal's web.xml - </para> + </example> + <para> + It is also possible to specify that all the portlets declared within a given portlet application to be + remotable by default. This is done by specifying the + <code> + container-runtime-option + </code> + at the + <code>portlet-app</code> + element level. Individual portlets can override that value to not be remotely exposed. Let's look at an + example: + </para> + <example> + <title>Example</title> + <para> + <programlisting><![CDATA[ +<?xml version="1.0" standalone="yes"?> +<portlet-app xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" + version="2.0"> +<portlet-app> - </listitem> - <listitem> - <para> - the enable wss feature must be check in the wsrp admin - </para> + <portlet> + <portlet-name>RemotelyExposedPortlet</portlet-name> + ... + </portlet> + <portlet> + <portlet-name>NotRemotelyExposedPortlet</portlet-name> + ... + <container-runtime-option> + <name>org.gatein.pc.remotable</name> + <value>false</value> + </container-runtime-option> + </portlet> - </listitem> + <container-runtime-option> + <name>org.gatein.pc.remotable</name> + <value>true</value> + </container-runtime-option> +</portlet-app>]]> + </programlisting> + </para> - </orderedlist> - <para> - The consumer will not properly handle ws-security unless all three items are correctly configured. - </para> + </example> - </section> + <para> + In the example above, we defined two portlets. The + <code>org.gatein.pc.remotable container-runtime-option</code> + being set to + <code>true</code> + at the + <code>portlet-app</code> + level, all portlets defined in this particular portlet application are exposed remotely by JBoss Enterprise Portal Platform's + WSRP + producer. + Note, however, that it is possible to override the default behavior: specifying a value for the + <code>org.gatein.pc.remotable container-runtime-option</code> + at the + <code>portlet</code> + level will take precedence over the default. In the example above, the + <varname>RemotelyExposedPortlet</varname> + inherits the remotable status defined at the + <code>portlet-app</code> + level since it does not specify a value for the<code>org.gatein.pc.remotable container-runtime-option</code>. + The<varname>NotRemotelyExposedPortlet</varname>, however, overrides the default behavior and is not remotely + exposed. Note that in the absence of a top-level + <code>org.gatein.pc.remotable container-runtime-option</code> + value set to<code>true</code>, portlets are NOT remotely exposed. + </para> + </section> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Making_a_Portlet_Remotable"> - <title>Making a Portlet Remotable</title> - <note> - <para> - Only JSR-286 (Portlet 2.0) portlets can be made remotable as the mechanism to expose a portlet to WSRP relies on a JSR-286-only functionality. - </para> + <section> + <title>Consuming JBoss Enterprise Portal Platform's WSRP portlets from a remote Consumer</title> + <para>WSRP Producers vary a lot as far as how they are configured. Most of them require that you specify + the URL for the Producer's WSDL definition. Please refer to the remote producer's documentation for specific + instructions. For instructions on how to do so in JBoss Enterprise Portal Platform, please refer to + <xref linkend="consumer_configuration"/>. + </para> + <para> + JBoss Enterprise Portal Platform's Producer is automatically set up when you deploy a portal instance with the WSRP service. + You can access the WSDL file at + <filename>http://{hostname}:{port}/wsrp-producer/v2/MarkupService?wsdl</filename>. If you wish to use only the + WSRP 1 compliant version of the producer, please use the WSDL file found at + <filename>http://{hostname}:{port}/wsrp-producer/v1/MarkupService?wsdl</filename>. + The default hostname is + <literal>localhost</literal> + and the default port is 8080. + </para> + </section> - </note> + <section id="consumer_configuration"> + <title>Consuming remote WSRP portlets in JBoss Enterprise Portal Platform</title> + <section> + <title>Overview</title> <para> - JBoss Enterprise Portal Platform does <emphasis role="bold">not</emphasis>, by default, expose local portlets for consumption by remote WSRP consumers. - </para> + To be able to consume WSRP portlets exposed by a remote producer, JBoss Enterprise Portal Platform's WSRP consumer needs to + know how to access that remote producer. One can configure access to a remote producer using the provided + configuration portlet. Alternatively, it is also possible to configure access to remote producers using an + XML descriptor, though it is recommended (and easier) to do so via the configuration portlet. + </para> <para> - In order to make a portlet remotely available, it must be made "remotable" by marking it as such in the associated <filename>portlet.xml</filename>. - </para> + Once a remote producer has been configured, the portlets that it exposes are then available in the + Application Registry to be added to categories and then to pages. + </para> + </section> + + <section id="consumer_gui"> + <title>Configuring a remote producer using the configuration portlet</title> <para> - A specific <code>org.gatein.pc.remotable container-runtime-option</code> is used to accomplish this. Setting its value to <code>true</code> makes the portlet available for remote consumption, while setting its value to <code>false</code> will not publish it remotely. - </para> - <para> - As specifying the remotable status for a portlet is optional, nothing need be done if portlets do not need to be remotely available. - </para> - <para> - In the following example, the "BasicPortlet" portlet is specified as being remotable. - </para> - -<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default255.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - It is also possible to specify that all the portlets declared within a given portlet application be remotable by default. - </para> - <para> - This is done by specifying the <code>container-runtime-option</code> at the <code>portlet-app</code> element level. Individual portlets can override that value to not be remotely exposed. - </para> - <para> - For example: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default256.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - This example defines two portlets. As the <code>org.gatein.pc.remotable container-runtime-option</code> is set to <code>true</code> at the <code>portlet-app</code> level, all portlets defined in this particular portlet application are exposed remotely by JBoss Enterprise Portal Platform's WSRP Producer. - </para> - <para> - It is possible to override this default behavior. Specifying a value for the <code>org.gatein.pc.remotable container-runtime-option</code> at the <code>portlet</code> level will take precedence over the default. - </para> - <para> - In the example above, the <literal>RemotelyExposedPortlet</literal> inherits the remotable status defined at the <code>portlet-app</code> level since it does not specify a value for the <code>org.gatein.pc.remotable container-runtime-option</code>. - </para> - <para> - The <literal>NotRemotelyExposedPortlet</literal>, however, overrides the default behavior and is not remotely exposed. - </para> + Let's work through the steps of defining access to a remote producer using the configuration portlet so that its portlets can be + consumed within JBoss Enterprise Portal Platform. We will configure access to NetUnity's public WSRP producer. + </para> + <note> - <title>Note</title> - <para> - Portlets are not remotely exposed if no top-level <code>org.gatein.pc.remotable container-runtime-option</code> value is set to <code>true</code>. + <para> + Some WSRP producers do not support chunked encoding that is activated by default by JBoss WS. If your + producer does not support chunked encoding, your consumer will not be able to properly connect to the + producer. This will manifest itself with the following error: + <code>Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service + Unavailable</code>. + Please see this GateIn's + <ulink url="http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported">wiki page + </ulink> + for more details. </para> + </note> - </note> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_WSRP_portlets_from_a_remote_Consumer"> - <title>Consuming WSRP portlets from a remote Consumer</title> <para> - Configuration is extremely variable between different WSRP Consumers. Most, however, require a specification of the URL for the Producer's WSDL definition. If the JBoss Enterprise Portal Platform Consumer is not being used, refer to the documentation for the Consumer that is in use for specific instructions. - </para> - <para> - For instructions on how to specify this URL in JBoss Enterprise Portal Platform, refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" />. - </para> - <para> - JBoss Enterprise Portal Platform's Producer is automatically set up when a portal instance is deployed with the WSRP service. - </para> - <para> - The WSDL file can be accessed at: - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consuming_WSRP_portlets_from_a_remote_Consumer-File_paths"> - <title>File paths:</title> - <varlistentry> - <term>WSRP 1.0:</term> - <listitem> - <para> - <filename>http://<replaceable>{hostname}</replaceable>:<replaceable>{port}</replaceable>/wsrp-producer/v1/MarkupService?wsdl</filename>. - </para> + JBoss Enterprise Portal Platform provides a portlet to configure access (among other functions) to remote WSRP Producers + grahically. Starting with &VY;, the WSRP configuration portlet is installed by default. You + can find it at + <ulink + url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass..."> + http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass... + </ulink> + </para> - </listitem> - - </varlistentry> - <varlistentry> - <term>WSRP 2.0:</term> - <listitem> - <para> - <filename>http://<replaceable>{hostname}</replaceable>:<replaceable>{port}</replaceable>/wsrp-producer/v2/MarkupService?wsdl</filename>. - </para> - - </listitem> - - </varlistentry> - - </variablelist> <para> - The default hostname is <literal>localhost</literal> and the default port is <literal>8080</literal>. - </para> + You should see a screen similar to: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_init.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + This screen presents all the configured Consumers associated with their status and possible actions on + them. A Consumer can be active or inactive. Activating a Consumer means that it is ready to act as a + portlet provider. Note also that a Consumer can be marked as requiring refresh meaning that the + information held about it might not be up to date and refreshing it from the remote Producer might be a + good idea. This can happen for several reasons: the service description for that remote Producer has not + been fetched yet, the cached version has expired or modifications have been made to the configuration + that could potentially invalidate it, thus requiring re-validation of the information. + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets"> - <title>Consuming Remote WSRP Portlets</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Overview"> - <title>Overview</title> - <para> - To be able to consume WSRP portlets exposed by a remote producer, JBoss Enterprise Portal Platform's WSRP consumer must be configured to access that remote producer. + <note> + <para> + The WSRP configuration didn't use to be installed by default in previous versions of JBoss Enterprise Portal Platform. + We include here the legacy instructions on how to install this portlet in case you ever need to + re-install it. </para> - <para> - Access to a remote producer can be configured using the provided configuration portlet. Alternatively, it is also possible to configure access to remote producers using an XML descriptor. The configuration portlet is the recommended method. - </para> - <para> - Once a remote producer has been configured, the portlets that it exposes are then available in the Application Registry to be added to categories and then to pages. - </para> -  - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Configuring_a_Remote_Producer"> - <title>Configuring a Remote Producer</title> - <para> - Access to a remote producer needs to be defined so that portlets can be consumed within JBoss Enterprise Portal Platform. This section will show how to configure access to <emphasis role="bold">NetUnity</emphasis>'s public WSRP producer. - </para> - <para> - Firstly using the configuration portlet and then how the same result can be accomplished with a producer descriptor, though it is far easier to do so via the configuration portlet. - </para> - <important> - <title>Chunked Encoding</title> - <para> - Some WSRP producers, such as Oracle, do not support chunked encoding. If your producer does not support chunked encoding, it will not be able to properly connect to the producer. - </para> - <para> - This will manifest itself with the following error: - </para> - -<screen>Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service Unavailable. -</screen> - <para> - A workaround for this issue involves editing the <parameter>chunksize</parameter> setting in the <filename>standard-jaxws-client-config.xml</filename> file. - </para> - <para> - Refer to <ulink type="http" url="http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported">http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported</ulink> for more information. - </para> - - </important> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet"> - <title>The Configuration Portlet</title> - <para> - JBoss Enterprise Portal Platform provides a graphical portlet to assist with configuring access to, and other facets of, remote WSRP Producers. - </para> - <para> - It is available at: <ulink type="http" url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass..." />. - </para> - <para> - The portlet also is a group page for /platform/administrators - </para> - <para> - Although the Configuration Portlet is installed by default in JBoss Enterprise Portal Platform &VY;., installation instructions are included below should the portlet ever need to be re-installed: - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Installing_the_configuration_portlet"> - <title><emphasis role="bold">Installing the configuration portlet:</emphasis></title> - <step> - <para> - Log into the portal as an administrator and go to the Application Registry (Click <ulink url="http://localhost:8080/portal/private/classic/administration/registry">http://localhost:8080/portal/private/classic/administration/registry</ulink> if using the default installation). - </para> - - </step> - <step> - <para> - Add the WSRP Configuration portlet to the Administration category. If the Import Applications functionality is used, the WSRP Configuration portlet will be automatically added to the Administration category. - </para> - - </step> - <step> - <para> - Once the portlet is added to a category, it can be added to a page and used. It is recommended that it be added to the same page as the Application Registry (as other operations relating to WSRP and adding portlets to categories are somewhat related). Add the WSRP Configuration portlet to the page using the standard procedure. - </para> - - </step> - - </procedure> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet"> - <title><emphasis role="bold">Using the Configuration portlet</emphasis></title> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_init.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_init.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - This screen presents all the configured consumers associated with their status and possible actions on them. - </para> - <para> - A Consumer can be active or inactive. Activating a Consumer means that it is ready to act as a portlet provider. - </para> - <para> - Note also that a Consumer can be marked as requiring <emphasis>refresh</emphasis>, which means that the information held about it might not be up to date. Refreshing it from the remote Producer will update this information. - </para> - <para> - This can happen for several reasons: the service description for that remote Producer has not been fetched yet, the cached version has expired or modifications have been made to the configuration that could potentially invalidate it, thus requiring re-validation of the information. - </para> - <para> - To create a new Consumer: - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Using_the_Configuration_portlet-Creating_a_Consumer"> - <title><emphasis role="bold">Creating a Consumer</emphasis></title> - <step> - <para> - Type "<literal>netunity</literal>" into the "<emphasis role="bold">Create a consumer named:</emphasis>" field. - </para> - - </step> - <step> - <para> - Click on "<emphasis role="bold">Create consumer</emphasis>" to create a new Consumer called <literal>netunity</literal>. - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_create.png" format="PNG" scale="100" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_create.png" format="PNG" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - In the next form, set the cache expiration value to <parameter>300</parameter> seconds. - </para> - - </step> - <step> - <para> - Leave the default timeout value for web services (WS) operations. - </para> - - </step> - <step> - <para> - Enter the WSDL URL for the producer in the text field. - </para> - - </step> - <step> - <para> - Press the "Refresh & Save" button: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_wsdl.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_wsdl.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - - </procedure> - - <para> - This will retrieve the service description associated with the Producer which WSRP interface is described by the WSDL file found at the URL entered. - </para> - <para> - In this case, querying the service description will show that the Producer requires registration, that it requested three registration properties and that the current configuration is missing values for these properties: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_missing.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_missing.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - This particular producer requests simple <literal>Yes</literal> or <literal>No</literal> values for the three registration properties. - </para> - <para> - Enter <literal>No</literal>, <literal>Yes</literal> and <literal>No</literal> (in that order) for the values and then pressing the "Refresh & Save" button should result in: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_end.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_end.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <note> - <title>Values</title> - <para> - Unfortunately there is no automated way to learn about which possible values (if any) are expected by the remote Producer. Possible values may be indicated in the registration property description but this is not always the case. Refer to the specific Producer's documentation. - </para> - - </note> - <para> - The Consumer for the <literal>netunity</literal> Producer should now be available as a portlet provider and be ready to be used. - </para> - <para> - If the producer had required registration but did not require any registration properties, as is the case for the <literal>selfv2</literal> consumer (the consumer that accesses the portlets made remotely available by JBoss Enterprise Portal Platform's producer via WSRP 2), the following screen would have appeared after pressing the "Refresh & Save" button: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_refresh.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_refresh.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Using_XML"> - <title>Using XML</title> - <para> - Although using the WSRP Configuration portlet to configure Consumers is recommended, the WSRP component provides an alternative way to configure consumers. - </para> - <para> - This is done by editing the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/conf/gatein/wsrp-consumers-config.xml</filename> XML file. - </para> -  <note> - <title>XML Elements</title> - <para> - An XML Schema defining which elements are available to configure Consumers via XML can be found in <filename><replaceable>WSRP_PATH</replaceable>/lib/wsrp-integration-api-<replaceable>WSRP_VERSION</replaceable>.jar/xsd/gatein_wsrp_consumer_1_0.xsd </filename> - </para> - - </note> -  <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Using_XML-The_Consumer_Configuration_file"> - <title>The Consumer Configuration file</title> - <para> - It is important to understand how the XML Consumers configuration file is processed. It is read the first time the WSRP service starts and the associated information is then put under control of the JCR (Java Content Repository). - </para> - - </formalpara> - <para> - Subsequent launches of the WSRP service will use the JCR-stored information for all producers that are already known to JBoss Enterprise Portal Platform. More specifically, the <filename>wsrp-consumers-config.xml</filename> file is scanned for producer identifiers. Any identifier that is already known will be bypassed and the JCR information associated with this remote producer will be used. - </para> - <para> - The information defined at the XML level is only processed for producer definition for which no information is already present in the JCR. - </para> - <para> - Therefore, to delete a Producer configuration, the associated information in the database must be deleted (this can be accomplished using the configuration portlet as shown in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> ). - </para> - <para> - The associated information in <filename>wsrp-consumers-config.xml</filename> (if such information exists) must also be removed, otherwise the producer will be re-created the next time the WSRP is launched. - </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Required_Configuration_Information"> - <title>Required Configuration Information</title> - <para> - The following information needs to be provided to configure access to a remote Producer: - </para> - <orderedlist> - <listitem> - <para> - An identifier must be provided for the producer being configured so that it can be referred to later. This is done in the mandatory <literal>id</literal> attribute of the <literal><wsrp-producer></literal> element. - </para> - - </listitem> - <listitem> - <para> - JBoss Enterprise Portal Platform also needs to know about the remote Producer's endpoints to be able to connect to the remote web services and perform WSRP invocations. Use the <literal><endpoint-wsdl-url></literal> element to specify the URL for the WSDL description of the remote WSRP service. - </para> - - </listitem> - - </orderedlist> - <para> - Both the <literal>id</literal> attribute and <literal><endpoint-wsdl-url></literal> elements are required for a functional remote producer configuration. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Optional_Configuration"> - <title>Optional Configuration</title> - <para> - It is also possible to provide additional configuration, which, in some cases, might be important to establish a proper connection to the remote producer. - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Optional_Configuration-Optional_Configurations"> - <title>Optional Configurations</title> - <varlistentry> - <term>Caching</term> - <listitem> - <para> - To prevent unnecessary traffic between the local consumer and the remote producer, it is possible to cache some of the information sent by the producer (such as the list of offered portlets) for a given duration. - </para> - <para> - The rate at which the information is refreshed is defined by the <literal>expiration-cache</literal> attribute of the <literal><wsrp-producer></literal> element (in seconds). - </para> - <para> - For example; providing a value of <literal>120</literal> for expiration-cache means that the producer information will not be refreshed for 2 minutes after it has been accessed. If no value is provided, JBoss Enterprise Portal Platform will always access the remote producer regardless of whether the remote information has changed or not. - </para> - <para> - Since, in most instances, the information provided by the producer does not change often, use of this caching facility to minimize bandwidth usage is recommended. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>WS Timeout</term> - <listitem> - <para> - It is also possible to define a timeout after which WS operations are considered as failed. This is helpful to avoid blocking the WSRP service, as it waits on a service that does not answer. - </para> - <para> - Use the <literal>ws-timeout</literal> attribute of the <literal><wsrp-producer></literal> element to specify how many milliseconds the WSRP service will wait for a response from the remote producer before timing out. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Pre-registration information</term> - <listitem> - <para> - Some producers require consumers to register with them before authorizing them to access their offered portlets. If known, some registration information can be provided in the producer configuration beforehand, so that the consumer can register with the remote producer when required. - </para> - <note> - <para> - Only simple String properties are supported. It is not possible to configure complex registration data. However, this should be sufficient for most cases. - </para> - - </note> - <para> - This pre-registration configuration is done via the <literal><registration-data></literal> element. - </para> - <para> - If the remote producer does not require any registration properties, only an empty <literal><registration-data></literal> element need be provided, as JBoss Enterprise Portal Platform can generate the mandatory information. - </para> - <para> - Values for the registration properties required by the remote producer can be provided via <literal><property></literal> elements. Refer to the example below for more details. - </para> - <para> - Additionally, the default consumer name automatically provided by JBoss Enterprise Portal Platform can be overridden via the <literal><consumer-name></literal> element. When providing a consumer name, please remember that it should uniquely identify your consumer. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Examples"> - <title>Examples</title> - <para> - This is the configuration of the <literal>selfv1</literal> and <literal>selfv2</literal> consumers as found in <filename>default-wsrp.xml</filename> with a cache expiring every 500 seconds and with a 50 second timeout for web service operations: - </para> - <note> - <para> - This file contains the default configuration and should not need to be edited. If modifications are required, the recommended practice is to follow the procedure detailed in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet" />. - </para> - - </note> - -<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default258.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - This is an example of a WSRP descriptor with registration data and cache expiring every minute: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default259.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Adding_remote_portlets_to_categories"> - <title>Adding remote portlets to categories</title> - <para> - Clicking on the Portlet link in the Application Registry will now show the remote portlets in the <emphasis role="bold">REMOTE</emphasis> tab in the left column: + Now that the portlet is added to a category, it can be added to a page and used. We recommend adding + it to the same page as the Application Registry as operations relating to WSRP and adding portlets to + categories are somewhat related as we will see. Go ahead and add the WSRP Configuration portlet to the + page using the standard procedure. </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/remote_portlets.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/remote_portlets.png" format="PNG" width="444" /> - </imageobject> + </note> + <para> + Next, we create a new Consumer which we will call <literal>netunity</literal>. Type + "<literal>netunity</literal>" in + the "Create a consumer named:" field then click on "Create consumer": + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_create.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> </mediaobject> - <para> - These portlets are available to be used as regular portlets: they can be used in categories and added to pages. Using the Import Applications functionality will also automatically import them into categories based on the keywords they define. - </para> - <para> - More specifically, to add a <emphasis>WSRP</emphasis> portlet to a category, select <literal>wsrp</literal> in the Application Type drop-down menu: - </para> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/WSRP/remote_portlets_category.png" format="PNG" scalefit="1" valign="middle" /> - </imageobject> - + You should now see a form allowing you to enter/modify the information about the Consumer. + Set the cache expiration value to 300 seconds, leave the default timeout value for web services (WS) + operations and enter the WSDL URL for the producer in the text field + and press the "Refresh & Save" button: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_wsdl.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> </mediaobject> + This will retrieve the service description associated with the Producer which WSRP interface is described + by the WSDL file found at the URL you just entered. In our case, querying the service description will + allow us to learn that the Producer requires registration, requested three registration properties and that + we are missing values for these properties: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_missing.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + This particular producer requests simple + <literal>Yes</literal> + or + <literal>No</literal> + values for the three registration properties. Entering <literal>No</literal>, + <literal>Yes</literal> + and + <literal>No</literal> + (in that order) for the values and then pressing the "Refresh & Save" button should result in: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_end.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> - </section> - + <note> + <para>At this point, there is no automated way to learn about which possible values (if any) are + expected by the remote Producer. Sometimes, the possible values will be indicated in the + registration + property description but this is not always the case... Please refer to the specific Producer's + documentation. + </para> + </note> + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consumers_Maintenance"> - <title>Consumers Maintenance</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Modifying_a_Currently_Held_Registration"> - <title>Modifying a Currently Held Registration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_for_Service_Upgrade"> - <title>Registration Modification for Service Upgrade</title> - <para> - Producers often offer several levels of service depending on consumers' subscription levels (for example). This is implemented at the WSRP level with the registration concept: producers can assert which level of service to provide to consumers based on the values of given registration properties. - </para> - <para> - There may also be cases where the registration information has changed and must be updated. For example, the producer required you to provide a valid email and the previous email address is not valid anymore and needs to be updated. - </para> - <para> - Therefore at times it may be necessary to modify the registration that sets the service agreement between a consumer and a producer. - </para> - <para> - For example; the producer requiring an email that was configured in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> . In that case the producer was requiring registration and required a value to be provided for the <literal>email</literal> property. - </para> - <para> - To update the email address that was provided, the remote producer must be informed that some registration data has been modified. - </para> - <para> - The following procedure assumes access to the producer has been configured as previously described. - </para> - <procedure> - <step> - <para> - Go to the configuration screen for the <literal>self</literal> producer and change the value of <literal>email</literal> to <literal>foo(a)example.com</literal> instead of <literal>example(a)example.com</literal>: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_start.png" format="PNG" scale="100" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_start.png" format="PNG" width="444" /> - </imageobject> + <para> + If we had been dealing with a producer which required registration but didn't require any registration + properties, as is the case for the + <literal>selfv2</literal> + consumer (the consumer that accesses the portlets made remotely available by JBoss Enterprise Portal Platform's producer via + WSRP 2), we'd have seen something similar to, after pressing the "Refresh & Save" button: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_refresh.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + </para> + </section> - </mediaobject> + <section id="consumer_xml"> + <title>Configuring access to remote producers via XML</title> - </step> - <step> - <para> - Click on "<emphasis role="bold">Update properties</emphasis>" to save the change. A "<emphasis role="bold">Modify registration</emphasis>" button should now appear to let you send this new data to the remote producer: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_modify.png" format="PNG" scale="100" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_modify.png" format="PNG" width="444" /> - </imageobject> + <para>While we recommend you use the WSRP Configuration portlet to configure Consumers, we provide an + alternative way to configure consumers by adding an XML file called + <filename>wsrp-consumers-config.xml</filename> in the + <filename>$JBOSS_PROFILE_HOME/conf/gatein/</filename> directory. + <note> + <para>An XML Schema defining which elements are available to configure Consumers via XML can be found + in + <filename> + $JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/wsrp-integration-api-$WSRP_VERSION.jar/xsd/gatein_wsrp_consumer_1_0.xsd + </filename> + </para> + </note> + <important> + <para> + It is important to note that once the XML configuration file for consumers has been read upon + the WSRP service first start, the associated information is put under control of JCR (Java Content + Repository). Subsequent launches of the WSRP service will use the JCR-stored information and ignore + the content of the XML configuration file. + </para> - </mediaobject> +  + </important> + </para> - </step> - <step> - <para> - Click on <emphasis role="bold">Modify registration</emphasis> and, if the updated registration details have been accepted by the remote producer the following should appear: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_end.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_end.png" format="PNG" width="444" /> - </imageobject> + <section> + <title>Required configuration information</title> - </mediaobject> + <para>Let's now look at which information needs to be provided to configure access to a remote producer. + </para> - </step> + <para>First, we need to provide an identifier for the producer we are configuring so that we can refer to it + afterwards. This is accomplished via the mandatory + <literal>id</literal> + attribute of the + <literal><wsrp-producer></literal> + element. + </para> - </procedure> - + <para>JBoss Enterprise Portal Platform also needs to learn about the remote producer's endpoints to be able to connect to the + remote web services and perform WSRP invocations. This is accomplished by specifying the URL for the + WSDL description for the remote WSRP service, using the + <literal><endpoint-wsdl-url></literal> + element. + </para> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error"> - <title>Registration Modification on Producer Error</title> - <para> - If a Producer administrator changes the requirements for registered consumers, invoking operations on the producer may fail with an <exceptionname>OperationFailedFault</exceptionname>. JBoss Enterprise Portal Platform will attempt to assist in these cases. - </para> - <para> - This section will discuss an example using the <literal>self</literal> producer. - </para> - <para> - Assuming that the registration requires a valid value for an <literal>email</literal> registration property (as has been shown) the configuration screen for this producer should show: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_self.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_self.png" format="PNG" width="444" /> - </imageobject> + <para>Both the + <literal>id</literal> + attribute and + <literal><endpoint-wsdl-url></literal> + elements are required for a functional remote producer configuration. + </para> + </section> - </mediaobject> - <para> - If the administrator of the producer now requires an additional value to be provided for a <literal>name</literal> registration property operations with this producer will fail. - </para> - <para> - If a registration modification is required, go to the configuration screen for this remote producer and refresh the information held by the consumer by pressing "<emphasis role="bold">Refresh & Save</emphasis>": - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_self.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_self.png" format="PNG" width="444" /> - </imageobject> + <section> + <title>Optional configuration</title> + <para>It is also possible to provide addtional configuration, which, in some cases, might be important to + establish a proper connection to the remote producer. + </para> - </mediaobject> - <para> - The configuration screen now shows the currently held registration information and the expected information from the producer. - </para> - <para> - Enter a value for the <literal>name</literal> property and then click on "<emphasis role="bold">Modify registration</emphasis>". If the producer accepts the new registration data, the following screen will appear: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_self_end.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_self_end.png" format="PNG" width="444" /> - </imageobject> + <para>One such optional configuration concerns caching. To prevent useless roundtrips between the local + consumer and the remote producer, it is possible to cache some of the information sent by the producer + (such as the list of offered portlets) for a given duration. The rate at which the information is + refreshed is + defined by the + <literal>expiration-cache</literal> + attribute of the + <literal><wsrp-producer></literal> + element which specifies the refreshing period in seconds. For example, providing a value of 120 for + expiration-cache means that the producer information will not be refreshed for 2 minutes after it has + been somehow accessed. If no value is provided, JBoss Enterprise Portal Platform will always access the remote producer + regardless of whether the remote information has changed or not. Since, in most instances, the + information provided by the producer does not change often, we recommend that you use this caching + facility to minimize bandwidth usage. + </para> - </mediaobject> - <note> - <title><emphasis role="bold">JBoss Enterprise Portal Platform &VY; and WSRP 1 Exceptions</emphasis></title> - <para> - In WSRP 1, it can be difficult to ascertain what caused an <exceptionname> OperationFailedFault </exceptionname> as it is a generic exception returned by producers during a failed method invocation. - </para> - <para> - An <exceptionname>OperationFailedFault</exceptionname> failure can be caused by several different reasons, one of them being a request to modify the registration data. - </para> - <para> - In these instances examining the log files may assist in gathering more information about the problem. - </para> - <para> - WSRP 2 introduces an exception that is specific to a request to modify registrations which reduces the ambiguity that currently exists. - </para> + <para>It is also possible to define a timeout after which WS operations are considered as failed. This is + helpful to avoid blocking the WSRP service, waiting forever on the service that doesn't answer. Use the + <literal>ws-timeout</literal> + attribute of the + <literal><wsrp-producer></literal> + element to specify how many milliseconds the WSRP service will wait for a response from the remote + producer before timing out and giving up. + </para> - </note> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Consumer_Operations"> - <title>Consumer Operations</title> - <para> - Several operations are available from the consumer list view of the WSRP configuration portlet: + <para>Additionally, some producers require consumers to register with them before authorizing them to access + their offered portlets. If you know that information beforehand, you can provide the required + registration information in the producer configuration so that the consumer can register with the remote + producer when required. + <note> + <para>At this time, though, only simple String properties are supported and it is not possible to + configure complex registration data. This should, however, be sufficient for most cases. + </para> + </note> </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/consumer_operations.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/consumer_operations.png" format="PNG" width="444" /> - </imageobject> - </mediaobject> - <para> - The available operations are: + <para>Registration configuration is done via the + <literal><registration-data></literal> + element. Since JBoss Enterprise Portal Platform can generate the mandatory information for you, if the remote producer does + not require any registration properties, you only need to provide an empty + <literal><registration-data></literal> + element. Values for the registration properties + required by the remote producer can be provided via + <literal><property></literal> + elements. See the example below for more details. Additionally, you can override the default consumer + name automatically provided by JBoss Enterprise Portal Platform via the + <literal><consumer-name></literal> + element. If you choose to provide a consumer name, please remember that this should uniquely identify + your consumer. </para> - <variablelist> - <varlistentry> - <term>Configure</term> - <listitem> - <para> - Displays the consumer details and allows user to edit them. - </para> + </section> - </listitem> + <section> + <title>Examples</title> - </varlistentry> - <varlistentry> - <term>Refresh</term> - <listitem> - <para> - Forces the consumer to retrieve the service description from the remote producer to refresh the local information (such as offered portlets, registration information). - </para> + <para> + Here is the configuration of the + <literal>selfv1</literal> + and + <literal>selfv2</literal> + consumers as found in + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/extension-component-$WSRP_VERSION.jar/conf/wsrp-consumers-config.xml</filename> + with a cache expiring every 500 seconds and with a 50 second timeout for web service operations. + <note> + <para> + This file contains the default configuration and you shouldn't need to edit it. If you want to make + modifications to it, we recommend that you follow the procedure detailed in + <xref linkend="consumer_gui"/>. + </para> + </note> + </para> - </listitem> + <example> + <title>Example</title> + <para> + <programlisting><![CDATA[ +<?xml version='1.0' encoding='UTF-8' ?> +<deployments xmlns="http://www.gatein.org/xml/ns/gatein_wsrp_consumer_1_0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_wsrp_consumer_1_0 http://www.jboss.org/portal/xsd/gatein_wsrp_consumer_1_0.xsd"> + <deployment> + <wsrp-producer id="selfv1" expiration-cache="500" ws-timeout="50000"> + <endpoint-wsdl-url>http://localhost:8080/wsrp-producer/v1/MarkupService?wsdl</endpoint-wsdl-url> + <registration-data/> + </wsrp-producer> + </deployment> + <deployment> + <wsrp-producer id="selfv2" expiration-cache="500" ws-timeout="50000"> + <endpoint-wsdl-url>http://localhost:8080/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> + <registration-data/> + </wsrp-producer> + </deployment> +</deployments>]]> + </programlisting> + </para> - </varlistentry> - <varlistentry> - <term>Activate/Deactivate</term> - <listitem> - <para> - Activates or deactivates a consumer, governing whether it will be available to provide portlets and receive portlet invocations. - </para> + </example> - </listitem> + <para>Here is an example of a WSRP descriptor with registration data and cache expiring every minute: + </para> - </varlistentry> - <varlistentry> - <term>Register/De-register</term> - <listitem> - <para> - Registers or de-registers a consumer based on whether registration is required and/or acquired. - </para> + <example> + <title>Example</title> + <para> + <programlisting><![CDATA[ +<?xml version='1.0' encoding='UTF-8' ?> +<deployments xmlns="http://www.gatein.org/xml/ns/gatein_wsrp_consumer_1_0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_wsrp_consumer_1_0 http://www.jboss.org/portal/xsd/gatein_wsrp_consumer_1_0.xsd"> +<deployments> + <deployment> + <wsrp-producer id="AnotherProducer" expiration-cache="60"> + <endpoint-wsdl-url>http://example.com/producer/producer?WSDL</endpoint-wsdl-url> + <registration-data> + <property> + <name>property name</name> + <lang>en</lang> + <value>property value</value> + </property> + </registration-data> + </wsrp-producer> + </deployment> +</deployments>]]></programlisting> + </para> + </example> + </section> + </section> - </listitem> + <section> + <title>Adding remote portlets to categories</title> + <para> + If we go to the Application Registry and examine the available portlets by clicking on the + Portlet link, you will now be able to see remote portlets if you click on the REMOTE tab in the left + column: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/remote_portlets.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + </para> - </varlistentry> - <varlistentry> - <term>Delete</term> - <listitem> - <para> - Destroys the consumer, after de-registering it if it was registered. - </para> + <para> + These portlets are, of course, available to be used such as regular portlets: they can be used in + categories and added to pages. If you use the Import Applications functionality, they will also be + automatically imported in categories based on the keywords they define. + </para> - </listitem> + <para> + More specifically, if you want to add a WSRP portlet to a category, you can access these portlets by + selecting + <literal>wsrp</literal> + in the Application Type drop-down menu: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/remote_portlets_category.png" format="PNG" align="center" + valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + </para> + </section> + </section> - </varlistentry> + <section> + <title>Consumers maintenance</title> - </variablelist> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functionalities_in_WSRP_2.0"> - <title><emphasis role="bold">Additional Functionalities in WSRP 2.0</emphasis></title> - <para> - In addition to those listed above, the WSRP 2.0 implementation in JBoss Enterprise Portal Platform &VY; also includes the following functions: - </para> + <section> + <title>Modifying a currently held registration</title> - </formalpara> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functions"> - <title>Additional Functions:</title> - <varlistentry> - <term>Export</term> - <listitem> - <para> - Exports some or all of the consumer's portlets to be able to later import them in a different context - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Import</term> - <listitem> - <para> - Imports some or all of previously exported portlets. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Importing_and_Exporting_Portlets"> - <title><emphasis role="bold">Importing and Exporting Portlets</emphasis></title> - <para> - Import and export are new functionalities added in WSRP 2. - </para> - <para> - Exporting a portlet allows a consumer to get an opaque representation of the portlet which can then be use by the corresponding import operation to reconstitute it. - </para> - <para> - This is mostly used in migration scenarios during batch operations. Since JBoss Enterprise Portal Platform does not currently support automated migration of portal data, the functionality provided as part of WSRP 2 is necessarily less complete than it could be with full portal support. - </para> - <para> - The import/export implementation in JBoss Enterprise Portal Platform allows users to export portlets from a given consumer and then import them back to replace existing portlets assigned to windows on pages by the previously exported portlets. - </para> - <procedure> - <title></title> - <step> - <para> - Click on the "<guilabel>Export</guilabel>" action for a given consumer to display the list of portlets currently made available by this specific consumer. An example list is shown below: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/export_portlet_list.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_portlet_list.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - Once portlets have been selected, they can be exported by clicking on the "<guilabel>Export</guilabel>" button. This makes them available for later import: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/export_done.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_done.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - The portlets can be re-imported directly by pressing the "<guilabel>Use for import</guilabel>" button or, on the Consumers list page, using the "<guilabel>Import</guilabel>" action for a given consumer. - </para> - <para> - The example below assumes that the second option has been used and that several sets of previously exported portlets are available to import from. After clicking the action link, a screen similar to the one below should appear: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/export_list.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_list.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - This screen presents the list of available exports with available operations for each. - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Importing_and_Exporting_Portlets-Operations"> - <title>Operations:</title> - <varlistentry> - <term>View</term> - <listitem> - <para> - Displays the export details as previously seen when the export was first performed. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Delete</term> - <listitem> - <para> - Deletes the selected export, asking you for confirmation first. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Use for import</term> - <listitem> - <para> - Selects the export to import portlets from. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - - </step> - <step> - <para> - Once you have selected an export to import from, you will see a screen similar to the one below: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_start.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_start.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - The screen displays the list of available exported portlets for the previously selected export. You can select which portlet you want to import by checking the checkbox next to its name. - </para> - - </step> - <step> - <para> - Select the content of which window the imported portlet will replace. This process is done in three steps: - </para> - <para> - This example assumes that you have the following page called <literal>page1</literal> which contains two windows called <literal>NetUnity WSRP 2 Interop - Cache Markup (remote)</literal> and <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal>, as shown below: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_original_page.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_original_page.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - In this example, we want to replace the content of the <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> with the content of the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> portlet that was previously exported. - </para> - <procedure> - <title></title> - <step> - <para> - Check the box next to the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> portlet name to indicate that you want to import its data. - </para> - - </step> - <step> - <para> - Select <literal>page1</literal> in the list of available pages. The screen will then refresh to display the list of available windows on that page, similar to the image below: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_selected_page.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_selected_page.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <note> - <title>Note</title> - <para> - At this point, you still need to select which window content you want to replace before being able to complete the import operation - </para> - - </note> - - </step> - <step> - <para> - Select the <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> window, which enables the "<guilabel>Import</guilabel>" button. This indicates that all the necessary data to perform the import is available. - </para> - - </step> - <step> - <para> - Click the "<guilabel>Import</guilabel>" button. A screen similar to the one below will appear: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_success.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_success.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - - </procedure> - - - </step> - <step> - <para> - The <literal>page1</literal> page should now show that the content of <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> window has been replaced by the content of the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> imported portlet and that the window has been renamed appropriately. - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_modified_page.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_modified_page.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - - </procedure> - - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Erasing_Local_Registration_Data"> - <title>Erasing Local Registration Data</title> - <para> - In rare cases, it may be necessary to erase the local data without being able to de-register first. + <section> + <title>Registration modification for service upgrade</title> + <para> + Producers often offer several levels of service depending on consumers' subscription levels (for + example). This is implemented at the WSRP level with the registration concept: producers can assert which + level of service to provide to consumers based on the values of given registration properties. </para> - <para> - This can occur when a consumer is registered with a producer that has been modified by its administrator to not require registration any longer. + <para> + There might also be cases where you just want to update the registration information because it has + changed. For example, the producer required you to provide a valid email and the previously email + address is not valid anymore and needs to be updated. </para> - <para> - In this scenario, local registration information can be erased from the consumer to allow it to resume interacting with the remote producer. + <para> + It is therefore sometimes necessary to modify the registration that concretizes the service agreement + between a consumer and a producer. Let's take the example of a producer requiring a valid email (via an + <literal>email</literal> + registration property) as part of its required information that consumers need to provide to be properly + registered. </para> - <para> - To do this click on the "<emphasis role="bold">Erase local registration</emphasis>" button next to the registration context information on the consumer configuration screen: + <para> + Suppose now that we would like to update the email address that we provided to the remote producer when + we first registered. We will need to tell the producer that our registration data has been modified. + Let's see how to do this. Select the consumer for the remote producer in the available consumers list to + display its configuration. Assuming you want to change the email you registered with to + <literal>foo(a)example.com</literal>, change its value in the field for the + <literal>email</literal> + registration property: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_start.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + Now click on "Update properties" to save the change. A "Modify registration" button should now appear to + let you send this new data to the remote producer: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_modify.png" format="PNG" align="center" + valign="middle" scalefit="1"/> + </imageobject> + </mediaobject> + Click on this new button and, if everything went well and your updated registration has been accepted by + the remote producer, you should see something similar to: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_end.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/erase_registration.png" format="PNG" scale="80" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/erase_registration.png" format="PNG" width="444" /> - </imageobject> - </mediaobject> - <warning> - <para> - This operation is dangerous as it can result in inability to interact with the remote producer if invoked when not required. The warning message below will be displayed before any data is erased. - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/erase_registration_warning.png" format="PNG" scale="100" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/erase_registration_warning.png" format="PNG" width="444" /> - </imageobject> + </section> - </mediaobject> + <section id="reg_mod_error"> + <title>Registration modification on producer error</title> - </warning> + <para> + It can also happen that a producer administrator decided to change its requirement for registered + consumers. JBoss Enterprise Portal Platform will attempt to help you in this situation. Let's walk through an example using + the <literal>selfv2</literal> consumer. Let's assume that registration is requiring a valid value for an + <literal>email</literal> + registration property. If you go to the configuration screen for this consumer, you should see: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_self.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> - </section> - + Now suppose that the administrator of the producer now additionaly requires a value to be provided for a + <literal>name</literal> + registration property. We will actually see how to do perform this operation + in JBoss Enterprise Portal Platform when we examine how to configure JBoss Enterprise Portal Platform's producer in + <xref linkend="producer_config"/>. + Operations with this producer will now fail. If you suspect that a registration modification is required, + you should go to the configuration screen for this remote producer and refresh the information held by + the consumer by pressing "Refresh & Save": + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_self.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Configuring_the_WSRP_Producer"> - <title>Configuring the WSRP Producer</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Overview"> - <title>Overview</title> - <para> - The behavior of the Portal's WSRP Producer can be configured using the WSRP administration interface, (this is the recommended method), or by editing the <filename><replaceable>WSRP_PATH</replaceable>/lib/gatein.portal.component.wsrp-<replaceable><VERSION></replaceable>-epp-GA.jar/conf/wsrp-producer-config.xml</filename> file. - </para> - <para> - Several aspects can be modified with respect to whether registration is required for consumers to access the Producer's services. An XML Schema for the configuration format is available at <filename><replaceable>WSRP_PATH</replaceable>/lib/wsrp-integration-api-<replaceable>WSRP_VERSION</replaceable>.jar/xsd/gatein_wsrp_producer_1_0.xsd </filename>. - </para> - <para> - An alternative to editing the default <filename>wsrp-producer-config.xml</filename> file is to make a custom copy containing the required configuration options. - </para> - <para> - If a copy is used in place of the original, however, the <filename><replaceable>WSRP_PATH</replaceable>/02portal.war/WEB-INF/conf/wsrp/wsrp-configuration.xml</filename> <emphasis role="bold">must</emphasis> be updated to reference the custom file (this file defines the component <literal>WSRPServiceIntegration</literal> and contains a producer and consumer configuration location). - </para> + As you can see, the configuration screen now shows the currently held registration information and + the expected information from the producer. Enter a value for the + <literal>name</literal> + property + and then click on "Modify registration". If all went well and the producer accepted your new registration + data, you should see something similar to: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_self_end.png" format="PNG" align="center" + valign="middle" scalefit="1"/> + </imageobject> + </mediaobject> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Default_Configuration"> - <title>Default Configuration</title> - <para> - The default producer configuration requires that consumers register with it before providing access to its services. However it does not require any specific registration properties (excepting those mandated by the WSRP standard). + <note> + <para>WSRP 1 makes it rather difficult to ascertain for sure what caused an + <exceptionname>OperationFailedFault</exceptionname> + as it is the generic exception returned by + producers if something didn't quite happen as expected during a method invocation. This means that + <exceptionname>OperationFailedFault</exceptionname> + can be caused by several different reasons, one + of them being a request to modify the registration data. Please take a look at the log files to see + if you can gather more information as to what happened. WSRP 2 introduces an exception that is + specific to a request to modify registrations thus reducing the ambiguity that exists when using WSRP 1. + </para> + + </note> </para> - <para> - It does, however, require consumers to be registered before sending them a full service description. This means that the WSRP producer will not provide the list of offered portlets and other capabilities to unregistered consumers. - </para> - <para> - The producer also uses the default <classname>RegistrationPolicy</classname> paired with the default <classname>RegistrationPropertyValidator</classname>. - </para> - <para> - This allows users to customize how Portal's WSRP Producer decides whether a given registration property is valid or not (however property validators are discussed in greater detail in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration" /> ). - </para> - <para> - JBoss Enterprise Portal Platform provides a web interface to configure the producer's behavior. It can be accessed by clicking on the "<emphasis role="bold">Producer Configuration</emphasis>" tab of the "<emphasis role="bold">WSRP</emphasis>" page of the "<emphasis role="bold">admin</emphasis>" portal. - </para> - <para> - The default configuration should show: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/producer_default.png" format="PNG" scale="110" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_default.png" format="PNG" width="444" /> - </imageobject> + </section> + </section> + <section> + <title>Consumer operations</title> + <para> + Several operations are available from the consumer list view of the WSRP configuration portlet: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/consumer_operations.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> </mediaobject> - <para> - You can specify whether or not the producer will send the full service description to unregistered consumers, and, if it requires registration, which <literal>RegistrationPolicy</literal> to use (and, if needed, which <literal>RegistrationPropertyValidator</literal>), along with required registration property description for which consumers must provide acceptable values to successfully register. + </para> + <para> + The available operations are: + <itemizedlist> + <listitem> + <para>Configure: displays the consumer details and allows user to edit them</para> + </listitem> + <listitem> + <para>Refresh: forces the consumer to retrieve the service description from the remote producer to + refresh + the local information (offered portlets, registration information, etc.) + </para> + </listitem> + <listitem> + <para>Activate/Deactivate: activates/deactivates a consumer, governing whether it will be available to + provide portlets and receive portlet invocations + </para> + </listitem> + <listitem> + <para>Register/Deregister: registers/deregisters a consumer based on whether registration is required + and/or acquired + </para> + </listitem> + <listitem> + <para>Delete: destroys the consumer, after deregistering it if it was registered</para> + </listitem> + <listitem> + <para>Export: exports some or all of the consumer's portlets to be able to later import them in a + different context + </para> + </listitem> + <listitem> + <para>Import: imports some or all of previously exported portlets</para> + </listitem> + </itemizedlist> + </para> + <note> + <para> + Import/Export functionality is only available to WSRP 2 consumers of producers that support this optional + functionality. Import functionality is only available if portlets had previously been exported. </para> - <para> - WSDL URLs to access JBoss Enterprise Portal Platform's WSRP producer are now displayed in either in WSRP 1 or WSRP 2 mode. - </para> + </note> + </section> - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration"> - <title>Registration Configuration</title> - <para> - In order to have consumers register with Portal's producer the Portal's behavior with respect to registration must be configured. - </para> - <para> - Registration is optional, as are registration properties. The producer can require registration without requiring consumers to pass any registration properties as is the case in the default configuration. - </para> - <para> - The following section discusses configuring a producer's registration behavior from a blank state: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/producer_blank.png" format="PNG" width="700" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_blank.png" format="PNG" width="444" /> - </imageobject> + <section> + <title>Importing and exporting portlets</title> + <para>Import and export are new functionalities added in WSRP 2. Exporting a portlet allows a consumer to get + an opaque representation of the portlet which can then be use by the corresponding import operation to + reconstitute it. It is mostly used in migration scenarios during batch operations. Since JBoss Enterprise Portal Platform + does not currently support automated migration of portal data, the functionality that we provide as part of + WSRP 2 is necessarily less complete than it could be with full portal support. + </para> + <para>The import/export implementation in JBoss Enterprise Portal Platform (available since 3.1) allows users to export portlets + from a given consumer. + These portlets can then be used to replace existing content on pages. This is accomplished by assigning + previously exported portlets to replace the content displayed by windows on the portal's pages. Let us walk + through an example to make things clearer. + </para> + <para>Clicking on the "Export" action for a given consumer will display the list of portlets currently made + available by this specific consumer. An example of such a list is shown below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/export_portlet_list.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>Once portlets have been selected, they can be exported by clicking on the "Export" button thus making + them available for later import: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/export_done.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>You can re-import the portlets directly by pressing the "Use for import" button or, on the Consumers list + page, using the "Import" action for a given consumer. Let's assume that you used that second option and that + you currently have several available sets of previously exported portlets to import from. After clicking the + action link, you should see a screen similar to the one below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/export_list.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>As you can see this screen presents the list of available exports with available operations for each. + <itemizedlist> + <listitem> + <para>View: displays the export details as previously seen when the export was first performed</para> + </listitem> + <listitem> + <para>Delete: deletes the selected export, asking you for confirmation first</para> + </listitem> + <listitem> + <para>Use for import: selects the export to import portlets from</para> + </listitem> + </itemizedlist> + </para> + <para>Once you've selected an export to import from, you will see a screen similar to the one below:</para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_start.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>The screen displays the list of available exported portlets for the previously selected export. You can + select which portlet you want to import by checking the checkbox next to its name. Next, you need to select + the content of which window the imported portlet will replace. This process is done in three steps. Let's + assume in this example that you have the following page called + <literal>page1</literal> + and containing two windows called + <literal>NetUnity WSRP 2 Interop - Cache Markup (remote)</literal> + and + <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> + as shown below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_original_page.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>In this example, we want to replace the content of the + <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> + by the content of the + <literal>/ajaxPortlet.JSFAJAXPortlet</literal> + portlet that we previously exported. To do so, we will check the checkbox next to the + <literal>/ajaxPortlet.JSFAJAXPortlet</literal> + portlet name to indicate that we want to import its data and then select the + <literal>page1</literal> + in the list of available pages. The screen will then refresh to display the list of available windows on + that page, similar to the one seen below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_selected_page.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>Note that, at this point, we still need to select the window which content we want to replace before + being able to complete the import operation. Let's select the + <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> + window, at which point the "Import" button will become enabled, indicating that we now have all the + necessary data to perform the import. If all goes well, pressing that button should result in a screen + similar to the one below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_success.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>If you now take a look at the + <literal>page1</literal> + page, you should now see that the content + <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> + window has been replaced by the content of the + <literal>/ajaxPortlet.JSFAJAXPortlet</literal> + imported portlet and the window renamed appropriately: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_modified_page.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + </section> + <section> + <title>Erasing local registration data</title> + <para> + There are rare cases where it might be required to erase the local information without being able to + deregister first. This is the case when a consumer is registered with a producer that has been modified by + its administrator to not require registration anymore. If that ever was to happen (most likely, it won't), + you can erase the local registration information from the consumer so that it can resume interacting with + the remote producer. To do so, click on "Erase local registration" button next to the registration context + information on the consumer configuration screen: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/erase_registration.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para> + <emphasis>Warning:</emphasis> + This operation is dangerous as it can result in inability to interact with the remote producer if invoked + when not required. A warning screen will be displayed to give you a chance to change your mind: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/erase_registration_warning.png" format="PNG" align="center" + valign="middle"/> + </imageobject> + </mediaobject> + </section> + </section> + + <section id="producer_config"> + <title>Configuring JBoss Enterprise Portal Platform's WSRP Producer</title> + <section> + <title>Overview</title> + <para> + The preferred way to configure the behavior of Portal's WSRP Producer is via the WSRP configuration portlet. + Alternatively, it is possible to add an XML file called + <filename>wsrp-producer-config.xml</filename> + in the + <filename>$JBOSS_PROFILE_HOME/conf/gatein/</filename> + directory. + Several aspects can be modified with respects to whether registration is required for consumers to access + the Producer's services. + <note> + <para>An XML Schema defining which elements are available to configure Consumers via XML can be found + in + <filename> + $JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/wsrp-integration-api-$WSRP_VERSION.jar/xsd/gatein_wsrp_producer_1_0.xsd + </filename> + </para> + </note> + <important> + <para> + It is important to note that once the XML configuration file for the producer has been read upon + the WSRP service first start, the associated information is put under control of JCR (Java Content + Repository). Subsequent launches of the WSRP service will use the JCR-stored information and ignore + the content of the XML configuration file. + </para> + </important> + <note> + <para> + The default configuration file for the producer can be found at + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/extension-component-$WSRP_VERSION.jar/conf/wsrp-producer-config.xml</filename> + </para> + </note> + </para> + </section> + <section> + <title>Default configuration</title> + <para> + The default producer configuration is to require that consumers register with it before providing access its + services but does not require any specific registration properties (apart from what is mandated by the + WSRP standard). It does, however, require consumers to be registered before sending them a full service + description. This means that our WSRP producer will not provide the list of offered portlets and other + capabilities to unregistered consumers. The producer also uses the default + <classname>RegistrationPolicy</classname> + paired with the default + <classname>RegistrationPropertyValidator</classname>. We will look into property + validators in greater detail later in<xref linkend="registration-configuration"/>. Suffice to say for now + that this allows users to customize how Portal's WSRP Producer decides whether a given registration property + is valid or not. + </para> + <para> + JBoss Enterprise Portal Platform provides a web interface to configure the producer's behavior. You can access it + by clicking on the "Producer Configuration" tab of the "WSRP" page of the "admin" portal. Here's what you + should see with the default configuration: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/producer_default.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> </mediaobject> - <procedure> - <step> - <para> - To allow unregistered consumers to see the list of offered portlets, leave the first checkbox ("<emphasis role="bold">Access to full service description requires consumers to be registered.</emphasis>") unchecked. - </para> + As would be expected, you can specify whether or not the producer will send the full service description to + unregistered consumers, and, if it requires registration, which + <classname>RegistrationPolicy</classname> + to use (and, if needed, which + <classname>RegistrationPropertyValidator</classname>), along with required + registration property description for which consumers must provide acceptable values to successfully + register. + </para> + <para>New in JBoss Enterprise Portal Platform, we now display the WSDL URLs to access JBoss Enterprise Portal Platform's WSRP producer either in WSRP 1 + or WSRP 2 mode. + </para> + </section> - </step> - <step> - <para> - To specify, however, that consumers will need to be registered to be able to interact with the producer, check the second box ("<emphasis role="bold">Requires registration. Modifying this information will trigger invalidation of consumer registrations."</emphasis>). - </para> - <para> - The screen will refresh and display: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/producer_registration.png" format="PNG" width="700" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_registration.png" format="PNG" width="444" /> - </imageobject> + <section id="registration-configuration"> + <title>Registration configuration</title> + <para> + In order to require consumers to register with Portal's producer before interacting with it, you need to + configure Portal's behavior with respect to registration. Registration is optional, as are registration + properties. The producer can require registration without requiring consumers to pass any registration + properties as is the case in the default configuration. Let's configure our producer starting with a blank + state: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/producer_blank.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + We will allow unregistered consumers to see the list of offered portlets so we leave the first checkbox + ("Access to full service description requires consumers to be registered.") unchecked. We will, however, + specify that consumers will need to be registered to be able to interact with our producer. Check the second + checkbox ("Requires registration. Modifying this information will trigger invalidation of consumer + registrations."). The screen should now refresh and display: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/producer_registration.png" format="PNG" align="center" + valign="middle" scalefit="1"/> + </imageobject> + </mediaobject> + You can specify the fully-qualified name for your + <classname>RegistrationPolicy</classname> + and + <classname>RegistrationPropertyValidator</classname> + there. We will keep the default value. See + <xref linkend="custom_registration"/> + for more details. Let's add, however, a registration property called + <literal>email</literal>. Click "Add property" and enter the appropriate information in the fields, + providing a description for the registration property that can be used by consumers to figure out its + purpose: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/producer_email.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + Press "Save" to record your modifications. - </mediaobject> + <note> + <para>At this time, only String (xsd:string) properties are supported. If your application requires more + complex properties, please let us know. + </para> + </note> - </step> - <step> - <para> - The fully-qualified name for the <classname>RegistrationPolicy</classname> and <classname>RegistrationPropertyValidator</classname> can be specified here. The default values are acceptable. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior" /> for more information. - </para> + <note> + <para>If consumers are already registered with the producer, modifying the configuration of required + registration + information will trigger the invalidation of held registrations, requiring consumers to modify their + registration before being able to access the producer again. We saw the consumer side of that process + in + <xref linkend="reg_mod_error"/>. + </para> - </step> - <step> - <para> - To add a registration property called <literal>email</literal> click "<emphasis role="bold">Add property</emphasis>" and enter the appropriate information in the fields, providing a description for the registration property that can be used by consumers to determine its purpose: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/producer_email.png" format="PNG" width="700" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_email.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - Press "Save" to record the modifications. - </para> - - </step> - - </procedure> - - <note> - <para> - At this time, only String (<literal>xsd:string</literal>) properties are supported. - </para> - </note> - <note> - <para> - If consumers are already registered with the producer, modifying the configuration of required registration information will trigger the invalidation of held registrations, requiring consumers to modify their registration before being able to access the producer again. The consumer side of that process is documented in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error" />. - </para> + </para> - </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior"> - <title>Customization of Registration Handling Behavior</title> - <para> - Registration handling behavior can be customized by users to suit their Producer needs. This is done with an implementation of the <classname>RegistrationPolicy</classname> interface. - </para> - <para> - This interface defines methods that are called by Portal's Registration service so that decisions can be made appropriately. A default registration policy that provides basic behavior is provided and should be enough for most user needs. - </para> - <para> - While the default registration policy provides default behavior for most registration-related aspects, one aspect requires specific configuration: whether a given value for a registration property is acceptable by the WSRP Producer. - </para> - <para> - This is done by plugging a <classname>RegistrationPropertyValidator</classname> into the default registration policy. This allows users to define their own validation mechanism. - </para> - <para> - Refer to the <trademark class="trade">Javadoc</trademark> for <classname>org.gatein.registration.RegistrationPolicy</classname> and <classname>org.gatein.registration.policies.RegistrationPropertyValidator</classname> for more details on what is expected of each method. - </para> - <para> - A defined registration policy is required for the producer to be correctly configured. Do this by specifying the qualified class name of the registration policy. - </para> - <para> - As it is anticipated that most users will use the default registration policy, it is possible to provide the class name of a custom property validator instead to customize the default registration policy behavior. Note that property validators are only used by the default policy. - </para> - <note> - <para> - Since the policy or the validator are defined via their class name and dynamically loaded, it is important to ensure that the identified class is available to the application server. - </para> - <para> - One way to accomplish that is to deploy the policy implementation as a JAR file in the AS instance deploy directory. - </para> - <para> - Note also that, since both policies and validators are dynamically instantiated, they must provide a default, no-argument constructor. - </para> - - </note> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-WSRP_Validation_Mode"> - <title>WSRP Validation Mode</title> - <para> - The lack of conformance kit and the wording of the WSRP specification leaves room for differing interpretations, resulting in interoperability issues. It is therefore possible to encounter issues when using consumers from different vendors. + <section id="custom_registration"> + <title>Customization of Registration handling behavior</title> + <para> + Registration handling behavior can be customized by users to suit their Producer needs. This is + accomplished by providing an implementation of the + <classname>RegistrationPolicy</classname> + interface. This interface defines methods that are called by Portal's Registration service so that + decisions can be made appropriately. A default registration policy that provides basic + behavior is provided and should be enough for most user needs. </para> - <para> - Experience of these issues has produced a way to relax the validation that the WSRP producer performs on the data provided by consumers to help with interoperability by accepting data that would normally be invalid. + <para> + While the default registration policy provides default behavior for most registration-related aspects, + there is still one aspect that requires configuration: whether a given value for a registration property + is acceptable by the WSRP Producer. This is accomplished by plugging a + <classname>RegistrationPropertyValidator</classname> + in the default registration policy. This allows users to define their own validation mechanism. </para> - <para> - Note that the our validation algorithm is only relaxed on aspects of the specification that are deemed harmless such as invalid language codes. + <para> + Please refer to the + <trademark class="trade">Javadoc</trademark> + for + <classname>org.gatein.registration.RegistrationPolicy</classname> + and + <classname>org.gatein.registration.policies.RegistrationPropertyValidator</classname> + for more + details on what is expected of each method. </para> - <para> - By default, the WSRP producer is configured in strict mode. If you experience issues with a given consumer, you may attempt to relax the validation mode. Un-checking the "Use strict WSRP compliance" checkbox on the Producer configuration screen to do this. - </para> + <para>Defining a registration policy is required for the producer to be correctly configured. This is + accomplished by specifying the qualified class name of the registration policy. Since we anticipate that + most users will use the default registration policy, it is possible to provide the class + name of your custom property validator instead to customize the default registration policy behavior. + Note that property validators are only used by the default policy. - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Removing_WSRP"> - <title>Removing WSRP</title> + <note> + <para>Since the policy or the validator are defined via their class name and dynamically loaded, it is + important that you make sure that the identified class is available to the application server. One + way + to accomplish that is to deploy your policy implementation as JAR file in your AS instance deploy + directory. Note also that, since both policies and validators are dynamically instantiated, they + must + provide a default, no-argument constructor. + </para> + </note> + </para> + </section> + </section> + <section id="strict-mode"> + <title>WSRP validation mode</title> + <para>The lack of conformance kit and the wording of the WSRP specification leaves room for differing + interpretations, resulting in interoperability issues. It is therefore possible to encounter issues when + using consumers from different vendors. We have experienced such issues and have introduced a way to relax + the validation that our WSRP producer performs on the data provided by consumers to help with + interoperability by accepting data that would normally be invalid. Note that we only relax our validation + algorithm on aspects of the specification that are deemed harmless such as invalid language codes. + </para> <para> - If you are not going to use WSRP in your JBoss Enterprise Portal Platform instance, the WSRP configuration files may be left in place. They will not adversely affect your installation. - </para> - <para> - However, if you wish to completely remove WSRP from your portal installation, remove the <filename>gatein-wsrp-integration.ear</filename> file from your application server deploy directory. - </para> -  - </section> - - + </section> </chapter> -

13 years, 1 month

1
0
0 / 0

gatein SVN: r8138 - portal/trunk/docs/reference-guide/en-US/modules.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-11-24 12:26:22 -0500 (Thu, 24 Nov 2011) New Revision: 8138 Modified: portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml Log: - GTNWSRP-267: + Use important instead of note for important stuff. Clever, uh? :) + Fixed improper name for default producer configuration file. Modified: portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml =================================================================== --- portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml 2011-11-24 14:39:01 UTC (rev 8137) +++ portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml 2011-11-24 17:26:22 UTC (rev 8138) @@ -310,12 +310,12 @@ <sect1> <title>Making a portlet remotable</title> - <note> + <important> <para> Only JSR-286 (Portlet 2.0) portlets can be made remotable as the mechanism to expose a portlet to WSRP relies on a JSR-286-only functionality. </para> - </note> + </important> <para>&PRODUCT_NAME; does <emphasis role="bold">NOT</emphasis>, by default, expose local portlets for consumption by remote WSRP consumers. In order to make a portlet remotely available, it must be made "remotable" by marking @@ -617,7 +617,7 @@ </filename> </para> </note> - <note> + <important> <para> It is important to note that once the XML configuration file for consumers has been read upon the WSRP service first start, the associated information is put under control of JCR (Java Content @@ -643,7 +643,7 @@ (if such information exists) as the producer will be re-created the next time the WSRP is launched if that information is not removed. </para>--> - </note> + </important> </para> <sect3> @@ -1185,18 +1185,18 @@ </filename> </para> </note> - <note> + <important> <para> It is important to note that once the XML configuration file for the producer has been read upon the WSRP service first start, the associated information is put under control of JCR (Java Content Repository). Subsequent launches of the WSRP service will use the JCR-stored information and ignore the content of the XML configuration file. </para> - </note> + </important> <note> <para> The default configuration file for the producer can be found at - <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/extension-component-$WSRP_VERSION.jar/conf/wsrp-consumers-config.xml</filename> + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/extension-component-$WSRP_VERSION.jar/conf/wsrp-producer-config.xml</filename> </para> </note> </para>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8137 - in components/sso/trunk: agent and 4 other directories.

by do-not-reply＠jboss.org

Author: mposolda Date: 2011-11-24 09:39:01 -0500 (Thu, 24 Nov 2011) New Revision: 8137 Modified: components/sso/trunk/agent/pom.xml components/sso/trunk/packaging/pom.xml components/sso/trunk/packaging/src/main/assembly/src.xml components/sso/trunk/packaging/src/main/resources/README components/sso/trunk/pom.xml components/sso/trunk/spnego/pom.xml Log: GTNPORTAL-2294 packaging improvement for SPNEGO Modified: components/sso/trunk/agent/pom.xml =================================================================== --- components/sso/trunk/agent/pom.xml 2011-11-24 13:58:33 UTC (rev 8136) +++ components/sso/trunk/agent/pom.xml 2011-11-24 14:39:01 UTC (rev 8137) @@ -62,17 +62,15 @@ <groupId>org.josso</groupId> <artifactId>josso-protocol-client</artifactId> </dependency> - - <dependency> - <groupId>org.jboss.security</groupId> - <artifactId>jboss-negotiation-spnego</artifactId> - </dependency> + <dependency> + <groupId>org.jboss.security</groupId> + <artifactId>jboss-negotiation-spnego</artifactId> + </dependency> + <dependency> + <groupId>javax.security</groupId> + <artifactId>jacc</artifactId> + </dependency> - <dependency> - <groupId>javax.security</groupId> - <artifactId>jacc</artifactId> - </dependency> - </dependencies> <build> Modified: components/sso/trunk/packaging/pom.xml =================================================================== --- components/sso/trunk/packaging/pom.xml 2011-11-24 13:58:33 UTC (rev 8136) +++ components/sso/trunk/packaging/pom.xml 2011-11-24 14:39:01 UTC (rev 8137) @@ -23,7 +23,7 @@ </dependency> <dependency> <groupId>org.jboss.security</groupId> - <artifactId>jboss-negotiation-spnego</artifactId> + <artifactId>jboss-negotiation</artifactId> </dependency> </dependencies> Modified: components/sso/trunk/packaging/src/main/assembly/src.xml =================================================================== --- components/sso/trunk/packaging/src/main/assembly/src.xml 2011-11-24 13:58:33 UTC (rev 8136) +++ components/sso/trunk/packaging/src/main/assembly/src.xml 2011-11-24 14:39:01 UTC (rev 8137) @@ -45,7 +45,7 @@ <useProjectArtifact>false</useProjectArtifact> <useTransitiveDependencies>false</useTransitiveDependencies> <includes> - <include>org.jboss.security:jboss-negotiation-spnego</include> + <include>org.jboss.security:jboss-negotiation</include> </includes> </dependencySet> Modified: components/sso/trunk/packaging/src/main/resources/README =================================================================== --- components/sso/trunk/packaging/src/main/resources/README 2011-11-24 13:58:33 UTC (rev 8136) +++ components/sso/trunk/packaging/src/main/resources/README 2011-11-24 14:39:01 UTC (rev 8137) @@ -6,6 +6,7 @@ - OpenSSO - JOSSO - CAS + - SPNEGO Please refer to the GateIn Portal documentation for usage of the embedded files. Modified: components/sso/trunk/pom.xml =================================================================== --- components/sso/trunk/pom.xml 2011-11-24 13:58:33 UTC (rev 8136) +++ components/sso/trunk/pom.xml 2011-11-24 14:39:01 UTC (rev 8137) @@ -204,17 +204,21 @@ </dependency>  - <dependency> - <groupId>org.jboss.security</groupId> - <artifactId>jboss-negotiation-spnego</artifactId> - <version>${version.jboss.negotiation}</version> - </dependency> - - <dependency> - <groupId>javax.security</groupId> - <artifactId>jacc</artifactId> - <version>1.0</version> - </dependency> + <dependency> + <groupId>org.jboss.security</groupId> + <artifactId>jboss-negotiation-spnego</artifactId> + <version>${version.jboss.negotiation}</version> + </dependency> + <dependency> + <groupId>org.jboss.security</groupId> + <artifactId>jboss-negotiation</artifactId> + <version>${version.jboss.negotiation}</version> + </dependency> + <dependency> + <groupId>javax.security</groupId> + <artifactId>jacc</artifactId> + <version>1.0</version> + </dependency> </dependencies> </dependencyManagement> Modified: components/sso/trunk/spnego/pom.xml =================================================================== --- components/sso/trunk/spnego/pom.xml 2011-11-24 13:58:33 UTC (rev 8136) +++ components/sso/trunk/spnego/pom.xml 2011-11-24 14:39:01 UTC (rev 8137) @@ -23,7 +23,7 @@ </dependency> <dependency> <groupId>org.jboss.security</groupId> - <artifactId>jboss-negotiation-spnego</artifactId> + <artifactId>jboss-negotiation-spnego</artifactId> </dependency> <dependency> <groupId>org.gatein.sso</groupId>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8136 - portal/trunk/docs/reference-guide/en-US/modules.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-11-24 08:58:33 -0500 (Thu, 24 Nov 2011) New Revision: 8136 Modified: portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml Log: - GTNWSRP-267: + Added reference to JBOSS_PROFILE_HOME for greater clarity. + Fixed improper documentation as to the behavior of the consumers configuration: we do not read the XML configuration anymore if it's already been imported in JCR. Note that this was a mistake that probably dates back to GateIn 3 documentation. - GTNWSRP-231: added documentation on the possibility of adding a wsrp-producer-config.xml file to conf/gatein to use instead of having to modify the extension to change the initial producer configuration. Modified: portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml =================================================================== --- portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml 2011-11-24 10:43:24 UTC (rev 8135) +++ portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml 2011-11-24 13:58:33 UTC (rev 8136) @@ -86,9 +86,10 @@ &PRODUCT_NAME; provides a complete support of WSRP 1.0 and 2.0 standard interfaces and offers both consumer and producer services. Starting with version 2.1.0-GA of the component, WSRP is packaged as a &PRODUCT_NAME; extension and is now self-contained in an easy to install package named - <filename>gatein-wsrp-integration.ear</filename>, deployed directly in the - <filename>deploy</filename> - directory of your JBoss Application Server configuration directory. + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear</filename> + where + <filename>$JBOSS_PROFILE_HOME</filename> + refers to your JBoss AS profile directory (<filename>default</filename>, for instance). </para> <para> The extension itself is composed of the following components, assuming @@ -607,18 +608,24 @@ <para>While we recommend you use the WSRP Configuration portlet to configure Consumers, we provide an alternative way to configure consumers by adding an XML file called <filename>wsrp-consumers-config.xml</filename> in the - <filename>$JBOSS_PROFILE_HOME/conf/gatein/</filename> directory - where <code>$JBOSS_PROFILE_HOME</code> refers to your JBoss AS profile directory (<code>default</code>, for instance). + <filename>$JBOSS_PROFILE_HOME/conf/gatein/</filename> directory. <note> <para>An XML Schema defining which elements are available to configure Consumers via XML can be found in <filename> - gatein-wsrp-integration.ear/lib/wsrp-integration-api-$WSRP_VERSION.jar/xsd/gatein_wsrp_consumer_1_0.xsd + $JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/wsrp-integration-api-$WSRP_VERSION.jar/xsd/gatein_wsrp_consumer_1_0.xsd </filename> </para> </note> <note> - <para>It is important to note how the XML consumers configuration file is processed. It is read the first + <para> + It is important to note that once the XML configuration file for consumers has been read upon + the WSRP service first start, the associated information is put under control of JCR (Java Content + Repository). Subsequent launches of the WSRP service will use the JCR-stored information and ignore + the content of the XML configuration file. + </para> + +  </note> </para> @@ -735,7 +742,7 @@ and <literal>selfv2</literal> consumers as found in - <filename>gatein-wsrp-integration.ear/lib/extension-component-$WSRP_VERSION.jar/conf/wsrp-consumers-config.xml</filename> + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/extension-component-$WSRP_VERSION.jar/conf/wsrp-consumers-config.xml</filename> with a cache expiring every 500 seconds and with a 50 second timeout for web service operations. <note> <para> @@ -1162,16 +1169,36 @@ <sect2> <title>Overview</title> <para> - !!! TODO claprun update from here !!! - - You can configure the behavior of Portal's WSRP Producer by using the WSRP administration interface, which - is the preferred way, or by editing the - <filename>$GATEIN_HOME/wsrp-producer.war/WEB-INF/conf/producer/config.xml</filename> - file. Several aspects can be modified with respects to whether registration is required for consumers to - access the Producer's services. An XML Schema for the configuration format is available at - <filename> - $GATEIN_HOME/lib/wsrp-integration-api-$WSRP_VERSION.jar/xsd/gatein_wsrp_producer_1_0.xsd - </filename>. + The preferred way to configure the behavior of Portal's WSRP Producer is via the WSRP configuration portlet. + Alternatively, it is possible to add an XML file called + <filename>wsrp-producer-config.xml</filename> + in the + <filename>$JBOSS_PROFILE_HOME/conf/gatein/</filename> + directory. + Several aspects can be modified with respects to whether registration is required for consumers to access + the Producer's services. + <note> + <para>An XML Schema defining which elements are available to configure Consumers via XML can be found + in + <filename> + $JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/wsrp-integration-api-$WSRP_VERSION.jar/xsd/gatein_wsrp_producer_1_0.xsd + </filename> + </para> + </note> + <note> + <para> + It is important to note that once the XML configuration file for the producer has been read upon + the WSRP service first start, the associated information is put under control of JCR (Java Content + Repository). Subsequent launches of the WSRP service will use the JCR-stored information and ignore + the content of the XML configuration file. + </para> + </note> + <note> + <para> + The default configuration file for the producer can be found at + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/extension-component-$WSRP_VERSION.jar/conf/wsrp-consumers-config.xml</filename> + </para> + </note> </para> </sect2> <sect2>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8135 - in portal/trunk/docs/reference-guide/en-US: modules and 1 other directory.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-11-24 05:43:24 -0500 (Thu, 24 Nov 2011) New Revision: 8135 Modified: portal/trunk/docs/reference-guide/en-US/images/WSRP/config_self.png portal/trunk/docs/reference-guide/en-US/images/WSRP/modify_reg_end.png portal/trunk/docs/reference-guide/en-US/images/WSRP/modify_reg_self.png portal/trunk/docs/reference-guide/en-US/images/WSRP/modify_reg_self_end.png portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml Log: - GTNWSRP-267: finished updating the consumers configuration part. Modified: portal/trunk/docs/reference-guide/en-US/images/WSRP/config_self.png =================================================================== (Binary files differ) Modified: portal/trunk/docs/reference-guide/en-US/images/WSRP/modify_reg_end.png =================================================================== (Binary files differ) Modified: portal/trunk/docs/reference-guide/en-US/images/WSRP/modify_reg_self.png =================================================================== (Binary files differ) Modified: portal/trunk/docs/reference-guide/en-US/images/WSRP/modify_reg_self_end.png =================================================================== (Binary files differ) Modified: portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml =================================================================== --- portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml 2011-11-24 03:40:22 UTC (rev 8134) +++ portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml 2011-11-24 10:43:24 UTC (rev 8135) @@ -103,7 +103,7 @@ contains files necessary for EAR packaging. The only file that is of interest from a user perspective is <filename>gatein-wsse-consumer.xml</filename> - which allows you to configure WS-Security support for the consumer. Please see the + which allows you to configure WS-Security support for the consumer. Please see the <link linkend="wss_configuration">WSRP and WS-Security</link> section for more details. </para> </listitem> @@ -144,9 +144,9 @@ </listitem> <listitem> <para><filename>wsrp-producer-jb5wsss-$WSRP_VERSION.war</filename>, which contains the producer-side - support for WS-Security. The only file of interest from a user perspective is - <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for - the producer. Please see the <link linkend="wss_configuration">WSRP and WS-Security</link> section + support for WS-Security. The only file of interest from a user perspective is + <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for + the producer. Please see the <link linkend="wss_configuration">WSRP and WS-Security</link> section for more details. </para> </listitem> @@ -192,31 +192,31 @@ </sect2> <sect2> <title>WSRP and WS-Security</title> - <para>Portlets may present different data or options depending on the currently authenticated user. For remote - portlets, this means having to propagate the user credentials from the consumer back to the producer in - a safe and secure manner. The WSRP specification does not directly specify how this should be + <para>Portlets may present different data or options depending on the currently authenticated user. For remote + portlets, this means having to propagate the user credentials from the consumer back to the producer in + a safe and secure manner. The WSRP specification does not directly specify how this should be accomplished, but delegates this work to the existing WS-Security standards. </para> <note> <title>Web Container Compatibility</title> - <para>WSRP and WS-Security is currently only supported on &PRODUCT_NAME; when running on top of JBoss + <para>WSRP and WS-Security is currently only supported on &PRODUCT_NAME; when running on top of JBoss AS 5. </para> </note> <warning> <title>Encryption</title> - <para>You will want to encrypt the credentials being sent between the consumer and producer, otherwise they - will be sent in plain text and could be easily intercepted. You can either configure WS-Security to - encrypt and sign the SOAP messages being sent, or secure the transport layer by using an https endpoint. - Failure to encrypt the soap message or transport layer will result in the username and password being + <para>You will want to encrypt the credentials being sent between the consumer and producer, otherwise they + will be sent in plain text and could be easily intercepted. You can either configure WS-Security to + encrypt and sign the SOAP messages being sent, or secure the transport layer by using an https endpoint. + Failure to encrypt the soap message or transport layer will result in the username and password being sent in plain text. <emphasis role="bold">Use of encryption is strongly recommended.</emphasis> </para> </warning> <important> <title>Credentials</title> - <para>When the consumer sends the user credentials to the producer, it is sending the credentials for the - currently authenticated user in the consumer. This makes signing in to remote portlets transparent - to end users, but also requires that the producer and consumer use the same credentials. This means + <para>When the consumer sends the user credentials to the producer, it is sending the credentials for the + currently authenticated user in the consumer. This makes signing in to remote portlets transparent + to end users, but also requires that the producer and consumer use the same credentials. This means that the username and password must be the same and valid on both servers. </para> <para>The recommended approach for this situation would be to use a common ldap configuration. Please @@ -224,12 +224,12 @@ </para> </important> <para>The GateIn Wiki article, <ulink url="http://community.jboss.org/wiki/GateInWSRPAndWebServiceSecurity"> - GateIn WSRP and Web Service Security</ulink>, also provides a step-by-step example on how to configure + GateIn WSRP and Web Service Security</ulink>, also provides a step-by-step example on how to configure WSRP with WS-Security. </para> <sect3 id="wss_configuration"> <title>WS-Security Configuration</title> - <para>&PRODUCT_NAME; uses JBossWS Native to handle ws-security. Please see the WS-Security section of the + <para>&PRODUCT_NAME; uses JBossWS Native to handle ws-security. Please see the WS-Security section of the <ulink url="http://www.jboss.org/jbossas/docs/5-x">JBoss AS 5 Administration and Configuration Guide </ulink> for indepth configuration options. Please note that since the consumer passes its credentials to the producer, the consumer will act at the wss client and the producer will act as the wss server. @@ -239,7 +239,7 @@ <itemizedlist> <listitem> <para> - <filename>gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</filename>: JBossWS + <filename>gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</filename>: JBossWS configuration file for the consumer. </para> </listitem> @@ -254,15 +254,15 @@ <sect3> <title>WS-Security Producer Configuration</title> <para> - Other than the JBossWS configuration file mention above, no other configuration changes should be necessary + Other than the JBossWS configuration file mention above, no other configuration changes should be necessary for the producer. </para> </sect3> <sect3> <title>WS-Security Consumer Configuration</title> - <para>The consumer requires a few changes before it will function properly with WS-Security. The consumer - needs access to the current servlet request since this is used to retrieve the currently authenticated - user. In order for the consumer to access this information, it needs a special servlet-filter added to + <para>The consumer requires a few changes before it will function properly with WS-Security. The consumer + needs access to the current servlet request since this is used to retrieve the currently authenticated + user. In order for the consumer to access this information, it needs a special servlet-filter added to the portal. </para> <para>In <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> add the following information: @@ -845,8 +845,6 @@ <sect3> <title>Registration modification for service upgrade</title> <para> - !!! TODO claprun continue update from here !!! - Producers often offer several levels of service depending on consumers' subscription levels (for example). This is implemented at the WSRP level with the registration concept: producers can assert which level of service to provide to consumers based on the values of given registration properties. @@ -858,25 +856,19 @@ </para> <para> It is therefore sometimes necessary to modify the registration that concretizes the service agreement - between a consumer and a producer. Let's take the example of the producer requiring an email we - configured in - <xref linkend="consumer_gui"/>. - If you recall, the producer was requiring registration and required a value to be provided for the + between a consumer and a producer. Let's take the example of a producer requiring a valid email (via an <literal>email</literal> - property. + registration property) as part of its required information that consumers need to provide to be properly + registered. </para> <para> - Suppose now that we would like to update the email address that we provided to the remote producer. We - will need to tell the producer that our registration data has been modified. Let's see how to do this. - Assuming you - have configured access to the producer as previously described, please go to the configuration screen for - the - <literal>self</literal> - producer and modify the value of + Suppose now that we would like to update the email address that we provided to the remote producer when + we first registered. We will need to tell the producer that our registration data has been modified. + Let's see how to do this. Select the consumer for the remote producer in the available consumers list to + display its configuration. Assuming you want to change the email you registered with to + <literal>foo(a)example.com</literal>, change its value in the field for the <literal>email</literal> - to - <literal>foo(a)example.com</literal> - instead of<literal>example(a)example.com</literal>: + registration property: <mediaobject> <imageobject> <imagedata fileref="images/WSRP/modify_reg_start.png" format="PNG" align="center" valign="middle" @@ -908,15 +900,10 @@ <para> It can also happen that a producer administrator decided to change its requirement for registered - consumers. In this case, invoking operations on the producer will fail with an - <exceptionname>OperationFailedFault</exceptionname>. &PRODUCT_NAME; will attempt to help you in this - situation. Let's walk through an example using the - <literal>self</literal> - producer. Let's assume that - registration is requiring a valid value for an + consumers. &PRODUCT_NAME; will attempt to help you in this situation. Let's walk through an example using + the <literal>selfv2</literal> consumer. Let's assume that registration is requiring a valid value for an <literal>email</literal> - registration property (as we have seen so far). If you go to the configuration screen for this producer, - you should see: + registration property. If you go to the configuration screen for this consumer, you should see: <mediaobject> <imageobject> <imagedata fileref="images/WSRP/config_self.png" format="PNG" align="center" valign="middle" @@ -961,7 +948,7 @@ can be caused by several different reasons, one of them being a request to modify the registration data. Please take a look at the log files to see if you can gather more information as to what happened. WSRP 2 introduces an exception that is - specific to a request to modify registrations thus reducing the ambiguity that currently exists. + specific to a request to modify registrations thus reducing the ambiguity that exists when using WSRP 1. </para> </note> @@ -1016,8 +1003,9 @@ </itemizedlist> </para> <note> - <para>Import/Export functionalities are only available to WSRP 2 consumers. Import functionality is only - available if portlets had previously been exported. + <para> + Import/Export functionality is only available to WSRP 2 consumers of producers that support this optional + functionality. Import functionality is only available if portlets had previously been exported. </para> </note> </sect2> @@ -1030,8 +1018,9 @@ does not currently support automated migration of portal data, the functionality that we provide as part of WSRP 2 is necessarily less complete than it could be with full portal support. </para> - <para>The import/export implementation in &PRODUCT; allows users to export portlets from a given consumer. - These portlets can then be used to replace existing content on pages. This is accomplished by assiging + <para>The import/export implementation in &PRODUCT_NAME; (available since 3.1) allows users to export portlets + from a given consumer. + These portlets can then be used to replace existing content on pages. This is accomplished by assigning previously exported portlets to replace the content displayed by windows on the portal's pages. Let us walk through an example to make things clearer. </para> @@ -1173,6 +1162,8 @@ <sect2> <title>Overview</title> <para> + !!! TODO claprun update from here !!! + You can configure the behavior of Portal's WSRP Producer by using the WSRP administration interface, which is the preferred way, or by editing the <filename>$GATEIN_HOME/wsrp-producer.war/WEB-INF/conf/producer/config.xml</filename>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8134 - epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2011-11-23 22:40:22 -0500 (Wed, 23 Nov 2011) New Revision: 8134 Added: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.ent epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml Removed: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.ent epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.xml Log: Removed beta info from Release Notes for new respin Deleted: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.ent =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.ent 2011-11-24 03:30:37 UTC (rev 8133) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.ent 2011-11-24 03:40:22 UTC (rev 8134) @@ -1,14 +0,0 @@ - -<!ENTITY PRODUCT "JBoss Site Publisher"> - - -<!ENTITY BOOKID "Site Publisher Release Notes"> - - -<!ENTITY YEAR "2011"> -<!ENTITY HOLDER "Red Hat, Inc"> - - -<!ENTITY VX "5"> -<!ENTITY VY "5.2"> -<!ENTITY VZ "5.2.0"> Deleted: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.xml 2011-11-24 03:30:37 UTC (rev 8133) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.xml 2011-11-24 03:40:22 UTC (rev 8134) @@ -1,156 +0,0 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_5.2.0_BETA_Release_Notes.ent"> -%BOOK_ENTITIES; -]> -<book> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> - <chapter id="Release_Notes-Introduction"> - <title>Introduction</title> - <para> - JBoss Site Publisher (powered by eXo) is an add-on component for JBoss Enterprise Portal Platform. Site Publisher enables users to create, edit and publish rich web content within the context of their portal installation. - </para> - <note> - <title>Subscription</title> - <para> - Subscriptions to JBoss Site Publisher are available at an additional fee over and above JBoss Enterprise Portal Platform subscriptions. - </para> - </note> - <para> - JBoss Site Publisher simplifies the authoring and management for every website an organization needs to deploy. It includes the ability to administer sites, manage navigation, and publish content. Site Publisher delivers powerful functionality to everyone responsible for maintaining web content: - </para> - <itemizedlist> - <listitem> - <para> - Webmasters can easily administer multiple websites. - </para> - </listitem> - <listitem> - <para> - Website administrators can set permission policies according to user roles to better control website changes. - </para> - </listitem> - <listitem> - <para> - Content providers can use JBoss Enterprise Portal Platform’s tools to create content and then choose how to publish it using blogs, RSS feeds, social networks and more. - </para> - </listitem> - <listitem> - <para> - Web developers can introduce other forms of rich media content to create truly professional websites easily and efficiently. - </para> - </listitem> - </itemizedlist> - </chapter> - <chapter id="Release_Notes-Component_Features"> - <title>Component Features</title> - <formalpara> - <title>New Components</title> - <para>The following new components warrant special mention.</para> - </formalpara> - <variablelist> - <varlistentry> - <term>In-line Editing</term> - <listitem> - <para>This updated functionality enables content authors to modify existing web content upon the page in which it is presented. All an author needs to do is double click on the content to launch the content editor within the page. </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Search Engine Optimization (SEO)</term> - <listitem> - <para>A new interface for content authors provides a means to enter information to promote pages to different search engines and manage SEO settings on each page of the site. </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Updated Authoring Interface</term> - <listitem> - <para>The authoring interface has been update to be more intuitive for content authors to more quickly and easily create and manage their content. </para> - </listitem> - </varlistentry> - </variablelist> - </chapter> - <chapter id="Release_Notes-Installation"> - <title>Installation</title> - <para> - The JBoss Site Publisher <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. - </para> - <para> - The <citetitle>Installation Guide</citetitle> can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. - </para> - </chapter> - <chapter id="Release_Notes-Issues_Resolved_In_Production"> - <title>Issues Resolved In Production</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml" encoding="XML"/> - </chapter> - <chapter id="Release_Notes-Issues_Resolved_Upstream"> - <title>Issues Resolved Upstream</title> - <para>This release contains Site Publisher issues resolved upstream by eXo Platform. These issues have been verified by the JBoss Enterprise Portal Platform Engineering team and included as part of this release. </para> - </chapter> - <chapter id="Release_Notes-Known_Issues"> - <title>Known Issues</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml"/> - </chapter> - <chapter id="Release_Notes-Documentation"> - <title>Documentation</title> - <para> - An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Site Publisher are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. - </para> - </chapter> - <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> - <title> Product Support and License Website Links </title> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> - <title>Support Processes</title> - <para> - <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_"> - <title> Production Support Scope of Coverage </title> - <para> - <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_"> - <title> Production Support Service Level Agreement </title> - <para> - <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> - <title> Developer Support Scope of Coverage </title> - <para> - <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_"> - <title> Developer Support Service Level Agreement </title> - <para> - <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_"> - <title> Product Update and Support Policy by Product </title> - <para> - <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> - <title> JBoss End User License Agreement </title> - <para> - <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink> - </para> - </formalpara> - </chapter> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> -</book> Copied: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.ent (from rev 8131, epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.ent) =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.ent (rev 0) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.ent 2011-11-24 03:40:22 UTC (rev 8134) @@ -0,0 +1,14 @@ + +<!ENTITY PRODUCT "JBoss Site Publisher"> + + +<!ENTITY BOOKID "Site Publisher Release Notes"> + + +<!ENTITY YEAR "2011"> +<!ENTITY HOLDER "Red Hat, Inc"> + + +<!ENTITY VX "5"> +<!ENTITY VY "5.2"> +<!ENTITY VZ "5.2.0"> Copied: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml (from rev 8131, epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_BETA_Release_Notes.xml) =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml (rev 0) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml 2011-11-24 03:40:22 UTC (rev 8134) @@ -0,0 +1,156 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_5.2.0_BETA_Release_Notes.ent"> +%BOOK_ENTITIES; +]> +<book> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <chapter id="Release_Notes-Introduction"> + <title>Introduction</title> + <para> + JBoss Site Publisher (powered by eXo) is an add-on component for JBoss Enterprise Portal Platform. Site Publisher enables users to create, edit and publish rich web content within the context of their portal installation. + </para> + <note> + <title>Subscription</title> + <para> + Subscriptions to JBoss Site Publisher are available at an additional fee over and above JBoss Enterprise Portal Platform subscriptions. + </para> + </note> + <para> + JBoss Site Publisher simplifies the authoring and management for every website an organization needs to deploy. It includes the ability to administer sites, manage navigation, and publish content. Site Publisher delivers powerful functionality to everyone responsible for maintaining web content: + </para> + <itemizedlist> + <listitem> + <para> + Webmasters can easily administer multiple websites. + </para> + </listitem> + <listitem> + <para> + Website administrators can set permission policies according to user roles to better control website changes. + </para> + </listitem> + <listitem> + <para> + Content providers can use JBoss Enterprise Portal Platform’s tools to create content and then choose how to publish it using blogs, RSS feeds, social networks and more. + </para> + </listitem> + <listitem> + <para> + Web developers can introduce other forms of rich media content to create truly professional websites easily and efficiently. + </para> + </listitem> + </itemizedlist> + </chapter> + <chapter id="Release_Notes-Component_Features"> + <title>Component Features</title> + <formalpara> + <title>New Components</title> + <para>The following new components warrant special mention.</para> + </formalpara> + <variablelist> + <varlistentry> + <term>In-line Editing</term> + <listitem> + <para>This updated functionality enables content authors to modify existing web content upon the page in which it is presented. All an author needs to do is double click on the content to launch the content editor within the page. </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Search Engine Optimization (SEO)</term> + <listitem> + <para>A new interface for content authors provides a means to enter information to promote pages to different search engines and manage SEO settings on each page of the site. </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Updated Authoring Interface</term> + <listitem> + <para>The authoring interface has been update to be more intuitive for content authors to more quickly and easily create and manage their content. </para> + </listitem> + </varlistentry> + </variablelist> + </chapter> + <chapter id="Release_Notes-Installation"> + <title>Installation</title> + <para> + The JBoss Site Publisher <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. + </para> + <para> + The <citetitle>Installation Guide</citetitle> can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. + </para> + </chapter> + <chapter id="Release_Notes-Issues_Resolved_In_Production"> + <title>Issues Resolved In Production</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml" encoding="XML"/> + </chapter> + <chapter id="Release_Notes-Issues_Resolved_Upstream"> + <title>Issues Resolved Upstream</title> + <para>This release contains Site Publisher issues resolved upstream by eXo Platform. These issues have been verified by the JBoss Enterprise Portal Platform Engineering team and included as part of this release. </para> + </chapter> + <chapter id="Release_Notes-Known_Issues"> + <title>Known Issues</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml"/> + </chapter> + <chapter id="Release_Notes-Documentation"> + <title>Documentation</title> + <para> + An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Site Publisher are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. + </para> + </chapter> + <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> + <title> Product Support and License Website Links </title> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> + <title>Support Processes</title> + <para> + <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_"> + <title> Production Support Scope of Coverage </title> + <para> + <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_"> + <title> Production Support Service Level Agreement </title> + <para> + <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> + <title> Developer Support Scope of Coverage </title> + <para> + <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_"> + <title> Developer Support Service Level Agreement </title> + <para> + <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_"> + <title> Product Update and Support Policy by Product </title> + <para> + <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> + <title> JBoss End User License Agreement </title> + <para> + <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink> + </para> + </formalpara> + </chapter> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> +</book>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8133 - in epp/docs/branches/5.2/Developer_Guide/en-US: images/7372876 and 1 other directory.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-23 22:30:37 -0500 (Wed, 23 Nov 2011) New Revision: 8133 Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Author_Group.xml epp/docs/branches/5.2/Developer_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Developer_Guide/en-US/Developer_Guide.ent epp/docs/branches/5.2/Developer_Guide/en-US/Developer_Guide.xml epp/docs/branches/5.2/Developer_Guide/en-US/Preface.xml epp/docs/branches/5.2/Developer_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-1-GDG_Introduction.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-3-GDG_Design_choices.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml epp/docs/branches/5.2/Developer_Guide/en-US/images/7372876/complexinfra.png Log: Re-exported after image issues. Corrected image paths. Added Intro text. Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Author_Group.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/Author_Group.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/Author_Group.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -1,20 +1,25 @@ <?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> +<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> <authorgroup> - <author> - <firstname>Thomas</firstname> - <surname>Heute</surname> - <email>theute(a)redhat.com</email> - </author> - <author> - <firstname>Prabhat</firstname> - <surname>Jha</surname> - <email>prabhat.jha(a)jboss.com</email> - - </author> + <author> + <firstname>Vlastimil</firstname> + <surname>Eliáš</surname> + <email>velias(a)redhat.com</email> + </author> + <author> + <firstname>Thomas</firstname> + <surname>Heute</surname> + <email>theute(a)redhat.com</email> + </author> + <author> + <firstname>Prabhat</firstname> + <surname>Jha</surname> + <email>prabhat.jha(a)jboss.com</email> + </author> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email>smumford(a)redhat.com</email> + </author> </authorgroup> - Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/Book_Info.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/Book_Info.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -2,6 +2,14 @@ <!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> %BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> +%BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM ".ent"> +%BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> +%BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> +%BOOK_ENTITIES; ]> <bookinfo id="book-Developer_Guide-Developer_Guide"> <title>Developer Guide</title> @@ -9,7 +17,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>3</pubsnumber> + <pubsnumber>4</pubsnumber> <abstract> <para> This guide is intended to assist developers working with JBoss Enterprise Portal Platform. It assumes a high level of technical knowledge. Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Developer_Guide.ent =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/Developer_Guide.ent 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/Developer_Guide.ent 2011-11-24 03:30:37 UTC (rev 8133) @@ -7,7 +7,7 @@  <!ENTITY BZPRODUCT "JBoss Enterprise Portal Platform 5"> <!ENTITY BZCOMPONENT "docs-Developer_Guide"> -<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Enterpri...'>http://bugzilla.redhat.com/</ulink>"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Enterpri...'>http://bugzilla.redhat.com/</ulink>">  <!ENTITY YEAR "2011"> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Developer_Guide.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/Developer_Guide.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/Developer_Guide.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -1,16 +1,13 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> <book> - <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="chapter-1-GDG_Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="chapter-2-GDG_Architectural_choices.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="chapter-3-GDG_Design_choices.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="chapter-4-GDG_Portal_Development.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="chapter-5-GDG_Application_development.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -</book> + <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="chapter-1-GDG_Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="chapter-2-GDG_Architectural_choices.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="chapter-3-GDG_Design_choices.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="chapter-4-GDG_Portal_Development.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="chapter-5-GDG_Application_development.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +</book> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Preface.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/Preface.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/Preface.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -2,6 +2,14 @@ <!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> %BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> +%BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM ".ent"> +%BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> +%BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> +%BOOK_ENTITIES; ]> <preface id="pref-Developer_Guide-Preface"> <title>Preface</title> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/Revision_History.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/Revision_History.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -2,12 +2,34 @@ <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> %BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> +%BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM ".ent"> +%BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> +%BOOK_ENTITIES; +<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> +%BOOK_ENTITIES; ]> <appendix id="appe-Developer_Guide-Revision_History"> <title>Revision History</title> <simpara> <revhistory> <revision> + <revnumber>5.2.0-4</revnumber> + <date>Tue Nov 15 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Staged for beta release.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.0-3</revnumber> <date>Wed Oct 19 2011</date> <author> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-1-GDG_Introduction.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-1-GDG_Introduction.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-1-GDG_Introduction.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -1,13 +1,7 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> -<chapter id="chap-Developer_Guide-Introduction"> - <title>Introduction</title> - <para> - - </para> - -</chapter> - +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="sid-819799"> + + <title>Introduction</title> + <para>This is the EPP Developer Guide. This document is intended for those developing applications and gadgets for the EPP product and outlines options and strategies for successful deployment.</para> + </chapter> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-2-GDG_Architectural_choices.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -1,135 +1,91 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> -<chapter id="chap-Developer_Guide-Architectural_choices"> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="sid-7372876"> + <title>Architectural choices</title> - <para> - Depending on environment and goals, decisions has to be made regarding the components that will make up the final website. Some elements may already be in place (such as an identity server) and some elements may still be free to choose. This section aims at helping taking the right decisions. - </para> - <section id="sect-Developer_Guide-Architectural_choices-Identity_server"> - <title>Identity server</title> - <para> - JBoss Enterprise Portal Platform &VY; comes with a component named PicketLink IDM, which is made to adapt to store and retrieve users and groups from various identity servers. We can separate the different options into three: - </para> - <orderedlist> - <listitem> - <para> - <emphasis role="strong">Database</emphasis> : users, groups and their relationships are stored in a RDBMS database. Tables names and column names can be changed, but the overall relationship between tables remains the same. This solution is particularly adapted to a new identity server that will handle thousands of users. - </para> - - </listitem> - <listitem> - <para> - <emphasis role="strong">LDAP</emphasis> : users, groups and their relationships are stored in an LDAP (or ActiveDirectory) server, the directory structure can be adapted by configuration to the most common scenarios. This solution is particularly adapted to infrastructure that are already using an LDAP server, for infrastructure that will share the server identity among multiple service (and the website being one of them) or for very large set of users (millions). When using LDAP with large number of users, it is recommended to use LDAP tools to do the provisioning of users. - </para> - - </listitem> - <listitem> - <para> - <emphasis role="strong">Custom</emphasis> : when retrieving users, groups and their relationship cannot be done by configuration, it is possible to implement the Picketlink IDM SPI to implement the methods in charge of retrieving and storing user information. - </para> - - </listitem> - - </orderedlist> - <para> - Picketlink IDM also supports mix environments, this is very useful when an LDAP infrastructure is provided but in a read-only mode. Since the website may need to store additional information about users (such as his preferred language or skin), it can combine LDAP + Database, to retrieve users from LDAP but store additional properties in a database. During the calls to the identity API, the information from both sources will be transparently merged. For more information about PicketLink IDM, please check the JBoss Enterprise Portal Platform &VY; reference guide and the PicketLink IDM documentation. - </para> - + <para>Depending on environment and goals, decisions has to be made regarding the components that will make up the final website. Some elements may already be in place (such as an identity server) and some elements may still be free to choose. This section aims at helping taking the right decisions.</para> + <section id="sid-7372876_GDG-Architecturalchoices-Identityserver"> + + <title>Identity server</title> + <para>EPP 5.2 comes with a component named PicketLink IDM, which is made to adapt to store and retrieve users and groups from various identity servers. We can separate the different options into three:</para> + <orderedlist> + <listitem> + <para> + <emphasis role="strong">Database</emphasis> + : users, groups and their relationships are stored in a RDBMS database. Tables names and column names can be changed, but the overall relationship between tables remains the same. This solution is particularly adapted to a new identity server that will handle thousands of users. + </para> + </listitem> + <listitem> + <para> + <emphasis role="strong">LDAP</emphasis> + : users, groups and their relationships are stored in an LDAP (or ActiveDirectory) server, the directory structure can be adapted by configuration to the most common scenarios. This solution is particularly adapted to infrastructure that are already using an LDAP server, for infrastructure that will share the server identity among multiple service (and the website being one of them) or for very large set of users (millions). When using LDAP with large number of users, it is recommended to use LDAP tools to do the provisioning of users. + </para> + </listitem> + <listitem> + <para> + <emphasis role="strong">Custom</emphasis> + : when retrieving users, groups and their relationship cannot be done by configuration, it is possible to implement the Picketlink IDM SPI to implement the methods in charge of retrieving and storing user information. + </para> + </listitem> + </orderedlist> + <para> + Picketlink IDM also supports mix environments, this is very useful when an LDAP infrastructure is provided but in a read-only mode. Since the website may need to store additional information about users (such as his preferred language or skin), it can combine LDAP + Database, to retrieve users from LDAP but store additional properties in a database. During the calls to the identity API, the information from both sources will be transparently merged. + + For more information about PicketLink IDM, please check the EPP 5.2 reference guide and the PicketLink IDM documentation. + </para> </section> - - <section id="sect-Developer_Guide-Architectural_choices-Storage"> - <title>Storage</title> - <para> - The portal framework stores page compositions, portlet preferences, gadget code in a database through a Java Content Repository (JCR) API. A set of database servers and JDBC connectors are part of our quality assurance cycles and the certified environments are mentioned <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">here</ulink> . - </para> - <para> - It is important to choose one of the combination or check with a Red Hat contact for specific environments that would differ from this list. - </para> - <para> - The database schema will be automatically created during the very first startup of the website and then it is required that the database users has sufficient rights to create tables. This privilege can be revoked after the initial startup, also the database content can be exported and imported in a new server. This makes the installation of the product very easy in most cases. - </para> - <para> - We do not provide additional recommendation to choose a database server over another as long as it is part of our certified environment. - </para> - <para> - As said earlier content is stored through a JCR API, RDBMS aren't a great fit to store large files and it is possible to configure eXo JCR to store such files in the filesystem instead of database, metadata about the files would still be stored into the database. Note that if the website is running on a cluster the filesystem will need to be accessible from all nodes and a NFS solution needs to be setup. For more details see the notion of "value storage" in the reference guide. - </para> - + <section id="sid-7372876_GDG-Architecturalchoices-Storage"> + + <title>Storage</title> + <para> + The portal framework stores page compositions, portlet preferences, gadget code in a database through a Java Content Repository (JCR) API. A set of database servers and JDBC connectors are part of our quality assurance cycles and the certified environments are mentioned + <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">here</ulink> + . + </para> + <para>It is important to choose one of the combination or check with a Red Hat contact for specific environments that would differ from this list.</para> + <para>The database schema will be automatically created during the very first startup of the website and then it is required that the database users has sufficient rights to create tables. This privilege can be revoked after the initial startup, also the database content can be exported and imported in a new server. This makes the installation of the product very easy in most cases.</para> + <para>We do not provide additional recommendation to choose a database server over another as long as it is part of our certified environment.</para> + <para>As said earlier content is stored through a JCR API, RDBMS aren't a great fit to store large files and it is possible to configure eXo JCR to store such files in the filesystem instead of database, metadata about the files would still be stored into the database. Note that if the website is running on a cluster the filesystem will need to be accessible from all nodes and a NFS solution needs to be setup. For more details see the notion of "value storage" in the reference guide.</para> </section> - - <section id="sect-Developer_Guide-Architectural_choices-Cluster"> - <title>Cluster</title> - <para> - Clustering for failover or load-balancing requirements requires to spend more time configuring it for your environment, we made it easy to handle common situations though. There is a cost associated to clustering (JBoss Enterprise Portal Platform &VY; has some optimization when running on a single node) but the product is designed to linearly scale up so that same performance is added every time a new node is added. All critical parts are kept in sync among nodes and the less critical ones left aside to achieve better performance. It will be equally critical that applications developed for the final websites pay the same attention when it comes to replicate data across a cluster of nodes. - </para> - <para> - The number of nodes will vary a lot depending on the applications developed and used on the final website. We recommend to do early performance analysis with tools such as JMeter, Grinder etc to measure the impact of heavy loads. - </para> - <para> - It is usually recommended to run a cluster to achieve high availability. - </para> - + <section id="sid-7372876_GDG-Architecturalchoices-Cluster"> + + <title>Cluster</title> + <para>Clustering for failover or load-balancing requirements requires to spend more time configuring it for your environment, we made it easy to handle common situations though. There is a cost associated to clustering (EPP 5.2 has some optimization when running on a single node) but the product is designed to linearly scale up so that same performance is added every time a new node is added. All critical parts are kept in sync among nodes and the less critical ones left aside to achieve better performance. It will be equally critical that applications developed for the final websites pay the same attention when it comes to replicate data across a cluster of nodes.</para> + <para>The number of nodes will vary a lot depending on the applications developed and used on the final website. We recommend to do early performance analysis with tools such as JMeter, Grinder etc to measure the impact of heavy loads.</para> + <para>It is usually recommended to run a cluster to achieve high availability.</para> </section> - - <section id="sect-Developer_Guide-Architectural_choices-SSO"> - <title>SSO</title> - <para> - If the website is part of a more global infrastructure with various components (the website being one of several), it may be in the benefit of users to put a Single-Sign-On solution in place among them. Various SSO solutions are supported by JBoss Enterprise Portal Platform &VY; as seen <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">here</ulink> . In some cases it can be better to have the token manager service on a specific server. - </para> - <para> - Summary - </para> - <para> - By now you should know what infrastructure you will need: - </para> - <para> - - A database - </para> - <para> - - Optionally LDAP, depending on your choice - </para> - <para> - - Optionally NFS, depending on the configuration (mandatory on a cluster with default settings: -  - </para> - <para> - - Optionally an SSO token service - </para> - <para> - - Optionally, a cluster of nodes - </para> - <para> - Here is an example of the simplest setup: - </para> - <figure id="figu-Developer_Guide-SSO-Simple_Infrastructure"> - <title>Simple Infrastructure</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372876/simpleinfra.png" width="444" /> - </imageobject> - - </mediaobject> - - </figure> - <para> - Here is an example of a more complex setup: - </para> - <figure id="figu-Developer_Guide-SSO-Complex_Infrastructure"> - <title>Complex Infrastructure</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372876/complexinfra.png" width="444" /> - </imageobject> - - </mediaobject> - - </figure> - + <section id="sid-7372876_GDG-Architecturalchoices-SSO"> + + <title>SSO</title> + <para> + If the website is part of a more global infrastructure with various components (the website being one of several), it may be in the benefit of users to put a Single-Sign-On solution in place among them. Various SSO solutions are supported by EPP 5.2 as seen + <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">here</ulink> + . In some cases it can be better to have the token manager service on a specific server. + </para> + <para>Summary</para> + <para>By now you should know what infrastructure you will need:</para> + <para>- A database</para> + <para>- Optionally LDAP, depending on your choice</para> + <para>- Optionally NFS, depending on the configuration (mandatory on a cluster with default settings: TODO: More QA on a setup without NFS)</para> + <para>- Optionally an SSO token service</para> + <para>- Optionally, a cluster of nodes</para> + <para>Here is an example of the simplest setup:</para> + <figure> +<title></title> + <mediaobject> + <imageobject> + <imagedata fileref="images/7372876/simpleinfra.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Here is an example of a more complex setup:</para> + <figure> +<title></title> + <mediaobject> + <imageobject> + <imagedata fileref="images/7372876/complexinfra.png"/> + </imageobject> + </mediaobject> + </figure> </section> - - -</chapter> - + </chapter> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-3-GDG_Design_choices.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-3-GDG_Design_choices.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-3-GDG_Design_choices.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -1,177 +1,122 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> -<chapter id="chap-Developer_Guide-Design_choices"> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="sid-7372952"> + <title>Design choices</title> - <para> - Now that the main components of the architecture has been decided, choices must be made on the overall design. - </para> - <section id="sect-Developer_Guide-Design_choices-Dashboards"> - <title>Dashboards</title> - <para> - User dashboards may be very costly in a website, as each user will have the opportunity to design his own personal website, it comes with the cost of storing all that information. Efforts have been made (and are still made) to reduce this cost, but there will always be an overhead. + <para>Now that the main components of the architecture has been decided, choices must be made on the overall design.</para> + <section id="sid-7372952_GDG-Designchoices-Dashboards"> + + <title>Dashboards</title> + <para>User dashboards may be very costly in a website, as each user will have the opportunity to design his own personal website, it comes with the cost of storing all that information. Efforts have been made (and are still made) to reduce this cost, but there will always be an overhead.</para> + <para>This overhead might be hard to estimate as this will depend a lot on how the users will navigate the website, maybe only a minority will use this functionality, or maybe the website is only made of dashboards. In any case the impact of making this feature available must be measured by:</para> + <itemizedlist> + <listitem> + <para>estimating the number of dashboards and pages that will be created</para> + </listitem> + <listitem> + <para>observing the impact on the database (through JCR) in terms of size</para> + </listitem> + </itemizedlist> + </section> + <section id="sid-7372952_GDG-Designchoices-JCRindexreplicationforclustersetup"> + + <title>JCR index replication for cluster setup</title> + <para> + The JCR implementation uses Apache Lucene for indexing the data. The indexes are used to search for content (It can be page nodes or WCM content for instance). + + Lucene isn't cluster-ready but on a cluster, each node will need to be able to search for content and will need to have access to the lucene indexes. + + When is comes to searching, there is always a tradeoff. Everyone would want to achieve all of the following: + </para> + <itemizedlist> + <listitem> + <para>Fast to search</para> + </listitem> + <listitem> + <para>Fast to index</para> + </listitem> + <listitem> + <para>Same search result on each node at the same time</para> + </listitem> + <listitem> + <para>No need to rebuild the index ever (No inconsistency)</para> + </listitem> + <listitem> + <para>No impact on overall performance</para> + </listitem> + <listitem> + <para>Easy to setup (no infrastructure change)</para> + </listitem> + </itemizedlist> + <para>But there are choices to be made. The JCR implementation used by EPP (eXo JCR) makes it possible to configure the storage and retrieval of indexes according to architect's choice on where it is acceptable to lose-up some constraints. For configuration details please refer to the EPP Reference Guide.</para> + <section id="sid-7372952_GDG-Designchoices-Standaloneindex"> + + <title>Standalone index</title> + <para> + This is only for a non-cluster environment, this is obviously the easiest setup, with a combination of in-memory and file based indexes. There is no replication involved so any entry can be found by a search as soon as they are created. + <figure> +<title>TODO Gliffy image title empty</title> +<mediaobject> +<imageobject> + <imagedata fileref="images/7372952/diagram-standalone-index.png"/> + </imageobject> +</mediaobject> +</figure> </para> - <para> - This overhead might be hard to estimate as this will depend a lot on how the users will navigate the website, maybe only a minority will use this functionality, or maybe the website is only made of dashboards. In any case the impact of making this feature available must be measured by: + </section> + <section id="sid-7372952_GDG-Designchoices-Localindex"> + + <title>Local index</title> + <para> + This environment is easy to setup, each node keeps a local copy of the full indexes so that when a search is requested on a node, there is no network communication requested. The downside is that when a node indexes an item, it requires to replicate that index on each and every node. If a node is unavailable at that time, it may miss an index update request and then the different nodes may be inconsistent. + + Also when a node is added it has to recreate it's own full index. + + An alternative to this setup is to ask a node to retrieve the info from a coordinator on each search, it makes the startup of the new node faster but impacts its performance during the runtime. This setup is new to EPP 5.2. </para> - <itemizedlist> - <listitem> - <para> - Estimating the number of dashboards and pages that will be created - </para> - - </listitem> - <listitem> - <para> - Observing the impact on the database (through JCR) in terms of size - </para> - - </listitem> - - </itemizedlist> - - </section> - - <section id="sect-Developer_Guide-Design_choices-JCR_index_replication_for_cluster_setup"> - <title>JCR index replication for cluster setup</title> - <para> - The JCR implementation uses Apache Lucene for indexing the data. The indexes are used to search for content (it can be page nodes or WCM content for instance). Lucene is not cluster-ready but on a cluster, each node will need to be able to search for content and will need to have access to the lucene indexes. All search implementations would want to achieve all of the following: + <para> + <figure> +<title>TODO InformalFigure image title empty</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/7372952/diagram-local-index.png"/> + </imageobject> + </mediaobject> + </figure> </para> - <itemizedlist> - <listitem> - <para> - Fast to search - </para> - - </listitem> - <listitem> - <para> - Fast to index - </para> - - </listitem> - <listitem> - <para> - Same search result on each node at the same time - </para> - - </listitem> - <listitem> - <para> - No need to rebuild the index ever (No inconsistency) - </para> - - </listitem> - <listitem> - <para> - No impact on overall performance - </para> - - </listitem> - <listitem> - <para> - Easy to setup (no infrastructure change) - </para> - - </listitem> - + </section> + <section id="sid-7372952_GDG-Designchoices-Sharedindex"> + + <title>Shared index</title> + <para> + In this setup there is a unique index created and shared among all nodes. It requires to configure the infrastructure so that a network file system is installed where all nodes can read content. + + Advantages: + </para> + <itemizedlist> + <listitem> + <para>Consistency, all the nodes see the same data</para> + </listitem> </itemizedlist> - <para> - The JCR implementation used by JBoss Enterprise Portal Platform (eXo JCR) makes it possible to configure the storage and retrieval of indexes according to architect's choice on where it is acceptable to lose-up some constraints. For configuration details please refer to the JBoss Enterprise Portal Platform Reference Guide. + <para>Drawback:</para> + <itemizedlist> + <listitem> + <para>Requires a highly available NFS setup (NFS 4 is recommended)</para> + </listitem> + <listitem> + <para>More network communication</para> + </listitem> + </itemizedlist> + <para> + <figure> +<title>TODO InformalFigure image title empty</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/7372952/diagram-shared-index.png"/> + </imageobject> + </mediaobject> + </figure> </para> - <section id="sect-Developer_Guide-JCR_index_replication_for_cluster_setup-Standalone_index"> - <title>Standalone index</title> - <para> - This is only for a non-cluster environment, this is obviously the easiest setup, with a combination of in-memory and file based indexes. There is no replication involved so any entry can be found by a search as soon as they are created. - <figure id="figu-Developer_Guide-Standalone_index-Standalone_Index"> - <title>Standalone Index</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372952/diagram-standalone-index.png" /> - </imageobject> - - </mediaobject> - - </figure> - - </para> - - </section> - - <section id="sect-Developer_Guide-JCR_index_replication_for_cluster_setup-Local_index"> - <title>Local index</title> - <para> - This environment is easy to setup, each node keeps a local copy of the full indexes so that when a search is requested on a node, there is no network communication requested. The downside is that when a node indexes an item, it requires to replicate that index on each and every node. If a node is unavailable at that time, it may miss an index update request and then the different nodes may be inconsistent. Also when a node is added it has to recreate its own full index. An alternative to this setup is to ask a node to retrieve the information from a coordinator on each search, it makes the startup of the new node faster but impacts its performance during the runtime. This setup is new to JBoss Enterprise Portal Platform &VY;. - </para> - <para> - <figure id="figu-Developer_Guide-Local_index-Local_Index"> - <title>Local Index</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372952/diagram-local-index.png" width="444" /> - </imageobject> - - </mediaobject> - - </figure> - - </para> - - </section> - - <section id="sect-Developer_Guide-JCR_index_replication_for_cluster_setup-Shared_index"> - <title>Shared index</title> - <para> - In this setup there is a unique index created and shared among all nodes. It requires to configure the infrastructure so that a network file system is installed where all nodes can read content. Advantages: - </para> - <itemizedlist> - <listitem> - <para> - Consistency, all the nodes see the same data - </para> - - </listitem> - - </itemizedlist> - <para> - Drawback: - </para> - <itemizedlist> - <listitem> - <para> - Requires a highly available NFS setup (NFS 4 is recommended) - </para> - - </listitem> - <listitem> - <para> - More network communication - </para> - - </listitem> - - </itemizedlist> - <para> - <figure id="figu-Developer_Guide-Shared_index-Shared_Index"> - <title>Shared Index</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372952/diagram-shared-index.png" width="444" /> - </imageobject> - - </mediaobject> - - </figure> - - </para> - - </section> - - + </section> </section> - - -</chapter> - + </chapter> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-4-GDG_Portal_Development.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -1,100 +1,79 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> -<chapter id="chap-Developer_Guide-Portal_Development"> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="sid-8094155"> + <title>Portal Development</title> - <section id="sect-Developer_Guide-Portal_Development-Portal_containers"> - <title>Portal containers</title> - <para> - In a single instance (or cluster) of JBoss Enterprise Portal Platform, multiple portals can be running and share resources with other portals with two level of granularities: - </para> - <itemizedlist> - <listitem> - <para> - Portal Containers: A portal container can host multiple sites, and an JBoss Enterprise Portal Platform instance can host multiple portal containers - </para> - - </listitem> - <listitem> - <para> - Site: A site can have a unique identity, with its own skin applied, set of pages... - </para> - - </listitem> - - </itemizedlist> - <para> - The biggest granularity is what is called "Portal Containers", a Portal Container can host multiple "Sites". Those two components have a unique identifier that can be found in the default URL Mapping according to the following scheme: <ulink url="http://localhost:8080/" /> <portalcontainer>/<site> - </para> - <para> - When creating a website, it is possible to create a portal container from scratch or extend an existing one. It is then possible to extend the portal container which is accessed at <ulink url="http://localhost:8080/portal" /> on the out of the box solution, this is the recommended way. While running multiple portal containers is possible, it's usually better to keep those on separate installation, note that multiple websites can run in a single portal container and share some services. - </para> - <para> - By providing an extension you can benefit from the portal provided by JBoss Enterprise Portal Platform and be able to customize the parts you want. The benefits over directly modifying the shipped files is that it will make the updates much easier (By just replacing the archives provided by JBoss Enterprise Portal Platform). - <figure id="figu-Developer_Guide-Portal_containers-Portal_Extension_Structure"> - <title>Portal Extension Structure</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372962/portalextensionstructure.png" width="444" /> - </imageobject> - - </mediaobject> - - </figure> - - </para> - <section id="sect-Developer_Guide-Portal_containers-Portal_extension"> - <title>Portal extension</title> - <para> - A portal extension is packaged as an Enterprise ARchive (EAR), a configuration file allows to define which services are required and by ordering those, it is possible to modify some elements. It can be a configuration setting, a translation, a visual template, a page to add... - </para> - <para> - Portal extensions can shadow existing services, a portal will usually be composed of various extensions, each of them usually add services. - <figure id="figu-Developer_Guide-Portal_extension-Portal_Extensions"> - <title>Portal Extensions</title> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/7372962/portalExtensions.png" width="444" /> - </imageobject> - - </mediaobject> - - </figure> - In a portal extension, elements are shadowed by using the same directory location, so if one wants to rewrite the groovy template of the HomePagePortlet which is located in: gatein.ear/02portal.war/templates/groovy/webui/component/UIHomePagePortlet.gtmpl it would be located in an extension such as myExtension/myWar.war/templates/groovy/webui/component/UIHomePagePortlet.gtmpl. The ordering will be defined by the portal extension configuration. - </para> - - </section> + <section id="sid-7372962"> + + <title>Portal containers</title> + <para>In a single instance (or cluster) of EPP, multiple portals can be running and share resources with other portals with two level of granularities:</para> + <itemizedlist> + <listitem> + <para>Portal Containers: A portal container can host multiple sites, and an EPP instance can host multiple portal containers</para> + </listitem> + <listitem> + <para>Site: A site can have a unique identity, with its own skin applied, set of pages...</para> + </listitem> + </itemizedlist> + <para> + The biggest granularity is what is called "Portal Containers", a Portal Container can host multiple "Sites". Those two components have a unique identifier that can be found in the default URL Mapping according to the following scheme: + <ulink url="http://localhost:8080/"/> + <portalcontainer>/<site> + </para> + <para> + When creating a website, it is possible to create a portal container from scratch or extend an existing one. It is then possible to extend the portal container which is accessed at + <ulink url="http://localhost:8080/portal"/> + on the out of the box solution, this is the recommended way. While running multiple portal containers is possible, it's usually better to keep those on separate installation, note that multiple websites can run in a single portal container and share some services. + </para> + <para> + By providing an extension you can benefit from the portal provided by EPP and be able to customize the parts you want. The benefits over directly modifying the shipped files is that it will make the updates much easier (By just replacing the archives provided by EPP). + <figure> +<title>TODO Gliffy image title empty</title> +<mediaobject> +<imageobject> + <imagedata fileref="images/7372962/portalextensionstructure.png"/> + </imageobject> +</mediaobject> +</figure> + </para> + <section id="sid-7372962_GDG-Portalcontainers-Portalextension"> - - </section> - - <section id="sect-Developer_Guide-Portal_Development-Visual_identity"> - <title>Visual identity</title> - <para> - A portal visual identity will be made of the HTML produced by the result of the portal aggregation (the components that makes a page like columns, rows combined with the content produced by the portlets) and associated CSS files. + <title>Portal extension</title> + <para>A portal extension is packaged as an Enterprise ARchive (EAR), a configuration file allows to define which services are required and by ordering those, it is possible to modify some elements. It can be a configuration setting, a translation, a visual template, a page to add...</para> + <para> + Portal extensions can shadow existing services, a portal will usually be composed of various extensions, each of them usually add services. + <figure> +<title>TODO Gliffy image title empty</title> +<mediaobject> +<imageobject> + <imagedata fileref="images/7372962/portalExtensions.png"/> + </imageobject> +</mediaobject> +</figure> + In a portal extension, elements are shadowed by using the same directory location, so if one wants to rewrite the groovy template of the HomePagePortlet which is located in: gatein.ear/02portal.war/templates/groovy/webui/component/UIHomePagePortlet.gtmpl it would be located in an extension such as myExtension/myWar.war/templates/groovy/webui/component/UIHomePagePortlet.gtmpl. The ordering will be defined by the portal extension configuration. </para> - <para> - JBoss Enterprise Portal Platform allows to deploy multiple skins which consists of CSS files, it makes it possible to apply styling on the page compositions and components of a page (Portlets). Different skins can be applied to the different websites, also if made available to the users, they can choose their preferred skin. - </para> - <section id="sect-Developer_Guide-Visual_identity-Customizing_the_login_page"> - <title>Customizing the login page</title> - <para> - When accessing a page that requires privileges, a login page is showing up, that page can be customized by using an extension. To do so it would be enough to copy the file located at <filename>gatein.ear/02portal.war/login/jsp/login.jsp</filename> and include it in the portal extension such as <filename>myExtension.ear/myWar.war/login/jsp/login.jsp</filename>. - </para> - <para> - All the logic must be carefully kept in the login page so that the portal will keep working as it should. - </para> - <para> - To modify the modal window which pops up when the user decides to sign-in, the extension would have a modified copy of <filename>gatein.ear/02portal.war/groovy/portal/webui/UILoginForm.gtmpl</filename> - </para> - - </section> + </section> + </section> + <section id="sid-8094158"> + + <title>Visual identity</title> + <para>A portal visual identity will be made of the HTML produced by the result of the portal aggregation (the components that makes a page like columns, rows combined with the content produced by the portlets) and associated CSS files.</para> + <para>EPP allows to deploy multiple skins which consists of CSS files, it makes it possible to apply styling on the page compositions and components of a page (Portlets). Different skins can be applied to the different websites, also if made available to the users, they can choose their preferred skin.</para> + <section id="sid-8094158_GDG-Visualidentity-Customizingtheloginpage"> - + <title>Customizing the login page</title> + <para>When accessing a page that requires privileges, a login page is showing up, that page can be customized by using an extension. To do so it would be enough to copy the file located at:</para> + <example> + <title>Login JSP</title> + <programlisting>gatein.ear/02portal.war/login/jsp/login.jsp</programlisting> + </example> + <para>and include it in the portal extension such as myExtension.ear/myWar.war/login/jsp/login.jsp</para> + <para>All the logic must be carefully kept in the login page so that the portal will keep working as it should.</para> + <para>To modify the modal window which pops up when the user decides to sign-in, the extension would have a modified copy of:</para> + <example> + <title>Login Form</title> + <programlisting>gatein.ear/02portal.war/groovy/portal/webui/UILoginForm.gtmpl</programlisting> + </example> + </section> </section> - - -</chapter> - + </chapter> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml =================================================================== --- epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml 2011-11-24 00:46:44 UTC (rev 8132) +++ epp/docs/branches/5.2/Developer_Guide/en-US/chapter-5-GDG_Application_development.xml 2011-11-24 03:30:37 UTC (rev 8133) @@ -1,48 +1,33 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> -<chapter id="chap-Developer_Guide-Application_development"> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> +<chapter id="sid-819803"> + <title>Application development</title> - <section id="sect-Developer_Guide-Application_development-Gadget_Development"> - <title>Gadget Development</title> - <section id="sect-Developer_Guide-Gadget_Development-Introduction"> - <title>Introduction</title> - <para> - In the context of JBoss Enterprise Portal Platform, gadgets are those as defined by the Google OpenSocial specifications. Since JBoss Enterprise Portal Platform 5.2, the portal framework includes Apache Shindig 2.0 which is made to support the version 0.9 and 1.0 of OpenSocial. - </para> - <para> - Within a portal it is possible to embed any OpenSocial gadget on a page or within the user dashboards, gadgets can be added to the application registry, or links can be added within the mini-composer (see the User Guide). - </para> - - </section> + <section id="sid-819807"> + + <title>Gadget Development</title> + <section id="sid-819807_GDG-GadgetDevelopment-Introduction"> - <section id="sect-Developer_Guide-Gadget_Development-Developing_Gadgets"> - <title>Developing Gadgets</title> - <para> - OpenSocial gadgets are made of standard HTML and javascript. The container offers an API for which the documentation is available <ulink url="http://opensocial-resources.googlecode.com/svn/spec/1.0/Core-Gadget.xml">here</ulink> . - </para> - <para> - Note that unlike portlets, a gadget has very little knowledge of its context (the portal) and its integration within the portal may be more limited (in terms of visual integration for instance). - </para> - <para> - Google Web Toolkit (GWT) applications can also be used as gadgets, it makes it easy to write user-friendly applications. - </para> - - </section> + <title>Introduction</title> + <para>In the context of EPP, gadgets are those as defined by the Google OpenSocial specifications. Since EPP 5.2, the portal framework includes Apache Shindig 2.0 which is made to support the version 0.9 and 1.0 of OpenSocial.</para> + <para>Within a portal it is possible to embed any OpenSocial gadget on a page or within the user dashboards, gadgets can be added to the application registry, or links can be added within the mini-composer (see the User Guide).</para> + </section> + <section id="sid-819807_GDG-GadgetDevelopment-DevelopingGadgets"> - - </section> - - <section id="sect-Developer_Guide-Application_development-Portlet_Development"> - <title>Portlet Development</title> - <para> - ToDo. + <title>Developing Gadgets</title> + <para> + OpenSocial gadgets are made of standard HTML and javascript. The container offers an API for which the documentation is available + <ulink url="http://opensocial-resources.googlecode.com/svn/spec/1.0/Core-Gadget.xml">here</ulink> + . </para> - + <para>Note that unlike portlets, a gadget has very little knowledge of its context (the portal) and its integration within the portal may be more limited (in terms of visual integration for instance).</para> + <para>While Google Web Toolkit (GWT) applications can also technically be used as gadgets and makes it easy to write user-friendly applications, we do not recommend its usage as its support can be limited and Google's strategy to keep GWT applications running as gadgets cannot clearly be established. Consequently GWT applications are not supported by the EPP support agreement.</para> + </section> </section> - - -</chapter> - + <section id="sid-819805"> + + <title>Portlet Development</title> + <para>JBoss Enterprise Portal interface is fully customized with applications called portlets. Application development can be done by using the plain Portlet specification (JSR-286) (See the "Portlet Primer" chapter in the reference guide) but it is also possible to use the JBoss Portlet Bridge to write applications with JSF and/or RichFaces and/or Seam, see the "Getting started with JBoss Portlet Bridge" chapter of the reference guide.</para> + <para>Depending on the complexity of the application and the familiarity of the team with JSF, one approach or the other can be the right choice for your team.</para> + </section> + </chapter> Modified: epp/docs/branches/5.2/Developer_Guide/en-US/images/7372876/complexinfra.png =================================================================== (Binary files differ)

13 years, 1 month

1
0
0 / 0

gatein SVN: r8132 - epp/docs/branches/5.2/Release_Notes/en-US.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2011-11-23 19:46:44 -0500 (Wed, 23 Nov 2011) New Revision: 8132 Added: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.ent epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml Removed: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.ent epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml Log: Refactored for actual EPP 5.2.0 release notes Deleted: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.ent =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.ent 2011-11-23 23:47:47 UTC (rev 8131) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.ent 2011-11-24 00:46:44 UTC (rev 8132) @@ -1,14 +0,0 @@ - -<!ENTITY PRODUCT "JBoss Site Publisher"> - - -<!ENTITY BOOKID "Site Publisher Release Notes"> - - -<!ENTITY YEAR "2011"> -<!ENTITY HOLDER "Red Hat, Inc"> - - -<!ENTITY VX "5"> -<!ENTITY VY "5.2"> -<!ENTITY VZ "5.2.0"> Deleted: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml 2011-11-23 23:47:47 UTC (rev 8131) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml 2011-11-24 00:46:44 UTC (rev 8132) @@ -1,268 +0,0 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_BETA_Release_Notes.ent"> -%BOOK_ENTITIES; -]> -<book> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> - <chapter id="Release_Notes-Introduction"> - <title>Introduction</title> - <para>JBoss Enterprise Portal Platform offers an intuitive, easy to manage user interface and a proven core infrastructure to enable organizations to quickly build dynamic web sites in a highly reusable way. By bringing the principals of Open Choice to the presentation layer, JBoss Enterprise Portal Platform 5 maximizes existing skills and technology investments. - </para> - <para>By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache, JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. As well, </para> - <para>JBoss Enterprise Portal Platform &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.</para> - </chapter> - <chapter> - <title>Upgraded Components</title> - <formalpara> - <title>New Components</title> - <para>The following new components warrant special mention.</para> - </formalpara> - <variablelist> - <varlistentry> - <term>Site Migration Utilities</term> - <listitem> - <para>This new functionality is designed to improve the experience of managing unique sites or groups of pages as they progress from the development to production life cycle. The Migration utility has multiple administrative interfaces to support the requirements of different enterprises.</para> - </listitem> - </varlistentry> - <varlistentry> - <term>Site Management Utilities</term> - <listitem> - <para>The new functionality is provided to assist administrators in performing routine tasks. This includes the release of IDM cache, gathering of performance metrics and other processes related to managing the portal server. </para> - </listitem> - </varlistentry> - </variablelist> - <formalpara> - <title>Updated Components</title> - <para>The following updated components warrant special mention.</para> - </formalpara> - <variablelist> - <varlistentry> - <term>Java Content Respostory</term> - <listitem> - <para>This updated release of the eXo Java Content Repository (JCR) has been updated to a newer version designed to improve the performance and scalability of large portal sites. </para> - </listitem> - </varlistentry> - </variablelist> - <note> - <para>For detailed information about component versions included in this release, refer to <xref linkend="Release_Notes-Component_Features"/></para> - </note> - </chapter> - <chapter id="Release_Notes-Component_Features"> - <title>Component Versions </title> - <para><remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705 (version 10)</remark></para> - <table frame="all" pgwide="1"> - <title>Component Versions</title> - <tgroup cols="2" colsep="1"> - <colspec colnum="1"/> - <colspec colnum="2"/> - <thead> - <row> - <entry>Component</entry> - <entry>Version</entry> - </row> - </thead> - <tbody> - <row> - <entry>EAP</entry> - <entry>5.1.1-GA</entry> - </row> - <row> - <entry>eXo junit</entry> - <entry>1.2.1-GA</entry> - </row> - <row> - <entry>eXo kernel</entry> - <entry>2.3.3-GA</entry> - </row> - <row> - <entry>eXo Core</entry> - <entry>2.4.3-GA</entry> - </row> - <row> - <entry>eXo WS</entry> - <entry>2.2.3-GA</entry> - </row> - <row> - <entry>eXo JCR</entry> - <entry>1.14.3-GA</entry> - </row> - <row> - <entry>Apache Shindig</entry> - <entry>2.0.2</entry> - </row> - <row> - <entry>Simple Captcha</entry> - <entry>1.1.1-GA-Patch01</entry> - </row> - <row> - <entry>GateIn Parent</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn dep</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn Common</entry> - <entry>2.0.4-GA</entry> - </row> - <row> - <entry>GateIn WCI</entry> - <entry>2.1.0-GA</entry> - </row> - <row> - <entry>GateIn PC</entry> - <entry>2.3.0-GA</entry> - </row> - <row> - <entry>GateIn WSRP</entry> - <entry>2.1.0-EPP520-GA</entry> - </row> - <row> - <entry>GateIn MOP</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn SSO</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>PicketLink IDM</entry> - <entry>1.3.0.GA</entry> - </row> - <row> - <entry>Chromattic</entry> - <entry>1.1.1</entry> - </row> - <row> - <entry>Portlet Bridge</entry> - <entry>2.2.0.GA.EPP520</entry> - </row> - <row> - <entry>Seam</entry> - <entry>2.2.4.EAP5</entry> - </row> - <row> - <entry>Richfaces</entry> - <entry>3.3.1.SP3</entry> - </row> - <row> - <entry>Groovy</entry> - <entry>1.7.6</entry> - </row> - <row> - <entry>Commons DBCP</entry> - <entry>1.4</entry> - </row> - <row> - <entry>Commons IO</entry> - <entry>1.4</entry> - </row> - <row> - <entry>Commons Lang</entry> - <entry>2.6</entry> - </row> - <row> - <entry>HSQLDB</entry> - <entry>2.0.0</entry> - </row> - <row> - <entry>JBoss Cache</entry> - <entry>3.2.7</entry> - </row> - <row> - <entry>GateIn Management</entry> - <entry>1.0.0-GA</entry> - </row> - </tbody> - </tgroup> - </table> - </chapter> - <chapter id="Release_Notes-Installation"> - <title>Installation</title> - <para> - The JBoss Enterprise Portal Platform <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. - </para> - <para> - The Installation Guide can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. - </para> - </chapter> - <chapter id="Release_Notes-Issues_Resolved_In_Production"> - <title>Resolved Issues </title> - <para> - The following issues were resolved in this release of JBoss Enterprise Portal Platform. </para> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml"/> - </chapter> - <chapter id="Release_Notes-Known_Issues"> - <title>Known Issues </title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml" encoding="XML"/> - </chapter> - <chapter id="Release_Notes-Documentation"> - <title>Documentation</title> - <para> - An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. - </para> - </chapter> - <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> - <title> Product Support and License Website Links </title> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> - <title>Support Processes</title> - <para> - <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_"> - <title> Production Support Scope of Coverage </title> - <para> - <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_"> - <title> Production Support Service Level Agreement </title> - <para> - <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> - <title> Developer Support Scope of Coverage </title> - <para> - <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_"> - <title> Developer Support Service Level Agreement </title> - <para> - <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_"> - <title> Product Update and Support Policy by Product </title> - <para> - <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink> - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> - <title> JBoss End User License Agreement </title> - <para> - <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink> - </para> - </formalpara> - </chapter> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> -</book> Copied: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.ent (from rev 8131, epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.ent) =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.ent (rev 0) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.ent 2011-11-24 00:46:44 UTC (rev 8132) @@ -0,0 +1,14 @@ + +<!ENTITY PRODUCT "JBoss Site Publisher"> + + +<!ENTITY BOOKID "Site Publisher Release Notes"> + + +<!ENTITY YEAR "2011"> +<!ENTITY HOLDER "Red Hat, Inc"> + + +<!ENTITY VX "5"> +<!ENTITY VY "5.2"> +<!ENTITY VZ "5.2.0"> Copied: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml (from rev 8131, epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_BETA_Release_Notes.xml) =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml (rev 0) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-11-24 00:46:44 UTC (rev 8132) @@ -0,0 +1,268 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_Release_Notes.ent"> +%BOOK_ENTITIES; +]> +<book> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <chapter id="Release_Notes-Introduction"> + <title>Introduction</title> + <para>JBoss Enterprise Portal Platform offers an intuitive, easy to manage user interface and a proven core infrastructure to enable organizations to quickly build dynamic web sites in a highly reusable way. By bringing the principals of Open Choice to the presentation layer, JBoss Enterprise Portal Platform 5 maximizes existing skills and technology investments. + </para> + <para>By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache, JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. As well, </para> + <para>JBoss Enterprise Portal Platform &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.</para> + </chapter> + <chapter> + <title>Upgraded Components</title> + <formalpara> + <title>New Components</title> + <para>The following new components warrant special mention.</para> + </formalpara> + <variablelist> + <varlistentry> + <term>Site Migration Utilities</term> + <listitem> + <para>This new functionality is designed to improve the experience of managing unique sites or groups of pages as they progress from the development to production life cycle. The Migration utility has multiple administrative interfaces to support the requirements of different enterprises.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Site Management Utilities</term> + <listitem> + <para>The new functionality is provided to assist administrators in performing routine tasks. This includes the release of IDM cache, gathering of performance metrics and other processes related to managing the portal server. </para> + </listitem> + </varlistentry> + </variablelist> + <formalpara> + <title>Updated Components</title> + <para>The following updated components warrant special mention.</para> + </formalpara> + <variablelist> + <varlistentry> + <term>Java Content Respostory</term> + <listitem> + <para>This updated release of the eXo Java Content Repository (JCR) has been updated to a newer version designed to improve the performance and scalability of large portal sites. </para> + </listitem> + </varlistentry> + </variablelist> + <note> + <para>For detailed information about component versions included in this release, refer to <xref linkend="Release_Notes-Component_Features"/></para> + </note> + </chapter> + <chapter id="Release_Notes-Component_Features"> + <title>Component Versions </title> + <para><remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705 (version 10)</remark></para> + <table frame="all" pgwide="1"> + <title>Component Versions</title> + <tgroup cols="2" colsep="1"> + <colspec colnum="1"/> + <colspec colnum="2"/> + <thead> + <row> + <entry>Component</entry> + <entry>Version</entry> + </row> + </thead> + <tbody> + <row> + <entry>EAP</entry> + <entry>5.1.1-GA</entry> + </row> + <row> + <entry>eXo junit</entry> + <entry>1.2.1-GA</entry> + </row> + <row> + <entry>eXo kernel</entry> + <entry>2.3.3-GA</entry> + </row> + <row> + <entry>eXo Core</entry> + <entry>2.4.3-GA</entry> + </row> + <row> + <entry>eXo WS</entry> + <entry>2.2.3-GA</entry> + </row> + <row> + <entry>eXo JCR</entry> + <entry>1.14.3-GA</entry> + </row> + <row> + <entry>Apache Shindig</entry> + <entry>2.0.2</entry> + </row> + <row> + <entry>Simple Captcha</entry> + <entry>1.1.1-GA-Patch01</entry> + </row> + <row> + <entry>GateIn Parent</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>GateIn dep</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>GateIn Common</entry> + <entry>2.0.4-GA</entry> + </row> + <row> + <entry>GateIn WCI</entry> + <entry>2.1.0-GA</entry> + </row> + <row> + <entry>GateIn PC</entry> + <entry>2.3.0-GA</entry> + </row> + <row> + <entry>GateIn WSRP</entry> + <entry>2.1.0-EPP520-GA</entry> + </row> + <row> + <entry>GateIn MOP</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>GateIn SSO</entry> + <entry>1.1.0-GA</entry> + </row> + <row> + <entry>PicketLink IDM</entry> + <entry>1.3.0.GA</entry> + </row> + <row> + <entry>Chromattic</entry> + <entry>1.1.1</entry> + </row> + <row> + <entry>Portlet Bridge</entry> + <entry>2.2.0.GA.EPP520</entry> + </row> + <row> + <entry>Seam</entry> + <entry>2.2.4.EAP5</entry> + </row> + <row> + <entry>Richfaces</entry> + <entry>3.3.1.SP3</entry> + </row> + <row> + <entry>Groovy</entry> + <entry>1.7.6</entry> + </row> + <row> + <entry>Commons DBCP</entry> + <entry>1.4</entry> + </row> + <row> + <entry>Commons IO</entry> + <entry>1.4</entry> + </row> + <row> + <entry>Commons Lang</entry> + <entry>2.6</entry> + </row> + <row> + <entry>HSQLDB</entry> + <entry>2.0.0</entry> + </row> + <row> + <entry>JBoss Cache</entry> + <entry>3.2.7</entry> + </row> + <row> + <entry>GateIn Management</entry> + <entry>1.0.0-GA</entry> + </row> + </tbody> + </tgroup> + </table> + </chapter> + <chapter id="Release_Notes-Installation"> + <title>Installation</title> + <para> + The JBoss Enterprise Portal Platform <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. + </para> + <para> + The Installation Guide can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. + </para> + </chapter> + <chapter id="Release_Notes-Issues_Resolved_In_Production"> + <title>Resolved Issues </title> + <para> + The following issues were resolved in this release of JBoss Enterprise Portal Platform. </para> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml"/> + </chapter> + <chapter id="Release_Notes-Known_Issues"> + <title>Known Issues </title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml" encoding="XML"/> + </chapter> + <chapter id="Release_Notes-Documentation"> + <title>Documentation</title> + <para> + An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. + </para> + </chapter> + <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> + <title> Product Support and License Website Links </title> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> + <title>Support Processes</title> + <para> + <ulink url="http://www.redhat.com/support/process/">http://www.redhat.com/support/process/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_"> + <title> Production Support Scope of Coverage </title> + <para> + <ulink url="http://www.redhat.com/support/policy/soc/production">http://www.redhat.com/support/policy/soc/production</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_"> + <title> Production Support Service Level Agreement </title> + <para> + <ulink url="http://www.redhat.com/support/policy/sla/production/">http://www.redhat.com/support/policy/sla/production/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_"> + <title> Developer Support Scope of Coverage </title> + <para> + <ulink url="http://www.redhat.com/support/policy/soc/developer/">http://www.redhat.com/support/policy/soc/developer/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_"> + <title> Developer Support Service Level Agreement </title> + <para> + <ulink url="http://www.redhat.com/support/policy/sla/developer/">http://www.redhat.com/support/policy/sla/developer/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_"> + <title> Product Update and Support Policy by Product </title> + <para> + <ulink url="http://www.redhat.com/security/updates/jboss_notes/">http://www.redhat.com/security/updates/jboss_notes/</ulink> + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> + <title> JBoss End User License Agreement </title> + <para> + <ulink url="http://www.redhat.com/licenses/jboss_eula.html">http://www.redhat.com/licenses/jboss_eula.html</ulink> + </para> + </formalpara> + </chapter> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> +</book>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8131 - epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-23 18:47:47 -0500 (Wed, 23 Nov 2011) New Revision: 8131 Modified: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.ent Log: Updated entities file Modified: epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.ent =================================================================== --- epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.ent 2011-11-23 23:46:33 UTC (rev 8130) +++ epp/docs/branches/5.2/PicketLink_IDM_Reference_Guide/en-US/PicketLink_IDM_Reference_Guide.ent 2011-11-23 23:47:47 UTC (rev 8131) @@ -7,7 +7,7 @@  <!ENTITY BZPRODUCT "JBoss Enterprise Portal Platform 5"> <!ENTITY BZCOMPONENT "docs-Installation_Guide"> -<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Enterpri...'>http://bugzilla.redhat.com/</ulink>"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Enterpri...'>http://bugzilla.redhat.com/</ulink>">  <!ENTITY YEAR "2011">

13 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits November 2011