3.1 Configuring System Properties

This section covers the following topics:

3.1.1 About System Properties

System properties are system-wide settings that enable you to tailor Content Server to your particular requirements. System properties are set during installation and are generally updated occasionally, or as needed, in contrast to other administration tools, which are used more regularly for maintenance of users and content.


Regardless of which method is used to modify system properties, you must restart Content Server for any configuration changes to take effect.

There are several ways to interact with system properties:

  • TheAdmin Server enables you to configure a single content server instance . You also can enable and disable system components. The Admin Server can be accessed by using a Web browser and selecting the Administration link.

  • TheSystem Properties utility enables you to configure a specific content server instance from the system on which the content server instance is deployed. For information on accessing the System Properties utility, see "Running Administration Applications in Standalone Mode".

  • Most system properties settings correspond to a configuration variable in one of the following configuration files:

    • IntradocDir/config/config.cfg

    • DomainHome/ucm/short-product-id/bin/intradoc.cfg

    • IntradocDir/search/search.cfg

    It is recommended that you make changes to these files through the Admin Server or System Properties tool to ensure that the settings are entered correctly. While it is possible to edit these files directly using a text editor, it may allow errors to be introduced. See the Oracle Fusion Middleware Idoc Script Reference Guide for more information on configuration variables.


For the System Properties utility to run as a standalone application for a content server instance on Oracle WebLogic Server, additional configuration may be required. See "Configuring System Database Provider for Standalone Mode".

There are many techniques for optimizing the performance of Content Server. One of the types of tuning involves changing default parameters and software settings that affect the core Content Server performance. System optimization and performance tuning is often accomplished by adjusting system settings and configuration variables or tuning resources such as databases and indexes.

For example, as the content in your content server instance increases, you may experience a shortage of available space. In this case, moving the vault, weblayout, and search index directories to another drive with more space can help alleviate storage problems. Moving these directories requires adding entries into the DomainHome/ucm/cs/bin/intradoc.cfg file.

You do not have to log in as the system administrator to access the System Properties application. You only need access to the local computer where the content server is installed.

3.1.2 Configuring General Options

You can set general options on the System Properties: Options Tab or on the Admin Server: General Configuration Page. You must restart the content server for any configuration changes to take effect.

If you plan to use the Batch Loader utility to update and insert a large number of files on your Content Server system simultaneously, you must create a batch load file. Two of the optional parameters that you can include in your batch load file are primaryOverrideFormat and alternateOverrideFormat. However, these options only work as parameters in the batch load file if you enable the IsOverrideFormat configuration variable. You can set this variable using the System Properties application. Revision Label Sequence

The metadata field named Revision has a default revision number sequence of 1, 2, 3, 4, 5, and so forth. This number increments automatically for each revision of a document.

You can override the Revision default by changing the definition of the revision label. The revision label consists of two parts: a major and minor revision sequence. The Major Revision Label Sequence is the first number or letter and the Minor Revision Label Sequence follows. For example, in the revision sequence 1a, 1b, 1c, 2a, 2b, 2c, 3a, 3b, 3c, and so forth, the numbers 1, 2, 3 are the major revision sequence and a, b, c are the minor revision sequence. Revision Label Ranges

Both the major and minor revision sequences are defined as a range of numbers or letters. The major sequence can have multiple ranges, while the minor sequence can only have one range.

The following are the restrictions on defining the range:

  • Numbers or letters can be used, but not both. For example, 1-10 is a valid range but A-10 is not a valid range.

  • Letter ranges can have only one letter. For example, A-Z is a valid range but AA-ZZ is not a valid range. Revision Examples

The following are examples of different revision sequences and how you would define the major and minor revision entries in the config.cfg file.

Example 1


The revision sequence is A, B, C, D, 1, 2, 3, 4, and so forth.

Example 2



The revision sequence is 1a, 1b, 1c, 2a, 2b, 2c, 3a, 3b, 3c, and so forth. Revision Configuration Settings

To change the default revision sequence manually in the IntradocDir/config/config.cfg file, enter the following name/value pairs:

  • MajorRevSeq=range1,range2,range3...

  • MinorRevSeq=range

where range1,range2,range3... and range are the defined range sequence. Chunking Function

The Content Server Chunking function protects large data transfers from transfer failures by dividing data into chunks and transferring one chunk at a time. If a transfer fails, all chunks transferred to the content server before failure are saved, and the transfer can be resumed from the point of failure.


If the client session using the Chunking function is killed, either by timeout or by closing the client browser, the transfer will fail.

You can use the Chunking function with the upload applet. Configuring the Chunking Function

