Open the provider.xml file for the URL-based portlets.

You can find it in the < OC4J_HOME>\j2ee\home\applications\jpdk\jpdk\WEB-INF\providers\urlsample directory.

Note: < OC4J_HOME> refers to the root directory of your OC4J installation.

Configure the proxy server settings in the provider.xml file (if required), because the URL-based portlets access URLs over the Internet. Depending on your setup, you may not need a proxy server to access external URLs. The URL-based portlet provider uses the proxy server settings that you specify in this file to connect to external Web sites.

 If you are using a proxy server, alter the following tags appropriately. If you are not using a proxy server, remove the following tags:

<proxyInfo class="oracle.portal.provider.v2.ProxyInformation">
<httpProxyHost>proxyServer.myDomain.com</httpProxyHost>
<httpProxyPort>80</httpProxyPort>
</proxyInfo>

For example, you can edit the provider.xml file to provide the proxy information, as shown below:

<proxyInfo class="oracle.portal.provider.v2.ProxyInformation">
<httpProxyHost>www-proxy.us.oracle.com</httpProxyHost>
<httpProxyPort>80</httpProxyPort>
</proxyInfo>

Modify the <stylesheet> tag to point to the correct location of the XML style sheet for the XML Filter portlet. It is located in the < OC4J_HOME>\j2ee\home\applications\jpdk\jpdk\htdocs\urlsample directory.

For example, you can edit the provider.xml file to provide the style sheet information, as shown below:

<stylesheet>
D:\pdk_oc4j\j2ee\home\applications\jpdk\jpdk\htdocs\urlsample\default_mit.xsl
</stylesheet>

http://< host name> :< port>/ jpdk/providers/urlsample

where < host name> and < port> are the host name and port number of the HTTP listener for your target OC4J instance.

Note: In an OracleAS installation with Web Cache installed, the port number should be the Web Cache listener port, for example 7777. In a stand-alone OC4J installation, the default HTTP port number is 8888.

Review the content of the displayed test page. This page lists the portlets that are included with the URL provider that has a service name of urlsample.

Access your OracleAS Portal instance. Click the Login link in the Login portlet.

Enter your username and password. Click Login.

Note: If you do not know your username or password, contact your portal administrator.

Click the Administer tab.

Click the Portlets sub-tab.

In the Remote Providers portlet, click the Register a Provider link.

Note: To register your provider, you must have Manage or Edit privileges on providers. If you do not have these privileges, you must request them from your portal administrator.

On the Provider Information page, provide the following details:

Click Next.

The portal and the provider communicate with each other over HTTP. Before using the provider and its portlets, you must specify the access details of the provider.

On the Connection page, specify the following provider information in the appropriate fields:

Click Finish.

You should receive a message indicating that your registration is successful.

Click OK.

Click the Navigator link.

Access your portal page.

To help you perform the steps in this section, a page group named Migrating URL Portlets and a page named URL Portlets Page within that page group have already been created.

Note: To learn more about creating page groups and pages, see the Building the Portal Site lesson.

Your path should be Path: Page Groups > <Migrating URL Portlets> Pages.

Click the Edit link to the right of the URL Portlets Page link.

Click the Add Portlet icon on the region header. OracleAS Portal displays the Portlet Repository.

Click the Portlet Staging Area link.

Note: By default, all the newly registered providers and portlets are available in the Portlet Staging Area in the Portlet Repository.

Click the URL Sample Portlets provider link.

Click the Google.com Portlet link to move it to the Selected Portlets area.

Click the ASP Portlet link to move it to the Selected Portlets area.

Click OK to return to the portal page.

Note that the URL-based sample portlets have been added to your portal page.

You can see your URL-based sample Google portlet, as shown below.

Note that the Refresh link is not available in the Portlet Header for the URL-based portlets.

You can see your URL-based sample ASP portlet, as shown below.

Note that the content rendered by the URL-based portlet is unorganized and poorly formatted.

Click the Navigator link at the top right of the page.

Click the Providers tab.

Click the Registered Providers link.

Click the Provider link to register a new Web provider.

The Register Provider page is displayed. Enter the following details in the Provider Information section:

Click Next.

Enter the Web Clipping Provider URL in the URL field.

The URL format is
http://< host name> :< port> /portalTools/webClipping/providers/webClipping .

In the User/Session Information section, select the User option button to send user-specific information to the provider.

Select Once Per User Session from the Login Frequency list.

