January 2012 - portal-commits - Jboss List Archives

JBoss Portal SVN: r14036 - docs/enterprise/trunk/Release_Notes/en-US.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 23:53:09 -0500 (Wed, 11 Jan 2012) New Revision: 14036 Modified: docs/enterprise/trunk/Release_Notes/en-US/Author_Group.xml docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml Log: Changed file names to match target release Modified: docs/enterprise/trunk/Release_Notes/en-US/Author_Group.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/Author_Group.xml 2012-01-12 04:44:58 UTC (rev 14035) +++ docs/enterprise/trunk/Release_Notes/en-US/Author_Group.xml 2012-01-12 04:53:09 UTC (rev 14036) @@ -1,6 +1,6 @@ <?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 "5.2.0_Release_Notes.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "CP07_Release_Notes.ent"> %BOOK_ENTITIES; ]> <authorgroup> Modified: docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml 2012-01-12 04:44:58 UTC (rev 14035) +++ docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml 2012-01-12 04:53:09 UTC (rev 14036) @@ -1,15 +1,15 @@ <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE articleinfo 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"> +<!ENTITY % BOOK_ENTITIES SYSTEM "CP07_Release_Notes.ent"> %BOOK_ENTITIES; ]> <bookinfo id="arti-Release_Notes-Release_Notes"> - <title>5.2.0 Release Notes</title> + <title>CP07 Release Notes</title> <subtitle>For use with JBoss Enterprise Portal Platform &VZ;.</subtitle> <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>5.2</productnumber> - <edition>5.2.0</edition> - <pubsnumber>101</pubsnumber> + <productnumber>4.3</productnumber> + <edition>4.3.7</edition> + <pubsnumber>1</pubsnumber> <abstract> <para> These release notes contain important information related to JBoss Enterprise Portal Platform &VZ; that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product. Modified: docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent 2012-01-12 04:44:58 UTC (rev 14035) +++ docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent 2012-01-12 04:53:09 UTC (rev 14036) @@ -2,7 +2,7 @@ <!ENTITY PRODUCT "JBoss Enterprise Portal Platform">  -<!ENTITY BOOKID "Release Notes CP07"> +<!ENTITY BOOKID "CP07 Release Notes">  <!ENTITY YEAR "2011"> Modified: docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml 2012-01-12 04:44:58 UTC (rev 14035) +++ docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml 2012-01-12 04:53:09 UTC (rev 14036) @@ -1,5 +1,6 @@ <?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" [ + +<!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 "CP07_Release_Notes.ent"> %BOOK_ENTITIES; ]> Modified: docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml 2012-01-12 04:44:58 UTC (rev 14035) +++ docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml 2012-01-12 04:53:09 UTC (rev 14036) @@ -1,6 +1,6 @@ <?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 "5.2.0_Release_Notes.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "CP07_Release_Notes.ent"> %BOOK_ENTITIES; ]> <appendix id="appe-Release_Notes-Revision_History">

12 years, 3 months

1
0
0 / 0

JBoss Portal SVN: r14035 - in docs/enterprise/trunk/Release_Notes: en-US and 1 other directory.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 23:44:58 -0500 (Wed, 11 Jan 2012) New Revision: 14035 Added: docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml Removed: docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.ent docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.xml Modified: docs/enterprise/trunk/Release_Notes/publican.cfg Log: Changed file names to match target release Deleted: docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.ent =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.ent 2012-01-12 04:29:54 UTC (rev 14034) +++ docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.ent 2012-01-12 04:44:58 UTC (rev 14035) @@ -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: docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.xml 2012-01-12 04:29:54 UTC (rev 14034) +++ docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.xml 2012-01-12 04:44:58 UTC (rev 14035) @@ -1,248 +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_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 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. </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 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 is available in multiple formats from <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. - </para> - </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 13)</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-CP01</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> - <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-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 Links </title> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> - <title>Product Update and Support Processes</title> - <para> - <ulink url="https://access.redhat.com/support/policy/updates/jboss_notes/">https://access.redhat.com/support/policy/updates/jboss_notes/</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, and Service Level Agreement</title> - <para><ulink url="https://access.redhat.com/support/offerings/developer/">https://access.redhat.com/support/offerings/developer/</ulink> - - </para> - </formalpara> - <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> - <title>Certified and Compatible Configurations</title> - <para> - <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">http://www.jboss.com/products/platforms/portals/testedconfigurations/</ulink> - </para> - </formalpara> - </chapter> - <chapter> - <title>New Features</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="feature_requests.xml" encoding="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-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> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> -</book> Copied: docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent (from rev 14034, docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.ent) =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.ent 2012-01-12 04:44:58 UTC (rev 14035) @@ -0,0 +1,14 @@ + +<!ENTITY PRODUCT "JBoss Enterprise Portal Platform"> + + +<!ENTITY BOOKID "Release Notes CP07"> + + +<!ENTITY YEAR "2011"> +<!ENTITY HOLDER "Red Hat, Inc"> + + +<!ENTITY VX "4"> +<!ENTITY VY "4.3"> +<!ENTITY VZ "4.3 CP07"> Copied: docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml (from rev 14034, docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.xml) =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml 2012-01-12 04:44:58 UTC (rev 14035) @@ -0,0 +1,248 @@ +<?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 "CP07_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 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. </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 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 is available in multiple formats from <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. + </para> + </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 13)</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-CP01</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> + <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-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 Links </title> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> + <title>Product Update and Support Processes</title> + <para> + <ulink url="https://access.redhat.com/support/policy/updates/jboss_notes/">https://access.redhat.com/support/policy/updates/jboss_notes/</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, and Service Level Agreement</title> + <para><ulink url="https://access.redhat.com/support/offerings/developer/">https://access.redhat.com/support/offerings/developer/</ulink> + + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> + <title>Certified and Compatible Configurations</title> + <para> + <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">http://www.jboss.com/products/platforms/portals/testedconfigurations/</ulink> + </para> + </formalpara> + </chapter> + <chapter> + <title>New Features</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="feature_requests.xml" encoding="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-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> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> +</book> Modified: docs/enterprise/trunk/Release_Notes/publican.cfg =================================================================== --- docs/enterprise/trunk/Release_Notes/publican.cfg 2012-01-12 04:29:54 UTC (rev 14034) +++ docs/enterprise/trunk/Release_Notes/publican.cfg 2012-01-12 04:44:58 UTC (rev 14035) @@ -7,4 +7,4 @@ #show_remarks: 1 cvs_branch: DOCS-RHEL-6 cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist -cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_Release_Notes-5.2-web-__LANG__ +cvs_pkg: JBoss_Enterprise_Portal_Platform-CP07_Release_Notes-4.3-web-__LANG__

12 years, 3 months

1
0
0 / 0