To enable and configure the Chunking function:

  1. Enable the upload applet or the HTTP provider. See "Configuring General Options".

  2. Set the following configuration settings in the Additional Configuration Variables box on the Admin Server: General Configuration Page:

    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 content server.

3.1.3 Configuring Content Security

You can set Content Server content security options on the System Properties: Content Security Tab or on the Admin Server: Content Security Page.

You must restart the content server for any configuration changes to take effect.

3.1.4 Configuring Internet Information

You can set Content Server Internet options on the System Properties: Internet Tab or on the Admin Server: Internet Configuration Page.

You must restart the content server for any configuration changes to take effect.

3.1.5 Configuring the Database

Content Server uses an Oracle WebLogic Server data source to communicate with the system relational database where metadata and other information is stored. The Oracle WebLogic Server Administration Console must be used to manage the database connection information, therefore JDBC username and password information is not stored in the IntradocDir/config/config.cfg file, and it is not managed through the System Properties utility.


If you set database connection information for Oracle WebLogic Server using the Content Server System Properties utility, the JDBC username and password are encrypted and stored in an unspecified location.

For more information on configuring databases with Content Server, see the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite. Configuring Database Driver Settings for Standalone Applications

If you want to use Content Server standalone applications such as System Properties or Batch Loader with a database other than Oracle Database, Oracle provides Fusion Middleware datadirect JDBC drivers for DB2, and MS SQL Server databases. For details, see "Configuring JDBC Database Drivers for Standalone Mode". Configuring IBM DB2 Database Searches in Content Server

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. Open a new browser window, and log in to Content Server as a system administrator (with the sysmanager role).

  2. Under Administration, click Admin Server.

  3. In the option list for the Content Server instance, click General Configuration.

    The General Configuration page is displayed.

  4. Add the following line to the Additional Configuration Variables box:

  5. Click Save.

  6. Restart Content Server.

3.1.6 Configuring Content Server

You can set Content Server options on the System Properties: Server Tab. For security reasons, the Admin Server cannot be used to configure these options. You must use the standalone application to configure options. For details about using standalone applications, see "Running Administration Applications in Standalone Mode".

Certain Content Server configuration options are set using Oracle Enterprise Manager Fusion Middleware Control. For details, see Chapter 2, "Using Oracle Fusion Middleware Control to Manage Oracle UCM Content Server".

You must restart the content server for any configuration changes to take effect.


If you do not use a Hostname filter, IP Address filter, or some other network-based security, you will have a security hole in your content server instance. For example, with no login, any user with in-depth knowledge of the system could create or modify any other user to have sysadmin access.

Hostname filter or IP Address filter values must be set to allow communication with the content server in the following situations:

  • Running Inbound Refinery and PDF Converter (even on the same physical computer as the content server).

  • Transferring content server archives between computers.

  • Configurations where the Web server and the content server are on different systems.

  • EJB-enhanced operations.

  • Using the IdcCommand or IdcCommandX utilities on a system separate from the content server. (You will need to change the default value and specify the IP address of the Web server.)

3.1.7 Configuring Locales

You can use the System Properties Localization tab to change language-specific issues such as date/time format, default time zone, sort order, and default interface language. Date Format

The default English-US locale uses two digits to represent the year (yy), where the year is interpreted to be between 1969 and 2068. In other words, 65 is considered to be 2065, not 1965. If you want years before 1969 to be interpreted correctly in the English-US locale, you must change the default date format for that locale to use four digits to represent years (yyyy).

This issue does not apply to the English-UK locale, which already uses four digits for the year.

To modify the default English-US data format:

  1. Start the System Properties applet:


    Select Start, then All Programs, then Content Server, then [Instance Name], then Utilities, then System Properties.


    The System Properties utility is located in the /bin subdirectory of the Content Server installation directory.

  2. Open the Localization tab.

  3. Select the English-US entry in the list of locales, and click Edit.

    The Configure Locale dialog is displayed.

  4. Modify the date format to use four digits for the year (yyyy) rather than two (yy).

  5. After you are done editing, click OK to close the Configure Locale dialog.

  6. Click OK to apply the change and exit System Properties.

  7. Stop and restart the Content Server (otherwise the change will not take effect). Interface Language

The default interface language for Content Server can be specified in several ways:

  • Select a default language in the Localization tab of the System Properties utility, using the same basic procedure described in "Date Format".

  • Use the Content Server navigation portal to selection Administration, then Localization. Select a check box for a default language from the list of Enabled Locales on the Localization Administration page.

3.1.8 Configuring Paths

You can use the System Properties: Paths Tab to change the location of the help browser, Java classpath, and the shared directory path. For security reasons, the Admin Server cannot be used to configure the path options. You must use the standalone application for this configuration.

You must restart the content server for any configuration changes to take effect.