Maintaining Migrated Portlets Migrating from URL-Based Portlets

5-26 Oracle Fusion Middleware Developers Guide for Oracle Portal portlet definition will be the one used to display the full page after the log in process. Whatever headerTrimTags and footerTrimTags you have previously specified will be lost, because external application integration occurs at the Portal side while the migration tool only handles the provider side. Because you are not connected to any Portal instances at the time of the migration, and the external applications framework resides only on the Portal side, the migration tool cannot fetch the authentication information necessary to log in to parse the HTML and use the headerTrimTags and footerTrimTags that you have previously specified to compute an HTML Tag Path to store in the Web Clipping Definition. In maintaining migrated portlets, you can edit the clipping through links in the test page. However, this does not include URL-based portlets that used external applications to authenticate themselves to the external sites. There is currently no workaround for this issue. ■ URL-based portlets that use the XML Filter cannot be migrated to Web Clipping portlets because there is a lack of such a functionality in the Web Clipping Portlet. Before proceeding with migration, make sure that you have backed up the URL-based portlets that use the XML Filter into a separate URL-based portlet provider. You must do this because the migration occurs at the provider level. That is, upon interpreting that a particular provider.xml file has URLProviderDefinition for its provider definition class, all the portlet definitions contained within that provider definition are migrated.

5.7 Current Limitations for Web Clipping

This section describes current limitations for Web Clipping. For information about the latest limitations in a release, be sure to read the Oracle Portal Release Notes. Following are the limitations: ■ If the site to which you are connecting uses a large amount of JavaScript to manipulate cookies or uses the JavaScript method document.write to modify the HTML document being written, you may not be able to clip content from the site. ■ When you integrate with partner applications through the use of mod_osso, you cannot clip directly through those partner applications in an authenticated manner. However, you can use the partner applications through the external application framework. ■ You cannot use the Web Clipping portlet to clip Oracle Portal pages. As a workaround, examine the portlet that is supplying the data and take the appropriate action, as follows: – For database provider portlets, use exportimport to copy pages across portals. – For Web provider portlets, re-register the same provider in the destination portal and edit the portal manually. ■ You cannot use the Web Clipping portlet to clip a Web page that contains more that one frame, that is, a frameset. ■ Note the following about Web Clipping and the use of cascading style sheets CSS: – If a Web page contains more than one portlet that uses a CSS, they should not conflict if the CSS uses distinct style names, such as OraRef, to specify a style within an HTML tag, rather than using an HTML tag name, such as A, as the name of the style. Creating Content-Based Portlets with Web Clipping 5-27 – If one portlet uses a CSS, and that CSS overwrites the behavior of HTML tags by using the name of the tag, such as A, as the name of the style, and a second portlet on the same page does not use a CSS, the second portlet will be affected by the style instructions of the CSS of the first portlet. – If two portlets on the same page use a different CSS and each CSS overwrites the behavior of HTML tags by using the name of an HTML tag, such as A, as the name of the style, the style that will be displayed depends on the browser. ■ Web Clipping checks for NLS settings in the following way: 1. Web Clipping checks the Content-Type in the HTTP header for the charset attribute. If this is present, it assumes that this is the character encoding of the HTML page. 2. If the charset attribute is not present, it checks the HTML META tag on the page to determine the character encoding. 3. If the HTML META tag is not found, Web Clipping uses the charset in the previous browsed page. If this is the first page, it defaults to the ISO-8859-1 character encoding. 4. If the value of the charset for Content-Type or META tag is not supported for example, if the charset was specified as NONE, Web clipping uses the default character set, ISO-8859-1, not the charset in the previously browsed page. ■ To use the Web Clipping portlet, you must use Netscape 7.0 or higher, or Microsoft Internet Explorer 5.5 or higher for Windows 2000, or Microsoft Internet Explorer 6.0 or higher for Windows XP. If you use browser versions older than these, you may encounter JavaScript errors. For troubleshooting information, see Appendix B, Troubleshooting Portlets and Providers.