!--a11y-->
Notes on Important iView
Properties 
This section discusses a few default iView properties that are common to most iView types, and refers you to topics which discuss them in more detail. They are brought to your attention since they have an overall effect on portal performance and stability.
See also URL iView Properties.
The isolation method of an iView determines how an iView is technically integrated into a portal page at run time.
For more
information, see
Isolation Method of
iViews.
iViews have several
cache-related properties, which determine whether an iView retrieves data from
its data source or from a cached store. Retrieving existing data from a cached
store decreases the fetch time of an iView, thus improving the performance of
a portal page when displayed at run time. The frequency an iView needs to
update its cached store depends on the dynamics of each data source; therefore
it is possible to specify the cache properties per iView. For information on
these properties, see
Caching.
In addition, the
portal has a global setting that also affects client-side browser caching. For
more information, see
Administering
Application Caching.
The Work Distribution Topic property enables you to group several iViews and map them to specific cluster zones. By defining zones in your cluster environment and mapping portal content to these zones, you can isolate certain part of the portal which may be problematic.

For example, all iViews with Work Distribution Topic value = a can be mapped to zone z1, all iViews with Work Distribution Topic value = b can be mapped to zone z2, and so on.
For more
information, see
Workload
Distribution.