|Oracle® Fusion Middleware User's Guide for Oracle WebCenter
11g Release 1 (11.1.1)
Part Number E10149-02
This chapter provides an overview of portlets. It contains the following sections:
Note:In WebCenter Spaces, avoid adding a portlet to a Movable Box layout component (see Section 6.5, "Working with Page Layout Components"). The Movable Box layout component duplicates the
showDetailFramethat the portlet provides by default. Adding a portlet to a Movable Box creates an unnecessary and potentially error-prone redundancy.
This chapter is intended for users who want to learn about portlets and how they integrate with Oracle WebCenter.
Portlets provide a means of presenting data from multiple sources in a meaningful and related way. Portlets can display excerpts of other web sites, generate summaries of key information, perform searches, and access assembled collections of information from a variety of data sources. Because different portlets can be placed on a common page, you receive a single-source experience, though the content may be derived from multiple sources.
Figure 29-1 illustrates the Most Active Customers portlet. As the name suggests, this portlet shows the most active customers of a business unit.
Figure 29-2 illustrates what a portlet typically looks like on a page in a WebCenter application. Note that the same portlet displayed in a different application could look different.
Portlet header. The area of the portlet that displays the portlet title and the icons that enable interaction with the portlet. The user who added the portlet to the page may have chosen to not display the portlet header.
Portlet title. Text in the portlet header that indicates the purpose of the portlet. You may be able to personalize this title to make it more meaningful for your particular usage.
Minimize/Expand icon. An icon in the portlet header. Clicking the Minimize icon causes the portlet content to collapse so that only the portlet header is displayed. This saves space on the page and reduces clutter without permanently removing the portlet from the page. When the portlet is minimized, the icon becomes an Expand icon that you can click to display the content again.
Actions icon. An icon in the portlet header. Clicking the Actions icon displays the Actions menu.
Actions menu. Lists the actions that you can perform on the portlet. The actions depend on whether you are logged in, your privileges, the logic of the portlet, and the specifics of how the portlet was placed on the page. Actions include Personalize, Maximize, Restore, Refresh, and Move Up or Down. If the portlet provides modes such as Help and About, these are also listed in the Actions menu.
If the user who added the portlet to the page chose to not display a portlet header, the Actions menu is displayed on a fade in/fade out toolbar that displays on mouse rollover.
Resize handle. Enables you to make the portlet bigger or smaller.
Portlet content. The actual content of the portlet as determined by the portlet developer.
The appearance of a portlet is determined by the internal logic of the portlet itself, as written by the portlet developer, the attributes specified by the user who added the portlet to the page, and any of your own personalizations. For example, the portlet developer can determine, during portlet creation, whether users can personalize the portlet at runtime. The user who adds the portlet to a page can decide whether the personalize option is displayed in the Actions menu. The user at runtime can minimize the portlet so that the content is not even displayed on the page.
If your application includes portlets, and you are logged in, you can edit those portlets to make them display the information that you, personally, want to see (this is known as personalization). To personalize a portlet, click the Actions icon in the portlet header and choose Personalize from the menu. The personalizations you can make depend on how the portlet developer designed the portlet. You can also hide portlets, or remove them entirely from the page. Note that the changes that you make apply only to you. If you delete a portlet, other users can still see it when they view the page (unless they have deleted it themselves).
If you have the appropriate privileges, you can also edit the way the portlet appears to all users (this is known as customization). To customize a portlet, click the Actions icon in the portlet header and choose Customize from the menu. The changes you make are visible to all users.
If you have the appropriate privileges to edit a page in a WebCenter application, you can add portlets to that page. The portlets you can add depend on the producers that have been registered with the application. A producer is the object that owns the portlet and makes it available to an application. If you cannot find a particular portlet, ask your WebCenter application administrator to register the associated producer for you. For information about adding portlets to a page, see Section 7.1.5, "Adding Portlets to a Page."
There are several different kinds of portlets available to you. Portlets fall into the following categories: prebuilt portlets provided by Oracle and third-party sources; portlets built for you by your own developers; and portlets that you can build yourself. However, you can only use portlets that the WebCenter application administrator has registered with the application. When it comes to adding portlets to a page, a portlet's category and how it was created are irrelevant; all portlets are listed in the Resource Catalog and are available for inclusion.
This section includes the following subsections:
Prebuilt portlets include partner portlets and integration solutions.
Partner portlets are available through Oracle's partnerships with leading system integrators, software vendors, and content providers. You can access these portlets by using the keywords
portlet when searching the Oracle PartnerNetwork (OPN) Solutions Catalog, available at:
Examples of these include portlets for the following purposes:
Generating point-to-point driving directions
Accessing Information Technology (IT) information from a wide variety of sources
Viewing summary information about news, stocks, and weather
If you think a particular portlet would be useful for your application, ask your WebCenter application administrator to register the appropriate producer for you.
JSF portlets expose existing JSF applications and task flows as JSR 168 portlets. They are created using the Oracle JSF Portlet Bridge. The Oracle JSF Portlet Bridge simplifies the integration of JSF applications with WSRP portlet consumers, such as Oracle Portal. Developers create JSF portlets in Oracle JDeveloper using the JSR 168 Java Portlet Wizard or the Portlet Bridge design-time wizard for pages and task flows.
JSF portlets do not require separate source code from that of the JSF application. Since these portlets are created using the Oracle JSF Portlet Bridge, developers need only to maintain one source for both the application and the portlets. Similarly, when the JSF application is deployed, JSF portlets are also deployed with it. Therefore, using the bridge eliminates having to store, maintain, and deploy portlets separately from the application.
Programmatic portlets are portlets that have been written specifically for your organization to meet a particular requirement not met by the out-of-the-box portlets. Oracle WebCenter Framework provides two declarative wizards for simplifying the creation of standards-based JSR 168 portlets and Oracle PDK-Java portlets. These wizards assist in the construction of the framework within which developers create the portlet.
Some examples of programmatic portlets might be:
Photo album portlet. A portlet that facilitates uploading, storing, and viewing user photos.
Shopping cart portlet. A portlet that facilitates the viewing and purchasing of, for example, company-branded items, such as mouse pads, pens, flash drives, tee shirts, and so on.
Programmatic portlets are written by experienced Java developers who are familiar with the Java Portlet Specification or Oracle PDK-Java. For more information about programmatic portlets, see the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.
Web Clipping is a publishing portlet that enables you to integrate any web application with your WebCenter application. It is designed to give you quick integration by leveraging the existing user interface of a web application. With Web Clipping, you can collect web content into portlets in a single centralized web page. You can use Web Clipping to consolidate content from web sites scattered throughout a large organization.
To create a Web Clipping portlet, use a web browser to navigate to a web page that contains the desired content. Through the Web Clipping Studio, you can drill down through a visual rendering of the target page to choose the desired content.
Web Clipping supports the following:
Fuzzy matching of clippings. If a web clipping gets reordered within the source page or if its character font, size, or style changes, it can still be identified correctly by the Web Clipping engine and delivered as the portlet content.
Personalization, allowing you to expose input parameters that you can then modify when you personalize the portlet. You can expose these parameters as public parameters that you can map as page parameters. This feature enables you to obtain personalized clippings.
Integrated authenticated web content through Single Sign-On, including integration with external applications, which enables you to leverage Oracle Single Sign-On and to clip content from authenticated external web sites.
Inline rendering, enabling you to set up Web Clipping portlets to display links within the context of the portlet. As a result, when you click a link in the Web Clipping product, the results display within the same portlet. You can use this feature with internal and external web sites.
Proxy Authentication, including support for global proxy authentication and authentication for each other. You can specify the realm of the proxy server and whether all users automatically log in using a user name and password you provide, each user logs in using an individual user name and password, or all users log in using a specified user name and password.
Resource Tunneling of images.
Open Transport API for customizing authentication mechanisms to clipped sites.
Some examples of how you might use Web Clipping are:
Stock chart portlet. Create a portlet that displays the stock market's daily performance chart from your financial advisor's web site. You can clip this information from an external web site, even if your company is using a proxy.
Web mail portlet. Access your confidential web mail account through a portlet and to display your in-boxes in the portlet.
For more information about using Web Clipping, see Chapter 31, "Working with the Web Clipping Portlet."
OmniPortlet is a data publishing portlet that you add to your application at design time, so that users can customize at runtime. Using a wizard, page designers can publish data from a variety of data sources (including SQL, XML, web services, spreadsheets, and web pages) to several different layouts, such as customizable charts and tables.
Like Web Clipping, OmniPortlet supports proxy authentication, including support for global proxy authentication and authentication for each user. You can specify whether all users automatically log in using a user name and password you provide, each user logs in using an individual user name and password, or all users log in using a specified user name and password.
Some examples of how you might use OmniPortlet are:
RSS news feed portlet. Create a portlet that displays live, scrolling news information to your users from a Really Simple Syndication (RSS) news feed, such as Oracle Technology Network Headlines. You can also include hyperlinks to the news source.
Sales chart portlet. Present up-to-date information about your company's sales results. You can choose to display the data as a pie chart and store the sales information in a remote relational database for later use.
For more information about OmniPortlet, see Chapter 30, "Working with OmniPortlet."
The Parameter Form portlet has three output parameters that are set when values are submitted in the form inside the portlet. The parameters can then be used to drive the content of other portlets. You can customize the Parameter Form portlet to determine how many of the three fields are displayed on the form, depending on how many parameters you require.
The Parameter Display portlet enables you to quickly test the wiring from the Parameter Form portlet. However, typically you use the values passed from the Parameter Form portlet to drive the content of some other portlet, for example, to pass a zip code to a weather portlet, or a stock symbol to a stock ticker portlet.
Figure 29-3 shows a Parameter Form portlet that has been customized to accept a single value (Zip Code). When a user enters a zip code and clicks OK, the Parameter Display portlet refreshes to display the same zip code.
For more information about linking portlets, see Chapter 8, "Wiring Pages, Task Flows, Portlets, and UI Components."