8 Configuring System Properties

This chapter describes how to configure Oracle WebCenter Content Server system properties using Oracle Enterprise Manager Fusion Middleware Control, the Content Server Administration interface, and the Content Server System Properties utility.

This chapter includes the following topics:

About System Properties

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

Note:

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

There are several tools for modifying system properties:

  • The Enterprise Manager Fusion Middleware Control interface can be used to view and modify server, Internet, e-mail, security, and component configuration for the Content Server instance. For information on accessing Fusion Middleware Control, see Starting and Stopping Content Server and Inbound Refinery.

  • The Content Server's Administration interface can be used to view and modify server, Internet, e-mail, security, and component configuration for the Content Server instance. Information on accessing these configuration options is provided in this chapter.

  • The System Properties utility is a Content Server administration application that can be used to configure system-wide settings from the system on which a Content Server instance is installed. This utility runs as a standalone application. For information on running the System Properties utility, see Running Administration Applications in Standalone Mode.

    Note:

    For the System Properties utility to run as a standalone application for a Content Server instance on a WebCenter Content domain, additional configuration is required.

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

    • IntradocDir/config/config.cfg

    • DomainHome/ucm/cs/bin/intradoc.cfg

    • IntradocDir/search/search.cfg

    It is recommended that you make changes to these files using the Administration interface or the System Properties utility to ensure that the settings are entered correctly. While it is possible to edit these files directly using a text editor, it might allow errors to be introduced. See Configuration Variables in Configuration Reference for Oracle WebCenter Content.

Tip:

There are many techniques for optimizing the performance of a Content Server instance. 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 might 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 in to the DomainHome/ucm/cs/bin/intradoc.cfg file.

Configuring System Properties Using Fusion Middleware Control

This section describes how to use Oracle Enterprise Manager Fusion Middleware Control interface to configure certain Content Server system properties.

This section covers the following topics:

Note:

For information on using Fusion Middleware Control to manage Content Server components, see Managing Components Using Fusion Middleware Control.

For information on records management configuration options, see Configuring Retention Definitions and Options in Managing Oracle WebCenter Content.

Modifying Content Security Configuration Using Fusion Middleware Control

WebCenter Content Server security configuration specifies settings used to control user access to WebCenter Content Server content items.

To modify content security configuration for WebCenter Content Server:

  1. When you are logged in to Enterprise Manager Fusion Middleware Control, in the navigation tree expand the appropriate domain name (for example, Content_base_domain).
  2. Expand WebCenter, then Content, then Content Server.
  3. Select the WebCenter Content Server instance name (for example, Oracle WebCenter Content - Content Server (UCM_server1)). The home page for your WebCenter Content Server instance appears.
  4. On the WebCenter Content Server home page, from the Content Server menu choose Configuration Pages, then General Configuration.
  5. You can modify the settings in the Content Security section of the General Configuration page. Settings are described in Table 8-1.
  6. Click Apply.

    If you do not want to apply changes, click Revert to return to the previous configuration settings.

Table 8-1 General Configuration: Content Security

Element Description

Allow get copy for user with Read privilege

Allows a user with Read privilege to a content item to get a copy of the content item. To enable, select the check box.

Allow author to delete revision

