4 Completing the WebCenter Content Configuration

This chapter explains how to complete the initial configuration of Oracle WebCenter Content, with Oracle WebCenter Content Server, in an Oracle WebLogic Server domain.

This chapter includes the following sections:

4.1 Configuring the Report Library for Records Management in Content Server

If you plan to configure the Records Management feature in Content Server, you need to configure the report library for Records Management after creating the domain that includes the WebCenter Content Managed Server, before starting it for the first time. Without this library, you cannot check in any templates to Content Server.

To configure the report library, you need to add the oracle.xdo.runtime library manually from the Oracle WebLogic Server Administration Console and then add a reference to this library in the weblogic-application.xml file of the WebCenter Content EAR.

Note:

This library is not needed for Oracle WebCenter Content: Records.

To add the oracle.xdo.runtime.ear library to the WebCenter Content Managed Server:

  1. After a domain is created, start only the Administration Server.

    If the WebCenter Content Managed Server has already been started, then you will have to perform additional steps to add a reference to the deployed WebCenter Content instance later.

  2. Open the Administration Console in browser, click Deployments on the left, and browse the pages to check if there is already an oracle.xdo.runtime file. If it is already present, then no more steps need to be performed.

  3. If the oracle.xdo.runtime file does not already exist, click Install on the Deployments display. A file selection dialog opens. Browse the available file system, and select the following path:

    MW_HOME/WCC_ORACLE_HOME/ucm/idc/components/ReportPublisher/lib/

  4. Click Next. The option page to select the file as a library opens. Select Install this deployment as a library, and click Next.

  5. The Target Selection Screen opens. Select all targets, and click Next.

  6. The Deployment Name screen opens. In the Security section, select DD Only: Use only roles and policies that are defined in the deployment descriptors. In the Source accessibility section, select Copy this application onto every target for me, and click Next.

  7. In the Additional Configuration section, select Yes, Take me to the deployment's configuration screen, and click Finish. The library is now deployed in the environment.

To reference the deployed library from the UCM Enterprise Application library:

  1. Extract the cs.ear file from the following path:

    MW_HOME/WCC_ORACLE_HOME/ucm/idc/components/ServletPlugin/cs.ear

  2. In the extracted directory, modify META-INF/weblogic-application.xml, and add the following library reference:

    <library-ref>
    <library-name>oracle.xdo.runtime</library-name>
</library-ref>

  3. Create an archive file named cs.ear from the extracted, modified directory, and replace the file of the same name in the path it was retrieved from. This change will take effect for all undeployed WebCenter Content instances.

  4. If this is not the first time the WebCenter Content Managed Server has been started since the domain was created, you need to perform these additional steps:

    1. Locate the weblogic-application.xml file of the WebCenter Content application in the deployed WebCenter Content Managed Server, with a path like this:

      DomainHome/servers/WCC_servername/tmp/_WL_user/Oracle WebCenter Content - Content Server/k6ggd/META-INF/weblogic-application.xml

      If the name of the WebCenter Content Managed Server is not in the DomainHome/servers directory, then these additional steps are not necessary because the Managed Server has not been started, which would have deployed it at this location.

    2. Modify the META-INF/weblogic-application.xml file, and add the following line for library reference:

      <library-ref>
    <library-name>oracle.xdo.runtime</library-name>
</library-ref>

    3. Start the WebCenter Content Managed Server, as described in Section 10.3, "Restarting a Managed Server."

  5. Start the WebCenter Content Managed Server, as described in Section 10.2, "Starting Managed Servers."

    If the Managed Server has been started before, restart it, as described in Section 10.3, "Restarting a Managed Server."

For information about adding the Records Management feature to Content Server, see Section 4.13, "Configuring Records Management in Content Server"

4.2 Completing the Initial WebCenter Content Configuration

After you start the Administration Server and Oracle WebCenter Content Managed Server, as described in Chapter 10, "Verifying the Oracle WebCenter Content Configuration," you can complete the WebCenter Content configuration on the postinstallation configuration page in Content Server.

The first user to log in to Oracle WebCenter Content Server must be the administrator of the Oracle WebLogic Server domain, to complete the configuration of Content Server. For more information, see Section 10.6, "Verifying the Configuration of Oracle WebCenter Content," and see also ”Overview of System Administration Tasks,” ”Understanding Security and User Access,” and ”Managing System Processes” in Oracle Fusion Middleware Administering Oracle WebCenter Content.

WebCenter Content displays the Content Server Configuration page when you first log in to Content Server at

http://managedServerHost:managedServerPort/cs

When you configure WebCenter Content on the same machine and in the same Oracle WebLogic Server domain as Oracle Web Center Content: Imaging, the postinstallation configuration of WebCenter Content is done automatically. If you follow the default configuration for the installation of WebCenter Content and Imaging, both applications are installed on the same machine. In this environment, Imaging provides a configuration file that sets up WebCenter Content for use by Imaging.

If WebCenter Content is intended to be used as a full Managed Server in addition to servicing Imaging, then the WebCenter Content administrator should review the automatic configurations through the administration interfaces in Content Server. The additional configuration steps described in the rest of this chapter should be done on the WebCenter Content Managed Server to fully configure it for production.

The Imaging administrator should verify that the default WebCenter Content configurations are correct for use by the Imaging Managed Server. For Imaging use, many of the WebCenter Content postinstallation configuration steps, such as configuring Oracle WebCenter Content: Inbound Refinery, are not required.

Before you can use Inbound Refinery with WebCenter Content, you need to configure Inbound Refinery for document and image conversions to work with Content Server. For transformations to work on some platforms, certain environment variables must be set before you start the Managed Server. For more information, see Section 3.7.2, "Setting Library Paths in Environment Variables on UNIX Platforms."

