11 Managing Content Repositories

11.2.1 Oracle Content Server 11g - Installation

Oracle Content Server 11g is installed as a part of Oracle Universal Content Management (Oracle UCM). Oracle UCM is a product of Oracle Enterprise Content Management Suite, which is an Oracle Fusion Middleware component. For information about upgrading Oracle Content 10g release 3 to Oracle Content Server 11g, see the Oracle Fusion Middleware Upgrade Guide for Oracle Enterprise Content Management Suite at http://download.oracle.com/docs/cd/E14571_01/doc.1111/e16451/upgrade_ecm.htm.

While installing Oracle Content Server, you may also install Oracle Inbound Refinery (Oracle IBR). Oracle IBR is a conversion server that manages file conversions for electronic assets such as documents, digital images, and motion videos. It also provides thumbnail functionality for documents and images and storyboarding for videos. You can use Oracle IBR to convert content items stored in Oracle Content Server.

For information about installing Oracle Content Server, see the section "Oracle Content Server - Installation" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter.

11.2.2 Oracle Content Server 11g - Configuration

This section includes the following subsections:

• Section 11.2.2.1, "Configuring Oracle Content Server 11g for All WebCenter Applications"

• Section 11.2.2.2, "Configuring Oracle Content Server 11g to Support Item Level Security in All WebCenter Applications"

• Section 11.2.2.3, "Configuring Security Between Oracle Content Server 11g and WebCenter Portal Applications"

11.2.3 Oracle Content Server - Security Considerations

Please consider the following while configuring security for Oracle Content Server:

• To secure identity propagation, you must configure SSL on Oracle Content Server. This is required when Oracle Content Server and your WebCenter application are not on the same system or the same trusted private network. For information, see Section 31.7, "Securing the WebCenter Spaces Connection to Oracle Content Server with SSL."

• Oracle Content Server must be configured to use the same identity store LDAP server as WebCenter Spaces. For information, see Section 28.1, "Reassociating the Identity Store with an External LDAP Server."

11.2.4 Oracle Content Server - Limitations in WebCenter

None.

11.3.1 Oracle Portal - Installation

For information on installing Oracle Portal, see Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer.

11.3.2 Oracle Portal - Configuration

Oracle Portal must be up-to-date with all the latest patches. For additional information about patches, see the product release notes. See also Oracle Fusion Middleware Administrator's Guide for Oracle Portal.

11.3.3 Oracle Portal - Security Considerations

None.

11.3.4 Oracle Portal - Limitations in WebCenter

Oracle Portal integration with Oracle WebCenter is read-only. It is not possible to create content in the portal from Oracle WebCenter.

You can expose Oracle Portal pages in WebCenter through the Federated Portal Adapter by publishing them as portlets in Oracle Portal. The following are not 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.4.1 File System - Security Considerations

All operations are executed as the system user under which the JVM is running and therefore inherit its permissions.

11.4.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.5.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 primary/active/default repository for WebCenter Spaces.

• 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.

    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.

  • 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/, /foldername/subfolder.

  • 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: <applicationName><WorkflowName> and <applicationName><WorkflowStepName>. 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.com/docs/cd/E10316_01/owc.htm.

11.5.2 Registering Content Repositories Using Fusion Middleware Control

To register a 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"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter Portal applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Service Configuration page, select Content Repository.

4. To connect to a new content repository, click Add (Figure 11-8).

   Figure 11-8 Configuring Content Repository Connections

   
   

