Portal Content Objects 

The infrastructure of the enterprise portal includes a number of different objects, such as roles, worksets, pages, and iViews. The different administration tools for the portal access these objects and enable them to be edited.

All these objects together form the content object model. Objects have certain features in common:

·        The objects can be accessed and viewed with a content browser. This browser is the Portal Catalog.

·        The objects can be maintained with a common user interface. The common interface is the Portal Content Studio.

·        The objects have certain properties, depending on the object type. These properties can be for example title, ID, master language, height or code link.

·        The objects can be transported. Also read Transport of Content Objects.

·        Permissions can be assigned to the objects using Access Control Lists. Also see Portal Permissions.

The following content objects are used in the portal:

Object	Link to the Description
iView and iView template	For more information see iViews and Creating iViews.
Page layout	For more information see Page Layouts.
Worksets	For more information see Roles and Worksets.
Roles	For more information see Roles and Worksets.
System and system templates	For more information see System Objects and System Templates.

The objects are related, for example:

·        An iView can contain a reference to a system from which it reads certain data at runtime.

·        A page can contain certain iViews

·        A role can contain references to worksets, iViews and pages as parent object.