To complete the WebCenter Content configuration:

  1. Start the Administration Server, as described in Section 10.1, "Starting the Administration Server."

  2. Start the WebCenter Content Managed Server, as described in Section 10.2, "Starting Managed Servers."

  3. Browse to the Content Server postinstallation configuration page, at this website:

    http://managedServerHost:16200/cs/

    Important:

    The first user to log in to Oracle WebCenter Content Server must be the administrator of the Oracle WebLogic Server domain, to complete the configuration of Content Server. For more information, see Section 10.6, "Verifying the Configuration of Oracle WebCenter Content," and see also ”Overview of System Administration Tasks,” ”Understanding Security and User Access,” and ”Managing System Processes” in Oracle Fusion Middleware Administering Oracle WebCenter Content.

  4. Enter or edit any configuration values you want to change.

    In the FullText Search Option field, you can select a full-text search engine. Leaving it blank will set up the system as metadata only.

    For information about the values to enter, see Section 4.3, "Completing the Initial Configuration of Content Server."

  5. To enable access from Inbound Refinery, provide a value for Incoming Socket Connection Address Security Filter, as follows:

    127.0.0.1|your.server.IP.address|0:0:0:0:0:0:0:1|

    This field accepts wildcards in the value, like 10.*.*.*. You can change this value later by setting SocketHostAddressSecurityFilter in DomainHome/ucm/cs/config/config.cfg and restarting Content Server.

    For Oracle WSM security, the SocketHostAddressSecurityFilter value needs to set to like this:

    SocketHostAddressSecurityFilter=*.*.*.*|0:0:0:0:0:0:0:1

    For more information, see Section 3.14.4, "Configuring the Server Socket Port and Incoming Socket Connection Address Security Filter for Oracle WSM."

  6. Click Submit.

  7. Restart Content Server, as described in Section 10.3, "Restarting a Managed Server."

4.3 Completing the Initial Configuration of Content Server

After installing and configuring WebCenter Content on an Oracle WebLogic Server Managed Server, you need to complete the initial configuration of Content Server. Completing its initial configuration includes these tasks:

For information about changing the configuration of Content Server and additional configuration options, see ”Configuring System Properties” in Oracle Fusion Middleware Administering Oracle WebCenter Content.

4.3.1 Starting Content Server

You can start WebCenter Content, which includes Content Server, with the Oracle WebLogic Server Administration Console, the startManagedWebLogic startup script, or Oracle Enterprise Manager Fusion Middleware Control.

For more information, see ”Managing System Processes” in Oracle Fusion Middleware Administering Oracle WebCenter Content.

4.3.2 Configuring the Content Server Instance

Figure 4-1 shows the configuration page for Content Server.

Figure 4-1 Configuration Page for Content Server

Description of Figure 4-1 follows
Description of "Figure 4-1 Configuration Page for Content Server"

The following table describes the fields on this page and the values you can enter to configure your Content Server instance.

Field Description

Cluster Node Identifier

The name of the WebCenter Content Managed Server where Content Server will run.

Content Server Instance Folder

The absolute path to the Oracle instance directory for Content Server. Oracle recommends that you specify an instance directory that is outside of the Domain home.

The default Oracle instance directory for Content Server follows:

MW_HOME/user_projects/domains/DomainHome/ucm/cs

The name of the top-level folder in the folder hierarchy for the Content Server instance is cs.

The path to the Oracle instance directory is the value of the IntradocDir variable for the Content Server instance. This directory path should be unique to this particular Managed Server, or node. For installations that are likely to be upgraded to future versions of the product, Oracle strongly recommends that you change the location of the Oracle instance directory to a directory outside of any Oracle WebLogic Server domain directories or installation directories. For installations that will be in a cluster, the Oracle instance directory must be on a network to which all nodes in the cluster have shared access.

Native File Repository Location

The path to the vault/ directory for storing native content checked into Content Server.

Weblayout Folder

The path to the weblayout/ directory for storing web-viewable renditions of native and alternate files.

User Profile Folder

The path to the profiles/ directory for storing user profiles.

Content Server URL Prefix

The relative URL for the Content Server instance.

Is New Content Server Instance

Whether or not the Content Server instance is a new one.

Server Socket Port

The number of the port for calling top-level services. The default value is blank.

Changing this field value changes the IntradocServerPort entry in DomainHome/ucm/cs/config/config.cfg. The default IntradocServerPort value is blank.

Incoming Socket Connection Address Security Filter

Restricts Content Server access to a computer or computers with a specified IP address or addresses.

  • By default, this field is prefilled with the IP address of the local host (127.0.0.1).

  • You can specify multiple IP addresses, separated by pipes ( | ). Make sure that there are no spaces on either side of the pipe character. (For example: 127.0.0.1|0:0:0:0:0:0:0:1|192.168.1.1)

  • You can use wildcards in this field, * for zero or many characters, and ? for any one character. (For example, 10.10.3.*)

  • Generally, use only the IP Address Filter field or Hostname Filter field, not both. (IP Address Filter is more commonly used.)

Web Server HTTP/HTTPS Address

The name of the web server. (HttpServerAddress property).

Web Address Is HTTPS

Whether or not the URL for the web server starts with HTTPS, for a Managed Server that has SSL enabled.

Company Mail Server

An email server that Content Server can use to send email notifications.

This value generally takes the form of mail.example.com. If applicable, make sure to allow for sending email through a firewall.

Administrator E-Mail Address

An email address that Content Server can use to send email notifications (SysAdminAddress).

This address will receive a returned message for any delivery failure that occurs.

Server Instance Name

The name of the Content Server instance.

This name should contain only letters, numerals, and underscore characters. Other characters can cause problems. For example, an instance name that contains periods can cause a JavaScript error if the name is used to create a JavaScript variable.

Server Instance Label

The instance name that is displayed in the Windows Start menu (InstanceMenuLabel property).

Server Instance Description

A description of the Content Server instance (InstanceDescription property).

Is Auto Number Enabled