5. Enter a unique name for this connection, specify the content repository type, and indicate whether this connection is the active (or default) connection for the application. See Table 11-4.

   Table 11-4 Manage Content Repository Connections

   Field	Description
   Connection Name	Enter a unique name for this content repository connection. The name must be unique (across all connection types) within the WebCenter application.
   Repository Type	Choose the type of repository you want to connect to. Select one of the following: Oracle Content Server - an Oracle Universal Content Management repository. See Section 11.2, "Oracle Content Server Prerequisites". Oracle Portal - an Oracle Portal content repository. See Section 11.3, "Oracle Portal Prerequisites". File System - a computer file system. See Section 11.4, "File System Prerequisites". Caution: File system connections must not be used in production or enterprise application deployments. This feature is provided for development purposes only. (WebCenter Spaces) If you are setting up the back-end content repository for WebCenter Spaces, that is, the repository used by WebCenter Spaces to store Space-related documents, you must select Oracle Content Server.
   Active Connection	Select to make this the default or primary content repository for your WebCenter application. You can connect your WebCenter application to multiple content repositories; all connections are used. One connection must be designated the default (or active) connection. Do one of the following: For WebCenter Spaces: Select to make this the active connection, that is, the back-end repository that WebCenter Spaces uses to store Space-related documents. The active connection must be to an Oracle Content Server. If this is the active connection for WebCenter Spaces, some additional configuration is required -- see Section 11.5.1, "What You Should Know About Registering Content Repositories for WebCenter Spaces." For WebCenter Portal applications: Select to make this the active connection; that is, the default connection for Content Presenter, Document Manager, Document List Viewer, and Recent Documents task flows. When no specific connection details are provided for these task flows, this default (also called primary, active) connection is used. Deselecting this option does not disable the content repository connection. If a content repository is no longer required, you must delete the connection.

   
   

6. (For the active connection in WebCenter Spaces only.) Enter additional details for the WebCenter Spaces repository. For information, see Section 11.5.1, "What You Should Know About Registering Content Repositories for WebCenter Spaces."

