URL iView Properties

Use

You configure the properties of URL iViews using the Property Editor (see Editing Object Properties ). This topic discusses some of the important properties available in URL iViews. The basic properties listed below also apply to XML iViews.

Basic Properties

Property Name	Description
`Fetch Mode`	Determines how the portal page builder handles the retrieval of data from the information source of a URL iView. It extends the functionality of the iView isolation method of type `URL Isolated` (see above). The valid values of this property are: `Client-side` or `Server-side` . By default, the fetch mode setting is `Client-side` . By default, you should apply the "server-side" fetch method to URL iViews. Although the "server-side" method may show a marginal reduction in performance in comparison to the "client-side" method, server-side fetching does however provide the following advantages: Uses the portal server's caching mechanism Supports user-defined parameters in the URL (created in the URL iView Editor) Supports both GET and POST request method ( `Client-side` supports only the GET request method) Supports user mapping Supports both HTTP and HTTPS protocols Supports automatic height-sizing of the iView at runtime Supports the iView capture functionality You should use client-side fetching as a fall-back option when an iView is unable to display content using the server-side fetch mode. These problems are often associated with encoding and scripting issues at the source or in the URL. For example, the server-side fetch mode does not support URLs that are automatically redirected to another URL. Caution When the fetch mode is set to `Client-side` , the proxy settings of the client's browser are used. When the fetch mode is set to `Server-side` , the proxy settings of the portal server are applied instead (see Defining a Proxy Server for the Portal ). To prevent iView runtime errors, make sure the proxy settings are defined either on the portal server or users' browsers, or both. Note XML iViews (see Creating XML iViews ) are automatically configured to use the "server-side" fetch method. This property is hidden in XML iViews and its setting cannot be changed.
`Height Type`	Determines how the height size of iViews is set. The valid values of this property are: `Automatic` , `Fixed` or `Full-page` . If the fetch mode (see above) is set to `Client-side` , then the automated height size calculation of iViews displayed in a portal page is not supported ( `Height Type` = `Automatic` ). In this case, you must set an iView height that is fixed or full-page. If the fetch mode is set to `Server-side` , then automated height size calculation of iViews is supported.

Property Name

Description

Fetch Mode

Determines how the portal page builder handles the retrieval of data from the information source of a URL iView. It extends the functionality of the iView isolation method of type URL Isolated (see above).

The valid values of this property are: Client-side or Server-side . By default, the fetch mode setting is Client-side .

By default, you should apply the "server-side" fetch method to URL iViews. Although the "server-side" method may show a marginal reduction in performance in comparison to the "client-side" method, server-side fetching does however provide the following advantages:

Uses the portal server's caching mechanism
Supports user-defined parameters in the URL (created in the URL iView Editor)
Supports both GET and POST request method ( Client-side supports only the GET request method)
Supports user mapping
Supports both HTTP and HTTPS protocols
Supports automatic height-sizing of the iView at runtime
Supports the iView capture functionality

You should use client-side fetching as a fall-back option when an iView is unable to display content using the server-side fetch mode. These problems are often associated with encoding and scripting issues at the source or in the URL. For example, the server-side fetch mode does not support URLs that are automatically redirected to another URL.

Caution

When the fetch mode is set to Client-side , the proxy settings of the client's browser are used. When the fetch mode is set to Server-side , the proxy settings of the portal server are applied instead (see Defining a Proxy Server for the Portal ). To prevent iView runtime errors, make sure the proxy settings are defined either on the portal server or users' browsers, or both.

Note

XML iViews (see Creating XML iViews ) are automatically configured to use the "server-side" fetch method. This property is hidden in XML iViews and its setting cannot be changed.

Height Type

Determines how the height size of iViews is set. The valid values of this property are: Automatic , Fixed or Full-page .

If the fetch mode (see above) is set to Client-side , then the automated height size calculation of iViews displayed in a portal page is not supported ( Height Type = Automatic ). In this case, you must set an iView height that is fixed or full-page.

If the fetch mode is set to Server-side , then automated height size calculation of iViews is supported.

Note

Isolation Method is a property available to all iViews. The property determines how iViews are loaded and displayed in portal pages, which ultimately affects page performance in the portal. For more information, see Isolation Method of iViews .

The isolation mode for URL iViews is always defined as URL ; and you cannot modify the setting. URL iViews are therefore always displayed within an iFrame in any portal page. This property may be hidden in the Property Editor when editing URL iViews.

Advanced Properties

The following properties allow you to improve the runtime response time of URL iViews in the portal and to control some aspects of their runtime behavior. The properties are grouped in the Web Page Area category.

Note

These properties are relevant in the following instances only:

The iView content is displayed in its source format. The rendering type must be defined as Keep Source Formatting . See Defining the Look and Feel of the iView Content .
The iView content displays a captured area, and not the entire Web page. See Selecting the Capture Area .

Caution

We recommend you first test the iView using the default settings. Change the default values only if necessary.

Property Name	Description
`Maintain Web site functionality`	Allows you to determine whether or not scripts originating in a Web page are kept active in the iView at runtime. Usually, you only need to disable this feature if a script is harmful to the rendition of an iView in the portal. Note that seemingly non-harmful Java-coded features, such as `onClick` (a basic JavaScript command commonly used in Web sites), may also be disruptive. When this option is disabled, the performance of the iView is reduced, since the HTML code of the iView content must be filtered and modified before it is sent to the client's browser for display.
`Adjust to structural changes in site`	Allows you to instruct the portal to verify if structural changes have taken place in the source Web page. If so, an attempt is made to adjust the captured area, as needed. You should only disable this feature if you are sure the structural layout of the Web site or Web-based application, upon which the iView is based, will not change (for example, static intranet Web pages). There is also no need to enable it if you are displaying an entire Web page. This verification process is time-consuming, thus when disabled, the retrieval of the iView and its display at runtime is faster.
`Open iView links in new window`	Allows you to force all hyperlinks displayed in the iView to open in a new browser window when clicked at runtime. When you enable this option, the performance of the iView is reduced, since the HTML code of the iView content must be filtered and modified before it is sent to the client's browser for display. When this option is not enabled, links are opened as coded in the source Web page.
`Remove client events from Web site content`	Allows you to remove client events, such as `onClick` and `onMouse` , from the iView before it is displayed at runtime. When you enable this option, the performance of the iView is reduced, since the HTML code of the iView content must be filtered and modified before it is sent to the clients' browser for display. You should only enable this feature if you know for certain that the Web page, upon which the iView is based, contains client events that you want to disable.
`Check scripts in Web site content`	Allows you to suppress any potential JavaScript errors that may result when Web content is running in an iView. When you enable this option, all JavaScript elements are wrapped in `[try...catch]` statements at runtime. If exceptions are thrown at runtime they are neutralized before being displayed in the iView. This process is time-consuming. When disabled, the retrieval of the iView and its display in the client's portal is faster. You should only disable this feature if you are sure the Web page, upon which the iView is based, does not contain scripts at all or contains compatible scripts.
`Always Detect Character Encoding of Web Page*`	For detailed information, see Character Encoding of Web Page .
`Force Detection of Character Encoding*`	For detailed information, see Character Encoding of Web Page .

* Property is not available to XML iViews.