Troubleshoot Web Clipping portlet

The following section lists known problems and solutions related to Web clipping.

 

Web clipping portlet: Needed certificate is missing error

If you attempt to connect to a secure site using the Web clipping portlet and get an error message indicating that the needed certificate is missing, add a certificate file to correct the problem. These instructions assume that a browser such as Internet Explorer can successfully connect to the site and that it has the root certificate that is needed.

Solution:

To add the necessary certificate, complete the following steps:

  1. Open a browser, and enter the Web address of the secure site that you are trying to connect to with the Web clipping portlet. After connecting to the site, see the SSL Secured icon displayed in status bar of the browser.
  2. Click File > Properties.
  3. Click the Certificates button to display the Certificate dialog box.
  4. Select the Certification Path tab.
  5. Select the topmost root certificate entry in the tree. Name of the certificate that export from the browser.
  6. Click OK to close the dialog box.
  7. Click Tools > Internet Options from the main menu of the browser.
  8. Select the Content tab.
  9. Click the Certificates button to display the Certificate dialog box.
  10. Select the Trusted Root Certification Authorities tab.
  11. Select the root that was previously identified.
  12. Click the Export button to open the Certificate Export Wizard dialog.
  13. Click Next in the wizard dialog box.
  14. Select Base-64 encoded X.509 (.CER) as the format to use for the certificate file.
  15. Click Next.
  16. Type the file name that you want to use for the certificate file.
  17. Click Browse, and select the directory to contain the .CER file.
  18. Click Next.
  19. Click Finish.
  20. Copy the .CER file that you created, and place it into the java\jre\lib\security directory, where WebSphere Application Server was installed. For example, if WebSphere Application Server was installed in C:\WebSphere\appserver, the .CER file must be saved in the C:\WebSphere\appserver\java\jre\lib\security directory. To verify that you have located the correct directory, find the cacerts file in the same directory.
  21. Restart WebSphere Application Server, and attempt to connect to the secure site with the Web Clipping portlet again.

 

Problem: SOCKS proxies are not supported for the Web Clipping Editor

Under the Web Clipper Editor Advanced options, there is no option in the Modify firewall options page to differentiate an HTTP proxy from a SOCKS proxy. This is because only HTTP proxies are supported for the Web Clipping Editor.

Solution: When modifying the firewall options for a Web Clipping portlet, use only HTTP proxies for your Proxy hostname and Proxy port.

 

Problem: Dynamic refreshing of existing Web Clipping portlet settings is not supported

When editing or modifying the settings of an existing Web Clipping portlet, the changes are not immediately reflected if it is already running on a page.

Solution: In order to ensure that your modified Web Clipping portlet settings take effect, restart your portal.

 

Problem: Empty content in the Web Clipping portlet

When clicking on a link in a Web Clipping portlet, you might find that no content appears.

Solution:

Ensure that:

  1. The destination of the link is secured.
  2. The URL in the link is valid.
  3. The destination of the link is located in the internet and the proxy setting is correct.
  4. The URL in the link is not redirected.

If you work through those steps and content still does not appear, the problem could be:

  1. The destination of the link contains some functions of Javascript which are not supported by the Web Clipper Editor in this release.
  2. The destination of the link returns applets or embedded objects like Flash which are not supported by the Web Clipper Editor in this release.

 

Problem: When using the Web Clipping Editor through Mozilla, users cannot select HTML images

Mozilla is not supported for creating Web Clipping portlets.

Solution: Use either Microsoft Internet Explorer or Netscape Navigator as your browser when creating Web Clipping portlets.

 

Problem: When using the Web Clipping Editor through Opera, the clear button does not function properly

Opera is not supported for creating Web Clipping portlets.

Solution: Use Microsoft Internet Explorer as your browser when creating Web Clipping portlets.

 

Problem: Receive portlet unavailable error when browsing a portlet created with the Web Clipping Editor

If you have a Web clipped portlet that contains a link which requires a third party authentication certificate, you might receive the following error when following that link: "This portlet is unavailable. If the problem persists, please contact the portal administrator"

Solution: Apply the WebSphere Application Server fix that updates the JSSE code. This fix can be found on the WebSphere Application Server Fix Pack and Fixes disc for your operating system. The fix is as follows:

/manualfixes/WAS_Security_07-07-2003_JSSE_cumulative_Fix.jar

Comments: If users will be clipping content from secure sites using https:// or sites that have links to secure sites using https:// this fix should be applied.

 

Problem: Web Clipping does not work with Machine Translation

If you use a clipping that is in a locale other than the local locale of WebSphere Portal, you get a wrong drop-down translation menu with EnableViewerInitiatedTranslation according to the locale of WebSphere Portal, but not according to the locale of the clipping portlet.

Solution: If you wish to use machine translation to translate the clipping, set the portlet parameter ContentLanguage with the locale of the clipping portlet.

 

See also

Home |

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.