IBM Rational application Developer V7.5 Portal Toolkit, part 3rd

Web 2.0 portlet and portal programming support for IBM WebSphere Portal V6.1

This article describes the V6.1 that is running on the IBM WebSphere Portal server in Ibm®websphere®portal Portl or later in Ibm®rational®application Developer V7.5 ET, and the WEB 2.0 tool support introduced by the portal program. This article can help you better understand the tool support, and also discusses the basics and advantages of WEB 2.0 technology.

This article has introduced you to how to use the Ibm®rational®application Developer V7.5 in the WEB 2.0 for portlets running on Ibm®websphere®portal V6.1 and portal programs The advantages of tool support. In a typical Portlet program, each request to the server will cause a refresh of the entire browser page, resulting in a page instability and performance flaws. WEB 2.0 technology allows you to create more dynamic and responsive programs. This technique is designed to convert a Web browser to half a user by planning the user interface logic for page design, navigation, aggregation, and communication across portlets in the user's browser.

The WEB 2.0 tool support provided by Rational application Developer can help you create such dynamic and highly responsive portlets as well as portal programs. The tool support provided enables you to:

Create an AC portlets using the client's click action, which is a new event legend introduced in the WebSphere Portal V6.1 to facilitate collaboration between portlets.

Insert personal menus and features to extend the person menu.

Ajax proxies that use portlet programs.

Use the client's programming model to efficiently obtain portlet preferences and perform portlet state changes on the client.

This article discusses the above four topics in order. For each topic, this article starts with a description of a particular web-based 2.0 technology, and then introduces a simple example that demonstrates its tool support.

Appropriate readership: Portlets and developers based on portal programs.

The purpose of this article is to describe how to develop efficient, highly communicative, responsive portlets and portal based programs, and to explore the advantages of implementing tool support for AJAX proxies and client programming models.

Use client-side clicks to develop highly interactive and collaborative portlets

The Click Action (C2A) event is a way for portlets to communicate with each other and share information.

Click Action (C2A)

With the C2a delivery method, you can easily click once to pass data from the source portlet to one or more target portlets. When you click on the target element, a pop-up menu appears, giving a list of target actions that match the selected elements. When you select a menu item, the corresponding target is activated, and the source data is passed to it. After the source data is successfully delivered, the target portlet fires an operation and displays the results.

The client's click action

The client-click operation is a new implementation of the C2A framework introduced in the WebSphere Portal V6.1. It is based on WEB 2.0 technology and enables semantic tags to define sources and targets.

The primary purpose of the semantic tag is to reuse the normal content of the HTML file and annotate it with the source information evaluated during the document Object Model (DOM) analysis.

Semantic tags and the Live Object Framework

The client's click Operation builds on the Live object Framework (LOF), which defines the C2A source as the active object in the system. Marks the root element of a semantic label by adding the specified class to the element, where the element is specified by the active object framework.

LOF also provides basic DOM analysis and menu Management services.

Advantages compared with early C2A technology

The new client-click Technology introduced by WebSphere Portal has many advantages over earlier C2A technologies.

Both IBM and Java™specification Request (JSR) portlets can create legends with newly introduced events, while early C2A techniques can only be used in the portlets of the IBM Portlet APIs.

It supports the client's JavaScript C2A target operations and server-side operations. For example, when you select a menu item in the source Portlet, the source data is passed to the appropriate target, and actions fired on the target portlet can be server-side operations or JavaScript operations.

Using the new client-click Technique, the evaluation and execution of the C2A source and target can be done in the browser. The source and target matches no longer need to match on the server, and the technology also removes the menu generation code from the server. This lowers the load on the server.

The menu tag is generated only when you click the C2A Source menu icon.

All of these advantages can create a highly responsive and responsive UI without a server dead loop and page instability. In addition, it can generate more advanced user experience.

Terms

Figure 1 shows the C2a widget. Table 1 lists the terms that will be used in this article for the introduction of the client-click operation.

Figure 1. The client's click action

Table 1. Terms

/tr>

term	description
c2a source	type data that is semantically marked as the source of the C2A.
c2a target
source portlet	contains one or more C2A the portlet defined by the source object.
target portlet	contains one or more A portlet defined by the C2A target object. (Note: A portlet can be both a source portlet and a target portlet.)
c2a hover UI	in C2A source pair Icons appear next to each other, indicating that there is a menu associated with the object.
c2a pop-up menu	> Click C2A The menu that appears when you hover the UI. It may contain an optional menu header (seeIn Figure 1).
Menu header
C2A is implemented as a service in this framework.