Click Browse next to Deployment Archive, select the

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. Managing Content Repositories 11-31 – For the active connection in WebCenter Spaces, the Root Folder and Application Name values are used to create the seed data in the WebCenter Spaces repository, to enable storage of the Space-related data. – The Root Folder value is used as the name for the root folder within the content repository under which all Spaces content is stored. For the Root Folder value, you must specify a content repository folder that does not yet exist. Use the format: foldername. For example: MyWebCenterSpaces. The Root Folder cannot be , the root itself, and it must be unique across different WebCenter applications. The folder specified is created for you when the WebCenter application starts up. Invalid entries include: , foldername, foldernamesubfolder. – The WebCenter Spaces application within this content repository must have a unique name. For example: MyWCS. The name must begin with an alphabetical character, followed by any combination of alphanumeric characters or the underscore character. The name specified here is also used to name document-related workflows, as follows: applicationNameWorkflowName and applicationNameWorkflowStepName. When naming workflows, only the first 14 characters of the Application Name are used. The Application Name value is used for the following: To separate data when multiple WebCenter Spaces applications share the same content repository and should be unique across applications. As the prefix to the seeded workflow and workflow steps. The Application Name is also used as the prefix to the seeded workflow and workflow steps. As the name of the security group. As the prefix for the role the name format is applicationNameUser To stripe users permissions on accounts for the particular WebCenter Spaces application. To stripe default attributes for the particular WebCenter Spaces application. For information about security groups and roles, see Managing Security and User Access for Content Server. For information about folders, see Folders and WebDav Administration Guide. These guides are available at http:download.oracle.comdocscdE10316_01owc.htm .

11.6.2 Registering Content Repositories Using Fusion Middleware Control

To register an Oracle Content Server, Oracle Portal, and file system content repository:

1. Log in to Fusion Middleware Control and navigate to the home page for

WebCenter Spaces or the WebCenter Portal application: ■ Section 6.2, Navigating to the Home Page for WebCenter Spaces ■ Section 6.3, Navigating to the Home Page for WebCenter Portal Applications Note: Although the Root Folder and Application Name values change, the old root content repository folder still appears in search results, like any other root folder in Oracle Content Server.