5 Configuring Oracle Universal Content Management

5.1 Completing the Oracle UCM Configuration

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

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

http://managedServerHost:managedServerPort/cs

When you configure Oracle UCM on the same machine and in the same Oracle WebLogic Server domain as Oracle I/PM, the postinstallation configuration of Oracle UCM is done automatically. If you follow the default configuration for the installation of Oracle UCM and Oracle I/PM, both applications are installed on the same machine. In this environment, Oracle I/PM provides a configuration file to Oracle UCM that sets up Oracle UCM for use by Oracle I/PM.

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

The Oracle I/PM administrator should verify that the default Oracle UCM configurations are correct for use by the Oracle I/PM Managed Server. For Oracle I/PM use, many of the Oracle UCM postinstallation configuration steps, such as configuring Oracle Inbound Refinery, are not required.

Before you can use Oracle Inbound Refinery (Oracle IBR) with Oracle UCM, you need to configure Oracle IBR for document and image conversions to work with Oracle 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 4.7.2, "Setting Library Paths in Environment Variables on UNIX Platforms."

To complete the Oracle UCM configuration:

1. Start the Administration Server, as described in Chapter 10, "Starting the Administration Server."

2. Start the Oracle UCM Managed Server, as described in Chapter 10, "Starting Managed Servers."

3. Browse to the Oracle Content Server postinstallation configuration page, at this web site:

   http://managedServerHost:16200/cs/
   

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.

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

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

   127.0.0.1your.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 Oracle 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 4.14.4, "Configuring the Server Socket Port and Incoming Socket Connection Address Security Filter for Oracle WSM."

6. If you want to set up a provider from Oracle IBR back to Oracle Content Server, enter an unused port number, such as 4444, for Server Socket Port.

   You can change this value later by setting IntradocServerPort in DomainHome/ucm/cs/config/config.cfg and restarting Oracle Content Server.

7. Click Submit.

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

5.2 Completing the Initial Configuration of Oracle Content Server

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

• Starting Oracle Content Server

• Configuring the Oracle Content Server Instance

• Configuring Oracle Content Server for IBM DB2 Database Searches

For information about changing the configuration of Oracle Content Server and additional configuration options, see "Configuring Content Server" in Oracle Fusion Middleware System Administrator's Guide for Oracle Content Server.

5.2.2 Configuring the Oracle Content Server Instance

Figure 5-1 shows the configuration page for Oracle Content Server.

Figure 5-1 Configuration Page for Oracle Content Server

Description of "Figure 5-1 Configuration Page for Oracle Content Server"

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

Field	Description
Cluster Node Identifier	The name of the Oracle UCM Managed Server where Oracle Content Server will run.
Content Server Instance Folder	The absolute path to the Oracle instance directory of Oracle Content Server, which is DomainHome/ucm by default. The default Oracle instance directory for Oracle Content Server follows: MW_HOME/user_projects/domains/DomainHome/ucm/cs The name of the top-level folder in the folder hierarchy for the Oracle Content Server instance is cs. The path to the Oracle instance directory is the value of the IntradocDir variable for the Oracle 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 Oracle Content Server.
Weblayout Folder	The path to the weblayout directory for storing web-viewable renditions of native and alternate files.
Content Server URL Prefix	The relative URL for the Oracle Content Server instance.
Is New Content Server Instance	Whether or not the Oracle 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 Oracle 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 Oracle 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 Oracle 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 Oracle Content Server instance.
Server Instance Label	The instance name that is displayed in the Windows Start menu (InstanceMenuLabel property).
Server Instance Description	A description of the Oracle Content Server instance (InstanceDescription property).
Is Auto Number Enabled	Whether or not automatic numbering of Oracle Content Server instances is enabled.
Auto Number Prefix	A unique prefix for an Oracle Content Server instance number, to avoid conflicts among multiple Oracle Content Server instances (Auto Number Prefix system property).
FullText Search Option	Specifies the search engine for full-text searches: None: The Oracle Content Server instance will use DATABASE.METADATA as the search engine. Internal: For Oracle Database, the Oracle Content Server instance will use OracleTextSearch with the system database. For Microsoft SQL Server, it will use DATABASE.FULLTEXT. External: The Oracle Content Server instance will use OracleTextSearch with an external data source for an Oracle Database (not the system database). 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 through the Administration Console and targeted to the Oracle UCM 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 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 5.3.2, "Configuring an External Database Provider for Standalone Applications." If the external data source is for use with IBM DB2, also see Section 5.2.4, "Configuring Oracle Content Server for IBM DB2 Database Searches." For information about the OCSSEARCH schema, see Section 2.2, "Creating Oracle Enterprise Content Management Suite Schemas."