7. Enter connection details for the content repository. For detailed parameter information, see:

   • Table 11-5, "Oracle Content Server Connection Parameters"

   • Table 11-6, "Connection Details - Oracle Content Server - Cache Details"

   • Table 11-7, "Oracle Portal Connection Parameters"

   • Table 11-8, "File System Connection Parameters"

   Table 11-5 Oracle Content Server Connection Parameters

   Field	Description
   RIDC Socket Type	Specify whether Oracle Content Server connects on the content server listener port or the Web server filter, and whether the listener port is SSL enabled. Choose from: Socket - Uses an intradoc socket connection to connect to the Oracle Content Server. The client IP address must be added to the list of authorized addresses in the Oracle Content Server. In this case, the client is the machine on which Oracle WebCenter is running. Socket SSL - Uses an intradoc socket connection to connect to the Oracle Content Server that is secured using the SSL protocol. The client's certificates must be imported in the server's trust store for the connection to be allowed. This is the most secure option, and the recommended option whenever identity propagation is required (for example, in WebCenter Spaces). Web - Uses an HTTP(S) connection to connect to the Oracle Content Server. JAX-WS - Uses an HTTP(S) connection to connect to the Oracle Content Server. For WebCenter Spaces, the Web option is not suitable for the active connection, that is, the back-end Oracle Content Server repository that is being used to store Space-related documents because it does not allow identity propagation.
   Server Host	Enter the host name of the machine where the Oracle Content Server is running. For example: mycontentserver.mycompany.com Server Host is required when the RIDC Socket Type is set to Socket or Socket SSL.
   Server Port	Enter the port on which the Oracle Content Server listens: Socket - Port specified for the incoming provider in the server. Socket SSL - Port specified for the sslincoming provider in the server. This property corresponds to the IntradocServerPort setting in the Content Server configuration file, which defaults to port 4444. Server Port is required when the RIDC Socket Type is set to Socket or Socket SSL.
   Web URL	Enter the Web server URL for the Oracle Content Server. Use the format: http://hostname:portnumber/web_root/plugin_root For example: http://mycontentserver/cms/idcplg Web URL is applicable when the RIDC Socket Type is set to Web.
   Web Service URL	Enter the Web service URL required to connect to Oracle Content Server when using the JAX-WS protocol. Use the format: http://hostname:port/web_root For example: http://myhost.com:9044/idcnativews Web Service URL is applicable when RIDC Socket Type is set to JAX-WS.
   Connection Timeout (ms)	Specify the length of time allowed to log in to Oracle Content Server (in milliseconds) before issuing a connection timeout message. If no timeout is set, there is no time limit for the login operation.
   Authentication Method	Choose from: Identity Propagation - Oracle Content Server and the WebCenter application use the same identity store to authenticate users. (WebCenter Spaces) Identity propagation is required on the active connection for WebCenter Spaces, that is, for the content repository being used to store Space-related documents. External Application - An external application authenticates users against the Oracle Content Server. Select this option if you want to use public, shared, or mapped credentials. See also, "Setting Security for the Documents Service" in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter. If an external application is used for authentication, use the Associated External Application drop down list to identify the application. If the application you want is not listed, select Create New to define the external application now.
   Web Server Context Root	Enter the Web server context root for Oracle Content Server. Use the format /<context_root>. For example, /cs. When specified, several Oracle Universal Content Management (UCM) features based on iFrame are available in the WebCenter application. This includes: Associating a content profile with files when uploading new or updated files to Oracle Content Server. For more information, see "Uploading New Files" and "Uploading a New Version of an Existing File" in Oracle Fusion Middleware User's Guide for Oracle WebCenter. Using the document review functionality available in Oracle AutoVue. For more information, see "Reviewing and Collaborating on Documents Using AutoVue" in Oracle Fusion Middleware User's Guide for Oracle WebCenter. Editing advanced document properties. For more information, see "Working with File Properties" in Oracle Fusion Middleware User's Guide for Oracle WebCenter. Viewing folder and file workflow details. For more information, see “Viewing Workflow Information" in Oracle Fusion Middleware User's Guide for Oracle WebCenter. Previewing files in a slide viewer. For more information, see "Opening a File" in Oracle Fusion Middleware User's Guide for Oracle WebCenter. Site Studio integration Without OHS (and WebContextRoot configuration), it is still possible to create or edit Site Studio content from within Content Presenter, but the create and edit actions launch new browser windows (or tabs) rather than opening within the Content Presenter task flow. For more information, see "Using Content Presenter to Create or Edit Oracle Site Studio Content" in Oracle Fusion Middleware User's Guide for Oracle WebCenter. The Web Server Context Root property is only applicable when the Authentication Method is set to Identity Propagation. Note: Specifying the Web Server Context Root is an indicator that the WebCenter application is front-ended by OHS. If you specify the Web Server Context Root and do not connect through OHS, a 404 error occurs while you attempt to edit the advanced metadata in the Document Viewer, upload using a profile, or click Details for a content item in a workflow in a Space. For information about setting up OHS to front-end WebCenter applications, see Appendix B, "Oracle HTTP Server Configuration for WebCenter". If your WebCenter application is connected to multiple UCM servers, Oracle recommends that each UCM server has a unique Web Server Context Root so that OHS re-direction works correctly.
   Associated External Application	Select the external application used to authenticate users against the Oracle Content Server. Associated External Application is applicable when RIDC Socket Type is set to Web and also when the RIDC Socket Type is Socket or Socket SSL (with Authentication Method set to External Application).
   Client Security Policy	Enter the client security policy to be used when the RIDC Socket Type is JAX-WS. For example: oracle/wss11_saml_token_with_message_protection_service_policy Leave this field blank if your environment supports Global Policy Attachments (GPA).
   Administrator User Name	Enter a user name with administrative rights for this Oracle Content Server instance. This user will be used to fetch content type information based on profiles and track document changes for cache invalidation purpose. Defaults to sysadmin.
   Administrator Password	Enter the password for the Oracle Content Server administrator.
   Key Store Location	Specify the location of key store that contains the private key used to sign the security assertions. The key store location must be an absolute path. For example: D:\keys\keystore.xyz Key Store Location is required when the RIDC Socket Type is set to Socket SSL.
   Key Store Password	Enter the password required to access the keystore. For example: T0PS3CR3T Key Store Password is required when the RIDC Socket Type is set to Socket SSL.
   Private Key Alias	Enter the client private key alias in the keystore. The key is used to sign messages to the server. The public key corresponding to this private key must be imported in the server keystore. Ensure that the alias does not contain special characters or white space. For example: enigma Private Key Alias is required when the RIDC Socket Type is set to Socket SSL.
   Private Key Password	Enter the password to be used with the private key alias in the key store. For example: c0d3bR3ak3R Private Key Password is required when the RIDC Socket Type is set to Socket SSL.

   
   

   Table 11-6 Connection Details - Oracle Content Server - Cache Details

   Element	Description
   Cache Invalidation Interval (minutes)	Specify the frequency between checks for external Oracle Content Server content changes (in minutes). WebCenter automatically clears items that have changed from the cache. The default is 0 which means that cache invalidation is disabled. The minimum interval is 2 minutes.
   Maximum Cached Document Size (bytes)	Enter a maximum cacheable size (in bytes) for Oracle Content Server binary documents. Documents larger than this size are not cached by WebCenter. The default is 102400 bytes (100K). Tune this value based on your machine's memory configuration and the types of binary documents that you expect to cache.

   
   

   Table 11-7 Oracle Portal Connection Parameters

   Field	Description
   Data Source Name	Enter the JNDI DataSource location used to connect to the portal. For example: jdbc/MyPortalDS The datasource must be on the server where the WebCenter application is deployed.
   Connection Timeout (ms)	Specify the length of time allowed to log in to Oracle Portal (in milliseconds) before issuing a connection timeout message. If no timeout is set, there is no time limit for the login operation.
   Authentication Method	Specify how to authenticate users against Oracle Portal. Choose from: Identity Propagation - Select this option when the WebCenter application and Oracle Portal both use the same user identity store. External Application - Use an external application to authenticate users against Oracle Portal. Select this option if you want to use public, shared, or mapped credentials. If an external application is used for authentication, use the Associated External Application dropdown list to identify the application.
   Associated External Application	Associate Oracle Portal with an external application. External application credential information is used to authenticate Oracle Portal users.You can select an existing external application from the dropdown list, or click Create New to configure a new external application now.

   
   

   Table 11-8 File System Connection Parameters

   Field	Description
   Base Path	Enter the full path to a folder on a local file system in which your content is placed. For example: C:\MyContent Caution: File system content must not be used in production or enterprise application deployments. This feature is provided for development purposes only.

   
   

