Embedded Isolation Method 
When you set an iView's Isolation Method property to Embedded, you create a simple HTML iView whose content is written "as is" into the page HTML. As a result, a content-loading event in the iView, such as launching a link or submitting a form, refreshes the whole page.
Features and Implications
iView content is collected at the server side and sent to the client with the entire page.
A request from the client to the server causes the server to reload all the iViews on the page.
This prevents unnecessary requests to the server
Performance may be degraded
Page Builder has no control over the appearance of the iView content.
Content is presented "as is" in the browser
The size of the iView depends on the content
iView height is not controlled by the page
The page does not add scrollbars to iViews
Supports both server-side and client-side events.
Limitations
A page may contain several form-type iViews. One iView may lose the information in its input fields when another form on the page is submitted.
Content external to the portal server requires special handling.
Caution
Content-loading events on embedded iViews cause the loss of iViews that are in iFrames. It is not recommended that you put embedded and isolated iViews on the same page.
EP5.0 iViews are URL-isolated iViews. To support EP5.0 iViews, add them to pages that contain only URL-isolated iViews.
Note
A regular portal iView that is set to Embedded should not be placed on a Web Dynpro page. If it is, a warning message is generated and its isolation method is changed automatically to URL.