5.3 Configuring Oracle Text Search for Oracle Content Server

The Oracle Text Search feature enables the use of Oracle Text 11g as the primary full-text search engine for Oracle UCM. Oracle Text 11g offers state-of-the-art indexing capabilities and provides the underlying search capabilities for Oracle Secure Enterprise Search (Oracle SES).

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

Before you can use Oracle Text Search, you need to run Repository Creation Utility (RCU) to create a search schema (prefix_OCSSEARCH) in an Oracle Database instance, create a data source that points to the search schema, and then use the Administration Console to target the data source to the Oracle UCM Managed Server (UCM_server1 by default). For information about creating a schema, see Chapter 2, "Creating Schemas for Oracle Enterprise Content Management Suite."

To search auxiliary metadata in Oracle URM with Oracle Text, you must configure Oracle Content Server to use Oracle Text Search as the search engine. You can set Oracle Text Search on the Oracle UCM postinstallation configuration page or in the configuration file. You can change the configuration of the full-text search option to Oracle Text Search in the config.cfg configuration file.

Oracle Text Search supports the use of Oracle Secure Enterprise Search (Oracle SES) 11g as the primary full-text search engine for Oracle UCM. If you have a license to use Oracle SES, you can configure it for use with Oracle Text Search on Oracle UCM and configure Oracle Content Server to use Oracle SES as its back-end search engine. For more information, see "Oracle Secure Enterprise Search" in Oracle Fusion Middleware System Administrator's Guide for Oracle Content Server.

You can configure Oracle Text Search on the postinstallation configuration page for Oracle Content Server, which Figure 5-1 shows, by selecting Internal or External in the FullText Search Option field. If you select the External option, you must provide the name of the external data source in the External DataSource field. For more information about these fields, see Section 5.2.2, "Configuring the Oracle Content Server Instance."

If you did not configure Oracle Text Search on the configuration page for Oracle Content Server, you can configure this search option in the config.cfg configuration file for the Oracle Content Server instance. You can also change the search option in this file. After changing the search option, you need to restart Oracle Content Server and rebuild the search index.

To configure Oracle Text Search for Oracle Content Server in the configuration file:

1. Open the config.cfg file for the Oracle Content Server instance in a text editor.

2. Set the following property value:

   SearchIndexerEngineName=OracleTextSearch
   

3. If you are using an external data source instead of the system database, change SystemDatabase in the following property to the external data source name:

   IndexerDatabaseProviderName=SystemDatabase
   

   Note:

   You can specify a separate Oracle Database as the value of IndexerDatabaseProviderName, instead of SystemDatabase. However, before Oracle Text Search can function properly with the separate Oracle Database, you need to manually copy the ojdbc14.jar file from the ECM_ORACLE_HOME/ucm/idc/shared/classes folder to the UCM_DOMAIN/config/lib folder.

4. Save the file.

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

6. Rebuild the search index.

   For more information about rebuilding the index, see "Working with the Search Index" in Oracle Fusion Middleware System Administrator's Guide for Oracle Content Server.

5.4 Configuring a JDBC Driver for Standalone Applications

For Oracle 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 Oracle Content Server standalone applications. You can use the System Properties utility, which Figure 5-2 shows, to enter the configuration information.

Figure 5-2 System Properties Utility

Description of "Figure 5-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 Oracle 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 Oracle Content Server, as described in Section 10.3, "Restarting a Managed Server."

5.5 Importing a Database Root CA Certificate into the Key Store for a Standalone Application

Oracle 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 key store that the application uses to check trusted sources.

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

1. Import the certificate into the standard Java key store 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_20_D1.1.0-2119\bin\keytool -import -trustcacerts 
     -alias dbroot -keystore 
   c:\mw_home\jrockit_160_20_D1.1.0-2119\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.

5.6 Enabling and Configuring Site Studio on Oracle Content Server

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

• Site Studio, which uses Site Studio Designer to create web sites

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

  The Site Studio Designer installer can be downloaded from the My Content Server tray or menu, under My Downloads. For information about using this application, see the Oracle Fusion Middleware User's Guide for Site Studio Designer.

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

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

  The Remote Intradoc Client (RIDC) extension and Site Studio for External Applications extension for Oracle 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 Universal Content Management 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 web sites, then you must configure Dynamic Converter in Oracle 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:

• Enabling Site Studio on Oracle Content Server

• Setting Default Project Document Information

• Setting Default Metadata for Web Site Assets

• Configuring Zone Fields

• Enabling JavaServer Pages on Oracle Content Server

• Rebuilding the Oracle Content Server Index

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

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

5.7 Configuring Oracle Content Server for Desktop Integration Suite

Before clients can use Desktop Integration Suite (DIS) with Oracle Content Server, you need to make sure the CoreWebdav system component is enabled, and you need to enable the DesktopIntegrationSuite, DesktopTag, FolderStructureArchive, and Folders_g components. You can also enable EmailMetadata, which maps email message fields to email metadata fields.

To configure Oracle Content Server for Desktop Integration Suite:

1. In the Oracle Content Server Administration tray, click Admin Server to display the Component Manager page.

2. Make sure that the CoreWebdav component is enabled:

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

   2. On the Advanced Component Manager page, select Show System Components.

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

      This component will be enabled when you restart Oracle Content Server.

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

4. On the Component Manager page, select Folders.

5. Select the DesktopIntegrationSuite, DesktopTag, FolderStructureArchive, and Folders_g components and, optionally, the EmailMetadata component.

6. Click the Update button.

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

5.8 Installing and Configuring Desktop Integration Suite on a Client Workstation

Desktop Integration Suite provides a set of embedded applications that help users seamlessly integrate their desktop experiences with Oracle 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 the Desktop Integration Suite on a client workstation, see "Setting Up Desktop Integration on Client Computers" in Oracle Fusion Middleware User's Guide for Desktop Integration Suite.

5.9 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 web site at

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

5.10 Configuring Records Management in Oracle Content Server

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

To configure Records Management in Oracle Content Server:

1. From the Administration tray, select Configure Records Settings to go to the Records Management Setup Checklist, and click Configure Installation.

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

   • None

   • Standalone

   • Adapter

3. Restart Oracle UCM, 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 Oracle UCM Managed Server.

4. After you restart Oracle UCM, the Records Management Setup Checklist is displayed again.

   For information about completing items on the Setup Checklist, see Section 9.1.2, "Completing the Setup Checklist for Oracle URM."

5. 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 Oracle URM 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 Oracle URM 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 Oracle URM Managed Server

   • Validate the specified source values

     Compare the retention schedules of the adapter and the Oracle URM Managed Server to determine whether any items in the adapter are not in the Oracle URM 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 Oracle URM 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 Oracle URM server, and the backups are checked into Oracle 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.

6. 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 Oracle Content Server. You can use the same name for each field as defined in Oracle Content Server, or you can rename the field to something different. When the content is uploaded to the Oracle URM 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.

7. After Records Management is initially configured on Oracle 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 the Oracle Fusion Middleware Setup Guide for Universal Records Management.

8. 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 Oracle URM server; otherwise, an error occurs. For more information about the Features and Disposition Actions sections of the Enabled Features page, see Section 9.1.1, "Enabling Oracle URM Components."

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

5.11 Configuring Oracle Application Extension Framework

Oracle Application Extension Framework (AXF) is automatically installed with Oracle I/PM. For information about verifying the installation, see Section 7.5, "Installing and Configuring Oracle Application Extension Framework."

For information about configuring and using AXF and the AXF database tables, see Oracle Fusion Middleware Administrator's Guide for Oracle Application Adapters for Oracle Enterprise Content Management.

5.12 Installing and Configuring Oracle Document Capture and Oracle Distributed Document Capture

Oracle Document Capture provides high-volume production scanning from a central location, while Oracle Distributed Document Capture provides a user-friendly web interface that enables distributed enterprises to capture images easily from remote locations.

For information about installing and configuring Oracle Document Capture, see Oracle Document Capture Installation Guide and Oracle Document Capture Administrator's Guide.

For information about installing and configuring Oracle Distributed Document Capture, see Oracle Distributed Document Capture Installation Guide and Oracle Distributed Document Capture Administrator's Guide.

The Oracle UCM 11g Commit Driver is required to commit documents from either capture application to Oracle UCM. For information about using the Oracle UCM 11g Commit Driver, see Oracle Distributed Document Capture Installation Guide or Oracle Distributed Document Capture Administrator's Guide.