8. Click OK to save this connection.

9. Click Test to verify if the connection you created works. For a successful connection, the Test Status message displays the advice that to start using the new (active) connection, you must restart the managed server on which the WebCenter application is deployed.

The registered connections are now available to Documents service and Content Presenter task flows, which you can add to pages in WebCenter Spaces or WebCenter Portal applications. See also, "Working with the Documents Service" in the Oracle Fusion Middleware User's Guide for Oracle WebCenter.

11.5.3 Registering Content Repositories Using WLST

Use the following WLST commands to register new content repository connections:

• Oracle Content Server - createJCRContentServerConnection

• File System - createJCRFileSystemConnection

• Oracle Portal - createJCRPortalConnection

For command syntax and examples, see the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To configure a particular connection as the default connection, set isPrimary='true'. See Section 11.6, "Changing the Active (or Default) Content Repository Connection".

For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

11.6.1 Changing the Active (or Default) Content Repository Connection Using Fusion Middleware Control

To change the active (or default) content repository connection:

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"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter Portal applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, select Content Repository.

   The Manage Content Repository Connections table indicates the current active connection (if any).

4. Select the connection you want to become the active (or default) connection, and then click Edit.

5. Select the Active Connection checkbox.

6. Click OK to update the connection.

7. Click Test to verify if the connection you activated works. For a successfully activated connection, the Test Status message displays the advice that to start using the updated connection you must restart the managed server on which the WebCenter application is deployed.

11.6.2 Changing the Active (or Default) Content Repository Connection Using WLST

Use the following WLST commands with isPrimary='true' to designate an existing content repository connection as the default connection:

• Oracle Content Server - setJCRContentServerConnection

• File System - setJCRFileSystemConnection

• Oracle Portal - setJCRPortalConnection

For command syntax and examples, see the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To subsequently disable a default content repository connection, run the same WLST command with isPrimary='false'. Connection details are retained but the connection is no longer named as the primary connection in adf-config.xml.

For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

11.7.1 Modifying Content Repository Connection Details Using Fusion Middleware Control

To update content repository connection details:

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"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter Portal applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose Content Repository.

4. Select the connection name, and click Edit.

5. Edit connection details, as required. For detailed parameter information, see:

   • Table 11-5, "Oracle Content Server Connection Parameters"

   • Table 11-7, "Oracle Portal Connection Parameters"

   • Table 11-8, "File System Connection Parameters"

6. Click OK to save your changes.

7. Click Test to verify if the updated connection works. For a successfully updated connection, the Test Status message displays the advice that to start using the updated connection, you must restart the managed server on which the WebCenter application is deployed.

11.7.2 Modifying Content Repository Connection Details Using WLST

Use the following WLST commands to edit content repository connections:

