The Isolation Method property of iViews defines how an iView or page is encoded in a page. It determines whether iView content is collected at the server or at the client, and how the Page Builder component displays the content. The value of this property can affect the performance of a page.
iViews can have one of the following isolation methods:
The Pumped isolation method is no longer supported, although it still appears (as Pumped-Deprecated ) in the Isolation Method iView property menu. For complete information, see SAP Note 739121 .
Assigning an Isolation Method
The Isolation Method property is in the Load category; you access it through the Properties editor. For information about editing properties, see Editing Object Properties .
Both the URL and the embedded isolation method are suitable for iViews with relatively heavy content.
Use the embedded isolation method for:
iViews that are tightly coupled (with POM events) and need to refresh themselves, through the server, according to mutual client actions
iViews that are presented as navigation nodes outside a page
Regular iViews that will not be assigned to a Web Dynpro page
When a regular iView with an embedded isolation method is assigned to a Web Dynpro page, a warning message is generated and the isolation method is changed on-the-fly to URL.
Use the URL isolation method for:
Presenting content that is external to the portal server
Regular iViews that will be assigned to a Web Dynpro page
After selecting an isolation method, check the iView functionality in its full portal environment
Pages also have isolation methods, which additionally affect the behavior of the page. Set pages to the embedded isolation method to avoid additional server requests for fetching the pages.
Adding a Page to a Page
It is possible for a portal page to contain another page, which itself contains iViews. If you add a page containing isolated iViews to a page containing embedded iViews, an event on the outer page will affect the isolated iViews on the inner page.
Pages Containing Only Embedded iViews
The issue discussed here applies to embedded pages containing embedded iViews. Generally, when a Web page link is activated, a browser, by default, replaces the current page with whatever content was retrieved.
When coding the links that retrieve external content, developers should make sure that the links open a new window rather than replace the work area and navigation area of the portal framework.
Since developers cannot control the behavior of links that retrieve content from external sources, they should bring external content to a page that is defined as isolated.
Using links to internal content (other iViews on the portal) should not have this effect, as long as the link is generated with standard portal runtime (PRT) URL generation API. For more information, see Triggering Navigation .