Introduction: Portlet applications
Portlet applications are special reusable Java servlets that appear as defined regions on portal pages. Portlets provide access to many different applications, services, and Web content.
- Set up the development environment
- Set up the IDE for developing and debugging console modules.
Use the Integrated Solutions Console Visual Designer feature to create the portal topology and security deployment descriptors needed to enable portlet applications to run in the admin console environment.
- Develop the portlet
- A simple Java class and JSP are provided.
- Develop portlets
- Console modules are portlets that run in the portlet container of WAS.
- Launching pages
- Typically, users of the console launch pages using the links in the console navigation. However, portlets in a console module also launch pages directly using the Dynamic UI Manager API.
- Passing properties to other portlets
- This page describes how portlets can exchange properties. You should be familiar with the concepts for launching console pages before reading this topic.
- Portlets are reusable Web modules that run on a portal server and provide access to Web-based content, applications, and other resources. We can assemble portlets into a larger portal page, with multiple instances of the same portlet displaying different data for each user.
- Portlet container
- Runtime environment for portlets using the portlet API in which portlets are instantiated, used, and finally destroyed.
- Portlet aggregation using JSPs
- The aggregation tag library is used to write JSPs to address one or more portlets to generate a portlet aggregation framework.
- Portlet URL addressability
- We can request a portlet directly through a URL to display its content without a portal aggregation. The PortletServingServlet servlet registers each Web app that contains portlets. It is similar to the FileServingServlet servlet of the Web container that serves resources.
The PortletServingServlet servlet allows you to directly render a portlet into a full browser page by a URL request.
- Portlet preferences
- Preferences are set by portlets to store customized information. By default, the PortletServingServlet servlet stores the portlet preferences for each portlet window in a cookie. However, we can change the location to store them in either a session, an .xml file, or a database.
- Portlet URL security
- WAS enables direct access to portlet URLs, just like servlets. This section describes security considerations when accessing portlets using URLs.
Related informationLearn about portlet applications