A Techno Blog, mainly about Java

Portlets with jetspeed 2

Jetspeed 2   : open source project for portlets. IBM Portal supports both the jetspeed and wps

June 24, 2005 Posted by | Portals | Leave a comment

MVC + Portlets


January 12, 2005 Posted by | Portals | Leave a comment

A well-behaved Jetspeed portlet

Java World

December 17, 2004 Posted by | Portals | Leave a comment



December 9, 2004 Posted by | Portals | Leave a comment

start Portal from linux

From the /opt/WebSphere/AppServer/bin directory:

root@ibm-orpheus bin]# ./ WebSphere_Portal

Then in a browser:


Admin console is here:


November 8, 2004 Posted by | Portals | Leave a comment

Hello World Portlet

From IBM:

WSAD Integration edition

First, this page has a link to the portal toolkit

Requirements: portlet-api.jar, wpsportlets.jar, wps.jar
Servlet functionality: j2ee.jar, dynacache.jar

javac -classpath %CLASSPATH%

import org.apache.jetspeed.portlet.*;
public class HelloWorld extends PortletAdapter {
public void init(PortletConfig portletConfig) throws UnavailableException
super.init( portletConfig );
public void doView( PortletRequest portletRequest, PortletResponse portletResponse )
throws PortletException, IOException
PrintWriter writer = portletResponse.getWriter();

Hello Portal World!


Developer Works On Portals

Portlet Redbook

October 11, 2004 Posted by | Portals | Leave a comment

Portlet Programming

This entry will document my learning on programming with Portlets. First link is an introduction on Portlets by two IBMers. Also, referenced is an article on Understanding the Portal Specification. The JSR168 spec and JavaPassion slides [1] [2].

Three main components:
portal (server): presentation layer, or an application which aggregates portlet applications together in a presentable format. Portals provide a secure, single point of interaction with diverse information, business processes, and people, personalized to a user’s needs and responsibilities. A portal server provides common services such as application connectivity, integration, administration, and presentation that would be required across all portal environments.

portlets: a portlet is a Java servlet that operates inside a portal. In other words, it is an individual web component that is made accessible to users via the portal.

portal container: sits between a portal and its portlets. The portlet container manages the lifecycle of the portlets. Controls portlet mode (View, Edit, and Help ) and window state (how much content should appear).

1) Users issue requests against portlets from the portal.
2) The portlet container receives requests from the portal server (instead of a web browser) and invokes the portlet’s “doView” and “doEdit” .
3)The portlet returns the generated markup.
4) The portal server aggregates the portlet makup for display.
5)The client displays the markup.

Portlet exposes four lifecycle methods:

– init(PortletConfig config)
– processAction(ActionRequest request, ActionResponse response)
– render(RenderRequest request, RenderResponse response)
– destroy()

* GenericPortlet: implements the render method and defines three empty methods, doView, doEdit, and doHelp. Your subclass of GenericPortlet can implement any of these methods.

* The ActionListener turns user clicks in your pages into action events…the WindowListener notifies your portlet of window events from the portal, such as when your portlet is maximixed, minimized, and restored. The MessageListener lets you handle messages sent from one portlet to another.

*PortletPreferences is an object that can be used to store persistent data for a portlet user.

*PortletSession : storing information within a user’s session.

*PortletRequestDistpacher: works in the same way a RequestDispatcher would in servlets.

*PortalContext: object can be used to query information about a portals supported extensions.

Onto Developing the Portlets:

July 27, 2004 Posted by | Portals | Leave a comment

Portal choices and more

The Gridsphere project: 100% JSR 168 Portlet API compliant , Portlet API implementation nearly fully compatible with IBM’s WebSphere┬« 4.2, Support for the easy development and integration of “third-party portlets”

Apache has several open source portal servers. Jetspeed 2 is JSR 168 compliant.

IBM Portal.

Jonas on ObjectWeb



Portlet article for newbies

Punit Pandely A Day in the Life of a Software Developer: Portlet Development & Portals.

IBM dw : Comparing the JSR 168 Java Portlet Specification with the IBM Portlet API

Websphere Application Server now has a new name starting with version 5.1 as far as I can tell. This article mentions the new IBM product – WebSphere Business Integration (WBI) Server Foundation 5.1

Also, the site defines SOA or that is SOA Enterprise.

Java Passion intro slides on portlets:

– Managed by Portlet container
– Generates piece of markup called Fragments
– Fragments vary based on user configuration

Portlet API:

For Portlets development, I will need to download the latest websphere studio application developer (called the integration edition) and also the toolkit for portlets. The portal page has the links to these two products.
I just found out yesterday that the websphere appplication server starting in 5.1 is now called WebSphere Business Integration (WBI) Server Foundation

WSRP(Web Services Remote Portlet):
-Presentation Orineted Web Service (enable interactive presentation orinted web services to be
easily plugged into standard compliant portals)

JSR 162
JSR 167
JSR 168

WebSphere Business Integration Server Foundation V5.1

Developing JavaServer Faces portlets using WebSphere Studio and the IBM Portal Toolkit — Part 1

Portlets plugin for eclipse – works w/o WSAD Integ Edtn



July 14, 2004 Posted by | Portals | Leave a comment