Portlet Factory, Version 6.1.2
Development of portlets
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.
- Using edit and configure modes
- Portlet models use the Portlet Adapter builder for tighter integration with the IBM WebSphere Portal environment.
- Using portlet events
- WebSphere Portal portlets can use either JSR 168 or Click-to-Action (C2A) for inter-portlet communication.
- Using profiling in portlets
- 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.
Parent topic: Working with WebSphere Portlet Factory
- Introduction to portlets
IBM WebSphere Portlet Factory enables you to rapidly deliver dynamic, highly customizable, and adaptive portlets.
- Providing configure and edit functionality
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.
- Implementing inter-portlet communication
Use inter-portlet communication to have portlets interact and share information.
- Profiling a portlet
You can profile a portlet like any other IBM WebSphere Portlet Factory model.
- Changing a portlet title or description
You can change the title or description of a portlet that you have deployed.
- Overview: security methodologies
Maintaining a secure environment is critical when you deploy a Web application.
- Portal Event Declaration builder
Use the Portal Event Declaration builder to define a portal event and create a method for firing the event.
- Setting the profile selection handler for a profile set
You can set the profile selection handler for a profile set.
- Portlet Adapter builder
The Portlet Adapter builder allows you to expose profile values for customization when the model is used as a portlet running on a portal server. It takes the inputs described in this table.
- Event Handler builder
The Event Handler builder lets you specify an action to perform when a specified event occurs.
- Adding IBM WebSphere Portal JAR Files
If you plan to use any Java APIs that are not already included in your IBM WebSphere Portlet Factory web application project, you need to add the corresponding JAR files to your environment.
Library | Support |