Introduction To Portlets

This chapter provides an overview of portlets & describes their uses. It explains portlet anatomy & the resources you can use to lớn create portlets. This chapter also explains the features, technologies, và tools to help you decide which portlet building technology best suits your needs.

Bạn đang xem: Introduction to portlets

A portlet is a reusable website component that can draw content from many different sources. Portlets can contain anything from static HTML content lớn Java controls lớn complex web services và process-heavy applications.

Portlets provide a means of presenting data from multiple sources in a meaningful & related way. Portlets can display excerpts of other website sites, generate summaries of key information, perform searches, & access assembled collections of information from a variety of data sources. Because several different portlets can be placed on a single page, users benefit from a single-source experience even though, in reality, the content may be derived from multiple sources.

Figure 11-1 Lottery Sample Portlet

Description of "Figure 1đối kháng Lottery Sample Portlet"

Portlets can communicate with each other using events và other techniques. A single portlet can also have sầu multiple instances—in other words, it can appear on a variety of different pages within a single portal, or even across multiple portals. Page designers can customize portlets to meet the needs of their specific audience. With the correct privileges, individual end users can further personalize portlets for their own particular requirements.

WebCenter Portal supports the development of portlets using JSR 286, an industry standard. You can also create portlets from existing JSF applications using the JSF Portlet Bridge. For more information, see About Portlet Resources.

11.2 About Portlet Anatomy

Portlet anatomy is the visual representation of the portlet on a page.

Figure 11-2 shows some aspects of portlet anatomy that you might expect lớn see in a typical portlet in WebCenter Portal. lưu ý that the same portlet displayed in a different application could look different.

Figure 11-2 Sample Portlet Showing Typical Portlet Anatomy

Description of "Figure 11-2 Sample Portlet Showing Typical Portlet Anatomy"

Aspects of portlet anatomy (some, but not all, of which are illustrated in Figure 11-2) include:

Portlet chrome—A collective sầu term for the different types of decoration that surround the portlet, including the header, shadow, rekích cỡ handle, Actions menu, và icons.

Portlet header—The area of the portlet that displays the portlet inhỏ, title, Actions thực đơn, & Customize và Personalize icons.

Portlet icon—A small image in the portlet header used lớn visually identify the portlet.

Portlet title—Text in the portlet header that indicates the purpose of the portlet. End users may be able to personalize this title at runtime khổng lồ make it more meaningful lớn their particular usage.

Personalize icon—An ibé in the portlet header that enables end users lớn make changes to the portlet that only they can see.

The Personalize icon is displayed only to authenticated users (that is, users who are logged in). It does not display lớn public users or unauthenticated users. You must implement some khung of application security for users lớn be able khổng lồ personalize their portlet views.

Customize icon—An ibé in the portlet header that enables application administrators lớn make changes to the mặc định settings of the portlet at runtime. These changes are visible lớn all users.

A typical customization setting is the portlet title. At runtime, the application administrator can determine what title should appear in the portlet header.

Actions icon—An ibé in the portlet header that displays the Actions menu when clicked.

Actions menu—A menu that lists various actions that users can persize on the portlet. The actions listed depover on whether the user is logged in, what privileges that user has, the functionality provided by the portlet, and the options specified when the portlet was added khổng lồ the page at thiết kế time. Actions include Move sầu, Remove sầu, Refresh, Move sầu Up, và Move sầu Down. The Actions menu also provides access to lớn other portlet modes available for the portlet, such as About, Help, Configure, và Print.

Xem thêm: Microsoft Office 2010 Full Không Cần Key, Crack

If the user who added the portlet to the page chose to lớn not display the portlet header, the Actions thực đơn is displayed on a fade in/fade out toolbar that displays on mouse rollover.

Resize handle—An area at the bottom right of the portlet that enables users to lớn change the form size of the portlet.

Scroll bars—Display when the portlet content does not fit the width và height specified for the portlet, providing access the content that is not initially displayed.

Portlet content—The actual nội dung of the portlet as determined by the portlet lô ghích.

The portlet anatomy rendered on the page is controlled by two factors:

The portlet"s own logic, as determined by the portlet developer. This includes which portlet modes are supported by the portlet.

The attributes of the portlet tag that binds the portlet khổng lồ the page, as determined by the application developer who added the portlet to the page at kiến thiết time.

For example, when designing the portlet, the portlet developer may implement Help mode for the portlet. When a page designer adds the portlet to lớn the page, he or she can determine, using the portlet property isHelpModeAvailable, whether or not to include the Help commvà in the portlet"s Actions menu. If the page designer sets isHelpModeAvailable to false, the Help commvà is not included in the Actions thực đơn even though it is provided in the portlet xúc tích và ngắn gọn. Conversely, if the portlet developer has not implemented Help mode for a portlet, the Help comm& is not displayed in the Actions thực đơn, even if isHelpModeAvailable is set khổng lồ true.

The portlets in your applications can come from a variety of sources, including other products and third-tiệc ngọt vendors.

Portlet resources also include custom built Java portlets built using WebCenter Portal"s Java portlet wizard for JSR 286. Each of these resources offers different sản phẩm features và are targeted toward users with different levels of experience.

This section includes the following topics: provides integration with other applications by enabling you khổng lồ expose functionality as portlets:

What Are They?

Supported applications include:

Other prebuilt portlets are available through"s partnerships with leading system integrators, software vendors, and nội dung providers.

Who Is the Intended User?

Fully developed, downloadable portlets are best suited for use by portal developers who understvà how khổng lồ tải về, install, & register producers in WebCenter Portal. They are available for use by all levels of experience.

When Should They Be Used?

Use prebuilt portlets when your needs are met by the functions the portlets offer and the màn chơi of personalization readily available is sufficient lớn complete the desired task.

Consider alternatives when you want lớn extkết thúc or personalize the portlet, for example, when you need a different user interface or when the functionality you require is not available out of the box.

What Are They?

The JSF Portlet Bridge enables application developers khổng lồ expose their existing JSF applications & task flows as JSR 286 Java portlets. The JSF Portlet Bridge simplifies the integration of JSF applications with WSRPhường portlet consumers, such as WebCenter Portal.

JSF portlets vì chưng not require separate source code from that of the JSF application. Since these portlets are created using the JSF Portlet Bridge, you need only maintain one source for both your application & your portlets. Similarly, when you deploy your portletized JSF application, the JSF portlets are also deployed with it. Therefore, using the JSF Portlet Bridge eliminates the requirement to store, maintain, and deploy your portlets separately from your application.

For more information about creating JSF portlets, see Creating Portlets from JSF Applications Using the JSF Portlet Bridge.