Performing the Migration Migrating from URL-Based Portlets

5-24 Oracle Fusion Middleware Developers Guide for Oracle Portal 2. Update all Portal instances where URL-Based portlets were previously registered. Go to Portal Navigator to find your previously registered URL-based Portlet provider. Click Edit Registration and then click the Connection tab to edit the connection information to the newly migrated provider. Depending on how you registered the portlet, perform either of the following steps: ■ If you previously registered your URL-based Portlet provider using the Service Id mechanism, your provider URL looked similar to the following: http:host:portjpdkjpdkproviders In this case, because the Service Id field already contains urn:someservice, you now need only to update the provider URL value to the following: http:host:portportalToolswebClippingproviders ■ If you registered your URL-based Portlet provider using a provider URL that contained the Service Id, your provider URL looked similar to the following: http:host:portjpdkjpdkprovidersservice_id In this case, you need to update the provider to the following: http:host:portportalToolswebClippingprovidersservice_id For the most part, the rest of the registration details can remain as they are. However, if you plan on using the in-line rendering functionality of the migrated portlets, you must select Once Per User Session for Login Frequency. 3. Restore HTTP proxy authentication setting that you altered in preparation for the migration. During the migration process, URL-based portlets are converted to Web Clipping portlets. If the Web Clipping provider has originally been configured with Requires Authentication enabled, your migrated URL-based portlets may not function properly. Check the test page at: http:host:portportalToolswebClippingproviderswebClipping If the Login Scheme is not set to Use login below for all users, then authentication is accomplished by mapping the current portal user to a proxy server username and password. A portal users proxy server credentials can only be entered through the Personalize link of the Web Clipping portlet. However this cannot be accomplished through the Personalize link of the migrated URL-based portlets. The workaround is to temporarily add a Web Clipping portlet to the page and personalize it to provide the security credentials. After this is complete, you can remove the temporary portlet. 4. Review each Portal page where you had used URL-based portlets and verify that the page still contains the content. Occasionally, you may find that, after migration, what used to be a trimmed Web page is now the entire Web page. This may be due to some of the limitations of the migration tool, which are discussed in Section 5.6.5, Limitations in Migrating URL-Based Portlets. If this happens, edit the portlet by altering the Web Clipping associated with it.

5.6.4 Maintaining Migrated Portlets

After you have migrated the portlets, you no longer use the provider.xml file to edit the portlets. Instead, you use Web Clipping to edit the portlets, as described in Section 5.2.3, Setting Web Clipping Portlet Properties. Creating Content-Based Portlets with Web Clipping 5-25 Note the following: ■ Whatever modifications you make to the clipping will affect it at the portlet definition level and therefore will affect all the instances of that portlet which may exist across Portal pages. ■ When you modify the clipping and you have made the portlet rendering to be Inline, and have registered the provider with a Login Frequency of Once per User Session , then page viewers who have an instance of the particular portlet on their page, will need to log out of Oracle Portal and log in again to see the changes implemented. This feature avoids disruption of the page viewers usage of a particular portlet when it is being modified. ■ For portlets with Web Clippings that require authentication to an external application prior to accessing the page containing the clip, the off-line editing mechanism detailed in the previous item does not provide such authentication information. Consequently, there is no way to modify the migrated clipping if the original URL-based portlet uses external applications. There is currently no workaround for this limitation.

5.6.5 Limitations in Migrating URL-Based Portlets

This sections describes limitations in migrating URL-based portlets to Web Clipping and describes some differences between the two methods. Following are the differences: ■ There is a fundamental difference between URL-based portlets and Web Clipping in the way that clippings are defined. URL-based portlets use the headerTrimTags and footerTrimTags tags to define the begin and end of a particular section in an HTML page. On the other hand, Web Clippings use the HTML tag path for example, htmlbodytable[2]tr[2]td[1] to denote the path to use when looking for an HTML tag that would contain the clipping within the page. While the header and footer trim tags for URL-based portlets offer greater flexibility that is, the clipping does not need to reside within one single HTML tag, it is not as robust. When a clipping can no longer be found in the same location within a page, there is no way to apply fuzzy matching logic to find the clipping again. On the other hand, Web Clipping stores key pieces of information to locate the clipping within the page. If the clipping is not in the same location, the fuzzy match feature looks for other candidates on the same HTML page to account for the possibility that the clip may have moved. ■ The migration tool tries to find the clipping HTML Tag that encapsulates the headerTrimTags and footerTrimTags. Often, this will not be the exact HTML that was extracted by the URL-based portlet. In these cases, the entire Web page will be returned as the content of the migrated Web Clipping Portlet. To amend this, simply edit the portlet. ■ URL-based portlets that have been migrated to Web Clipping do not support proxy authentication by default. This is because URL-based portlets inherently do not support proxy authentication and Web Clipping preserves the edit mode of the portlets. Their edit mode does not provide an opportunity to enter authentication information. To work around this restriction, add an empty Web Clipping portlet to the same portal and use the Web Clipping portlet Personalize link to enter the user name and password for proxy authentication. ■ URL-based portlets that used external applications are migrated as full-page Web Clipping portlets. This means that the URL previously specified by the URL-based