[portal-commits] JBoss Portal SVN: r7623 - in docs/trunk/quickstartuser/en: images and 1 other directories.

Author: cdelashmutt Date: 2007-06-28 20:10:09 -0400 (Thu, 28 Jun 2007) New Revision: 7623 Modified: docs/trunk/quickstartuser/en/images/image001.png docs/trunk/quickstartuser/en/images/image002.png docs/trunk/quickstartuser/en/images/image006.png docs/trunk/quickstartuser/en/images/image011.png docs/trunk/quickstartuser/en/images/image012.png docs/trunk/quickstartuser/en/images/image013.png docs/trunk/quickstartuser/en/images/image014.png docs/trunk/quickstartuser/en/images/image015.png docs/trunk/quickstartuser/en/images/image021.png docs/trunk/quickstartuser/en/images/image022.png docs/trunk/quickstartuser/en/images/image023.png docs/trunk/quickstartuser/en/images/image024.png docs/trunk/quickstartuser/en/images/image075.png docs/trunk/quickstartuser/en/images/image076.png docs/trunk/quickstartuser/en/images/image077.png docs/trunk/quickstartuser/en/images/image078.png docs/trunk/quickstartuser/en/images/image079.png docs/trunk/quickstartuser/en/images/image080.png docs/trunk/quickstartuser/en/images/image081.png docs/trunk/quickstartuser/en/images/image082.png docs/trunk/quickstartuser/en/images/image084.png docs/trunk/quickstartuser/en/images/image085.png docs/trunk/quickstartuser/en/images/image086.png docs/trunk/quickstartuser/en/images/image087.png docs/trunk/quickstartuser/en/images/image088.png docs/trunk/quickstartuser/en/images/image089.png docs/trunk/quickstartuser/en/images/image090.png docs/trunk/quickstartuser/en/images/image091.png docs/trunk/quickstartuser/en/images/image092.png docs/trunk/quickstartuser/en/images/image093.png docs/trunk/quickstartuser/en/images/image094.png docs/trunk/quickstartuser/en/images/image096.png docs/trunk/quickstartuser/en/images/image098.png docs/trunk/quickstartuser/en/images/image099.png docs/trunk/quickstartuser/en/images/image100.png docs/trunk/quickstartuser/en/images/image101.png docs/trunk/quickstartuser/en/images/image103.png docs/trunk/quickstartuser/en/images/image108.png docs/trunk/quickstartuser/en/master.xml docs/trunk/quickstartuser/en/modules/deployportlet.xml docs/trunk/quickstartuser/en/modules/fin.xml docs/trunk/quickstartuser/en/modules/forward.xml docs/trunk/quickstartuser/en/modules/installation.xml docs/trunk/quickstartuser/en/modules/interaction.xml docs/trunk/quickstartuser/en/modules/overview.xml docs/trunk/quickstartuser/en/modules/portalterminology.xml Log: Revamped quick start guide for 2.6 Modified: docs/trunk/quickstartuser/en/images/image001.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image002.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image006.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image011.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image012.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image013.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image014.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image015.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image021.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image022.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image023.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image024.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image075.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image076.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image077.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image078.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image079.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image080.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image081.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image082.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image084.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image085.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image086.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image087.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image088.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image089.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image090.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image091.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image092.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image093.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image094.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image096.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image098.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image099.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image100.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image101.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image103.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/images/image108.png =================================================================== (Binary files differ) Modified: docs/trunk/quickstartuser/en/master.xml =================================================================== --- docs/trunk/quickstartuser/en/master.xml 2007-06-29 00:07:57 UTC (rev 7622) +++ docs/trunk/quickstartuser/en/master.xml 2007-06-29 00:10:09 UTC (rev 7623) @@ -1,59 +1,77 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" - "../../docbook-support/support/docbook-dtd/docbookx.dtd" [ - <!ENTITY overview SYSTEM "modules/overview.xml"> - <!ENTITY forward SYSTEM "modules/forward.xml"> - <!ENTITY installation SYSTEM "modules/installation.xml"> - <!ENTITY portalterminology SYSTEM "modules/portalterminology.xml"> - <!ENTITY interaction SYSTEM "modules/interaction.xml"> - <!ENTITY deployportlet SYSTEM "modules/deployportlet.xml"> - <!ENTITY fin SYSTEM "modules/fin.xml"> - ]> +"../../docbook-support/support/docbook-dtd/docbookx.dtd" [ +<!ENTITY overview SYSTEM "modules/overview.xml"> +<!ENTITY forward SYSTEM "modules/forward.xml"> +<!ENTITY installation SYSTEM "modules/installation.xml"> +<!ENTITY portalterminology SYSTEM "modules/portalterminology.xml"> +<!ENTITY interaction SYSTEM "modules/interaction.xml"> +<!ENTITY deployportlet SYSTEM "modules/deployportlet.xml"> +<!ENTITY fin SYSTEM "modules/fin.xml"> +]> <book lang="en"> - <bookinfo> - <title>JBoss Portal 2.6</title> + <bookinfo> + <title>JBoss Portal 2.6</title> - <subtitle>Quickstart User Guide</subtitle> + <subtitle>Quickstart User Guide</subtitle> - <releaseinfo>Release 2.6 "Ninja"</releaseinfo> - <releaseinfo>June 2007</releaseinfo> + <releaseinfo>Release 2.6 "Ninja"</releaseinfo> - <author> - <firstname>Kevin</firstname> + <releaseinfo>June 2007</releaseinfo> - <surname>Barfield</surname> + <author> + <firstname>Kevin</firstname> - <email&gt;kevin.barfield(a)jboss.com&lt;/email&gt; - </author> - </bookinfo> + <surname>Barfield</surname> - <toc></toc> + <email&gt;kbarfiel(a)redhat.com&lt;/email&gt; + </author> - <!-- portal overview - marketing stuff --> + <author> + <firstname>Chris</firstname> - &overview; + <surname>DeLashmutt</surname> - <!-- forward --> + <email&gt;cdelashm(a)redhat.com&lt;/email&gt; + </author> - &forward; + <author> + <firstname>Xi</firstname> - <!-- installation --> + <surname>Huang</surname> - &installation; + <email&gt;xhuang(a)redhat.com&lt;/email&gt; + </author> - <!-- Portal terminology --> + </bookinfo> - &portalterminology; + <toc></toc> - <!-- Interacting with the portal --> + <!-- portal overview - marketing stuff --> - &interaction; + &overview; - <!-- portletswap deployment --> + <!-- forward --> - &deployportlet; + &forward; - <!-- end --> + <!-- installation --> - &fin; + &installation; + + <!-- Portal terminology --> + + &portalterminology; + + <!-- Interacting with the portal --> + + &interaction; + + <!-- portletswap deployment --> + + &deployportlet; + + <!-- end --> + + &fin; </book> Modified: docs/trunk/quickstartuser/en/modules/deployportlet.xml =================================================================== --- docs/trunk/quickstartuser/en/modules/deployportlet.xml 2007-06-29 00:07:57 UTC (rev 7622) +++ docs/trunk/quickstartuser/en/modules/deployportlet.xml 2007-06-29 00:10:09 UTC (rev 7623) @@ -1,152 +1,135 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="deployportlet"> - <chapterinfo> - <author> - <firstname>Kevin</firstname> + <chapterinfo> + <author> + <firstname>Kevin</firstname> - <surname>Barfield</surname> + <surname>Barfield</surname> - <email&gt;kevin.barfield(a)jboss.com&lt;/email&gt; - </author> - </chapterinfo> + <email&gt;kbarfiel(a)redhat.com&lt;/email&gt; + </author> - <title>Deploying Portlets</title> + <author> + <firstname>Chris</firstname> - <para>Let's add a portlet from Portletswap to the JBoss Portal we have - running. Open a browser to the following URL: - <ulink - url="http://www.portletswap.com">http://www.portletswap.com - </ulink> - (Figure - 47). - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image099.jpg" format="JPG" - valign="middle"/> - </imageobject> + <surname>DeLashmutt</surname> - <caption> - <para>Figure 47. Portletswap website</para> - </caption> - </mediaobject> - Click on the "Browse Portlets" link to see the categories - of portlets available (Figure 48). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image101.jpg" format="JPG" - valign="middle"/> - </imageobject> + <email&gt;cdelashm(a)redhat.com&lt;/email&gt; + </author> - <caption> - <para>Figure 48. Portlet categories on - portletswap. - </para> - </caption> - </mediaobject> - Click on the Miscellaneous Portlets browse link to see a - list of portlets (Figure 49). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image102.jpg" format="JPG" - valign="middle"/> - </imageobject> + <author> + <firstname>Xi</firstname> - <caption> - <para>Figure 49. List of portlets on - portletswap. - </para> - </caption> - </mediaobject> - Click on the download link next to the Flash MoviePortlet. - The download dialog will appear (Figure 50). - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image064.jpg" format="JPG" - valign="middle"/> - </imageobject> + <surname>Huang</surname> - <caption> - <para>Figure 50. Download dialog.</para> - </caption> - </mediaobject> - This zip file contains both the binary and the source for - the portlet. Open the zip and extract the flash.war file. Place this file in - the $JBOSS_HOME\server\default\deploy directory. The console for the - JBoss Portal will show the portlet being deployed (Figure 51). + <email&gt;xhuang(a)redhat.com&lt;/email&gt; + </author> + </chapterinfo> - <emphasis>11:23:17,640 INFO [TomcatDeployer] deploy, ctxPath=/flash, warUrl=.../tmp/deploy/tmp64975flash-exp.war/</emphasis> + <title>Deploying Portlets</title> - To see the deployed portlet, we need to add it to our - Starter portal page. First, we need to create an instance of the portlet. Go - to the Management Portlet and click "Portlet Definitions" tab (Figure 52). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image107.jpg" format="JPG" - valign="middle"/> - </imageobject> + <para>Let's add a portlet from Portletswap to the JBoss Portal we have + running. Open a browser to the following URL: <ulink + url="http://www.portletswap.com">http://www.portletswap.com </ulink> (Figure + 39). <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image099.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 52. Admin portal page.</para> - </caption> - </mediaobject> - </para> + <caption><para>Figure 39. Portletswap website</para></caption> + </mediaobject>Click on the "Browse Portlets" link to see the categories of + portlets available (Figure 40). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image101.png" format="PNG" + valign="middle" /> + </imageobject> - <para>A list of all portlets will be displayed. - Click on the FlashPortlet link. A dialog to create an instance will appear - (Figure 53). - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image103.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 40. Portlet categories on portletswap. + </para></caption> + </mediaobject>Click on the Miscellaneous Portlets browse link to see a + list of portlets (Figure 41).<mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image102.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 53. Portlets admininstration.</para> - </caption> - </mediaobject> - Type in "Flash Portlet" as the instance name and click on - the "Create Instance" button. The "Portlet Instances" tab page will show an instance list including "Flash Portlet" that we created. - (Figure 54). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image104.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 41. List of portlets on portletswap. + </para></caption> + </mediaobject>Click on the "Zip" link below the description for the Flash + Portlet. The download dialog will appear (Figure 42). <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image064.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 54. Portlet instances - admininstration. - </para> - </caption> - </mediaobject> - Now you may add it to the Starter portal page. Click on the "Portal Objects" tab and navigate to the "Page layout" page of "Starter" - portal page. Select "Flash Portlet" from the portlet list, and add it to - the "Starter" portal page with a name of "flash" (Figure 55). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image105.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 42. Download dialog.</para></caption> + </mediaobject>This ZIP file contains both the binary and the source for + the portlet. Open the zip and extract the flash.war file. Place this file in + the $JBOSS_HOME/server/default/deploy directory. The console for the JBoss + Portal will show the portlet being deployed (Figure 43). <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image109.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 55. Starter portal page with "flash" portlet - added. - </para> - </caption> - </mediaobject> - Click on the Starter portal page, and the "flash" portlet is - displayed (Figure 56). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image106.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 43. Flash Portlet deployed.</para></caption> + </mediaobject>To see the deployed portlet, we need to add it to our + Starter portal page. First, we need to create an instance of the portlet. Go + to the Management Portlet and click "Portlet Definitions" tab (Figure + 44).<mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image107.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 56. Starter portal page with "flash" - portlet. - </para> - </caption> - </mediaobject> - </para> + <caption><para>Figure 44. Admin portal page.</para></caption> + </mediaobject></para> + + <para>A list of all portlets will be displayed. Click on the + local.flashportlet.FlashPortlet link. Once the portal page refreshes, scroll + to the bottom of the page to see a dialog to create a new instance of the + Flash Portlet (Figure 45). <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image103.png" format="PNG" + valign="middle" /> + </imageobject> + + <caption><para>Figure 45. Portlets admininstration.</para></caption> + </mediaobject>Type in "Flash Portlet" as the instance name in the textbox + at the bottom of the page, and click on the "Create Instance" button. The + "Portlet Instances" tab page will be displayed automatically, with the new + "Flash Portlet" portlet instance that we created selected. (Figure 46). + <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image104.png" format="PNG" + valign="middle" /> + </imageobject> + + <caption><para>Figure 46. Portlet instances admininstration. + </para></caption> + </mediaobject>Now you can add this portlet instance to the Starter portal + page. Click on the "Portal Objects" tab and navigate to the "Page layout" + page of "Starter" portal page as we did in the last section. Select "Flash + Portlet" from the portlet list, click the "Select" button, and add it to + center of the "Starter" portal page with a name of "flash" (Figure + 47).<mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image105.png" format="PNG" + valign="middle" /> + </imageobject> + + <caption><para>Figure 47. Starter portal page with "flash" portlet + added. </para></caption> + </mediaobject>Click on the "Portal" link in the upper right of the page. + Click on the Starter portal page, and the "flash" portlet is displayed + (Figure 48). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image106.png" format="PNG" + valign="middle" /> + </imageobject> + + <caption><para>Figure 48. Starter portal page with "flash" portlet. + </para></caption> + </mediaobject></para> </chapter> \ No newline at end of file Modified: docs/trunk/quickstartuser/en/modules/fin.xml =================================================================== --- docs/trunk/quickstartuser/en/modules/fin.xml 2007-06-29 00:07:57 UTC (rev 7622) +++ docs/trunk/quickstartuser/en/modules/fin.xml 2007-06-29 00:10:09 UTC (rev 7623) @@ -6,8 +6,24 @@ <surname>Barfield</surname> - <email&gt;kevin.barfield(a)jboss.com&lt;/email&gt; + <email&gt;kbarfiel(a)redhat.com&lt;/email&gt; </author> + + <author> + <firstname>Chris</firstname> + + <surname>DeLashmutt</surname> + + <email&gt;cdelashm(a)redhat.com&lt;/email&gt; + </author> + + <author> + <firstname>Xi</firstname> + + <surname>Huang</surname> + + <email&gt;xhuang(a)redhat.com&lt;/email&gt; + </author> </chapterinfo> <title>Tutorial End</title> @@ -37,10 +53,10 @@ <listitem> Added a new portlet to the JBoss Portal </listitem> - </itemizedlist> Next steps: Next, take a look at the user guide for JBoss + </itemizedlist>Next steps: Next, take a look at the user guide for JBoss Portal. This will give you more information about using JBoss Portal. There is also a reference guide for developers using JBoss Portal. Both guides are accessible from our <ulink url="http://labs.jboss.com/portal/jbossportal/docs">Document... Page</ulink></para> -</chapter> \ No newline at end of file +</chapter> Modified: docs/trunk/quickstartuser/en/modules/forward.xml =================================================================== --- docs/trunk/quickstartuser/en/modules/forward.xml 2007-06-29 00:07:57 UTC (rev 7622) +++ docs/trunk/quickstartuser/en/modules/forward.xml 2007-06-29 00:10:09 UTC (rev 7623) @@ -6,8 +6,24 @@ <surname>Barfield</surname> - <email&gt;kevin.barfield(a)jboss.com&lt;/email&gt; + <email&gt;kbarfiel(a)redhat.com&lt;/email&gt; </author> + + <author> + <firstname>Chris</firstname> + + <surname>DeLashmutt</surname> + + <email&gt;cdelashm(a)redhat.com&lt;/email&gt; + </author> + + <author> + <firstname>Xi</firstname> + + <surname>Huang</surname> + + <email&gt;xhuang(a)redhat.com&lt;/email&gt; + </author> </chapterinfo> <title>Tutorial Forward</title> @@ -55,11 +71,11 @@ </listitem> <listitem> - This guide was created with JBoss Portal 2.6. This guide is expected to be forward compatible with future versions of Portal (although the screenshots may vary slightly). + This guide was created with JBoss Portal 2.6. This guide is expected to be forward compatible with future versions of Portal (although the screenshots may vary slightly). </listitem> <listitem> - JBoss Portal is platform independent, but this guide was developed using a windows platform. This guide should work equally well for Unix/Linux installations because JBoss Portal is 100% Pure Java. Obviously, you may need use the run_init_XXXX.sh instead of run.bat and use forward slashes instead of backslashes, etc. + JBoss Portal is platform independent, but this guide was developed using a Linux-based platform. This guide should work equally well for Unix/Linux/Windows installations because JBoss Portal is 100% Pure Java. Obviously, you may need use the run.bat instead of run.sh and use forward slashes instead of backslashes, etc. </listitem> </itemizedlist></para> </chapter> \ No newline at end of file Modified: docs/trunk/quickstartuser/en/modules/installation.xml =================================================================== --- docs/trunk/quickstartuser/en/modules/installation.xml 2007-06-29 00:07:57 UTC (rev 7622) +++ docs/trunk/quickstartuser/en/modules/installation.xml 2007-06-29 00:10:09 UTC (rev 7623) @@ -6,8 +6,24 @@ <surname>Barfield</surname> - <email&gt;kevin.barfield(a)jboss.com&lt;/email&gt; + <email&gt;kbarfiel(a)redhat.com&lt;/email&gt; </author> + + <author> + <firstname>Chris</firstname> + + <surname>DeLashmutt</surname> + + <email&gt;cdelashm(a)redhat.com&lt;/email&gt; + </author> + + <author> + <firstname>Xi</firstname> + + <surname>Huang</surname> + + <email&gt;xhuang(a)redhat.com&lt;/email&gt; + </author> </chapterinfo> <title>Installation</title> @@ -17,21 +33,21 @@ <para>The JBoss Portal bundle contains everything needed to execute JBoss Portal with the exception of Java itself. The JBoss Application Server in - the JBoss Portal bundle requires either JDK 1.4 or JDK 1.5. If you do not + the JBoss Portal bundle requires either JDK 1.5 or JDK 1.4. If you do not have one of these on the machine that JBoss Portal will be running on, please download it here: <ulink - url="http://java.sun.com/j2se/1.4.2/download.html">http://ja... + url="http://java.sun.com/javase/downloads/index_jdk5.jsp">ht...;. Once you have Java installed, you are ready to download the JBoss Portal bundle. The following link has the list of downloads for JBoss Portal: <ulink - url="http://www.jboss.com/products/jbossportal/downloads">ht... - . Please select the JBoss Portal bundled with JBoss Application Server and - select to download it to your machine. From here, you will need to unzip - it to your machine (Note: If you do not have Zip, please go to this link - to get it: <ulink + url="http://www.jboss.com/products/JBoss Portal/downloads">http://labs.jboss.com/portal/jbossportal/downlo... + . Download the "JBoss Portal +JBoss AS" bundle by clicking the "Download" + link on the right of the page. From here, you will need to unzip it to + your machine (Note: If you do not have a ZIP utility, please go to this + link to get it: <ulink url="http://sourceforge.net/projects/sevenzip/">http://sourc... ). Once you have unzipped it, you should have a directory structure with - the following folders under, jboss-portal-2.6-bundled: <itemizedlist> + the following folders under, jboss-portal-2.6-GA: <itemizedlist> <listitem> @@ -69,29 +85,17 @@ <emphasis role="bold">server</emphasis> - - Contains JBoss Application Server configuration and the Portal.sar file + - Contains JBoss Application Server configuration and the jboss-portal.sar file in the "deploy" directory </listitem> - </itemizedlist> - </para> - <note> - Binary distributions of JBoss Portal include the WSRP service which is not automatically deployed with the - source distribution. WSRP is built upon the JBoss WS web service stack. As such, it has some additional - constraints. In particular, there is a known issue with the version 1.0.0.GA of JBoss WS (bundled with JBoss - Application Server 4.0.4.GA) that prevents the complete deployment of JBoss Portal's WSRP service if the user - is not online or behind a firewall/proxy. This, in turn, prevents the deployment of JBoss Portal. If you do not - need the WSRP service, you can remove the <emphasis>portal-wsrp.sar</emphasis> file from the - <emphasis>jboss-portal.sar</emphasis> file. If you'd like to use the WSRP service, the JBoss WS issue has been - addressed in version 1.0.2.GA of JBoss WS. Please follow the instructions on - <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRP_UpdateJBossWS&quo... to upgrade JBoss WS</ulink> - as found on <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossPortal">J... Portal's wiki</ulink>. - </note> + </itemizedlist></para> </sect1> <sect1> <title>Starting JBoss Portal</title> - <para>Go to the bin directory and double click on the run.bat. A command - window should come up with the Portal console (Figure 1). <mediaobject> + <para>Go to the bin directory and double click on the run.sh (or run.bat). + A command window should come up displaying the startup messages for JBoss + Portal (Figure 1). <mediaobject> <imageobject> <imagedata align="center" fileref="images/image001.png" format="png" valign="middle" /> @@ -99,14 +103,14 @@ <caption><para>Figure 1: Portal console</para></caption> </mediaobject> <note> - If the database tables do not exist, you may see some errors the first time the portal runs and it creates the tables. This is not an error. + If the database tables do not exist, you may see a lot of messages the first time the portal runs and it creates the tables. This is not an error. </note></para> <para>Now, bring up your web browser and go to the following URL: <ulink - url="http://localhost:8080/portal">http://localhost:8080/portal</ulink> (You may also change the root context to "/", please refer to Reference Guide for details). + url="http://localhost:8080/portal">http://localhost:8080/portal</ulink> . You should see the default page for JBoss Portal (Figure 2). <mediaobject> <imageobject> - <imagedata align="center" fileref="images/image002.jpg" format="JPG" + <imagedata align="center" fileref="images/image002.png" format="PNG" scale="" valign="middle" /> </imageobject> Modified: docs/trunk/quickstartuser/en/modules/interaction.xml =================================================================== --- docs/trunk/quickstartuser/en/modules/interaction.xml 2007-06-29 00:07:57 UTC (rev 7622) +++ docs/trunk/quickstartuser/en/modules/interaction.xml 2007-06-29 00:10:09 UTC (rev 7623) @@ -1,581 +1,456 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="interaction"> - <chapterinfo> - <author> - <firstname>Kevin</firstname> + <chapterinfo> + <author> + <firstname>Kevin</firstname> - <surname>Barfield</surname> + <surname>Barfield</surname> - <email&gt;kevin.barfield(a)jboss.com&lt;/email&gt; - </author> - </chapterinfo> + <email&gt;kbarfiel(a)redhat.com&lt;/email&gt; + </author> - <title>Interaction with the Portal</title> + <author> + <firstname>Chris</firstname> - <sect1> - <title>Window States</title> + <surname>DeLashmutt</surname> - <para>Each portlet in the portal page can be interacted with individually. - Let's interact with a couple of portlets, and see the results. Click on - the minimize icon on the "Greeting" portlet. The portlet is - then minimized (Figure 5): - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image075.jpg" format="JPG" - scalefit="yes" valign="middle"/> - </imageobject> + <email&gt;cdelashm(a)redhat.com&lt;/email&gt; + </author> - <caption> - <para>Figure 5. Default page with portlet - minimized. - </para> - </caption> - </mediaobject> - Click on the maximize button for that same portlet, and - it now takes the entire page (Figure 6). Click on the "resize" icon to - return the portlet to its starting size. - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image076.jpg" format="JPG" - valign="middle"/> - </imageobject> + <author> + <firstname>Xi</firstname> - <caption> - <para>Figure 6. Portal with portlet - maximized. - </para> - </caption> - </mediaobject> - </para> - </sect1> + <surname>Huang</surname> - <sect1> - <title>User Creation</title> + <email&gt;xhuang(a)redhat.com&lt;/email&gt; + </author> + </chapterinfo> - <para>Let's create a user for the portal. Click on the "You can create a new user" link - in the user portlet. The create user view now shows in the user portlet. - Enter the information as shown in Figure 10 (password is starter). Once - you have clicked "New user registration" button, the default view will show (Figure - 11). - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image077.png" format="png" - valign="middle"/> - </imageobject> + <title>Interaction with the Portal</title> - <caption> - <para>Figure 10. The Create user view in the user - portlet. - </para> - </caption> - </mediaobject> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image078.jpg" format="jpg" - valign="middle"/> - </imageobject> + <sect1> + <title>Window States</title> - <caption> - <para>Figure 11. The default view after registering a new user.</para> - </caption> - </mediaobject> - </para> - </sect1> + <para>Each portlet in the portal page can be interacted with individually. + Let's interact with a couple of portlets, and see the results. Click on + the minimize icon on the "Greeting" portlet. The portlet is then minimized + (Figure 5): <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image075.png" format="PNG" + scalefit="yes" valign="middle" /> + </imageobject> - <sect1> - <title>Administrator Login</title> + <caption><para>Figure 5. Default page with portlet minimized. + </para></caption> + </mediaobject>Click on the maximize button for that same portlet, and it + now takes the entire page (Figure 6). Click on the "resize" icon to return + the portlet to its starting size. <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image076.png" format="PNG" + valign="middle" /> + </imageobject> - <para>Now, click "Login". The login page will show (Figure - 12). Log in with username and password of "admin" - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image079.jpg" format="png" - valign="middle"/> - </imageobject> + <caption><para>Figure 6. Portal with portlet maximized. + </para></caption> + </mediaobject></para> + </sect1> - <caption> - <para>Figure 12. Portal login page.</para> - </caption> - </mediaobject> - Click "Login", and the portal will now show us a link to the Admin portal (top-right) (Figure 13). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image080.jpg" format="png" - valign="middle"/> - </imageobject> + <sect1> + <title>User Creation</title> - <caption> - <para>Figure 13. default portal page for - administrator. - </para> - </caption> - </mediaobject> - </para> - </sect1> + <para>Let's create a user for the portal. Click on the "You can create an + account." link in the user portlet. The create user view now shows in the + user portlet. Enter the information as shown in Figure 7 (password is + starter). Once you have clicked "New user registration" button, the + default view will show (Figure 8). <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image077.png" format="png" + valign="middle" /> + </imageobject> - <sect1> - <title>Content Management</title> + <caption><para>Figure 7. The Create user view in the user portlet. + </para></caption> + </mediaobject> <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image078.png" format="PNG" + valign="middle" /> + </imageobject> - <para>Now that we are logged in, there is a portal page available for the - content management and portal administration. Click on the "Admin" link, and then on the "CMS" tab. - The CMS Admin portal page displays(Figure 14). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image081.jpg" format="png" - valign="middle"/> - </imageobject> + <caption><para>Figure 8. The default view after registering a new + user.</para></caption> + </mediaobject>This example models a user enrolling themselves in the + portal security repository, and at this point the user could login and + would have the default security role for the portal. Administrators can + also control user administration from the Admin portion of the portal for + more advanced user enrollment options. This will be covered in a later + section.</para> + </sect1> - <caption> - <para>Figure 14. CMS Admin portal page.</para> - </caption> - </mediaobject> - The content management portlet allows users to - create/delete files and folders, edit text/HTML files, and batch upload - files. These files are then viewable through the content view portlet. - HTML files can refer to other HTML files through the directory structure - in the CMS. Different groups or departments in an organization can have - their own area (directory structure) for the files/HTML pages they want to - share on the Portal. Let's batch upload a set of HTML pages with images - and style sheets. Mouse-over the "Select Action" dropdown menu, and click on the upload archive link. The - upload archive view shows (Figure 15). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image082.jpg" format="png" - valign="middle"/> - </imageobject> + <sect1> + <title>Administrator Login</title> - <caption> - <para>Figure 15. Upload Archive view.</para> - </caption> - </mediaobject> - <note> - Please use the quickstart.zip for the batch upload. You may also download it from - <ulink url="http://docs.jboss.org/jbportal/v2.6/quickstartuser/en/quickstar... - . - </note> - We can choose the destination folder for the upload (the current - folder structure is shown on the right), and the language of the files - being uploaded. Click browse to find the file you want to upload (Figure - 16). - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image011.jpg" - format="JPEG" valign="middle"/> - </imageobject> + <para>Now, click "Login". The login page will show (Figure 9). Log in with + username and password of "admin" <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image079.png" format="png" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 16. Choose file to batch - upload. - </para> - </caption> - </mediaobject> - Click on the quickstart.zip that you downloaded - earlier(see note above) and select "Open". The quickstart.zip will be - uploaded into the content repository, and the files and directories will - now appear in the content management structure (see the new quickstart - directory in Figure 17). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image012.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 9. Portal login page.</para></caption> + </mediaobject>Click "Login", and the portal will now show us a link to + the Admin portal (top-right) (Figure 10). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image080.png" format="png" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 17. New quickstart directory shows in content - management repository. - </para> - </caption> - </mediaobject> - </para> + <caption><para>Figure 10. default portal page for administrator. + </para></caption> + </mediaobject></para> + </sect1> - <para>Click on the quickstart link to see the HTML files and - sub-directories that were uploaded (Figure 18). Click on the "home" symbol - to return to the top of the content manager repository (back to Figure - 17). - </para> + <sect1> + <title>Content Management</title> - <para> - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image013.jpg" format="JPG" - valign="middle"/> - </imageobject> + <para>Now that we are logged in, there is a portal page available for the + content management and portal administration. Click on the "Admin" link, + and then on the "CMS" tab. The CMS Admin portal page displays (Figure + 11).<mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image081.png" format="png" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 18. HTML files and sub-directories that were - uploaded intoquickstart directory shows in content management - repository. - </para> - </caption> - </mediaobject> - </para> + <caption><para>Figure 11. CMS Admin portal page.</para></caption> + </mediaobject>The content management portlet allows users to + create/delete files and folders, edit text/HTML files, and batch upload + files. These files are then viewable through the content view portlet. + HTML files can refer to other HTML files through the directory structure + in the CMS. Different groups or departments in an organization can have + their own area (directory structure) for the files/HTML pages they want to + share on the Portal. Let's batch upload a set of HTML pages with images + and style sheets. Mouse-over the "Select Action" dropdown menu, and click + on the upload archive link. The upload archive view shows (Figure + 12).<mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image082.png" format="png" + valign="middle" /> + </imageobject> - <para></para> + <caption><para>Figure 12. Upload Archive view.</para></caption> + </mediaobject> <note> + Please use the quickstart.zip for the batch upload. You may also download it from - <para>Let's edit the default page to contain a link to our new pages. - Clicking on the default link, we can see that an images directory, as well - as three HTML files (Figure 19). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image014.jpg" format="JPG" - valign="middle"/> - </imageobject> + <ulink + url="http://docs.jboss.org/jbportal/v2.6/quickstartuser/en/quickstar... - <caption> - <para>Figure 19. Default directory listing.</para> - </caption> - </mediaobject> - Click on the index.html link. The file browser will show - the versions of this file (Figure 20). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image015.jpg" format="JPG" - valign="middle"/> - </imageobject> + . + </note>You can choose the destination folder for the upload by selecting + a folder from the tree control on the left side of the portlet. Then you + can select the language of the files being uploaded from the drop down + list. Finally, click "Browse" to find the file you want to upload (Figure + 13).<mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image011.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 20. Version view for - index.html. - </para> - </caption> - </mediaobject> - To edit this HTML file, click on the "text/html" link. The - WYSIWYG editor view will appear (Figures 21 and 22). Note: The WYSIWYG - editor is dependent on browser. Some browsers show a box to enter HTML. - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image016.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 13. Choose file to batch upload. + </para></caption> + </mediaobject>Click on the quickstart.zip that you downloaded earlier + (see note above) and select "Open". Finally, click the "Upload" button. + The quickstart.zip file will be uploaded, extracted into the content + repository, and the files and directories will now appear in the content + management structure (see the new "quickstart" directory in Figure + 14).<mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image012.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 21. Content editor view.</para> - </caption> - </mediaobject> - </para> + <caption><para>Figure 14. New quickstart directory shows in content + management repository. </para></caption> + </mediaobject></para> - <para>HTML pages can be edited through this view. Let's change this page - to point to our uploaded pages. Change the title next to the lightning - bolt from "Project Information" to "Quickstart Guide" and change the text - following the link below that to "to see the Quickstart guide for JBoss - Portal.". The updated text is in Figure 24. - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image019.jpg" format="JPG" - valign="middle"/> - </imageobject> + <para>Click on the quickstart link to see the HTML files and + sub-directories that were uploaded (Figure 15). Click on the "Home" link + from the breadcrumbs at the top of the portlet to return to the top + directory of the content manager repository (back to Figure 14).</para> - <caption> - <para>Figure 24. Updated text in HTML page.</para> - </caption> - </mediaobject> - </para> + <para><mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image013.png" format="PNG" + valign="middle" /> + </imageobject> - <para>Now let's update the link to point to the index.html page in the - quickstart directory. Click on the "Click here" link under Portal - Documentation, then on the edit link button (it looks like a chain). The - insert/edit link window appears. Change the Link URL to - "quickstart/index.html" (Figure 25). - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image021.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 15. HTML files and sub-directories that were + uploaded intoquickstart directory shows in content management + repository. </para></caption> + </mediaobject></para> - <caption> - <para>Figure 25. Insert/edit link window with updated link - URL - </para> - </caption> - </mediaobject> - Click "Update" button to save the updated link. Then click "Create" button to - create the new version of the HTML file. The file browser view shows again - with the new 1.1 version shown (Figure 26). The star icon next to the - version number shows this is the live version. - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image022.jpg" format="JPG" - valign="middle"/> - </imageobject> + <para>Let's edit the default page to contain a link to our new pages. + Clicking on the default link, we can see two directories, as well as three + HTML files (Figure 16). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image014.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 26. File browser with new version of - index.html. - </para> - </caption> - </mediaobject> - Click on the "Portal" link to see the changes we - have made. The content view portlet shows the update page for the portal - documentation (Figure 27). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image023.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 16. Default directory listing.</para></caption> + </mediaobject>Click on the index.html link. The file browser will show + the versions of this file (Figure 17). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image015.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 27. Content view portlet with the updated - default page. - </para> - </caption> - </mediaobject> - Click on the "Click here" link that was updated to go to - the new uploaded content (Figure 28). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image024.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 17. Version view for index.html. + </para></caption> + </mediaobject>To edit this HTML file, click on the "text/html" link. The + WYSIWYG editor view will appear (Figures 18). Note: The WYSIWYG editor is + dependent on browser. Some browsers show a box to enter HTML. <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image016.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 28. Content view portlet with docs page - shown. - </para> - </caption> - </mediaobject> - The links on the docs HTML page will go to other pages - that were uploaded to the content repository. Try them out to see for - yourself. - </para> - </sect1> + <caption><para>Figure 18. Content editor view.</para></caption> + </mediaobject></para> - <sect1> - <title>Portal Management</title> + <para>HTML pages can be edited through this view. Let's change this page + to point to our uploaded pages. Change the section title next to the + PortletSwap table cell from "Project Information" to "Quickstart Guide" + and change the text following the link below that to "to see the + Quickstart guide for JBoss Portal.". The updated text is in Figure 19. + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image019.png" format="PNG" + valign="middle" /> + </imageobject> - <para>Click on the Admin link. From this Admin Portal, you should have access to the CMS, Members, WSRP and Portal - management interfaces. (Figure 29). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image108.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 19. Updated text in HTML page.</para></caption> + </mediaobject></para> - <caption> - <para>Figure 29. Admin portal page.</para> - </caption> - </mediaobject> - Click the "Members" tab to access the member management page. Click on the "Search" button to see the users - in the portal (Figure 30). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image084.jpg" format="JPG" - valign="middle"/> - </imageobject> + <para>Now let's update the link to point to the index.html page in the + quickstart directory. Click on the "Click here" link under Portal + Documentation, then on the edit link button (it looks like a chain). The + insert/edit link window appears. Change the Link URL to + "quickstart/index.html" (Figure 20). <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image021.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 30. User portlet with user list - view. - </para> - </caption> - </mediaobject> - The starter user we created is shown in the list. Click - on the "Roles" link next to the starter user to see the available roles - (Figure 31). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image085.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 20. Insert/edit link window with updated link + URL </para></caption> + </mediaobject>Click "Update" button to save the updated link. Then click + "Create" button at the bottom of the portlet window to create the new + version of the HTML file. The CMS Administration view shows again with the + new 1.1 version shown (Figure 21). The star icon next to the version + number shows this is the live version. <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image022.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 31. User portlet with available roles - view. - </para> - </caption> - </mediaobject> - Add "Administrators" role and click the "Assign - roles" button. This brings us back to the User portlet menu view (Figure - 32). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image086.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 21. File browser with new version of index.html. + </para></caption> + </mediaobject>Click on the "Portal" link in the upper right corner of + the browser page to see the changes we have made. The content view portlet + shows the updated version of the index.html page we edited above (Figure + 22). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image023.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 32. User portlet menu view.</para> - </caption> - </mediaobject> - Now let's look at the user profile for the starter user. - Click on the "Profile" link next to the - starter user. The user profile view appears (Figure 33). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image087.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 22. Content view portlet with the updated + default page. </para></caption> + </mediaobject>Click on the "Click here" link that was updated to go to + the new uploaded content (Figure 23). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image024.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 33. User profile view.</para> - </caption> - </mediaobject> - This shows all of the fields available in the user - profile. Enter the first name of "starter" and click the "Save changes" - button. The Member management page is displayed now.(Figure - 34). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image089.jpg" format="jpg" - valign="middle"/> - </imageobject> + <caption><para>Figure 23. Content view portlet with docs page shown. + </para></caption> + </mediaobject>The links on the quickstart HTML page that you uploaded + will go to the other pages that were uploaded to the content repository + with it. Try them out to see for yourself.</para> + </sect1> - <caption> - <para>Figure 34. Member management portal page default - view. - </para> - </caption> - </mediaobject> - Now, let's explore the management portlet, by clicking on the "Home" tab. This portlet - shows a view of the portals, portal pages and portlet instances. - Click on "root" link, then choose the "admin" portal. - This shows us that there is an admin portal with 4 portal pages defined: CMS, default, WSRP and Members. After clicking "Members" link, we can see the 2 - portlet instances that are used in the Members portal page (Figure 35). - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image088.jpg" format="JPG" - valign="middle"/> - </imageobject> + <sect1> + <title>Portal Management</title> - <caption> - <para>Figure 35. Management portlet page view. - </para> - </caption> - </mediaobject> - <!--Using the arrows next to the portlet instance names, we - can dynamically move the portlet instances on the portal page. Click on - the up arrow icon next to the RolePortletWindow to move the role portlet - above the user portlet.--> + <para>Click on the Admin link in the upper right of the browser page. From + this Admin Portal, you should have access to the CMS, Members, WSRP and + Portal management interfaces. (Figure 24). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image108.png" format="PNG" + valign="middle" /> + </imageobject> - Let's create a new portal page. Click on the "root" link then choose "default" - portal. The add portal page view is shown (Figure 37). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image090.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 24. Admin portal page.</para></caption> + </mediaobject>Click the "Members" tab to access the member management + page. Click on the "Search" button to see all of the users currently + enrolled in the portal security repository (Figure 25). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image084.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 37. Management portlet add page - view. - </para> - </caption> - </mediaobject> - Enter "Starter" as the page name and click the "Add" - button. We now see the "Starter" page - in the list of portal pages (Figure 38). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image091.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 25. User portlet with user list view. + </para></caption> + </mediaobject>The starter user we created is shown in the list. Click on + the "Roles" link next to the starter user to see the available roles + (Figure 26). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image085.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 38. Starter portal page has been - added. - </para> - </caption> - </mediaobject> - Now let's add some portlet instances to the portal page. - Click on "Page layout" link of the "Starter" entry in the Management Portlet, and the details for - that portal page are shown (Figure 39). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image092.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 26. User portlet with available roles view. + </para></caption> + </mediaobject>Add the "Administrators" role to this user by selecting it + from the "Available roles" list box and clicking the "Add Roles" button. + Click the "Assign roles" button to apply the new roles list to the user. + This brings us back to the User portlet menu view (Figure 27). + <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image086.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 39. Management portlet for Starter portal - page. - </para> - </caption> - </mediaobject> - First, let's add a weather portlet. Choose the - "WeatherPorletInstance" portlet instance from the list (Figure 40). - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/image093.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 27. User portlet menu view.</para></caption> + </mediaobject>Now let's look at the user profile for the starter user. + Click on the "Profile" link next to the starter user. The user profile + view appears (Figure 28). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image087.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 40. Choosing the "WeatherPorletInstance" portlet instance - from the list. - </para> - </caption> - </mediaobject> - Type in the name you want to give this portlet instance - ("weather"), set Target Region to "center", then click the "Select" button. The "weather" portlet instance - is now shown under the "center Region" (Figure 41). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image094.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 28. User profile view.</para></caption> + </mediaobject>This shows all of the fields available in the user + profile. Enter the first name of "starter" and click the "Save changes" + button. The Member management page is displayed now (Figure 29). + <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image089.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 41. Nav portlet instance is - added. - </para> - </caption> - </mediaobject> - Click on the "Portlet Instance" tab to go into the details for that - portlet instance (Figure 42) - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image095.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 29. Member management portal page default view. + </para></caption> + </mediaobject>Now, let's explore the management portlet, by clicking on + the "Home" tab. This portlet shows a view of the portals, portal pages and + portlet instances. Click on the "admin" portal link. This shows us that + there is an admin portal with 4 portal pages defined: CMS, default, WSRP + and Members. After clicking "Members" page link, we can see the 2 portlet + instances that are used in the Members portal page (Figure 30). + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image088.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 42. Details for the weather portlet - instance. - </para> - </caption> - </mediaobject> - Click on the "Portal Objects" tab, choose the "default" portal then "Starter" link. You may update the theme for this - portlet. Let's set the Window Renderer, Decoration Renderer, and - Portlet Renderer to "emptyRenderer" (Figure 43). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image096.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 30. Management portlet page view. + </para></caption> + </mediaobject>Let's create a new portal page. Click on the "root" + breadcrumb link below the "Portal Objects" tab then choose "default" + portal. Enter "Starter" in the text field next to the "Create a page:" + label. Your portal page view should match the following figure (Figure + 31).<mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image090.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 43. Theme details for the weather portlet - instance. - </para> - </caption> - </mediaobject> - Finally, let's take a look at security in the Management - Portlet. Click on the "Security" link, and the list of available roles and - actions is shown for the "Starter" portal page.(Figure 45). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image098.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 31. Management portlet add page view. + </para></caption> + </mediaobject>Click the "Add" button to create the new page. We now see + the "Starter" page in the list of portal pages (Figure 32). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image091.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 45. Security for the "Starter" portal - page. - </para> - </caption> - </mediaobject> - Let's take a look at the Starter portal page we created. - Click on the "Portal" link, and then the "Starter" tab at the top to go to the "Starter" portal page - (Figure 46). - <mediaobject> - <imageobject> - <imagedata align="left" fileref="images/image100.jpg" format="JPG" - valign="middle"/> - </imageobject> + <caption><para>Figure 32. Starter portal page has been added. + </para></caption> + </mediaobject>Now let's add some portlet instances to the portal page. + Click on "Page layout" link of the "Starter" entry in the Management + Portlet, and the details for that portal page are shown (Figure 33). + <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image092.png" format="PNG" + valign="middle" /> + </imageobject> - <caption> - <para>Figure 46. The Starter portal page.</para> - </caption> - </mediaobject> - </para> - </sect1> + <caption><para>Figure 33. Management portlet for Starter portal page. + </para></caption> + </mediaobject>First, let's add a weather portlet. We know this is + portlet, so we can leave the "Content Type" drop-down set to "portlet". + It's a good idea to give the new portlet window a name instead of relying + on the portal to generate one for you, so enter "weather" in the "Window + Name" field. In the list labeled "Select a portlet instance to associate + to this window", select the "WeatherPortletInstance" portlet instance and + click the "Select" button. You can verify that you have the proper portlet + instance selected by viewing the details that show up below the Portlet + Instance list at the bottom of the portlet (Figure 34).<mediaobject> + <imageobject> + <imagedata align="center" fileref="images/image093.png" format="PNG" + valign="middle" /> + </imageobject> + + <caption><para>Figure 34. Choosing the "WeatherPorletInstance" portlet + instance from the list. </para></caption> + </mediaobject>Scroll up to the list box that is labeled "center Region". + Click the "Add" button to the left of that list box. The "weather" portlet + instance is now shown under the "center Region" (Figure 35). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image094.png" format="PNG" + valign="middle" /> + </imageobject> + + <caption><para>Figure 35. Weather portlet instance is added. + </para></caption> + </mediaobject>Lets change the theme for the weather portlet window we + just added so that the weather portlet window doesn't display any + decorations. Click on the "default" link in the breadcrumbs below the + "Portal Objects" tab, then choose the "Starter" link. Click on the "theme" + action link next to the "weather" window. Let's set the Window Renderer, + Decoration Renderer, and Portlet Renderer to "emptyRenderer" (Figure 36). + <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image096.png" format="PNG" + valign="middle" /> + </imageobject> + + <caption><para>Figure 36. Theme details for the weather portlet + instance. </para></caption> + </mediaobject>Click the "Update" button to apply the theme changes. + Finally, let's take a look at security in the Management Portlet. Click on + the "Starter" page in the breadcrumbs below the "Portal Objects" tab. Next + click the "Security" link which is just below the breadcrumbs links, and + the list of available roles and actions is shown for the "Starter" portal + page.(Figure 37). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image098.png" format="PNG" + valign="middle" /> + </imageobject> + + <caption><para>Figure 37. Security for the "Starter" portal page. + </para></caption> + </mediaobject>Let's take a look at the Starter portal page we created. + Click on the "Portal" link, and then the "Starter" tab at the top to go to + the "Starter" portal page (Figure 38). <mediaobject> + <imageobject> + <imagedata align="left" fileref="images/image100.png" format="PNG" + valign="middle" /> + </imageobject> + + <caption><para>Figure 38. The Starter portal page.</para></caption> + </mediaobject></para> + </sect1> </chapter> \ No newline at end of file Modified: docs/trunk/quickstartuser/en/modules/overview.xml =================================================================== --- docs/trunk/quickstartuser/en/modules/overview.xml 2007-06-29 00:07:57 UTC (rev 7622) +++ docs/trunk/quickstartuser/en/modules/overview.xml 2007-06-29 00:10:09 UTC (rev 7623) @@ -1,87 +1,106 @@ +<?xml version="1.0" encoding="UTF-8"?> <preface id="overview"> - <title>JBoss Portal - Overview</title> - <para> - <imageobject> - <imagedata fileref="images/image002.jpg" format="JPG" align="center" - valign="middle"/> - </imageobject> - </para> - <para>Many IT organizations look to achieve a competitive advantage for the enterprise by - improving business productivity and reducing costs. Today's top enterprises are realizing this - goal by deploying enterprise portals within their IT infrastructure. Enterprise portals - simplify access to information by providing a single source of interaction with corporate - information. Although today's packaged portal frameworks help enterprises launch portals more - quickly, only JBoss Portal can deliver the benefits of a zero-cost open source license - combined with a flexible and scalable underlying platform.</para> - <para>JBoss Portal provides an open source and standards-based environment for hosting and - serving a portal's Web interface, publishing and managing its content, and customizing its - experience. It is entirely standards-based and supports the JSR-168 portlet specification, - which allows you to easily plug-in standards-compliant portlets to meet your specific portal - needs. JBoss Portal is available through the business-friendly - <ulink - url="http://www.jboss.com/company/aboutopensource">LGPL</... - open source license and is - supported by - <ulink url="http://www.jboss.com/services/index">JBoss Inc. Professional Support - and Consulting</ulink> - . JBoss support services are available to assist you in designing, - developing, deploying, and ultimately managing your portal environment. JBoss Portal is - currently developed by JBoss, Inc. developers, Novell developers, and community contributors. - </para> - <para>The JBoss Portal framework and architecture includes the portal container and supports a - wide range of features including standard portlets, single sign-on, clustering and - internationalization. Portal themes and layouts are configurable. Fine-grained security - administration down to portlet permissions rounds out the security model. JBoss Portal - includes a rich content management system and message board support.</para> - <para> - <emphasis role="bold">JBoss Portal Resources:</emphasis> - <orderedlist> - <listitem> - <para> - <ulink url="http://www.jboss.org/products/jbossportal">JBoss Portal Home Page</ulink> - </para> - </listitem> - <listitem> - <para> - <ulink url="http://labs.jboss.com/portal/jbossportal/download/index.html&qu... - </para> - </listitem> - <listitem> - <para>Forums: - <ulink - url="http://www.jboss.org/index.html?module=bb&amp;op=viewforum&... - >User</ulink> - | - <ulink - url="http://www.jboss.org/index.html?module=bb&amp;op=viewforum&... - >Developer</ulink> - | - <ulink url="http://jboss.org/index.html?module=bb&amp;op=viewforum&... - | - <ulink url="http://jboss.org/index.html?module=bb&amp;op=viewforum&... Portlet - Plugin</ulink> - </para> - </listitem> - <listitem> - <para> - <ulink url="http://www.jboss.com/wiki/Wiki.jsp?page=JBossPortal">Wi... - </para> - </listitem> - <listitem> - <para> - <ulink url="http://www.portletswap.com">PortletSwap.com portlet exchange</ulink> - </para> - </listitem> - <listitem> - <para> - <ulink - url="http://jira.jboss.com/jira/browse/JBPORTAL?report=com.atlassian... - >Our Roadmap</ulink> - </para> - </listitem> - </orderedlist> - </para> - <para>The JBoss Portal team encourages you to use this guide to install and configure JBoss - Portal. If you encounter any configuration issues or simply want to take part in our - community, we would love to hear from you in our forums.</para> + <title>JBoss Portal - Overview</title> + + <para> + <imageobject> + <imagedata align="center" fileref="images/image002.png" format="PNG" + valign="middle" /> + </imageobject> + </para> + + <para>Many IT organizations look to achieve a competitive advantage for the + enterprise by improving business productivity and reducing costs. Today's + top enterprises are realizing this goal by deploying enterprise portals + within their IT infrastructure. Enterprise portals simplify access to + information by providing a single source of interaction with corporate + information. Although today's packaged portal frameworks help enterprises + launch portals more quickly, only JBoss Portal can deliver the benefits of a + zero-cost open source license combined with a flexible and scalable + underlying platform.</para> + + <para>JBoss Portal provides an open source and standards-based environment + for hosting and serving a portal's Web interface, publishing and managing + its content, and customizing its experience. It is entirely standards-based + and supports the JSR-168 portlet specification, which allows you to easily + plug-in standards-compliant portlets to meet your specific portal needs. + JBoss Portal is available through the business-friendly <ulink + url="http://www.jboss.org/opensource/lgpl/faq">LGPL</ulin... open source + license and is supported by <ulink + url="http://www.jboss.com/services/index">Red Hat</ulink>. Red Hat support + services are available to assist you in designing, developing, deploying, + and ultimately managing your portal environment. JBoss Portal is currently + developed by Red Hat, Inc. developers, and community contributors. </para> + + <para>The JBoss Portal framework and architecture includes the portal + container and supports a wide range of features including standard portlets, + single sign-on, clustering and internationalization. Portal themes and + layouts are configurable. Users have the ability to fully customize thier + own personal portal pages. Fine-grained security administration down to + portlet permissions rounds out the security model. JBoss Portal includes a + rich content management system with approval cycle support.</para> + + <para> + <emphasis role="bold">JBoss Portal Resources:</emphasis> + + <orderedlist> + <listitem> + <para> + <ulink url="http://www.jboss.org/products/jbossportal">JBoss Portal + Project Home Page</ulink> + </para> + </listitem> + + <listitem> + <para> + <ulink + url="http://labs.jboss.com/jbossportal/download/index.html">... + </para> + </listitem> + + <listitem> + <para> + <ulink + url="http://labs.jboss.com/jbossportal/docs/index.html">Docu... + </para> + </listitem> + + <listitem> + <para>Forums: <ulink + url="http://www.jboss.org/index.html?module=bb&amp;op=viewforum&... + | <ulink + url="http://www.jboss.org/index.html?module=bb&amp;op=main&a... + | <ulink + url="http://jboss.org/index.html?module=bb&amp;op=viewforum&... + Portlet Plugin</ulink> </para> + </listitem> + + <listitem> + <para> + <ulink + url="http://www.jboss.com/wiki/Wiki.jsp?page=JBossPortal">Wi... + </para> + </listitem> + + <listitem> + <para> + <ulink url="http://www.portletswap.com">PortletSwap.com portlet + exchange</ulink> + </para> + </listitem> + + <listitem> + <para> + <ulink + url="http://jira.jboss.com/jira/browse/JBPORTAL?report=com.atlassian... + Roadmap</ulink> + </para> + </listitem> + </orderedlist> + </para> + + <para>The JBoss Portal team encourages you to use this guide to install and + configure JBoss Portal. If you encounter any configuration issues or simply + want to take part in our community, we would love to hear from you in our + forums.</para> </preface> Modified: docs/trunk/quickstartuser/en/modules/portalterminology.xml =================================================================== --- docs/trunk/quickstartuser/en/modules/portalterminology.xml 2007-06-29 00:07:57 UTC (rev 7622) +++ docs/trunk/quickstartuser/en/modules/portalterminology.xml 2007-06-29 00:10:09 UTC (rev 7623) @@ -6,8 +6,24 @@ <surname>Barfield</surname> - <email&gt;kevin.barfield(a)jboss.com&lt;/email&gt; + <email&gt;kbarfiel(a)redhat.com&lt;/email&gt; </author> + + <author> + <firstname>Chris</firstname> + + <surname>DeLashmutt</surname> + + <email&gt;cdelashm(a)redhat.com&lt;/email&gt; + </author> + + <author> + <firstname>Xi</firstname> + + <surname>Huang</surname> + + <email&gt;xhuang(a)redhat.com&lt;/email&gt; + </author> </chapterinfo> <title>Portal Terminology</title> @@ -56,7 +72,7 @@ </listitem> </itemizedlist> <mediaobject> <imageobject> - <imagedata align="center" fileref="images/image005.jpg" format="jpg" + <imagedata align="center" fileref="images/image005.png" format="PNG" valign="middle" /> </imageobject> @@ -66,18 +82,18 @@ <para>Now let's look at that default portal page again with these terms in mind (Figure 4). <mediaobject> <imageobject> - <imagedata align="left" fileref="images/image006.jpg" format="JPG" + <imagedata align="left" fileref="images/image006.png" format="PNG" valign="middle" /> </imageobject> <caption><para>Figure 4. The default portal page with components highlighted.</para></caption> - </mediaobject> Now we see that the default portal we are looking at has - three portal pages, and the default portal page has five portlets on it - (navigation, greetings, user, portal pages, and content view). In addition, - we see that each portlet window is made up of decorations/controls and a - portlet fragment (navigation does not need decoration/controls). Each - portlet can represent some fragment of information that you want to present - to users. By having multiple portlets on a portal page, we can aggregate - portlet information.</para> + </mediaobject>Now we see that the default portal we are looking at has + four portal pages, and the default portal page has three portlets on it + (greetings, user, and content view). In addition, we see that each portlet + window is made up of decorations/controls and a portlet fragment (the + content view does not have any decoration/controls). Each portlet can + represent some fragment of information that you want to present to users. By + having multiple portlets on a portal page, we can aggregate information from + the portlets into a single browser window.</para> </chapter> \ No newline at end of file