Whether or not automatic numbering of Content Server instances is enabled.

Auto Number Prefix

A unique prefix for a Content Server instance number, to avoid conflicts among multiple Content Server instances (Auto Number Prefix system property).

FullText Search Option

Specifies the search engine for full-text searches:

  • None: The Content Server instance will use DATABASE.METADATA as the search engine.

  • Internal: For Oracle Database 11g, the Content Server instance will use OracleTextSearch with the system database. For Microsoft SQL Server, Content Server will use DATABASE.FULLTEXT. For IBM DB2, Content Server will use DATABASE.METADATA.

  • External: The Content Server instance will use OracleTextSearch with an external data source in an Oracle Database (not the system database), SQL Server, or IBM DB2. If you select this option, you must provide the name of the external data source in the External DataSource field.

External DataSource

The name of an external data source that was created and targeted through the Administration Console to the WebCenter Content Managed Server, using an OCSSEARCH schema that was created with Repository Creation Utility (RCU).

For information about creating an external data source and targeting it to a Managed Server, see ”How to Create a JDBC Data Source for Oracle WebLogic Server” in the Oracle Fusion Middleware Java EE Developer's Guide for Oracle Application Development Framework.

You can specify the name of an external provider for the data source. For information about creating an external provider, see Section 4.5.2, "Configuring an External Database Provider for Standalone Applications."

If the external data source is for use with IBM DB2, see also Section 4.3.5, "Configuring Content Server for IBM DB2 Database Searches."

For information about the OCSSEARCH schema, see Section 2.2, "Creating Oracle WebCenter Content Schemas with the Repository Creation Utility."

4.3.3 Enabling or Disabling Components

You can use the Advanced Component Manager to enable or disable components.

To enable or disable components:

  1. Log in to WebCenter Content as an administrator.

  2. From the Administration tray or menu for your Content Server instance, choose Admin Server, then Component Manager.

  3. In the first paragraph of the Component Manager page, click advanced component manager.

  4. You can select individual components in the lists of enabled and disabled server components to view details about each component, and you can select categories of components to view. You can enable and disable components on this page, plus install and uninstall custom components.

Notes:

  • If you are using Records Management with Content Server, do not disable the ContentFolios component, which is required for access to the Records Management web interface. This component is enabled automatically when you configure the Records Management feature.

    For more information about Records Management, see Section 4.13, "Configuring Records Management in Content Server."

  • If you upgrade from Oracle WebCenter Content 11gR1 (11.1.1.5) to Oracle WebCenter Content 11gR1 (11.1.1.8.0) with the LinkManager8 component enabled, you need to disable LinkManager8 and enable the LinkManager component. LinkManager8 was renamed to LinkManager in Oracle WebCenter Content 11gR1 (11.1.1.6).

4.3.4 Configuring the Folders Interface

Oracle WebCenter Content Server provides a hierarchical folder interface, the Folders feature, for organizing and managing content in the repository. Content Server also provides the legacy hierarchical folder interface, Contribution Folders. Oracle recommends Folders (the FrameworkFolders component) as the folder interface for WebCenter Content because it resolves performance issues that occur with Contribution Folders (the Folders_g component) and includes other enhancements.

To use a folder interface, you need to enable either the FrameworkFolders component or the Folders_g component. You cannot have both enabled on a Content Server instance. Having both the Folders and Contribution Folders features enabled is not a supported configuration because some other features, such as the CoreWebdav system component, would not work correctly with both enabled. If you have both features enabled after an upgrade, you need to disable one of them.

To configure the folders interface:

  1. Log in to WebCenter Content as an administrator.

  2. From the Administration tray or menu for your Content Server instance, choose Admin Server, then Component Manager.

  3. On the Component Manager page, select Folders to display the Folders category of components.

  4. Select the FrameworkFolders component.

  5. Click the Update button, and then click OK to confirm enabling the component.

  6. In the first paragraph of the Component Manager page, click advanced component manager.

  7. If Folders_g is in the Enabled Components box on the Advanced Component Manager page, select this component, and then click the Disable button.

  8. Restart Content Server, as described in Section 10.3, "Restarting a Managed Server."

If you want to configure Contribution Folders instead of Folders, you can enable the Folders_g component and make sure that FrameworkFolders is disabled on the Advanced Component Manager page.

4.3.5 Configuring Content Server for IBM DB2 Database Searches

An IBM DB2 database does not support the keyword CONTAINS in search queries. The correct configuration of a Content Server instance for IBM DB2 searches requires the addition of the flag SSUseContains=false on the General Configuration page and a restart of Content Server.

To configure IBM DB2 database searches in Content Server:

  1. Log in to WebCenter Content as an administrator.

  2. From the Administration tray or menu for your Content Server instance, choose Admin Server, then General Configuration.

  3. Near the bottom of the General Configuration page, add the following line to the Additional Configuration Variables box:

    SSUseContains=false

  4. Click Save.

  5. Restart Content Server, as described in Section 10.3, "Restarting a Managed Server."

4.3.6 Configuring Microsoft SQL Server to Work with WebCenter Content

Before you can use Microsoft SQL Server with WebCenter Content, you need to turn on snapshot isolation in the database. If you plan to use SQL Server for the back-end database for Imaging and Oracle SOA Suite, you also need to configure the Metadata Services (MDS) repository in the database and then create an MDS schema with Repository Creation Utility (RCU).

The prerequisite SQL Server configurations for WebCenter Content and the MDS repository follow:

  1. Log in to the database with a user name that has DBA privileges and does not have multiple logins on the database.

    Multiple logins for the DBA would result in a lock error.

  2. Alter the database to turn on the ALLOW_SNAPSHOT_ISOLATION option, with this command:

    ALTER DATABASE dbname SET ALLOW_SNAPSHOT_ISOLATION ON

  3. Alter the database to turn on the READ_COMMITTED_SNAPSHOT option, with this command:

    ALTER DATABASE MDS SET READ_COMMITTED_SNAPSHOT ON

