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

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