Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Portal Site Management



Contact David Sean Taylor for more information or training.

Contact David Sean Taylor for more information or training.

taylor at apache.org



Total Views
Views on SlideShare
Embed Views



1 Embed 1

https://bb4.utc.edu 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Portal Site Management Portal Site Management Presentation Transcript

      • Site Management in
      • Jetspeed-2
      • Roger Ruttimann
    Jetspeed-2 Enterprise Portals
  • Overview
    • Site Structure
    • Folder, Menus, PSML and portlets
    • Using Site Manger
    • Demo
  • Site Structure
    • Pages in PSML format are stored in folders
    • Pages reference portlets and define security constraints, layouts, decorators for portlets.
    • Metadata in folders to define the display order
    • Detailed documentation in
      • http://portals.apache.org/jetspeed-2/guides/guide-psml.html
  • Folders
    • PSML and metadata files are organized in a folder structure
    Site Management <folder> <!-- folder description --> <title>Root Folder</title> <metadata name=&quot;title&quot; xml:lang=&quot;fr&quot;>Répertoire racine</metadata> <metadata name=&quot;title&quot; xml:lang=&quot;es&quot;>Carpeta raiz</metadata> <!-- order of documents in folder --> <document-order>Jetspeed2.link</document-order> <document-order>Jetspeed2Wiki.link</document-order> <document-order>apache_portals.link</document-order> <document-order>apache.link</document-order>
  • Menus
    • Menus can be defined for folders and pages
    <!-- portal site menus --> <menu name=&quot;page-navigations&quot;> <separator> <text>Top Pages</text> <metadata name=&quot;text&quot; xml:lang=&quot;fr&quot;>Page haut</metadata> <metadata name=&quot;text&quot; xml:lang=&quot;es&quot;>Páginas más populares</metadata> </separator> <options>/Administrative</options> <separator> <text>Profiled Pages</text> <metadata name=&quot;text&quot; xml:lang=&quot;es&quot;>Páginas del Perfil</metadata> </separator> <options regexp=&quot;true&quot;>/p[0-9][0-9][0-9].psml</options> <separator> <text>Non Java Pages</text> <metadata name=&quot;text&quot; xml:lang=&quot;es&quot;>Ejemplos sin java</metadata> </separator> <options>/non-java</options> </menu>
  • Security
    • Security constraint in each page
    <!-- security constraints --> <security-constraints> <security-constraints-ref>public-view</security-constraints-ref> </security-constraints>
  • Security Constraint Definitions
    • Global page.security file:
    • <security-constraints-def name=&quot; admin &quot;>
    • <security-constraint>
    • <roles>admin</roles>
    • <permissions>view, edit</permissions>
    • </security-constraint>
    • </security-constraints-def>
    • <global-security-constraints-ref> admin </global-security-constraints-ref>
  • PSML
    • Description of a page. Content can be defined in fragments.
    • Allows to define layouts, decorators, links, menus, metadata and portlets
    • By default PSML are persisted as files on the file system
    • Simple configuration change to persist the PSML to the database instead of the file system.
    Site Management
  • Use Database persistence for PSML pages
    • Running J2 in a clustered environment requires pages to be in a database.
    • Changing PageManger to use database:
      • Comment out Update the spring assembly page-manager.xml. Comment out CastorXmlPageManger section:
        • <bean id=&quot;org.apache.jetspeed.page.PageManager&quot;
        • name=&quot;pageManager&quot;
        • class=&quot;org.apache.jetspeed.page.psml.CastorXmlPageManager&quot;>
    Page Manger
  • Portlets
    • PSML pages reference portlets
    • Define decorators and positions of the portlets in the page
    Site Management <fragment id=&quot;100393&quot; type=&quot;layout&quot; name=&quot;jetspeed-layouts::VelocityOneColumn&quot;> <fragment id=&quot;100939&quot; type=&quot;portlet&quot; name=&quot;j2-admin::LocaleSelector&quot;> <property layout=&quot;OneColumn&quot; name=&quot;row&quot; value=&quot;0&quot;/> </fragment> <fragment id=&quot;100345&quot; type=&quot;layout&quot; name=&quot;jetspeed-layouts::VelocityTwoColumns&quot;> <property layout=&quot;OneColumn&quot; name=&quot;row&quot; value=&quot;1&quot;/> <property layout=&quot;TwoColumns&quot; name=&quot;sizes&quot; value=&quot;33%,66%&quot;/> <fragment id=&quot;100121&quot; type=&quot;portlet&quot; name=&quot;j2-admin::LoginPortlet&quot;> <property layout=&quot;TwoColumns&quot; name=&quot;row&quot; value=&quot;0&quot;/> <property layout=&quot;TwoColumns&quot; name=&quot;column&quot; value=&quot;0&quot;/> </fragment> <fragment id=&quot;100171&quot; type=&quot;portlet&quot; name=&quot;demo::UserInfoTest&quot;> <property layout=&quot;TwoColumns&quot; name=&quot;row&quot; value=&quot;0&quot;/> <property layout=&quot;TwoColumns&quot; name=&quot;column&quot; value=&quot;1&quot;/> </fragment> </fragment> </fragment>
  • Site Manager
    • Site Manager part of the admin portlets
    • Site Manger Portlet allows users to add and edit pages
    • Adding portlets need to go to the page and enter edit mode
    • Ongoing work for an Ajax based Customizer. Will include the page creation and the portlet configuration in one page.
    Site Management
  • Site Manager Portlet
  • Demo
    • The demo shows the following:
    • Create new page
    • Add portlets
    • Change layouts and configure portlets
    Site Management
  • Jetspeed Desktop
    • The Jetspeed desktop combines server-side Jetspeed AJAX services with client-side services. It is a key change to the way Jetspeed presents its data. With the Jetspeed portal, it’s a server-centric application, with all requests and user interaction going back to the server. The user experience is driven by the HTTP page paradigm.
    • The Jetspeed Desktop solution is a client-side solution. The user interface is controlled by the client-side:
    • Aggregation of portlets
    • Customization
    • With the Jetspeed Desktop, the server side does what it does best: handles the portal model, user information and persistence of state.
    Jetspeed Desktop
  • Jetspeed Desktop Aggregation
    • Each portlet makes its own HTTP request for its own content. The request delivers the content for only that one portlet. The portlet aggregation component is moved to the client side, making ‘AJAX’ requests for each portlet’s content on the page.
    • This may lead to an overall slightly slower response time for the first hit on a page due to the increased number of HTTP requests, but subsequent interaction is usually much more responsive.
    • The “portlet pipeline” is used to make the AJAX requests.
    Jetspeed Desktop
  • The Desktop today
    • The desktop is undergoing a lot of new development and changing just about everyday. Still early in development cycle…
    Jetspeed Desktop
  • Jetspeed Desktop Customization
    • Customization is well-suited for the Desktop solution. Customization should always be available, if you have secured access. The customization changes are persisted over the Jetspeed AJAX API to the server, but all client interaction such as drag and drop or best handled on the client-side. Here we right-click on the tab menu to get the portlet-selector:
    Jetspeed Desktop
  • Jetspeed Desktop Portlet Selector
    • The Jetspeed Desktop Portlet Selector supports drag and drop of portlets onto the desktop. The Portlet Selector is a light-weight popup window (not a real browser popup):
    Jetspeed Desktop
  • Desktop Drag and Drop
    • Dropping the portlet on the page (better suited for a demo…):
    Jetspeed Desktop
  • Moving and Resizing
    • Portlets can also be moved or resized (better suited for a demo…):
    Jetspeed Desktop
  • Themes
    • The desktop still uses PSML as its instructions for which portlets appear on the page. However, page and portlet decorators are no longer relevant on the desktop. Instead we use “ themes ”. There are currently 2 themes available (tigris, blue)
    Jetspeed Desktop
  • Desktop System Portlets
    • Portlet Selector – select then drag and drop portlets
    • My Portal (edit your view of the site) i.e. folders pages, links **
    • My Admin – same as My Portal, but manage the whole site **
    • Portlet Finder – like the Portlet Selector, allows you to search **
    • My Dashboards – alternative to Jetspeed standard menus **
    • My Desktop – manage your desktop, change themes, colour, skins **
    Jetspeed Desktop
  • Future Directions
    • We are exploring development of the system administrative portlets with client-side widgets and DOJO
    Jetspeed Desktop
  • Google Map Portlet Jetspeed Desktop