In the Web Clipping portlet header, click Personalize, as shown in

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. Creating Content-Based Portlets with Web Clipping 5-21 ■ Finally, users must restart the producer server for the changes to take effect.

5.6 Migrating from URL-Based Portlets

You can migrate URL-based portlets that are stored in a provider.xml file to Web Clipping portlets. These Web Clipping portlets will exist in the Web Clipping Repository, but you can access the portlets through pointers defined in the provider.xml file. Note that, during the migration process, no modifications will be done on the original files used by these URL-based portlets. This section describes the following tasks: ■ Section 5.6.1, Preparing for Migration ■ Section 5.6.2, Performing the Migration ■ Section 5.6.3, Post-Migration Configuration ■ Section 5.6.4, Maintaining Migrated Portlets ■ Section 5.6.5, Limitations in Migrating URL-Based Portlets

5.6.1 Preparing for Migration

Before you begin the migration, take the following steps:

1. Verify that the Web provider that contains the URL-based portlets you want to

migrate is functional. The migration process will not succeed with non-functional URL-based portlets. To verify, make sure that the URL-based portlets are used by your Portal pages and that they appear correctly.

2. Find existing URL-based portlets.

Before you run the migration tool, make sure that you know the file path to the service deployment properties file, which holds pointers to everything about the service, including the path to the provider.xml file that holds the URL services definitions. You must run the migration tool once for each service. If you have multiple services, find the entire list of service deployment properties files that will be used during migration. The location of these service deployment properties files may vary depending on individual deployment scenarios. Typically, with JPDK samples, they are located in: Domain_homeserversWLS_PORTALtmp_WL_userjpdk JPDK samples that are shipped with the Oracle Portal are located in the same directory path. The list of sample service deployment properties files include the following: ■ urlbasicauth.properties ■ urlexternalauth.properties ■ urlnls.properties ■ urlparams.properties ■ urlsample.properties