Preface

This manual describes how to use Oracle Portal (Oracle Portal) to build a portal, and how to use that portal to your best advantage. Assuming that all configuration tasks have been completed (see the Oracle Fusion Middleware Administrator's Guide for Oracle Portal for those tasks), this book assists with considering how best to construct your portal, how to build the portal with attractive and professional looking pages, how to load those pages with content, and how to make that content easy for others to find.

Note:

For the portable document format (PDF) version of this manual, when a URL breaks onto two lines, the full URL data is not sent to the browser when you click it. To get to the correct target of any URL included in the PDF, copy and paste the URL into your browser's address field. In the HTML version of this manual, you can click on a link to directly display its target in your browser.

Intended Audience

This manual is divided into four volumes:

Volume 1, Understanding Oracle Portal, provides information about moving around the portal, setting personal options, and locating content within the portal's pages.
Volume 2, Planning Your Portal, provides information about creating a page group framework and preparing the portal for others to populate with content.
Volume 3, Creating Pages and Designing the Layout and Appearance of Pages, provides information about Oracle Portal's basic and advanced page design features for creating pleasing, useful pages.
Volume 4, Working with Content and Advanced Page Design Features, provides information about using WebDAV with Oracle Portal, translating portal content, setting up an approval workflow, and enhancing your portal's performance. These volume also contains appendixes that supplement the information provided in all four volumes.

There are many definitions of the term user as it pertains to this manual. Each volume is dedicated to one or more particular sets of users. These sets are described in the next few sections.

What Is a Public User?

Public users are users who access a portal without logging in. When users first access a portal, they access it as public users, whether or not they have the ability to log in. Public users can view any page that has been marked as Public by the page manager, but they cannot edit the content of pages. Volume 1 defines the concept of a portal and assists public users with locating content and viewing pages.

What Is an Authenticated User?

Authenticated users are users who have logged in to a portal. Authenticated users can edit and delete the objects they create, such as pages, styles, and content. Authenticated users can also have additional responsibilities or be granted additional specific privileges on objects created by other users. An authenticated user's privileges may vary from object to object.

Authenticated users will use Volume 1 for basic things like learning to navigate the portal and locating portal content, and Volume 3 for things like creating pages and editing and deleting objects.

What Is a Content Contributor? A content contributor is an authenticated user who can add content to a page. The person who creates (or manages) a page decides who can contribute to the page. There are two levels of contributor:

The page privilege Manage Content

Contributors with this privilege can add new items to the page and edit and delete any item in the page. Such users can also add and remove portlets.
The page privilege Manage Items With Approval

This page privilege is available when approvals and notifications are enabled for the page's page group. Contributors with this privilege can add items to the page and edit any existing item. Revisions and additions are not published in the portal (that is, displayed to other users) until they are approved. Contributors can track the items waiting for approval through the My Approval Status portlet. Such users can also personalize page content.

What Is a Page Designer? A page designer (also known as page manager) is an authenticated user with the page privilege Manage on a page. A user with this privilege can perform any action on the page and can create sub-pages under the page. The page designer is often responsible for designing the layout (or region configuration) of the page and assigning privileges on the page to other users (for example, to determine who can add content to the page). The scope of a page designer's control over a page may be limited if the page is based on a template.

Page designers will find Volume 3 most useful for completing their tasks.

What Is a Page Group Administrator? A page group administrator is an authenticated user who has full privileges on the structure, style, and content of a page group, and can view, edit, and delete any object in that page group, including pages and styles that are otherwise secure from unprivileged users. A page group administrator can also assign page group privileges to other users.

When a page group is created, the user who created the page group is automatically assigned as its administrator. This user can also edit the page group to assign a different page group administrator.

Volume 2 assists page group administrators in establishing the page group structure and choosing settings that are appropriate for the target user base.

Note:

A page group administrator cannot create new page groups or users. These are tasks performed by the portal administrator.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.

Conventions

The following text conventions are used in this document:

Convention	Meaning
boldface	Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic	Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
`monospace`	Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Preface

Intended Audience

Documentation Accessibility

Related Documents

Conventions