IBM® WebSphere® Portlet Factory Designer supports development of Web applications that use either the Java Portlet Standard 2.0 (JSR 286) or the Java Portlet Standard 1.0 (JSR 168) API.
These applications can run in the WebSphere Portal server but cannot use features specific to that server.
Development of a WebSphere JSR 168 portlet
To limit yourself to the functionality defined in JSR 168, you cannot use features specific to WebSphere Portal server, such as Click-to-Action (C2A) or People Awareness. These features work on a WebSphere Portal server that uses JSR 168, but do not work on other JSR 168 portals.
The JSR 168 portlet specification does not support J2EE 1.2 portlet applications. If you build JSR 168 portlets, the portlets must be based on the J2EE 1.3 or later specification.
Do not rely on HTTP headers for the functionality of your models and portlets. The JSR 168 Portlet Specification states the following :
"Depending on the underlying web-server/servlet container and the portal/portlet container implementation, client request HTTP headers may not be always available. Portlets should not rely on the presence of headers to function properly."
Portlets may run remote to the portal server, by Web Services for Remote Portlets (WSRP). As such, do not rely on HttpServletRequest API methods that in a traditional Web application return information about the caller or browser request (for example, getRemoteAddr
). In other words, the HTTP request to the portlet may not be the same as the HTTP request from the browser to the portal.
Existing portlets configured using the WebSphere Portal portlet adapter are not immediately and automatically configured once the JSR 168 Portlet Adapter is installed. To make an existing deployed portlet available as a JSR 168 portlet, simply perform a copy of the base portlet and set the model name. Your portlets can then run as JSR 168 portlets and do not require any code changes.
Web Services for Remote Portlets (WSRP) support
WebSphere Portlet Factory provides qualified support for WSRP 1.0 on WebSphere Portal 6.0.1 and for WSRP 2.0 on WebSphere Portal 6.1 and later systems.
The following WebSphere Portlet Factory functionality does not work in a portlet that is built to the WSRP specification.
- Partial-page refresh and Ajax operations
- Usage of the PUMA API and any portlets that utilize the PUMA API
- Content Model builders
- Spreadsheet Export builder
- Lotus Forms Embed and Lotus Forms Launch builders
- WebSphere Portal Server Group Segment handler
- Edit Defaults (Shared Settings)
These limitations are not inclusive of any limitations imposed by WebSphere Portal and WSRP specifications.
Additionally, cooperative portlets (Property Broker) are only supported when the Java Portlet Standard 2.0 API is used on WebSphere Portal 6.1 and later systems with WSRP 2.0.
Although WebSphere Portlet Factory generates applications that conform to the WSRP 1.0 and WSRP 2.0 specifications, IBM provides no explicit support for the production or consumption of portlets for specific WSRP compliant portlet containers, portal servers, and application servers other than WebSphere Portal server and WebSphere Application Server.
For more information on WSRP support, see the WebSphere Portlet Factory wiki
Parent topic: Development of a WebSphere portlet: wpf7