For information about creating an MDS schema with RCU, see Section 2.2, "Creating Oracle WebCenter Content Schemas with the Repository Creation Utility."

For more information about supported databases, see Section 2.2.1.1, "Database Prerequisites."

4.4 Configuring Additional Parameters for WebCenter Content Cluster Nodes

For WebCenter Content cluster nodes, you need to add some additional parameters to avoid performance problems such as stuck threads or other file system issues.

Using a text editor, add the following options to each cluster node's DOMAIN_HOME/ucm/cs/bin/intradoc.cfg file, where the directories specified are on a direct-bus-attached-controlled local disk and not a remote file system, such as a Windows mapped drive to NTFS/CIFS, or a UNIX/Linux mounted NFS or clustered file system (like OCFS2, GFS2, or GPFS):

TraceDirectory=local_domain_home/servers/UCM_serverN/logs/ 
EventDirectory=local_domain_home/servers/UCM_serverN/logs/event/ 
ArchiverDoLocks=true 
DisableSharedCacheChecking=true

For each cluster node created with the Oracle WebLogic Scripting Tool (WLST) unpack command, you will need to create the preceding directories, ensuring that the permissions are the same as for the first installed node (RWXD for the user executing the WebCenter Content Managed Server, usually oracle). The trailing N should match the node's server name, like UCM_server1 is node1, UCM_server2 is node 2, and so on.

Note:

The directories can reside in any local disk path that you have determined to have enough space to hold the WebCenter Content logs and any trace that you might configure. The preceding paths are suggestions.

Finally, add one more parameter, which must be on a shared file system (unlike the other entries, which should point to the local disk installation):

UserProfilesDir=ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/data/users/profiles/

Note:

A WebCenter Content Managed Server cannot be configured for server migration.

4.5 Configuring OracleTextSearch for Content Server

If you have a license to use OracleTextSearch (with Oracle Database 11g), then you can configure it to use Oracle Text 11g as the primary full-text search engine for WebCenter Content. Oracle Text 11g offers state-of-the-art indexing capabilities and provides the underlying search capabilities for Oracle Secure Enterprise Search (Oracle SES). To search auxiliary metadata in Oracle WebCenter Content: Records with Oracle Text 11g, you must configure it to use OracleTextSearch as the search engine.

If you have a license to use Oracle SES, you can configure it for use with OracleTextSearch on WebCenter Content and configure Content Server to use Oracle SES as its back-end search engine. For more information, see ”Managing Oracle Secure Enterprise Search” in Oracle Fusion Middleware Administering Oracle WebCenter Content.

OracleTextSearch enables administrators to specify certain metadata fields to be optimized for the search index as well as to customize additional fields. OracleTextSearch also enables a fast index rebuild and index optimization.

You can set OracleTextSearch on the WebCenter Content postinstallation configuration page, which Figure 4-1 shows.

To configure OracleTextSearch for Content Server on the postinstallation configuration page:

  1. Select Internal or External in the FullText Search Option field.

  2. If you selected the External option, provide the name of the external data source in the External DataSource field.

For more information about these fields, see Section 4.3.2, "Configuring the Content Server Instance."

If you have Oracle Database 11g, and you specify Internal for Fulltext Search Option, you do not need to run the Repository Creation Utility (RCU) to create a search schema.

You might want to use an external data source so you can put the search engine on another system or in another database. Before you can use an external data source with OracleTextSearch, you need to create a search schema in a database other than the system database and configure the data source.