• Oracle Content Server - setJCRContentServerConnection

• File System - setJCRFileSystemConnection

• Oracle Portal - setJCRPortalConnection

For command syntax and examples, see the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

To configure a particular connection as the active (or default) connection, set isPrimary='true'. See Section 11.6, "Changing the Active (or Default) Content Repository Connection".

For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

11.7.3 Modifying Cache Settings for Content Presenter

The content management code for Content Presenter, the Content Management Interoperability Services (CMIS) REST APIs, and so on, are shipped out of the box with local (in-memory) caches. This code does not use Coherence. You can enable Coherence for caches in the content-coherence-cache-config.xml file. For WebCenter Spaces this file is stored in the ORACLE_HOME/user_projects/applications/wc_domain/custom.webcenter.spaces.fwk/APP-INF/classes/ directory. For WebCenter Portal applications, developers must create the content-coherence-cache-config.xml file in the application (EAR) classpath or server's system classpath.

A sample Coherence configuration file, as shown in Example 11-1, is provided within the content-app-lib.ear file. This EAR file is located at: ORACLE_HOME/as11gr1wc/webcenter/modules/oracle.webcenter.content.integration_11.1.1/content-app-lib.ear). The sample file location is: /content-app-lib.ear/APP-INF/classes/sample-content-coherence-cache-config.xml file. You can copy this file and rename it to content-coherence-cache-config.xml, and then set the values to meet customer's deployment needs. Table 11-9 describes the cache entries in this file.

<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
  <caching-scheme-mapping>
    <cache-mapping>
      <cache-name>repo.ucm.nodeUidCache.*</cache-name>
      <scheme-name>ContentNodeCaches</scheme-name>
    </cache-mapping>
    <cache-mapping>
      <cache-name>repo.ucm.nodePathToUidCache.*</cache-name>
      <scheme-name>ContentNodeCaches</scheme-name>
    </cache-mapping>
    <cache-mapping>
      <cache-name>repo.ucm.securityInfoCache.*</cache-name>
      <scheme-name>ContentNodeCaches</scheme-name>
    </cache-mapping>
    <cache-mapping>
      <cache-name>repo.ucm.typeNameCache.*</cache-name>
      <scheme-name>ContentTypeCaches</scheme-name>
    </cache-mapping>
   <cache-mapping>
      <cache-name>repo.ucm.typeNamesCache.*</cache-name>
      <scheme-name>ContentTypeCaches</scheme-name>
    </cache-mapping>
    <cache-mapping>
      <cache-name>binaryCache.*</cache-name>
      <scheme-name>ContentBinaryCaches</scheme-name>
    </cache-mapping>
    <cache-mapping>
      <cache-name>repo.ucm.searchCriteriaCache.*</cache-name>      <scheme-name>ContentSearchCaches</scheme-name>
    </cache-mapping>
    <cache-mapping>
      <cache-name> repo.ucm.indexedFieldsCache.*</cache-name>
      <scheme-name>ContentSearchCaches</scheme-name>
    </cache-mapping>
    <cache-mapping>
      <cache-name>repo.ucm.securityUserCache.*</cache-name>
      <scheme-name>ContentSecurityCaches</scheme-name>
    </cache-mapping>
    <cache-mapping>
      <cache-name>repo.ucm.profileTriggerValueCache.*</cache-name>
      <scheme-name>ContentProfileCaches</scheme-name>
    </cache-mapping>
  </caching-scheme-mapping>
  <caching-schemes>
