Configuring Content Security Configuring Internet Information Configuring the Database

4-4 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server transfer fails, all chunks transferred to the Oracle Content Server instance before failure are saved, and the transfer can be resumed from the point of failure. You can use the Chunking function with the upload applet.

4.1.2.6 Configuring the Chunking Function

To enable and configure the Chunking function:

1. Enable the upload applet or the HTTP provider. See

Section 4.1.2, Configuring General Options. ■ To enable the upload applet, see Section 4.1.2, Configuring General Options. ■ To create an HTTP provider, see Section 5.8, Additional Oracle Content Server Security Connections.

2. Set the following configuration settings in the Additional Configuration Variables

box on the Admin Server: General Configuration Page : DisableHttpUploadChunking=false AppletChunkThreshold=size in bytes AppletChunkSize=size in bytes The AppletChunkSize setting sets the size of the individual chunks. The AppletChunkThreshold setting sets the minimum file size that will use the Chunking function. Both of these values default to 1M.

3. To debug the Chunking function, set ChunkedRequestTrace=true.

This setting enables you to view the chunked requests on Admin Server Output Page .

4. Save the changes.

5. Restart the Oracle Content Server instance.

4.1.3 Configuring Content Security

You can set Oracle Content Server content security options on the System Properties: Content Security Tab or on the Admin Server: Content Security Page . You must restart the Oracle Content Server instance for any configuration changes to take effect.

4.1.4 Configuring Internet Information

You can set Oracle Content Server Internet options on the System Properties: Internet Tab or on the Admin Server: Internet Configuration Page . You must restart the Oracle Content Server instance for any configuration changes to take effect.

4.1.5 Configuring the Database

The Oracle Content Server system uses an Oracle WebLogic Server data source to communicate with the system relational database where metadata and other Note: If the client session using the Chunking function is killed, either by timeout or by closing the client browser, the transfer will fail. Managing System Settings 4-5 information is stored. The Oracle WebLogic Server Administration Console must be used to manage the database connection information for the system relational database, therefore JDBC user name and password information is not stored in the IntradocDirconfigconfig.cfg file, and it is not managed through the SystemProperties utility. For information about supported databases, see the System Requirements and Supported Platform document for your product on the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network at http:www.oracle.comtechnologysoftwareproductsiasfilesfus ion_certification.html For information on configuring database connections for an Oracle Content Server system running standalone applications, see Section 3.4.2.1, Configuring a SystemDatabase Provider for Standalone Mode, Section 3.4.2.2, Configuring a JDBC Database Driver for Standalone Mode, and Section 3.4.2.3, Configuring an External Database Provider for Standalone Mode. Configuring Oracle Content Server for IBM DB2 Database Searches An IBM DB2 database does not support the keyword CONTAINS in search queries. The correct configuration of the Oracle Content Server instance for IBM DB2 searches requires the addition of the flag SSUseContains=false variable. To configure the Oracle Content Server instance: 1. Open a new browser window, and log in to the Oracle Content Server instance as system administrator.

2. In the navigation tree, choose Administration, then Admin Server.

3. In the option list for the Oracle Content Server instance, choose General

Configuration . The General Configuration page is displayed.

4. Add the following line in the Additional Configuration Variables area:

SSUseContains=false

5. Click Save.

6. Restart the Oracle Content Server instance.

4.1.6 Configuring Oracle Content Server Options