Click OK. Personalizing a Web Clipping Portlet

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 5-22 Oracle Fusion Middleware Developers Guide for Oracle Portal ■ urlssl.properties In the migration process, the service deployment properties file as well as the provider.xml file used to contain old URL-based portlets will be copied and imported into the Web Clipping application, together with all the previous customizations based on the File Preference store. Because no modifications will be done on the original files used by these URL-based portlets, you do not need to back up any of these files. They can continue to be used as URL-based portlets. 3. Depending on the types of URL-based portlets you have, you may need to rearrange them as follows: ■ Because Web Clipping does not offer parallel functionality for the XML Filter capability that URL-based portlets offer, isolate all of the URL-based portlets that use the XML Filter into a separate service deployment and provider.xml file that will not be migrated. ■ Because you may face limitations when migrating URL-based portlets that use external applications, you may decide that the migration is too costly for that subset of your URL-based portlets. In this case, you can isolate them into a separate service deployment and provider.xml file that will not be migrated. 4. Make sure that the machine where you are planning to run the migration tool has local access to the service deployment files and files that the deployment files point to, for both the URL-based portlets provider and the Web Clipping provider. 5. Make sure that both the Web Clipping Repository and the HTTP Proxy are configured, and that the proxy settings concur with those used by your deployment of URL-based portlets. If you have a proxy server that requires authentication, the Web Clipping provider must be configured with Requires Authentication enabled. Set the Login scheme to use a global log in Use Login below for all users . Check the Web Clipping Provider Test page at: http:host:portportalToolswebClippingproviderswebClipping See the Oracle Fusion Middleware Administrators Guide for Oracle Portal for more information about setting proxy authentication. 6. Shut down the WLS instance where your Portal Tools application is running. This step ensures that no modifications are made to the files that will be migrated. Do not restart the WLS instance until after the migration is completed. To shut down the WLS instance in a Portal instance, use the following command from the Oracle\Middleware\user_projects\domains\Domain Name\bin directory: stopWebLogic.cmd Domain Name refers to the domain you have configured for your Portal.

5.6.2 Performing the Migration

The migration tool parses the service deployment properties file to find the provider.xml file that contains the XML definition of the URL-based portlets to be migrated. The tool changes the Provider Definition class from URLProviderDefinition to WcProviderDefinition. For each of the URL-based portlets defined in the provider.xml file, an equivalent clipping definition is created and inserted into the