Portal Presention

Jaya Prakash M...

Portal Session Agenda
What is a Portal
Goal of Portal
Properties of portals
Benefits to the user s and Companies.
Portal features
Why the portal so popular
Portal types
Various elements of portal page .
Portal Framework
Portal Architecture
Portal Life Cycle
Portal Server & Portlet Container
What is Portlet
Portlet Lifecycle
Interfaces And Classes Summary
Portlet Modes & Window States
Comparison Of Portlet with Servlet.
JSR(JAVA SPECIFICATION REQUEST) 168 Portlets
Examples on Weblogic WorkShop

What is Portal
A portal represents a web site that provides a single point of access to applications and information.
A portal is a unified gateway to several dynamic information sources .
End User Perspective:-
A portal is a web site with pages that are organized by tabs or some other form of navigation. Users can also customize their view of a portal by adding their own pages, adding portlets of their choosing, and changing the Look And Feel of the interface.

What is Portal
Technical Perspective:-
A portal is a container of resources and functionality that can be made available to end users. A portal presents diverse content and applications to users through a consistent, unified web-based interface. Portal administrators and users can customize portals, and content can be presented based on user preferences or rule-based personalization. Each portal is associated with a web application that contains all of the resources required to run portals on the web.
Portlet Specification:-
A portal is a web application that commonly provides personalization, single sign on, content aggregation from different sources, and hosts the presentation layer of information systems.

Goal & Properties Of Portal
Goal Of Portal:-
The ultimate goal of any portal implementation is to provide users with access to the systems and information they need to do their jobs more productively.
Properties of portals:-
Look and feel
Consistent headers and footers, color schemes, icons and logos which gives the user a feel and sense of consistency and uniformity.
Ease of navigation

Logical View Of Portal

Benefits to users and Companies
Benefits to users:-
Aggregation - The user can go to a single place for all content and applications.
Customization - The preferences for a user determine how the portal looks and feels.
Personalization - The user can obtain content that is specific to their interests and needs.
Organization - The user can arrange the content and applications to make better sense of the information.
Integration - The user can work with multiple applications and content sources in a unified fashion.

Benefits to users and Companies
Benefits to Companies :-
Modern software is complex and expensive, which has motivated many companies to invest in enterprise portals as a mechanism by which they can manage information in a cohesive and structured fashion.
Portals provide a single point of entry for employees, partners, and customers.
Portals are highly flexible; they can exist in the form of intra-nets, inter-nets.
Rapid, easy modification and maintenance of the website.
* Time shown with out day light savings

Features Provided by Portals
Features:-
Search - Enterprise and web-based search facilities
Content Management - Creation, management, and delivery of content
Content Repurposing - Including content from multiple disparate data sources
Portals optionally include the following features and benefits:
Single Sign-On - Allows users to log on once for all applications within the portal

Why the portals are so hot in the Industry?
The portal is a complete environment for managing and integrating a large number diverse applications.
A single administrative interface makes it possible to manage users, applications, content, look, feel and navigation of an entire website. Centralized administration of a huge web based infrastructure is probably the most compelling reason for adopting the portal.
A portal on the other hand builds heavily upon the dynamic nature of a normal website. Furthermore, a portal has built in user functions, and the ability for the user to customize their own experience.

Portal Types
1)Horizantal Portals
2)Vertical Portals
Some Portals
Sportal (sports portal ) Voice portals Mini portals Investment portals Environmental portals Entertainment portals Domain specific portals Corporate web portals Government web portals Regional web portals

Example Portal Page

Various elements of portal page

Portal Architecture
NO Single “Industry Standard” architectural framework for Portals.
Following Minimum Functionality Must Include:-
1)Interface To web.
2)User Interface Management
(Presentation Services)
3)External Data Access Mechanisms
4)Data Management Services
5)Security, authentication and Personalization
6)Portal Development Tools
7)Portal Administration and Management Tools

Basic Portal Architecture

Architectural Flow

Portal Life Cycle
The creation and management of a portal flows through a portal life cycle. The portal life cycle contains four phases:
Architecture
Development
Staging
Production

Portal Life Cycle
Architecture:-
During the architecture phase, you design and plan the configuration of your portal.
you can create a detailed specification outlining the requirements for your portal, the specific portlets you require, where those portlets will be hosted, and how they will communicate and interact with one another. You might also consider the deployment strategy for your portal. Security is another consideration for the portal architect.

Portal Lifecycle
Development:-
Developers used to create portals, portlets, pages, and books. During development, you can implement data transfer and interportlet communication strategies and consider the security of the components.
Staging:-
staging environment where it can be assembled and tested before going live. You also test your portal in a staging environment before propagating it to a live production system. In the testing aspect of the staging phase, there is tight iteration between staging and development until the application is ready to be released.

Portal Lifecycle
Production:-
A production portal is live and available to end users. A portal in production can be modified by administrators and users. For instance, an administrator might add additional portlets to a portal or reconfigure the contents of a portal.

Portal Server
Portal server aggregates portlet Markup for display.
Features:-
personalization
single sign-on
Content aggregator
security: users, groups, roles
portlet admin: deploy, undeploy capabilities
page layouts

Portal Server
Personalization:-
The basic implementation of personalization service allows a user to customize her page in two ways. First, the user can decide what colors she wants for title bars and what icons she wants for controls. Second, the user can decide which portlets she wants on her page.
Single Sign On:-
Allows you to get access to all other applications once you log into the portal server, meaning you don't have to log into every application separately.
Content aggregator:-
Aggregate content generated by various portlet applications