To create a search schema and configure an external data source:

  1. Run RCU to create a search schema (prefix_OCSSEARCH in the database where you want the search engine, as described in Section 2.2, "Creating Oracle WebCenter Content Schemas with the Repository Creation Utility."

  2. Create a JDBC data source that points to the search schema.

    You can use the Administration Console, WebLogic Scripting Tool Command, or Fusion Middleware Control to create a data source.

  3. Use the Administration Console to target the data source to the WebCenter Content Managed Server (UCM_server1 by default).

For information about creating an external data source and targeting it to a Managed Server, see ”How to Create a JDBC Data Source for Oracle WebLogic Server” in the Oracle Fusion Middleware Java EE Developer's Guide for Oracle Application Development Framework.

If you did not configure OracleTextSearch on the configuration page for Content Server or you want to change the configuration, you can configure this search option in the DomainHome/ucm/cs/config/config.cfg configuration file for the Content Server instance. After changing the search option, you need to restart Content Server and rebuild the search index.

To configure OracleTextSearch for Content Server in the configuration file:

  1. Open the DomainHome/ucm/cs/config/config.cfg file for the Content Server instance in a text editor.

  2. Set the following values:

    SearchIndexerEngineName=OracleTextSearch

IndexerDatabaseProviderName=SystemDatabase

    Notes:

    • You can specify a separate Oracle Database as the value of IndexerDatabaseProviderName, instead of SystemDatabase. The driver jar ojdbc6.jar is provided by Oracle in the MW_HOME/wlserver_10.3/server/lib directory. Before Oracle Text Search can function properly with the separate Oracle Database, however, you need to manually copy the ojdbc6.jar file from the MW_HOME/wlserver_10.3/server/lib directory to the DomainHome/lib directory.

    • OracleTextSearch requires a JDBC driver version of 10.2.0.4 or higher. The component will not work with older JDBC driver versions.

  3. Save the file.

  4. Restart Content Server, as described in Section 10.3, "Restarting a Managed Server."

  5. Rebuild the search index using the Indexer tab of the Repository Manager, located under Administration, in Admin Applets.

    For more information about rebuilding the index, see ”Working with the Search Index” in Oracle Fusion Middleware Administering Oracle WebCenter Content.

4.5.1 Applying Patches for Using Oracle Text 11g with Oracle Database 11.1.0.7.0

If you are using Oracle Database 11.1.0.7.0, you should apply the following patches to the database to prevent problems with using Oracle Text 11g:

  • Patch 7446163

  • Patch 6851110

To apply patches for using Oracle Text 11g with Oracle Database 11.1.0.7.0

  1. Download patches 7446163 and 6851110 and print or save their Read Me documents from My Oracle Support (formerly OracleMetaLink) at https://support.oracle.com.

  2. To apply each patch, follow the instructions in its Read Me document.

4.5.2 Configuring an External Database Provider for Standalone Applications

You can create an external database provider in Content Server for standalone applications, such as the Batch Loader utility, to connect directly to the database with JDBC without using the SystemDatabase Provider for the Oracle WebLogic Server data source. For standalone applications to use OracleTextSearch, you must configure the external database provider to include the JDBC connection information.

By default, the configuration of an incoming provider does not include values for JDBC Driver and JDBC Connection String. You need to add these values, but be careful not to change the provider name because you cannot rename an existing provider. To change the name of a provider, you need to delete it and add it again. For information about changing the configuration of a provider, see ”Editing Provider Configuration” in Oracle Fusion Middleware Administering Oracle WebCenter Content.

4.6 Installing the Check Out and Open ActiveX Control on a Windows Client

Check Out and Open is a component of Content Server that enables users to check out and open content items in WebDAV-compliant applications directly from Content Server.

An ActiveX control is used for Internet Explorer browsers to provide the Check Out and Open functionality on Windows client computers. (A Java applet is used for other browsers, such as Firefox.) Some organizations have user environments that do not allow downloaded ActiveX controls to be installed. In addition, users in such environments might not have administrative access to their client computers. This limits the ability for individual users to install client software or allow downloaded controls to be installed.

To work around this limitation, you can manually register the CheckOutAndOpen.dll file on a client computer. The following instructions are for a Windows operating system.

To install the Check Out and Open ActiveX control on a Windows client:

  1. Obtain the CheckOutAndOpen.dll file. This DLL file is located inside the DomainHome/ucm/cs/weblayout/common/checkoutandopen.cab file. Use a standard ZIP file tool, such as WinZip, to extract the file to a directory, such as C:\Windows\System32.

    You can extract the CheckOutAndOpen.dll file to a different directory of your choice.

  2. Open a command-line console.

  3. Go to the location where you extracted the CheckOutAndOpen.dll file; for example:

    cd \windows\system32

  4. Register the DLL file with the following command:

    regsvr32 CheckOutAndOpen.dll

    You can include the silent switch, –s, in the regsvr32 command.

  5. At this point the ActiveX control is registered with the Windows system.

    The first time a check-out-and-open operation is attempted on the computer, the control will be enabled within the browser. Internet Explorer will attempt to first look to see if an object with the COAO CLSID is installed and use it before attempting to download the ActiveX control. The user should not be prompted to accept the installation.

You can validate that the control is registered in Internet Explorer 7 or 8 as follows:

  1. From the Tools menu, choose Internet Options.

  2. Click the Programs tab.

  3. Click the Manage add-ons button.

  4. Verify that Check Out And Open Control is in the list of enabled add-ons.

Note:

If Desktop Integration Suite 7.5 or later (including 10gR3) is installed, it will copy a version of CheckOutAndOpen.dll and register it. If the Check Out and Open component is referencing the same CLSID as the one installed by Desktop Integration Suite, then this control is used rather than downloaded.

4.7 Configuring a JDBC Driver for Standalone Applications

For Content Server to work with standalone applications, such as the Batch Loader Utility, you need to configure a JDBC driver for the system database or an external database provider. Oracle Fusion Middleware provides DataDirect JDBC drivers for Microsoft SQL Server and IBM DB2 databases to support Content Server standalone applications. You can use the System Properties utility, which Figure 4-2 shows, to enter the configuration information.

Figure 4-2 System Properties Utility

Description of Figure 4-2 follows
Description of "Figure 4-2 System Properties Utility"

To configure a JDBC Driver for standalone applications:

  1. As a system administrator, run SystemProperties from the bin directory for the Content Server instance to start the System Properties utility.

    • UNIX path: DomainHome/ucm/cs/bin/SystemProperties

    • Windows path: DomainHome\ucm\cs\bin\SystemProperties

  2. On the System Properties screen, click the Database tab, where you can select the appropriate driver and enter the connection string, user name, and password.

    You do not need to enter a class path or driver name, or copy any JAR files.

    You can find the JDBC connection string and user name in the Oracle WebLogic Server Administration Console. Log in to the Administration Console, and then select Services, then Data Sources, then CSDS (or URMDS), and then Connection Pool. On the Connection Pool tab, the connection string is in the URL field, and the user name is in the Properties field. For security, the password is not displayed.

  3. On the Database tab, select the appropriate driver under Use Java Database Connectivity, and enter the connection string.

    For Microsoft SQL Server, select DataDirect SQL Server JDBC Driver, and enter a connection string of this form:

    jdbc:weblogic:sqlserver://database_hostname:database_port_number;databaseName=database_name

    For IBM DB2, select DataDirect DB2 JDBC Driver, and enter a connection string of this form:

    jdbc:weblogic:db2://database_hostname:database_port_number;databaseName=database_name

  4. Enter the user name and password for the database in the JDBC User Name and JDBC User Password fields.

  5. Click OK.

  6. Restart Content Server, as described in Section 10.3, "Restarting a Managed Server."

4.8 Importing a Database Root CA Certificate into the Keystore for a Standalone Application

Content Server components that are standalone applications do not use Oracle WebLogic Server data sources to connect and interact with a relational database management system. Standalone applications connect directly to a database using a JDBC driver.

If a standalone application is required to connect to an SSL-enabled database where digital certificates are used for authentication, then the database root CA certificate must be imported into the standard Java keystore that the application uses to check trusted sources.

To import a database root CA certificate into the keystore for a standalone application:

  1. Import the certificate into the standard Java keystore that corresponds to the application's JDK.

    The following example shows the commands to import a certificate for an application that uses the Oracle JRockit JDK on a Windows operating system:

    c:\mw_home\jrockit_160_29_D1.2.0-10\bin\keytool -import -trustcacerts 
  -alias dbroot -keystore 
c:\mw_home\jrockit_160_29_D1.2.0-10\jre\lib\security\cacerts -storepass 
  changeit -file b64certificate.txt

  2. Configure SystemProperties with the SSL connection string.

    For example:

    jdbc:oracle:thin:@( DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCPS)(HOST=mydbhost.example.com) (PORT=2490
)))(CONNECT_DATA=(SERVICE_NAME=orcl.example.com))(SECURITY=(SSL_SERVER_CERT_ 
DN="CN=orcl,O=server_test,C=US")))

    For Oracle Database, you can find the SSL connection string in tnsnames.ora.

  3. Do any other configuration required for your application, and then log in.

