You can develop IBM® WebSphere® Portlet Factory models to be run as portlets.
This development involves most of the same practices that are used when you develop standard models. You use the models to develop a portlet user interface or a data service. Portlets created with WebSphere Portlet Factory are dynamic, robust Java 2 Enterprise Edition (J2EE) applications. However, there are differences you need to take into account when developing a model that is to be used as a portlet.
The following list describes the major differences between WebSphere portlet models and standard models.
Portlet models use the Portlet Adapter builder for tighter integration with the IBM WebSphere Portal environment.
WebSphere Portal portlets can use JSR 168, JSR 286, or Click-to-Action (C2A) for inter-portlet communication.
Portlets can use the WebSphere Portal Server Group Segment Handler, which associates a user with a group defined in the WebSphere Portal and with the WPSPortalMode profile set that allows you to profile builder call inputs based on whether the model runs as a WebSphere portlet.
Creating a cooperative portlet source model: wpf7
If you developed a cooperative portlet target model, you can develop a cooperative portlet source model.
Creating a Cooperative Portlet Target Model: wpf7
In creating cooperative portlets, you create the target portlet first.
Sending cooperative portlet events to target portlets: wpf7
You can send events to multiple target portlets.
Changing a portlet title or description: wpf7
You can change the title or description of a portlet that you have published.
Creating a Click to Action receiver portlet: wpf7
In developing a C2A application, develop a receiver portlet first.
Creating a Click to Action sender portlet: wpf7
Once you have developed a receiver portlet, you can develop a sender portlet.
Sending a Click to Action event to multiple portlets: wpf7
Because C2A technology follows a broadcaster paradigm, sending C2A events to multiple portlets is as easy as sending C2A events to a single portlet.
Development of a WebSphere portlet: wpf7
You use IBM WebSphere Portlet Factory Designer to develop the portlet functionality.
Providing configure and edit functionality: wpf7
When the user views WebSphere Application Server portlets, they may have the option to configure or edit the portlet, which entails setting values for any configurable or editable properties of the portlet.
Profiling a portlet: wpf7
You can profile a portlet like any other IBM WebSphere Portlet Factory model.
Overview of IBM WebSphere Portlet Factory support for rich client platforms: wpf7
In WebSphere Portlet Factory, many WebSphere Portlet Factory portlets can now run on rich client platforms, such as IBM Lotus® Expeditor 6.1.1 and later, and IBM Lotus Notes® 8 Standard and later versions.