Skip Headers
Oracle® Fusion Middleware Developer's Guide for Oracle WebCenter Portal
11g Release 1 (11.1.1.7.0)

Part Number E10148-20
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

25 Introduction to Integrating and Publishing Content

There are several ways to integrate content into a WebCenter Portal: Framework application. The method you choose is dependent on the requirements of the application and how you want to expose content to end users.

You can integrate content into a Framework application using any of the following methods (for more information, see the references at the end of this chapter):

Table 25-1 provides a comparative overview of these methods to help you select the most appropriate method for your needs.

Table 25-1 Methods of Integrating Content into a Framework Application


Content Data Controls Content Management REST APIs Content Presenter Documents Service

Repository

Content Server

Oracle Portal

SharePoint

Content Server

Content Server

Content Server

Oracle Portal

SharePoint

Content Types

Folders and content files.

Folders and content files with support for metadata properties.

Folders and content files with support for metadata properties.

Supports Oracle Site Studio region definitions-based content.

Folders and content files.

Content Server only: supports folder and content file metadata properties.

Content Display

Surface content using ADF render components: ADF Go Link, ADF Go Button, ADF Image, and ADF inline frame functions.

Surface content using REST APIs and custom client or server side application code.

Surface content through single item selection, by folder, and by query results.

Task flow-based component intended primarily for rendering content.

Surface content through single item selection, by folder, and by query results.

Surface content in display templates: either built-in templates or custom display templates developed in JDeveloper.

Reuse Oracle Site Studio display templates for Site Studio content.

Supports WebCenter Personalization Services Conductor scenario (query results).

Task flow-based components intended primarily for collaborating and managing content.

Content Server only:

  • Document preview

  • View links

  • View images

  • View file information (properties, version history)

  • View metadata

Content Management

None.

Manage content using REST APIs and custom client or server side application code.

Create, update, delete folders and content files and associated metadata fields.

In-context contribution editing for HTML and Site Studio content.

Manage content through graphical user interface.

Create, update, delete folders and content files.

Content Server only:

  • Manage associated metadata properties

  • Item-level security

  • Oracle Workflow (WebCenter Portal: Spaces only)

  • View metadata

Benefits

Standard JCR API integrates with many different content repositories.

Flexible REST-based APIs useful for client-side style development.

Flexible display using display templates.

Oracle Site Studio support.

Choice of task flows to provide easy UI access to managing content.

Limitations

Read-only content.

No Oracle Site Studio support.

Content must reside in Oracle Content Server repository.

No Oracle Site Studio support.

Content must reside in Content Server repository.

No Oracle Site Studio support.


The following chapters provide information that you will need for any method you use:

The following chapter provides information about using content data controls:

The following manual provides information about using CMIS (Content Management Interoperability Services) REST APIs:

The following chapters provide information about using Content Presenter:

The following chapters provide information about using the Documents service, which includes the Documents service task flows, document components (links, inline frames, and images), wikis, and blogs: