[jboss-cvs] jboss-portal-docs/quickstart-user/en/modules ...
Roy Russo
russo at jboss.com
Tue Jul 18 12:16:08 EDT 2006
User: russo
Date: 06/07/18 12:16:08
Modified: quickstart-user/en/modules deployportlet.xml fin.xml
forward.xml installation.xml interaction.xml
portalterminology.xml
Log:
JBPORTAL-942 - updated to 2.4
Revision Changes Path
1.2 +110 -87 jboss-portal-docs/quickstart-user/en/modules/deployportlet.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: deployportlet.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-portal-docs/quickstart-user/en/modules/deployportlet.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- deployportlet.xml 28 Jun 2006 14:40:11 -0000 1.1
+++ deployportlet.xml 18 Jul 2006 16:16:08 -0000 1.2
@@ -3,88 +3,111 @@
<chapterinfo>
<author>
<firstname>Kevin</firstname>
+
<surname>Barfield</surname>
- <email>kevin.barfield at jboss.org</email>
+
+ <email>kevin.barfield at jboss.com</email>
</author>
</chapterinfo>
+
<title>Deploying Portlets</title>
- <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 46).
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/image089.png" format="png" align="center" valign="middle"/>
- </imageobject>
- <caption>
- <para>Figure 46. Portletswap website</para>
- </caption>
- </mediaobject>
- Click on the "Browse Portlets" link to see the categories of portlets available (Figure 47).
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/image091.png" format="png" align="center" valign="middle"/>
- </imageobject>
- <caption>
- <para>Figure 47. Portlet categories on portletswap.</para>
- </caption>
- </mediaobject>
- Click on the Miscellaneous Portlets browse link to see a list of portlets (Figure 48).
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/image093.png" format="png" align="center" valign="middle"/>
- </imageobject>
- <caption>
- <para>Figure 48. List of portlets on portletswap.</para>
- </caption>
- </mediaobject>
- Click on the download link next to the JBoss Weather Portlet. The download dialog will appear (Figure 49).
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/image095.png" format="png" align="center" valign="middle"/>
- </imageobject>
- <caption>
- <para>Figure 49. Download dialog.</para>
- </caption>
- </mediaobject>
- Save the zip file to your machine (Figure 50).
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/image097.png" format="png" align="center" valign="middle"/>
- </imageobject>
- <caption>
- <para>Figure 50. Saving the portlet zip file.</para>
- </caption>
- </mediaobject>
- This zip file contains both the binary and the source for the portlet. Open the zip and extract the
- weatherportlet.ear file. Place this file in the jboss-portal/server/default/deploy directory. The console for the
- JBoss Portal will show the portlet being deployed (Figure 51).
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/image099.png" format="png" align="center" valign="middle"/>
- </imageobject>
- <caption>
- <para>Figure 51. Weather portlet is deployed to JBoss Portal.</para>
- </caption>
- </mediaobject>
- To see the deployed portlet, simply refresh the page. A new "Weather" tab will appear (Figure 52).
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/image101.png" format="png" align="center" valign="middle"/>
- </imageobject>
- <caption>
- <para>Figure 52. Weather portal page now appears.</para>
- </caption>
- </mediaobject>
- The Weather portal page was created automatically by JBoss Portal as part of the deployment of the weather
- portlet. The weather portlet had in its configuration descriptor for the portal to create the Weather portal page.
- Click on the Weather portal page to see the weather portlet (Figure 53).
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/image103.png" format="png" align="center" valign="middle"/>
- </imageobject>
- <caption>
- <para>Figure 53. Weather portal page with weather portlet.</para>
- </caption>
- </mediaobject>
- </para>
+
+ <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/image089.png" format="png"
+ valign="middle" />
+ </imageobject>
+
+ <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>
+
+ <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>
+
+ <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>
+
+ <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-portal-2.4\server\default\deploy directory. The console for the
+ JBoss Portal will show the portlet being deployed (Figure 51). <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/image066.jpg" format="JPG"
+ valign="middle" />
+ </imageobject>
+
+ <caption><para>Figure 51. Flash portlet is deployed to JBoss
+ Portal.</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 Admin portal page (Figure 52). <mediaobject>
+ <imageobject>
+ <imagedata align="left" fileref="images/image012.jpg" format="JPG"
+ valign="middle" />
+ </imageobject>
+
+ <caption><para>Figure 52. Admin portal page.</para></caption>
+ </mediaobject></para>
+
+ <para>Click on the Portlets link. 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 53. Portlets admininstration.</para></caption>
+ </mediaobject> Type in "Flash Portlet " as the instance name and click on
+ the create instance button. Now there is an instance of the portlet that can
+ be added to the Starter portal page. Click on the Instances link to see all
+ portlet instances (Figure 54).<mediaobject>
+ <imageobject>
+ <imagedata align="left" fileref="images/image104.jpg" format="JPG"
+ valign="middle" />
+ </imageobject>
+
+ <caption><para>Figure 54. Portlet instances
+ admininstration.</para></caption>
+ </mediaobject>Click on the Portal link and expand the tree to the Starter
+ portal page. Select the 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 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 56. Starter portal page with flash
+ portlet.</para></caption>
+ </mediaobject></para>
</chapter>
\ No newline at end of file
1.2 +44 -23 jboss-portal-docs/quickstart-user/en/modules/fin.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: fin.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-portal-docs/quickstart-user/en/modules/fin.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- fin.xml 28 Jun 2006 14:49:14 -0000 1.1
+++ fin.xml 18 Jul 2006 16:16:08 -0000 1.2
@@ -3,23 +3,44 @@
<chapterinfo>
<author>
<firstname>Kevin</firstname>
+
<surname>Barfield</surname>
- <email>kevin.barfield at jboss.org</email>
+
+ <email>kevin.barfield at jboss.com</email>
</author>
</chapterinfo>
+
<title>Tutorial End</title>
- <para>Congratulations! You have completed the JBoss Portal Quickstart Tutorial. During this tutorial, you:
- <itemizedlist>
- <listitem>Downloaded and unziped the JBoss Portal bundle</listitem>
- <listitem>Executed the JBoss Portal</listitem>
- <listitem>Interacted with the default portal</listitem>
- <listitem>Created and edited content in the JBoss Portal</listitem>
- <listitem>Managed the JBoss Portal</listitem>
- <listitem>Added a new portlet to the JBoss Portal</listitem>
- </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 and developer's tutorials for developers using JBoss Portal,
- accessible from our
- <ulink url="http://labs.jboss.com/portal/jbossportal/download/index.html">Documentation Page</ulink>
- </para>
+
+ <para>Congratulations! You have completed the JBoss Portal Quickstart
+ Tutorial. During this tutorial, you: <itemizedlist>
+ <listitem>
+ Downloaded and unziped the JBoss Portal bundle
+ </listitem>
+
+ <listitem>
+ Executed the JBoss Portal
+ </listitem>
+
+ <listitem>
+ Interacted with the default portal
+ </listitem>
+
+ <listitem>
+ Created and edited content in the JBoss Portal
+ </listitem>
+
+ <listitem>
+ Managed the JBoss Portal
+ </listitem>
+
+ <listitem>
+ Added a new portlet to the JBoss Portal
+ </listitem>
+ </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">Documentation
+ Page</ulink></para>
</chapter>
1.2 +62 -34 jboss-portal-docs/quickstart-user/en/modules/forward.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: forward.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-portal-docs/quickstart-user/en/modules/forward.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- forward.xml 26 Jun 2006 16:00:02 -0000 1.1
+++ forward.xml 18 Jul 2006 16:16:08 -0000 1.2
@@ -3,35 +3,63 @@
<chapterinfo>
<author>
<firstname>Kevin</firstname>
+
<surname>Barfield</surname>
- <email>kevin.barfield at jboss.org</email>
+
+ <email>kevin.barfield at jboss.com</email>
</author>
</chapterinfo>
+
<title>Tutorial Forward</title>
- <para>Welcome to the JBoss Portal Quickstart tutorial. In this tutorial, you will:
- <itemizedlist>
- <listitem>Download and unzip the JBoss Portal bundle</listitem>
- <listitem>Execute the JBoss Portal</listitem>
- <listitem>Interact with the default portal</listitem>
- <listitem>Create and edit content in the JBoss Portal</listitem>
- <listitem>Manage the JBoss Portal</listitem>
- <listitem>Add a new portlet to the JBoss Portal</listitem>
- </itemizedlist>
- </para>
+
+ <para>Welcome to the JBoss Portal Quickstart tutorial. In this tutorial, you
+ will: <itemizedlist>
+ <listitem>
+ Download and unzip the JBoss Portal bundle
+ </listitem>
+
+ <listitem>
+ Execute the JBoss Portal
+ </listitem>
+
+ <listitem>
+ Interact with the default portal
+ </listitem>
+
+ <listitem>
+ Create and edit content in the JBoss Portal
+ </listitem>
+
+ <listitem>
+ Manage the JBoss Portal
+ </listitem>
+
+ <listitem>
+ Add a new portlet to the JBoss Portal
+ </listitem>
+ </itemizedlist></para>
+
<para>Before we get started, a couple of notes about this tutorial:
<itemizedlist>
- <listitem>For those that are not familiar with portals or portlets, please start with this article on portals:
- <ulink url="http://java.sys-con.com/read/131819.htm">http://java.sys-con.com/read/131819.htm</ulink>
+ <listitem>
+ For those that are not familiar with portals or portlets, please start with this article on portals:
+
+ <ulink
+ url="http://java.sys-con.com/read/131819.htm">http://java.sys-con.com/read/131819.htm</ulink>
+
+
+ </listitem>
+
+ <listitem>
+ This guide is not intended to show all of the features of JBoss Portal. The intention is to show how to use the basic functionality of JBoss Portal. There is also a user guide and reference guide that will assist you with further use of JBoss Portal.
+ </listitem>
+
+ <listitem>
+ This guide was created with JBoss Portal 2.4. 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.
</listitem>
- <listitem>This guide is not intended to show all of the features of JBoss Portal. The intention is to show how
- to use the basic functionality of JBoss Portal. At the bottom of this guide is a list of resources that will
- assist you with further use of JBoss Portal.</listitem>
- <listitem>This guide was created with JBoss Portal 2.4. 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 to download the tarball instead of the zipfile and use forward slashes instead of
- backslashes, etc.</listitem>
- </itemizedlist>
- </para>
+ </itemizedlist></para>
</chapter>
\ No newline at end of file
1.3 +101 -84 jboss-portal-docs/quickstart-user/en/modules/installation.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: installation.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-portal-docs/quickstart-user/en/modules/installation.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- installation.xml 26 Jun 2006 18:14:53 -0000 1.2
+++ installation.xml 18 Jul 2006 16:16:08 -0000 1.3
@@ -3,85 +3,102 @@
<chapterinfo>
<author>
<firstname>Kevin</firstname>
+
<surname>Barfield</surname>
- <email>kevin.barfield at jboss.org</email>
+
+ <email>kevin.barfield at jboss.com</email>
</author>
</chapterinfo>
+
<title>Installation</title>
+
<sect1>
<title>Downloading and Installing</title>
- <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 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://java.sun.com/j2se/1.4.2/download.html</ulink>
- 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/JBoss Portal/downloads">http://www.jboss.com/products/JBoss
- Portal/downloads</ulink>
- . 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://sourceforge.net/projects/sevenzip/">http://sourceforge.net/projects/sevenzip</ulink>
- ).
- Once you have unzipped it, you should have a directory structure with the following folders under,
- jboss-portal-2.4-bundled:
- <itemizedlist>
+
+ <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
+ 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://java.sun.com/j2se/1.4.2/download.html</ulink>
+ 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/JBoss Portal/downloads">http://labs.jboss.com/portal/jbossportal/download</ulink>
+ . 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://sourceforge.net/projects/sevenzip/">http://sourceforge.net/projects/sevenzip</ulink>
+ ). Once you have unzipped it, you should have a directory structure with
+ the following folders under, jboss-portal-2.4-bundled: <itemizedlist>
<listitem>
+
+
<emphasis role="bold">bin</emphasis>
+
- Contains the startup/shutdown commands for the JBoss Portal
</listitem>
+
<listitem>
+
+
<emphasis role="bold">client</emphasis>
+
- Contains client libraries
</listitem>
+
<listitem>
+
+
<emphasis role="bold">docs</emphasis>
+
- Contains documentation for the JBoss Portal
</listitem>
+
<listitem>
+
+
<emphasis role="bold">lib</emphasis>
+
- Contains libraries
</listitem>
+
<listitem>
+
+
<emphasis role="bold">server</emphasis>
- - Contains server configuration and the Portal.sar file
+
+ - Contains JBoss Application Server configuration and the Portal.sar file
</listitem>
- </itemizedlist>
- </para>
+ </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.bat. A command
+ window should come up with the Portal console (Figure 1). <mediaobject>
<imageobject>
- <imagedata fileref="images/image001.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image001.png" format="png"
+ valign="middle" />
</imageobject>
- <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.</note>
- </para>
- <para>
- Now, bring up Internet Explorer and go to the following URL:
- <ulink url="http://localhost:8080/portal">http://localhost:8080/portal</ulink>
- . You should see the default page for JBoss Portal (Figure 2).
- <mediaobject>
+
+ <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.
+ </note></para>
+
+ <para>Now, bring up Internet Explorer and go to the following URL: <ulink
+ url="http://localhost:8080/portal">http://localhost:8080/portal</ulink> .
+ You should see the default page for JBoss Portal (Figure 2). <mediaobject>
<imageobject>
- <imagedata fileref="images/image003.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image002.jpg" format="JPG"
+ scale="" valign="middle" />
</imageobject>
- <caption>
- <para>Figure 2. Default page for the JBoss Portal.</para>
- </caption>
- </mediaobject>
- </para>
+
+ <caption><para>Figure 2. Default page for the JBoss
+ Portal.</para></caption>
+ </mediaobject></para>
</sect1>
</chapter>
\ No newline at end of file
1.3 +358 -170 jboss-portal-docs/quickstart-user/en/modules/interaction.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: interaction.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-portal-docs/quickstart-user/en/modules/interaction.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- interaction.xml 28 Jun 2006 14:17:44 -0000 1.2
+++ interaction.xml 18 Jul 2006 16:16:08 -0000 1.3
@@ -3,424 +3,612 @@
<chapterinfo>
<author>
<firstname>Kevin</firstname>
+
<surname>Barfield</surname>
- <email>kevin.barfield at jboss.org</email>
+
+ <email>kevin.barfield at jboss.com</email>
</author>
</chapterinfo>
+
<title>Interaction with the Portal</title>
+
<sect1>
<title>Window States</title>
- <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 "Select a Portal Theme" portlet. The portlet
- is then minimized (Figure 5):
+
+ <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 "Select a Portal Theme" portlet. The portlet is
+ then minimized (Figure 5):
<mediaobject>
<imageobject>
- <imagedata fileref="images/image009.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image075.jpg" format="JPG"
+ scalefit="yes" valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 5. Default page with portlet minimized.</para>
+ <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 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 fileref="images/image011.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image076.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 6. Portal with portlet maximized.</para>
+ <para>Figure 6. Portal with portlet
+ maximized.</para>
</caption>
</mediaobject>
</para>
</sect1>
+
<sect1>
<title>User Creation</title>
- <para>
- Let's create a user for the portal. Click on the "create one" 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 "create new user", the default view will show (Figure 11).
+
+ <para>Let's create a user for the portal. Click on the "create one" 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 "create new user", the default view will show (Figure
+ 11).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image018.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image077.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 10. The Create user view in the user portlet.</para>
+ <para>Figure 10. The Create user view in the user
+ portlet.</para>
</caption>
</mediaobject>
<mediaobject>
<imageobject>
- <imagedata fileref="images/image020.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image078.jpg" format="png"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 11. The default view in the user portlet maximized.</para>
+ <para>Figure 11. The default view in the user portlet
+ maximized.</para>
</caption>
</mediaobject>
</para>
</sect1>
+
<sect1>
<title>Administrator Login</title>
- <para>
- Click on the resize button to make the user portlet shrink back to normal size. Now, click "Standard login".
- The login page will show (Figure 12). Log in with username and password of "admin"
+
+ <para>Click on the resize button to make the user portlet shrink back to
+ normal size. Now, click "Standard login". The login page will show (Figure
+ 12). Log in with username and password of "admin"
<mediaobject>
<imageobject>
- <imagedata fileref="images/image022.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image079.jpg" format="png"
+ valign="middle"/>
</imageobject>
+
<caption>
<para>Figure 12. Portal login page.</para>
</caption>
</mediaobject>
- Click "Login", and the portal will now show us the portlets and portal pages for the administrator (Figure 13).
+ Click "Login", and the portal will now show us the
+ portlets and portal pages for the administrator (Figure 13).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image024.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image080.jpg" format="png"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 13. default portal page for administrator.</para>
+ <para>Figure 13. default portal page for
+ administrator.</para>
</caption>
</mediaobject>
</para>
</sect1>
+
<sect1>
<title>Content Management</title>
- <para>
- There is a portal page available now for the content management. Click on the "CMS Manager" tab. The CMS
- Manager portal page displays(Figure 14).
+
+ <para>Now that we are logged in, there is a portal page available for the
+ content management and portal administration. Click on the "Admin" tab.
+ The Admin portal page displays(Figure 14).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image026.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image081.jpg" format="png"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 14. CMS Manager portal page.</para>
+ <para>Figure 14. 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. Click on the upload archive file icon on the
- page. The upload archive view shows (Figure 15).
+ 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. Click on the upload archive file icon on the page. The
+ upload archive view shows (Figure 15).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image028.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image082.jpg" format="png"
+ valign="middle"/>
</imageobject>
+
<caption>
<para>Figure 15. Upload Archive view.</para>
</caption>
</mediaobject>
- <note>Please use the docs.zip located at (TODO) for the batch upload.</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).
+ <note>
+ Please use the quickstart.zip for the batch upload. You may also download it from
+ <ulink url="http://docs.jboss.org/jbportal/v2.4/quickstartuser/en/quickstart.zip">here</ulink>
+ .
+ </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 fileref="images/image030.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image011.jpg"
+ format="JPEG" valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 16. Choose file to batch upload.</para>
+ <para>Figure 16. Choose file to batch
+ upload.</para>
</caption>
</mediaobject>
- Click on the docs.zip that you downloaded earlier(see note above) and select "Open". The docs.zip will be
- uploaded into the content repository, and the files and directories will now appear in the content management
- structure (see the new docs directory in Figure 17).
+ 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 fileref="images/image032.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image012.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 17. New docs directory shows in content management repository.</para>
+ <para>Figure 17. New quickstart directory shows in content
+ management repository.</para>
</caption>
</mediaobject>
- 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 18).
+ </para>
+
+ <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>
+
+ <para>
<mediaobject>
<imageobject>
- <imagedata fileref="images/image032.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image013.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 18. Default directory listing.</para>
+ <para>Figure 18. HTML files and sub-directories that were
+ uploaded intoquickstart directory shows in content management
+ repository.</para>
</caption>
</mediaobject>
- Click on the index.html link. The file browser will show the versions of this file (Figure 19).
+ </para>
+
+ <para></para>
+
+ <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 fileref="images/image034.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image014.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 19. Version view for index.html.</para>
+ <para>Figure 19. Default directory listing.</para>
</caption>
</mediaobject>
- To edit this HTML file, click on the edit icon. The WYSIWYG editor view will appear (Figures 20 and 21). Note:
- The WYSIWYG editor is dependent on browser. Some browsers show a box to enter HTML.
+ Click on the index.html link. The file browser will show
+ the versions of this file (Figure 20).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image036.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image015.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 20. Content editor view (top).</para>
+ <para>Figure 20. Version view for
+ index.html.</para>
</caption>
</mediaobject>
+ To edit this HTML file, click on the edit icon. 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 fileref="images/image038.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image016.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 21. Content editor view (bottom).</para>
+ <para>Figure 21. Content editor view (top).</para>
</caption>
</mediaobject>
- 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 lighning bolt from "Project Information" to "Portal Documentation" and delete the following
- text below that "project, on-going development, open issues, and our vibrant user and developer communities".
- The updated text is in Figure 22.
<mediaobject>
<imageobject>
- <imagedata fileref="images/image042.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image017.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 22. Updated text in HTML page.</para>
+ <para>Figure 22. Content editor view
+ (bottom).</para>
</caption>
</mediaobject>
- Now let's update the link to point to the index.html page in the docs 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 "docs/index.html" (Figure 23).
+ </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 Figures 23 and 24.
<mediaobject>
<imageobject>
- <imagedata fileref="images/image044.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image018.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 23. Insert/edit link window with updated link URL</para>
+ <para>Figure 23. Updated heading text in HTML
+ page.</para>
</caption>
</mediaobject>
- Click Insert to save the updated link. Click Create to create the new version of the HTML file. The file
- browser view shows again with the new 1.1 version shown (Figure 24). The star icon next to the version number
- shows this is the live version.
<mediaobject>
<imageobject>
- <imagedata fileref="images/image046.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image019.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 24. File browser with new version of index.html.</para>
+ <para>Figure 24. Updated heading text in HTML
+ page.</para>
</caption>
</mediaobject>
- Click on the default portal page to see the changes we have made. The content view portlet shows the update
- page for the portal documentation (Figure 25).
+ </para>
+ <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 fileref="images/image048.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image021.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 25. Content view portlet with the updated default page.</para>
+ <para>Figure 25. Insert/edit link window with updated link
+ URL</para>
</caption>
</mediaobject>
- Click on the "Click here" link that was updated to go to the new uploaded content (Figure 26).
+ Click Insert to save the updated link. Click Create 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 fileref="images/image050.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image022.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 26. Content view portlet with docs page shown.</para>
+ <para>Figure 26. File browser with new version of
+ index.html.</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>
- <sect1>
- <title>Portal Management</title>
- <para>Click on the management portal page. The user, role, catalog, and management portlets are on this portal
- page (Figure 27).
+ Click on the default portal page to see the changes we
+ have made. The content view portlet shows the update page for the portal
+ documentation (Figure 27).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image052.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image023.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 27. Management portal page.</para>
+ <para>Figure 27. Content view portlet with the updated
+ default page.</para>
</caption>
</mediaobject>
- First, let's add a new role. Click on the "Create new role" link. The role management view is displayed (Figure
- 28).
+ Click on the "Click here" link that was updated to go to
+ the new uploaded content (Figure 28).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image054.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image024.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 28. Role management portlet with create user role view.</para>
+ <para>Figure 28. Content view portlet with docs page
+ shown.</para>
</caption>
</mediaobject>
- Fill in "starter" as both the role name and the display name and select the "Create user role" button. This
- returns you to the management portal page. Click on the "List of all the users" link to see the users in the
- portal (Figure 29).
+ 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>
+
+ <sect1>
+ <title>Portal Management</title>
+
+ <para>Click on the Admin portal page. The user, role, catalog, CMS Admin,
+ and management portlets are on this portal page (Figure 29).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image056.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image012.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 29. User portlet with user list view.</para>
+ <para>Figure 29. Admin portal page.</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 30).
+ Click on the "List of all the users" link to see the users
+ in the portal (Figure 30).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image058.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image084.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 30. User portlet with available roles view.</para>
+ <para>Figure 30. User portlet with user list
+ view.</para>
</caption>
</mediaobject>
- Select the starter role and click the "Assign roles" button. This brings us back to the User portlet menu view
+ 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 fileref="images/image060.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image085.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 31. User portlet menu view.</para>
+ <para>Figure 31. User portlet with available roles
+ view.</para>
</caption>
</mediaobject>
- Now let's look at the user profile for the starter user. Click on the "List of all users" link, then the
- "Profile" link next to the starter user. The user profile view appears (Figure 32).
+ Select the Administrators role and click the "Assign
+ roles" button. This brings us back to the User portlet menu view (Figure
+ 32).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image062.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image086.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 32. User profile view.</para>
+ <para>Figure 32. User portlet menu 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 User portlet menu view is displayed again. Click on the default size icon to go back
- to the management portal page default view (Figure 33).
+ Now let's look at the user profile for the starter user.
+ Click on the "List of all users" link, then the "Profile" link next to the
+ starter user. The user profile view appears (Figure 33).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image064.jpg" format="jpg" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image087.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 33. Management portal page default view.</para>
+ <para>Figure 33. User profile view.</para>
</caption>
</mediaobject>
- Now, let's explore the management portlet. This portlet shows a tree view of the portals, portal pages, and
- portlet instances. Click on the "+" icon next to root, then the "+" icon next to default, and finally the "+"
- icon next to management. This shows us that there is a default portal with four portal pages defined. In
- addition, we can see the five portlet instances (including navigation) that are used in the management portal
- page (Figure 34).
+ This shows all of the fields available in the user
+ profile. Enter the first name of "starter" and click the "Save changes"
+ button. The User portlet menu view is displayed again. Click on the
+ default size icon to go back to the Admin portal page default view (Figure
+ 34).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image065.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image012.jpg" format="jpg"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 34. Management portlet with tree expanded.</para>
+ <para>Figure 34. Management portal page default
+ 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 The page now shows the role portlet above the user portlet on the page (Figure 35).
+ Now, let's explore the management portlet. This portlet
+ shows a tree view of the portals, portal pages, and portlet instances.
+ Click on the "+" icon next to root, then the "+" icon next to default, and
+ finally the "+" icon next to Admin. This shows us that there is a default
+ portal with four portal pages defined. In addition, we can see the six
+ portlet instances (including navigation) that are used in the management
+ portal page (Figure 35).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image067.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image088.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 35. Role portlet is moved on the management portlet page.</para>
+ <para>Figure 35. Management portlet with tree
+ expanded.</para>
</caption>
</mediaobject>
- Let's create a new portal page. Click on the "default" portal link. The add portal page view is shown (Figure
- 36).
+ 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 The page now shows the role portlet above the user
+ portlet on the page (Figure 36).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image069.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image089.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 36. Management portlet add page view.</para>
+ <para>Figure 36. Role portlet is moved on the management
+ portlet page.</para>
</caption>
</mediaobject>
- Enter "Starter" as the page name and click the "Add page" button. We now see the Starter tab at the top and
- Starter as a portal page in the list of portal pages (Figure 37).
+ Let's create a new portal page. Click on the "default"
+ portal link. The add portal page view is shown (Figure 37).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image071.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image090.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 37. Starter portal page has been added.</para>
+ <para>Figure 37. Management portlet add page
+ view.</para>
</caption>
</mediaobject>
- Now let's add some portlet instances to the portal page. Click on the starter page in the management portlet,
- and the details for that portal page are shown (Figure 38).
+ Enter "Starter" as the page name and click the "Add page"
+ button. We now see the Starter tab at the top and Starter as a portal page
+ in the list of portal pages (Figure 38).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image073.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image091.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 38. Management portlet for Starter portal page.</para>
+ <para>Figure 38. Starter portal page has been
+ added.</para>
</caption>
</mediaobject>
- First, let's add a navigation portlet. Choose the navigation portlet instance from the dropdown (Figure 39).
+ Now let's add some portlet instances to the portal page.
+ Click on the starter page in the management portlet, and the details for
+ that portal page are shown (Figure 39).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image075.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image092.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 39. Choosing the Navigation portlet instance from the dropdown.</para>
+ <para>Figure 39. Management portlet for Starter portal
+ page.</para>
</caption>
</mediaobject>
- Type in the name you want to give this portlet instance ("nav") and click the "Add instance" button under
- navigation. The "nav" portlet instance is now shown under navigation (Figure 40).
+ First, let's add a navigation portlet. Choose the
+ navigation portlet instance from the dropdown (Figure 40).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image077.png" format="png" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image093.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 40. Nav portlet instance is added.</para>
+ <para>Figure 40. Choosing the Navigation portlet instance
+ from the dropdown.</para>
</caption>
</mediaobject>
- Click on the "nav" link to go into the details for that portlet instance (Figure 41)
+ Type in the name you want to give this portlet instance
+ ("nav") and click the "Add navigation" button. The "nav" portlet instance
+ is now shown under navigation (Figure 41).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image079.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image094.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 41. Details for the nav portlet instance.</para>
+ <para>Figure 41. Nav portlet instance is
+ added.</para>
</caption>
</mediaobject>
- Click on the "Theme" link to update the theme for this portlet. Since this is a navigation portlet, let's set
- the Window Renderer, Decoration Renderer, and Portlet Renderer to "emptyRenderer" (Figure 42).
+ Click on the "nav" link to go into the details for that
+ portlet instance (Figure 42)
<mediaobject>
<imageobject>
- <imagedata fileref="images/image081.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image095.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 42. Theme details for the nav portlet instance.</para>
+ <para>Figure 42. Details for the nav portlet
+ instance.</para>
</caption>
</mediaobject>
- Click the "Update" button, then click the Starter portal page in the management portlet to continue adding
- portlets to the Starter portal page. Select the CatalogPortletInstance from the portlet instance list, enter a
- name of "catalog", and click the "Add instance" button under the "left" column. Select the
- DefaultCMSPortletInstance from the portlet instance list, enter a name of "default CMS", and click the "Add
- instance" button under the "center" column. See Figure 43 for the updated detail of the Starter portal page.
+ Click on the "Theme" link to update the theme for this
+ portlet. Since this is a navigation portlet and it doesn't need portlet
+ decorations, let's set the Window Renderer, Decoration Renderer, and
+ Portlet Renderer to "emptyRenderer" (Figure 43).
<mediaobject>
<imageobject>
- <imagedata fileref="images/image083.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image096.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 43. Starter page detail with portlet instances added.</para>
+ <para>Figure 43. Theme details for the nav 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 44).
+ Click the "Update" button, then click the Starter portal
+ page in the management portlet to continue adding portlets to the Starter
+ portal page. Select the CatalogPortletInstance from the portlet instance
+ list, enter a name of "catalog", and click the "Add left" button. Select
+ the CMSPortletInstance from the portlet instance list, enter a name of
+ "CMS", and click the "Add center" button. See Figure 44 for the updated
+ detail of the Starter portal page.
<mediaobject>
<imageobject>
- <imagedata fileref="images/image083.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image097.jpg" format="JPG"
+ valign="middle"/>
</imageobject>
+
<caption>
- <para>Figure 44. Security for the Starter portal page.</para>
+ <para>Figure 44. Starter page detail with portlet instances
+ added.</para>
</caption>
</mediaobject>
- We can see the new starter role that we created. Let's take a look at the Starter portal page we created. Click
- on the "Starter" tab at the top to go to the Starter portal page (Figure 45).
+ 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 fileref="images/image083.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image098.jpg" format="JPG"
+ 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 "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 45. The Starter portal page.</para>
+ <para>Figure 46. The Starter portal page.</para>
</caption>
</mediaobject>
</para>
1.2 +80 -57 jboss-portal-docs/quickstart-user/en/modules/portalterminology.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: portalterminology.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-portal-docs/quickstart-user/en/modules/portalterminology.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- portalterminology.xml 26 Jun 2006 19:00:07 -0000 1.1
+++ portalterminology.xml 18 Jul 2006 16:16:08 -0000 1.2
@@ -3,58 +3,81 @@
<chapterinfo>
<author>
<firstname>Kevin</firstname>
+
<surname>Barfield</surname>
- <email>kevin.barfield at jboss.org</email>
+
+ <email>kevin.barfield at jboss.com</email>
</author>
</chapterinfo>
+
<title>Portal Terminology</title>
- <para>JBoss Portal is made up of portals, portal containers, portal pages, and portlets. What are these things? Here
- are some definitions:
+
+ <para>JBoss Portal is made up of portals, portal containers, portal pages,
+ and portlets. What are these things? Here are some definitions:
<itemizedlist>
<listitem>
+
+
<emphasis role="bold">Portal:</emphasis>
+
Hosts the presentation layer for personalization, single sign on and content aggregation.
</listitem>
+
<listitem>
+
+
<emphasis role="bold">Portlet Container:</emphasis>
+
A Portal can host multiple portlet containers and each portlet container has its own runtime environment.
</listitem>
+
<listitem>
- <emphasis role="bold">Portlet Page:</emphasis>
+
+
+ <emphasis role="bold">Portal Page:</emphasis>
+
Aggregation of portlets, organized and displayed on a single page.
</listitem>
+
<listitem>
+
+
<emphasis role="bold">Portlet:</emphasis>
- A portlet is a Java technology based web component, managed by a portlet container, that processes requests
- and generates dynamic content.
+
+ A portlet is a Java technology based web component, managed by a portlet container, that processes requests and generates dynamic content.
</listitem>
+
<listitem>
+
+
<emphasis role="bold">Portlet Instance:</emphasis>
+
A portlet instance can be placed on multiple pages and will show the same state.
</listitem>
- </itemizedlist>
- <mediaobject>
+ </itemizedlist> <mediaobject>
<imageobject>
- <imagedata fileref="images/image005.jpg" format="jpg" align="center" valign="middle"/>
+ <imagedata align="center" fileref="images/image005.jpg" format="jpg"
+ valign="middle" />
</imageobject>
- <caption>
- <para>Figure 3. Portal Definition Diagram.</para>
- </caption>
- </mediaobject>
- </para>
- <para>Now let's look at that default portal page again with these terms in mind (Figure 4).
- <mediaobject>
+
+ <caption><para>Figure 3. Portal Definition Diagram.</para></caption>
+ </mediaobject></para>
+
+ <para>Now let's look at that default portal page again with these terms in
+ mind (Figure 4). <mediaobject>
<imageobject>
- <imagedata fileref="images/image009.png" format="png" align="center" valign="middle"/>
+ <imagedata align="left" fileref="images/image006.jpg" format="JPG"
+ 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 two portal pages, and the default portal page has five
- portlets on it (navigation, user, portal pages, portal theme, 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>
+
+ <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>
</chapter>
\ No newline at end of file
More information about the jboss-cvs-commits
mailing list