4.9 Enabling and Configuring Site Studio on Content Server

Before you can use Site Studio, you need to complete some configuration steps in Content Server. You can configure Site Studio on Content Server after you install the Oracle WebCenter Content software. Site Studio is available in two versions:

  • Site Studio, which uses Site Studio Designer to create websites

    This version requires that the SiteStudio component be enabled on Content Server. For more information, see Section 4.9.1, "Enabling Site Studio on Content Server."

    You can download the Site Studio Designer Installer from the My Content Server tray or menu, under My Downloads. For information about using this application, see the Oracle WebCenter Content User's Guide for Site Studio Designer.

  • Site Studio for External Applications, which uses Oracle JDeveloper as the development environment to create Site Studio websites

    This version requires that both the SiteStudio component and SiteStudioExternalApplications component be enabled in Content Server and both the RIDC extension and Site Studio for External Applications extension be installed on JDeveloper. For installation instructions, see ”Installing Site Studio for External Applications” in the Oracle WebCenter Content Developer's Guide for Site Studio for External Applications. For information about using the Site Studio for External Applications extension in JDeveloper, see the JDeveloper help.

    The Remote Intradoc Client (RIDC) extension and Site Studio for External Applications extension for JDeveloper are included in the RIDC suite distribution and Web Content Management (WCM) suite distribution, respectively, which can be downloaded from the Oracle Fusion Middleware WebCenter Content section of the Oracle Technology Network (OTN) at

    http://www.oracle.com/technetwork/index.html

    If you plan to use dynamic conversion of native documents on your Site Studio websites, then you must configure Dynamic Converter in Content Server.

The Site Studio version and Site Studio for External Applications version must have exactly the same feature extensions number; otherwise, error messages are reported and the Site Studio features will not work.

To configure Site Studio, you need to complete these tasks:

After you configure Site Studio, you can use Site Studio for External Applications in JDeveloper to create Site Studio websites.

You can create an 11g Site Studio site running on Oracle WebLogic Server and use an Oracle Universal Content Management (Oracle UCM) 10gR3 server as the back end. For information about using Site Studio 11gR1 (11.1.1.7.0) with Oracle UCM 10gR3, see ”Configuring Oracle Content Server 10gR3 for Use with Site Studio 11gR1” in the Oracle WebCenter Content Technical Reference Guide for Site Studio.

4.9.1 Enabling Site Studio on Content Server

Before you can use Site Studio, you must enable the Site Studio features on Content Server.

To enable Site Studio on Content Server:

  1. Log in to WebCenter Content as an administrator.

  2. In the Content Server Administration tray or menu, choose Admin Server, then Component Manager.

  3. On the Component Manager page, under Web Content Management, select SiteStudio, SiteStudioExternalApplications, and DBSearchContainsOpSupport, and click Update.

    You need to enable the SiteStudioExternalApplications feature only if you want to use the Site Studio extension in JDeveloper.

  4. Click OK to enable these features.

  5. Restart Content Server, as described in Section 10.3, "Restarting a Managed Server."

4.9.2 Setting Default Project Document Information

When you create a new website in Site Studio, a new project file is created and checked into Content Server for you. Before you can create websites, you must specify the metadata that will be assigned to the new project files. You do this on the Set Default Project Document Information page in Content Server.

To set the default project document information:

  1. Log in to Content Server as an administrator.

  2. Go to the Administration page, and click Site Studio Administration.

    The Site Studio Administration page is displayed.

  3. Click Set Default Project Document Information.

    This option displays the Set Default Project Document Information page, where you can assign the default metadata for new projects generated by Site Studio.

  4. Set the metadata as required, and click Update when you have finished.

    This button returns you to the Site Studio Administration page.

4.9.3 Setting Default Metadata for Website Assets

Site Studio websites created by Site Studio for External Applications in JDeveloper need their default metadata set in Content Server. You can set this default metadata on the Set Default Web Asset Document Information page, available through the Content Server Administration tray or menu under Site Studio Administration.

For information about setting default metadata for Site Studio website assets, see ”Set Default Web Asset Document Information Page” in the Oracle WebCenter Content Administrator and Manager's Guide for Site Studio.

4.9.4 Configuring Zone Fields

The Site Studio component uses several metadata fields that are added to Content Server. If you do not use OracleTextSearch, some of these fields must be configured as zone fields to ensure that they are full-text indexed.

Make sure that the DBSearchContainsOpSupport component is enabled on Content Server. This component ensures that the zone fields are full-text indexed, which is required for Site Studio sites to work correctly. If this component is not enabled, you should enable it with the Component Manager, as described in Section 4.9, "Enabling and Configuring Site Studio on Content Server."

Configuring zone fields is configuring Site Studio metadata fields as zone fields. Make sure that the zone fields are configured as follows.

