This chapter describes the various ways to integrate content into a WebCenter Portal Framework application: content data controls, Content Management Interoperability Services (CMIS) REST APIs, Content Presenter, and the Documents tool. 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 Portal Framework application using any of the following methods (for more information, see the references at the end of this chapter):
Documents task flows and components offer a variety of formats to display folders and files, including wikis and blogs, on a page in a Portal Framework application. You can choose the task flows appropriate for your application to provide features for accessing, adding, and managing folders and files; configuring and viewing file and folder properties; and searching file and folder content in WebCenter Content, Oracle Portal, or SharePoint content repositories.
Note:
The availability of SharePoint as a content repository requires the installation of the SharePoint adapter, as described in Section 25.2.3.1, "Installing the Oracle WebCenter Adapter for SharePoint." Administration for SharePoint is performed using WLST commands, not Oracle Enterprise Manager Fusion Middleware Control Console.Using documents task flows and document components (such as links, previews, and images), you can add content to the application, and also provide end users with content and documents task flows built into the application to manage, display, and search documents at runtime.
Content Presenter enables you to precisely customize the selection and presentation of content in a Portal Framework application. The Content Presenter task flow is available only when the connected content repository is WebCenter Content and your WebCenter Portal administrator has completed the prerequisite configuration. With Content Presenter, you can select a single item of content, contents under a folder, a list of items, query for content, or select content based on the results of a Personalization Conductor scenario, and then select a template to render the content on a page in a Portal Framework application. Content Presenter has no dependency on the Documents tool for adding or managing the content it displays.
CMIS REST APIs surface and manage content in WebCenter Content.
Content data controls use JCR adapters to enable read-only access to content in a WebCenter Content, Oracle Portal, or SharePoint content repository, and maintain tight control over the way the content displays in a Portal Framework application.
This functionality is available primarily for backward compatibility with prior releases, and for requirements outside the capability of Content Presenter or the Documents tool and its task flows.
Table 24-1 provides a comparative overview of these methods to help you select the most appropriate method for your needs.
Table 24-1 Methods of Integrating Content into a Framework Application
| Content Data Controls | Content Management REST APIs | Content Presenter | Documents Tool | |
|---|---|---|---|---|
|
Repository |
|
|
|
|
|
Content Types |
|
|
|
|
|
Content Display |
|
|
|
WebCenter Content only:
|
|
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 WebCenter Content only:
|
|
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 WebCenter Content repository |
No Oracle Site Studio support |
The following chapters provide information that you will need for any method you use:
"Managing Content Repositories" in Administering Oracle WebCenter Portal to configure and manage content repositories used by WebCenter Portal applications.
Chapter 25, "Configuring Content Repository Connections" to configure and edit content repository connections that provide access to decentralized content.
The following chapter provides information about using content data controls:
Chapter 26, "Working with Content Data Controls" to use Java Content Repository (JCR) data controls to enable read-only access to any content repository.
The following manual provides information about using CMIS (Content Management Interoperability Services) REST APIs:
The following chapters provide information about using Content Presenter:
Chapter 29, "Adding Content Task Flows and Document Components to a Portal Page"
"Publishing Content Using Content Presenter" in Building Portals with Oracle WebCenter Portal to work with content at runtime in WebCenter Portal applications.
The following chapters provide information about using the Documents tool, which includes the documents task flows, document components (links, inline frames, and images), wikis, and blogs:
Chapter 29, "Adding Content Task Flows and Document Components to a Portal Page"
"Working with Content in a Portal" in Building Portals with Oracle WebCenter Portal to work with content at runtime in WebCenter Portal applications.