How to Troubleshoot Apps for the Modern Connected Worker
Jetspeed-2 Overview
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18. Pluggable Components and Jetspeed API LDAP User Manager Jetspeed API User Manager Role Manager Component Implementations RDBMS User Manager Custom User Manager
19. Component API Bus Jetspeed API User Manager Statistics Portlet Registry Page Manager SSO Aggregator Component Implementations
45. Pipeline Valves (continued) Uses the Profiler, Site Manager, and Page Manager components to locate the requested page and menu ‘site’ navigations Profiler Valve Determines the targeted action window in the request, if found, executes the action via the portlet container. This is the standard “ action phase ”, blocking all rendering. At completion of the action phase, the action valve redirects back to the portal to process the render phase. Action Valve Builds the actions available on the page and all portlet windows Decorator Valve Executes the standard “ render phase ”, where the actual rendering of all portlets and page decorations occurs. Aggregator Valve
46. Pipeline Valves (Desktop) Renders the skeleton of the Jetspeed Desktop. All desktop portlet rendering is controlled on the client side, with javascript and the portlet pipeline Desktop Valve Executes Jetspeed Desktop actions over the span of one request. The client-side desktop controls the execution of the action phase, and then the subsequent render phases, achieving parallel processing from the client-side. Desktop Action Valve
47. Jetspeed Components: Core Engine Wrapper around Pluto Container to enable Spring configuration of Pluto DesktopPortletContainer Wrapper around Pluto Container to enable Spring configuration of Pluto PortletContainer The Pluto portlet container for the desktop (requires different action handling) DesktopPluto The Pluto portlet container Pluto Handles all access to portlet windows. Portlet windows are temporary objects representing a portlet and its preferences for a particular window or fragment PortletWindowAccessor The Jetspeed Engine (not configured in Spring. The Jetspeed bootstrap servlet adds the engine to the Spring container) Engine
48. Jetspeed Components: Core Engine Handles caching of PSML files Page File Cache Generates Unique Ids for pages and fragment IdGenerator The Jetspeed Power Tool factory Powertools Handles algorithms for locating language, country, media-type specific decorations DecorationLocator Handles algorithms for locating language, country, media-type specific Jetspeed web application templates (JSP, Velocity) TemplateLocator Wire in the Servlet configuration from the Jetspeed servlet webapp javax.servlet.ServletConfig Wire in global properties configuration from a file portal_configuration
49. Jetspeed Components: Core Engine Alternative property configuration for production systems ProductionConfiguration Allows components to participate in the creation of the <HEAD> markup, supplying scripts and CSS into the header area. (NOTE: a header phase will be added to the Portlet API 2.0 spec) HeaderResourceFactory Request Context Factory RequestContextComponent
50.
51. Aggregation Handles the “ render phase ” of the Portlet API, aggregating content of all portlets and decorations on a page PageAggregator Renders single portlets from all pipelines PortletRenderer Handles aggregation processing of single portlet requests from the portlet pipeline PortletAggregator
52. Ajax Actions AjaxChangeWindow AjaxGetPages AjaxGetPage List is growing, under development AjaxGetPortlets AjaxRequestService AjaxRemovePortlet AjaxGetMenu AjaxAddPortlet AjaxGetMenus AjaxMove*