Create a Web clipping portlet

To help you perform Web clipping on sites that you want to include in portlets, WebSphere Portal enables you to create Web clipping portlets to specify how you want to tailor the content of particular documents. To create a Web clipping portlet, select Web clipping under Portlet Management in the Administration tab of the portal.

For each Web clipping portlet that you create with the Web Clipping Editor, you can indicate the URL of the Web site being clipped and other settings that influence how the content is clipped, including the level of authentication required to access the site and whether URL rewriting is performed on the clipped output. There are three methods for clipping the contents of a page within the Web clipping portlet:

Access to the HTML source of the clipped document is not necessary. Once the Web clipping portlet is created, you can administer it as you would any other portlet.

To remove a Web clipping portlet, use the Delete capability of the Web Clipping Editor portlet. This action removes all relevant information. If you delete a Web clipping portlet manually, be sure to delete both the portlet itself and its associated portlet application through Portal Administration. Otherwise, you will not be able to create another Web clipping portlet using the same name.


Add Client Header parameters

After creating a new Web clipping portlet, you can add parameters using Manage Portlets to specify extra headers that will be sent with each HTTP request for that clipping portlet. This is useful when the clipping portlet needs to connect to a backend web server that requires extra information to be sent as part of the request. The following table provides required format examples for header parameters:

Header value Description
header1.name headerName
header1.value headerValue
header2.name headerName
header2.value headerValue

These name and value pairs will then be read by the clipper and sent as extra headers on EVERY HTTP request. In the case where a clipping portlet has been deployed on a page and then the extra header parameters are added later, the portal will have to be restarted so that the clipping portlet picks up the new parameter values. If you add a header name that is already used by the clipping portlet, the newly added header will be ignored.


Parent

Use Web clipping to import content

 


+

Search Tips   |   Advanced Search