Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Troubleshoot Web Clipping portlet
The following section lists known problems and solutions related to Web clipping.
- Problem: Error message says a certificate is missing when connecting to a secure site
- Problem: SOCKS proxies are not supported for the Web Clipping Editor
- Problem: No content appears in a portlet
- Problem: Receive portlet unavailable error when browsing a portlet created with the Web Clipping Editor
- Problem: Web Clipping does not work with Machine Translation
- Problem: Web Clipping does not support :
- Problem: Web Clipping does not show the selection clipped with HTML clipping.
- Problem: Text is merged in the upper right corner of the screen
Problem: Error message says a certificate is missing when connecting to a secure site
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...
- 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, you should see the SSL Secured icon displayed in status bar of the browser.
- Click File > Properties.
- Click the Certificates button to display the Certificate dialog box.
- Select the Certification Path tab.
- Select the topmost root certificate entry in the tree. This is the name of the certificate that you will need to export from the browser.
- Click OK to close the dialog box.
- Click Tools > Internet Options from the main menu of the browser.
- Select the Content tab.
- Click the Certificates button to display the Certificate dialog box.
- Select the Trusted Root Certification Authorities tab.
- Select the root that was previously identified.
- Click the Export button to open the Certificate Export Wizard dialog.
- Click Next in the wizard dialog box.
- Select Base-64 encoded X.509 (.CER) as the format to use for the certificate file.
- Click Next.
- Type the file name that you want to use for the certificate file.
- Click Browse, and select the directory to contain the .CER file.
- Click Next.
- Click Finish.
- 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, you should find the cacerts file in the same directory.
- 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: No content appears in a portlet
When clicking on a link in a Web Clipping portlet, you might find that no content appears.
Solution:
Ensure that:
- The destination of the link is secured.
- The URL in the link is valid.
- The destination of the link is located in the internet and the proxy setting is correct.
- The URL in the link is not redirected.
If you work through those steps and content still does not appear, the problem could be:
- The destination of the link contains some functions of Javascript which are not supported by the Web Clipper Editor in this release.
- 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: 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 want to use machine translation to translate the clipping, set the portlet parameter ContentLanguage with the locale of the clipping portlet.
Problem: Web Clipping does not support ":"
The Web Clipping portlet does not support entering a single character ":" in the URL to clip field.
Solution: Do not use ":" in the URL to clip field.
Problem: Web Clipping does not show the selection clipped with HTML clipping.
Transcoding must be enabled in order for HTML clipping to work. See Creating a Web clipping portlet for more information.
Problem: Text is merged in the upper right corner of the screen
The merged text is a limitation with the Web Clipping portlet due to the position:absolute css attribute. The Web Clipping portlet does not modify any CSS information in the clipped site, which causes the merged text.