To configure Site Studio metadata fields as zone fields:

  1. Log in to WebCenter Content as an administrator.

  2. In the Content Server Administration tray or menu, choose Zone Fields Configuration.

  3. On the Zone Fields Configuration page, select Web Sites and Exclude From Lists as zone text fields.

You do not need to rebuild the search index after enabling these fields as zone fields.

4.9.5 Enabling JavaServer Pages on Content Server

If you plan to use JavaServer Pages in Site Studio, you must enable JSP on Content Server. This enables you to access and modify content and services (personalization, security definitions, predefined variables, and so on) on Content Server.

Important:

  • JSP is supported only in legacy Site Studio projects; that is, projects that use the pre-10gR4 architecture. These are typically projects that were created in a Site Studio release before 10gR4 and that are opened in Designer 11gR1.

  • You cannot enable JSP on Content Server and then use Site Studio for External Applications remote templates in the same security group. If you did, Content Server would attempt to evaluate the Site Studio for External Applications page templates, resulting in an error that would shut down the server.

If you enable any JSP groups after you enable the Site Studio component, you must configure the JSP support so that the JSP fragments function properly.

If you enable the Site Studio component and then add a group to the list of JSP Enabled Groups in Content Server, you must redeploy the JSP support files for that group to enable Site Studio JSP fragments to work correctly.

For more information about enabling JavaServer Pages, see Getting Started with the Software Developer's Kit (SDK), which is part of the Oracle Content Server 10gR3 documentation set.

To configure JSP Support for a new JSP group:

  1. Log in to WebCenter Content as an administrator.

  2. In the Administration tray or menu, choose Site Studio Administration.

  3. On the Site Studio Administration page, click Manage Fragment Libraries.

  4. Click the Configure JSP Support button.

    The JSP support files are extracted to the required directories on Content Server.

4.9.6 Rebuilding the Content Server Index

If you are using database search and indexing (full-text or metadata-only), you do not need to rebuild the search index after you install or upgrade the Site Studio component on Content Server. If you are using a different search engine (typically, Verity), you must rebuild the search index when installing or upgrading the Site Studio component. You should rebuild the search index after enabling the component and configuring Content Server.

The index rebuild is necessary to take advantage of new metadata fields introduced by Site Studio.

Important:

Rebuilding the search index can be a time-consuming process, depending on the number of content items managed by your Content Server instance. You should perform this rebuild during off-peak hours of Content Server use (typically at night or on the weekend).

If you plan to upgrade websites created in Site Studio releases before 7.5 (see the Oracle WebCenter Content Technical Reference Guide for Site Studio), you must rebuild the search index on Content Server at that time. To prevent rebuilding the index more than once, you may want to skip this step until after you have successfully upgraded your sites.

For more information on rebuilding the index, see ”Configuring the Search Index” in Oracle Fusion Middleware Administering Oracle WebCenter Content.

4.10 Configuring Content Server for Desktop

Before clients can use Oracle WebCenter Content: Desktop with Content Server, you need to make sure the CoreWebdav system component is enabled, and you need to enable these components:

  • DesktopIntegrationSuite

  • DesktopTag

  • FolderStructureArchive

  • FrameworkFolders

You can also enable EmailMetadata, which maps email message fields to email metadata fields.

When you enable the FrameworkFolders component (Folders feature), you need to make sure that the Folders_g component (Contribution Folders feature) is disabled because CoreWebdav would not work correctly with both enabled. For more information, see Section 4.3.4, "Configuring the Folders Interface."

To configure Content Server for Desktop:

  1. Log in to WebCenter Content as an administrator.

  2. In the Content Server Administration tray or menu, choose Admin Server, then Component Manager.

  3. On the Component Manager page, select Folders to display the Folders category of components.

  4. Select the FrameworkFolders component.

  5. Select the DesktopIntegrationSuite, DesktopTag, and optionally, the EmailMetadata components.

  6. Click the Update button, and then click OK to confirm your selections.

  7. In the first paragraph of the Component Manager page, click advanced component manager.

  8. In the Disabled Components box on the Advanced Component Manager page, select FolderStructureArchive, and click the Enable button.

  9. If Folders_g is in the Enabled Components box, select this component, and click the Disable button.

  10. Make sure that the CoreWebdav component is enabled:

    1. Under Category Filters on the Advanced Component Manager page, select Show System Components.

    2. If CoreWebdav is not in the Enabled Components box, select CoreWebdav in the Disabled Components box, and click the Enable button.

  11. Restart Content Server, as described in Section 10.3, "Restarting a Managed Server."

4.11 Installing and Configuring Desktop on a Client Workstation

Oracle WebCenter Content: Desktop provides a set of embedded applications that help users seamlessly integrate their desktop experiences with Content Server, Oracle Content Database, or other WebDAV-based content repositories. More specifically, these applications provide convenient access to these content repositories directly from Microsoft Windows Explorer, Microsoft Office applications (Word, Excel, and PowerPoint), and supported email clients (Microsoft Outlook and Lotus Notes).

For information about how to install Desktop on a client workstation, see ”Setting Up the Desktop Client Software on Your Computer” in Oracle Fusion Middleware Using Oracle WebCenter Content: Desktop.

4.12 Opening Files from Microsoft Office 2010 Over a Non-SSL Connection

By default, Microsoft Office 2010 will not open files over WebDAV using basic authentication over a non-SSL connection. To get around this, you can create the following registry entry and set its value to 2:

HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Internet\BasicAuthLevel

For more information, see Microsoft Knowledge Base article 2123563 on the Microsoft Support website at

http://support.microsoft.com/kb/2123563

4.13 Configuring Records Management in Content Server

If you are licensed to configure Records Management in a WebCenter Content Managed Server, you can configure either standalone Records Management or the Oracle URM Adapter in Content Server after the Oracle WebCenter Content: Records Managed Server is configured.