JBoss Portal SVN: r14034 - in docs/enterprise/trunk: Release_Notes and 2 other directories.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 23:29:54 -0500 (Wed, 11 Jan 2012) New Revision: 14034 Added: docs/enterprise/trunk/Release_Notes/ docs/enterprise/trunk/Release_Notes/en-US/ docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.ent docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.xml docs/enterprise/trunk/Release_Notes/en-US/Author_Group.xml docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml docs/enterprise/trunk/Release_Notes/en-US/feature_requests.old docs/enterprise/trunk/Release_Notes/en-US/feature_requests.xml docs/enterprise/trunk/Release_Notes/en-US/images/ docs/enterprise/trunk/Release_Notes/en-US/images/icon.svg docs/enterprise/trunk/Release_Notes/en-US/known_issues.old docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml docs/enterprise/trunk/Release_Notes/en-US/need_info.old docs/enterprise/trunk/Release_Notes/en-US/need_info.xml docs/enterprise/trunk/Release_Notes/en-US/needinfo.xml docs/enterprise/trunk/Release_Notes/en-US/new_features.xml docs/enterprise/trunk/Release_Notes/en-US/not_documented.xml docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.old docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml docs/enterprise/trunk/Release_Notes/publican.cfg Log: Added new Book Release Note format document Added: docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.ent =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.ent (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.ent 2012-01-12 04:29:54 UTC (rev 14034) @@ -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"> Added: docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/5.2.0_Release_Notes.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,248 @@ +<?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 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. </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 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 is available in multiple formats from <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. + </para> + </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 13)</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-CP01</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> + <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-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 Links </title> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> + <title>Product Update and Support Processes</title> + <para> + <ulink url="https://access.redhat.com/support/policy/updates/jboss_notes/">https://access.redhat.com/support/policy/updates/jboss_notes/</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, and Service Level Agreement</title> + <para><ulink url="https://access.redhat.com/support/offerings/developer/">https://access.redhat.com/support/offerings/developer/</ulink> + + </para> + </formalpara> + <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_"> + <title>Certified and Compatible Configurations</title> + <para> + <ulink url="http://www.jboss.com/products/platforms/portals/testedconfigurations/">http://www.jboss.com/products/platforms/portals/testedconfigurations/</ulink> + </para> + </formalpara> + </chapter> + <chapter> + <title>New Features</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="feature_requests.xml" encoding="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-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> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> +</book> Added: docs/enterprise/trunk/Release_Notes/en-US/Author_Group.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/Author_Group.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/Author_Group.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,15 @@ +<?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 "5.2.0_Release_Notes.ent"> +%BOOK_ENTITIES; +]> +<authorgroup> + <author> + <firstname>Red Hat</firstname> + <surname>Documentation Team</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>Engineering Content Services</orgdiv> + </affiliation> + </author> +</authorgroup> Added: docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,27 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE articleinfo 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; +]> +<bookinfo id="arti-Release_Notes-Release_Notes"> + <title>5.2.0 Release Notes</title> + <subtitle>For use with JBoss Enterprise Portal Platform &VZ;.</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>5.2</productnumber> + <edition>5.2.0</edition> + <pubsnumber>101</pubsnumber> + <abstract> + <para> + These release notes contain important information related to JBoss Enterprise Portal Platform &VZ; that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product. + </para> + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"/> + </imageobject> + </inlinemediaobject> + </corpauthor> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Common_Content/Legal_Notice.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Author_Group.xml"/> +</bookinfo> Added: docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,26 @@ +<?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 "5.2.0_Release_Notes.ent"> +%BOOK_ENTITIES; +]> +<appendix id="appe-Release_Notes-Revision_History"> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>5.2.0-101</revnumber> + <date>Thu Dec 14 2011</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email>jmorgan [at] redhat [dot] com</email> + </author> + <revdescription> + <simplelist> + <member>Release Notes prepared for JBoss Enterprise Portal Platform 5.2.0 GA.</member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </simpara> +</appendix> Added: docs/enterprise/trunk/Release_Notes/en-US/feature_requests.old =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/feature_requests.old (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/feature_requests.old 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,4 @@ + +<para> +There are no Feature Request in this release. +</para> Added: docs/enterprise/trunk/Release_Notes/en-US/feature_requests.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/feature_requests.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/feature_requests.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,333 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<variablelist> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + It is possible to switch portal clusters between UDP and TCP communication modes using a command-line parameter. The -Dgatein.default.jgroups.stack=[tcp | udp] parameter switches EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService) between the two protocols. The functionality is implemented using an adapted, and mutually exclusive implementation of jboss.default.jgroups.stack. + +<note> + <para>This enhancement is based on, but deliberately independent of, the JBoss Enterprise Application Platform parameter. "jboss.default.jgroups.stack" which supports more values by default than Enterprise Portal Platform currently does. The decision to keep the two parameters separate was for upstream compatibility.</para> + </note> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + URL handler support is available in this release. The WCM component uses this feature to support locales as part of the URL. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Performance bottlenecks have been removed when a portal runs with hundreds of navigation nodes. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + In previous releases, navigation node translations had to be managed in language property files. This release allows Navigation nodes to be translated directly through the administration interface. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + It is now possible to define a portlet.xml that describes elements such as filters that need to be applied to all portlets. The file is located in jboss-as/server/[configuration]/conf/gatein/portlet.xml + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + This release upgrades Shindig to version 2.0.2. Shindig is used to embed OpenSocial gadgets. Refer to the Component Versions section for the definitive version featured in this release. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + Web service security between WSRP producers and consumers is available in this release. This enhancement allows for encrypted communication and access to authenticated user content over WSRP. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + This release makes it possible to configure several LDAP servers containing different users with GateIn. In a ReadOnly scenario, the user is searched in all configured sources. In a ReadWrite scenario, the user is created only in the first configured LDAP server, but obtained from all. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + Application registry categories are now cached for better performance. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Each site can now have a site description, which can be accessed and used by the management applications. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + Priority for the loading of skin css files can now be specified in gatein-resources.xml using the css-priority xml element. This allows the css elements to be loaded in a specific order, which can be useful for overriding existing css elements. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + WSRP was previously unavailable for portal extensions. The new WSRP component now properly initializes itself even when started from an extension (as opposed to the default portal container). + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077</ulink> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> + The datasource for JCR is now using managed transactions, and required a change in the datasource descriptor. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + EPP is now partially available in Czech language. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When adding a page to a site, pages are displayed in a drop-down list instead of a free form text field. This makes adding pages more intuitive. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + This release of JBoss Enterprise Portal Platform adds a configurable setting to control whether the 'info bar' which surrounds new portlets is displayed by default. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + In this release, the Single Sign On (SSO) component has been enhanced to support FORM authentication for instances where the user can not get access to SSO authentication sessions (such as a Kerberos ticket). Users can now authenticate manually with the portal-specific username and password as a fall-back. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + Configuring a page is no longer restricted to local portlets. It is now possible to define remote portlets (WSRP) in page descriptors to populate the base data for the page. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + In previous releases, the portal did not indicate it had started clearly in the logs. Changes to core portal code now specifies the portal has started in the logs, and includes the portal version number for reference. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + This release contains enhancements to Gadgets, which, like portlets, can now be integrated on a page definition through XML descriptors. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + The HTML Document Object Module (DOM) has been optimized to achieve better performance when transmitting markup, and has been simplified for faster rendering on recent web browsers. Older browsers such as Internet Explorer will still work, however performance will be degraded. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + The Apache Shindig configuration file has been made more accessible to be modified more easily. It is now part of eXoGadgetServer.war/containers/default/container.js + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + An enhancement to the UserDashboardImpl object now allows dashboard instances to be reused. Dashboards now require less resources to operate correctly. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + Cluster data transportation has been optimized to reduce the number of network connections and threads. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When defining navigation in an XML descriptor, it is now possible to define the strategy to apply during startup. It is possible to "conserve", "insert", "merge" or "rewrite" the content previously imported. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + In this release the default JCR workspace name and system JCR workspace name can now be configured in the configuration.properties file. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + There was no way to determine the Enterprise Portal Platform version, based on what was displayed when starting the portal. An enhancement to UIFooterPortlet.gtmpl has been implemented, which allows the user to see what portal version is used by mouse-hovering in the site footer. + </para> + </listitem> + </varlistentry> +</variablelist> Added: docs/enterprise/trunk/Release_Notes/en-US/images/icon.svg =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/images/icon.svg (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/images/icon.svg 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0" width="32" height="32" id="svg3017"> + <defs id="defs3019"> + <linearGradient id="linearGradient2381"> + <stop id="stop2383" style="stop-color:#ffffff;stop-opacity:1" offset="0"/> + <stop id="stop2385" style="stop-color:#ffffff;stop-opacity:0" offset="1"/> + </linearGradient> + <linearGradient x1="296.4996" y1="188.81061" x2="317.32471" y2="209.69398" id="linearGradient2371" xlink:href="#linearGradient2381" gradientUnits="userSpaceOnUse" gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)"/> + </defs> + <g transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" id="g5089"> + <path d="m 8.4382985,-6.28125 c -0.6073916,0 -4.3132985,5.94886271 -4.3132985,8.25 l 0,26.71875 c 0,0.846384 0.5818159,1.125 1.15625,1.125 l 25.5625,0 c 0.632342,0 1.125001,-0.492658 1.125,-1.125 l 0,-5.21875 0.28125,0 c 0.49684,0 0.906249,-0.409411 0.90625,-0.90625 l 0,-27.9375 c 0,-0.4968398 -0.40941,-0.90625 -0.90625,-0.90625 l -23.8117015,0 z" transform="translate(282.8327,227.1903)" id="path5091" style="fill:#5c5c4f;stroke:#000000;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none"/> + <rect width="27.85074" height="29.369793" rx="1.1414107" ry="1.1414107" x="286.96509" y="227.63805" id="rect5093" style="fill:#032c87"/> + <path d="m 288.43262,225.43675 25.2418,0 0,29.3698 -26.37615,0.0241 1.13435,-29.39394 z" id="rect5095" style="fill:#ffffff"/> + <path d="m 302.44536,251.73726 c 1.38691,7.85917 -0.69311,11.28365 -0.69311,11.28365 2.24384,-1.60762 3.96426,-3.47694 4.90522,-5.736 0.96708,2.19264 1.83294,4.42866 4.27443,5.98941 0,0 -1.59504,-7.2004 -1.71143,-11.53706 l -6.77511,0 z" id="path5097" style="fill:#a70000;fill-opacity:1;stroke-width:2"/> + <rect width="25.241802" height="29.736675" rx="0.89682275" ry="0.89682275" x="290.73544" y="220.92249" id="rect5099" style="fill:#809cc9"/> + <path d="m 576.47347,725.93939 6.37084,0.41502 0.4069,29.51809 c -1.89202,-1.31785 -6.85427,-3.7608 -8.26232,-1.68101 l 0,-26.76752 c 0,-0.82246 0.66212,-1.48458 1.48458,-1.48458 z" transform="matrix(0.499065,-0.866565,0,1,0,0)" id="rect5101" style="fill:#4573b3;fill-opacity:1"/> + <path d="m 293.2599,221.89363 20.73918,0 c 0.45101,0 0.8141,0.3631 0.8141,0.81411 0.21547,6.32836 -19.36824,21.7635 -22.36739,17.59717 l 0,-17.59717 c 0,-0.45101 0.3631,-0.81411 0.81411,-0.81411 z" id="path5103" style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1"/> + </g> +</svg> Added: docs/enterprise/trunk/Release_Notes/en-US/known_issues.old =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/known_issues.old (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/known_issues.old 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,4 @@ + +<para> +There are no known issues in this release. +</para> Added: docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,116 @@ +<?xml version='1.0'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + + +<variablelist> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1376">JBEPP-1376</ulink></term> + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + When serving content from a portlet, resource encoding is being rewritten with the default encoding of the running JVM. To work around the issue, server the resource as a binary, or set the default system encoding to ISO-8859-1. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1396">JBEPP-1396</ulink></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + When a dashboard page is created and its title translated in various languages, switching languages will not update the dashboard page name on the user interface immediately. To work around the issue, log out and log back in to show the correct translation for the page name. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1399">JBEPP-1399</ulink></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + If you create a system subnode under a node in the Navigation Management, you are allowed the delete the parent node without the "Cannot delete a system node" message being shown. When trying to save the result, a message "Unknown error" is shown and the following NPE is thrown. A fix is being investigated for a future release. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1401">JBEPP-1401</ulink></term> + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + An issue with the No Result Found pop-up causes it to display after first searching for a non-existent user string, then searching for a string that is known to exist. There is no work around for this issue. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1402">JBEPP-1402</ulink></term> + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + An issue with node copy or clone behavior allows users to copy or clone a system node but not delete the node. This is caused by the node already being a system node, and therefore it can not be deleted based on it's context. There is no work around for this issue. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1411">JBEPP-1411</ulink></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + System child nodes can be deleted if the parent node is deleted. A system node should not be able to de be deleted, regardless of its position in a navigation tree. This behavior will be fixed in a future release. + </para> + + </listitem> + </varlistentry> + +</variablelist> Added: docs/enterprise/trunk/Release_Notes/en-US/need_info.old =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/need_info.old (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/need_info.old 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,4 @@ + +<para> +There are no issues that require more information at this time. +</para> Added: docs/enterprise/trunk/Release_Notes/en-US/need_info.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/need_info.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/need_info.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,4 @@ + +<para> +There are no issues that require more information at this time. +</para> Added: docs/enterprise/trunk/Release_Notes/en-US/needinfo.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/needinfo.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/needinfo.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,4 @@ + +<para> +There are no issues that require more information at this time. +</para> Added: docs/enterprise/trunk/Release_Notes/en-US/new_features.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/new_features.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/new_features.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,117 @@ +<?xml version='1.0'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + + +<variablelist> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1224" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + The Services Management Gadget currently has a display issue with the tabs displaying to the left of the table containing the data. This problem presented on Microsoft Internet Explorer 7 on Windows Vista. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1236" /></term> + <listitem> + + <remark>Assignee is: mwringe</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + org.exoplatform.services.cache.impl.jboss.ExoCacheFactoryImpl.createCache runs for both clustered and non-clustered environments. This class registers JBoss Cache to JMX, which produces MBeans for clustered services regardless of whether the clustered services are actively used in the environment. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1258" /></term> + <listitem> + + <remark>Assignee is: mwringe</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + Some CSS issues have been identified with the way the Portal home page is rendered. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1271" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + When adding a portlet into a 2-column layout container, the container collapses while dragging the portlet into the container. The container sometimes remains collapsed after moving the portlet into the container. This problem presented on Microsoft Windows 7, using Internet Explorer 8. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1345" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + An interface abnormality was discovered in the Account Portlet. If more than one instance of the Account Portlet is present on a page, tabs switching will work in the first portlet as designed. If tab switching is attempted in the other instances, the tab and the content in the portlet flashes temporarily, and the original tab is shown again. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1359" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + Sybase 15.5 imposes a limitation on the case used in portal names. Only lowercase portal names are supported. The problem does not present in Sybase 15.0.3. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +</variablelist> Added: docs/enterprise/trunk/Release_Notes/en-US/not_documented.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/not_documented.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/not_documented.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,3 @@ +<para> +All Issues are documented. +</para> Added: docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.old =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.old (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.old 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,4 @@ + +<para> +There are no resolved issues in this release. +</para> Added: docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml (rev 0) +++ docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,457 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<variablelist> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-348">JBEPP-348</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the portlet description, which allowed Javascript to be specified in the portlet description through the application registry. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered when adding a portlet to a category. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + Remote Gadgets were not persisting data in category gadgets with more than five categories when the user switched between pages. User data entered in one screen was being lost when the user switched between pages. The fix implements changes to UIForm.js and UIFormCheckBoxInput.java which handles selected values reliably when the user switches between screens. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699</ulink> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> + A bug in UIUserLanguageSelector caused a problem with dynamically updating the locale when a user selected a different language. The language state had to be saved using the Apply button. The fix introduces changes to locale handling in the affected module which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715</ulink> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> + The page URL conventions in previous versions of JBoss Enterprise Portal Platform did not allow for Portal pages to have the same name. In these instances, pages with identical names were allocated the same URL, with only one page available through it. A change to the way JBoss Enterprise Portal Platform constructs page URLs resolves this issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + The platform ships with a resource compressor (CSS and Javascript). Some javascript files were incorrectly compressed and would break unless the developer mode was enabled. Enabling the developer mode introduced performance side-effects. The Javascript compression engine has been replaced, and can be turned off if required, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A bug in the Logo Portlet caused the processAction methods to be called once when the first, valid, processAction method was called to submit the value, and again when the page was rendered. This caused null values to be passed on the second submit. A fix to UILogoPortlet.gtmpl removes the second processAction call issue, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + When a "root" user (advanced administrative rights) logs onto the portal, part of the logon process calls a query that fetches all the groups from the database. This query was not optimized to handle databases containing very large numbers of groups. When testing with a large group database, the login process took an unacceptable amount of time. The fix implements performance improvements to the query, and provides enhanced caching for large group records. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + An issue was identified when the OrganizationManagementPortlet displayed many users from the IDM DB. This caused performance issues, specifically impacting load times for the portlet. The fix implements performance optimizations for specific database queries related to the process. Load time performance is improved for the portlet. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + A performance issue in a database query that checked for duplicate emails at user registration caused unacceptable wait times. The larger the user count was in the database, the more pronounced the issue. The fix implements performance optimization in the database query. User registration wait time is improved for portal instances with very large user databases. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + It is not possible to save notes in the TODO gadget when the gadget is placed anywhere except a dashboard. This behavior is expected. A workaround to this issue has been implemented in this version, which allows notes to be entered into this gadget only. Other gadgets still have this issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + An inefficiency in MOPSessionManager cache was causing unacceptable wait times when an user accessed the portal for the first time, when the portal was idle for an extended period, or when accessing pages that had not been previously cached. The fix implements performance improvements for cases where a portal instance has many pages and navigation nodes, improving overall response time. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + Performance issues were discovered in the portal when editing a navigation, or portal page that contained many sub-pages. In some cases, the save action was taking longer than one minute to complete. The fix implements changes to the queries used to retrieve navigation, or portal pages after saving, which improves load times significantly. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + An inconsistency in how portlets are handled across different part of the administration interface resulted in an error when remote portlets were added to a category from the "Portlet" tab of the Application Registry. The inconsistency has now be resolved and it should be now possible to properly display remote portlets regardless of how they were added to categories. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + DateTimeValidator.java had an unnecessary check where the date input value needed to match the (not localized) DATETIME_REGEX. This superfluous requirement caused localized date input to fail. The fix removes the DATETIME_REGEX, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + A bug was discovered where a transaction commit related to IDM database operations was not placed within a final() block. Any misconfiguration, or operation failure, could cause the database connection to remain open. The fix ensures the transaction commit related to IDM database operations is placed within a final() block, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page > Container Title field. The vulnerability is fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the New Node label. The vulnerability has been removed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the RSS reader gadget. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + Only users from the LDAP database were shown in organization management if LDAP did not support sorting. The fix changes the logging level to INFO in PicketLink IDM. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + If gadget restrict access to specific group, it was accessible for not members in Dashboard and page editing. +Now users cannot add restricted gadget. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Activating JRMP configuration in JBoss EPP 5.1.x (or EPP based products) produced a large quantity of JMX/RMI logs in stdout/stderr. The JRMP agent had logging set to FINE, which resulted in verbose log information. The fix removes the embedded logger configuration, which results in the JBoss Enterprise Application Platform server log configuration being used for logging. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150</ulink> + </term> + <listitem> + <remark>Assignee is: mputz</remark> + <remark>JIRA is Closed</remark> + <para> + An invisible navigation node was displayed in the Sitemap portlet when the parent node was expanded (not with Expand All button). The workaround described in the linked JIRA has been implemented in this release, which corrects the originally reported issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with regard to the location of token keys prevented Gadgets from working in load-balanced clustered portal environments. Token keys have been moved to a location accessible by all load-balanced clustered portal instances. Gadgets can now be used as intended. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with UploadService was causing the MIME type of .rtf files extracted from DiskFileItem in Apache as "text/rtf". The value should have been extracted as "application/rtf", which caused problems for applications dependent on correct MIME type information. The fix corrects the MIME type encoding, and ensures .rtf files are set with the MIME type "application/rtf". + + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with the GroupManagement.java isAdministrator method caused a NullPointerException when the Organization Portlet is placed on a page and an anonymous user tries to access it. The fix changes the behavior of isAdministrator for anonymous users, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the UIFormDateTimeInput component. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Group descriptions text entered by users was not properly protected from XSS attacks. It was possible to execute arbitrary Javascript if a user had permissions to enter a group description. The group description field has been protected to not execute any Javascript, which resolves the issue. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html">(CVE-2011-4580)</ulink> + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293</ulink> + </term> + <listitem> + <remark>Assignee is: kenfinni</remark> + <remark>JIRA is Closed</remark> + <para> + org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() did not correctly handle exceptions. Exceptions that typically occurred during during afterPhase() were truncated (for example StaleObjectStateException in Hibernate commit). The Seam exception handler was not notified of the truncated exceptions therefore the application moves to a next page instead of an error page. The fix ensures org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() catches exceptions and passes them to Seam exception handler (for example, org.jboss.seam.jsf.SeamPhaseListener). Because exceptions are handled correctly, the Seam exception handler displays and error page given the appropriate conditions. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + If the Opera browser is used to access the portal home page, a Javascript Uncaught exception is raised: "TypeError: 'Browser.setOpacity' is not a function". The fix incorporates a verified customer-submitted patch to Browser.js, which allows Opera browsers to access the portal home page. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + If the WSRP consumer was refreshed and activated, WSRP selfv2 prevented the server from starting when it was rebooted. The only way to work around this issue was to perform a force quit. The fix adds a &lt;value-param&gt; configuration option to the main WSRP configuration. consumersInitDelay provides a way to specify a delayed start (configurable, in seconds) of the ConsumerRegistry, which prevents a deadlock situation while the self consumers wait for the producer WSDL to be published. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + It was found that the invoker servlets, deployed by default via +httpha-invoker, only performed access control on the HTTP GET and POST +methods, allowing remote attackers to make unauthenticated requests by +using different HTTP methods. Due to the second layer of authentication +provided by a security interceptor, this issue is not exploitable on +default installations unless an administrator has misconfigured the +security interceptor or disabled it. (CVE-2011-4085) + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When a portal host name contained the word "portal" in the name, gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds functionality to several portal components which allows for the word "portal" in the host name. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + It was found that the GateIn Portal contained verb-specific security constraints. As a result, authentication and authorization were only correctly applied to requests made using the GET and POST HTTP verbs. The GateIn Portal application does not allow a user to trigger any action using HTTP verbs other than POST and GET, so this issue did not expose an exploitable security flaw. As a defence-in-depth measure, the verb-specific security constraints have been removed. Authentication and authorization now correctly apply to requests made using all HTTP verbs. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + The org.gatein.sso.agent.login.SSOLoginModule contains the common options "portal" and "realmName" as offered in other LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module did not have these options. This caused problems when a customer wanted to implement SSO on a different portal container (for example in ecmdemo). The fix includes these common options in gatein-jboss-beans.xml, which resolves the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + The Web Services for Remote Portlet (WSRP) configuration files for consumers and producer were previously only looked for in the WSRP extension archive. This resulted in extra configuration complexity for customers who wanted to edit the configuration directives for WSRP consumers and producer. The fix implements changes to the WSRP integration point that will now also look for WSRP configuration files in the conf/gatein directory of the active JBoss AS profile. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + The JBoss Clustered Single Sign On (SSO) Valve must authenticate on all clustered nodes using the same password. The login process in Enterprise Portal Platform differed from normal authentication methods, and customers had to bypass standard authentication by enabling BASIC authentication, or patch login.jsp as described in the Reference Guide. The fix introduces PortalClusteredSSOSupportValve, which removes the patching and workarounds customers had to implement in earlier versions of the product, and increases overall platform security. + </para> + </listitem> + </varlistentry> +</variablelist> Added: docs/enterprise/trunk/Release_Notes/publican.cfg =================================================================== --- docs/enterprise/trunk/Release_Notes/publican.cfg (rev 0) +++ docs/enterprise/trunk/Release_Notes/publican.cfg 2012-01-12 04:29:54 UTC (rev 14034) @@ -0,0 +1,10 @@ +# Config::Simple 4.59 +# Tue Nov 16 11:07:34 2010 + +xml_lang: en-US +type: Book +brand: JBoss +#show_remarks: 1 +cvs_branch: DOCS-RHEL-6 +cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist +cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_Release_Notes-5.2-web-__LANG__

12 years, 3 months

1
0
0 / 0

JBoss Portal SVN: r14033 - docs/enterprise/trunk.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 23:27:49 -0500 (Wed, 11 Jan 2012) New Revision: 14033 Added: docs/enterprise/trunk/Release_Notes_Old/ Removed: docs/enterprise/trunk/Release_Notes/ Log: Deprecated the Release Notes Article Format for 4.3

12 years, 3 months

1
0
0 / 0

JBoss Portal SVN: r14032 - docs/enterprise/trunk/User_Guide/en-US.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 20:53:50 -0500 (Wed, 11 Jan 2012) New Revision: 14032 Removed: docs/enterprise/trunk/User_Guide/en-US/Middleware_Feedback.xml Log: Removing unused files from repo Deleted: docs/enterprise/trunk/User_Guide/en-US/Middleware_Feedback.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/Middleware_Feedback.xml 2012-01-12 01:53:17 UTC (rev 14031) +++ docs/enterprise/trunk/User_Guide/en-US/Middleware_Feedback.xml 2012-01-12 01:53:50 UTC (rev 14032) @@ -1,52 +0,0 @@ -<?xml version='1.0'?> -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -  - -<section id="jboss-feedback"> - <title>Give us Feedback</title> - - <para> - If you find a typographical error, or know how this guide can be improved, we would love to hear from you. Submit a report in Bugzilla against the &PRODUCT; &BOOKID;. The following link will take you to bug report for &PRODUCT; <ulink type="http" url="https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss%20Enterprise%20Po...">https://bugzilla.redhat.com/</ulink>. - </para> - <para> - Select the document name and version number relevant to the document you found the error in from the available lists then complete the description with as much detail as you can provide. - </para> - - - - <para> - Be sure to give us your name so that you can receive full credit for reporting the issue. - </para> - -</section>

12 years, 3 months

1
0
0 / 0

JBoss Portal SVN: r14031 - docs/enterprise/trunk/Tuning_Guide/en-US.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 20:53:17 -0500 (Wed, 11 Jan 2012) New Revision: 14031 Removed: docs/enterprise/trunk/Tuning_Guide/en-US/Middleware_Feedback.xml Log: Removing unused files from repo Deleted: docs/enterprise/trunk/Tuning_Guide/en-US/Middleware_Feedback.xml =================================================================== --- docs/enterprise/trunk/Tuning_Guide/en-US/Middleware_Feedback.xml 2012-01-12 01:51:15 UTC (rev 14030) +++ docs/enterprise/trunk/Tuning_Guide/en-US/Middleware_Feedback.xml 2012-01-12 01:53:17 UTC (rev 14031) @@ -1,52 +0,0 @@ -<?xml version='1.0'?> -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -  - -<section id="jboss-feedback"> - <title>Give us Feedback</title> - - <para> - If you find a typographical error, or know how this guide can be improved, we would love to hear from you. Submit a report in Bugzilla against the &PRODUCT; &BOOKID;. The following link will take you to bug report for &PRODUCT; <ulink type="http" url="https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss%20Enterprise%20Po...">https://bugzilla.redhat.com/</ulink>. - </para> - <para> - Select the document name and version number relevant to the document you found the error in from the available lists then complete the description with as much detail as you can provide. - </para> - - - - <para> - Be sure to give us your name so that you can receive full credit for reporting the issue. - </para> - -</section>

12 years, 3 months

1
0
0 / 0

JBoss Portal SVN: r14030 - docs/enterprise/trunk/PortletBridge/en-US.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 20:51:15 -0500 (Wed, 11 Jan 2012) New Revision: 14030 Removed: docs/enterprise/trunk/PortletBridge/en-US/Middleware_Feedback.xml Log: Removing unused files from repo Deleted: docs/enterprise/trunk/PortletBridge/en-US/Middleware_Feedback.xml =================================================================== --- docs/enterprise/trunk/PortletBridge/en-US/Middleware_Feedback.xml 2012-01-12 01:50:32 UTC (rev 14029) +++ docs/enterprise/trunk/PortletBridge/en-US/Middleware_Feedback.xml 2012-01-12 01:51:15 UTC (rev 14030) @@ -1,52 +0,0 @@ -<?xml version='1.0'?> -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -  - -<section id="jboss-feedback"> - <title>Give us Feedback</title> - - <para> - If you find a typographical error, or know how this guide can be improved, we would love to hear from you. Submit a report in Bugzilla against the &PRODUCT; &BOOKID;. The following link will take you to bug report for &PRODUCT; <ulink type="http" url="https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss%20Enterprise%20Po...">https://bugzilla.redhat.com/</ulink>. - </para> - <para> - Select the document name and version number relevant to the document you found the error in from the available lists then complete the description with as much detail as you can provide. - </para> - - - - <para> - Be sure to give us your name so that you can receive full credit for reporting the issue. - </para> - -</section>

12 years, 3 months

1
0
0 / 0

JBoss Portal SVN: r14029 - docs/enterprise/trunk/Installation_Guide/en-US.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 20:50:32 -0500 (Wed, 11 Jan 2012) New Revision: 14029 Removed: docs/enterprise/trunk/Installation_Guide/en-US/Middleware_Feedback.xml Log: Removing unused files from repo Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Middleware_Feedback.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Middleware_Feedback.xml 2012-01-12 01:49:50 UTC (rev 14028) +++ docs/enterprise/trunk/Installation_Guide/en-US/Middleware_Feedback.xml 2012-01-12 01:50:32 UTC (rev 14029) @@ -1,52 +0,0 @@ -<?xml version='1.0'?> -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -  - -<section id="jboss-feedback"> - <title>Give us Feedback</title> - - <para> - If you find a typographical error, or know how this guide can be improved, we would love to hear from you. Submit a report in Bugzilla against the &PRODUCT; &BOOKID;. The following link will take you to bug report for &PRODUCT; <ulink type="http" url="https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss%20Enterprise%20Po...">https://bugzilla.redhat.com/</ulink>. - </para> - <para> - Select the document name and version number relevant to the document you found the error in from the available lists then complete the description with as much detail as you can provide. - </para> - - - - <para> - Be sure to give us your name so that you can receive full credit for reporting the issue. - </para> - -</section>

12 years, 3 months

1
0
0 / 0

JBoss Portal SVN: r14028 - docs/enterprise/trunk/Reference_Guide/en-US.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 20:49:50 -0500 (Wed, 11 Jan 2012) New Revision: 14028 Removed: docs/enterprise/trunk/Reference_Guide/en-US/Middleware_Feedback.xml docs/enterprise/trunk/Reference_Guide/en-US/Trademarks.xml docs/enterprise/trunk/Reference_Guide/en-US/_Common_Content/ Log: Removing unused files from repo Deleted: docs/enterprise/trunk/Reference_Guide/en-US/Middleware_Feedback.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Middleware_Feedback.xml 2012-01-12 01:47:10 UTC (rev 14027) +++ docs/enterprise/trunk/Reference_Guide/en-US/Middleware_Feedback.xml 2012-01-12 01:49:50 UTC (rev 14028) @@ -1,52 +0,0 @@ -<?xml version='1.0'?> -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -  - -<section id="jboss-feedback"> - <title>Give us Feedback</title> - - <para> - If you find a typographical error, or know how this guide can be improved, we would love to hear from you. Submit a report in Bugzilla against the &PRODUCT; &BOOKID;. The following link will take you to bug report for &PRODUCT; <ulink type="http" url="https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss%20Enterprise%20Po...">https://bugzilla.redhat.com/</ulink>. - </para> - <para> - Select the document name and version number relevant to the document you found the error in from the available lists then complete the description with as much detail as you can provide. - </para> - - - - <para> - Be sure to give us your name so that you can receive full credit for reporting the issue. - </para> - -</section> Deleted: docs/enterprise/trunk/Reference_Guide/en-US/Trademarks.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Trademarks.xml 2012-01-12 01:47:10 UTC (rev 14027) +++ docs/enterprise/trunk/Reference_Guide/en-US/Trademarks.xml 2012-01-12 01:49:50 UTC (rev 14028) @@ -1,63 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.docbook.org/xml/4.5/docbookx.dtd"> - -<preface id="trademarks"> - <title>Please Read: Important Trademark Information</title> - <para> - Sun, JavaServer, JSP, Java, JMX, JDK, Java runtime environment, J2EE, JVM, Javadoc, 100% Pure Java, JDBC, and JavaScript are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. - </para> - <para> - JBoss is a registered trademark of Red Hat, Inc. in the U.S. and other countries. - </para> - <para> - Red Hat is a registered trademark of Red Hat, Inc. in the United States and other countries. - </para> - <para> - Oracle is a registered trademark of Oracle International Corporation. - </para> - <para> - Microsoft, Windows, Active Directory, and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. - </para> - <para> - Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. - </para> - <para> - UNIX is a registered trademark of The Open Group. - </para> - <para> - MySQL is a trademark or registered trademark of MySQL AB in the U.S. and other countries. - </para> - <para> - Apache is a trademark of The Apache Software Foundation. - </para> - <para> - Mac and Mac OS are trademarks of Apple Inc., registered in the U.S. and other countries. - </para> - <para> - All other trademarks referenced herein are the property of their respective owners. - </para> -</preface> - - - \ No newline at end of file

12 years, 3 months

1
0
0 / 0

JBoss Portal SVN: r14027 - in docs/enterprise/trunk: PortletBridge/en-US and 3 other directories.

by portal-commits＠lists.jboss.org

Author: jaredmorgs Date: 2012-01-11 20:47:10 -0500 (Wed, 11 Jan 2012) New Revision: 14027 Added: docs/enterprise/trunk/Reference_Guide/en-US/_Common_Content/ Removed: docs/enterprise/trunk/Reference_Guide/en-US/Common_Content/ Modified: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide.xml docs/enterprise/trunk/Installation_Guide/en-US/Preface.xml docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml docs/enterprise/trunk/PortletBridge/en-US/Portlet_Bridge_Overview.xml docs/enterprise/trunk/PortletBridge/en-US/Preface.xml docs/enterprise/trunk/Reference_Guide/en-US/Book_Info.xml docs/enterprise/trunk/Reference_Guide/en-US/Preface.xml docs/enterprise/trunk/Reference_Guide/en-US/Reference_Guide.xml docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml docs/enterprise/trunk/Tuning_Guide/en-US/Preface.xml docs/enterprise/trunk/Tuning_Guide/en-US/Tuning_Guide.xml docs/enterprise/trunk/User_Guide/en-US/Administration_CMS_Portlet.xml docs/enterprise/trunk/User_Guide/en-US/Book_Info.xml docs/enterprise/trunk/User_Guide/en-US/Dynamicity.xml docs/enterprise/trunk/User_Guide/en-US/JBoss_Portal_Basics.xml docs/enterprise/trunk/User_Guide/en-US/Preface.xml docs/enterprise/trunk/User_Guide/en-US/User_Guide.xml docs/enterprise/trunk/User_Guide/en-US/User_Role.xml Log: Initial changes for 4.3.7 release. Modified: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -7,8 +7,8 @@ <subtitle>An Installation Guide for &PRODUCT;</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>4.3</productnumber> - <edition>1</edition> - <pubsnumber>1.4</pubsnumber> + <edition>4.3.7</edition> + <pubsnumber>1</pubsnumber> <abstract><para>This Installation Guide documents relevant information regarding the installation of JBoss Enterprise Portal Platform</para> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,17 +1,18 @@ -<?xml version='1.0'?> +<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> +%BOOK_ENTITIES; ]> - <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="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Getting_Started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Post_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Introduction.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Getting_Started.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installation.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Post_Installation.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Configuration.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Databases.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Test_Your_Installation.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Uninstall_JBoss.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> </book> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Preface.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Preface.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/Installation_Guide/en-US/Preface.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,13 +1,8 @@ -<?xml version='1.0'?> +<?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" [ ]> - <preface id="Portal_User_Guide-Preface"> - <title>Preface</title> - <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Middleware_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> + <title>Preface</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Common_Content/Conventions.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Common_Content/Feedback.xml"/> + </preface> Modified: docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,38 +1,32 @@ -<?xml version='1.0' encoding='utf-8' ?> +<?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" [ ]> <bookinfo id="book-Overview-Overview"> - <title>Portlet Bridge Overview</title> - <subtitle>For use with JBoss Enterprise Portal Platform 4.3</subtitle> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>4.3</productnumber> - - <edition>1</edition> - <pubsnumber>2.1</pubsnumber> - <abstract> - <para> + <title>Portlet Bridge Overview</title> + <subtitle>For use with JBoss Enterprise Portal Platform 4.3</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>4.3</productnumber> + <edition>4.3.7</edition> + <pubsnumber>1</pubsnumber> + <abstract> + <para> The JBoss Portlet Bridge is an implementation of the JSR-301 specification to support JSF within a portlet and with added enhancements to support other web frameworks. Currently the bridge supports any combination of JSF, Seam, and RichFaces to run inside a portlet. </para> - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" /> - </imageobject> - <textobject> - <phrase>Logo</phrase> - </textobject> - - </inlinemediaobject> - - </corpauthor> - <copyright> - <year>&YEAR;</year> - <holder>&HOLDER;</holder> - - </copyright> - <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"/> + </imageobject> + <textobject> + <phrase>Logo</phrase> + </textobject> + </inlinemediaobject> + </corpauthor> + <copyright> + <year>&YEAR;</year> + <holder>&HOLDER;</holder> + </copyright> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Common_Content/Legal_Notice.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Author_Group.xml"/> </bookinfo> - Modified: docs/enterprise/trunk/PortletBridge/en-US/Portlet_Bridge_Overview.xml =================================================================== --- docs/enterprise/trunk/PortletBridge/en-US/Portlet_Bridge_Overview.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/PortletBridge/en-US/Portlet_Bridge_Overview.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,13 +1,15 @@ -<?xml version='1.0' encoding='utf-8' ?> +<?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 "Portlet_Bridge_Overview.ent"> +%BOOK_ENTITIES; ]> <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="overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="gettingstarted.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="portlet_development.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="overview.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="gettingstarted.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="configuration.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="portlet_development.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> </book> - Modified: docs/enterprise/trunk/PortletBridge/en-US/Preface.xml =================================================================== --- docs/enterprise/trunk/PortletBridge/en-US/Preface.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/PortletBridge/en-US/Preface.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -4,8 +4,6 @@ <preface id="pref-Overview-Preface"> <title>Preface</title> <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Middleware_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> + <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </preface> Modified: docs/enterprise/trunk/Reference_Guide/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Book_Info.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/Reference_Guide/en-US/Book_Info.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,30 +1,27 @@ -<?xml version="1.0" encoding="UTF-8"?> +<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ ]> - <bookinfo id="JBoss_Portal_Reference_Guide"> - <title>Reference Guide</title> - <subtitle>A Reference Guide for Enterprise Portal Platform 4.3</subtitle> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>4.3</productnumber> - <edition>1</edition> - <pubsnumber>1.10</pubsnumber> - - <abstract><para>This book is the Enterprise Portal Platform Reference Guide.</para> - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata fileref="Common_Content/images/redhat-logo.svg" /> - </imageobject> - </inlinemediaobject> - </corpauthor> - - <copyright> - <year>&YEAR;</year> - <holder>&HOLDER;</holder> - </copyright> - <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <title>Reference Guide</title> + <subtitle>A Reference Guide for Enterprise Portal Platform 4.3</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>4.3</productnumber> + <edition>4.3.7</edition> + <pubsnumber>1</pubsnumber> + <abstract> + <para>This book is the Enterprise Portal Platform Reference Guide.</para> + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/redhat-logo.svg"/> + </imageobject> + </inlinemediaobject> + </corpauthor> + <copyright> + <year>&YEAR;</year> + <holder>&HOLDER;</holder> + </copyright> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Common_Content/Legal_Notice.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Author_Group.xml"/> </bookinfo> - Modified: docs/enterprise/trunk/Reference_Guide/en-US/Preface.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Preface.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/Reference_Guide/en-US/Preface.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -5,9 +5,5 @@ <preface id="Portal_User_Guide-Preface"> <title>Preface</title> <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Middleware_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> + <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </preface> Modified: docs/enterprise/trunk/Reference_Guide/en-US/Reference_Guide.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Reference_Guide.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/Reference_Guide/en-US/Reference_Guide.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,67 +1,42 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" - "http://www.docbook.org/xml/4.5/docbookx.dtd"> +<?xml version='1.0' encoding='UTF-8'?> + +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> +%BOOK_ENTITIES; +]> <book id="jboss_portal_reference_guide"> - -  - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml" /> - <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trademarks.xml" /> - - - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Target.xml" /> - - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Supported.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installation.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Configuration.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Migration.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Tutorials.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="XML_Descriptors.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="URLs.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Coordination.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Error_Handling.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Content_Integration.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Widget_Integration.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portlet_Modes.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_API.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Clustering.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="WSRP.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Security.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Identity.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Identity_Portlets.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Authentication.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Ldap.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="SSO.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="CMS_Portlet.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Workflow.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Nav_Tabs.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Theme_And_Layouts.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Ajax.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Troubleshooting.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_Objects_DTD.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portlet_Instances_DTD.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Jboss_Portlet_DTD.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml" /> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Target.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Supported.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installation.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Configuration.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Migration.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Tutorials.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="XML_Descriptors.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="URLs.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Coordination.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Error_Handling.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Content_Integration.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Widget_Integration.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portlet_Modes.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_API.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Clustering.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="WSRP.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Security.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Identity.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Identity_Portlets.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Authentication.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Ldap.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="SSO.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="CMS_Portlet.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Workflow.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Nav_Tabs.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Theme_And_Layouts.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Ajax.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Troubleshooting.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_Objects_DTD.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portlet_Instances_DTD.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Jboss_Portlet_DTD.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> </book> Modified: docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,36 +1,31 @@ -<?xml version='1.0' encoding='utf-8' ?> +<?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 "Tuning_Guide.ent"> %BOOK_ENTITIES; ]> <bookinfo id="book-Tuning_Guide-Tuning_Guide"> - <title>Tuning Guide</title> - <subtitle>A guide to tuning the performance of JBoss Enterprise Portal Platform 4.3.</subtitle> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>4.3</productnumber> - <edition>1</edition> - <pubsnumber>1.5</pubsnumber> - <abstract> - <para> + <title>Tuning Guide</title> + <subtitle>A guide to tuning the performance of JBoss Enterprise Portal Platform 4.3.</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>4.3</productnumber> + <edition>4.3.7</edition> + <pubsnumber>1</pubsnumber> + <abstract> + <para> This Installation Guide documents tuning of JBoss Enterprise Portal Platform. </para> - - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata fileref="Common_Content/images/redhat-logo.svg" format="SVG" /> - </imageobject> - - </inlinemediaobject> - - </corpauthor> - <copyright> - <year>&YEAR;</year> - <holder>&HOLDER;</holder> - - </copyright> - <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/redhat-logo.svg" format="SVG"/> + </imageobject> + </inlinemediaobject> + </corpauthor> + <copyright> + <year>&YEAR;</year> + <holder>&HOLDER;</holder> + </copyright> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Common_Content/Legal_Notice.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Author_Group.xml"/> </bookinfo> - Modified: docs/enterprise/trunk/Tuning_Guide/en-US/Preface.xml =================================================================== --- docs/enterprise/trunk/Tuning_Guide/en-US/Preface.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/Tuning_Guide/en-US/Preface.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -6,8 +6,6 @@ <preface id="pref-Tuning_Guide-Preface"> <title>Preface</title> <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Middleware_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> + <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </preface> Modified: docs/enterprise/trunk/Tuning_Guide/en-US/Tuning_Guide.xml =================================================================== --- docs/enterprise/trunk/Tuning_Guide/en-US/Tuning_Guide.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/Tuning_Guide/en-US/Tuning_Guide.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,17 +1,17 @@ -<?xml version='1.0' encoding='utf-8' ?> +<?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 "Tuning_Guide.ent"> %BOOK_ENTITIES; ]> <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="overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jbossweb.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="hibernate.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="identity.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="clustering.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="jvm.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="overview.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="jbossweb.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="hibernate.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="identity.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="clustering.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="jvm.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> </book> - Modified: docs/enterprise/trunk/User_Guide/en-US/Administration_CMS_Portlet.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/Administration_CMS_Portlet.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/User_Guide/en-US/Administration_CMS_Portlet.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,470 +1,390 @@ -<?xml version='1.0'?> +<?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="Portal_User_Guide-Test-Administration_CMS_Portlet"> - <title>Administration Content Management System (CMS) Portlet</title> - - - -<section id="Portal_User_Guide-Administration_-_Content_Management_System-Introduction"> - <title>Introduction</title> - - - <para> - The CMSAdmin Portlet allows control over the content management system. - </para> - - <para> - Viewing the CMSAdmin Portlet is accomplished by logging in as admin (admin/admin) and navigating to the admin portal and then the CMS Page tab. - </para> - - <para> - You will then be presented with a page that is similar to this: - </para> - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/cms_adminpage.png" format="PNG"/> - </imageobject> - </mediaobject> -</section> - -<section id="Portal_User_Guide-Administration_-_Content_Management_System-Actions"> - <title>Actions</title> - - - <para> - This section describes common actions an administrator can perform from within the AdminCMS Portlet. All - actions are available using the flyout menu. Note that the Pending Items action is only available if the - workflow mechanism has been activated. - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/actions_menu.png" format="PNG"/> - </imageobject> - </mediaobject> - </para> - - - <section id="Portal_User_Guide-Actions-Viewing-Directories"> - - <title>Viewing Directories</title> - - <para> - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/ss_viewfile.png" format="PNG"/> - </imageobject> - </mediaobject> - - A user can list directory contents by either clicking on the folder name or selecting "view" from the Action - dropdown and clicking "go". - </para> - </section> - - <section id="Portal_User_Guide-Actions-Viewing_File_Properties"> - - <title>Viewing File Properties</title> - - <para> - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/ss_viewfile.png" format="PNG"/> - </imageobject> - </mediaobject> - Clicking on the "Name" of a file brings up the File Properties page. - </para> - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/fileproperties.png" format="PNG"/> - </imageobject> - </mediaobject> - <para> - The File Properties window displays all the possible actions available to perform on a file. - </para> - - <para> - Version and Locale Information are also contained on this screen. Note that any version labeled with a - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/live.png" format="PNG"/> - </imageobject> - </mediaobject> - - is the current "live" version shown to users. - </para> - -</section> - - <section id="Portal_User_Guide-Actions-Copying_Files"> - - <title>Copying Files/Directories</title> - - <para> - Clicking on the "Copy" action, displays the copy file/directory dialog window. - </para> - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/resourcecopy.png" format="PNG"/> - </imageobject> - </mediaobject> - - <para> - The copy resource window allows a user to copy files to any folder on the system, as well as copy whole directory trees to any directory on the system. A user can select which - destination directory to copy the resource to by using the directory browser. Clicking the - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/plus.png" format="PNG"/> - </imageobject> - </mediaobject> - - icon expands the directory tree. Clicking on the name of the directory within the tree sets it as the destination directory for the copied resource. - - </para> -</section> - - - <section id="Portal_User_Guide-Actions-Moving_Files"> - <title>Moving Files/Directories</title> - - - <para> - Clicking on the "Move" action, displays the move file/directory dialog window. - </para> - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/resourcemove.png" format="PNG"/> - </imageobject> - </mediaobject> - - <para> - The move resource window allows a user to move files to any folder on the system, as well as move whole directory trees to any directory on the system. A user can select which destination directory to move the resource to, by using the directory browser. Clicking the - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/plus.png" format="PNG"/> - </imageobject> - </mediaobject> - - icon expands the directory tree. Clicking on the name of the directory within the tree sets it as the destination directory for the moved resource. - - </para> - -</section> - - <section id="Portal_User_Guide-Actions-Deleting_Files"> - <title>Deleting Files/Directories</title> - - - <para> - Clicking on the "Delete" action, displays the delete file/directory confirmation window. - </para> - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/resourcedelete.png" format="PNG"/> - </imageobject> - </mediaobject> - - <para> - The delete resource confirmation window allows a user to delete a file or a directory on the system. Note that deleting a directory will delete the entire tree, so all directories under the deleted one will also be deleted. - - </para> - - <warning> - <para> - Currently, there is no way to retrieve deleted files/directories! Deleting a file or directory is permanent! - </para> - </warning> -</section> - - <section id="Portal_User_Guide-Actions-Creating_Directories"> - - <title>Creating Directories</title> - - <para> - Clicking on the "Create Folder" action, displays the create directory dialog window. - </para> - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/createdirectory.png" format="PNG"/> - </imageobject> - </mediaobject> - - <para> - The create directory resource window allows a user to create a directory under chosen path. On this window, a user can specify a name for the new empty directory and assign it a description. - </para> -</section> - - <section id="Portal_User_Guide-Actions-Creating_Text"> - - <title>Creating Text/HTML Files</title> - - <para> - Clicking on the "Create File" action, displays the create file dialog window with the embedded WYSIWYG editor and directory browser. - </para> - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/createhtml.png" format="PNG"/> - </imageobject> - </mediaobject> - - <para> - The create file window allows a user to create a text or HTML file using the embedded WYSIWYG HTML editor. The editor is a fully-functional HTML editor with a myriad of HTML functions. It also includes a preview - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/editorpreview.png" format="PNG"/> - </imageobject> - </mediaobject> - - button and a source view - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/editorsource.png" format="PNG"/> - </imageobject> - </mediaobject> - - button. - </para> - - <para> - An in-depth walk-through of the editor is beyond the scope of this document. However, the editor does contain help pages within it, that can be accessed by clicking the - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/editorhelp.png" format="PNG"/> - </imageobject> - </mediaobject> - - icon. - </para> - <important> - <para> - It is important to note here that when creating links to images or other resources within the system, a user must use the relative file path to that resource. ie: images/hello.i.e.,. Keep in mind at all times that the document base is http://localhost/portal/ by default!</para> - </important> - - <para> - Additionally, a user can set a title for the file that will be used in the portlet title bar, and a language for the file, used in serving localized content. - </para> -</section> - - <section id="Portal_User_Guide-Actions-Uploading_Files"> - - <title>Uploading Files</title> - - <para> - Clicking on the "Upload File" action, displays the upload file dialog window. - </para> - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/resourceupload.png" format="PNG"/> - </imageobject> - </mediaobject> - - <para> - The upload file window allows a user to upload files to any directory on the system. The upload process will work on files up to 1GB and of all types. A user can select which destination directory to upload the resource to, by using the directory browser. Clicking the - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/plus.png" format="PNG"/> - </imageobject> - </mediaobject> - - icon expands the directory tree. Clicking on the name of the directory within the tree, sets it as the destination directory for the uploaded resource. Additionally, a user can set a title for the file that will be used in the portlet title bar, and a language for the file, used in serving localized content. - </para> -</section> - - <section id="Portal_User_Guide-Actions-Uploading-Archives"> - - <title>Uploading Archives</title> - - <para> - Clicking on the "Upload Archive" action, displays the upload archive dialog window. - </para> - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/resourceuploadarchive.png" format="PNG"/> - </imageobject> - </mediaobject> - - <para> - The upload archive window allows a user to upload archives to any directory on the system. The system will then explode the archive, create versions, and place all the files in the repository. A user can select which destination directory to upload the resource to, by using the directory browser. Clicking the - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/plus.png" format="PNG"/> - </imageobject> - </mediaobject> - - icon expands the directory tree. Clicking on the name of the directory within the tree, sets it as the destination directory for the uploaded resource. Additionally, a user can set a language for the archive files, used in serving localized content. - - </para> - -</section> - - <section id="Portal_User_Guide-Actions-Exporting_Folders"> - <title>Exporting Folders</title> - - - <para> - Clicking on the "Export Folder" action, displays the export archive dialog window. - </para> - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/ss_exportarchive.png" format="PNG"/> - </imageobject> - </mediaobject> - - <para> - The export folder window allows a user to export entire directory structures as zip files. The system will aggregate all contents of a specific directory, and present to the user to download it. - A user can select which source directory to export the resources from, by using the directory browser. Clicking the - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/plus.png" format="PNG"/> - </imageobject> - </mediaobject> - - icon expands the directory tree. Clicking on the name of the directory within the tree, sets it as the source directory for the export resource. Additionally, a user can set a language for the files to be exported. - </para> - - <important> - <para> - Version information is not exported. Only versions labeled "Live" are exported! - </para> - </important> - -</section> - - - <section id="Portal_User_Guide-Actions-Editing_Text"> - <title>Editing Text/HTML Files</title> - - <para> - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/fileproperties.png" format="PNG"/> - </imageobject> - </mediaobject> - - Clicking on the "text/html"link, displays the edit file dialog window with the embedded WYSIWYG editor and directory browser. - </para> - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/editfile.png" format="PNG"/> - </imageobject> - </mediaobject> - - <para> - The edit file window allows a user to edit a text or HTML file using the embedded WYSIWYG HTML editor. The editor is a fully-functional HTML editor with a myriad of HTML functions. It also includes a preview - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/editorpreview.png" format="PNG"/> - </imageobject> - </mediaobject> - - button and a source view - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/editorsource.png" format="PNG"/> - </imageobject> - </mediaobject> - - button. - - </para> - - <para> - A user may specify at this point if he would like to make the new edit "live", or available in production. Additionally, a user can set a title for the file that will be used as the portlet window title. - </para> -</section> - - <section id="Portal_User_Guide-Actions-Securing_Resources"> - - <title>Securing Resources</title> - - <para> - Administrators are able to apply permissions settings to any folder or file in the CMS. These permissions on a specific node, can be applied on a per-Role and/or per-User basis. - </para> - - <para> - The security dialogue is accessed by navigating to the node you want to secure and selecting <emphasis>Secure</emphasis> - . - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/secure_menu.png" format="PNG"/> - </imageobject> - </mediaobject> - </para> - <para> - You should then be presented with a screen that allows you to assign read, write, and manage privileges on the selected node for selected Roles or specific Users. - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/secure_node.png" format="PNG"/> - </imageobject> - </mediaobject> - - There are three main security settings for every node in the CMS. - <itemizedlist> - <listitem> - <para><emphasis role="bold">Read Permissions:</emphasis> - Assigned roles/users can view the resource.</para> - </listitem> - <listitem> - <para> - <emphasis role="bold">Write Permissions:</emphasis> Assigned roles/users are able to edit the resource, or create nodes within it (as is the case for folders)</para> - - </listitem> - <listitem> - <para> - <emphasis role="bold">Manage Permissions:</emphasis> These permissions include: copy, move, delete, and exporting.</para> - </listitem> - </itemizedlist> - - Administrating and assigning permissions on a selected node is as simple as selecting which Roles and/or Users you want to allow to have a specific permission. - - </para> -</section> - <section id="Portal_User_Guide-Actions-Workflow"> - - <title>Content Publish/Approval Workflow</title> - - <para> - When the Publish/Approval Workflow service is activated on the CMS, any requests for publishing new content or making updates to existing content requires an Approval process before going "Live". You can specify a list of Portal Roles that can act as Approvers who can authorize/deny the publishing of content in the CMS. - </para> - <para> - When a content is created in the CMS, the screen should show an Pending Queue of Approvals for that particular content as shown below in the screen. The content waiting in this queue is not accessible for "Live" usage. - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/workflow_file_view.png" format="PNG"/> - </imageobject> - </mediaobject> - </para> - <para> - The user's who are designated as Approvers can view the CMS pending queue by clicking the <emphasis role="bold">Pending Items</emphasis> link in the flyout menu. The Pending Queue screen is as follows: - - <mediaobject> - <imageobject> - <imagedata fileref="images/admincms/workflow_pending_items.png" format="PNG"/> - </imageobject> - </mediaobject> - </para> -</section> -</section> + <title>Administration Content Management System (CMS) Portlet</title> + <section id="Portal_User_Guide-Administration_-_Content_Management_System-Introduction"> + <title>Introduction</title> + <para> + The CMSAdmin Portlet allows control over the content management system. + </para> + <para> + Viewing the CMSAdmin Portlet is accomplished by logging in as admin (admin/admin) and navigating to the admin portal and then the CMS Page tab. + </para> + <para> + You will then be presented with a page that is similar to this: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/cms_adminpage.png" format="PNG"/> + </imageobject> + </mediaobject> + </section> + <section id="Portal_User_Guide-Administration_-_Content_Management_System-Actions"> + <title>Actions</title> + <para> + This section describes common actions an administrator can perform from within the AdminCMS Portlet. All + actions are available using the flyout menu. Note that the Pending Items action is only available if the + workflow mechanism has been activated. + + + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/actions_menu.png" format="PNG"/> + </imageobject> + </mediaobject> + <section id="Portal_User_Guide-Actions-Viewing-Directories"> + <title>Viewing Directories</title> + <para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/ss_viewfile.png" format="PNG"/> + </imageobject> + </mediaobject> + + A user can list directory contents by either clicking on the folder name or selecting "view" from the Action + dropdown and clicking "go". + </para> + </section> + <section id="Portal_User_Guide-Actions-Viewing_File_Properties"> + <title>Viewing File Properties</title> + <para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/ss_viewfile.png" format="PNG"/> + </imageobject> + </mediaobject> + Clicking on the "Name" of a file brings up the File Properties page. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/fileproperties.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The File Properties window displays all the possible actions available to perform on a file. + </para> + <para> + Version and Locale Information are also contained on this screen. Note that any version labeled with a + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/live.png" format="PNG"/> + </imageobject> + </mediaobject> + + is the current "live" version shown to users. + </para> + </section> + <section id="Portal_User_Guide-Actions-Copying_Files"> + <title>Copying Files/Directories</title> + <para> + Clicking on the "Copy" action, displays the copy file/directory dialog window. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/resourcecopy.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The copy resource window allows a user to copy files to any folder on the system, as well as copy whole directory trees to any directory on the system. A user can select which + destination directory to copy the resource to by using the directory browser. Clicking the + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/plus.png" format="PNG"/> + </imageobject> + </mediaobject> + + icon expands the directory tree. Clicking on the name of the directory within the tree sets it as the destination directory for the copied resource. + + </para> + </section> + <section id="Portal_User_Guide-Actions-Moving_Files"> + <title>Moving Files/Directories</title> + <para> + Clicking on the "Move" action, displays the move file/directory dialog window. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/resourcemove.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The move resource window allows a user to move files to any folder on the system, as well as move whole directory trees to any directory on the system. A user can select which destination directory to move the resource to, by using the directory browser. Clicking the + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/plus.png" format="PNG"/> + </imageobject> + </mediaobject> + + icon expands the directory tree. Clicking on the name of the directory within the tree sets it as the destination directory for the moved resource. + + </para> + </section> + <section id="Portal_User_Guide-Actions-Deleting_Files"> + <title>Deleting Files/Directories</title> + <para> + Clicking on the "Delete" action, displays the delete file/directory confirmation window. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/resourcedelete.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The delete resource confirmation window allows a user to delete a file or a directory on the system. Note that deleting a directory will delete the entire tree, so all directories under the deleted one will also be deleted. + + </para> + <warning> + <para> + Currently, there is no way to retrieve deleted files/directories! Deleting a file or directory is permanent! + </para> + </warning> + </section> + <section id="Portal_User_Guide-Actions-Creating_Directories"> + <title>Creating Directories</title> + <para> + Clicking on the "Create Folder" action, displays the create directory dialog window. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/createdirectory.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The create directory resource window allows a user to create a directory under chosen path. On this window, a user can specify a name for the new empty directory and assign it a description. + </para> + </section> + <section id="Portal_User_Guide-Actions-Creating_Text"> + <title>Creating Text/HTML Files</title> + <para> + Clicking on the "Create File" action, displays the create file dialog window with the embedded WYSIWYG editor and directory browser. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/createhtml.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The create file window allows a user to create a text or HTML file using the embedded WYSIWYG HTML editor. The editor is a fully-functional HTML editor with a myriad of HTML functions. It also includes a preview + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/editorpreview.png" format="PNG"/> + </imageobject> + </mediaobject> + + button and a source view + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/editorsource.png" format="PNG"/> + </imageobject> + </mediaobject> + + button. + </para> + <para> + An in-depth walk-through of the editor is beyond the scope of this document. However, the editor does contain help pages within it, that can be accessed by clicking the + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/editorhelp.png" format="PNG"/> + </imageobject> + </mediaobject> + + icon. + </para> + <important> + <para> + It is important to note here that when creating links to images or other resources within the system, a user must use the relative file path to that resource. ie: images/hello.i.e.,. Keep in mind at all times that the document base is http://localhost/portal/ by default!</para> + </important> + <para> + Additionally, a user can set a title for the file that will be used in the portlet title bar, and a language for the file, used in serving localized content. + </para> + </section> + <section id="Portal_User_Guide-Actions-Uploading_Files"> + <title>Uploading Files</title> + <para> + Clicking on the "Upload File" action, displays the upload file dialog window. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/resourceupload.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The upload file window allows a user to upload files to any directory on the system. The upload process will work on files up to 1GB and of all types. A user can select which destination directory to upload the resource to, by using the directory browser. Clicking the + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/plus.png" format="PNG"/> + </imageobject> + </mediaobject> + + icon expands the directory tree. Clicking on the name of the directory within the tree, sets it as the destination directory for the uploaded resource. Additionally, a user can set a title for the file that will be used in the portlet title bar, and a language for the file, used in serving localized content. + </para> + </section> + <section id="Portal_User_Guide-Actions-Uploading-Archives"> + <title>Uploading Archives</title> + <para> + Clicking on the "Upload Archive" action, displays the upload archive dialog window. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/resourceuploadarchive.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The upload archive window allows a user to upload archives to any directory on the system. The system will then explode the archive, create versions, and place all the files in the repository. A user can select which destination directory to upload the resource to, by using the directory browser. Clicking the + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/plus.png" format="PNG"/> + </imageobject> + </mediaobject> + + icon expands the directory tree. Clicking on the name of the directory within the tree, sets it as the destination directory for the uploaded resource. Additionally, a user can set a language for the archive files, used in serving localized content. + + </para> + </section> + <section id="Portal_User_Guide-Actions-Exporting_Folders"> + <title>Exporting Folders</title> + <para> + Clicking on the "Export Folder" action, displays the export archive dialog window. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/ss_exportarchive.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The export folder window allows a user to export entire directory structures as zip files. The system will aggregate all contents of a specific directory, and present to the user to download it. + A user can select which source directory to export the resources from, by using the directory browser. Clicking the + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/plus.png" format="PNG"/> + </imageobject> + </mediaobject> + + icon expands the directory tree. Clicking on the name of the directory within the tree, sets it as the source directory for the export resource. Additionally, a user can set a language for the files to be exported. + </para> + <important> + <para> + Version information is not exported. Only versions labeled "Live" are exported! + </para> + </important> + </section> + <section id="Portal_User_Guide-Actions-Editing_Text"> + <title>Editing Text/HTML Files</title> + <para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/fileproperties.png" format="PNG"/> + </imageobject> + </mediaobject> + + Clicking on the "text/html"link, displays the edit file dialog window with the embedded WYSIWYG editor and directory browser. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/editfile.png" format="PNG"/> + </imageobject> + </mediaobject> + <para> + The edit file window allows a user to edit a text or HTML file using the embedded WYSIWYG HTML editor. The editor is a fully-functional HTML editor with a myriad of HTML functions. It also includes a preview + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/editorpreview.png" format="PNG"/> + </imageobject> + </mediaobject> + + button and a source view + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/editorsource.png" format="PNG"/> + </imageobject> + </mediaobject> + + button. + + </para> + <para> + A user may specify at this point if he would like to make the new edit "live", or available in production. Additionally, a user can set a title for the file that will be used as the portlet window title. + </para> + </section> + <section id="Portal_User_Guide-Actions-Securing_Resources"> + <title>Securing Resources</title> + <para> + Administrators are able to apply permissions settings to any folder or file in the CMS. These permissions on a specific node, can be applied on a per-Role and/or per-User basis. + </para> + <para> + The security dialogue is accessed by navigating to the node you want to secure and selecting <emphasis>Secure</emphasis> + . + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/secure_menu.png" format="PNG"/> + </imageobject> + </mediaobject> + </para> + <para> + You should then be presented with a screen that allows you to assign read, write, and manage privileges on the selected node for selected Roles or specific Users. + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/secure_node.png" format="PNG"/> + </imageobject> + </mediaobject> + + There are three main security settings for every node in the CMS. + <itemizedlist> + <listitem> + <para><emphasis role="bold">Read Permissions:</emphasis> + Assigned roles/users can view the resource.</para> + </listitem> + <listitem> + <para> + <emphasis role="bold">Write Permissions:</emphasis> Assigned roles/users are able to edit the resource, or create nodes within it (as is the case for folders)</para> + </listitem> + <listitem> + <para> + <emphasis role="bold">Manage Permissions:</emphasis> These permissions include: copy, move, delete, and exporting.</para> + </listitem> + </itemizedlist> + + Administrating and assigning permissions on a selected node is as simple as selecting which Roles and/or Users you want to allow to have a specific permission. + + </para> + </section> + <section id="Portal_User_Guide-Actions-Workflow"> + <title>Content Publish/Approval Workflow</title> + <para> + When the Publish/Approval Workflow service is activated on the CMS, any requests for publishing new content or making updates to existing content requires an Approval process before going "Live". You can specify a list of Portal Roles that can act as Approvers who can authorize/deny the publishing of content in the CMS. + </para> + <para> + When a content is created in the CMS, the screen should show an Pending Queue of Approvals for that particular content as shown below in the screen. The content waiting in this queue is not accessible for "Live" usage. + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/workflow_file_view.png" format="PNG"/> + </imageobject> + </mediaobject> + </para> + <para> + The user's who are designated as Approvers can view the CMS pending queue by clicking the <emphasis role="bold">Pending Items</emphasis> link in the flyout menu. The Pending Queue screen is as follows: + + <mediaobject> + <imageobject> + <imagedata fileref="images/admincms/workflow_pending_items.png" format="PNG"/> + </imageobject> + </mediaobject> + </para> + </section> + </section> </chapter> - Modified: docs/enterprise/trunk/User_Guide/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/Book_Info.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/User_Guide/en-US/Book_Info.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,35 +1,33 @@ -<?xml version='1.0'?> +<?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" [ ]> - <bookinfo id="Portal_User_Guide-Documentation"> - <title>User Guide</title> - <subtitle>A User Guide for Enterprise Portal Platform 4.3</subtitle> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>4.3</productnumber> - <edition>1</edition> - <pubsnumber>1.10</pubsnumber> - <abstract> - <para>This document is intended for those using JBoss Portal as End-Users. This is a "Where do I Click?" Guide.</para> - <para> + <title>User Guide</title> + <subtitle>A User Guide for Enterprise Portal Platform 4.3</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>4.3</productnumber> + <edition>4.3.7</edition> + <pubsnumber>1</pubsnumber> + <abstract> + <para>This document is intended for those using JBoss Portal as End-Users. This is a "Where do I Click?" Guide.</para> + <para> For Portlet developers, Portal administrators, and those wishing to extend and/or implement the JBoss Portal framework, there is a Reference Guide available from our <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index....">documentation page</ulink>. </para> - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata format='SVG' fileref="Common_Content/images/title_logo.svg" /> - </imageobject> - <textobject><phrase>Logo</phrase></textobject> - </inlinemediaobject> - </corpauthor> - <copyright> - <year>&YEAR;</year> - <holder>&HOLDER;</holder> - </copyright> - <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata format="SVG" fileref="Common_Content/images/title_logo.svg"/> + </imageobject> + <textobject> + <phrase>Logo</phrase> + </textobject> + </inlinemediaobject> + </corpauthor> + <copyright> + <year>&YEAR;</year> + <holder>&HOLDER;</holder> + </copyright> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Common_Content/Legal_Notice.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Author_Group.xml"/> </bookinfo> - - - Modified: docs/enterprise/trunk/User_Guide/en-US/Dynamicity.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/Dynamicity.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/User_Guide/en-US/Dynamicity.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,150 +1,134 @@ -<?xml version='1.0'?> +<?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="Portal_User_Guide-Dynamicity"> - <title>Administration - Portal Object Management (Dynamicity)</title> - - <section id="Portal_User_Guide-Dynamacity-Introduction"> - <title>Introduction</title> - - - - <para> + <title>Administration - Portal Object Management (Dynamicity)</title> + <section id="Portal_User_Guide-Dynamacity-Introduction"> + <title>Introduction</title> + <para> The concept of dynamicity refers to the fact all portal objects can be dynamically modified at runtime, eliminating the need to struggle with large xml files, or restarting the application server for changes to take effect. In the scope of dynamicity, portal objects are defined and can be altered as follows: <itemizedlist> - <listitem> - <para>Portal Instances: Multiple Portal instances can be launched at any time, secured, and skinned.</para></listitem> - <listitem><para>Pages: Multiple pages, composed of windows, can securely coexist inside a portal instance. Each - could have its own theme applied, if desired.</para></listitem> - <listitem><para>Portlets: Can be hot-deployed and will instantly register with the portal, appearing in the - management portlet.</para></listitem> - <listitem><para>Portlet Instances: Instances can be created/destroyed. Instance preference variables can be modified - at runtime, assigned to windows and secured.</para></listitem> - <listitem><para>Windows: Windows can be secured, created/destroyed, and assigned to specific pages.</para></listitem> - <listitem><para>Themes/Layouts: Can be hot-deployed and will register with the portal. They appear in the management + <listitem> + <para>Portal Instances: Multiple Portal instances can be launched at any time, secured, and skinned.</para> + </listitem> + <listitem> + <para>Pages: Multiple pages, composed of windows, can securely coexist inside a portal instance. Each + could have its own theme applied, if desired.</para> + </listitem> + <listitem> + <para>Portlets: Can be hot-deployed and will instantly register with the portal, appearing in the + management portlet.</para> + </listitem> + <listitem> + <para>Portlet Instances: Instances can be created/destroyed. Instance preference variables can be modified + at runtime, assigned to windows and secured.</para> + </listitem> + <listitem> + <para>Windows: Windows can be secured, created/destroyed, and assigned to specific pages.</para> + </listitem> + <listitem> + <para>Themes/Layouts: Can be hot-deployed and will register with the portal. They appear in the management portlet, allowing for dynamic customization of any of the above components.</para> - </listitem> - </itemizedlist> + </listitem> + </itemizedlist> </para> - <note> - <para> + <note> + <para> Viewing the Management Portlet is accomplished by logging in as an admin (admin/admin) and navigating to the Admin portal (see <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"/>). </para> - </note> - -  - - </section> - - <section id="Portal_User_Guide-Dynamicity-Management_Portlet"> - <title>Management Portlet</title> - - - - <para> + --> </section> + <section id="Portal_User_Guide-Dynamicity-Management_Portlet"> + <title>Management Portlet</title> + <para> The management portlet provides a two-part interface: tabs at the top which correspond to the different sections that can be managed; and the main area under it, which displays the current information for the selected tab. </para> - <note> - <para> + <note> + <para> For the remainder of this chapter, the term <emphasis role="bold">object</emphasis> will be used to mean Portal, Page, Portlet, or Window indifferently. </para> - </note> - <para> - <mediaobject> - <imageobject> - <imagedata fileref="images/intro/adminportal.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> - </para> - <para> + </note> + <mediaobject> + <imageobject> + <imagedata fileref="images/intro/adminportal.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> + <para> The tabs are: <itemizedlist> - <listitem> - <para><emphasis role="bold">Portal Objects</emphasis> gather operations pertaining to managing portal objects + <listitem> + <para><emphasis role="bold">Portal Objects</emphasis> gather operations pertaining to managing portal objects (portal instances, pages, windows and their respective configuration information). This is the most complex part of the interface.</para> - </listitem> - <listitem><para><emphasis role="bold">Portlet Instances</emphasis> give access to all the Portlet instances that have been + </listitem> + <listitem> + <para><emphasis role="bold">Portlet Instances</emphasis> give access to all the Portlet instances that have been configured.</para> - </listitem> - <listitem><para><emphasis role="bold">Portlet Definitions</emphasis> give access to the currently available portlet + </listitem> + <listitem> + <para><emphasis role="bold">Portlet Definitions</emphasis> give access to the currently available portlet providers as well as the Portlets that each provider publishes.</para> - </listitem> - <listitem> - <para><emphasis role="bold">Dashboards</emphasis> allow administrators to configure how Dashboards should behave.</para> - </listitem> - </itemizedlist> + </listitem> + <listitem> + <para><emphasis role="bold">Dashboards</emphasis> allow administrators to configure how Dashboards should behave.</para> + </listitem> + </itemizedlist> We will look at each of these tabs and their functionality in the following sections. </para> - - - - <section id="Portal_User_Guide-Management_Portlet-Managing_Portal_Objects"> - <title>Managing Portal Objects</title> - - - - - <section id="Portal_User_Guide-Managing_Portal_Objects-Portals_Operations"> - <title>Portals Operations</title> - - - <mediaobject> - <imageobject> - <imagedata fileref="images/management/portals.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> - - <para> + <section id="Portal_User_Guide-Management_Portlet-Managing_Portal_Objects"> + <title>Managing Portal Objects</title> + <section id="Portal_User_Guide-Managing_Portal_Objects-Portals_Operations"> + <title>Portals Operations</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/management/portals.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> + <para> <emphasis role="bold">Portal Objects</emphasis> brings the administrator to a page displaying a list of the available portal instances defined for this Portal server. Several points are of particular interest. First, a - navigation indicator or "breadcrumbs" is located right beneath the tabs. This provides context as to + navigation indicator or "breadcrumbs" is located right beneath the tabs. This provides context as to where in the hierarchy of portal objects the current screen is located. Some of the screens can be found at several levels of the hierarchy. If you are lost, refer to the breadcrumbs for context. When you first click on the <emphasis role="bold">Portal Objects</emphasis> tab, the context is the list of portals as shown in the picture above. </para> - - <para> + <para> A link to access server-wide portal properties is located right beneath the breadcrumbs. This allows the administrator to set server-wide property and configure how errors should be handled: <mediaobject> - <imageobject> - <imagedata fileref="images/management/portals_properties.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/portals_properties.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> Please refer to the - <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Error - handling</ulink> chapter of the JBoss Portal Reference Guide for more information on this point. + <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Error handling</ulink> chapter of the JBoss Portal Reference Guide for more information on this point. </para> - - <para> + <para> A form allowing administrator to create new portal instances is located beneath the <literal>Properties</literal> link. Enter the name of the new portal (which, of course, should be different from any of the already existing one) and click on <literal>Create portal</literal> and the portal instances list will be refreshed to display the newly created portal instance. </para> - - <para> + <para> The last element at this level is a table listing all the available portal instances along with possible actions on them. Clicking on the portal name will display a screen showing the information for this given portal instance, thus drilling down the @@ -158,33 +142,29 @@ refreshed and the selected portal status will be refreshed, its action now showing its <literal>Default</literal> status. </para> - - <para> + <para> In the next sections we will demonstrate the functionality of the management portlet by drilling progressively further down this hierarchy to look at the default portal, one of its pages, show how to configure content on a page and, finally, look at specific window information. </para> -</section> - - <section id="Portal_User_Guide-Managing_Portal_Objects-Portal_instance_configuration"> - <title>Looking at portal instance information</title> - - <para> + </section> + <section id="Portal_User_Guide-Managing_Portal_Objects-Portal_instance_configuration"> + <title>Looking at portal instance information</title> + <para> If you click on the <literal>default</literal> portal in the list of available portal instances on the top-level <literal>Portal Objects</literal> page, you will be taken to a page showing the information - for the portal instance named "default", as shown below: + for the portal instance named "default", as shown below: <mediaobject> - <imageobject> - <imagedata fileref="images/management/default_portal.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/default_portal.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> Note the breadcrumbs at the top of the screen indicating where in the hierarchy you currently are. In this case, we are looking at the <literal>default</literal> portal. </para> - - <para> + <para> Links to more information and operations that affect this portal instance are located beneath the breadcrumbs. We will look at them in turn later, excluding the <literal>Destroy</literal> operation, which as its name implies, allows an @@ -192,14 +172,12 @@ available in the portal instances list on the top level page, <literal>Make Default/Default</literal> excepted. </para> - - <para> + <para> It is possible to create new pages using the page creation form located under the portal-wide operation links. Enter the new page name and click on <literal>Create page</literal> and the new page will appear in the pages list, ready to be configured. </para> - - <para> + <para> Finally, a table displaying the list of available pages for this portal instance is located at the bottom of this screen. The first column shows the page name, which you can click to drill down the hierarchy and display the information specific to that particular page. The second column, on the other @@ -210,131 +188,115 @@ in this list: this is where you specify which page should be the default one when users first access the portal instance. </para> - - <para> - Let's now look at the default portal's <literal>Security</literal> information screen. This can be + <para> + Let's now look at the default portal's <literal>Security</literal> information screen. This can be accessed by clicking the <literal>Security</literal> action link on the portal page. Here, an administrator can configure the default policy for security on objects for this portal instance: <mediaobject> - <imageobject> - <imagedata fileref="images/management/default_portal_security.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/default_portal_security.png" format="PNG"/> + </imageobject> + </mediaobject> Please refer to the - <ulink - url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Security - </ulink> + <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Security </ulink> chapter of the JBoss Portal Reference Guide for more information about how to secure portal objects. </para> - - <para> + <para> The <literal>Properties</literal> action link displays the currently configured properties for this portal instance and allows you to modify them, as well as configure the error handling strategy: <mediaobject> - <imageobject> - <imagedata fileref="images/management/default_portal_properties.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/default_portal_properties.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> </para> - - <para> + <para> The <literal>Theme</literal> action link displays a screen where the administrator can configure theme, layout and render set for this portal instance: <mediaobject> - <imageobject> - <imagedata fileref="images/management/default_portal_theme.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/default_portal_theme.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> Please refer to the - <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Layouts - and Themes</ulink> + <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Layouts and Themes</ulink> chapter of the Reference Guide for more information about themes and layouts. </para> - - <para> + <para> The <literal>Display Name</literal> action link displays a screen where the administrator can configure different names for different languages: <mediaobject> - <imageobject> - <imagedata fileref="images/management/display_names.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/display_names.png" format="PNG"/> + </imageobject> + </mediaobject> The different names will be used as page display names for the preferred locale of the logged-in user. This is used by the default tab navigation of the default layouts. </para> - - <para> - Now that we have looked at portal level information, let's drill down the hierarchy again and look at + <para> + Now that we have looked at portal level information, let's drill down the hierarchy again and look at a page, more precisely the <literal>default</literal> page, by clicking its name in the pages list. </para> - </section> - -<section id="Portal_User_Guide-Managing_Portal_Objects-Page_configuration"> - <title>Looking at a page configuration</title> - - - - <para> + </section> + <section id="Portal_User_Guide-Managing_Portal_Objects-Page_configuration"> + <title>Looking at a page configuration</title> + <para> <mediaobject> - <imageobject> - <imagedata fileref="images/management/default_page.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/default_page.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> The layout of this screen should start feeling familiar. The information for a page looks a lot like the information for a portal instance. Note the breadcrumbs indicating that you are indeed looking at a page. Again, we find the action links at the top of the page, mirroring the ones that were available - for each page in the pages list of the portal instance screen. Once again, you can configure the page's + for each page in the pages list of the portal instance screen. Once again, you can configure the page's security, theme and properties. You can also destroy it if so desired. </para> - - <para> + <para> Similarly to other screens in the portal objects hierarchy, a page configuration screen also provides a list of all windows for that page. This list contains two columns: the first one contains the name of the window, while the second one provides a list of action links for that specific window. Clicking on a window name will display information about that window. </para> - - <para> + <para> Just like a portal instance can contain several pages, a page can contain several subpages. As such a page defines means to create subpages and set which subpage to display when a user is first directed to the page. These operations work similarly to the same operations at the portal instance level. </para> - - <para> + <para> You can also rename the page if desired: <mediaobject> - <imageobject> - <imagedata fileref="images/management/default_page_rename.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/default_page_rename.png" format="PNG"/> + </imageobject> + </mediaobject> </para> - - <para> + <para> Of specific interest, though, is the <literal>Page Layout</literal> link. This is where you need to go to configure which portlet instance will be displayed in which window on which region on the page. - Let's take a look at this screen and how it works: + Let's take a look at this screen and how it works: <mediaobject> - <imageobject> - <imagedata fileref="images/management/default_page_layout.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/default_page_layout.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> This screen is structured in two parts, flowing from left to right, following the natural process involved in displaying content on a page. First, you need to identify which content you want to @@ -342,99 +304,95 @@ figure out where on the page should this content be displayed, hence the <literal>Page Layout</literal> section. </para> - - <para> - Let's add a window named <literal>test</literal> displaying the content of the portlet instance + <para> + Let's add a window named <literal>test</literal> displaying the content of the portlet instance named <literal>NewsPortletInstance</literal> to the center region, beneath the already existing <literal>CMSWindow</literal>. First, we need to enter our new window name in the <literal>Window name</literal> field and select the <literal>portlet</literal> content type from the drop down menu: <mediaobject> - <imageobject> - <imagedata fileref="images/management/layout_content.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/layout_content.png" format="PNG"/> + </imageobject> + </mediaobject> Once this is done, we can select the portlet instance by clicking its name in the instances list: <mediaobject> - <imageobject> - <imagedata fileref="images/management/layout_instance.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/layout_instance.png" format="PNG"/> + </imageobject> + </mediaobject> Note that this displays some information about the portlet instance. Finally, we can add our window to the center region of the page by clicking on the <literal>Add</literal> button located left to the windows list for the region: <mediaobject> - <imageobject> - <imagedata fileref="images/management/layout_region.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/layout_region.png" format="PNG"/> + </imageobject> + </mediaobject> Note that we could move the window up or down in the region by selecting it in the list and using the button to the right of the list, or even destroy it if desired. </para> - - <para> - We can repeat this process to add content of different types. Let's add a window using a Google widget - game. First, give a name to your window (we'll use "google" here) + <para> + We can repeat this process to add content of different types. Let's add a window using a Google widget + game. First, give a name to your window (we'll use "google" here) and select <literal>widget/google</literal> from the content type drop-down menu: <mediaobject> - <imageobject> - <imagedata fileref="images/management/layout_google1.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/layout_google1.png" format="PNG"/> + </imageobject> + </mediaobject> Note how the instances list is replaced by a list of Google widgets. The widget we want to use is located in the <literal>Fun & Games</literal> category, so select it from the category drop-down menu: <mediaobject> - <imageobject> - <imagedata fileref="images/management/layout_google2.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/layout_google2.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> Press <literal>Search Gadgets</literal> and the widget list will be refreshed. The widget we want is <literal>Bejeweled</literal>: <mediaobject> - <imageobject> - <imagedata fileref="images/management/layout_google3.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/layout_google3.png" format="PNG"/> + </imageobject> + </mediaobject> You can now add the new window to the desired region. </para> - - <para> - Let's repeat this process again, this time with content from CMS. Enter a new window name (we'll - use "cms" here) and select <literal>cms</literal> from the content type drop-down menu: + <para> + Let's repeat this process again, this time with content from CMS. Enter a new window name (we'll + use "cms" here) and select <literal>cms</literal> from the content type drop-down menu: <mediaobject> - <imageobject> - <imagedata fileref="images/management/layout_cms1.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/layout_cms1.png" format="PNG"/> + </imageobject> + </mediaobject> Once again, the instances list was replaced by a directory listing showing the available content roots. Click on <literal>default</literal> and select <literal>project.html</literal>: <mediaobject> - <imageobject> - <imagedata fileref="images/management/layout_cms2.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/layout_cms2.png" format="PNG"/> + </imageobject> + </mediaobject> You can now add the window to the desired region. </para> - - <para> + <para> - We've added three new windows to the default page using different content types. We added a window + We've added three new windows to the default page using different content types. We added a window displaying the content of a portlet (displaying the content of an RSS feed in this case). Another one displaying a Google widget and yet another one some CMS-issued content. We decided to remove the existing <literal>CMSWindow</literal>, add the <literal>cms</literal> window below the @@ -442,38 +400,31 @@ to the left region, below the existing content: <mediaobject> - <imageobject> - <imagedata fileref="images/management/layout_final.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/layout_final.png" format="PNG"/> + </imageobject> + </mediaobject> If all went well, logging out of the Admin portal, you should see: <mediaobject> - <imageobject> - <imagedata fileref="images/management/default_page_after.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/default_page_after.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> </para> - - <para> + <para> You can read more about - <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Content - Integration - </ulink> + <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Content Integration </ulink> in the Reference Guide. More details on how to setup content roots in CMS are available in <xref linkend="Portal_User_Guide-Administration_-_Content_Management_System-Introduction"/>. </para> - -</section> - - -<section id="Portal_User_Guide-Managing_Portal_Objects-Window_configuration"> - <title>Looking at windows of a given page</title> - - <para> + </section> + <section id="Portal_User_Guide-Managing_Portal_Objects-Window_configuration"> + <title>Looking at windows of a given page</title> + <para> Window operations are similar to the same operations at other level of the hierarchy of portal objects. The only information displayed when a window name is clicked in the windows list of a portal page information screen is information about the content, similar to the one that is displayed in the @@ -481,106 +432,92 @@ section: <mediaobject> - <imageobject> - <imagedata fileref="images/management/google_window.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/google_window.png" format="PNG"/> + </imageobject> + </mediaobject> </para> -</section> -</section> - + </section> + </section> <section id="Portal_User_Guide-Management_Portlet-Managing_Portlet_Instances"> - <title>Managing Portlet Instances</title> - - <para> + <title>Managing Portlet Instances</title> + <para> The <literal>Portlet Instances</literal> tab brings the administrator to the list of instances created in the running portal. On this page, the user can either modify the security constraints for the portlet (to grant access only to certain roles), destroy an instance or override the portlet definition preferences for a specific instance if there is any overridable preference. <mediaobject> - <imageobject> - <imagedata fileref="images/management/instances.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/instances.png" format="PNG"/> + </imageobject> + </mediaobject> </para> -</section> - - <section id="Portal_User_Guide-Management_Portlet-Managing_Portlet_Definitions"> - <title>Managing Portlet Definitions</title> - - <para> + </section> + <section id="Portal_User_Guide-Management_Portlet-Managing_Portlet_Definitions"> + <title>Managing Portlet Definitions</title> + <para> The <literal>Portlet Definitions</literal> tab brings the administrator to the list of portlet definitions, formatted as a table displaying name, description, whether the portlet is remote (i.e., accessed - via WSRP from a remote producer) or if it is remotable (i.e., if it is exposed to WSRP consumers by Portal's + via WSRP from a remote producer) or if it is remotable (i.e., if it is exposed to WSRP consumers by Portal's producer). </para> - - <para> + <para> Portlet definitions can be made available by different providers. You can select the provider you want to browse by selecting it in the drop-down menu and clicking <literal>View portlets</literal>. By default, two providers are available: <itemizedlist> - <listitem> - <para><emphasis role="bold">local</emphasis>: this is Portal's portlet container. Any successfully deployed portlet will + <listitem> + <para><emphasis role="bold">local</emphasis>: this is Portal's portlet container. Any successfully deployed portlet will appear in the list of available portlet definitions for this provider.</para> - </listitem> - <listitem> - <para><emphasis role="bold">self</emphasis>: this is Portal's default WSRP consumer configured to consume portlets - published by Portal's own WSRP producer. This doesn't have much practical interest apart from allowing + </listitem> + <listitem> + <para><emphasis role="bold">self</emphasis>: this is Portal's default WSRP consumer configured to consume portlets + published by Portal's own WSRP producer. This doesn't have much practical interest apart from allowing a quick test of the WSRP functionality of Portal.</para> - </listitem> - </itemizedlist> + </listitem> + </itemizedlist> More providers can be added to this list. In particular, any active, properly configured WSRP consumer will also appear in the drop-down menu. Please refer to the - <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Consuming - remote WSRP portlets in JBoss Portal - </ulink> + <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">Consuming remote WSRP portlets in JBoss Portal </ulink> chapter of the Reference Guide for more information on this topic. <mediaobject> - <imageobject> - <imagedata fileref="images/management/portlets.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/portlets.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> </para> - - <para> + <para> Clicking on a portlet name in the list will display the portlet definition title, description, supported languages and keywords. <mediaobject> - <imageobject> - <imagedata fileref="images/management/portlet_details.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/portlet_details.png" format="PNG"/> + </imageobject> + </mediaobject> The <literal>Preferences</literal> action (when available) is used to edit preferences at the portlet definition level as explained in the JSR-168 specification. </para> - -</section> - -<section id="Portal_User_Guide-Management_Portlet-Managing_Dashboards"> - <title>Managing Dashboards</title> - - <para> + </section> + <section id="Portal_User_Guide-Management_Portlet-Managing_Dashboards"> + <title>Managing Dashboards</title> + <para> The <literal>Dashboards</literal> tab allows the administrator to configure parameters for all user dashboards. It also allows the user to configure the error pages and theme properties as for the other portal objects. </para> -</section> - -<section id="Portal_User_Guide-Management_Portlet-Wizard_mode"> - <title>Wizard mode</title> - - - <para> + </section> + <section id="Portal_User_Guide-Management_Portlet-Wizard_mode"> + <title>Wizard mode</title> + <para> The wizard mode is a fast and easy way to create a new window on a page backed by a portlet instance. The user just needs to define which portlet definition to use and where the instance should be located (portal / page / location on the page. The wizard will automatically create a new instance of @@ -588,19 +525,12 @@ defined by the user. <mediaobject> - <imageobject> - <imagedata fileref="images/management/wizard.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/wizard.png" format="PNG"/> + </imageobject> + </mediaobject> </para> - - - - </section> - - </section> - + </section> </chapter> - Modified: docs/enterprise/trunk/User_Guide/en-US/JBoss_Portal_Basics.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/JBoss_Portal_Basics.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/User_Guide/en-US/JBoss_Portal_Basics.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,35 +1,27 @@ -<?xml version='1.0'?> +<?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="Portal_User_Guide-JBoss_Portal_Basics"> - <title>JBoss Portal Basics</title> - - - <section id="Portal_User_Guide-JBoss_Portal_Basics-Portal_Concepts"> - <title>Portal Concepts - Illustrated</title> - - <para> + <title>JBoss Portal Basics</title> + <section id="Portal_User_Guide-JBoss_Portal_Basics-Portal_Concepts"> + <title>Portal Concepts - Illustrated</title> + <para> This section will introduce the reader to some basic portal terms and concepts used within JBoss Portal and throughout this document. </para> - - <section id="Portal_User_Guide-Portal_Concepts-Portal_Instances"> - <title>Portal Instances</title> - - <para> - JBoss Portal supports multiple portal instances running within one container. A portal instance can be viewed as a 'bucket', containing portal objects such as Portal Pages, Themes, Layouts, and Portlet Windows. It also manages the relationship between the user and the portal itself. The hierarchy of portal objects is depicted in the following diagram: + <title>Portal Instances</title> + <para> + JBoss Portal supports multiple portal instances running within one container. A portal instance can be viewed as a 'bucket', containing portal objects such as Portal Pages, Themes, Layouts, and Portlet Windows. It also manages the relationship between the user and the portal itself. The hierarchy of portal objects is depicted in the following diagram: <mediaobject> - <imageobject> - <imagedata fileref="images/management/tree.gif" format="GIF" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/management/tree.gif" format="GIF" scalefit="1"/> + </imageobject> + </mediaobject> </para> - - <para> + <para> A portal instance is reachable by the url format <emphasis>http://<replaceable>[domain]</replaceable>/<replaceable>[context]</replaceable>/portal/<replaceable>[portal_name]</replaceable></emphasis>. In a default/local install, the @@ -38,16 +30,13 @@ http://localhost:8080/portal/portal/default.Consult your portal administrator for information on the available portal instances - some of which may have restricted logins. . </para> - -</section> - + </section> <section id="Portal_User_Guide-Portal_Concepts-Portal_Pages"> - <title>Pages</title> - <para> + <title>Pages</title> + <para> A Portal Page is an aggregator of Portlet Windows. It is generated by the portal, during the response phase. During this phase, the portal aggregates all of the HTML markup created by the individual portlets, decorates them with window controls, and presents them to the user as a consolidated page. </para> - - <para> + <para> A portal page is reachable by the url format <emphasis>http://<replaceable>[domain]</replaceable>/<replaceable>[context]</replaceable>/portal/<replaceable>[portal_name]</replaceable>/<replaceable>[page_name]</replaceable></emphasis>. In a default/local install, the <emphasis>default</emphasis> @@ -60,44 +49,41 @@ http://localhost:8080/portal/portal/default/News </para> - - <para> + <para> More, on navigating the portal pages and what they contain can be found in, <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Contents_Pages"/> </para> </section> - -<section id="Portal_User_Guide-Portal_Concepts-Portlet_Windows"> - - <title>Portlet Windows</title> - <para> + <section id="Portal_User_Guide-Portal_Concepts-Portlet_Windows"> + <title>Portlet Windows</title> + <para> Portlet Windows are found on Portal Pages and contain the HTML markup for a specific portlet instance. <mediaobject> - <imageobject> - <imagedata fileref="images/intro/window.jpg" format="JPG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/window.jpg" format="JPG" scalefit="1"/> + </imageobject> + </mediaobject> The diagram above shows the default JBoss Portal page with certain window-related items highlighted (in red). Lets look at these items: </para> - <itemizedlist> - <listitem> - <para> + <itemizedlist> + <listitem> + <para> <emphasis role="bold">Window Title:</emphasis> Defines the content and purpose of the individual portlet window. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <emphasis role="bold">Window Fragment:</emphasis> Generated HTML markup produced by the portlet on the server-side. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <emphasis role="bold">Window Controls:</emphasis> Window controls are divided into two categories and control different aspects of how the user can impact the generated markup. Each window control can be clicked on to interact with the window in @@ -106,683 +92,598 @@ <emphasis role="bold">Portlet Mode</emphasis> icons, on the other hand, control the mode in which the portlet operates, thus impacting the type of generated markup. Note that not all portlets support all defined window states and/or portlet modes. The table below explains the different Window State icons and their meaning. - </para> - </listitem> - </itemizedlist> - <table id="Table_1"> - <title>Window state icons and their meaning</title> - <tgroup cols="3"> - <colspec colname="c1" colnum="1" colwidth="1*"/> - <colspec colname="c2" colnum="2" colwidth="4*"/> - <colspec colname="c3" colnum="3" colwidth="4*"/> - <thead> - <row> - <entry> - Window State - </entry> - <entry> - Icon - </entry> - <entry> - Meaning - </entry> - - </row> - </thead> - <tbody> - <row> - <entry> - Normal - </entry> - <entry> - <mediaobject> - <imageobject> - <imagedata fileref="images/intro/ico_16_normal.gif" format="GIF"/> - </imageobject> - </mediaobject> - </entry> - - - <entry> - Normal window state, is the most common state for portlets (portlets in the above image are in the normal window state). The portlet window will occupy only enough space to show the portlet content on the page. - </entry> - - - - </row> - <row> - <entry> - Minimized - </entry> - <entry> - <mediaobject> - <imageobject> - <imagedata fileref="images/intro/ico_16_minimize.gif" format="GIF"/> - </imageobject> - </mediaobject> - </entry> - - <entry> - The portlet is instructed to render minimal-to-no markup. - </entry> - </row> - <row> - <entry> - Maximized - </entry> - <entry> - <mediaobject> - <imageobject> - <imagedata fileref="images/intro/ico_16_maximize.gif" format="GIF"/> - </imageobject> - </mediaobject> - </entry> - - <entry> - The portlet window can occupy as much space of real estate on the page. - </entry> - </row> - </tbody> - </tgroup> - </table> - - - - <para> + </para> + </listitem> + </itemizedlist> + <table id="Table_1"> + <title>Window state icons and their meaning</title> + <tgroup cols="3"> + <colspec colname="c1" colnum="1" colwidth="1*"/> + <colspec colname="c2" colnum="2" colwidth="4*"/> + <colspec colname="c3" colnum="3" colwidth="4*"/> + <thead> + <row> + <entry> Window State </entry> + <entry> Icon </entry> + <entry> Meaning </entry> + </row> + </thead> + <tbody> + <row> + <entry> Normal </entry> + <entry> + <mediaobject> + <imageobject> + <imagedata fileref="images/intro/ico_16_normal.gif" format="GIF"/> + </imageobject> + </mediaobject> + </entry> + <entry> Normal window state, is the most common state for portlets (portlets in the above image are in the normal window state). The portlet window will occupy only enough space to show the portlet content on the page. </entry> + </row> + <row> + <entry> Minimized </entry> + <entry> + <mediaobject> + <imageobject> + <imagedata fileref="images/intro/ico_16_minimize.gif" format="GIF"/> + </imageobject> + </mediaobject> + </entry> + <entry> The portlet is instructed to render minimal-to-no markup. </entry> + </row> + <row> + <entry> Maximized </entry> + <entry> + <mediaobject> + <imageobject> + <imagedata fileref="images/intro/ico_16_maximize.gif" format="GIF"/> + </imageobject> + </mediaobject> + </entry> + <entry> The portlet window can occupy as much space of real estate on the page. </entry> + </row> + </tbody> + </tgroup> + </table> + <para> <emphasis role="bold">Portlet Modes and their meaning:</emphasis> Portlet modes are not always available (it depends on the portlet support for a given mode). Moreover, the Edit mode is only available to logged-in users, as in this mode, the portlet - preferences can be modified to be individually suited to a particular user's needs. + preferences can be modified to be individually suited to a particular user's needs. </para> - <itemizedlist> - <listitem> - <para> + <itemizedlist> + <listitem> + <para> <mediaobject> - <imageobject> - <imagedata fileref="images/intro/ico_edit.gif" format="GIF"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/ico_edit.gif" format="GIF"/> + </imageobject> + </mediaobject> <emphasis role="bold">Edit</emphasis> : Only visible to logged-in users. Allows a logged-in user to customize the - portlet's preferences. + portlet's preferences. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <mediaobject> - <imageobject> - <imagedata fileref="images/intro/ico_cancel.gif" format="GIF"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/ico_cancel.gif" format="GIF"/> + </imageobject> + </mediaobject> <emphasis role="bold">Return to View mode</emphasis> - : The button labeled 'Cancel' is only visible when a user is logged in and the + : The button labeled 'Cancel' is only visible when a user is logged in and the portlet associated to the current window is in the Edit mode. This replaces the Edit button so the user understands that by clicking it the user will leave the - "Edit mode" and revert back to "View mode". Portlets are by default in View + "Edit mode" and revert back to "View mode". Portlets are by default in View mode. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <mediaobject> - <imageobject> - <imagedata fileref="images/intro/ico_16_help.gif" format="GIF"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/ico_16_help.gif" format="GIF"/> + </imageobject> + </mediaobject> <emphasis role="bold">Help</emphasis> : Allows a user to access useful information about the portlet. </para> - </listitem> - </itemizedlist> - - -</section> -</section> - -<section id="Portal_User_Guide-JBoss_Portal_Basics-Contents_Pages"> - <title>Default Portal installation</title> - - <para> + </listitem> + </itemizedlist> + </section> + </section> + <section id="Portal_User_Guide-JBoss_Portal_Basics-Contents_Pages"> + <title>Default Portal installation</title> + <para> This section covers the default Portal installation and the pages and portlets that come with it. </para> - -<section id="Portal_User_Guide-Contents_Pages-Default_Portal_Pages"> - <title>Default Portal Pages</title> - - <para> + <section id="Portal_User_Guide-Contents_Pages-Default_Portal_Pages"> + <title>Default Portal Pages</title> + <para> Three pages are available in the default Portal: Home, News and Weather. You can access pages either by entering the page URL in your browser location bar, as shown in <xref linkend="Portal_User_Guide-Portal_Concepts-Portal_Pages"/>, or by clicking the tab associated to the page in the Navigation Tabs at the top of the page. <mediaobject> - <imageobject> - <imagedata fileref="images/intro/tabs.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/tabs.png" format="PNG"/> + </imageobject> + </mediaobject> </para> - - - <para> + <para> Although there are no pages with sub-pages in the default Portal installation, you can configure the navigation tabs to support sub-page navigation. By hovering over a tab with child Pages, it will display a menu for those subpages: <mediaobject> - <imageobject> - <imagedata fileref="images/intro/nav_sub.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/nav_sub.png" format="PNG"/> + </imageobject> + </mediaobject> , .</para> - - <para> + <para> While you can use a Portal anonymously, it is much more interesting to do so while logged in, as you get the opportunity to customize the content you want to see or even create your own personal Dashboard, as explained in <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Dashboard"/> . </para> -</section> - -<section id="Portal_User_Guide-Contents_Pages-Logging_In"> - <title>Logging in to the Portal</title> - - <para> + </section> + <section id="Portal_User_Guide-Contents_Pages-Logging_In"> + <title>Logging in to the Portal</title> + <para> Logging in to the portal is accomplished by clicking the <emphasis>Login</emphasis> link at the top-right of the portal page. The portal will present you with a login screen where you can enter your credentials: <mediaobject> - <imageobject> - <imagedata fileref="images/intro/login_ss.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/login_ss.png" format="PNG"/> + </imageobject> + </mediaobject> The default Portal installation defines two users: a regular user with no special privileges (login: <literal>user</literal>, password: <literal>user</literal>) and an - administrator user who can alter Portal's content (login: <literal>admin</literal>, password: + administrator user who can alter Portal's content (login: <literal>admin</literal>, password: <literal>admin</literal>). </para> - <para> + <para> Once logged in, the top-right menu will change so you can then navigate to your personal dashboard or log out. If you have access to other portal instances, they will be shown here as well. <mediaobject> - <imageobject> - <imagedata fileref="images/intro/logged.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/logged.png" format="PNG"/> + </imageobject> + </mediaobject> </para> - <note> - <para> + <note> + <para> If you login as an administrator, you will also be presented with a link to the <emphasis role="bold">Admin</emphasis> portal. </para> - </note> - -</section> -</section> - - <section id="Portal_User_Guide-Contents_Pages-Home_Page"> - <title>Home Page</title> - - - + </note> + </section> + </section> + <section id="Portal_User_Guide-Contents_Pages-Home_Page"> + <title>Home Page</title> <section id="Portal_User_Guide-Home_Page-Intro_greetings_portlet"> - <title>Greetings Portlet</title> - - <para> + <title>Greetings Portlet</title> + <para> <mediaobject> - <imageobject> - <imagedata fileref="images/intro/greetings.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/greetings.png" format="PNG"/> + </imageobject> + </mediaobject> The Greetings Portlet displays default authentication information on logging in, as well as a link to the official documentation. It is using JSP to show right from the first page, three heteregenous components, a JSP portlet, a JSF portlet and a CMS content. </para> -</section> - + </section> <section id="Portal_User_Guide-Home_Page-Intro_user_portlet"> - <title>Identity User Portlet</title> - - <note> - <para> + <title>Identity User Portlet</title> + <note> + <para> Administrators should view <xref linkend="Portal_User_Guide-User_Role-Managing_Users"/> for managing the portal user base. Only user operations are covered in this section.</para> - </note> - <para> + </note> + <para> <mediaobject> - <imageobject> - <imagedata fileref="images/intro/user_portlet.png" format="PNG" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/user_portlet.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> </para> - <para> + <para> Once successfully logged in to the Identity User Portlet, the user will have additional functionality at their disposal, that is covered in the following sections. <mediaobject> - <imageobject> - <imagedata fileref="images/intro/user_portlet_loggedin.png" format="PNG" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/user_portlet_loggedin.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> The Identity User Portlet allows a user to: <itemizedlist> - <listitem> - <para> + <listitem> + <para> <emphasis role="bold">Create a new account</emphasis> </para> - <para> + <para> Create a new account by clicking on the <emphasis role="bold">Register</emphasis> link in the navigation of the portlet. A user can then fill in the necessary information to create an account on the system: <mediaobject> - <imageobject> - <imagedata fileref="images/intro/user_portlet_create.png" format="PNG" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/user_portlet_create.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <emphasis role="bold">Lost password</emphasis> </para> - <para> + <para> Already registered users can request a new password by clicking on the <emphasis role="bold">Lost password</emphasis> link in the navigation of the portlet. After entering your user name you will receive an e-mail with your new login credentials. </para> - <para> + <para> <mediaobject> - <imageobject> - <imagedata fileref="images/intro/user_portlet_lost.png" format="PNG" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/user_portlet_lost.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <emphasis role="bold">View profile</emphasis> </para> - <para> + <para> The default page after login is the view profile page. This page displays a summary of the most important properties of a user. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <emphasis role="bold">Edit personal information</emphasis> </para> - <para>A user has the ability to edit their personal information, change their password and e-mail address at any time by clicking on the + <para>A user has the ability to edit their personal information, change their password and e-mail address at any time by clicking on the <emphasis role="bold">Edit profile</emphasis> link, when logged in. </para> - </listitem> - </itemizedlist> + </listitem> + </itemizedlist> </para> - -</section> - -<section id="Portal_User_Guide-Home_Page-Intro_CMS_portlet"> - <title>CMS Portlet</title> - - <para> + </section> + <section id="Portal_User_Guide-Home_Page-Intro_CMS_portlet"> + <title>CMS Portlet</title> + <para> <mediaobject> - <imageobject> - <imagedata fileref="images/intro/cms_portlet.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/cms_portlet.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> Portal includes a basic Content Management System (CMS) portlet which allows users to navigate the CMS content (static html, images, binary files, etc.). </para> - <para> + <para> Content is displayed through the portal using a path mapper. For example, if you wanted to display a zip file, located in <emphasis>/default/foo/bar.zip</emphasis>, you would type in the URL <emphasis>http://localhost:8080/content/default/foo/bar.zip</emphasis>. - Notice how the path to the content, is prefixed with the <emphasis - role="bold">/content</emphasis> term. + Notice how the path to the content, is prefixed with the <emphasis role="bold">/content</emphasis> term. Although in this example we are describing binary content retrieval, the same can be said for text/html files. Keep in mind, however, that binary files are displayed outside of the portal pages, but text/html are displayed inside the CMSPortlet Window. </para> - <para> + <para> <emphasis role="bold">Serving Logic:</emphasis> - The CMS Portlet now serves content based on the user's locale setting. For example, if a user's locale is + The CMS Portlet now serves content based on the user's locale setting. For example, if a user's locale is set to Spanish in their browser, and they request URL: default/index.html, the CMSPortlet will first try and retrieve the Spanish version of that file. If a Spanish version is not found, it will then try and retrieve the default language version set for the CMSPortlet (set to English, by default). </para> - <note> - <para> + <note> + <para> Administrators should read <xref linkend="Portal_User_Guide-Test-Administration_CMS_Portlet"/> for managing the data in the CMS. </para> - </note> - </section> - </section> - -<section id="Portal_User_Guide-Contents_Pages-News_Page"> - <title>News Page</title> - - <para> + </note> + </section> + </section> + <section id="Portal_User_Guide-Contents_Pages-News_Page"> + <title>News Page</title> + <para> The News Page contains 2 portlets displaying news from common internet feeds. An open internet - connection on the server-side is therefore required for them to operate. <mediaobject> - - <imageobject> - <imagedata fileref="images/intro/newspage.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + connection on the server-side is therefore required for them to operate. </para> - -<section id="Portal_User_Guide-News_Page-News_Portlet"> - <title>News Portlet</title> - <para> + <mediaobject> + <imageobject> + <imagedata fileref="images/intro/newspage.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> + <section id="Portal_User_Guide-News_Page-News_Portlet"> + <title>News Portlet</title> + <para> The News Portlet retrieves an RSS news feed from a URL and displays it as HTML to the user. <mediaobject> - <imageobject> - <imagedata fileref="images/intro/newsportlet.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/newsportlet.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> </para> - <para> + <para> Additionally, a logged-in user is able to modify their preference in RSS feed source by using the - Portlet's Edit Mode by clicking + Portlet's Edit Mode by clicking <mediaobject> - <imageobject> - <imagedata fileref="images/intro/ico_edit.gif" format="GIF"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/ico_edit.gif" format="GIF"/> + </imageobject> + </mediaobject> Once the form is submitted, this property will be saved - in the user's preference, so the user will always see the same news source when logged in. + in the user's preference, so the user will always see the same news source when logged in. <mediaobject> - <imageobject> - <imagedata fileref="images/intro/newsportlet_edit.png" format="PNG"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/newsportlet_edit.png" format="PNG"/> + </imageobject> + </mediaobject> </para> - <note> - <para> + <note> + <para> This portlet is capable of handling most RSS 1.0 and RSS 2.0 feeds. </para> - </note> - -</section> -</section> - -<section id="Portal_User_Guide-Contents_Pages-Weather_Page"> - <title>Weather Page</title> - - <para> + </note> + </section> + </section> + <section id="Portal_User_Guide-Contents_Pages-Weather_Page"> + <title>Weather Page</title> + <para> Within the samples you will find a basic weather portlet that can be deployed in the Enterprise Portal Platform. By copying the web archive into the <literal>deploy</literal> directory of your EPP configuration, it will automatically create a new page with the weather portlet on it. This page contains a portlet that displays the weather forecast for a specific location. </para> - -<section id="Portal_User_Guide-Weather_Page-Weather_Portlet"> - <title>Weather Portlet</title> - - <para> + <section id="Portal_User_Guide-Weather_Page-Weather_Portlet"> + <title>Weather Portlet</title> + <para> The Weather Portlet retrieves an RSS weather feed, based on a key (commonly a US Postal Code), and displays it as HTML to the user. <mediaobject> - <imageobject> - <imagedata fileref="images/intro/weatherportlet.gif" format="GIF"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/weatherportlet.gif" format="GIF"/> + </imageobject> + </mediaobject> </para> - <para> - Additionally, a logged-in user is able to modify their location preference by using the Portlet's <emphasis role="bold">Edit Mode</emphasis> by clicking + <para> + Additionally, a logged-in user is able to modify their location preference by using the Portlet's <emphasis role="bold">Edit Mode</emphasis> by clicking <mediaobject> - <imageobject> - <imagedata fileref="images/intro/ico_edit.gif" format="GIF"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/ico_edit.gif" format="GIF"/> + </imageobject> + </mediaobject> Any valid US Postal Code can be input here. Once the form is submitted, this property will be saved - in the user's preference, so the user will always see the same weather data for their location when logged in. + in the user's preference, so the user will always see the same weather data for their location when logged in. <mediaobject> - <imageobject> - <imagedata fileref="images/intro/weatherportlet_edit.gif" format="GIF" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/weatherportlet_edit.gif" format="GIF" align="center" valign="middle"/> + </imageobject> + </mediaobject> </para> - <para> + <para> If you are not located in the United States you will need to configure the Weather portlet to display the information for your area. <orderedlist> - <listitem> - <para>Go to + <listitem> + <para>Go to <ulink url="http://weather.yahoo.com/">http://weather.yahoo.com/</ulink> </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> Enter your city name in the location field: <mediaobject> - <imageobject> - <imagedata fileref="images/intro/weather_config1.png" format="PNG" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/weather_config1.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> Find your location on the list under the <emphasis role="bold">Search Results</emphasis> and click on it (<emphasis>Marseille, France</emphasis>, in this case): <mediaobject> - <imageobject> - <imagedata fileref="images/intro/weather_config2.gif" format="GIF" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/weather_config2.gif" format="GIF" align="center" valign="middle"/> + </imageobject> + </mediaobject> </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> Copy the location digits from the address bar in your browser (<emphasis>FRXX0059</emphasis> in this case): <mediaobject> - <imageobject> - <imagedata fileref="images/intro/weather_config3.gif" format="GIF" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/weather_config3.gif" format="GIF" align="center" valign="middle"/> + </imageobject> + </mediaobject> </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> Paste these numbers into the weather portlet edit form (<emphasis>FRXX0059</emphasis> in this case): <mediaobject> - <imageobject> - <imagedata fileref="images/intro/weather_config4.png" format="PNG" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/weather_config4.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> Click on <emphasis role="bold">submit</emphasis> <mediaobject> - <imageobject> - <imagedata fileref="images/intro/weather_config5.png" format="PNG" align="center" - valign="middle"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/weather_config5.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> </para> - </listitem> - </orderedlist> + </listitem> + </orderedlist> </para> - - </section> - </section> - -<section id="Portal_User_Guide-JBoss_Portal_Basics-Dashboard"> - <title>Personal Dashboard</title> - - <para> + </section> + </section> + <section id="Portal_User_Guide-JBoss_Portal_Basics-Dashboard"> + <title>Personal Dashboard</title> + <para> Once logged in, all users/administrators of the portal can access a personal dashboard by clicking the <emphasis role="bold">Dashboard</emphasis> link at the top-right of the portal page. Note how the links changed. - <mediaobject> - <imageobject> - <imagedata fileref="images/intro/dashboard.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + The personal dashboard allows users to customize their portal pages however they like. All changes will be persisted so the next time the user logs in to their dashboard, the user will see the previous changes they made. While navigating any of the dashboard pages, a user will be able to drag and drop portlet windows to any location, if the administrator allows this functionality. Changes made in this fashion will also be persisted. </para> - <para> + <mediaobject> + <imageobject> + <imagedata fileref="images/intro/dashboard.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> + <para> It is also possible to copy the content of a shared page to your dashboard so you can customize it to your liking. Just click the <emphasis role="bold">Copy to my dashboard</emphasis> link at the top right of the page. This will clone the page and add it to your personal dashboard as a page with the same name. - <mediaobject> - <imageobject> - <imagedata fileref="images/intro/dashboard_copy_to.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + </para> - - -<section id="Portal_User_Guide-Dashboard-Dashboard_Configure"> - <title>Configuring your personal dashboard</title> - - <para> - You can configure your dashboard by using the top-right menu item labeled <emphasis role="bold">'Configure dashboard'</emphasis>: + <mediaobject> + <imageobject> + <imagedata fileref="images/intro/dashboard_copy_to.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> + <section id="Portal_User_Guide-Dashboard-Dashboard_Configure"> + <title>Configuring your personal dashboard</title> + <para> + You can configure your dashboard by using the top-right menu item labeled <emphasis role="bold">'Configure dashboard'</emphasis>: <mediaobject> - <imageobject> - <imagedata fileref="images/intro/dashboard_configure.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> - </para> -</section> - -<section id="Portal_User_Guide-Dashboard_Configure-Dashboard_Operations"> - <title>Dashboard-wide operations</title> - - <para> + <imageobject> + <imagedata fileref="images/intro/dashboard_configure.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> + </para> + </section> + <section id="Portal_User_Guide-Dashboard_Configure-Dashboard_Operations"> + <title>Dashboard-wide operations</title> + <para> You can select a theme and layout for your dashboard by selecting from the available ones and then clicking on select in the <emphasis role="bold">Theme and Layout</emphasis> form. </para> - <para> + <para> You can also create new pages that will be added to your dashboard by simply entering the name of the new page in the <emphasis role="bold">Create New Page</emphasis> form at the top left of the screen. <note> - <itemizedlist> - <listitem> - <para> + <itemizedlist> + <listitem> + <para> Page names must be unique. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> Page names cannot be blank. </para> - </listitem> - </itemizedlist> - - </note> + </listitem> + </itemizedlist> + </note> Upon creating a new page, the screen will refresh and allow a user to customize the new page. </para> - <para> + <para> You may delete dashboard pages at any time, by first selecting the page you want to delete using the pop-up menu at the top of the screen and then clicking the <emphasis role="bold">Delete this page</emphasis> button at the bottom of the screen. Users are not able to delete the default dashboard page. <mediaobject> - <imageobject> - <imagedata fileref="images/intro/dashboard_deletepage.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/dashboard_deletepage.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> <warning> - <para> + <para> Deleted pages are NOT recoverable. This change is permanent! </para> - </warning> + </warning> </para> -</section> - - + </section> <section id="Portal_User_Guide-Dashboard_Configure-Dashboard_Assignportlets"> - <title>Managing Portlets on a page</title> - - <para> + <title>Managing Portlets on a page</title> + <para> You can add, remove and reorder portlets on a dashboard page to suit your specific requirements. Select the page you want to modify by using the page pop-up selector and then the portlet management form. We will not explain how to use it here as it is similar to the page layout functionality of the Admin portal, which we will look at in <xref linkend="Portal_User_Guide-Managing_Portal_Objects-Page_configuration"/> <mediaobject> - <imageobject> - <imagedata fileref="images/intro/dashboard_assignportlets.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + <imageobject> + <imagedata fileref="images/intro/dashboard_assignportlets.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> </para> - </section> -</section> - -<section id="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"> - <title>Admin Portal</title> - - - <para> + </section> + </section> + <section id="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"> + <title>Admin Portal</title> + <para> - The Admin Portal's purpose is to allow an administrator to manage all aspects of the portal. You <emphasis role="bold">must be</emphasis> logged in as an administrator, or have proper privileges + The Admin Portal's purpose is to allow an administrator to manage all aspects of the portal. You <emphasis role="bold">must be</emphasis> logged in as an administrator, or have proper privileges to see this portal. Follow the links for in-depth reviews of these functions: <itemizedlist> - <listitem> - <para> + <listitem> + <para> Users/Roles (See: <xref linkend="Portal_User_Guide-User_Role-Managing_Users"/> - <xref linkend="Portal_User_Guide-User_Role-Managing_Roles"/></para></listitem> - <listitem><para>Content Management System (See: <xref linkend="Portal_User_Guide-Test-Administration_CMS_Portlet"/> </para></listitem> - <listitem><para>Portal Objects (themes, layouts, portal instances, pages, windows, security, and deployed - portlets) (See: <xref linkend="Portal_User_Guide-Dynamicity"/> </para></listitem> - <listitem><para>WSRP (See the + <xref linkend="Portal_User_Guide-User_Role-Managing_Roles"/></para> + </listitem> + <listitem> + <para>Content Management System (See: <xref linkend="Portal_User_Guide-Test-Administration_CMS_Portlet"/> </para> + </listitem> + <listitem> + <para>Portal Objects (themes, layouts, portal instances, pages, windows, security, and deployed + portlets) (See: <xref linkend="Portal_User_Guide-Dynamicity"/> </para> + </listitem> + <listitem> + <para>WSRP (See the <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...">WSRP chapter</ulink> in the Reference Guide for more information)</para> - </listitem> - </itemizedlist> - <mediaobject> - <imageobject> - <imagedata fileref="images/intro/adminportal.png" format="PNG" scalefit="1"/> - </imageobject> - </mediaobject> + </listitem> + </itemizedlist> + </para> - - - - -</section> - - - - + <mediaobject> + <imageobject> + <imagedata fileref="images/intro/adminportal.png" format="PNG" scalefit="1"/> + </imageobject> + </mediaobject> + </section> </chapter> - Modified: docs/enterprise/trunk/User_Guide/en-US/Preface.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/Preface.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/User_Guide/en-US/Preface.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -5,9 +5,5 @@ <preface id="Portal_User_Guide-Preface"> <title>Preface</title> <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Middleware_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> + <xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </preface> Modified: docs/enterprise/trunk/User_Guide/en-US/User_Guide.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/User_Guide.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/User_Guide/en-US/User_Guide.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,15 +1,14 @@ -<?xml version='1.0'?> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "User_Guide.ent"> +%BOOK_ENTITIES; ]> - <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="JBoss_Portal_Basics.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Dynamicity.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Administration_CMS_Portlet.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="User_Role.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JBoss_Portal_Basics.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Dynamicity.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Administration_CMS_Portlet.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="User_Role.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> </book> - Modified: docs/enterprise/trunk/User_Guide/en-US/User_Role.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/User_Role.xml 2012-01-09 10:06:11 UTC (rev 14026) +++ docs/enterprise/trunk/User_Guide/en-US/User_Role.xml 2012-01-12 01:47:10 UTC (rev 14027) @@ -1,305 +1,261 @@ -<?xml version='1.0'?> +<?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="Portal_User_Guide-User_Role"> - <title>Administration - Users and Roles</title> - <para> - - This chapter covers the administrator functions made available by the User management portlet. For end-user operation, see: - <xref linkend="Portal_User_Guide-Home_Page-Intro_user_portlet"/>. Administrative functions are available once you are logged in with the proper - credentials (admin/admin), then going to the <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"/> and then the Members Page tab. You can change between - user and role management by clicking on the corresponding links in the top of the portlet. - </para> - - - - <section id="Portal_User_Guide-User_Role-Managing_Users"> - <title>Managing Users</title> - - <para> - This section covers the user management of the <classname>IdentityUserManagementPortlet</classname> which is displayed by default. - For role management please see <xref linkend="Portal_User_Guide-User_Role-Managing_Roles"/>. - - <mediaobject> - <imageobject> - <imagedata fileref="images/role/memberspage.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - The Members page in the <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"/>. - </para> - </caption> - </mediaobject> - </para> - - <section id="Portal_User_Guide-Managing_Users-Actions"> - <title>Actions</title> - - <para> - The first page of the user management portlet displays some user related actions (e.g.. Search users, Create new user account) and some additional information (e.g. Registered users and Subscription mode). The registered users represent the count of all registered users and the subscription mode describes the required tasks for registering a user (i.e. first e-mail validation and then approval by the administrator). - The <emphasis>Subscription mode</emphasis> symbolizes the mode used in the User portlet. The <emphasis>Admin subscription mode</emphasis> represents - the mode used in the User management portlet. - - <mediaobject> - <imageobject> - <imagedata fileref="images/role/user_management.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - The User management portlet. - </para> - </caption> - </mediaobject> - - </para> -<section id="Portal_User_Guide-Actions-Searching_for_Users"> - <title>Searching for Users</title> - <para> - To search for a user click on the link <emphasis role="bold">Search users</emphasis> and then type a partial username in the form text field. This will search for usernames that match that - criteria. - - <mediaobject> - <imageobject> - <imagedata fileref="images/role/user_su.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - The search users page. - </para> - </caption> - </mediaobject> - </para> - - </section> - -<section id="Portal_User_Guide-Actions-Updating_User_Profiles"> - <title>Updating User Profiles</title> - <para> - Clicking on the - <emphasis role="bold">Edit user</emphasis> - link on the search page will allow you to edit a user's profile data, and even reset his password. - - <mediaobject> - <imageobject> - <imagedata fileref="images/role/edit_profile.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - Editing a users profile. - </para> - </caption> - </mediaobject> - </para> -</section> - - -<section id="Portal_User_Guide-Actions-Updating_User_Roles"> - <title>Updating User Roles</title> - - - <para> - Clicking on the - <emphasis role="bold">Roles</emphasis> - link in the search page allows you to modify the roles a specific user belongs to. - - <mediaobject> - <imageobject> - <imagedata fileref="images/role/assign_roles.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - Assign roles to a user. - </para> - </caption> - </mediaobject> - </para> - -</section> - -<section id="Portal_User_Guide-Actions-Creating_Users"> - <title>Creating Users</title> - <para> - Clicking on the - <emphasis role="bold">Create User Account</emphasis> - link on the main UserPortlet view, allows administrators to instantly create new users. - - <mediaobject> - <imageobject> - <imagedata fileref="images/role/create_user.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - Creating a user in the User management portlet. - </para> - </caption> - </mediaobject> - - </para> - - </section> - -<section id="Portal_User_Guide-Actions-Pending_Users"> - <title>Pending Users</title> - - - <para> - Click on the <emphasis role="bold">Show pending registrations</emphasis> link to show all registrations with validated e-mail addresses. - You can approve or reject each user by clicking on the corresponding action or click on <emphasis>select all</emphasis> - to approve or reject all selected users. - </para> - - <para> - - <mediaobject> - <imageobject> - <imagedata fileref="images/role/user_pending.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - Approve or reject pending registrations. - </para> - </caption> - </mediaobject> - - </para> - <note> - <para> - By default the subscription modes are set to <emphasis>automatic</emphasis> and users will be created automatically. Furthermore the - link to <emphasis role="bold">Show pending registrations</emphasis> will only be displayed if a user needs to be approved by the administrator. - </para> - </note> -</section> -</section> -</section> - - - -<section id="Portal_User_Guide-User_Role-Managing_Roles"> - <title>Managing Roles</title> - - <para> - The User management portlet is also responsible to create and edit roles and it is accessible once logged in - as described in previously - when clicking on the <emphasis role="bold">role management</emphasis> - link in the User management portlet. - </para> - -<section id="Portal_User_Guide-Managing_Roles-Introduction"> - <title>Introduction</title> - - <para> - A role will be used to grant different permission levels to different portlets, pages, or portal instances. A user can have several roles. - </para> - <para> - <mediaobject> - <imageobject> - <imagedata fileref="images/role/role_management.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - Role management. - </para> - </caption> - </mediaobject> - </para> -</section> - -<section id="Portal_User_Guide-Managing_Roles-Actions"> - <title>Actions</title> - - <para> - The User management portlet also provides several actions related to role management, which are described in the following sections. - - </para> - - -<section id="Portal_User_Guide-Actions-Creating_Roles"> - <title>Creating Roles</title> - - <para> - Creating new roles, is accomplished by first clicking on the - <emphasis role="bold">Create new role</emphasis> - link in the portlet. - <mediaobject> - <imageobject> - <imagedata fileref="images/role/create_role.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - Create a new role. - </para> - </caption> - </mediaobject> - - To create a new role, you need to define a short name that will be used for - reference, and a display name for displaying to the user, for example - <literal>admin</literal> - would be a good name for the display name - <literal>Administrators</literal> - , changing the display name will not affect the - security rules. - </para> -</section> - - -<section id="Portal_User_Guide-Actions-Edit_Role"> - <title>Edit a role</title> - - <para> - Editing roles is accomplished by clicking on <emphasis role="bold">Edit role</emphasis> in the row of the role you want to edit. - <mediaobject> - <imageobject> - <imagedata fileref="images/role/edit_role.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - Edit an existing role. - </para> - </caption> - </mediaobject> - While editing a role, you just need to pick an existing role then change the display name. + <title>Administration - Users and Roles</title> + <para> + + This chapter covers the administrator functions made available by the User management portlet. For end-user operation, see: + <xref linkend="Portal_User_Guide-Home_Page-Intro_user_portlet"/>. Administrative functions are available once you are logged in with the proper + credentials (admin/admin), then going to the <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"/> and then the Members Page tab. You can change between + user and role management by clicking on the corresponding links in the top of the portlet. + </para> + <section id="Portal_User_Guide-User_Role-Managing_Users"> + <title>Managing Users</title> + <para> + This section covers the user management of the <classname>IdentityUserManagementPortlet</classname> which is displayed by default. + For role management please see <xref linkend="Portal_User_Guide-User_Role-Managing_Roles"/>. + + + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/role/memberspage.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + The Members page in the <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"/>. + </para> + </textobject> + </mediaobject> + <section id="Portal_User_Guide-Managing_Users-Actions"> + <title>Actions</title> + <para> + The first page of the user management portlet displays some user related actions (e.g.. Search users, Create new user account) and some additional information (e.g. Registered users and Subscription mode). The registered users represent the count of all registered users and the subscription mode describes the required tasks for registering a user (i.e. first e-mail validation and then approval by the administrator). + The <emphasis>Subscription mode</emphasis> symbolizes the mode used in the User portlet. The <emphasis>Admin subscription mode</emphasis> represents + the mode used in the User management portlet. + + <mediaobject> + <imageobject> + <imagedata fileref="images/role/user_management.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + The User management portlet. + </para> + </textobject> + </mediaobject> + + </para> + <section id="Portal_User_Guide-Actions-Searching_for_Users"> + <title>Searching for Users</title> + <para> + To search for a user click on the link <emphasis role="bold">Search users</emphasis> and then type a partial username in the form text field. This will search for usernames that match that + criteria. + + + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/role/user_su.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + The search users page. + </para> + </textobject> + </mediaobject> + </section> + <section id="Portal_User_Guide-Actions-Updating_User_Profiles"> + <title>Updating User Profiles</title> + <para> + Clicking on the + <emphasis role="bold">Edit user</emphasis> + link on the search page will allow you to edit a user's profile data, and even reset his password. + + + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/role/edit_profile.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + Editing a users profile. + </para> + </textobject> + </mediaobject> + </section> + <section id="Portal_User_Guide-Actions-Updating_User_Roles"> + <title>Updating User Roles</title> + <para> + Clicking on the + <emphasis role="bold">Roles</emphasis> + link in the search page allows you to modify the roles a specific user belongs to. + + + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/role/assign_roles.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + Assign roles to a user. + </para> + </textobject> + </mediaobject> + </section> + <section id="Portal_User_Guide-Actions-Creating_Users"> + <title>Creating Users</title> + <para> + Clicking on the + <emphasis role="bold">Create User Account</emphasis> + link on the main UserPortlet view, allows administrators to instantly create new users. + + + + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/role/create_user.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + Creating a user in the User management portlet. + </para> + </textobject> + </mediaobject> + </section> + <section id="Portal_User_Guide-Actions-Pending_Users"> + <title>Pending Users</title> + <para> + Click on the <emphasis role="bold">Show pending registrations</emphasis> link to show all registrations with validated e-mail addresses. + You can approve or reject each user by clicking on the corresponding action or click on <emphasis>select all</emphasis> + to approve or reject all selected users. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/role/user_pending.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + Approve or reject pending registrations. + </para> + </textobject> + </mediaobject> + <note> + <para> + By default the subscription modes are set to <emphasis>automatic</emphasis> and users will be created automatically. Furthermore the + link to <emphasis role="bold">Show pending registrations</emphasis> will only be displayed if a user needs to be approved by the administrator. + </para> + </note> + </section> + </section> + </section> + <section id="Portal_User_Guide-User_Role-Managing_Roles"> + <title>Managing Roles</title> + <para> + The User management portlet is also responsible to create and edit roles and it is accessible once logged in - as described in previously - when clicking on the <emphasis role="bold">role management</emphasis> + link in the User management portlet. + </para> + <section id="Portal_User_Guide-Managing_Roles-Introduction"> + <title>Introduction</title> + <para> + A role will be used to grant different permission levels to different portlets, pages, or portal instances. A user can have several roles. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/role/role_management.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + Role management. + </para> + </textobject> + </mediaobject> + </section> + <section id="Portal_User_Guide-Managing_Roles-Actions"> + <title>Actions</title> + <para> + The User management portlet also provides several actions related to role management, which are described in the following sections. + + </para> + <section id="Portal_User_Guide-Actions-Creating_Roles"> + <title>Creating Roles</title> + <para> + Creating new roles, is accomplished by first clicking on the + <emphasis role="bold">Create new role</emphasis> + link in the portlet. + + + To create a new role, you need to define a short name that will be used for + reference, and a display name for displaying to the user, for example + <literal>admin</literal> + would be a good name for the display name + <literal>Administrators</literal> + , changing the display name will not affect the + security rules. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/role/create_role.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + Create a new role. + </para> + </textobject> + </mediaobject> + </section> + <section id="Portal_User_Guide-Actions-Edit_Role"> + <title>Edit a role</title> + <para> + Editing roles is accomplished by clicking on <emphasis role="bold">Edit role</emphasis> in the row of the role you want to edit. + + While editing a role, you just need to pick an existing role then change the display name. </para> -</section> - - -<section id="Portal_User_Guide-Actions-Editing_Role_Members"> - <title>Editing Role Members</title> - - <para> - Editing role members is accomplished by first clicking the - <emphasis role="bold">Members</emphasis> - link at the role management page for the role you would like to modify. - - <mediaobject> - <imageobject> - <imagedata fileref="images/role/role_members.png" format="PNG" scalefit="1"/> - </imageobject> - <caption> - <para> - Show the members of an existing role. - </para> - </caption> - </mediaobject> - - Allows for an administrator to search and modify the members' assigned roles. - </para> - -</section> - -<section id="Portal_User_Guide-Actions-Deleting_Roles"> - <title>Deleting Roles</title> - - <para> - Deleting roles is accomplished by clicking the - <emphasis role="bold">Delete</emphasis> - link for the role you would like to remove. - </para> - - - - -</section> -</section> -</section> - + <mediaobject> + <imageobject> + <imagedata fileref="images/role/edit_role.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + Edit an existing role. + </para> + </textobject> + </mediaobject> + </section> + <section id="Portal_User_Guide-Actions-Editing_Role_Members"> + <title>Editing Role Members</title> + <para> + Editing role members is accomplished by first clicking the + <emphasis role="bold">Members</emphasis> + link at the role management page for the role you would like to modify. + + + + Allows for an administrator to search and modify the members' assigned roles. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/role/role_members.png" format="PNG" scalefit="1"/> + </imageobject> + <textobject> + <para> + Show the members of an existing role. + </para> + </textobject> + </mediaobject> + </section> + <section id="Portal_User_Guide-Actions-Deleting_Roles"> + <title>Deleting Roles</title> + <para> + Deleting roles is accomplished by clicking the + <emphasis role="bold">Delete</emphasis> + link for the role you would like to remove. + </para> + </section> + </section> + </section> </chapter> -

12 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

portal-commits January 2012