Portlet Container
A portlet container is very similar to a servlet container , in that every portlet is deployed inside a portlet container that controls the life cycle of the portlet and provides it with necessary resources and information about its environment. A portlet container is responsible for initializing and destroying portlets and also for passing user requests to it and collecting responses .

Portlal Server & Portlet Container

What is Portlet
Portlets are web components--like servlets--specifically designed to be aggregated in the context of a composite page.
The Portlet specification defines a portlet as a "Java-technology-based web component, managed by a portlet container that processes requests and generates dynamic content.
On the technical side, a portlet is a class that implements the javax.portlet.Portlet interface and is packaged and deployed as a .war file inside of a portlet container.

Portlet interface
package javax.portlet;
Public interface Portlet {
void init (PortletConfig config);
void processAction (ActionRequest req, ActionResponse res);
void render (RenderRequest req, RenderResponse res);
void destroy ();
}

Portlet Lifecycle

Portlet Interface Methods :-
Request Processing
processAction() -- Action Requests
render()------Render Requests
Lifecycle Management
init()
destroy()

Interfaces Summary

Diagramatic Representation Of Portlet,PortletConfig and PortletContext interfaces in PortletContainer

PortletConfig & PortletContext
PortletConfig:-
The configuration holds information about the portlet that is valid for all users.”
One per portlet definition
Portlet init parameters
Title & keywords (ResourceBundle)
PortletContext:-
The PortletContext interface defines a portlet’s view of the portlet application within which the portlet is running.”
One instance per portlet app.
Context Init Parameters
Request Dispatching
Use context attributes to share information between your portlets and servlets/JSPs in the same web application.

Classes Summary

Generic Portlet , PortletMode & WindowState
GenericPortlet:-
doView(...)
doEdit(...)
doHelp(...)
PortletMode :-
EDIT
VIEW
HELP
WindowState:-
MAXIMIZED
MINIMIZED
NORMAL

Portlets similarities and Differences to servlets
Portlets are similar to servlets, in that:
Portlets are managed by a specialized container.
Portlets generate dynamic content.
A portlet's life cycle is managed by the container.
Portlets interact with web client via a request/response paradigm.
Portlets are different from servlets, in that:
Portlets only generate markup fragments, not complete documents.
Portlets are not directly URL addressable. You cant send somebody URL of a portlet. You can send him the URL of the page containing a portlet.
Portlets cannot generate arbitrary content, since the content generated by a portlet is going to be part of portal page. If a portal server is asking for html/text, then all portlets should generate text/html content. On the other hand, if the portal server is asking for WML, then each portlet should generate WML content.

Additional functionality Of Portlets On Servlets
Persistent storage for preferences
Request processing
Portlet modes
Window state
User information

Portlet Types Business logic and presentation layer can get combined in JSPs . Not well suited for advanced portlet navigation Simple to implement and deploy . Provides basic functionality without a lot of complexity . JSP or HTML based portlets . Cons Pros Portlet Types

Portlet Types Advanced Pageflow features not necessary for static or simple, one view portlets Allow you to separate t he user interface code from navigation control and other business logic Provides the ability to model both simple and advanced portlet navigation Provides a visual environment to build rich applications based on Struts Java Page Flow based portlets Cons Pros Portlet Types

Portlet Types Does not leverage BEA advanced portlet features i.e. generating our own skins, Automatic export/ import of custom content, dumping registries.. etc. Requires deeper understanding of J2EE programming model Accommodate portability for portlets across platforms Does not require use of portal server specific JSP tags Behavior is similar to a Servlet JSR 168 based portlets Cons Pros Portlet Types

JSR(JAVA SPECIFICATION REQUEST) 168 Portlets
JSR 168 defines a standard Java portlet API,
(i.e JSR 168 Portlet is nothing but the contract between the API and the container .)
Portal Server Vendors:-
Sun(IPlanet)
Oracle , IBM(IBM Portlet)
Vignette , SAP , Sybase
TIBCO, Plumtree(Gadgets) and
BEA

Why JSR 168 Portlets entered in to the market
In the pre-JSR 168 days, you had to develop and maintain a separate version of your portlet that complied with the vendor-specific portlet API for each and every vendor portal.
Disadvantages:-
Time-consuming
Cumbersome
JSR 168 brought a world of a difference: By adhering to the standards , you can build portlets that can run in portals, irrespective of their vendors.

What are the portlet Specifications

JSR 168 provides three modes for portlet interactions:
VIEW -- This mode, a mandatory one that's defined by a portlet, renders markup fragments.
EDIT -- This optional mode enables changes to per-user settings to customize rendering.
HELP -- This optional mode displays help information.

Window States:-
Window state indicates the amount of portal page space that will be assigned to a portlet. The portlet can use this information to decide how much information to render.
Three window states—
Normal
Maximized and
Minimized.

Portlet Preferences
PreferencesValidator
Security:
In the portlet deployment descriptor, a flag can be set to restrict the portlet to running only over HTTPS. This appropriate for portlets that contain confidential information that should be encrypted when sent over the network.

Questions

Portal Presention

by JayaPrakash.m on Dec 26, 2008

Accessibility

Upload Details

Usage Rights

2 Embeds 6

Statistics

Portal Presention Presentation Transcript

http://www.slideshare.net	3
http://static.slidesharecdn.com	3