Create a Web clipping portlet

To create a Web clipping portlet, select...

Administration | Portlet Management | Web clipping

For each Web clipping portlet that created with the Web Clipping Editor, we 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.

Methods for clipping the contents of a page within the Web clipping portlet:

HTML clipping	Display a rendered view of the contents from the specified URL, displaying it as seen a browser. To select the elements of the page to clip, move your mouse over the element and click on it. The element will be highlighted to indicate that is has been clipped. To clear it, click it again. This is not supported for iFrames.
Keep all content	Default. No clipping is performed on the contents from the specified URL. The contents are brought through untouched. This method is useful to create a portlet to proxy some external content without filtering it.
Text clipping	Allows the contents from the specified URL to be clipped based on a pair of strings whose occurrences within the content denote the boundaries of the portions of content to be retained. The pair of strings is specified by the user, the first string being the start string and the second the end string. When selected, the contents from the specified URL are searched for literal occurrences of the start string followed by the end string. The portions of content between such occurrences are presented to the user, allowing the user to select which occurrences should be retained. This is not supported for iFrames.

Access to the HTML source of the clipped document is not necessary. Once the Web clipping portlet is created, we 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, we 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 we add a header name that is already used by the clipping portlet, the newly added header will be ignored.

Parent: Web clipping