PUBLIC MARKS with tags portal & portlet

JSR-168 is a collection of Java APIs for portlet developers. There are a number of reasons to design JSR-168 portlets that adhere to the specification. Portability is an obvious benefit. Code written according to the specification will be easier to move to among portal servers. The majority of Java-based portal servers support JSR-168 portlets. Another benefit is easier federation. Exposing JSR-168 Portlets via Web Services for Remote Portlets (WSRP) producers is easier when portlets adhere to the JSR-168 specification. WSRP provides a standard to federate portlet content via Web services. JSR-168 and WSRP 1.0 portlet capabilities are tightly coupled. JSR-168 to WSRP portlet bridges utilize JSR-168's URL rewriting APIs. This article illustrates best practices for developing JSR-168 portlets for portability.

StringbeansTM is a platform for building enterprise information portals. The platform is composed of three components: a portal container/server, a Web Services platform, and a process automation engine. At this time we have released the portal server and Web services platform. The process automation engine will be released in the near future.

This article describes the first steps a team would typically take when starting a new project to implement a portal using IBM® WebSphere® Portal. It also provides some basic tools that can help you with these first steps. It discusses issues that teams typically face when starting a new portal project, and suggests some approaches to dealing with them. It describes various types of portals and how the type of portal you choose can influence your planning process. Finally, it introduces several tools, or work products, which you can use to plan and set up your own portal. This article is the first in a multiple-part series Creating a new portal.

Portlet Frequently Asked Questions (FAQ) - a collection by Punit Pandey