Make sure that you have specified the correct proxy settings in the Proxy Settings section of the page. OracleAS Portal uses the proxy server settings that you specify in this section to connect to the Web Clipping provider.

Click Finish.

Click OK to complete the Web provider registration.

Before you initiate migration, ensure that no other users have modified the files that you intend to migrate.

Shut down the OC4J instance in your Oracle Application Server instance or the stand-alone OC4J instance where your Portal Tools application is running.

To shut down a stand-alone OC4J instance, you can use the following command from the < OC4J_HOME>\j2ee\home directory:

java -jar admin.jar ormi://< host name> admin admin_password -shutdown

Note: Do not restart OC4J until the migration has finished.

To shut down the OC4J instance in your OracleAS instance, execute the following command from the < INSTALL_HOME>/opmn/bin directory:

opmnctl stopproc gid="< OC4J_INSTANCE>"

For example, if your Portal Tools application is running in the OC4J_Portal instance, enter
opmnctl stopproc gid="OC4J_Portal" at the command prompt, as shown below:

Note: < OC4J_INSTANCE> refers to the OC4J instance where your Portal Tools application was deployed.

< INSTALL_HOME> refers to the OracleAS installation home, which is the root directory of your OracleAS installation.

Open the command window. If you are using a stand-alone OC4J instance, change your current directory to < OC4J_HOME>/portal/jlib .

If you are using OC4J in your OracleAS installation, change your current directory to < INSTALL_HOME>/portal/jlib .

Execute the following command:

java -jar wcwebdb.jar -import -from urlservices < WEBCLIP_SVC_DEP_PROPS> < URLSVCS_SVC_DEP_PROPS>

where

< WEBCLIP_SVC_DEP_PROPS> refers to the path to your Web Clipping service deployment properties file.
It is typically found in the < INSTALL_HOME>/j2ee/< OC4J_INSTANCE>/applications/portalTools/webClipping/WEB-INF/deployment/webClipping.properties directory.

< URLSVCS_SVC_DEP_PROPS> refers to the path to the URL-based portlets service deployment properties file pointing to URL-based portlets that you want to migrate.
It is typically found in the < INSTALL_HOME>/j2ee/home/applications/jpdk/jpdk/WEB-INF/deployment directory.

For example, you can see the command that is executed on a stand-alone OC4J instance.

Look for the “ Importing into Web Clipping was successful” message to check that your URL portlet has been imported.

Note: If you encounter any problems or errors during the migration process, please see the Limitations and Troubleshooting section in the Migrating From URL-Based Portlets to Web Clippings Portlets document in Portal Center.

After migrating all the URL-based portlets, you must verify that the migration is successful. First, restart the OC4J instance that hosts your provider.

To start a stand-alone OC4J instance, execute the following command from the < OC4J_HOME>\j2ee\home directory:

java -jar oc4j.jar -err errors.log

Note: The errors.log file is an arbitrary file where the standard error messages are written. You can access the errors.log file to identify the errors that might have occurred when you started the OC4J instance.

To start the OC4J instance in your OracleAS instance, execute the following command from the < INSTALL_HOME>/opmn/bin directory:

opmnctl startproc gid="< OC4J_INSTANCE>"

Access the Portal Navigator page.

Access the Registered Providers. Your path should be Path: Providers > Registered Providers.

Click the Edit Registration link to the right of the URL Sample Portlets link.

Click the Connection tab.

Update the provider URL value to:

http://< host name> :< port> /portalTools/webClipping/providers

Note: If you registered your URL-based portlet provider by using a provider URL that contained the Service ID, you must update the provider URL to:

http://< host name> :< port> /portalTools/webClipping/providers/urlsample

Click OK.

Click the Refresh link to update the provider registration.

Click the Page Groups tab.

Click the Migrating URL Portlets link.

Click the Pages link.

Click the Edit link to the right of the URL Portlets Page link.

You can now see your migrated URL-based sample Google portlet, as shown below. Note that the Refresh link is available by default in the Portlet Header for the Web Clipping portlet.

You can see your migrated URL-based sample ASP portlet, as shown below.

Note the difference in the rendering of content in the Web Clipping portlets. You can see that the style sheet has been applied and the content is better organized.

Access the test page for the migrated URL-based sample portlets by using the following URL:
http://< host name> :< port> /portalTools/webClipping/providers/urlsample

Click the Edit link to edit the Google.com portlet.

Note that you can alter the clipping for the migrated URL-based portlet without modifying the provider.xml file.