Above the Web Clipping portlet you just added, click the Edit Defaults icon, as In the Find a Web Clipping page, modify the following items in the Properties

Creating Content-Based Portlets with Web Clipping 5-19 Figure 5–24 Clicking Personalize in the Web Clipping Portlet Header

8. In the page that displays, scroll down to the Inputs section. Notice that the

parameter field for the search string is labeled OTN Search, as you specified for the Display Name for this parameter. In the OTN Search field, enter a different search string. For example, enter OmniPortlet 2004, as shown in Figure 5–25 . Figure 5–25 Specifying Input for Parameters

9. Click OK.

The Web Clipping portlet now displays the results of performing a search on OTN for OmniPortlet 2004 information, as shown in Figure 5–26 . Figure 5–26 New Web Clipping Result Based on Customer Input Parameter 5-20 Oracle Fusion Middleware Developers Guide for Oracle Portal

5.5 Using Web Clipping Open Transport API

To support custom authentication methods, users can use the Web Clipping Transport API. To extend the Web Clipping transport layer to support custom authentication methods, users must perform the following implementation and deployment procedures: Implementation Users can implement their own transport classes. ■ Users can provide overrides for two use cases of the oracle.portal.wcs.transport.http.HttpTransportLiaison interface. In Web Clipping, this interface is used to abstract the HTTP transport layer. By default, the two use cases of this interface are manifested by following implementations: – HttpClientStudioTransportLiaison, which handles HTTP transport in Web Clipping Studio mode – HttpClientProviderTransportLiaison, which handles HTTP transport in Web Clipping Producer show mode To support more authentication methods, users must override the addRequestHeaders methods for both the Studio and Provider HttpClientTransportLiaison implementations to add their own authentication-specific headers. For more information about implementation, see Oracle WebLogic Server Web Clipping Transport API Reference. ■ Users must compile the new subclasses and package them into a jar file. To compile the new subclasses, users can use the following command: javac -classpath path_to_wcejar -d classes Where, path_to_wcejar refers to the path to the wce.jar file. To create the jar file, for example, users can use the following command from the classes directory: jar cvf ..mytransport.jar Where, mytransport.jar refers to t he jar file users want to create. Deployment Users must deploy the jar file to support the custom authentication method. ■ Users must place the jar file into the class path or shared library that is used by the Web Clipping producer at runtime. ■ Users must register the transport class in the web.xml file for Web Clipping producer by making the following modifications to the context parameters defined for HttpClientProviderTranportiaison and HttpClientStudioTransportLiaison: – Change the parameter value for oracle.webclipping.provider.TransportLiaisonClass to the name of the new class extended from the HttpClientProviderTransportLiaison class. – Change the parameter value for oracle.webclipping.studio.TransportLiaisonClass to the name of the new class extended from the HttpClientStudioTransportLiaison class.