<!--    The following schemes are all local.  For a clustered deployment,
    a distributed, replcated, or other clustered scheme is recommended.
    See Coherence documentation for more information.
    -->
    <local-scheme>
      <scheme-name>ContentNodeCaches</scheme-name>
      <expiry-delay>1m</expiry-delay>
      <high-units>100</high-units>
    </local-scheme>
    <local-scheme>
      <scheme-name>ContentTypeCaches</scheme-name>
      <expiry-delay>30m</expiry-delay>
      <high-units>50</high-units>
    </local-scheme>
    <local-scheme>
      <scheme-name>ContentBinaryCaches</scheme-name>
      <expiry-delay>1m</expiry-delay>
      <high-units>100000</high-units>
      <unit-calculator>
        <class-scheme>
          <class-name>com.tangosol.net.cache.SimpleMemoryCalculator</class-name>
        </class-scheme>
      </unit-calculator>
    </local-scheme>
    <local-scheme>
      <scheme-name>ContentSearchCaches</scheme-name>
      <expiry-delay>5m</expiry-delay>
      <high-units>50</high-units>
    </local-scheme>
   <local-scheme>
      <scheme-name>ContentSecurityCaches</scheme-name>
      <expiry-delay>10m</expiry-delay>
      <high-units>50</high-units>
    </local-scheme>
   <local-scheme>
      <scheme-name>ContentProfileCaches</scheme-name>
      <expiry-delay>1h</expiry-delay>
      <high-units>100</high-units>
    </local-scheme>
    <!--
    <class-scheme>
      <scheme-name>ContentDisabledCaches</scheme-name>
      <class-name>com.tangosol.util.NullImplementation$NullMap</class-name>
    </class-scheme>
    -->
  </caching-schemes>
</cache-config>

11.8.1 Deleting Content Repository Connections Using Fusion Middleware Control

To delete a content repository connection:

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"

2. Do one of the following:

   • For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.

   • For WebCenter Portal applications - From the Application Deployment menu, choose WebCenter > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose Content Repository.

4. Select the connection name, and click Delete.

5. To effect this change you must restart the managed server on which the WebCenter application is deployed.

11.8.2 Deleting Content Repository Connections Using WLST

Use the WLST command deleteConnection to remove a content repository connection. For command syntax and examples, see "deleteConnection" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

11.9.1 Setting Connection Properties for the WebCenter Spaces Content Repository Using Fusion Middleware Control

To set content repository connection properties:

1. Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the WebCenter Portal application. See Section 6.2, "Navigating to the Home Page for WebCenter Spaces".

2. From the WebCenter menu, choose Settings > Service Configuration.

3. From the list of services on the WebCenter Services Configuration page, choose Content Repository.

4. Select the connection name, and click Edit.

5. (For the active connection in WebCenter Spaces only.) Set connection properties for the WebCenter Spaces repository. For information, see Section 11.5.1, "What You Should Know About Registering Content Repositories for WebCenter Spaces."

6. Click OK to save your changes.

7. To start using the updated (active) connection properties, you must restart the managed server on which the WebCenter application is deployed.

11.9.2 Setting Connection Properties for the WebCenter Spaces Content Repository Using WLST

The following commands are valid only for the WebCenter Spaces application to view, set, and delete properties for the Oracle Content Server repository that is being used by WebCenter Spaces to store Space and Home Space documents:

• listDocumentsSpacesProperties

• setDocumentsSpacesProperties

• deleteDocumentsSpacesProperties

For command syntax and detailed examples, see the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".

11.10.1 Testing Oracle Content Server Connections

To verify a connection of the socket type web, log in to the Web interface of Oracle Content Server as administrator. You can obtain the URL of a socket type connection through Fusion Middleware Control as follows:

1. In Fusion Middleware Control, from the WebCenter menu, choose Settings and select Service Configuration (Figure 11-9).

   Figure 11-9 Fusion Middleware Control WebCenter Menu

   
   

2. On the Manage Content Repository Connections page, select the connection and click Edit (Figure 11-10).

   Figure 11-10 Manage Content Repository Connections Page

   
   

3. On the Edit Content Repository Connection page, copy the Web URL (Figure 11-11).

   Note:

   Remove the /idcplg/ suffix from the URL before using it.

   The URL format is: http://host_name/web_root/ For example: http://mycontentserver/cms/

   Figure 11-11 Edit Content Repository Connection Page

   
   

11.10.2 Testing Oracle Portal Connections

To verify the full state of an Oracle Portal connection:

1. In the Oracle WebLogic Administration Console, under Domain Structure, expand Services > JDBC, then double-click Data Sources (Figure 11-12).

   Figure 11-12 Oracle WebLogic Administration Console

   
   

2. On the Summary of JDBC Data Sources page, select the data source you intend to test (Figure 11-13).

   Figure 11-13 Summary of JDBC Data Sources Page

   
   

3. In the Settings for datasource_name section, select the tabs Monitoring, then Testing. Select the data source target server, then click Test Data Source to test the connection (Figure 11-14).

   Figure 11-14 Data Source Settings Section