Notes:

The ContentFolios component is required for access to the Records Management web interface. This component is enabled automatically when you configure Records Management in Content Server. Do not disable the ContentFolios component.

If you do not want to use Records Management in Content Server, you can remove the configuration user interface by disabling the RMFeatureConfig component. Before you disable Records Management and restart Content Server, you need to delete the Report template files that Records Management installs. You cannot delete them after Records Management is disabled. For more information about how to disable this feature, see Section 4.3.3, "Enabling or Disabling Components."

To configure Records Management in Content Server:

  1. From the Administration tray or menu, choose Configure Records Settings to go to the Records Management Setup Checklist, then click Configure Installation.

  2. On the Enabled Features page, select a Records Management option for which you are licensed:

    • None

    • Standalone

    • Adapter

  3. Click Submit.

  4. Restart WebCenter Content, as described in Section 10.3, "Restarting a Managed Server."

    Whenever the screen says to restart the server during the Records Management configuration, restart the WebCenter Content Managed Server.

  5. After you restart WebCenter Content, the Records Management Setup Checklist is displayed again.

    For information about completing items on the Setup Checklist, see Section 8.1.2, "Completing the Setup Checklist for Records."

  6. If you selected Adapter, click Register Source on the Enabled Features page, and then supply values for the fields on the Register Source page:

    • Provider Name: Specify the outgoing provider used to connect to the Records Managed Server. You can choose from the list of current outgoing providers, or you can click the Add button and create one yourself. The provider dialog box shows an abbreviated list of provider fields.

      You can also add providers from the regular Providers page. To view information about an existing provider, click Info in the Action column.

    • Source Name: Specify the name of the external source to be added to the Records Managed Server. The source name is required and cannot contain spaces.

    • Source Table Name: Specify the prefix to use for creating database tables. If this value is not specified, it is defaulted to the source name.

    • Source Display Name: Specify the caption to use for displaying the source name. If this value is not specified, it is defaulted to the source name.

    After you supply the field values, click Register.

    Before the source is actually registered, the following tests are run:

    • Validate the provider and test the connection to the Records Managed Server

    • Validate the specified source values

      Compare the retention schedules of the adapter and the Records Managed Server to determine whether any items in the adapter are not in the Records server. Before the source can be registered, you need to resolve any such items after on the Import Retention Schedule page. This page lists all of the items that need to be resolved and gives options for resolving the differences.

      The retention schedule needs to be synchronized between the adapter and server. By default, all of the items that need to be resolved will be imported into the Records server. You will also have the option of deleting any of the items instead of importing them into the server. Before any items are imported or deleted, backups of retention schedules are made on both the adapter and the Records server, and the backups are checked in to Content Server.

      After the source is registered, the Retention Schedule and Upload Content task will run in the background.

    After the source has been successfully registered, click OK on the confirmation page. You will be redirected to the configuration wizard.

  7. Configure the adapter on the following pages in the configuration wizard:

    • Configure Custom Fields

      The Configure Custom Fields page enables you to specify custom fields on the external source. When you add or edit custom fields, you map them to existing document metadata fields defined in Content Server. You can use the same name for each field as defined in Content Server, or you can rename the field to something different. When the content is uploaded to the Records server as external content items, these fields are mapped to their external field names.

      You can configure custom fields, as needed, in any of these ways:

      • Add an external custom field.

      • Edit an external custom field.

      • Configure the disposition actions.

      • Configure the scheduled events.

      • View the external source information (from the Info menu, select Source Information).

    • Configure Scheduled Times

      The Configure Scheduled Times page enables you to specify when the scheduled tasks are to run. You can specify the interval at which the tasks are run (in hours, days, or weeks) and the time of day. This enables you to schedule the tasks at times when there might be less activity.

  8. After Records Management is initially configured on Content Server, the menu bar includes a Records menu. You can change the Records Management configuration through options on this menu.

    For more information about configuring Records Management, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

  9. From the Records menu, select Configure and then Enabled Features.

    On the Enabled Features page, you can change the selection of features and dispositions. For the adapter, the features you select cannot be more than the features selected on the Records server. For more information about the Features and Disposition Actions sections of the Enabled Features page, see Section 8.1.1, "Configuring the Level of Records Features."

    After you change any features or dispositions, restart WebCenter Content, as described in Section 10.3, "Restarting a Managed Server."

4.14 Configuring Oracle iPlanet Web Server As a Web Tier for Oracle WebCenter Content

You can configure the Oracle iPlanet Web Server as a web tier for Oracle WebCenter Content. For more information, see the "Configuring the iPlanet as web tier for Oracle WebCenter Content" blog.

4.15 Configuring Shared Folders for WebCenter Content Clustering

If you are using a cluster of WebCenter Content Managed Servers, you need to configure a shared file system for the WebCenter Content cluster. For more information, see the "WebCenter Content shared folders for clustering" blog.

4.16 Installing and Configuring AXF for BPM and AXF for BPEL

Oracle WebCenter Content: AXF for BPM and Oracle Application Extensions Framework (AXF) for BPEL are installed automatically with Imaging. Before you can configure AXF for BPM or AXF for BPEL in a WebLogic Server domain with Imaging, you need to create an AXF schema with the Repository Creation Utility, as described in Section 2.2.2, "Creating Schemas for Oracle WebCenter Content Applications." You can select AXF for BPM to it to the Imaging Managed Server when the domain is created or extended, as described in Chapter 3, "Configuring Oracle WebCenter Content Applications." AXF for BPEL is deployed as part of the Imaging application.

For information about AXF for BPM or AXF for BPEL installation, configuration, and verification with Imaging, see Section 6.5, "Installing and Configuring AXF for BPM and AXF for BPEL."

For additional information about configuring and using AXF for BPM or AXF for BPEL and the AXF for BPEL database tables (Imaging tables), see Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter.