Managing Content Repositories 11-35
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 Developers 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.
Table 11–5 Cont. Oracle Content Server Connection Parameters
Field Description
11-36 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter
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
Users 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 Users
Guide for Oracle WebCenter.
■
Editing advanced document properties.
For more information, see Working with File Properties in Oracle Fusion Middleware Users Guide for Oracle WebCenter.
■
Viewing folder and file workflow details.
For more information, see “Viewing Workflow Assignments in Oracle Fusion Middleware Users Guide for Oracle WebCenter.
■
Previewing files in a slide viewer.
For more information, see Opening a File in Oracle Fusion Middleware Users 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 Users 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. Table 11–5
Cont. Oracle Content Server Connection Parameters Field
Description
Managing Content Repositories 11-37
Client Security Policy Enter the client security policy to be used when the RIDC Socket
Type
is JAX-WS. For example:
oraclewss11_saml_token_with_message_protection_serv ice_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.
Table 11–5 Cont. Oracle Content Server Connection Parameters
Field Description
11-38 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter
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. 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 machines 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: jdbcMyPortalDS
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.
Table 11–6 Cont. Connection Details - Oracle Content Server - Cache Details
Element Description
Managing Content Repositories 11-39
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 Users Guide for Oracle WebCenter.
11.6.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
■
Microsoft SharePoint -
createJCRSharePointConnection 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=1.
See Section 11.7, 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 Changing the Active or Default Content Repository Connection
WebCenter applications support multiple content repository connections but only one content repository connection can be designated the active or default connection.
In WebCenter Spaces, the active connection becomes the default back-end repository for Space and Home Space documents and the repository must be an Oracle Content
Server. The active connection is also used as the default connection for the Documents service and Content Presenter task flows.
For other WebCenter applications, the active connection becomes the default connection for Content Presenter, Document Manager, Document List Viewer, and Recent
Documents, and so on. When no specific connection details are provided for these task flows, the default active connection is used.
This section contains the following subsections:
■
Section 11.7.1, Changing the Active or Default Content Repository Connection Using Fusion Middleware Control
■
Section 11.7.2, Changing the Active or Default Content Repository Connection Using WLST
11.7.1 Changing the Active or Default Content Repository Connection Using Fusion Middleware Control
To change the active or default content repository connection:
Note: To start using the new active connection you must restart the
managed server on which the WebCenter application is deployed. See Starting and Stopping WebLogic Managed Servers Using the
Command Line in the Oracle Fusion Middleware Administrators Guide.
11-40 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter
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.7.2 Changing the Active or Default Content Repository Connection Using WLST
Use the following WLST commands with isPrimary=1 to designate an existing content repository connection as the default connection:
■
Oracle Content Server - setJCRContentServerConnection
■
File System - setJCRFileSystemConnection
■
Oracle Portal - setJCRPortalConnection
■
Microsoft SharePoint -
setJCRSharePointConnection See also,
listJCRSharePointConnections 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 .
Note: To start using the new active connection you must restart the
managed server on which the WebCenter application is deployed. See, Starting and Stopping WebLogic Managed Servers Using the
Command Line in the Oracle Fusion Middleware Administrators Guide.
Managing Content Repositories 11-41
11.8 Modifying Content Repository Connection Details
This section contains the following subsections:
■
Section 11.8.1, Modifying Content Repository Connection Details Using Fusion Middleware Control
■
Section 11.8.2, Modifying Content Repository Connection Details Using WLST
■
Section 11.8.3, Modifying Cache Settings for Content Presenter
11.8.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.8.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.
11-42 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter
To configure a particular connection as the active or default connection, set isPrimary=1. See
Section 11.7, 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.8.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_projectsapplicationswc_domaincustom.webcente r.spaces.fwkAPP-INFclasses directory. For WebCenter Portal applications,
developers must create the content-coherence-cache-config.xml file in the application EAR classpath or servers 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 as11gr1wcwebcentermodulesoracle.webcenter.content
.integration_11.1.1content-app-lib.ear. The sample file location is: content-app-lib.earAPP-INFclassessample-content-coherence-ca
che-config.xml file. You can copy this file and rename it to content-coherence-cache-config.xml, and then set the values to meet
customers deployment needs.
Table 11–9 describes the cache entries in this file.
Example 11–1 Sample Coherence Configuration File
DOCTYPE cache-config SYSTEM cache-config.dtd cache-config
caching-scheme-mapping cache-mapping
cache-namerepo.ucm.nodeUidCache.cache-name scheme-nameContentNodeCachesscheme-name
cache-mapping cache-mapping
cache-namerepo.ucm.nodePathToUidCache.cache-name scheme-nameContentNodeCachesscheme-name
cache-mapping cache-mapping
cache-namerepo.ucm.securityInfoCache.cache-name scheme-nameContentNodeCachesscheme-name
cache-mapping cache-mapping
cache-namerepo.ucm.typeNameCache.cache-name scheme-nameContentTypeCachesscheme-name
cache-mapping cache-mapping
cache-namerepo.ucm.typeNamesCache.cache-name scheme-nameContentTypeCachesscheme-name
Note: To start using the updated active connection details, you
must restart the managed server on which the WebCenter application is deployed. See Starting and Stopping WebLogic Managed Servers
Using the Command Line in the Oracle Fusion Middleware Administrators Guide.
Managing Content Repositories 11-43
cache-mapping cache-mapping
cache-namebinaryCache.cache-name scheme-nameContentBinaryCachesscheme-name
cache-mapping cache-mapping
cache-namerepo.ucm.searchCriteriaCache.cache-name scheme-nameContentSearchCachesscheme-name
cache-mapping cache-mapping
cache-name repo.ucm.indexedFieldsCache.cache-name scheme-nameContentSearchCachesscheme-name
cache-mapping cache-mapping
cache-namerepo.ucm.securityUserCache.cache-name scheme-nameContentSecurityCachesscheme-name
cache-mapping cache-mapping
cache-namerepo.ucm.profileTriggerValueCache.cache-name scheme-nameContentProfileCachesscheme-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-nameContentNodeCachesscheme-name
expiry-delay1mexpiry-delay high-units100high-units
local-scheme local-scheme
scheme-nameContentTypeCachesscheme-name expiry-delay30mexpiry-delay
high-units50high-units local-scheme
local-scheme scheme-nameContentBinaryCachesscheme-name
expiry-delay1mexpiry-delay high-units100000high-units
unit-calculator class-scheme
class-namecom.tangosol.net.cache.SimpleMemoryCalculatorclass-name class-scheme
unit-calculator local-scheme
local-scheme scheme-nameContentSearchCachesscheme-name
expiry-delay5mexpiry-delay high-units50high-units
local-scheme local-scheme
scheme-nameContentSecurityCachesscheme-name expiry-delay10mexpiry-delay
high-units50high-units local-scheme
local-scheme scheme-nameContentProfileCachesscheme-name
