Oracle WebCenter enables content integration through:
Content Repository data controls, which enable read-only access to a content repository, and maintain tight control over the way the content displays in a custom WebCenter application.
The Documents service, which enables users to view and manage documents and other types of content in your organization's content repositories.
Content Presenter, available through the Documents service, enables end users to select content in a variety of ways and then display those items using available display templates. A Content Presenter task flow can be added during development of a custom WebCenter application, or can be added to editable pages at runtime through the Documents service.
This chapter describes how to configure and manage content repositories used by WebCenter applications. For more information about managing and including content in WebCenter applications, see:
"Integrating Content" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter to configure content repository connections that provide access to decentralized content, and learn how to create custom display templates to integrate and publish decentralized content in your WebCenter application using Content Presenter, as well as how to use Java Content Repository (JCR) controls to enable read-only access to a content repository.
"Integrating the Documents Service" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter to integrate the Documents service in custom WebCenter applications to provide end users with a user-friendly interface to manage, display, and search documents at runtime.
Working with the Documents Service" in Oracle Fusion Middleware User's Guide for Oracle WebCenter to work with the Documents service and task flows at runtime in WebCenter applications.
Note:
Any content repository configuration changes that you make through Fusion Middleware Control or using WLST are not dynamic; you need to restart the managed server on which the WebCenter application is deployed for your changes to take effect. See Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments".This chapter contains the following sections:
Section 11.1, "What You Should Know About Content Repository Connections"
Section 11.4, "Changing the Active (or Default) Content Repository Connection"
Section 11.5, "Modifying Content Repository Connection Details"
Section 11.7, "Setting Connection Properties for the WebCenter Spaces Content Repository"
The content of this chapter is intended for Fusion Middleware administrators (users granted the Admin
or Operator
role through the Oracle WebLogic Server Administration Console). See Section 1.8, "Understanding Administrative Operations, Roles, and Tools".
WebCenter users need to store, publish, and share files. The Documents service provides content management and storage capabilities for WebCenter applications, including content upload, file and folder creation and management, file check out, versioning, and so on. To do this, the Documents service requires at least one content repository connection (WebCenter applications can support multiple content repository connections) to be made active:
WebCenter Spaces - In WebCenter Spaces, every group space and personal space has its own document folder, unique to its parent space. The back-end service providing this functionality is Oracle Content Server. When a content repository is made active (see Section 11.4, "Changing the Active (or Default) Content Repository Connection"), it becomes the default content repository and additional properties become available for configuration. WebCenter Spaces requires the default content repository to be Oracle Content Server. Additionally, administrators may connect WebCenter Spaces to other content repositories that WebCenter Spaces may use.
Other WebCenter applications - When a content repository is made active (see Section 11.4, "Changing the Active (or Default) Content Repository Connection"), Documents service task flows use that content repository in instances where no specific connection details are provided. There is no particular requirement on the default content repository used.
When Oracle Content Server is the content repository (required for WebCenter Spaces), the identity store configured for the Documents service must be LDAP-based, not a file-based jazn store, and Oracle Content Server must be connected to that same identity store.
Just like other service connections, post-deployment, content repository connections are registered and managed through Fusion Middleware Control or using the WLST command-line tool. Connection information is stored in configuration files and in the MDS repository. For more information, see Section 1.3.5, "Oracle WebCenter Configuration Considerations".
Always use Fusion Middleware Control or WLST command-line tool to review and configure back-end services for WebCenter applications. Any changes that you make to WebCenter applications, post-deployment, are stored in the Oracle Metadata Service (MDS) repository as customizations.
Once connection details are defined, WebCenter users can expose the content of the connected content repositories through several ADF Faces components, such as <af:image>
, <af:inlineFrame>
, and <af:goLink>
, and built-in Documents service task flows (Content Presenter, Document Manager, Document List Viewer, and Recent Documents). For more information, see "Working with Page Content" and "Working with the Documents Service" in Oracle Fusion Middleware User's Guide for Oracle WebCenter.
Oracle WebCenter's support of the JCR 1.0 open document standard enables integration with multiple back-end content stores. Oracle WebCenter supports the following content repositories: Oracle Content Server, Oracle Portal, and the file system.
Caution:
File system connections must not be used in production or enterprise application deployments. This feature is provided for development purposes onlyPrerequisities for each content repository are described in the following sections:
This section discusses the prerequisites for an Oracle Content Server content repository in the following subsections:
Section 11.2.1.3, "Oracle Content Server - Security Considerations"
Section 11.2.1.4, "Oracle Content Server - Limitations in WebCenter"
Oracle Content Server 10.1.3.5.1 installation is integrated with Oracle WebCenter installation, which is included in the Universal Content Management (UCM) media shipped with Oracle WebCenter. Alternatively, you can choose to install Oracle Content Server separately from the UCM media and then integrate it with Oracle WebCenter, provided certain configuration requirements are satisfied. Before installing Oracle Content Server, ensure that Oracle HTTP Server is installed on the same system.
For information about installing Oracle Content Server, see the Oracle Fusion Middleware Installation Guide for Oracle WebCenter.
After installing Oracle Content Server, you must configure the server to use the same LDAP-based identity store that Oracle WebCenter has been configured to use. You can optionally configure Oracle Content Server for using full-text search and index and Secure Sockets Layer (SSL) for secure identity propagation. Table 11-1 lists the various configuration tasks and specifies whether these tasks are mandatory or optional.
See Also:
"Administering Content Server" in Getting Started With Content Server at:http://download-west.oracle.com/docs/cd/E10316_01/cs/cs_doc_10/getting_started/index.htm
Table 11-1 Oracle WebCenter-Specific Postinstallation Configuration Tasks for Oracle Content Server
Task | Mandatory/Optional |
---|---|
Mandatory |
|
Optional |
|
Optional |
Note:
If you intend to manage Oracle Content Server through a browser or add content on the server through WebDAV, then you must configure Oracle Content Server to work with Oracle HTTP Server.Both Oracle Content Server and Oracle WebCenter must be configured to use the same LDAP-based identity store and this identity store must be supported by the user or role API. To enable communication between Oracle Content Server and LDAP-based identity store, you must add a JPS user provider configured for this identity store.
To add a JPS user provider to Oracle Content Server:
Stop Oracle Content Server and the Admin Server. For information, see the section "Oracle Content Server - Installation" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter.
See Also:
"Starting and Stopping a Content Server" in Getting Started With Content Server at:http://download-west.oracle.com/docs/cd/E10316_01/cs/cs_doc_10/getting_started/index.htm
Update the Oracle Content Server's JPS configuration file, jps-config.xml
:
cd CONTENT_SERVER_HOME
/config
Add a serviceInstanceEntry
which looks like Example 11-1.
Note:
Ensure that all entries in the service instance match your LDAP server.
The security.principal.key
and security.principal.alias
values (in bold) used in Example 11-1 must match the input you provide when running the script. See Step 3.
Some specific properties like idstore.type
may vary from Example 11-1, depending on the type of identity store being configured. For information on other permissible values, see the Appendix "OPSS System and Configuration Properties" in Oracle Fusion Middleware Security Guide.
Example 11-1 serviceInstanceEntry in Oracle Content Server's jps-config.xml
<serviceInstance name="idstore.oid" provider="idstore.ldap.provider"> <property name="subscriber.name" value="dc=example,dc=com"/> <property name="idstore.type" value="OID"/> <property name="security.principal.key" value="ldap.credential"/> <property name="security.principal.alias" value="JPS"/> <property name="ldap.url" value="ldap://ldaphost:389"/> <extendedProperty> <name>user.search.bases</name> <values> <value>cn=users,dc=example,dc=com</value> </values> </extendedProperty> <extendedProperty> <name>group.search.bases</name> <values> <value>cn=groups,dc=example,dc=com</value> </values> </extendedProperty> <property name="username.attr" value="cn"/> <property name="user.login.attr" value="cn"/> <property name="groupname.attr" value="cn"/> </serviceInstance>
Ensure that the <jpsContext>
entry in the jps-config.xml
file refers to this new serviceInstance
, that is, idstore.oid
and not idstore.ldap
:
<jpsContext name="default"> <serviceInstanceRef ref="idstore.oid"/>
Run the new script to set up the credentials for idstore.oid
in the credential store:
cd CONTENT_SERVER_HOME
/custom/FusionLibraries/tools
Note:
Ensure that the script is executable, for example,chmod +x run_credtool.sh
.On Windows, run the run_credtool.cmd
script. If platform is Linux, run the ./run_credtool.sh
script.
When the script prompts for input, defaults are shown in []
.
Enter the input on the line following the prompt. The following extracts show you which defaults to take:
On Windows:
input] Alias: [JPS] [input] Key: [ldap.credential] [input] User Name:cn=user name [input] Password:password [input] JPS Config: [WC_ORACLE_HOME\ucm\custom\FusionLibraries\tools/../../../config/jps-config.xml]
On Linux:
[input] Alias: [JPS] [input] Key: [ldap.credential] [input] User Name:cn=user name [input] Password:password [input] JPS Config: [WC_ORACLE_HOME/ucm/custom/FusionLibraries/tools/../../../config/jps-config.xml]
Note:
The Alias and Key input must match the values used in the serviceInstancesecurity.principal.alias
and security.principal.key
respectively.Restart Oracle Content Server and the Admin Server. For information, see the section "Oracle Content Server - Installation" in Oracle Fusion Middleware Installation Guide for Oracle WebCenter.
See Also:
"Starting and Stopping a Content Server" in Getting Started With Content Server at:http://download-west.oracle.com/docs/cd/E10316_01/cs/cs_doc_10/getting_started/index.htm
Ensure that the JpsUserProvider
is available in Oracle Content Server:
Start the Oracle Content Server console and log on as an administrator.
From the Administration menu, select Providers.
Ensure that the jpsuser
provider is listed on the Providers page and its status is good in the Connection State column.
If an ldapuser
provider is enabled, disable it.
To disable the ldapuser
provider, on the Providers page, in the Action column, click the info link next to the provider. In the new page that opens, under the JPS User Provider Information section, click the Disable button.
By default, the database used by Oracle Content Server is set up to provide metadata-only searching and indexing capabilities. However, you can modify the default configuration of SQL Server, Oracle, and DB2 to additionally support full-text searching and indexing. Configuring full-text searching and indexing capabilities is optional, but advisable. For full-text search, it is recommended that you use the OracleTextSearch
option.
For information about enabling full-text searching and indexing, see the "Setting Up Database Search and Indexing" appendix in the Content Server Installation Guide for Microsoft Windows or Content Server Installation Guide for UNIX available at:
If Oracle Content Server and the WebCenter application in which you intend to create a repository connection are not on the same system or the same trusted private network, then identity propagation is not secure. To ensure security, you must configure SSL on Oracle Content Server.
Configuration of SSL on Oracle Content Server involves the following tasks:
You can also refer to "SSL Properties" in Content Integration Suite Administration Guide available at http://download.oracle.com/docs/cd/E10316_01/ouc.htm
. Perform these procedures if you use self-signed certificates.
In a production environment, it is recommended that you use real certificates. For information about how to configure keystores when using real certificates, see the "Using Security Providers" chapter in the Security Providers Component Administration Guide available at http://download.oracle.com/docs/cd/E10316_01/ouc.htm
.
For more information about configuration for SSL, see Section 23.6, "Configuring WebCenter Applications and Components to Use SSL".
Configuring a Keystore and Key on the Client Side
To configure a keystore on the WebCenter application (client) side:
In your development environment, go to JDEV_HOME
/jdk/bin
and open the command prompt.
Generate the client keystore by running the following keytool command:
keytool -genkey -keyalg RSA -validity 5000 -alias Client private key alias -keystore client-keystore.jks -dname "cn=client" -keypass Private key password -storepass KeyStore password
To verify that the keys have been correctly created, you can optionally run the following keytool command:
keytool -list -keystore client-keystore.jks -storepass KeyStore password
To use the key, sign it by running the following keytool command:
keytool -selfcert -validity 5000 -alias Client private key alias -keystore client-keystore.jks -keypass Private key password -storepass KeyStore password
Export the client public key by running the following keytool command:
keytool -export -alias Client private key alias -keystore client-keystore.jks -file client.pubkey -keypass Private key password -storepass KeyStore password
Configuring a Keystore and Key on the Server Side
To configure a keystore on the Oracle Content Server side:
In the same development environment, go to JDEV_HOME
/jdk/bin
and open the command prompt.
Generate the server keystore by running the following keytool command:
keytool -genkey -keyalg RSA -validity 5000 -alias Server public key alias -keystore server-keystore.jks -dname "cn=server" -keypass Private server key password -storepass KeyStore password
To verify that the key has been correctly created, run the following keytool command:
keytool -list -keystore server-keystore.jks -keypass Server private key password -storepass KeyStore password
To use the key, sign it by running the following keytool command:
keytool -selfcert -validity 5000 -alias Server public key alias -keystore server-keystore.jks -keypass Private server key password -storepass KeyStore password
Export the server public key to the server keystore by running the following keytool command:
keytool -export -alias Server public key alias -keystore server-keystore.jks -file server.pubkey -keypass Server private key password -storepass KeyStore password
Verifying Signatures of Trusted Clients
To verify signatures of trusted clients, import the client public key into the server keystore:
In your development environment, go to JDEV_HOME
/jdk/bin
and open the command prompt.
To verify the signature of trusted clients, import the client's public key in to the server keystore by running the following keytool command:
keytool -import -alias Client public key alias -file client.pubkey -keystore server-keystore.jks -keypass Private server key password -storepass KeyStore password
Import the server public key into the client keystore by running the following keytool command:
keytool -import -alias Server public key alias -file server.pubkey -keystore client-keystore.jks -keypass Private key password -storepass KeyStore password
When the tool prompts you if the key is self-certified, you must enter Yes
. Example 11-2 shows a sample output that is generated after this procedure is completed successfully.
Example 11-2 Sample Output Generated by the Keytool
[user@server]$ keytool -import -alias client -file client.pubkey -keystore server-keystore.jks -keypass Server private key password -storepass Keystore password Owner: CN=client Issuer: CN=client Serial number: serial number, for example, 123a19cb Valid from: Date, Year, and Time until: Date, Year, and Time Certificate fingerprints: ... Trust this certificate? [no]: yes Certificate was added to keystore.
To secure identity propagation, you must configure SSL on Oracle Content Server.
Log on to Oracle Content Server as an administrator.
From Administration, choose Providers.
On the Create a New Provider page, click Add for sslincoming.
On the Add Incoming Provider page, in Provider Name, enter a name for the provider, for example, sslincomingprovider
.
When the new provider is set up, a directory with the provider name is created as a subdirectory of the CONTENT_SERVER_HOME
/data/providers
directory.
In Provider Description, briefly describe the provider, for example, SSL Incoming Provider for securing the Content Server
.
In Provider Class, enter the class of the sslincoming provider, for example, idc.provider.ssl.SSLSocketIncomingProvider
.
Note:
You can add a new SSL keepalive incoming socket provider or a new SSL incoming socket provider. Using a keepalive socket improves the performance of a session and is recommended for most implementations.In Connection Class, enter the class of the connection, for example, idc.provider.KeepaliveSocketIncomingConnection
.
In Server Thread Class, enter the class of the server thread, for example, idc.server.KeepaliveIdcServerThread
.
In Server Port, enter an open server port, for example, 5555
.
Select the Require Client Authentication checkbox.
In Keystore password, enter the password to access the keystore.
In Alias, enter the alias of the keystore.
In Alias password, enter the password of the alias.
In Truststore password, enter the password of the trust store.
Click Add.
The new incoming provider is now added.
Go to the new provider directory that was created in step 4.
To specify truststore and keystore, create a file named sslconfig.hda
.
Copy the server keystore to the server.
Configure the sslconfig.hda
file. Example 11-3 shows how the .hda
file should look after you include the truststore and keystore information.
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 11.2.1.2.3, "Configuring Secure Sockets Layer (SSL)."
None.
This section discusses the prerequisites for an Oracle Portal content repository in the following subsections:
For information on installing Oracle Portal, see Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer.
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.
None.
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.
This section discusses the prerequisites for a file system content repository in the following subsections:
All operations are executed as the system user under which the JVM is running and therefore inherit its permissions.
This section contains the following subsections:
Section 11.3.1, "What You Should Know About Registering Content Repositories for WebCenter Spaces"
Section 11.3.2, "Registering Content Repositories Using Fusion Middleware Control"
Section 11.3.3, "Registering Content Repositories Using WLST"
Please consider the following while registering Oracle Content Server repositories for WebCenter Spaces:
At the start up, WebCenter Spaces applications create seed data, if it does not already exist.
For active connections in WebCenter Spaces, the Spaces Root and Application Name values are used to create the seed data in the WebCenter Spaces repository, to enable storage of the Group Space data.
The Spaces Root value is used as the name for the root folder within the content repository under which all Group Spaces content is stored.
The Application Name value is used when creating the following security settings:
The name of the security group
The prefix for the role (the name format is applicationName
User
)
The prefix for all folder and content item accounts
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
.
Oracle does not recommend changing the Spaces Root and Application Name values. However, if you change the Spaces Root value after configuring and running a WebCenter Spaces application, then you must also change the Application Name value, and vice versa. That is, you must change both values (Spaces Root and Application Name) 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 Group Space data is created under the new Spaces Root and existing Group Space data under the old Spaces Root is no longer available. This means that any Group Space which had the Documents service provisioned prior to changing the Spaces Root will no longer have it provisioned.
Note:
Although the Spaces Root and Application Name values change, the old root content respository folder still appears in search results, like any other root folder in Oracle Content Server.To register a content repository:
Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:
Do one of the following:
For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.
For custom WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.
From the list of services on the WebCenter Service Configuration page, select Content Repository.
To connect to a new content repository, click Add (Figure 11-1).
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-2.
Table 11-2 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:
(WebCenter Spaces) If you are setting up the backend content repository for WebCenter Spaces, that is, the repository used by WebCenter Spaces to store group space and personal space documents, you must select Oracle Content Server. |
Active Connection |
Select to make this the default 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:
Deselecting this option does not disable the content repository connection. If a content repository is no longer required, you must delete the connection. |
(For the active connection in WebCenter Spaces only.) Enter additional details for the WebCenter Spaces repository (see Table 11-3).
See Also:
Section 11.3.1, "What You Should Know About Registering Content Repositories for WebCenter Spaces"Table 11-3 Content Repository Connection - WebCenter Spaces Repository Details
Field | Description |
---|---|
Administrator User Name |
Enter the user name of the content repository administrator. For example: Administrative privileges are required for this connection so that operations can be performed on behalf of WebCenter users. |
Spaces Root |
Enter the root folder under which all Group Spaces content is stored. Specify a content repository folder that does not yet exist and use the format: For example: The Invalid entries include: |
Application Name |
Enter a unique name for this WebCenter Spaces application within this content repository. For example: The name must begin with an alphabetical character, followed by any combination of alphanumeric characters or the underscore character. The string must be less than or equal to 30 characters. |
Enter connection details for the content repository. For detailed parameter information, see:
Table 11-4 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:
For more information on the configuration parameters required for each RIDC socket type, see the table "Oracle Content Server Connection Parameters for Each RIDC Socket Type" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter. |
Authentication Method |
Choose from:
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. |
Server Host |
Enter the hostname of the machine where the Oracle Content Server is running. For example: 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:
For example, Server Port is required when the RIDC Type is set to Socket or Socket SSL. |
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. |
Web URL |
Enter the Web server URL for the Oracle Content Server. Use the format: For example: Web URL is applicable when the RIDC Type is set to Web. |
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: Key Store Location is required when the RIDC Type is set to Socket SSL. |
Key Store Password |
Enter the password required to access the keystore. For example: Key Store Password is required when the RIDC 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: Private Key Alias is required when the RIDC 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: Private Key Password is required when the RIDC Socket Type is set to Socket SSL. |
Table 11-5 Connection Details - Oracle Content Server - Cache Details
Element | Description |
---|---|
Cache Invalidation Interval (minutes) |
Specify the polling interval (in minutes) used by the Oracle Content Server service provider interface (SPI) to check for cache invalidations. The default is 0 which means that cache invalidation is disabled. The minimum interval is 2 minutes. |
Maximum Cached Document Size (bytes) |
Enter the maximum size (in bytes) for documents that are cached in the virtual content repository (VCR) binary cache. The default is 1024 bytes (1K). Tune this value based on your machine's memory configuration and the types of binary documents that you expect to cache. |
Administrator User Name |
Enter a user name with administrative rights for this Oracle Content Server instance. |
Administrator Password |
Enter the password for the Oracle Content Server administrator. |
Table 11-6 Oracle Portal Connection Parameters
Field | Description |
---|---|
Data Source Name |
Enter the JNDI DataSource location used to connect to the portal. For example: 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:
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-7 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: Caution: File system content must not be used in production or enterprise application deployments. This feature is provided for development purposes only. |
Click OK to save this connection.
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 task flows, which you can add to pages in WebCenter Spaces or custom WebCenter applications. See also, "Working with the Documents Service" in the Oracle Fusion Middleware User's Guide for Oracle WebCenter.
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.4, "Changing the Active (or Default) Content Repository Connection".
For information on how to run WLST commands, see Section 1.12.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 Administrator's Guide.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 group space and personal space documents and the repository must be an Oracle Content Server.
For other WebCenter applications, the active connection becomes the default connection for Documents service task flows (Content Presenter, Document Manager, Document List Viewer, and Recent Documents). When no specific connection details are provided for these task flows, the default (active) connection is used.
This section contains the following subsections:
To change the active (or default) content repository connection:
Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:
Do one of the following:
For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.
For custom WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.
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).
Select the connection you want to become the active (or default) connection, and then click Edit.
Select the Active Connection checkbox.
Click OK to update the connection.
To start using the updated active connection you must restart the managed server on which the WebCenter application is deployed.
Use the following WLST commands with Primary='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.12.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 Administrator's Guide.This section contains the following subsections:
Section 11.5.1, "Modifying Content Repository Connection Details Using Fusion Middleware Control"
Section 11.5.2, "Modifying Content Repository Connection Details Using WLST"
To update content repository connection details:
Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:
Do one of the following:
For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.
For custom WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.
From the list of services on the WebCenter Services Configuration page, choose Content Repository.
Select the connection name, and click Edit.
Edit connection details, as required. For detailed parameter information, see:
Click OK to save your changes.
To start using the updated (active) connection details, you must restart the managed server on which the WebCenter application is deployed.
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.4, "Changing the Active (or Default) Content Repository Connection".
For information on how to run WLST commands, see Section 1.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".
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 Administrator's Guide.For each content connection, caches are created automatically at runtime. However, you can configure or modify Universal Content Management (UCM) repository caches in two ways: in the EAR project file META-INF/p13n-cache-config.xml
or in the Portal Administration Console (under Configuration & Monitoring > Service Administration). Cache settings configured in the Portal Administration Console take precedence over the file-based settings. You can also flush the caches from the Portal Administration Console.
Note:
If you already have ap13n-cache-config.xml
file configured for another repository, you can add the UCM repository cache settings to this file.Table 11-8 and Table 11-9 describe the default cache settings in the p13n-cache-config.xml
file. Table 11-8 describes the VCR caches, which are caches used by the VCR component. These caches are repository-specific and can exist for any repository. Table 11-9 describes the SPI caches, which are specific to the UCM SPI adapter component.
The pattern for the cache entry names is <elementName>
.<repositoryName>
, where <repositoryName>
is the name of the UCM repository as specified in the META-INF/content-config.xml
file. For example, nodeCache.StellentRepository
. Note that some <time-to-live>
values are specified in milliseconds.
Table 11-8 VCR-Level Cache Entry Descriptions
Cache Entry Name | Description |
---|---|
|
Caches node Id of repository's node instance. Defaults: enabled = |
|
Caches node path to repository's node Id. Default values: enabled = |
|
Caches type Id of repository's type instance. Default values: enabled = |
|
Caches type name for repository's type Id. Default values: enabled = |
|
Default values: enabled = The maximum binary entry size is specified as the repository property |
|
Caches search results for a repository. Default values: enabled = |
|
Authorization cache for a repository when using native security. Default values: enabled = |
Table 11-9 SPI-Level Cache Entry Descriptions
Cache Entry Name | Description |
---|---|
|
Caches UCM server type metadata by type name. Default values: enabled = |
|
Caches UCM server node Ids by node path. Default values: enabled = |
|
Caches UCM server node metadata by node Id. Default values: enabled = |
|
Caches UCM server node security information. Default values: enabled = |
|
Caches the relationship between the UCM user names and UCM server user Ids (user security information.) Default value: 10 minutes ( |
|
Caches the list of UCM type names. Default values: enabled= |
|
Caches information about which UCM fields are indexed. Default values: enabled= |
This section contains the following subsections:
Section 11.6.1, "Deleting Content Repository Connections Using Fusion Middleware Control"
Section 11.6.2, "Deleting Content Repository Connections Using WLST"
Caution:
Delete a content repository connection only if it is not in use. If a connection is marked as active, it should first be removed from the active list, and then deleted.To delete a content repository connection:
Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application:
Do one of the following:
For WebCenter Spaces - From the WebCenter menu, choose Settings > Service Configuration.
For custom WebCenter applications - From the Application Deployment menu, choose WebCenter > Service Configuration.
From the list of services on the WebCenter Services Configuration page, choose Content Repository.
Select the connection name, and click Delete.
To effect this change you must restart the managed server on which the WebCenter application is deployed.
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.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".
Note:
To effect this change 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 Administrator's Guide.You can view, modify, and delete connection properties for the back-end Oracle Content Server repository that is being used by WebCenter Spaces to store group space and personal space documents. Specifically, you can define the root folder under which group space content is stored, the name of the content repository administrator, and a unique application identifier for separating application data on the Oracle Content Server.
This section contains the following subsections:
To set content repository connection properties:
Log in to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or the custom WebCenter application. See Section 6.2, "Navigating to the Home Page for WebCenter Spaces".
From the WebCenter menu, choose Settings > Service Configuration.
From the list of services on the WebCenter Services Configuration page, choose Content Repository.
Select the connection name, and click Edit.
(For the active connection in WebCenter Spaces only.) Set connection properties for the WebCenter Spaces repository (see Table 11-10).
Table 11-10 Content Repository Connection - WebCenter Spaces Repository Details
Field | Description |
---|---|
Administrator User Name |
Enter the user name of the content repository administrator. For example: Administrative privileges are required for this connection so that operations can be performed on behalf of WebCenter users. |
Spaces Root |
Enter the root folder under which group space content is stored. Specify a folder that does not yet exist and is unique across applications. Use the format: For example: If it does not already exist, the folder specified is automatically created when the WebCenter application starts. Invalid entries include: |
Application Name |
Enter a unique name for this WebCenter Spaces application within this content repository. For example: The name must begin with an alphabetical character, followed by any combination of alphanumeric characters or the underscore character. The string must be less than or equal to 30 characters. |
Click OK to save your changes.
To start using the updated (active) connection properties, you must restart the managed server on which the WebCenter application is deployed.
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 group space and personal space documents:
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.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands".
After setting up content repository connections, you can test them to make sure that you can access the content repository, as described in the following sections:
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:
In Fusion Middleware Control, from the WebCenter menu, choose Settings and select Service Configuration (Figure 11-2).
On the Manage Content Repository Connections page, select the connection and click Edit (Figure 11-3).
On the Edit Content Repository Connection page, copy the Web URL (Figure 11-4).
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/
To verify the full state of an Oracle Portal connection:
In the Oracle WebLogic Administration Console, under Domain Structure, expand Services > JDBC, then double-click Data Sources (Figure 11-5).
On the Summary of JDBC Data Sources page, select the data source you intend to test (Figure 11-6).
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-7).
By default, the maximum upload size for files is:
2 MB for custom WebCenter applications. This default is imposed by Apache MyFaces Trinidad, which handles uploading files from a browser to the application server.
2 GB for WebCenter Spaces applications.
The WebCenter application developer can customize the default file upload size at design time by setting the UPLOAD_MAX_MEMORY
, UPLOAD_MAX_DISK_SPACE
, and UPLOAD_TEMP_DIR
parameters in the web.xml
file. For information about manually editing web.xml
, see Section A.1.2, "web.xml".
For more information, see "Setting Parameters to Upload Files to Content Repositories" in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.