Find existing URL-based portlets.

Creating Content-Based Portlets with Web Clipping 5-23 Web Clipping Repository. Then, the PortletDefinition XML snippet corresponding to the portlet being migrated is replaced with a new one that uses WcPortletDefinition as its class. The replacement XML snippet contains a Clip Id that is a pointer to the newly inserted clipping definition. The new PortletDefinition XML snippet will no longer contain the same information as it did when it was a URLPortletDefinition. Namely, the migration tool uses the URL to visit as well as the headerTrimTag and footerTrimTag to generate an equivalent Web Clipping definition that will be stored within the Web Clipping Repository and only accessible from the provider.xml file through the Clip Id. The only information remaining will be the title and description. See Section 5.2.3, Setting Web Clipping Portlet Properties for instructions on modifying your clipping. To migrate portlets, take the following steps: 1. Set environment variables as follows: ■ On UNIX, set LD_LIBRARY_PATH to either the Install_homelib or Install_home lib32, depending on whether the operating system is 32-bit or 64-bit. ■ On Windows, set PATH to Install_home\bin. 2. Change to the ORACLE_HOMEportaljlib directory. 3. Use the following command to import the portlet to Web Clipping: java -Doracle.ons.oraclehome=ORACLE_HOME -jar wcwebdb.jar -import -from urlservices webclip_depprop urlsvc_depprop In the example, the parameters have the following meanings: ■ ORACLE_HOME refers to the directory where Oracle application is installed. ■ webclip_depprop refers to the path to your webClipping service deployment properties file. The path is typically: MW_HOME\user_projects\domains\DomainName\servers\WLS_PORTAL\tmp\_WL_ user\portalTools_11.1.1.1.0\kjdcke\war\WEB-INF\deployment Inst_Home refers to the location where Portal is installed. WLS_PORTAL refers to the WLS instance where your PortalTools application is deployed. ■ urlsvc_depprop refers to the path for the URL-based portlets service deployment properties file that points to URL-based portlets that you wish to migrate. For example, assume your URL-based portlets are deployed in the following directory on Windows: MW_HOME\user_projects\domains\DomainName\servers\WLS_PORTAL\tmp\_WL_ user\\portalTools_11.1.1.1.0\kjdcke\war\WEB-INF\deployment\providers

5.6.3 Post-Migration Configuration

After you migrate all of the URL-based portlets, take the following steps: 1. Start the WLS instance that hosts your provider. To start the WLS instance, use the following command: startWeblogic.cmd 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.