Allows the author of a content item to delete revisions of the item as long as the author/owner has Read privilege (otherwise requires Delete privilege to the content item's security group). To enable, select the check box.

Note: If a site is using Contribution Folders, then this setting means an author/owner can delete the content item without having Delete privilege to the content item's security group.

Allow only original contributor to checkout

Allows only the original contributor of a content item to check out the item. To enable, select the check box.

Show only known accounts

Displays only known accounts to users. Known accounts are those to which a user has been authorized. To enable, select the check box.

Modifying General Configuration Using Fusion Middleware Control

General configuration specifies a variety of settings used to configure WebCenter Content Server, including enabling accounts and adding configuration variables specific to your unique deployment.

To modify general configuration for WebCenter Content Server:

  1. In the navigation tree, expand the appropriate domain name (for example, Farm_base_domain).
  2. Expand WebCenter, then Content, then Content Server.
  3. Select the WebCenter Content Server instance name (for example, Oracle WebCenter Content - Content Server (UCM_server1)).

    The home page for your WebCenter Content Server instance appears.

  4. On the WebCenter Content Server home page, from the Content Server menu choose Configuration Pages, then General Configuration.
  5. You can modify the settings in the General Admin Server Configuration section of the General Configuration page. Settings are described in Table 8-2.
  6. Click Apply.

    If you do not want to apply changes, click Revert to return to the previous configuration settings.

Table 8-2 General Configuration: General Admin Server Configuration

Element Description

Allow override format on check-in

Allows the format to be overridden on a content item when it is checked in to the repository. To enable, select the check box.

Enable download applet

Enables download applet to download multiple files to check out or download at the same time. To enable, select the check box.

Enable upload applet

Allows applets to be uploaded from the WebCenter Content Server. To enable, select the check box.

Enable accounts

Enables the use of accounts in WebCenter Content Server. To enable, select the check box.

For more information, see Managing Accounts.

Automatically assign a content ID on check-in

Automatically assigns a content ID to a content item when it is checked in to the repository. To enable, select the check box.

Major revision label sequence

Displays the Major Revision Label Sequence from the system configuration.

Minor revision label sequence

Displays the Minor Revision Label Sequence from the system configuration.

Auto number prefix

Displays the auto number prefix from the system configuration.

Additional Configuration Variables

Displays additional general configuration variables for the system configuration. You can add configuration variables in this field.

See Configuration Variables in Configuration Reference for Oracle WebCenter Content.

Modifying Internet Configuration Using Fusion Middleware Control

WebCenter Content Server configuration settings specify information used to identify a Content Server deployment scenario.

To modify the Internet server configuration:

  1. In the navigation tree, expand the appropriate domain name (for example, Farm_base_domain).
  2. Expand WebCenter, then Content, then Content Server.
  3. Select the Content Server instance name (for example, Oracle WebCenter Content - Content Server (UCM_server1)).

    The home page for your Content Server instance appears.

  4. On the Content Server home page, from the Content Server menu choose Configuration Pages, then Internet Configuration.
  5. You can modify some of the settings in the Server Configuration section of the Internet Configuration page. Some of the settings are Read Only and cannot be changed. Settings are described in Table 8-3.
  6. Click Apply.

    If you do not want to apply changes, click Revert to return to the previous configuration settings.

Table 8-3 Oracle WebCenter Content - Internet Configuration

Element Description

HTTP Address

Name of the HTTP web server for the Content Server instance. For security reasons, this field cannot be changed from the interface. You must change the field using the Oracle WebCenter Content standalone application.

The server address is used to formulate full URLs in the Content Server user interface. This prevents users from being prompted to log in again because the domain name used to enter the server is not changed when links on pages are relative. Example: pc.idc.example.com.

IP Address Filter

The list of IP addresses that can be used to access the Content Server instance. This field is required.

The list of IP addresses are allowed to communicate to the Content Server instance through the Intradoc Server Port. The field accepts both IP and IPv6 addresses, with a pipe as the separator between addresses. This list must be well defined because it is a trusted connection. Example: 10.131.123.*.

Intradoc Server Port

The server port number for the Content Server instance.

The Intradoc server port is the port number listened to by the Content Server instance. This is a trusted connection where only the user ID is required to authenticate. Example: 4056.

Use SSL

Specifies whether a Secure Sockets Layer (SSL) enabled web server is being used. For security reasons, this field cannot be changed from the interface. You must change the field using the Oracle WebCenter Content standalone application.

SSL is related to the HTTP server address and indicates that the full URL uses the secured HTTP nomenclature. For example, it generates an address with https://HttpServerAddress/... instead of http://HttpServerAddress/...

Modifying Email Configuration Using Fusion Middleware Control

WebCenter Content Server email configuration settings specify information used to identify the Content Server deployment scenario.

To modify the email configuration:

  1. In the navigation tree, expand the appropriate domain name (for example, Farm_base_domain).
  2. Expand WebCenter, then Content, then Content Server.
  3. Select the Content Server instance name (for example, Oracle WebCenter Content - Content Server (UCM_server1)).
  4. On the Content Server home page, from the Content Server menu choose Configuration Pages, then Internet Configuration.
  5. You can modify some of the settings in the Email Configuration section of the Internet Configuration page. One of the settings is Read Only and cannot be changed. Settings are described in Table 8-4
  6. Click Apply.

    If you do not want to apply changes, click Revert to return to the previous configuration settings.

Table 8-4 Oracle WebCenter Content - Email Configuration

Element Description

Mail Server

Name of the mail server used to send email notifications from the Content Server instance. Example: mailserver.example.com.

SMTP Port

Port number used for SMTP communications. Example: 25.

For security reasons, this field cannot be changed from the interface. You must change the field using the Oracle WebCenter Content standalone application.

Admin Mail Address

Email address for the administrator for the Content Server instance.

This is the administrator email address that receives error messages. Such messages are generally logged, but this is an additional method of notification. Example: mymail@example.com.

HTTP Server Address Web address on which the mail server runs where a partial URL is used instead of a full address. Example:HttpServerAddress=example.

Configuring General Options

After WebCenter Content and a Content Server instance are deployed and initial configuration specified, you can set or modify general function options for Content Server using the Options tab on the System Properties utility or using the General Configuration page accessed through the Administration interface.

Using general function options, you can:

  • Enable users to select the format of a document during check-in

  • Enable users to select multiple files to check out or download at the same time

  • Enable users to check in multiple files as a single Zip file

  • Enable the use of accounts

  • Enable all full-text search terms to be highlighted in returned PDF, HTML, and text documents.

  • Enable Enterprise Search fields to be displayed on search pages if Enterprise Search is configured for use

  • Enable Content IDs to be generated automatically as six-digit, sequential numbers

  • If automatic Content ID generation is enabled, the string specified in this field is added as a prefix to the six-digit, sequential number

  • Specify how the optional second letter or number in a revision number is incremented

You must restart the Content Server instance for any configuration changes to take effect.

Revision Label Sequence

Among the General Configuration options that can be set is the 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 revision sequence and minor revision sequence. The Major Revision Label Sequence (MajorRevSeq) is the first number or letter and the Minor Revision Label Sequence (MinorRevSeq) 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 through 10 is a valid range but A through 10 is not a valid range.

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

  • If a letter range is used in the major revision sequence, then the minor revision sequence must be either a numeric range or not used. If a numeric range is used in the major revision sequence, then the minor revision sequence must be either a letter range or not used.

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

MajorRevSeq=A-D,1-99

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

Example 2

MajorRevSeq=1-99

MinorRevSeq=a-c

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 instance before failure are saved, and the transfer can be resumed from the point of failure.

Note:

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

You can use the Chunking function with the upload applet.

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 field on the 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 chunked requests on the Server Output page.
  4. Save the changes.
  5. Restart the Content Server instance.

Vertical Clustering and Scale-Up

You can set up instance specific configurations (in vertical scale-up):

  1. Open a new browser window, and log in to the Content Server instance as system administrator.
  2. Choose Administration, then Admin Server, then General Configuration.
  3. Set Server Port (Default), Server Port (<server_name>), Server IP Filter, and Server Hostname Filter fields.

    Example:

    IntradocServerPort=4444
    

    Server specific IntradocServerPort can be specified by appending a "." and a server name:

    IntradocServerPort.UCM_server1=5500
    
    SocketHostAddressSecurityFilter=127.0.0.1|10.196.18.56|0:0:0:0:0:0:0:1
  4. Click Save.
  5. Restart the Content Server instance.
Extending WebCenter Content: Inbound Refinery Components

WebCenter Content: Inbound Refinery components don't use WebLogic Server clustering for scale up and failover. You can deploy and configure multiple, independent Inbound Refinery Managed Servers for WebCenter Content to use.

WebCenter Content Scaleup and Ports

When you scale up WebCenter Content, the scaled-up server uses a port which is different from the port that you configured in the Configuration Wizard.

In the WebCenter Content configuration file, you must specify the IntradocServerPort value for each Managed Server instance. The port for each Managed Server instance that resides in one machine must be unique. For example, if Content_server1 and Content_server2 are in the same machine, the configuration file should look similar to the following:

IntradocServerPort=4444
IntradocServerPort.UCM_serverd1=4444
IntradocServerPort.UCM_serverd2=4445

Configuring Content Security

After WebCenter Content and a Content Server instance are deployed and initial configuration specified, you can set or modify some Content Server content security options using the Content Security tab on the System Properties utility Content Security tab or using the Content Security page accessed through the Administration interface.

Using content security options, you can:

  • Allow users with only Read privilege to a content item's security group to get a copy of the native file.

  • Allow only the author or a user with Admin privilege to a content item's security group to check out the content item.

  • Allow the author of a content item to delete the content item as long as they have Read privilege, where otherwise they would need Delete privilege to the content item's security group.

    Note:

    If a site is using Contribution Folders, then this setting means an author can delete the content item without having Delete privilege to the content item's security group.

  • Allow only globally predefined accounts to appear in the Accounts list on checkin page.

You must restart the Content Server instance for any configuration changes to take effect.

Configuring Internet Information Using Content Server

After the WebCenter Content domain and Content Server are deployed and initial configuration specified, you can view or modify Content Server Internet options using the Internet tab on the System Properties utility, or using the Internet Configuration page accessed through the Administration interface. Typically Internet options are specified during Oracle WebCenter Content installation and initial configuration.

  • To access the System Properties: Internet tab, see Running Administration Applications in Standalone Mode. Certain fields can only be modified using the System Properties utility.

  • To access the Internet Configuration page, choose Administration, then Admin Server, then Internet.

Using Internet configuration options, you can:

  • View the HTTP server address for the Content Server instance. For security reasons, this field cannot be changed from the interface. You must change the field using the Oracle WebCenter Content standalone application.

  • View and modify the IP Address Filter which lists IP addresses that can be used to access the Content Server instance.

  • View and modify the Intradoc Server Port, which is the server port number for the Content Server instance.

  • View whether a Secure Sockets Layer (SSL)-enabled web server is used. For security reasons, this field cannot be changed from the interface. You must change the field using the Oracle WebCenter Content standalone application.

  • View and modify the email server used to send email notifications from the Content Server instance

  • View the port used for SMTP communications. For security reasons, this field cannot be changed from the interface. You must change the field using the Oracle WebCenter Content standalone application.

  • View and modify the administrator email address that the Content Server instance uses to send email notifications.

You must restart the Content Server instance for any configuration changes to take effect.

Configuring System Database Properties

After WebCenter Content and a WebCenter Content Server instance are deployed and initial configuration specified, you can set or modify Content Server system database properties. The system database can be an Oracle Database, Microsoft SQL Server, IBM DB2, or another database.

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 the Oracle Technology Network at:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

See Configuring the WebCenter Content Domain in Installing and Configuring Oracle WebCenter Content.

Note:

For security reasons, the Content Server Administration interface cannot be used to configure these options. You must start the System Properties utility as a standalone application from the computer where the Content Server instance is installed. The method required to start this program differs slightly between Windows and UNIX installations. For details, see Running Administration Applications in Standalone Mode.

Using system database options, you can:

  • Modify whether JDBC is enabled and choose a driver option.

  • Modify whether the database is case sensitive (such as Oracle or Informix).

  • Modify whether a database driver classpath must be specified in the Database Driver Classpath field to support a database connection.

  • Specify the classpath for the database driver.

  • Specify the name of the JDBC driver.

  • Specify the connection string for the JDBC driver.

  • Specify the user name that owns the tables inside the database.

  • Specify the password for the user name that owns the tables inside the database.

You must restart the Content Server instance for any configuration changes to take effect.

About the Content Server System 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 for the system relational database, therefore JDBC user name and password information is no longer stored in the IntradocDir/config/config.cfg file and it is not managed through the System Properties utility.

Caution:

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

Content Server supports GridLink data sources for connections to an Oracle Database relational database for an Oracle Real Application Cluster (RAC). For details, see Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server and Oracle Fusion Middleware Administrator's Guide.

For information on configuring database connections for a Content Server instance running applications in standalone mode, see:

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 the Content Server instance for IBM DB2 searches requires the addition of the flag SSUseContains=false variable. To configure the Content Server instance:

  1. Open a new browser window, and log in to the Content Server instance as system administrator.
  2. Choose Administration, then Admin Server, then General Configuration.
  3. Add the following line in the Additional Configuration Variables area of the General Configuration page:
    SSUseContains=false
    
  4. Check that the variable DatabasePreserveCase is set to true (or 1) in the config.cfg file. If the variable is not set to true, add DatabasePreserveCase=true to the Additional Configuration Variables area of the General Configuration page
  5. Click Save.
  6. Restart the Content Server instance.

Configuring Oracle Content and Experience Integration Settings

Oracle Content and Experience integration with Content Server provides Oracle WebCenter Content users with the ability to store and retrieve documents in the Oracle Content and Experience cloud. It also allows users to copy content stored in the Content Server to Oracle Content and Experience cloud.

To configure Content Server to integrate with Oracle Content and Experience:
  1. Enable the OracleDocumentsFolders component using the Component Manager. See Enabling or Disabling a Component Using the Component Manager.

    Note:

    Ensure that the FrameworkFolders component is enabled before enabling the OracleDocumentsFolders component.

  2. Configure the Oracle Content and Experience connection information on the Oracle Content and Experience Integration Settings page.
    1. Open a new browser window, and log in to the Content Server instance as system administrator.

    2. Choose Administration, then Oracle Content and Experience. The Oracle Content and Experience Integration Settings page opens.

    3. Enter the following details:
      • Oracle Content and Experience URL
      • Oracle Content and Experience User Name
      • Oracle Content and Experience Password
    4. Select one of the following options from the Select when cloud folders can be shared drop-down list:
      • Never: To prevent sharing the cloud folder from the WebCenter Content user interface.
      • Creation: To enable sharing of a cloud folder when it is being created with only the folder owner’s ODCS account. After the folder is created, it cannot be shared.
      • Always: To enable sharing of a cloud folder during and after its creation. A cloud folder can be shared during its creation with the owner’s ODCS account, and after its creation, users who have access to the cloud folder can share it with their respective ODCS accounts
    5. Click Save.

      Note:

      You can test the Oracle Content and Experience Server connection settings by clicking the Test button.

    You must restart the Content Server instance for any configuration changes to take effect.

  3. Configure wildcard hostname verifier in Content Server using the Oracle WebLogic Server Administration Console.
    1. On the Administration Console home page, in the Domain Configurations area choose Environment, then Servers.

    2. On the Configuration tab for the Summary of Servers page, select the name of the WebCenter Content server for the Content Server instance.

    3. Click the SSL sub-tab, and expand Advanced.

    4. Configure the following settings:

      1. In the Hostname Verification field, select Custom Hostname Verifier.

      2. In the Custom Hostname Verifier field, enter weblogic.security.utils.SSWLSWildcardHostnameVerifier.

      3. Click Save.

Configuring Server Properties

After WebCenter Content and a Content Server instance are deployed and an initial configuration specified, you can set or modify Content Server options using the Server tab on System Properties utility.

Note:

For security reasons, the Content Server Administration interface cannot be used to configure these options. You must start the System Properties utility as a standalone application from the computer where the Content Server instance is installed. The method required to start this program differs slightly between Windows and UNIX installations. For details, see Running Administration Applications in Standalone Mode.

Using server options you can:

  • Specify how the Content Server instance handles several language-specific issues such as the language of the user interface, stemming rules, sort order, and date/time format.

  • Select the time zone in which the Content Server instance is located.

  • Specify the instance name that is displayed in the Windows Start menu.

  • Restrict access to the Content Server instance to computers with the specified IP address.

  • Specify the password for the proxy.

  • Specify whether internal JSP support is enabled in the Content Server instance.

  • Specify the security groups that are enabled for internal JSP support.

You must restart the Content Server instance for any configuration changes to take effect.

Caution:

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 system administrator access.

Hostname filter or IP Address filter values must be set to allow communication with the Content Server instance in the following situations:

  • Running Inbound Refinery and PDF Converter (even on the same physical computer as the Content Server instance).

  • Transferring Content Server archives between computers.

  • Configurations where the web server and the Content Server instance are on different systems.

  • EJB-enhanced operations.

  • Using the IdcCommand or IdcCommandX utilities on a system separate from the Content Server instance. (You must change the default value and specify the IP address of the web server.)

Configuring Localization Properties

After WebCenter Content and Content Server instance are deployed and an initial configuration specified, you can use the Localization tab on the System Properties utility to change language-specific items such as date/time format, default time zone, sort zone, and enabled interface languages.

You can use the Localization page to enable or disable locales for users to select in their User Profile.

Configuring 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:
    • Windows: Choose Start, then All Programs, then Content Server, then instance_name, then Utilities, then System Properties.

    • UNIX: Run the System Properties utility, which is located in the /bin subdirectory of the Content Server installation directory:

      ./SystemProperties
      
  2. Select the Localization tab.
  3. Choose the English-US entry in the list of locales, and click Edit.
  4. In the Configure Locale dialog, 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. Restart the Content Server instance for configuration changes to take effect.

Configuring Interface Language

To add, edit, remove, enable, or disable interface languages for the Content Server instance:

  1. Select a locale in the Localization tab of the System Properties utility using the same basic procedure described in Configuring Date Format.

  2. Make the interface language change, and click OK. Enabling a locale on the Localization tab also enables it on the Administration Localization page.

Specifying a Locale

Administrators can enable multiple locales so that users can select one of the enabled locales from their User Profile for their individual user interface language.

To specify what locales are enabled for users to select:

  1. On the Content Server main page, choose Administration, then Localization.
  2. Select the check boxes from the list of Enabled Locales to specify the languages.
  3. Click Update.

Configuring Paths Properties

After WebCenter Content and a Content Server instance are deployed and initial configuration specified, you can use the Paths tab on the System Properties utility to:

  • Modify the location of the browser executable that is used to display the online help from the standalone administration utilities and applications.

  • Modify the path to the Java class files.

  • Modify the path to the shared directory.

You must restart the Content Server instance for configuration changes to take effect.

Note:

For security reasons, the Content Server Administration interface cannot be used to configure these options. You must start the System Properties utility as a standalone application from the computer where the Content Server instance is installed. The method required to start this program differs slightly between Windows and UNIX installations. For details, see Running Administration Applications in Standalone Mode.