What You Should Know About Microsoft SharePoint Server Installation

Managing Content Repositories 11-29 returned by the Federated Portal Adapter, and thus are not visible in Oracle WebCenter: ■ Seeded page groups: – Oracle Portal repository. – Oracle Portal design-time pages. ■ Pages of the following types: – Mobile. – URL. – Navigation pages. ■ Items of the following types: – Navigation items. – PLSQL items. – Portlet. – Portlet instance. – URL items. – Mobile items. – Page links. – Item links. ■ Items defined as: – Expired. – Hidden.

11.5 File System Prerequisites

This section discusses the prerequisites for a file system content repository in the following subsections: ■ Section 11.5.1, File System - Security Considerations ■ Section 11.5.2, File System - Limitations in WebCenter

11.5.1 File System - Security Considerations

All operations are executed as the system user under which the JVM is running and therefore inherit its permissions. Caution: File system connections must not be used in production or enterprise application deployments. This feature is provided for development purposes only. Connections created through the file system adapter can be used during the development of WebCenter Portal applications using Oracle JDeveloper. WebCenter Spaces applications do not support file system connections. 11-30 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

11.5.2 File System - Limitations in WebCenter

File system connections must not be used in production or enterprise application deployments, and search capabilities are limited and slow due to the absence of an index. This feature is provided for development purposes only.

11.6 Registering Content Repositories

This section contains the following subsections: ■ Section 11.6.1, What You Should Know About Registering Content Repositories for WebCenter Spaces Section 11.6.2, Registering Content Repositories Using Fusion Middleware Control ■ Section 11.6.3, Registering Content Repositories Using WLST

11.6.1 What You Should Know About Registering Content Repositories for WebCenter Spaces

Consider the following when registering Oracle Content Server repositories for WebCenter Spaces: ■ At start up, WebCenter Spaces creates seed data if it does not already exist in the primaryactivedefault repository for WebCenter Spaces. ■ For WebCenter Spaces, an Oracle Content Server repository connection must always be provided as a primary connection, even if another repository such as Microsoft SharePoint is made available. ■ A user name with administrative rights for the Oracle Content Server instance is required Content Administrator. This user will be used to create and maintain folders for WebCenter Spaces content and manage content access rights. The default content administrator is sysadmin. Administrative privileges are required for this connection so that operations can be performed on behalf of WebCenter users. ■ Root Folder and Application Name values: – Oracle does not recommend changing the Root Folder and Application Name values. However, if you change the Root Folder value after configuring and running WebCenter Spaces, then you must also change the Application Name value, and vice versa. That is, you must change both values Root Folder and Application Name to unique values if the WebCenter Spaces application already contains the seed data. When you change these values, the existing seed data is not renamed in the Oracle Content Server repository. Instead, new seed data is created using the new values, when you start the application. Once the application is started, new WebCenter Spaces data is created under the new Root Folder and existing data under the old Root Folder is no longer available. This means that the Documents service will now be disabled in Spaces where the Documents service was previously enabled, prior to changing the Root Folder.