Configure portlet filtering for IBM API portlets
A portlet filter enables the administrator of a portal to intercept and modify the output of a portlet before it is aggregated to the entire portal page. This way we can support different languages and markups other than those for which the portlet was originally designed. Use portlet filters also for adding additional information to the portlet output, for example, a copyright statement, deleting unimportant or restricted content, and for parsing destructive JavaScript.
To use portlet filters, we need to perform all of the following procedures:
- Enable portlet filtering for the portal
- Register the portlet filters, that is define and activate them in a properties file
- Assign the filters to the portlet.
Using portlet filters only applies to the IBM portlet API. For portlets written against the JSR 286 specification, portlet filtering is already defined within the JSR 286 standard and is configured differently.
See
- Enable portlet filtering
- Register portlet filters
- Assigning filters to a portlet
- Portlet filter life cycle
- Supported filter targets
- Programming tips: wrapper objects
- Request flow of portlet filters
Parent Configure portal behavior