Oracle® Fusion Middleware

Configuration Reference for Oracle WebCenter Content

11g Release 1 (11.1.1)

E10726-07

April 2015

Documentation for administrators and developers that provides descriptions and syntax for Oracle WebCenter Content system configuration variables.

Oracle Fusion Middleware Configuration Reference for Oracle WebCenter Content, 11g Release 1 (11.1.1)

E10726-07

Copyright © 1996, 2015, Oracle and/or its affiliates. All rights reserved.

Primary Author: Kalpana N

Contributor: Oracle WebCenter Content development and support

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

What's New in This Guide

- New and Changed Features for 11g Release 1 (11.1.1.9)

- New and Changed Features for 11g Release 1 (11.1.1.8)

- New and Changed Features for 11g Release 1 (11.1.1.7)

- Other Significant Changes in this Book

1 Introduction to System Configuration Variables

- 1.1 Document Organization

- 1.2 Oracle WebCenter Content Terminology

2 Configuration Variables List by Usage

- 2.1 Archiver

- 2.2 Batch Loader

- 2.3 Clients

- 2.4 Content Tracker

- 2.5 Content Items

- 2.6 Content Profiles

- 2.7 Content Server

- 2.8 Conversion

- 2.8.1 Inbound Refinery

- 2.8.2 PDF Converter

- 2.8.2.1 General Variables

- 2.8.2.2 Microsoft Office

- 2.8.2.3 InDesign

- 2.8.2.4 Other Formats

- 2.8.3 Dynamic Converter

- 2.9 Database

- 2.10 Date and Time

- 2.11 Debugging

- 2.12 Directories and Paths

- 2.13 Field Display

- 2.14 Folders and WebDAV

- 2.15 HTML Preview

- 2.16 Indexing

- 2.17 JSP

- 2.18 Localization

- 2.19 Page Display

- 2.20 Pop-Up Calendar

- 2.21 Records

- 2.22 Schema

- 2.23 Searching

- 2.24 Security

- 2.24.1 Internal Security

- 2.24.2 External Security

- 2.25 Strings

- 2.26 Users

- 2.27 Web Server

- 2.28 Workflow

3 Configuration Variables

- AccessListPrivilegesGrantedWhenEmpty

- AccesslistPrivilegesGrantedWhenEmpty

- AdditionalIndexBuildParams

- AdditionalSubscriptionCollatedFieldList

- AllowAllRedirectUrls

- AllowAlternateMetaFile

- AllowConcurrentUpdate

- AllowForceDelete

- AllowMatchesInDateCheck

- AllowPrimaryMetaFile

- AllowRetentionPeriodWithoutCutoff

- AllowSamePrimaryAlternateExtensions

- AllowSecondaryConversion

- AllowSkippedHyperlinktoCauseIncomplete

- AppendToAllowedUploadServices

- AppletChunkSize

- AppletChunkThreshold

- ArchiverDoLocks

- ArchiverTouchMonitorInterval

- ArchiverTraceLockMaintenance

- ArchiverTraceLocks

- AuthorDelete

- AutoNumberPrefix

- AutoNumberWidth

- BatchLoaderPath

- BatchLoaderUserName

- BinDir

- CachedResultRowCount

- ChunkedRequestTrace

- CleanUp

- ClearMissingAttributes

- coaoShowLinkExtensions

- CollectionDeleteEnabled

- CollectionHiddenMeta

- CollectionInfoEnabled

- CollectionInhibitUpdateMeta

- CollectionLinkEnabled

- CollectionLocation

- CollectionMeta

- CollectionMoveEnabled

- CollectionReadOnlyMarkedFolders

- CollectionReadOnlyMeta

- CollectionReleasedOnly

- CollectionSecurityReadOnly

- CollectionTrashDeleteDate

- CollectionTrashDeleteLocation

- CollectionTrashDeleteOldName

- CollectionTrashDeleter

- CollectionWebDAVServer

- ColumnMapFile

- ConfigDir

- ConversionCacheExpirationPeriodInDays

- CookieAuthTimeoutInDays

- CookieProxyPassword

- createAlternateMetaFile

- createPrimaryMetaFile

- DatabasePreserveCase

- DatabaseWildcards

- DatedCacheIntervalDays

- DataDir

- DateOutputFormat

- DCMaxFileSize

- DCTimeOut

- DCViewFormat

- DebugStdConversion

- DefaultAccounts

- DefaultFilterInputFormat

- DefaultFilterOutputFormat

- DefaultGraphicTimeout

- DefaultHtmlConversion

- DefaultHtmlRefreshTimeoutInSeconds

- DefaultNativeTimeout

- DefaultPasswordEncoding

- DefaultPostscriptTimeout

- DirectoryLockingLogPath

- DisableContentProfiles

- DisableDBLongIntegerField

- DisableESigSSLCheck

- DisableForcedConversions

- DisableGzipCompression

- DisableHttpUploadChunking

- DisableKeepingForcedConversions

- DisableOptimizedLatestReleaseQuerying

- DisableSharedCacheChecking

- DistillerPath

- DoDocNameOrder

- dodSkipCatFolderRequirement

- DomainControllerName

- DoMetaInternetSearch

- DownloadApplet

- DtmPort

- DynamicConverterHtmlFlavor

- EmailNotificationType

- EnableDocumentHighlight

- EnableEnvironmentPackager

- EnableErrorFile

- EnableExpirationNotifier

- EnableRebuildForcesReconversion

- EnableSchemaPublish

- ExclusiveCheckout

- ExpireRevisionOnly

- FileEncoding

- FldEnforceCaseInsensitiveNameUniqueness

- FldEnforceFolderFileNameUniqueness

- ForcedConversionRules

- ForceDistinctRevLabels

- ForceDocTypeChoice

- ForceJdbcSync

- ForcePermissionCheckforAllowedUploadServices

- ForceSecurityGroupChoice

- FormInheritMetaDataFieldList

- FrameMakerCyclesAllowed

- FrameMakerTimeout

- GetCopyAccess

- HasExternalUsers

- HasSiteStudio

- HideVitalReview

- HighlightBegin

- HighlightEnd

- HtmlDataInputFilterLevel

- HTMLEditorPath

- HttpAbsoluteCgiRoot

- HttpAbsoluteWebRoot

- HttpBrowserHttpHostDoesNotHavePort

- HttpIgnoreWebServerInternalPortNumber

- HttpRelativeCgiRoot

- HttpRelativeWebRoot

- HttpServerAddress

- IDC_Name

- IdcAnalyzeLogDir

- IdcAuthExtraRequestParams

- IdcCommandFile

- IdcCommandLog

- IdcCommandServerHost

- IdcCommandUser

- IdcHttpHeaderVariables

- IdcHomeDir

- IdcLocale

- IdcNativeDir

- IdcResourcesDir

- IdcServerBindAddress

- IdcServerSocketQueueDepth

- IdcServerThreadQueryTimeout

- IndexableRenditions

- IndexerAutoWorkInterval

- IndexerLargeFileSize

- IndexerRebuildStagingManualCopy

- IndexerRebuildStagingPath

- IndexerTouchMonitorInterval

- IndexerTraceCycleListChanges

- IndexerTraceLockFileChanges

- IndexerTraceStartStop

- InitialColID

- InstanceDescription

- InstanceMenuLabel

- IntradocDir

- IntradocRealm

- IntradocServerHostName

- IntradocServerPort

- IsAllowIndexRenditions

- IsAutoArchiver

- IsAutoNumber

- IsAutoQueue

- IsAutoSearch

- IsContentRefineryPresent

- IsDpSubmitErrorFatal

- IsDynamicConverterEnabled

- IsFormsPresent

- IsJava

- IsJdbcLockTrace

- IsJdbcQueryTrace

- IsJspServerEnabled

- IsOverrideFormat

- IsPageDebug

- isPhysicallySplitDir

- IsPrimaryUserBase

- isRepromptLogin

- IsSavedWfCompanionFile

- isValidateFile

- IsWebServerPagesOnly

- JdbcConnectionString

- JdbcDriver

- JdbcPassword

- JdbcPasswordEncoding

- JdbcUser

- JspAdminQuery

- JspDefaultIndexPage

- JspEnabledGroups

- JvmCommandLine

- LatestReleasedTimestampTimeout

- LdapAdminDN

- LdapAdminPassword

- LdapPort

- LdapServer

- LdapSuffix

- LkDisableOnRebuild

- LkDisableReferenceInfo

- LkDisallowConversionFormats

- LkIsSecureSearch

- LkReExtractOnRebuild

- LkRefreshBatchSize

- LkRefreshErrorPercent

- LkRefreshErrorsAllowed

- LkRefreshErrorThreshold

- LmDefaultLayout

- LmDefaultSkin

- LocaleArchiverDateFormat

- LogMessagePrefix

- LogName

- MacSupportsSignedApplets

- MailServer

- MajorRevSeq

- MaxArchiveErrorsAllowed

- MaxCollectionSize

- MaxConversionCacheSizeInMegs

- MaxDocIndexErrors

- MaxErrorsAllowed

- MaxIndexableFileSize

- MaxIntegerAllowed

- MaxNumRecursiveStepDefinitions

- MaxQueryRows

- MaxRequestThreadCount

- MaxResults

- MaxRowsPerTableArchiveExportBatch

- MaxSavedSearchResults

- MaxSearchableSubfolders

- MaxSearchConnections

- MaxSizeResourceFileCacheMillions

- MaxStandardDatabaseResults

- MemoFieldSize

- MinIndexableFileSize

- MinIntegerAllowed

- MinMemoFieldSize

- MinorRevSeq

- MSPubexePath

- MultiUpload

- NeverTimeoutForcedConversionsTemplateChange

- NoAutomation

- noInfoColumn

- noRevisionsColumn

- NoSearchConnectionCloseOnDocChange

- NotationForRequiredFields

- NotificationIntervalInDays

- NotificationMaximum

- NotificationQuery

- NotifyExtras

- NotifyTime

- NtlmSecurityEnabled

- NumAdditionalRenditions

- NumConnections

- OdbcDateFormat

- OpenOfficeListenerPort

- OpenOfficeListenerURL

- OpenOfficePath

- PageMakerExePath

- PLUGIN_DEBUG

- PostConversionTimeOut

- PostprocessPDFPath

- PostscriptPrinterName

- PowerPointPrintOutput

- PreconversionPath

- PreconversionWaitTime

- PreviewOutputExtension

- PreviewPath

- PrimaryWorkQueueTimeout

- PrinterPortPath

- Priority

- ProcessExcelUrlHyperlinks

- ProcessInDesignBookMarks

- ProcessInDesignHyperlinks

- ProcessInDesignInternalPDFThumbnail

- ProcessInDesignLinkUpdate

- ProcessInDesignPDFCompatibility50

- ProcessPowerpointHyperlinks

- ProcessVisioInternalHyperlinks

- ProcessVisioUrlHyperlinks

- ProcessWordBookMarks

- ProcessWordComments

- ProcessWordEmailLinks

- ProcessWordFootEndNote

- ProcessWordHeadings

- ProcessWordHyperlinks

- ProcessWordToc

- ProcessWordUrlHyperlinks

- ProviderClass

- ProviderConfig

- ProviderConnection

- ProviderCredentialsMap

- ProviderDir

- ProviderType

- pucDefaultTime

- pucEnableOnSearch

- pucHideTimeInDateFields

- pucUseMonthLocale

- pucUseWeekdayLocale

- pucXOffset

- pucYOffset

- pucZIndex

- QueueDir

- RecordsManagementDenyAuthorFreePassOnRMSecurity

- RecordsManagementNumberOverwriteOnDelete

- RedirectHostsFilter

- RequestAuditAdditionalVerboseFieldsList

- RequestAuditIntervalSeconds1

- RequestAuditIntervalSeconds2

- RequestAuditListDepth1

- RequestAuditListDepth2

- RequestAuditSubClassificationField

- ResultsTitle

- RmaAddDocWhereClauseForScreening

- RmaAllowKeepOrDestroyMetadataOption

- RmaEnableFilePlan

- RmaEnableFixedClones

- RmaEnablePostFilterOnScreening

- RmaFilePlanVolumePrefix and RmaFilePlanVolumeSuffix

- RmaFixedClonesTitleSuffix

- RMAHideExternalFieldsFromCheckInUpdate

- RMAHideExternalFieldsFromSearchInfo

- RmaNotifyDispReviewerAndCatAuthor

- RmaNotifyReviewerAndAlternateReviewer

- rule:IsFragmentOnly

- SceUseNativeInDataFeeds

- SchemaAllowRecursiveFileMove

- SchemaBuildDigestFile

- SchemaPublishCheckInterval

- SchemaPublishInterval

- SchemaPublishMaximumInterval

- SchemaPublishMinimumInterval

- SchemaPublishRenameRetryInitialInterval

- SchemaPublishRenameRetryIterations

- SchemaPublishRetryInterval

- SchemaPublishRetryIntervalMax

- SchemaVerifyPublishing

- SchemaWin32RenameDelayInterval

- SctAutoTruncateDataStrings

- SctComponentDir

- SctDebugLogEnabled

- SctDebugLogFilePath

- SctDebugServiceBinderDumpEnabled

- SctDoNotArchive

- SctDoNotPopulateAccessLogColumns

- SctExternalUserLogEnabled

- SctFilterPluginLogDir

- SctIgnoreDirectories

- SctIgnoreFileTypes

- SctLogDir

- SctLogEnabled

- SctLogSecurity

- SctMaxRecentCount

- SctMaxRereadTime

- SctReductionAvailableDatesLookback

- SctReductionLogDir

- SctReductionRequireEventLogs

- SctrEnableSecurityCheck

- SctScheduledReductionEnable

- SctSimplifyUserAgents

- SctSnapshotEnable

- SctSnapshotLastAccessEnable

- SctSnapshotLastAccessField

- SctSnapshotLongCountEnable

- SctSnapshotLongCountField

- SctSnapshotLongCountInterval

- SctSnapshotShortCountEnable

- SctSnapshotShortCountField

- SctSnapshotShortCountInterval

- SctTrackContentAccessOnly

- SctUseGMT

- SearchCacheCleanerInterval

- SearchCacheMaxItemAgeInMinutes

- SearchDebugLevel

- SearchDir

- SearchIndexerEngineName

- SearchQueryFormat

- SearchQueryTrace

- SecondaryConversionStepName

- SelfRegisteredAccounts

- SelfRegisteredRoles

- ServiceStartupTimeout

- ShowContentForStorageBrowse

- ShowCreateExternalMenu

- showDocActions

- ShowEmailMetadataMenu

- ShowHyperlinkBox

- IsSimpleProfilesEnabled

- ShowOnlyKnownAccounts

- ShowRevisionsColumn

- showSearchResultsCheckoutColumn

- SkipMozillaMailToWorkaround

- SmtpPort

- SocketHostAddressSecurityFilter

- SocketHostNameSecurityFilter

- SourcePath

- StdPageWidth

- StrConfineOverflowChars

- StyleForRequiredFields

- SubjectsDir

- SubscriptionCollatedFieldList

- SubscriptionMethod

- SysAdminAddress

- SystemDateFormat

- SystemLocale

- SystemTimeZone

- TempDir

- TextIndexerFilterValidateFormats

- TimeoutChangedTemplateForcedConversionsInMins

- TimeoutMismatchedForcedConversionsInMins

- TimeoutPerOneMegInSec

- TraceConversionCacheCleanup

- TraceResourceConflict

- TraceResourceLoad

- TraceResourceOverride

- UieHideSearchCheckboxes

- UniversalSearchAllowFullText

- UploadApplet

- UseAccounts

- UseAdsi

- UseCascadingStyleSheets

- UseDatabaseWfInQueue

- UseDatabaseShortIndexName

- UseFourDigitYear

- UseNestedGroups

- UseNetscape

- UseNtlm

- UserCache

- UserCacheMaxSize

- UserCacheClusterSupport

- UserCacheMaxSizeMatchInitialSize

- UserCacheTimeout

- UseRedirectedOutput

- UseRevisionCreateDate

- UserFilteredSubjects

- UseSearchCache

- UseSecureLdap

- UseSSL

- VaultDir

- VerboseMode

- WarnAboutTimeZone

- WebBrowserPath

- WebDAVMaxInactiveInterval

- WeblayoutDir

- WebServerAuthOnly

- WorkflowDir

- WorkflowIntervalHours

- XMLEncodingMode

Preface

This document describes system configuration variables used in Oracle WebCenter Content.

Audience

This guide is intended for administrators and developers who use variables to access and customize Oracle WebCenter Content functions.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in the Oracle WebCenter Content documentation set:

- Oracle WebCenter Content Release Notes

- Oracle Fusion Middleware Services Reference for Oracle WebCenter Content

- Oracle Fusion Middleware Developing with Oracle WebCenter Content

- Oracle Middleware Administering Oracle WebCenter Content

- Oracle Middleware Managing Oracle WebCenter Content

Further details about Oracle WebCenter Content Server can be found in The Definitive Guide to Stellent Content Server Development by Brian Huff, 2006, Apress, Berkeley, CA.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

What's New in This Guide

The following topics introduce the new and changed features of Oracle WebCenter Content and other significant changes that are described in this guide, and provide pointers to additional information

New and Changed Features for 11g Release 1 (11.1.1.9)

Oracle WebCenter Content 11g Release 1 (11.1.1.9) contains the following new or changed configuration variables:

- MaxRowsPerTableArchiveExportBatch sets the maximum number of rows in a table to be archived before exporting Folders structure data.

- SceUseNativeInDataFeeds enables the SESCrawlerExport component to select a web viewable file or a native file for indexing.

New and Changed Features for 11g Release 1 (11.1.1.8)

Oracle WebCenter Content 11g Release 1 (11.1.1.8) contains the following new or changed configuration variables:

- EmailNotificationType specifies where the links in notification emails point for workflows and subscriptions in different Content Server user interfaces.

- DisableESigSSLCheck disables the SSL requirement for Electronic Signature when used in workflows.

- HttpBrowserHttpHostDoesNotHavePort notifies Content Server that the HTTP address that it computed for the Content Server's administration server and applets does not have a port number and it needs to look for a port number.

- CachedResultRowCount default value has changed.

- coaoShowLinkExtensions limits the display of the Check Out and Open component Edit action menu to the specified file extension values.

- The following variables have been removed and are no longer supported:

- ARCHIVE_COLLECTION

- SearchCacheHardLimit

- SearchCacheSoftLimit

- SearchCacheTrace

- SearchConnectionWaitTimeout

New and Changed Features for 11g Release 1 (11.1.1.7)

Oracle WebCenter Content 11g Release 1 (11.1.1.7) includes the following new and changed configuration variables:

- DoMetaInternetSearch, enables Internet search syntax for metadata fields.

- FldEnforceFolderFileNameUniqueness, makes name-uniqueness checks for folder and file names case-insensitive, and makes path resolution case-insensitive.
This variable prevents folders from having a child folder with the same name as a child document.

- MaxIndexableFileSize, sets a maximum document file size for indexing.

- MinIndexableFileSize, sets a minimum document file size for indexing.

- UseNestedGroups, used with JPS provider, specifies whether Oracle WebCenter Content Server retrieves users' direct and indirect group membership in the authentication provider.

Other Significant Changes in this Book

For 11g Release 1 (11.1.1.7), this guide was updated in several ways.

- This book was restructured so that it contains only information about configuration variables that can be used in the Oracle WebCenter Content config.cfg file, intradoc.cfg file, and other .cfg files. Some variables also can be used with Idoc Script.
All information about Idoc Script, Idoc Script functions, and variables that are used only in Idoc Script, was moved to Oracle Fusion Middleware Developing with Oracle WebCenter Content.

- The lists of content for each chapter (core Content Server variables, management and configuration variables, and feature variables) were removed.

- The master list for Type was removed.

- The master list for Usage was revised to reference only configuration variables.

1 Introduction to System Configuration Variables

This guide describes Oracle WebCenter Content system configuration variables usage and syntax, and provides examples of configuration settings.

This chapter covers these topics:

- Document Organization

- Oracle WebCenter Content Terminology

1.1 Document Organization

The information contained in this guide is based on Oracle WebCenter Content 11g Release 1 (11.1.1). The information is subject to change as the product technology evolves and as hardware and operating systems are created and modified. Due to the technical nature of browsers, databases, web servers, and operating systems, Oracle cannot warrant compatibility with all versions and features of third-party products.

This guide is divided into the following chapters:

- Chapter 2, "Configuration Variables List by Usage," lists all variables sorted by where they are used in Oracle WebCenter Content (for example, in Debugger, or in Inbound Refinery).

- Chapter 3, "Configuration Variables," lists all variables in alphabetical order.

1.2 Oracle WebCenter Content Terminology

Oracle WebCenter Content documentation uses the following terms when referring to variables in the directories associated with the Oracle WebCenter Content and Oracle WebCenter Content Server configuration:

- IdcHomeDir: This variable refers to the ucm/idc directory in the Oracle WebCenter Content home where the Oracle WebCenter Content server media is located. The server media can run Oracle WebCenter Content Server, Oracle WebCenter Content: Inbound Refinery, or Oracle WebCenter Content: Records software. This is essentially a read-only directory. The default location is WCC_ORACLE_HOME/ucm/idc. The variable portion of the default location can be changed, but the path cannot be changed from ucm/idc.

- DomainHome: This variable refers to the user-specified directory where an Oracle WebCenter Content application is deployed to run on an Oracle WebLogic Server application server. The DomainHome/ucm/short-product-id/bin directory contains the intradoc.cfg file and executables. The default location for DomainHome is MW_HOME/user_projects/domains/base_domain, but you can change the path and domain name (base_domain) during the deployment of an Oracle WebCenter Content application to an application server.

- short-product-id: This variable refers to the type of Oracle WebCenter Content server deployed to an application server. This name is used as the context root (default HttpRelativeWebRoot configuration value). Possible values include:

- cs (Oracle WebCenter Content Server)

- ibr (Oracle WebCenter Content: Inbound Refinery)

- urm (Oracle WebCenter Content: Records)

- IntradocDir: This variable refers to the root directory for configuration and data files specific to an Oracle WebCenter Content instance that is part of an Oracle WebCenter Content application deployed to an application server. This Idoc Script variable is configured for one type of Oracle WebCenter Content instance: Content Server (cs), Inbound Refinery (ibr), or Records (urm). This directory can be located elsewhere, but the default location is DomainHome/ucm/short-product-id. The specified directory must be an absolute path to the instance directory and must be unique to a particular server or node. The directory includes a bin/ directory, which contains the startup files (intradoc.cfg and executables).

2 Configuration Variables List by Usage

This chapter lists Oracle WebCenter Content variables grouped by common usage.

This chapter covers the following topics:

- Archiver

- Batch Loader

- Clients

- Content Tracker

- Content Items

- Content Profiles

- Content Server

- Conversion

- Database

- Date and Time

- Debugging

- Directories and Paths

- Field Display

- Folders and WebDAV

- HTML Preview

- Indexing

- JSP

- Localization

- Page Display

- Pop-Up Calendar

- Records

- Schema

- Searching

- Security

- Strings

- Users

- Web Server

- Workflow

2.1 Archiver

The following variables are related to the Archiver utility:

AllowMatchesInDateCheck
ArchiverDoLocks
ArchiverTouchMonitorInterval
ArchiverTraceLockMaintenance
ArchiverTraceLocks
CollectionLocation
IsAutoArchiver
LocaleArchiverDateFormat
MaxArchiveErrorsAllowed
MaxRowsPerTableArchiveExportBatch
OdbcDateFormat

2.2 Batch Loader

The following variables are related to the Batch Loader utility:

BatchLoaderPath
BatchLoaderUserName
CleanUp
EnableErrorFile
MaxErrorsAllowed

2.3 Clients

The following variables are related to client applications:

AppendToAllowedUploadServices
DownloadApplet
ForcePermissionCheckforAllowedUploadServices
MacSupportsSignedApplets
MultiUpload
showDocActions
UploadApplet

2.4 Content Tracker

The following variables are related to the Content Tracker application:

SctAutoTruncateDataStrings
SctComponentDir
SctDebugLogEnabled
SctDebugLogFilePath
SctDebugServiceBinderDumpEnabled
SctDoNotArchive
SctDoNotPopulateAccessLogColumns
SctExternalUserLogEnabled
SctFilterPluginLogDir
SctIgnoreDirectories
SctIgnoreFileTypes
SctLogDir
SctLogEnabled
SctLogSecurity
SctMaxRecentCount
SctMaxRereadTime
SctReductionAvailableDatesLookback
SctReductionLogDir
SctReductionRequireEventLogs
SctrEnableSecurityCheck
SctScheduledReductionEnable
SctSimplifyUserAgents
SctSnapshotEnable
SctSnapshotLastAccessEnable
SctSnapshotLastAccessField
SctSnapshotLongCountEnable
SctSnapshotLongCountField
SctSnapshotLongCountInterval
SctSnapshotShortCountEnable
SctSnapshotShortCountField
SctSnapshotShortCountInterval
SctTrackContentAccessOnly
SctUseGMT

2.5 Content Items

The following variables are related to content items:

AllowAlternateMetaFile
AllowForceDelete
AllowPrimaryMetaFile
AllowSamePrimaryAlternateExtensions
AutoNumberPrefix
AutoNumberWidth
CachedResultRowCount
createAlternateMetaFile
createPrimaryMetaFile
EmailNotificationType
EnableExpirationNotifier
ExpireRevisionOnly
FormInheritMetaDataFieldList
ForceDistinctRevLabels
ForceDistinctRevLabels
HasSiteStudio
IsAutoNumber
LkDisableReferenceInfo
LkDisallowConversionFormats
LkIsSecureSearch
LkReExtractOnRebuild
LkRefreshBatchSize
LkRefreshErrorsAllowed
LkRefreshErrorPercent
LkRefreshErrorThreshold
MinorRevSeq
MinorRevSeq
noInfoColumn
noRevisionsColumn
NotificationMaximum
NotificationQuery
NotifyExtras
NotifyTime
NumAdditionalRenditions
showDocActions

2.6 Content Profiles

The following variables are related to the Content Profiles application:

DisableContentProfiles
IsDpSubmitErrorFatal

2.7 Content Server

The following variables are related to Content Server:

AccessListPrivilegesGrantedWhenEmpty
AdditionalSubscriptionCollatedFieldList
AppendToAllowedUploadServices
AppletChunkSize
AppletChunkThreshold
ChunkedRequestTrace
ClearMissingAttributes
coaoShowLinkExtensions
CookieAuthTimeoutInDays
CookieProxyPassword
DefaultHtmlRefreshTimeoutInSeconds
DefaultPasswordEncoding
DisableDBLongIntegerField
DisableHttpUploadChunking
DisableSharedCacheChecking
DoDocNameOrder
DownloadApplet
FileEncoding
FldEnforceCaseInsensitiveNameUniqueness
FldEnforceFolderFileNameUniqueness
ForcePermissionCheckforAllowedUploadServices
HasExternalUsers
HttpAbsoluteCgiRoot
HttpAbsoluteWebRoot
HttpRelativeCgiRoot
IDC_Name
IdcCommandFile
IdcCommandLog
IdcCommandServerHost
IdcCommandUser
IdcServerBindAddress
IdcServerSocketQueueDepth
IdcServerThreadQueryTimeout
InstanceDescription
InstanceMenuLabel
IntradocServerHostName
IntradocServerPort
IsFormsPresent
isValidateFile
IsWebServerPagesOnly
JvmCommandLine
LmDefaultLayout
LmDefaultSkin
LogMessagePrefix
LogName
MacSupportsSignedApplets
MailServer
MaxIntegerAllowed
MaxQueryRows
MaxRequestThreadCount
MaxRowsPerTableArchiveExportBatch
MaxSizeResourceFileCacheMillions
MaxStandardDatabaseResults
MinIntegerAllowed
MinIntegerAllowed
MinorRevSeq
NoAutomationSceUseNativeInDataFeeds
PrimaryWorkQueueTimeout
ProviderClass
ProviderConfig
ProviderConnection
ProviderCredentialsMap
ProviderType
SceUseNativeInDataFeeds
ServiceStartupTimeout
ShowCreateExternalMenu
SkipMozillaMailToWorkaround
SmtpPort
SubscriptionCollatedFieldList
SubscriptionMethod
SysAdminAddress
UploadApplet
UserCacheClusterSupport
UserCacheMaxSizeMatchInitialSize
UserCacheMaxSize
UserCacheTimeout
UseRevisionCreateDate
XMLEncodingMode

2.8 Conversion

This section describes the variables that are related to various conversion applications:

- Section 2.8.1, "Inbound Refinery"

- Section 2.8.2, "PDF Converter"

- Section 2.8.3, "Dynamic Converter"

2.8.1 Inbound Refinery

The following variables are related to Inbound Refinery.

AllowSecondaryConversion
DefaultFilterInputFormat
DefaultFilterOutputFormat
DefaultGraphicTimeout
DefaultNativeTimeout
DefaultNativeTimeout
FileEncoding
IsAutoQueue
IsContentRefineryPresent
JvmCommandLine
MaxConversionCacheSizeInMegs
MaxNumRecursiveStepDefinitions
PostConversionTimeOut
PreconversionPath
PreconversionWaitTime
QueueDir
SecondaryConversionStepName
VaultDir
VerboseMode
WeblayoutDir

2.8.2 PDF Converter

This section lists the variables that are related to PDF Converter:

- Section 2.8.2.1, "General Variables"

- Section 2.8.2.2, "Microsoft Office"

- Section 2.8.2.3, "InDesign"

- Section 2.8.2.4, "Other Formats"

2.8.2.1 General Variables

The following variables are related to PDF Converter:

DefaultPostscriptTimeout
DistillerPath
NumAdditionalRenditions
PostprocessPDFPath
PostscriptPrinterName
PrinterPortPath
ShowHyperlinkBox

2.8.2.2 Microsoft Office

The following variables are related to the use of Microsoft Office applications with PDF Converter:

AllowSkippedHyperlinktoCauseIncomplete
OpenOfficePath
PowerPointPrintOutput
ProcessExcelUrlHyperlinks
ProcessPowerpointHyperlinks
ProcessVisioInternalHyperlinks
ProcessVisioUrlHyperlinks
ProcessWordBookMarks
ProcessWordComments
ProcessWordEmailLinks
ProcessWordFootEndNote
ProcessWordHeadings
ProcessWordHyperlinks
ProcessWordToc
ProcessWordUrlHyperlinks

2.8.2.3 InDesign

The following variables are related to the use of Adobe InDesign with PDF Converter:

ProcessInDesignBookMarks
ProcessInDesignHyperlinks
ProcessInDesignInternalPDFThumbnail
ProcessInDesignLinkUpdate
ProcessInDesignPDFCompatibility50

2.8.2.4 Other Formats

The following variables are related to the use of various native applications with PDF Converter:

FrameMakerCyclesAllowed
FrameMakerTimeout
MSPubexePath
OpenOfficeListenerPort
OpenOfficeListenerURL
PageMakerExePath

2.8.3 Dynamic Converter

The following variables are related to Dynamic Converter:

ConversionCacheExpirationPeriodInDays
DatedCacheIntervalDays
DCMaxFileSize
DCTimeOut
DCViewFormat
DefaultFilterInputFormat
DefaultFilterOutputFormat
DefaultHtmlConversion
DisableForcedConversions
DisableKeepingForcedConversions
DisableOptimizedLatestReleaseQuerying
DynamicConverterHtmlFlavor
EnableRebuildForcesReconversion
ForcedConversionRules
HighlightBegin
HighlightEnd
IsDynamicConverterEnabled
LatestReleasedTimestampTimeout
MaxConversionCacheSizeInMegs
NeverTimeoutForcedConversionsTemplateChange
rule:IsFragmentOnly
TimeoutChangedTemplateForcedConversionsInMins
TimeoutMismatchedForcedConversionsInMins
TraceConversionCacheCleanup
UseCascadingStyleSheets

2.9 Database

The following variables are related to databases:

ColumnMapFile
ConfigDir
DatabasePreserveCase
DatabaseWildcards
ForceJdbcSync
IsJdbcLockTrace
IsJdbcQueryTrace
JdbcConnectionString
JdbcDriver
JdbcPassword
JdbcPasswordEncoding
JdbcUser
MemoFieldSize
MinMemoFieldSize
NumConnections
UseDatabaseShortIndexName

2.10 Date and Time

The following variables are related to the formatting and manipulation of dates and times:

DateOutputFormat
SystemDateFormat
SystemTimeZone
UseFourDigitYear
WarnAboutTimeZone

2.11 Debugging

The following variables are related to debugging:

ArchiverTraceLockMaintenance
ArchiverTraceLocks
ChunkedRequestTrace
DebugStdConversion
DirectoryLockingLogPath
EnableEnvironmentPackager
EnableErrorFile
ForceJdbcSync
IdcAnalyzeLogDir
IndexerTraceCycleListChanges
IndexerTraceLockFileChanges
IndexerTraceStartStop
IsJava
IsJdbcLockTrace
IsJdbcQueryTrace
IsPageDebug
LogMessagePrefix
LogName
PLUGIN_DEBUG
RequestAuditAdditionalVerboseFieldsList
RequestAuditIntervalSeconds1
RequestAuditIntervalSeconds2
RequestAuditListDepth1
RequestAuditListDepth2
RequestAuditSubClassificationField
SearchDebugLevel
SearchQueryTrace
TempDir
TraceResourceConflict
TraceResourceLoad
TraceResourceOverride
UseRedirectedOutput
VerboseMode

2.12 Directories and Paths

The following variables are related to directories and file paths:

BinDir
CollectionLocation
ConfigDir
DataDir
HTMLEditorPath
HttpAbsoluteCgiRoot
HttpAbsoluteWebRoot
HttpRelativeCgiRoot
HttpRelativeWebRoot
HttpServerAddress
IdcAnalyzeLogDir
IdcHomeDir
IdcNativeDir
IdcResourcesDir
IntradocDir
isPhysicallySplitDir
ProviderDir
SearchDir
SubjectsDir
TempDir
UserCache
VaultDir
WebBrowserPath
WeblayoutDir
WorkflowDir

2.13 Field Display

The following variables are related to the display of metadata fields on Content Server web pages:

ForceDocTypeChoice
ForceSecurityGroupChoice
IsOverrideFormat
MemoFieldSize
MinMemoFieldSize
NotationForRequiredFields
ShowOnlyKnownAccounts
ShowRevisionsColumn
StyleForRequiredFields

2.14 Folders and WebDAV

The following variables are related to Contribution Folders and WebDAV installation and use:

CollectionDeleteEnabled
CollectionHiddenMeta
CollectionInfoEnabled
CollectionInhibitUpdateMeta
CollectionLinkEnabled
CollectionMeta
CollectionMoveEnabled
CollectionReadOnlyMarkedFolders
CollectionReadOnlyMeta
CollectionReleasedOnly
CollectionSecurityReadOnly
CollectionTrashDeleteDate
CollectionTrashDeleteLocation
CollectionTrashDeleteOldName
CollectionTrashDeleter
CollectionWebDAVServer
InitialColID
MaxSearchableSubfolders
WebDAVMaxInactiveInterval

2.15 HTML Preview

The following variables are related to HTML Preview:

DtmPort
DisableGzipCompression
PreviewOutputExtension
PreviewPath

2.16 Indexing

The following variables are related to indexing:

AdditionalIndexBuildParams
AllowConcurrentUpdate
DateOutputFormat
IndexableRenditions
IndexerAutoWorkInterval
IndexerLargeFileSize
IndexerRebuildStagingManualCopy
IndexerRebuildStagingPath
IndexerTouchMonitorInterval
IndexerTraceCycleListChanges
IndexerTraceLockFileChanges
IndexerTraceStartStop
IsAllowIndexRenditions
LkDisableOnRebuild
LkRefreshErrorsAllowed
MaxCollectionSize
MaxDocIndexErrors
MaxIndexableFileSize
MinIndexableFileSize
SceUseNativeInDataFeeds
TimeoutPerOneMegInSec
TextIndexerFilterValidateFormats

2.17 JSP

The following variables are related to JSP support:

IsJspServerEnabled
JspAdminQuery
JspDefaultIndexPage
JspEnabledGroups

2.18 Localization

The following variables are related to localization:

DefaultFilterInputFormat
DefaultFilterOutputFormat
FileEncoding
IdcLocale
LocaleArchiverDateFormat
SystemDateFormat
SystemLocale
SystemTimeZone
WarnAboutTimeZone

2.19 Page Display

The following variables are related to the display of Content Server web pages:

noInfoColumn
noRevisionsColumn
ResultsTitle
showDocActions
showSearchResultsCheckoutColumn
StdPageWidth

2.20 Pop-Up Calendar

The following variables are used with Pop-Up Calendar:

pucDefaultTime
pucEnableOnSearch
pucHideTimeInDateFields
pucUseMonthLocale
pucUseWeekdayLocale
pucXOffset
pucYOffset
pucZIndex

2.21 Records

The following variables are used with Oracle WebCenter Content: Records:

AccesslistPrivilegesGrantedWhenEmpty
AllowRetentionPeriodWithoutCutoff
dodSkipCatFolderRequirement
HideVitalReview
RecordsManagementDenyAuthorFreePassOnRMSecurity
RecordsManagementNumberOverwriteOnDelete
RmaAddDocWhereClauseForScreening
RmaAllowKeepOrDestroyMetadataOption
RmaEnableFilePlan
RmaEnableFixedClones
RmaEnablePostFilterOnScreening
RmaFilePlanVolumePrefix and RmaFilePlanVolumeSuffix
RmaFixedClonesTitleSuffix
RMAHideExternalFieldsFromCheckInUpdate
RMAHideExternalFieldsFromSearchInfo
RmaNotifyDispReviewerAndCatAuthor
RmaNotifyReviewerAndAlternateReviewer
ShowContentForStorageBrowse
ShowEmailMetadataMenu
IsSimpleProfilesEnabled
UieHideSearchCheckboxes

2.22 Schema

Schema are republished whenever a change occurs that may affect the relationship between the parts of the schema. These settings relate to publishing factors.

The following variables are related to schema:

EnableSchemaPublish
SchemaAllowRecursiveFileMove
SchemaBuildDigestFile
SchemaPublishCheckInterval
SchemaPublishInterval
SchemaPublishMaximumInterval
SchemaPublishMinimumInterval
SchemaPublishRenameRetryInitialInterval
SchemaPublishRenameRetryIterations
SchemaPublishRetryInterval
SchemaPublishRetryIntervalMax
SchemaVerifyPublishing
SchemaWin32RenameDelayInterval

2.23 Searching

The following variables are related to searching:

AllowForceDelete
CachedResultRowCount
DoMetaInternetSearch
EnableDocumentHighlight
HasSiteStudio
IsAutoSearch
MaxResults
MaxSavedSearchResults
MaxSearchConnections
noInfoColumn
noRevisionsColumn
NoSearchConnectionCloseOnDocChange
ResultsTitle
SearchCacheCleanerInterval
SearchCacheMaxItemAgeInMinutes
SearchDebugLevel
SearchDir
SearchIndexerEngineName
SearchQueryFormat
SearchQueryTrace
showDocActions
UniversalSearchAllowFullText
UseSearchCache

2.24 Security

This section lists variables that are related to security:

- Section 2.24.1, "Internal Security"

- Section 2.24.2, "External Security"

2.24.1 Internal Security

The following variables are related to internal security:

AllowAllRedirectUrls
AuthorDelete
DefaultAccounts
ExclusiveCheckout
GetCopyAccess
HtmlDataInputFilterLevel
SelfRegisteredAccounts
SelfRegisteredRoles
ShowOnlyKnownAccounts
UseAccounts
UserFilteredSubjects

2.24.2 External Security

The following variables are related to external security (web server and NTLM security):

ClearMissingAttributes
DomainControllerName
HasExternalUsers
IntradocRealm
IsPrimaryUserBase
LdapAdminDN
LdapAdminPassword
LdapPort
LdapServer
LdapSuffix
NtlmSecurityEnabled
Priority
ProviderClass
ProviderConfig
ProviderConnection
ProviderCredentialsMap
ProviderType
RedirectHostsFilter
SocketHostAddressSecurityFilter
SocketHostNameSecurityFilter
SourcePath
UseAdsi
UseNestedGroups
UseNetscape
UseNtlm
UseSecureLdap
UseSSL
WebServerAuthOnly

2.25 Strings

The following variable is related to strings:

StrConfineOverflowChars

2.26 Users

The following variables are related to users:

DefaultAccounts
ExclusiveCheckout
SysAdminAddress
UserCacheClusterSupport
UserCacheMaxSizeMatchInitialSize
UserCacheMaxSize
UserCacheTimeout

2.27 Web Server

The following variables are related to web servers:

DomainControllerName
HttpAbsoluteWebRoot
HttpBrowserHttpHostDoesNotHavePort
HttpIgnoreWebServerInternalPortNumber
HttpRelativeWebRoot
HttpServerAddress
IdcAuthExtraRequestParams
IdcHttpHeaderVariables
IntradocRealm
PLUGIN_DEBUG
RedirectHostsFilter
SocketHostAddressSecurityFilter
SocketHostNameSecurityFilter
UseSSL
WebServerAuthOnly

2.28 Workflow

The following variables are related to workflows:

DisableESigSSLCheck
EmailNotificationType
IsSavedWfCompanionFile
isRepromptLogin
PrimaryWorkQueueTimeout
UseDatabaseWfInQueue
WorkflowDir
WorkflowIntervalHours

3 Configuration Variables

This chapter lists Oracle WebCenter Content configuration variables in alphabetical order, and provides details about each variable.

AccessListPrivilegesGrantedWhenEmpty

This configuration variable changes the default behavior of core collaboration, where an empty access control list allows access to everyone, to instead deny access. When all access control lists are blank, permission is denied to all users except those with the admin role.

When this flag is set to FALSE, users could lose access to or be unable to checkin documents to Content Server unless they specify the appropriate access control list. For example, if a user who has a testrole role wants to checkin and access a document when AccessListPrivilegesGrantedWhenEmpty=false is set, the user must specify testrole with Read/Write (RW) privileges in the Role Entity access control list.

Usage

- Section 2.7, "Content Server"

Parameters

There are no parameters, just the setting of 0 (FALSE) to deny access to everyone.

Example

This example denies access to everyone (except users with the admin role) when the access control list is empty:

AccessListPrivilegesGrantedWhenEmpty=0

AccesslistPrivilegesGrantedWhenEmpty

Specifies that empty Access Control Lists (ACLs) in Content Server behave the same as empty lists in Oracle WebCenter Content: Records.

- When set to FALSE, empty ACLs in Records behave as if no ACL is defined.

- When set to TRUE, if no ACL is defined in standard WebCenter Content then only users with Admin permission are able to access content.

The default is FALSE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

AccesslistPrivilegesGrantedWhenEmpty=false

AdditionalIndexBuildParams

Adds build parameters to every indexer execution.

- This can be used to force optimization to occur after every indexing bulkload instead of every few bulkloads. For example, when a collection is not fully merged, the collection can be spread over many files, making searching inefficient and consuming many file handles.

- Default is an empty string.

Usage

- Section 2.16, "Indexing"

Parameters

- Each build parameter is prefixed with a hyphen. For example, -repair.

- If a build parameter has its own sub-parameters, the first sub-parameter does not have a hyphen. For example, -optimize maxmerge.

- If a build parameter has multiple sub-parameters, each sub-parameter after the first one is prefixed with a hyphen. For example, -optimize maxmerge -squeeze.

Parameter

Description

-repair

Repairs the collection.

-servlev

Overrides the service level to allow collection functions to be enabled, using one or more of the following parameters:
search: Enables search and retrieval.

optimize: Enables collection optimization.

assist: Enables building of the word list.

housekeep: Enables housekeeping of unneeded files.

insert: Enables adding and updating documents.

delete: Enables document deletion.

backup: Enables backup.

purge: Enables background purging.

repair: Enables collection repair.

index: Same as insert -delete.

dataprep: Same as search -optimize -assist -housekeep -index.

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

AdditionalIndexBuildParams=-repair

AdditionalIndexBuildParams=-optimize maxclean

AdditionalIndexBuildParams=-optimize maxmerge -squeeze

AdditionalSubscriptionCollatedFieldList

Defines a list of additional fields displayed for subscriptions.

The default fields are defined in SubscriptionCollatedFieldList.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

AdditionalSubscriptionCollatedFieldList=dOriginalName

See Also

- SubscriptionCollatedFieldList

AllowAllRedirectUrls

Resets functionality defined by RedirectHostsFilter and causes Content Server to act as it did before that variable was set. Setting this variable to TRUE allows the user to be redirected to any URL instead of those specified by RedirectHostsFilter.

Usage

- Section 2.24.1, "Internal Security"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

AllowAllRedirectUrls=true

See Also

- RedirectHostsFilter

AllowAlternateMetaFile

Allows users to submit metadata-only content as the alternate file.

- Enables the metadata-only file creation capability. In this scenario, the contributor does not specify an alternate file. Instead, the system will create the alternate file using a template and the content item's metadata.

- If set to TRUE in the config.cfg file, an extra check box is added to the checkin page. When this check box is selected, the createAlternateMetaFile setting is enabled, which directs the system to actually create the alternate file.

- Default is FALSE.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

AllowAlternateMetaFile=true

See Also

- createAlternateMetaFile

- AllowPrimaryMetaFile

AllowConcurrentUpdate

Used to allow new documents to be added to the existing collection during a rebuild of the index.

This is not supported for a rebuild into a new index type (for example, DATABASE.FULLTEXT) when the existing or old index type is different (for example, OracleTextSearch).

Usage

- Section 2.16, "Indexing"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

AllowConcurrentUpdate=TRUE

AllowForceDelete

Used to delete content items that are referenced or used by other content items.

The default setting is AllowForceDelete=FALSE. This configures the Content Server instance to refuse a request to delete a content item that is referenced as a link.

If set to AllowForceDelete=true, allows Content Server to delete a content item that is referenced as a link. Deleting a content item that is referenced by other content items invalidates the links. If the value is not set to true, a request to delete a referenced content item will fail.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

AllowForceDelete=TRUE

See Also

- For details about Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

AllowMatchesInDateCheck

When set to TRUE, the date validation code is changed so that dates that match a prior revision date are valid.

- Setting this variable allows an archive import and batch load process to import revisions of a content item that have matching creation dates or release dates.

- Standard date validation in the archiver normally disallows an import of a revision that matches or is within a minute of the prior revision of a document.

Usage

- Section 2.1, "Archiver"

Location

IntradocDir/config/config.cfg

Example

AllowMatchesInDateCheck=TRUE

AllowPrimaryMetaFile

Allows users to submit metadata-only content as the primary file.

- Enables the metadata-only file creation capability. In this scenario, the contributor does not specify a primary file. Instead, the system will create the primary file using a template and the content item's metadata.

- If set to TRUE in the config.cfg file, an extra check box is added to the checkin page. When this check box is selected, the createPrimaryMetaFile setting is enabled, which directs the system to actually create the primary file.

- Default is FALSE.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

AllowPrimaryMetaFile=true

See Also

- AllowAlternateMetaFile

- createPrimaryMetaFile

AllowRetentionPeriodWithoutCutoff

Specifies retention periods for triggers for non-record content items.

- If set to TRUE, retention periods for triggers for non-record content items are enabled.

- If set to FALSE, retention periods are disabled.

The default is TRUE.

Restart WebCenter Content for this variable to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

AllowRetentionPeriodWithoutCutoff=false

AllowSamePrimaryAlternateExtensions

Allows the primary file and alternate file to have the same file extension.

- When set to TRUE, the primary file and alternate file can have the same file extension.

- When set to FALSE, the primary file and alternate file cannot have the same file extension.

- Default is FALSE.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

AllowSamePrimaryAlternateExtensions=true

AllowSecondaryConversion

Defines if Inbound Refinery will use a backup conversion step if the native conversion step fails.

- When set to TRUE, the backup conversion step will be used upon conversion failure.

- When set to FALSE, no backup conversion step will be used upon conversion failure.

The Default is TRUE.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

- Local Inbound Refinery Configuration screen, General tab, Allow secondary conversion step

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

AllowSecondaryConversion=false

See Also

- SecondaryConversionStepName

AllowSkippedHyperlinktoCauseIncomplete

Marks the conversion as incomplete when a link cannot be converted to PDF.

- When set to TRUE, the conversion is marked as incomplete when a link cannot be converted.

- When set to FALSE, hyperlinks that cannot be converted are skipped, and the conversion is marked as converted.

The default is TRUE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

As a configuration entry:

AllowSkippedHyperlinktoCauseIncomplete=false

AppendToAllowedUploadServices

Add additional services to the custom or standard file upload services list.

Usage

- Section 2.7, "Content Server"

- Section 2.3, "Clients"

Location

IntradocDir/config/config.cfg

Example

As a configuration entry:

AppendToAllowedUploadServices=<ServiceName1>,<ServiceName2>,<ServiceName3>

See Also

- ForcePermissionCheckforAllowedUploadServices

AppletChunkSize

Sets the size of the transfer chunks for the chunking function, in bytes.

- Files that exceed the AppletChunkThreshold size will be transferred in chunks of this size.

- Default is 1 MB.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

AppletChunkSize=10000

See Also

- AppletChunkThreshold

- ChunkedRequestTrace

- DisableHttpUploadChunking

AppletChunkThreshold

Sets the minimum file size for the chunking function, in bytes.

- The chunking function will not be used for files smaller than this size.

- Default is 1 MB.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

AppletChunkThreshold=500000

See Also

- AppletChunkThreshold

- ChunkedRequestTrace

- DisableHttpUploadChunking

ArchiverDoLocks

Activates a locking algorithm on archive files at the file system level.

- If you do automated imports or transfers with multiple Content Server instances sharing an instance, set this variable to TRUE.

- If only one instance is doing automated imports or transfers in a load balancing configuration, then this variable does not need to be set.

- There is no default setting.

Usage

- Section 2.1, "Archiver"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

ArchiverDoLocks=true

See Also

- ArchiverTouchMonitorInterval

- ArchiverTraceLockMaintenance

- ArchiverTraceLocks

ArchiverTouchMonitorInterval

Defines the time that a contending Content Server instance will wait before it will treat an archive lock file whose timestamp has not changed as having expired. The Content Server instance will also touch any locks it is maintaining twice during this interval.

- An archive lock is created by placing a lock file into an appropriate directory. In order for the lock to persist, the timestamp on the file must change periodically; otherwise any contending Content Server instance will treat the lock as an expired lock.

- The smaller the value of this setting, the quicker that locks can alternate between Content Server instances. The larger the value, the more likely that high activity (which could keep a touch request delayed for many seconds) on the network drive will cause a Content Server instance to falsely report a lock as having expired. If a lock is falsely expired, it can cause duplicated effort (although it should not have any long term impact on the state of the Content Server instance).

- The default is 12000 milliseconds (12 seconds).

Usage

- Section 2.1, "Archiver"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

ArchiverTouchMonitorInterval=15000

See Also

- ArchiverDoLocks

- ArchiverTraceLockMaintenance

- ArchiverTraceLocks

ArchiverTraceLockMaintenance

Dumps trace information to the console for timestamp maintenance on any outstanding archive locks and the discovery of timestamp changes on locks maintained by other servers.

- An archive lock is created by placing a lock file into an appropriate directory. In order for the lock to persist, the timestamp on the file must change periodically; otherwise any contending Content Server instance will treat the lock as an expired lock.

- There is no default setting.

Note:
This variable is obsolete as of the Content Server 7.0 release. The functionality is now available in the System Audit Information page.

Usage

- Section 2.1, "Archiver"

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

ArchiverTraceLockMaintenance=true

See Also

- ArchiverDoLocks

- ArchiverTouchMonitorInterval

- ArchiverTraceLocks

ArchiverTraceLocks

Dumps trace information to the console when locks on an archive are acquired and released.

There is no default setting.

Note:
This variable is obsolete as of the Content Server 7.0 release. The functionality is now available in the System Audit Information page.

Usage

- Section 2.1, "Archiver"

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

ArchiverTraceLocks=true

See Also

- ArchiverDoLocks

- ArchiverTouchMonitorInterval

- ArchiverTraceLockMaintenance

AuthorDelete

Enables authors of content items to delete their own revisions without having Delete privilege to the security group.

- When set to TRUE, and Content Server is configured to use Folders (enabled by the FrameworkFolders component), authors can delete their own revisions as long as they have Read privilege, otherwise they would need Delete privilege to the content items' security group.

- When set to TRUE, and Content Server is configured to use Contribution Folders (enabled by the Folders_g component), authors can delete their own revisions without Delete privilege to the content items' security group.

- Default is an empty string.

Usage

- Section 2.24.1, "Internal Security"

Location

- System Properties, Content Security tab, Allow author to delete revision

- Administration, Admin Server, Content Security menu option, Allow author to delete revision

- IntradocDir/config/config.cfg

Example

As a configuration entry:

AuthorDelete=true

As Idoc Script:

<$if AuthorDelete$>
<$AuthorDelete$>
<$else$>
false
<$endif$>

AutoNumberPrefix

Defines the prefix that will be added to all automatically numbered Content IDs.

- Returns the automatic numbering prefix (returns value in configuration settings).

- Returns a string.

Usage

- Section 2.5, "Content Items"

Location

- System Properties, Options tab, Auto Name Prefix

- Administration, Admin Server, General Configuration menu option, Auto Number Prefix

- IntradocDir/config/config.cfg

Example

As a configuration setting, defines the automatic numbering prefix:

AutoNumberPrefix=HR

As Idoc Script, returns the value of the configuration setting:

<$AutoNumberPrefix$>

See Also

- IsAutoNumber

AutoNumberWidth

Allows you to use more than six digits for a Content ID number, providing support for up to one hundred million content items (eight digits).

Usage

- Section 2.5, "Content Items"

Location

- IntradocDir/config/config.cfg

Example

As a configuration setting:

AutoNumberWidth=8

BatchLoaderPath

Defines the path to the default batch load text file.

Returns the file path as a string.

Usage

- Section 2.2, "Batch Loader"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

- As a Windows configuration entry:

BatchLoaderPath=c:/domain/BatchLoader/batchfile.txt

- As a Solaris/UNIX configuration entry:

BatchLoaderPath=/u1/intradoc3/batLd/batchfile

- As Idoc Script, returns the file path as a string:

<$BatchLoaderPath$>

BatchLoaderUserName

Defines the authorized user name for the Batch Loader utility. The user name must belong to the admin role.

- Default is sysadmin.

- Returns the Batch Loader user name as a string.

Usage

- Section 2.2, "Batch Loader"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

BatchLoaderUserName=sysadmin

BinDir

Defines the path to the Content Server launch executable files, such as IdcServer.exe.

Usage

- Section 2.12, "Directories and Paths"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

BinDir=c:/domain/bin/

CachedResultRowCount

Sets the size of the search cache.

- The search cache can improve search performance by caching recent search engine queries. Increasing the size reduces search time, but increases memory usage.

- Default is 40,000 rows.

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

CachedResultRowCount=30000

ChunkedRequestTrace

Outputs chunked file transfer requests on the View Server Output page for Content Server.

- When set to TRUE, chunking requests are output to the View Server Output page.

- When set to FALSE, chunking requests are not output.

- For this setting to output data, the Chunking function must be enabled using DisableHttpUploadChunking.

- Default is FALSE.

Usage

- Section 2.7, "Content Server"

- Section 2.11, "Debugging"

Location

- Administration, System Audit Information, View Server Output

- IntradocDir/config/config.cfg

Example

As a configuration setting:

ChunkedRequestTrace=true

See Also

- AppletChunkSize

- AppletChunkThreshold

- DisableHttpUploadChunking

CleanUp

Determines whether files should be deleted from the file system as they are being batch loaded.

- When set to TRUE, deletes each batch loaded file from the hard drive after it is successfully checked in or updated.

- Default is FALSE.

Usage

- Section 2.2, "Batch Loader"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

CleanUp=true

ClearMissingAttributes

Clears custom fields mapped from an LDAP service to Oracle WebCenter Content through the JpsUser provider. This is useful when you have mapped custom fields and then removed values from one or more of those fields. Oracle WebCenter Content ignores the missing attributes and continues to use the previous values unless you enable this variable and set it to true.

The default is FALSE.

Usage

- Section 2.24.2, "External Security"

- Section 2.7, "Content Server"

Location

- IntradocDir/data/providers/jpsuserprovider/provider.hda

Example

Used as a configuration entry. Add the line before the @end line in the file. The last lines of the file should look similar to:

SourcePath=jpsuser
ProviderClass=idc.provider.jps.JpsUserProvider
ClearMissingAttributes=true
@end

coaoShowLinkExtensions

Limits the display of the Check Out and Open component Edit action menu to the file extension values listed in the specified pattern. If the file extension matches the pattern then the action menu is displayed.

The default value is *doc*|*xls*|*ppt*|*vsd*. This means that, by default, the Check Out and Open action is available for Microsoft Word, Excel, PowerPoint, and Visio files.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/components/CheckoutAndOpenInNative/checkoutandopennnnsative_environment.cfg

Example

Used as a configuration entry:

coaoShowLinkExtensions=*doc*|*xls*|*ppt*|*vsd*

CollectionDeleteEnabled

Specifies if the Delete icon is displayed so users can delete Contribution Folders and content items.

- When set to TRUE, displays the Delete icon so users can delete Contribution Folders and content items from the Exploring page.

- When set to FALSE, hides the Delete icon.

- The default value is TRUE if the variable is not set explicitly by the user.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

Used as a configuration entry:

CollectionDeleteEnabled=true

CollectionHiddenMeta

Enables users to specify if a folder or content item is hidden or visible.

- This setting adds Hide/Unhide icons to the Exploring page.

- This setting adds a Show hidden when browsing check box to the Folder Configuration page.

- This is set automatically by the Contribution Folders installer program according to options specified at install time.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/data/components/Folders_g/install.cfg

See Also

This feature can be enabled manually. For details, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

CollectionInfoEnabled

Specifies if the Folder Information and Content Information options on an Actions menu are displayed or hidden.

- When set to TRUE, displays the Folder Information and Content Information options on an Actions menu so users can choose to view folder and content item information.

- When set to FALSE, hides the Folder Information and Content Information options on an Actions menu.

- The default value is TRUE if the variable is not set explicitly by the user.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

Used as a configuration entry:

CollectionInfoEnabled=false

CollectionInhibitUpdateMeta

Defines an inhibit field for the metadata propagation function. This variable enables contributors to copy metadata values from a Contribution Folder to its subfolders and content items.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

See Also

This feature can be enabled manually. For details, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

CollectionLinkEnabled

Specifies if the Create Shortcut option on an Actions menu is displayed or hidden.

- When set to TRUE, displays the Create Shortcut option on an Actions menu so users can choose to create a shortcut to the Contribution Folder.

- When set to FALSE, hides the Create Shortcut option on an Actions menu.

- The default value is TRUE if the variable is not set explicitly by the user.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

Used as a configuration entry:

CollectionLinkEnabled=false

CollectionLocation

Defines where the Archive collection is located. If you change the Archive directory to a different location from the default, you must specify the new location.

Default is DomainHome/ucm/cs/archives/

Usage

- Section 2.1, "Archiver"

- Section 2.12, "Directories and Paths"

Location

- IntradocDir/config/config.cfg

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

Example

Used as a configuration entry:

CollectionLocation=c:/domain/new/archives/

CollectionMeta

Specifies the metadata field that is used to store the unique Collection ID for each Contribution Folder.

- If this setting is not specified in the configuration file, the default value is xCollectionID.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

See Also

This feature can be enabled manually. For details, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

CollectionMoveEnabled

Specifies if the Move icon is displayed on the Exploring pages.

- When set to TRUE, displays the Move icon so users can move Contribution Folders and content items to other Contribution Folders.

- When set to FALSE, hides the Move icon.

- The default value is TRUE if the variable is not set explicitly by the user.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

Used as a configuration entry:

CollectionMoveEnabled=true

CollectionReadOnlyMarkedFolders

Specifies if system-level Contribution Folders (such as contribution server folders and Trash) can be modified (that is, set to Read Only status).

- When set to TRUE, prevents modification of system-level Contribution Folders.

- When set to FALSE, enables modifications.

- This variable is set to TRUE by default.

- If this variable is set to FALSE, you should assign an appropriate security group to the system-level Contribution Folders so only authorized personnel can change them. System-level Contribution Folders should be changed only if there is a particular reason to do so.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

Used as a configuration entry:

CollectionReadOnlyMarkedFolders=true

CollectionReadOnlyMeta

Enables users to specify if a Contribution Folder and its contents are read-only.

- Read-only is subject to the rules of the operating environment where the instance is run.

- This adds Read-only/Editable icons to the Exploring pages.

- This setting applies only to the current Contribution Folder level. A subfolder does not inherit the status from the parent.

- This variable is set automatically by the Folders installation program according to options specified at install time.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/data/components/Folders_g/install.cfg

See Also

This feature can be enabled manually. For details, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

CollectionReleasedOnly

Specifies if a revised document is visible to the author and users with Read permission to the content item.

- If set to FALSE, then allows the author and all users with Read permission to the content item to see the latest version. Content item visibility is based on the item version, not the release state.
The author and users with Read access can view revised items before and after they are converted, indexed, and released. Even if the revised content item fails conversion or indexing, it is still visible to the author and users with Read access. If the release date of the new revision is set to a future date, the revised content item is also visible to the author and all other users with Read access.

- If set to TRUE, and if the item has not released, and the user accessing the item is not the author, then no part of the content item will be visible. Content item visibility is based on the release state, not the item version.
When a new revision of a content item is checked into a Contribution Folder, the new revision is only visible to the author. It does not become visible to other users with Read access to that content item until it is converted, indexed, and released. Therefore, until the content item is released, nothing is displayed for non-authoring users. If the release date of the new revision is set to a future date, the revised content item is not visible to other users until that point in time.

- This variable is set to FALSE by default.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

Used as a configuration entry:

CollectionReleasedOnly=false

CollectionSecurityReadOnly

Specifies if users can see content items for which they have only Read permission.

- When set to TRUE, allows users to see content items for which they have only Read permissions.

- When set to FALSE, requires that users have at least Write permission to see a content item.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

Used as a configuration entry:

CollectionSecurityReadOnly=false

CollectionTrashDeleteDate

Defines a date metadata field for the Trash function.

- When set, this defines a date metadata field for the Trash function, which enables the deletion date and time to be recorded as metadata for items moved to the Trash folder.

- This variable is set automatically by the Folders installation program if the Trash Bin function is enabled at install time.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

See Also

This feature can be enabled manually. For details, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

CollectionTrashDeleteLocation

Defines an integer metadata field designating the parent Contribution Folder for the Trash function.

- When set, this enables the original parent Contribution Folder to be recorded as metadata for items moved to the Trash folder.

- If set, users can restore deleted items from the Trash folder.

- If set, the deletion date and time are displayed in the Trash folder.

- This variable is set automatically by the Folders installation program if the Trash Bin function is enabled at install time.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

See Also

This feature can be enabled manually. For details, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

CollectionTrashDeleteOldName

Defines a metadata field for the Trash function to track file names of deletions.

- When set, files that are renamed due to a naming conflict in the Trash folder can be restored with their original file names.

- This defines a file name metadata field for the Trash function. This enables the original file name to be recorded as metadata for items that are moved to the Trash folder.

- This variable is set automatically by the Folders installation program if the Trash Bin function is enabled at install time.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

See Also

This feature can be enabled manually. For details, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

CollectionTrashDeleter

Defines a metadata field for the Trash function to track user deletions.

- When set, this defines a metadata field for the Trash function which records the user's login information as metadata for items that are moved to the Trash folder.

- If set, users can choose to view only the items they have moved to the Trash folder or view all items that everyone has moved to the Trash folder.

- This variable is set automatically by the Folders installation program if the Trash Bin function is enabled at install time.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

See Also

This feature can be enabled manually. For details, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

CollectionWebDAVServer

Enables switching views in Windows Explorer.

- If set to a WebDAV URL, this enables users to switch the view from a Content Server page to a WebDAV Contribution Folder in Windows Explorer.

- WebDAV functionality on the Content Server instance must be installed before you can use this function.

- In Microsoft Internet Explorer 5.0 or later, this adds a web Contribution Folder icon to the virtual Exploring Contribution Folder (this icon is not displayed in any other browser).

- This variable is set automatically by the Folders installation program if the WebDAV function is enabled at install time.

- If the WebDAV function is enabled by setting the environment variable, instead of being set by the Folders installation program, then the setting must be to the WebDAV root of your Content Server instance.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

CollectionWebDAVServer=http://domain/_dav/cs/idcplg/webdav

ColumnMapFile

Specifies the column mapping HTM resource file.

- The system uses the column mapping file to map database column names to all uppercase, which is required for Oracle.

- If no path is referenced, the default path is IntradocDir/shared/config/resources/.

- The standard column mapping file provided with Content Server is upper_clmns_map.htm.

- There is no default value.

Usage

- Section 2.9, "Database"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ColumnMapFile=upper_clmns_map.htm

ConfigDir

Defines the path to the config/ directory.

Default is IntradocDir/config/.

Usage

- Section 2.9, "Database"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

As a configuration setting:

ConfigDir=c:/domain/config/

ConversionCacheExpirationPeriodInDays

Defines the minimum number of days that Dynamic Converter content will remain cached.

- Content converted by Dynamic Converter will not be deleted from the cache before it is this many days old (based on last access date). Content may stay in the cache longer, depending on when the next cleanup scan is run. See DatedCacheIntervalDays.

- This setting applies only to files that are no longer in the Content Server or were not generated by a forced or up front conversion. For information on cache cleanup rules, see MaxConversionCacheSizeInMegs.

- Default is 7.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ConversionCacheExpirationPeriodInDays=14

See Also

- DatedCacheIntervalDays

- MaxConversionCacheSizeInMegs

CookieAuthTimeoutInDays

Used with the ExtranetLook component. This variable is used with the CookieLoginPlugin, which monitors web requests and determines if a request is authenticated. It can support authentication based on browser cookies.

- When CookieAuthTimeoutInDays is set to a positive numeric value, the cookie will not time out for that number of days. The user needs a logout option that clears the cookie.

- If set to zero (0) or less, the cookie lasts as long as the browser session.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

CookieAuthTimeoutInDays=2

See Also

- CookieProxyPassword

- IsWebServerPagesOnly

CookieProxyPassword

Used with the ExtranetLook component. This variable is used to encrypt the passwords when users log in to the web site using cookie authentication. It is used with the CookieLoginPlugin, which monitors web requests and determines if a request is authenticated. It can support authentication based on browser cookies. This can be set to any desired value.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

CookieProxyPassword=x2x

See Also

- CookieAuthTimeoutInDays

- IsWebServerPagesOnly

createAlternateMetaFile

Allows users to submit metadata-only content for the alternate file.

- Directs the system to create a metadata-only alternate file. In this scenario, the contributor does not specify an alternate file. Instead, the system will create the alternate file using a template and the content item's metadata.

- When AllowAlternateMetaFile is set to TRUE, an extra check box is added to the checkin page. When this check box is selected, the createAlternateMetaFile variable is enabled.

- For use in the Batch Loader, createAlternateMetaFile must be set to TRUE in the batch load file.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

createAlternateMetaFile=true

See Also

- AllowAlternateMetaFile

- createPrimaryMetaFile

createPrimaryMetaFile

Allows users to submit metadata-only content for the primary file.

- Directs the system to create a metadata-only primary file. In this scenario, the contributor does not specify a primary file. Instead, the system will create the primary file using a template and the content item's metadata.

- When AllowPrimaryMetaFile is set to TRUE, an extra check box is added to the checkin page. When this check box is selected, the createPrimaryMetaFile variable is enabled.

- For use in the Batch Loader, createPrimaryMetaFile must be set to TRUE in the batch load file.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

createPrimaryMetaFile=true

See Also

- AllowPrimaryMetaFile

- createPrimaryMetaFile

DatabasePreserveCase

Defines whether the character case from the database is preserved.

- When set to TRUE, character case is preserved.

- This setting must be TRUE for Oracle and any other database that is case sensitive.

- Default is TRUE.

Usage

- Section 2.9, "Database"

Location

- System Properties, Database tab, Enable database preserve case

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DatabasePreserveCase=false

DatabaseWildcards

Defines the wildcard characters that are used to represent multiple characters in database queries.

- For JDBC databases, the default is %.

- For Microsoft Access, the default is *.

Usage

- Section 2.9, "Database"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DatabaseWildcards=%

DatedCacheIntervalDays

Defines the number of days between scans for cached Dynamic Converter content to delete.

- Content Server scans at this interval to find and delete old cached content.

- Default is 7.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DatedCacheIntervalDays=30

See Also

- ConversionCacheExpirationPeriodInDays

- MaxConversionCacheSizeInMegs

DataDir

Defines the path to the data/ directory.

Default is IntradocDir/data/.

Usage

- Section 2.12, "Directories and Paths"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

DataDir=c:/domain/data/

DateOutputFormat

Sets the date output format for the Indexer.

There is no default value.

Usage

- Section 2.10, "Date and Time"

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DateOutputFormat=M/d/yyyy hh:mm:ss a

DCMaxFileSize

Defines the maximum size in bytes of files that Dynamic Converter will process.

- If a source file is larger than the specified value, the conversion will not occur.

- Default is 20000000 (20 megabytes).

- Used in Dynamic Converter version 5.0 and higher.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DCMaxFileSize=10000000

DCTimeOut

Sets the timeout value in minutes for the Dynamic Converter conversion process.

- Defines the number of minutes to wait for the dynamic conversion of a document into HTML.

- Default is 3 minutes.

- Used in Dynamic Converter version 5.0 and higher.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DCTimeOut=5

DCViewFormat

Defines which rendition of the source file will be converted by Dynamic Converter.

- native: the native file is converted. This is the default.

- webviewable: the web-viewable file is converted.

- alternate,:the alternate file is converted.

Used in Dynamic Converter version 5.0 and later.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DCViewFormat=webviewable

DebugStdConversion

Configuration setting that overrides the conversion/step definitions published by Content Server.

Usage

- Section 2.11, "Debugging"

Parameters

This variable takes one argument, the path to the new definitions.

Location

IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

DebugStdConversion=/temp/idcconversions

DefaultAccounts

Defines the default accounts for anonymous users.

- This must be a comma-delimited list of accounts.

- Permissions for each account must be specified in parentheses after the account name.

- The #none entry grants privileges to content items that have no account assigned. The #all entry grants privileges to all accounts.

- Default is #none(RWDA).

- Returns the list of accounts as a string.

Usage

- Section 2.24.1, "Internal Security"

- Section 2.26, "Users"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting, defines default account information:

DefaultAccounts=BOS(R),SEA(RW),MSP/Gen(RWD)

As Idoc Script, returns the account information as a string:

<$DefaultAccounts$>

See Also

- "External User Accounts" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

- SelfRegisteredAccounts

DefaultFilterInputFormat

Defines the default input character set for conversion filters, such as Dynamic Converter or the Text Indexer Filter component.

- Conversion products use the character encoding of the system to determine the encoding of the input to the conversion filter. This should be sufficient in most cases; however, there may be cases when you want to override this value.

- For a complete list of encoding values, see the lcIsoEncoding values in the std_encoding.htm file, which is located in the IdcHomeDir/resources/ directory.

- Default is Cp1252.

Usage

- Section 2.18, "Localization"

- Section 2.8.1, "Inbound Refinery"

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry for Japanese text:

DefaultFilterInputFormat=shift_jis

Used as a configuration entry for Korean text:

DefaultFilterInputFormat=euc-kr

See Also

- DefaultFilterOutputFormat

DefaultFilterOutputFormat

Defines the default output character set for conversion filters, such as Dynamic Converter or the Text Indexer Filter component.

- Conversion products use the character encoding of the system to determine the encoding of the output to the conversion filter. This should be sufficient in most cases; however, there might be cases when you want to override this value.

- For a complete list of encoding values, see the lcIsoEncoding values in the std_encoding.htm file, which is located in the IdcHomeDir/resources/ directory.

- Default is Cp1252.

Usage

- Section 2.18, "Localization"

- Section 2.8.1, "Inbound Refinery"

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry for Japanese text:

DefaultFilterOutputFormat=shift_jis

Used as a configuration entry for Korean text:

DefaultFilterOutputFormat=euc-kr

See Also

- DefaultFilterOutputFormat

DefaultGraphicTimeout

Defines the default thumbnail timeout.

- Returns the thumbnail timeout values.

- This variable must be followed by one of these flags.

Flag

Description

#factor

This value is multiplied by the file size to determine the amount of time allowed for thumbnail conversion. (The resulting time is limited by the #max and #min flags.) The default value is 3. Increase this value for busy or slow systems.

#max

Specifies the maximum time in seconds that Inbound Refinery waits for the thumbnail conversion process to complete. The default time is 60 seconds.

#min

Specifies the minimum time in seconds that Inbound Refinery waits for the thumbnail conversion process to complete. The default time is 5 seconds.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

- Shared Inbound Refinery Configuration screen, Timeout Values tab, Default Timeout for Graphics

- IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

DefaultGraphicTimeout#factor=3

DefaultHtmlConversion

Defines the default template for Dynamic Converter conversions.

- This value must be the Content ID of a checked-in template file to specify as the default.

- There is no default value.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DefaultHtmlConversion=PLAIN

DefaultHtmlRefreshTimeoutInSeconds

Defines the time, in seconds, that a Work In Progress page, My Checked-Out Content page, and My Workflow Assignments page refreshes.

In addition to this variable, htmlRefreshTimeout can be set in the URL or the service's databinder. This can be used to set a different refresh time for different pages. If that is needed, do not set DefaultHtmlRefreshTimeoutInSeconds in the config.cfg file, but instead set htmlRefreshTimeout in the URL or databinder.

htmlRefreshUrl can be set to the URL of the page to load after the page refreshes. The default is the current page. This variable can be set in the URL of the page or the databinder.

The default value for DefaultHtmlRefreshTimeoutInSeconds is 60.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DefaultHtmlRefreshTimeoutInSeconds=120

DefaultNativeTimeout

Defines the default native file timeout.

- Returns the native file timeout values.

- This variable must be followed by one of these flags.

Flag

Description

#factor

This value is multiplied by the file size to determine the amount of time allowed for native-to-PostScript conversion. (The resulting time is limited by the #max and #min flags.) The default value is 3. Increase this value for busy or slow systems.

#max

Specifies the maximum time in seconds that Inbound Refinery waits for the native-to-PostScript conversion process to complete. The default time is 10 seconds.

#min

Specifies the minimum time in seconds that Inbound Refinery waits for the native-to-PostScript conversion process to complete. The default time is 2 seconds.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

- Shared Inbound Refinery Configuration screen, Timeout Values tab, Default Native to Postscript Timeout

- IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

DefaultNativeTimeout#factor=3

DefaultPasswordEncoding

Defines the type of encoding to use for storing user passwords.

- Default is to use the Secure Hash Algorithm update 1 (SHA1).

- If you want to have open text passwords, the suggested value is OpenText.

- If any other nonempty value is assigned, no encoding is performed.

- Default value is SHA1-CB.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DefaultPasswordEncoding=OpenText

DefaultPostscriptTimeout

Defines the default PostScript timeout.

- Returns the default PostScript timeout values.

- This variable must be followed by one of these flags.

Flag

Description

#factor

This value is multiplied by the file size to determine the amount of time allowed for PostScript-to-PDF conversion. (The resulting time is limited by the #max and #min flags.) The default value is 4. Increase this value for busy or slow systems.

#max

Specifies the maximum time in seconds that Inbound Refinery waits for the PostScript-to-PDF conversion process to complete. The default time is 2 seconds.

#min

Specifies the minimum time in seconds that Inbound Refinery waits for the PostScript-to-PDF conversion process to complete (native or PostScript). The default time is 20 seconds.

Usage

- Section 2.8.2.1, "General Variables"

Location

- Shared Inbound Refinery Configuration screen, Timeout Values tab, Default Postscript to PDF Timeout

- IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

DefaultPostscriptTimeout#factor=4

DirectoryLockingLogPath

Enables logging and defines the path for the log file during temporary locking of directories.

- Any errors that occur during temporary locking of directories will be reported to this log file.

- If this setting has no value, logging is disabled.

- There is no default value.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DirectoryLockingLogPath=C:/temp/locking.log

DisableContentProfiles

Used to disable Content Profile functionality but does not remove profiles that have already been created. Profiles remain available through the user interface.

This configuration variable can be used to help determine whether specific behavior is caused by Content Profiles or by another component.

After debugging has been completed, remove this variable from the config.cfg file and restart the Content Server instance to use Content Profiles again.

Usage

- Section 2.6, "Content Profiles"

Location

IntradocDir/config/config.cfg

Example

DisableContentProfiles=true

DisableDBLongIntegerField

In older versions of MSDE software, 4-byte integers were allowed. In newer versions, 8-byte integers and larger are used. This variable allows Content Server to continue to use 4-byte integers.

If you upgrade Content Server version 6.2 with MSDE to a newer release, the upgraded instance does not start because of the addition of the dRevRank column. Content Server version 6.2 uses an older MSDE version than later versions. The system will start with the addition of this variable set to TRUE.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DisableDBLongIntegerField=true

DisableESigSSLCheck

Disables SSL requirement for Electronic Signature when it is used in workflows. Otherwise Electronic Signature used in workflows requires that SSL be implemented.

Usage

- Section 2.28, "Workflow"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DisableESigSSLCheck=true

DisableForcedConversions

Defines whether forced and up front conversions in Dynamic Converter are disabled.

- When set to TRUE, files will only be converted by Dynamic Converter when a user views the dynamically converted rendition. Conversions at checkin (forced and up front) will not occur.

- This variable applies to any new files checked in after the setting is set to TRUE. Any existing forced and up front conversions will still be used, unless the DisableKeepingForcedConversions setting is enabled.

- This variable might be useful in the following situations:

- Server space for caching or processing capacity for conversion is limited.

- Most files are rarely viewed as web pages, so a relatively small number of files must be converted dynamically.

- The delay time for on-the-fly conversions is acceptable.

- Default is FALSE.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DisableForcedConversions=true

See Also

- DisableKeepingForcedConversions

- ForcedConversionRules

DisableGzipCompression

Disables gzip compression of HTML pages and log files. Pages are compressed only if the client browser supports compressed HTML. Compression makes pages an average of 80% smaller and is supported by any HTTP 1.1 compatible browser.

- When set to TRUE, pages will not be compressed before being sent to a client web browser.

- Default is FALSE.

Usage

- Section 2.15, "HTML Preview"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DisableGzipCompression=true

See Also

- "HTTP_ACCEPT_ENCODING" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

DisableHttpUploadChunking

Disables the upload chunking function, which is used with the Upload Applet or an HTTP provider.

- When set to TRUE, the chunking function is disabled.

- When set to FALSE, the chunking function is enabled.

- Default is TRUE.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

DisableHttpUploadChunking=false

See Also

- AppletChunkSize

- AppletChunkThreshold

- ChunkedRequestTrace

DisableKeepingForcedConversions

Defines whether Dynamic Converter treats converted files as forced conversions for updating purposes.

- When set to TRUE, files that were converted by forced or up front conversion are not considered forced conversions by Dynamic Converter. This means that even if Dynamic Converter would normally use the existing conversion rather than reconverting the file, the existing conversion will not be recognized as a forced conversion and the file will be reconverted.

- Default is FALSE.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DisableKeepingForcedConversions=true

See Also

- DisableForcedConversions

DisableOptimizedLatestReleaseQuerying

Defines whether cached timestamps or Content Server database information is used by Dynamic Converter to determine which files must be reconverted.

- When set to TRUE, Dynamic Converter queries the Content Server database rather than the cached timestamps to determine which files must be reconverted.

- Enabling this setting reverts to pre-6.2 Dynamic Converter behavior. This setting can be used if you need to troubleshoot a related issue.

- Default is FALSE.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DisableOptimizedLatestReleaseQuerying=true

DisableSharedCacheChecking

Disables timestamp checking on all loaded resources.

- When set to TRUE, resource files defined in components will be refreshed only when the Content Server instance is restarted.

- This setting does not stop timestamp checking on HCST and HCSP pages.

- This setting can be used to limit file system activity, typically when the Content Server file system is on a network share. This setting is particularly important in production environments where file checking and timestamp overhead can seriously degrade performance. In a development environment this setting can be optional.

- See the clustering documentation for more information.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DisableSharedCacheChecking=true

DistillerPath

Sets the path to the executable used by PDF Converter to convert files to PDF.

- Returns the path as a string.

- If Adobe Acrobat Distiller is not detected during installation of PDF Converter, the default is the path to the Jaws PDF Library.

- If Adobe Acrobat Distiller is detected during installation of PDF Converter, the default is the path to the Distiller executable.

Usage

- Section 2.8.2.1, "General Variables"

Location

- Shared Inbound Refinery Configuration screen, Paths tab, Adobe Distiller Executable File Path

- IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

DistillerPath=C:/Program Files/IdcRefinery/shared/jaws_ps/ps2pdf.exe

DoDocNameOrder

Sorts content items in the Repository Manager by dDocName. When Repository Manager is started, a default query is run against the database. By default the query results are sorted by the dDocName of the items. Ordering by dDocName makes the order predictable but can result in longer query results.

- When set to TRUE, content items are sorted by dDocName.

- When set to FALSE, content items are not sorted.

- Default is TRUE.

You can enable the JDBC Query Trace to log information to the console log and verify that the 'order by' clause is no longer part of the query. To enable the JDBC Query Trace, select systemdatabase as an option in the Edit Active Console Output Tracing section of the System Audit Information page.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DoDocNameOrder=false

dodSkipCatFolderRequirement

Specifies that an item is allowed to be checked in without specifying a category or Contribution Folder for the checkin. If a DoD configuration is in use, this will cause non-conformance with DoD regulations.

- When set to TRUE, items must be checked in with a category or Contribution Folder specified.

- When set to FALSE, items may be checked in without specifying a category or Contribution Folder.

The default is TRUE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

dodSkipCatFolderRequirement=false

DomainControllerName

Defines the domain controller to use for NTLM calls.

- If a value is not set, an API call is made to find a domain controller to talk to.

- Default is an empty string.

Usage

- Section 2.24.2, "External Security"

- Section 2.27, "Web Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DomainControllerName=PDC servername

DoMetaInternetSearch

Enables Internet search syntax for metadata fields.

- When set to TRUE, Internet searching for metadata is enabled.

- When set to FALSE, Internet searching for metadata is disabled.

Default is FALSE.

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

DoMetaInternetSearch=true

DownloadApplet

Enables the multiple file Download Applet.

- When set to TRUE, the Download Applet is enabled so that multiple files can be downloaded from a search results page.

- When set to FALSE, the Download Applet is disabled.

- Default is FALSE.

Usage

- Section 2.7, "Content Server"

- Section 2.3, "Clients"

Location

- System Properties, Options tab, Enable download applet

- Administration, Admin Server, General Configuration menu option, Enable download applet

- IntradocDir/config/config.cfg

Example

As a configuration setting, enables the Download Applet:

DownloadApplet=true

As script, evaluates the condition of the Download Applet:

<$DownloadApplet$>

See Also

- MultiUpload

- UploadApplet

DtmPort

Defines the port number on which the DtmServer (required for HTML Preview) listens to connections from Content Publisher clients.

Default is 4441.

Usage

- Section 2.15, "HTML Preview"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DtmPort=4442

DynamicConverterHtmlFlavor

Defines the HTML flavor used by Dynamic Converter.

- Possible settings are:

- Internet Explorer 4.0

- Netscape 4.0

- HTML 3.0

- HTML 4.0

- Default is null.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

DynamicConverterHtmlFlavor=HTML 4.0

EmailNotificationType

Specifies where the links in notification emails point for workflows and subscriptions in different Content Server user interfaces.

Possible settings are:

- NativeWebUI (the native 11g user interface)

- ContentUI (the ADF-based user interface, which is newer than the native 11g interface)

- ContentUI,NativeWebUI (both the native 11g user interface and the ADF-based user interface)

This variable is not set automatically. When set, if no value is specified, it defaults to NativeWebUI.

Usage

- Section 2.5, "Content Items"

- Section 2.28, "Workflow"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

EmailNotificationType=ContentUI,NativeWebUI

EnableDocumentHighlight

Enables highlighting of full-text search terms in PDF, text, and HTML files.

- When set to TRUE, search term highlighting is enabled.

- When set to FALSE, search term highlighting is disabled.

- Default is FALSE after installation of Content Server.

- Default is TRUE after installation of PDF Converter.

Usage

- Section 2.23, "Searching"

Location

- System Properties, Options tab, Enable search keyword highlighting

- Administration, Admin Server, General Configuration menu option, Enable search keyword highlighting

- IntradocDir/config/config.cfg

Example

As a configuration setting:

EnableDocumentHighlight=false

As script, returns the value of the configuration setting:

<$EnableDocumentHighlight$>

See Also

- "UseHtmlOrTextHighlightInfo" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

EnableEnvironmentPackager

Enables the Environment Packager debugging function.

- This function enables an administrator to package all files in the admin, config, and bin directories into a ZIP archive, along with a text file called environment.txt. This text file contains additional information about the Java Virtual Machine, and the operating system of the server. The ZIP file, server_environment.zip, is placed in the root directory of the Content Server instance.

- When set to TRUE, the Environment Packager function is enabled.

- When set to FALSE, the Environment Packager function is disabled.

- Default is FALSE.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

EnableEnvironmentPackager=true

EnableErrorFile

Generates a Batch Loader error file.

- If errors are encountered during a batch load, an error file is generated with those problem records added.

- When set to TRUE, an error file is generated.

- There is no default value.

Usage

- Section 2.2, "Batch Loader"

- Section 2.11, "Debugging"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

EnableErrorFile=true

EnableExpirationNotifier

Enables notification of expiration (NOE) of content items. This provides email notification to authors and administrators for documents that will be expired in a short time.

- After enabling the NOE and restarting, an entry is included in the ScheduledEvents DomainHome/ucm/cs/config/activestate.hda file.

- The include that controls when the NOE runs is set_doevent_for_notification_of_expiration. The NotifyTime parameter described below is used in this include.

- Note that in the following parameters, NotificationQuery can be set to 30 (not 7, as is the default) and NotificationIntervalInDays can be set to 7; this provides weekly emails about what will expire within the month.

- The table that defines scheduled events is in the IdcHomeDir/resources/core/tables/std_resources.htm file. The table is named IdcScheduledSystemEvents and the row is named NotificationOfExpiration.

- To obtain debugging information for the NOE, set the following variables in the config.cfg file and restart the Content Server instance. Logging goes to the server output:

TraceSectionsList=system,scheduledevents
TraceIsVerbose=true

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Parameters

Takes the following optional parameters:

Parameter

Description

NotificationQuery

Specifies the query to be run to find the expired documents for the notification. The default is the following:

dOutDate > <$dateCurrent()$> <AND> dOutDate < <$dateCurrent(7)$>

NotificationMaximum

Specifies the maximum number of documents returned from the query. Default: 1000.

NotifyExtras

Denotes the administration users who receive the notification emails. If left blank, no extra notification is sent.

NotifyTime

The time of day to send the notification. Default: 00:01. Specified in 24-hour clock notation.

NotificationFieldNames

Specifies the field names to include in the notification. Default: dDocAuthor, dOutDate, dDocTitle, dDocName, dDocType, dID, dInDate, dRevLabel, dSecurityGroup

NOEUsePlainTextEmail

Allows the use of plain text email for the notification. Default: false. The email template is named QUERY_NOTIFICATION. If NOEUsePlainTextEmail=true, emailFormat=text.

NotificationIntervalInDays

Specifies the interval in days. Default: 1.

Example

Used as a configuration entry:

EnableExpirationNotifier=true

EnableRebuildForcesReconversion

Defines whether up front and forced Dynamic Converter conversions are reevaluated during a rebuild of the search index.

- When set to TRUE, content items being indexed during an index rebuild will be reevaluated for conversion by Dynamic Converter based on the conversion rules for forced and up front conversions.

- This setting can be used to dynamically convert files during an index rebuild after you have created a new conversion rule.

- Default is FALSE.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

EnableRebuildForcesReconversion=true

See Also

- ForcedConversionRules

EnableSchemaPublish

Enables or disables Schema Publisher.

- When set to TRUE, publishing is enabled.

- When set to FALSE, publishing is disabled.

- Default is TRUE.

Caution:
If set to FALSE, publishing is disabled even if the Republish Scheme option is used on the Configuration Manager Admin Applet. Setting this value to FALSE is normally used in clusters where Schema Publisher should be enabled only on selected nodes.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

EnableSchemaPublish=false

ExclusiveCheckout

Determines whether users can check out content that was authored by another user.

- When set to TRUE, only the author or a user with Admin permission to the security group can check out a content item.

- When set to FALSE, users with Write permission to the security group can check out content that was authored by another user.

- Default is FALSE.

Usage

- Section 2.24.1, "Internal Security"

- Section 2.26, "Users"

Location

- System Properties, Content Security tab, Allow only original contributor to check out

- Administration, Admin Server, Content Security menu option, Allow only original contributor to check out

- IntradocDir/config/config.cfg

Example

As a configuration setting, only original contributor can check out a content item.

ExclusiveCheckout=true

As Idoc Script, returns the value of the configuration setting:

<$ExclusiveCheckout$>

See Also

- "isUserOverrideSet" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

ExpireRevisionOnly

Determines if all revisions or only a specific revision of a content item is expired on the specified Expiration Date.

Note:
This variable applies to Content Server version 6.2 and later. Before version 6.2, only the specific revision expired on the specified Expiration Date. Starting with version 6.2, the default behavior is that if the current revision expires, all revisions of that content item also expire. Setting this variable to TRUE returns the system to the pre-6.2 behavior.

- When set to TRUE, only the current revision expires, and the most recent unexpired revision becomes the current revision.

- When set to FALSE, all revisions expire when the current revision expires.

- Default is FALSE.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ExpireRevisionOnly=true

FileEncoding

Specifies the file encoding to be used.

If Content Server is configured to use languages other than operating system's native language (for example, using both English and Japanese locales on an English system), this variable must be set to UTF8 in both the Content Server and the Inbound Refinery instances.

Usage

- Section 2.18, "Localization"

- Section 2.7, "Content Server"

- Section 2.8.1, "Inbound Refinery"

Location

- Content Server: DomainHome/ucm/cs/bin/intradoc.cfg

- Inbound Refinery: IntradocDir/data/configuration/connections/main/intradoc.cfg

Example

Used as a configuration entry:

FileEncoding=UTF8

FldEnforceCaseInsensitiveNameUniqueness

Makes name-uniqueness checks for folder and file names case-insensitive, and makes path resolution case-insensitive.

- Use this variable with the variable FldEnforceFolderFileNameUniqueness.

- Default setting is TRUE.

- If Oracle WebCenter Content is being upgraded and the existing folder structure does not meet the uniqueness constraints enforced by this variable and the variable FldEnforceFolderFileNameUniqueness, these two variables must be set to FALSE.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

FldEnforceCaseInsensitiveNameUniqueness=true

FldEnforceFolderFileNameUniqueness

Prevents folders from having a child folder with the same name as a child document. The same name mean it is case-insensitive. Child folder and child document refer to both owner links and soft links.

- Use this variable with the variable FldEnforceCaseInsensitiveNameUniqueness.

- Default setting is TRUE.

- If Oracle WebCenter Content is being upgraded and the existing folder structure does not meet the uniqueness constraints enforced by this variable and the variable FldEnforceCaseInsensitiveNameUniqueness, these two variables must be set to FALSE.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

FldEnforceFolderFileNameUniqueness=true

ForcedConversionRules

Defines the Dynamic Converter rules that will apply forced conversions upon file checkin.

- This is a comma-delimited list.

- If a content item matches any of the specified conversion rules upon checkin, the file will be converted according to that rule. Each file can be converted into multiple renditions.

- There is no default.

Note:
The forced conversion process does not apply the same Dynamic Converter template twice. For example, if you set ForcedConversionRules=RuleA,RuleB, but RuleA and RuleB specify the same template with a different layout, the conversion according to RuleB will not occur. (Best practice in this case would be to merge the layouts and use Idoc Script to dynamically select the appropriate layout elements.)

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ForcedConversionRules=Rule1,Rule2,Rule3

See Also

- DisableForcedConversions

- "incDynamicConversionByRule" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

- rule:IsFragmentOnly

ForceDistinctRevLabels

Defines whether additional revisions for the same content item can have the same revision label.

- Changing this setting will apply to new content only.

- When set to TRUE, two revisions of the same content cannot have the same revision label.

- Default setting is FALSE.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ForceDistinctRevLabels=true

ForceDocTypeChoice

Adds a blank option as the default for the Type option list on checkin pages. This requires the user to select a Type.

- Used on pages as a display option.

- When set to TRUE, the checkin page displays the Type option list with a blank option.

- Default setting is FALSE.

Usage

- Section 2.13, "Field Display"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ForceDocTypeChoice=true

ForceJdbcSync

Restricts access to the database to one query at a time.

This setting is typically used for debugging or for problematic JDBC drivers.

If the system is being used mostly for read-only type activity, setting this to FALSE will improve the throughput to the database.

When set to TRUE, one query at a time can access the database.

When set to FALSE, multiple queries can access the database at a time.

Default setting is FALSE. (Default for version 4.5 and earlier was TRUE.)

Usage

- Section 2.9, "Database"

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ForceJdbcSync=true

ForcePermissionCheckforAllowedUploadServices

Enforce user permission is validated during file upload services.

When set to TRUE, the user permission has to be validated during file upload.

When set to FALSE, the user permission is not validated during file upload.

Default is FALSE.

Usage

- Section 2.7, "Content Server"

- Section 2.3, "Clients"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ForcePermissionCheckforAllowedUploadServices=true

See Also

AppendToAllowedUploadServices

ForceSecurityGroupChoice

Adds a blank option as the default for the Security Group option list on checkin pages. This requires the user to select a Security Group.

Used on pages as a display option.

When set to TRUE, the checkin page displays the Security Group option list with a blank option.

Default setting is FALSE.

Usage

- Section 2.13, "Field Display"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ForceSecurityGroupChoice=true

FormInheritMetaDataFieldList

Defines the custom metadata fields that are inherited by subsequent revisions of a PDF form.

This is a comma-delimited list.

Standard metadata fields (such as Type, Security Group, and Account) are inherited by default.

Custom metadata fields begin with a lowercase x (for example, xComments).

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

FormInheritMetaDataFieldList=xDepartment,xRegion

FrameMakerCyclesAllowed

The maximum number of 30-second cycles that Inbound Refinery allows before FrameMaker is considered to be not responding.

Inbound Refinery watches the consfile.txt file for FrameMaker activity.

Default is 1.

Usage

- Section 2.8.2.4, "Other Formats"

Location

IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

FrameMakerCyclesAllowed=1

FrameMakerTimeout

Defines the FrameMaker conversion timeout.

Returns the FrameMaker timeout values.

This variable must be followed by one of these flags.

Flag

Description

#factor

This value is multiplied by the file size to determine the amount of time allowed for FrameMaker conversion. (The resulting time is limited by the #max and #min flags.) The default value is 1. Increase this value for busy or slow systems.

#max

Specifies the maximum time in seconds that Inbound Refinery waits for the FrameMaker conversion process to complete. The default time is 10 seconds.

#min

Specifies the minimum time in seconds that Inbound Refinery waits for the FrameMaker conversion process to complete. The default time is 1 second.

Usage

- Section 2.8.2.4, "Other Formats"

Location

- Shared Inbound Refinery Configuration screen, Timeout Values tab, FrameMaker to PostScript Timeout

- IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

FrameMakerTimeout#factor=2

GetCopyAccess

Determines what permission a user must have to get a copy of a content item.

When set to TRUE, users can get a copy of a content item for which they have only Read permission.

When set to FALSE, users must have Write permission to a content item to be able to get a copy.

Default is FALSE.

Usage

- Section 2.24.1, "Internal Security"

Location

- System Properties, Content Security tab, Allow get copy for user with read privilege

- Administration, Admin Server, Content Security menu option, Allow get copy for user with read privilege

- IntradocDir/config/config.cfg

Example

As a configuration setting:

GetCopyAccess=true

As Idoc Script, returns the value of the configuration setting:

<$GetCopyAccess$>

HasExternalUsers

Indicates to Content Server that an external user database is present.

When set to TRUE, the system recognizes external users. If a custom component has been written to support an external user integration (such as LDAP), this should be set to TRUE.

Default is FALSE.

Usage

- Section 2.7, "Content Server"

- Section 2.24.2, "External Security"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

HasExternalUsers=true

As Idoc Script, returns the value of the configuration setting:

<$HasExternalUsers$>

See Also

- NtlmSecurityEnabled

HasSiteStudio

Used with the Link Manager functionality.

If Site Studio is installed, this variable enables the Site Studio-specific link patterns for parsing friendly URLs for the pattern engine. If set to TRUE, this variable enables the Site Studio-specific link patterns.

The default value is FALSE, which disables the Site Studio-specific link patterns.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

HasSiteStudio=TRUE

See Also

- For details about Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

HideVitalReview

This variable hides the Subject to Review related fields on Oracle WebCenter Content: Records Search and Checkin pages.

- If set to TRUE, Subject to Review fields are hidden.

- If set to FALSE, Subject to Review fields are revealed.

The default is TRUE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

HideVitalReview=false

HighlightBegin

Sets the opening HTML tag of the text highlighting style for files converted by Dynamic Converter.

Default is <strong>.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

HighlightBegin=<b><font color=blue>

See Also

- HighlightEnd

HighlightEnd

Sets the closing HTML tag of the text highlighting style for files converted by Dynamic Converter.

Default is </strong>.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

HighlightEnd=</font></b>

See Also

- HighlightBegin

HtmlDataInputFilterLevel

A configuration entry used in conjunction with the encodeHtml function. This entry applies a level of encoding to filter all input to the system for bad HTML constructions.

All input data received by the system when using the unsafe value for the encodeHtml rule parameter applies only to well-known unsafe script tags. This functionality can be altered by using the HtmlDataInputFilterLevel configuration variable to change the filtering that is done.

Usage

- Section 2.24, "Security"

Parameters

This entry takes one parameter, the filter level. Accepted values are:

- none: No filtering is performed.

- unsafe: Protects against bad HTML constructions.

- exceptsafe: Allows only well-known safe constructions through the filter.

Location

IntradocDir/config/config.cfg

See Also

- "encodeHtml" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

- Oracle Fusion Middleware Administering Oracle WebCenter Content

HTMLEditorPath

Defines the path for the executable that is used to edit component files from within the Component Wizard.

This path is defined in the Component Wizard.

You should specify a text editor (such as WordPad) rather than a graphical HTML editor (such as FrontPage). Graphical editors can insert or change HTML tags and may cause Idoc Script tags to be converted into a string of characters that will not be recognized by Content Server.

There is no default value.

Usage

- Section 2.12, "Directories and Paths"

Location

- IntradocDir/config/config.cfg

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

Example

Used as a configuration entry:

HTMLEditorPath=C:/Program Files/Windows NT/Accessories/wordpad.exe

HttpAbsoluteCgiRoot

Defines the Content Server CGI path as a complete URL.

Usage

- Section 2.7, "Content Server"

- Section 2.12, "Directories and Paths"

Location

IntradocDir/config/config.cfg

Example

For a Content Server instance:

HttpAbsoluteCgiRoot=http://my_computer/idcplg/idc_cgi_isapi-instance.dll

See Also

- "HttpAbsoluteCgiPath" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

HttpAbsoluteWebRoot

Defines the web server root directory as a complete URL.

Usage

- Section 2.12, "Directories and Paths"

- Section 2.27, "Web Server"

Location

IntradocDir/config/config.cfg

Example

For a Content Server:

HttpAbsoluteWebRoot=http://my_computer/domain/

See Also

- HttpRelativeWebRoot

HttpBrowserHttpHostDoesNotHavePort

When set to TRUE, Content Server is notified that the HTTP address that it computed for the Content Server's administration server and applets does not have a port number and it needs to look for a port number. This setting is only necessary if you want to change the default behavior.

If HttpIgnoreWebServerInternalPortNumber is also set to TRUE, Content Server looks at the HttpServerAddress setting to determine the port number. Otherwise Content Server uses the server port number provided by the web server.

Usage

- Section 2.27, "Web Server"

Location

IntradocDir/config/config.cfg

Example

HttpBrowserHttpHostDoesNotHavePort=true

See Also

- HttpIgnoreWebServerInternalPortNumber

HttpIgnoreWebServerInternalPortNumber

When set to TRUE, causes the HTTP address computed for the Content Server's administration server and applets to not use the server port value provided by the web server.

This prevents a load balancing configuration problem in which the load balancing server is using a different port number than the internal web server actually delivering the response to the request.

Usage

- Section 2.27, "Web Server"

Location

IntradocDir/config/config.cfg

Example

HttpIgnoreWebServerInternalPortNumber=true

See Also

- "HttpBrowserFullCgiPath" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

HttpRelativeCgiRoot

Defines the Content Server CGI path as a relative URL.

Usage

- Section 2.12, "Directories and Paths"

Location

IntradocDir/config/config.cfg

Example

For a Content Server:

HttpRelativeCgiRoot=/idcplg/idc_cgi_isapi-instance.dll

See Also

- HttpAbsoluteCgiRoot

HttpRelativeWebRoot

Defines the web server root directory as a relative URL.

- A relative root such as /domain/ is used rather than a full root such as http://www.example.com/domain/.

- Returns the relative web root directory as a string.

- There is no default value.

Usage

- Section 2.12, "Directories and Paths"

- Section 2.27, "Web Server"

Location

- System Properties, Internet tab, Http Relative Web Root

- Content Server: IntradocDir/config/config.cfg

Example

As a configuration setting, defines the relative web root:

HttpRelativeWebRoot=/domain/

As Idoc Script, returns the relative web root as a string:

<$HttpRelativeWebRoot$>

See Also

- HttpAbsoluteWebRoot

HttpServerAddress

Defines the web server address as a partial URL.

A partial URL such as example is used rather than a full address such as http://www.example.com/.

Returns the web server address as a string.

There is no default value.

Usage

- Section 2.12, "Directories and Paths"

- Section 2.27, "Web Server"

Location

- System Properties, Internet tab, HTTP Server Address

- Content Server: IntradocDir/config/config.cfg

Example

As a configuration setting, defines the web server address:

HttpServerAddress=example

As Idoc Script, returns the web server address as a string:

<$HttpServerAddress$>

See Also

- IdcCommandServerHost

- IntradocServerHostName

IDC_Name

Defines the unique name of the Content Server instance.

Caution:
Using duplicate IDC_Name settings will cause data corruption. The Archiver utility cannot be used to move or copy data between two instances that share the same IDC_Name setting. To do so will corrupt the data on the target system. Give each of your instances a unique IDC_Name setting.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IDC_Name=OracleMSP

See Also

- InstanceDescription

- InstanceMenuLabel

IdcAnalyzeLogDir

Specifies the location where the Content Server Analyzer utility writes output files and transfers extra files detected during the file system analysis process.

You can specify a partial or complete directory path.

- If a partial directory path (such as analyzer_logs/) is specified, this subdirectory is created in the DomainHome/ucm/cs/bin/ directory.

- If a complete directory path (such as c:/analyzer_logs/) is specified, this is the log directory.

The log file name is specified by the LogName setting.

The default is DomainHome/ucm/cs/bin/logs/.

Usage

- Section 2.11, "Debugging"

- Section 2.12, "Directories and Paths"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

As a configuration setting:

IdcAnalyzeLogDir=f:/domain/analyzer_logs/

See Also

- LogName

- "SafeDir" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

- TempDir

IdcAuthExtraRequestParams

Specifies values for the web server plug-in to get from its local data and send in the header of its requests.

For example, if you have a plug-in to the web server filter getting some attributes for a user and placing them into a local value, you could specify the name of the attributes in IdcAuthExtraRequestParams, and the data would be passed to the Content Server instance.

This setting can also be used to access extra HTTP header values using Idoc Script. These variables will become part of the Data Binder environment variable set.

- The names in the IdcAuthExtraRequestParams list must match the header names without regard for case (case insensitive match).

- When used as Idoc Script variables, the names in the IdcAuthExtraRequestParams must match exactly (case sensitive match).

There is no default value.

For information about IdcCommand, see Oracle Fusion Middleware Developing with Oracle WebCenter Content.

Usage

- Section 2.27, "Web Server"

Location

IntradocDir/config/config.cfg

Example

The following setting tells the IIS web server plug-in to send the local value of HTTP_REFERER in the header (IIS automatically adds the HTTP_ prefix):

IdcAuthExtraRequestParams=referer

IdcCommandFile

Specifies a file containing commands to execute using IdcCommand.

There is no default setting.

For information about IdcCommand, see Oracle Fusion Middleware Developing with Oracle WebCenter Content.

Usage

- Section 2.7, "Content Server"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

IdcCommandFile=c:/ucm/idc/add_user.txt

IdcCommandLog

Specifies the path to the log file for IdcCommand execution.

The log file contains the time the command was executed and the success or failure status of the command.

There is no default setting.

For information about IdcCommand, see Oracle Fusion Middleware Developing with Oracle WebCenter Content.

Usage

- Section 2.7, "Content Server"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

IdcCommandLog=c:/idc/idccommand.log

IdcCommandServerHost

Specifies the web server address of the Content Server instance to which IdcCommand is connecting.

Default is the HttpServerAddress of the Content Server instance to which IdcCommand is connecting.

For information about IdcCommand, see Oracle Fusion Middleware Developing with Oracle WebCenter Content.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IdcCommandServerHost=instance_name.example.com

See Also

- HttpServerAddress

IdcCommandUser

Specifies the user that is permitted to execute commands using IdcCommand.

There is no default setting.

For information about IdcCommand, see Oracle Fusion Middleware Developing with Oracle WebCenter Content.

Usage

- Section 2.7, "Content Server"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

IdcCommandUser=sysadmin

IdcHttpHeaderVariables

Defines data parameters to include in HTTP header responses.

This is a comma-delimited list.

The format for encoding the name value pairs is the typical hda format after applying the Content Server HTTP header encoding.

The values are UTF-8 encoded and special characters are %xx encoded.

This setting is specifically designed for web server plug-ins that want to audit the requests made by the client. The plug-ins can examine the HTTP headers in the responses, but not the body of the content. By pushing some of the parameters of the request into an HTTP header response, a plug-in can audit which documents were accessed and what actions were performed on them.

The name of the HTTP header generated by the Content Server instance when sending a response to an HTTP-based client is IdcVariables.

Usage

- Section 2.27, "Web Server"

Location

IntradocDir/config/config.cfg

Example

If IdcHttpHeaderVariables=IdcService,dDocName, then prior to the UTF-8 encoding being applied, the header value might be:

@Properties LocalData
IdcService=GET_DOC_PAGE
dDocName=TestDoc
blDateFormat=M/d{/yy}{ h:mm[:ss]{ a}}!mAM,PM!tAmerica/New_York
blFieldTypes=
@end

The UTF-8 encoding would leave all the above characters alone, except that it would change every line feed character into the %0A characters. The blDateFormat is the system date format for the Content Server instance.

IdcHomeDir

Defines the location of the server media for Oracle WebCenter Content, which can run media for any of the following: Content Server, Inbound Refinery, and Records.

The location can not be modified by an administration after Oracle WebCenter Content is deployed; it is a fixed location based on the current location of the media

Usage

- Section 2.12, "Directories and Paths"

Location

DomainHome/ucm/idc

Example

Used as a configuration setting:

IdcHomeDir=MW_HOME/user_projects/domains/base_domain/ucm/idc

IdcLocale

Sets the value that is placed in the HTTP cookie of the client to keep track of the current user's locale.

Usage

- Section 2.18, "Localization"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IdcLocale=Deutsch

IdcNativeDir

Defines the path to the resource data subdirectory of the runtime media home for Oracle WebCenter Content.

For information on local copies and load balancing, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Content.

Usage

- Section 2.12, "Directories and Paths"

Location

- IdcNativeDir/resources/

Example

Used as a configuration entry:

$IdcNativeDir=/ucm/cs/resources/

IdcResourcesDir

Defines the path to the resource data subdirectory of the runtime media home for Oracle WebCenter Content.

For information on local copies and load balancing, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Content.

Usage

- Section 2.12, "Directories and Paths"

Location

- IdcHomeDir/resources/

Example

Used as a configuration entry:

$IdcHomeDir=/ucm/resources/

IdcServerBindAddress

Used in clustered environments to bind the Content Server instance to a specific IP address.

Usage

- Section 2.7, "Content Server"

Location

Set in the config.cfg file of the Content Server instance listening for requests:

IntradocDir/config/config.cfg

Example

Used as a configuration variable:

IdcServerBindAddress=IPaddress

IdcServerSocketQueueDepth

Specifies the depth of the TCP/IP socket queue.

This setting can be used to tune Content Server performance, particularly in a clustered environment. Decreasing this value might limit Content Server throughput.

Default is 200.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IdcServerSocketQueueDepth=256

IdcServerThreadQueryTimeout

Specifies the checkout time. The configuration is defined for all user threads and applicable to all user services.

Large file checkins often time out due to the amount of I/O that occurs. Database locks are held while the large file is written and this blocks subsequent checkins. This configuration setting can be used to lengthen the checkout time.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

The setting is expressed in seconds. To make the timeout 5 minutes, set:

IdcServerThreadQueryTimeout=300

IndexableRenditions

A comma-delimited list of single character codes for renditions to be indexed other than the primary, alternate, or web-viewable renditions. Typically only one letter will be used because only one rendition will be indexable (such as the XML rendition).

This is used in conjunction with IsAllowIndexRenditions.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

See Also

- IsAllowIndexRenditions

IndexerAutoWorkInterval

Defines the interval in seconds at which the Indexer automatic update cycle checks for changes.

Default is 300 (5 minutes).

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IndexerAutoWorkInterval=600

IndexerLargeFileSize

Determines the file size in megabytes at which the Indexer will place the file in its own bulkload (batch) file.

Files larger than this setting are indexed in a separate bulkload. Files smaller than this setting will be indexed in a batch with other files.

Default is 1 megabyte.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IndexerLargeFileSize=2

IndexerRebuildStagingManualCopy

Enables an index rebuild to create the collection in another location.

This variable is typically used when rebuilding extremely large collections. When the rebuild is finished, the results can be merged back to the collection manually.

When set to TRUE, the rebuilt index is created in the location set by the IndexerRebuildStagingPath value.

When set to FALSE, the rebuilt index is created in the next active index directory.

Default is FALSE.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IndexerRebuildStagingManualCopy=true

See Also

- IndexerRebuildStagingPath

IndexerRebuildStagingPath

Defines the path where an Indexer rebuild will be created.

This variable is typically used when rebuilding extremely large collections. When the rebuild is finished, the results can be merged back to the collection manually.

There is no default value.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IndexerRebuildStagingPath=c:/buildX/

See Also

- IndexerRebuildStagingManualCopy

IndexerTouchMonitorInterval

Defines the time that Content Server waits before it will treat an Indexer lock file whose timestamp has not changed as having expired. The system will also touch any locks it is maintaining twice during this interval.

An Indexer lock is created by placing a lock file into an appropriate directory. In order for the lock to persist, the timestamp on the file must change periodically. Otherwise Content Server will treat the lock as an expired lock.

The smaller the value of this setting, the quicker that locks can alternate between Indexing cycles. The larger the value, the more likely that high activity (which could keep a touch request delayed for many seconds) will cause Content Server to falsely report a lock as having expired. If a lock is falsely expired, it can cause duplicated effort (although it should not have any long term impact on the state of Content Server).

Default is 12000 milliseconds (12 seconds).

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

IndexerTouchMonitorInterval=15000

See Also

- IndexerTraceCycleListChanges

- IndexerTraceLockFileChanges

IndexerTraceCycleListChanges

Dumps trace information to the console for changes to the list of active indexing cycles maintained by Content Server.

At certain points in an indexing cycle, an exclusive lock is required, so indexing cycles may have to wait for other cycles to become inactive. Enabling this setting can help you audit the performance of the Indexer.

When set to TRUE, changes to the indexing cycle list are output to the console.

When set to FALSE, changes to the indexing cycle list are not output.

Default is FALSE.

Note:
This variable is obsolete as of Content Server version 7.0. Functionality is now available on the System Audit Information page.

Usage

- Section 2.11, "Debugging"

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IndexerTraceCycleListChanges=true

See Also

- IndexerTouchMonitorInterval

- IndexerTraceLockFileChanges

IndexerTraceLockFileChanges

Dumps trace information to the console for changes Content Server makes to the Indexer lock and suspension files.

When set to TRUE, changes to the files are output to the Content Server console.

When set to FALSE, changes to the files are not output.

Default is FALSE.

Note:
This variable is obsolete as of Content Server version 7.0. Functionality is now available on the System Audit Information page.

Usage

- Section 2.11, "Debugging"

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IndexerTraceLockFileChanges=true

See Also

- IndexerTouchMonitorInterval

- IndexerTraceCycleListChanges

IndexerTraceStartStop

When set to TRUE, traces the starting and stopping of index cycles.

Default is FALSE.

Note:
This variable is obsolete as of Content Server version 7.0. Functionality is now available on the System Audit Information page.

Usage

- Section 2.11, "Debugging"

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IndexerTraceStartStop=true

See Also

- IndexerTouchMonitorInterval

- IndexerTraceCycleListChanges

InitialColID

Defines the counter that initializes the first collection ID.

This defines the initial Contribution Folder identifier for the server (in millions).

This variable is set automatically by the Folders installation program if the WebDAV function is enabled at install.

Default is 0.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

InitialColID=0

InstanceDescription

Defines a description for the instance.

The instance description is used in the Content Server interface.

Usage

- Section 2.7, "Content Server"

Location

- System Properties, Server tab, Instance Description

- IntradocDir/config/config.cfg

Example

As a configuration entry:

InstanceDescription=Master_on_Server1

As Idoc Script, returns the server instance description as a string:

<$InstanceDescription$>

See Also

- IDC_Name

- InstanceMenuLabel

InstanceMenuLabel

Defines the label for the instance that is used in the Windows Start menu.

There is no default value.

Usage

- Section 2.7, "Content Server"

Location

System Properties, Server tab, Instance Menu Label

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

InstanceMenuLabel=Master_on_Server1

See Also

- IDC_Name

- InstanceDescription

IntradocDir

The directory containing the configuration and data specific to a Content Server instance.

There is no default value. The value depends on which configuration is specified: cs (for Content Server), ibr (for Inbound Refinery), or urm (for Records).

It is recommended that you move the directory onto a network share if you are managing a load balancing cluster.

Usage

- Section 2.12, "Directories and Paths"

Location

- Content Server: DomainHome/ucm/cs/bin/intradoc.cfg

- Inbound Refinery: DomainHome/ucm/ibr/bin/intradoc.cfg

- Records: DomainHome/ucm/urm/bin/intradoc.cfg

Example

Used as a configuration entry:

IntradocDir=c:/ucm/cs1

IntradocRealm

Defines the realm used when the Content Server instance or the web server plug-in challenges for Basic authentication.

In browsers, the realm is usually called a resource when it is displayed in the login dialog.

NTLM does not use a realm; authentication is always against the entire Microsoft network.

Default is IDC Security.

Usage

- Section 2.24.2, "External Security"

- Section 2.27, "Web Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IntradocRealm=main

See Also

- NtlmSecurityEnabled

IntradocServerHostName

Defines the host name to use when opening a socket connection to the Content Server instance.

This setting is used by the CGI code that translates calls from the web server to requests to the Content Server.

Default value is localhost.

To call services remotely, IntradocServerHostName must be set to IP or DNS.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IntradocServerHostName=IP

See Also

- HttpServerAddress

IntradocServerPort

Defines the port that the web server filter or any other application should use to talk to the Content Server instance.

This setting tells the CGI code that translates from a call to the web server to a request to the Content Server instance to use this port when talking to Content Server. The CGI code will pick up this value automatically if the web server is stopped and started after the Content Server instance has been stopped and started.

In IIS, the CGI code is implemented by the iis_idc_cgi.dll ISAPI extension.

Default is 4444.

To call services remotely, the server port must be defined.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IntradocServerPort=5550

IsAllowIndexRenditions

If set to TRUE, allows extra renditions of a document. This is only used if there are no indexable vault renditions or web-viewable renditions.

The accepted rendition types are listed in IndexableRenditions.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

See Also

- IndexableRenditions

IsAutoArchiver

Enables the automatic import or transfer of content items.

When set to TRUE, Content Server will automatically import and transfer archives.

When set to FALSE, Content Server will not automatically import or transfer archives.

The NoAutomation setting overrides this setting.

Default is TRUE.

Usage

- Section 2.1, "Archiver"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IsAutoArchiver=false

See Also

- NoAutomation

IsAutoNumber

Enables automatic numbering of Content IDs.

When set to TRUE, a Content ID (dDocName) is automatically assigned to each new content item upon checkin.

When set to FALSE, the user must specify a Content ID for each new content item.

Default is FALSE.

Usage

- Section 2.5, "Content Items"

Location

- System Properties, Options tab, Automatically assign a Content ID on check in

- Administration, Admin Server, General Configuration menu option, Automatically assign a content ID on check in

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IsAutoNumber=true

See Also

- AutoNumberPrefix

IsAutoQueue

Enables the processing of content items after conversion by Inbound Refinery.

If set to TRUE, Content Server will process content items after conversion by Inbound Refinery.

If set to FALSE, Content Server will not process content items after conversion by Inbound Refinery.

The NoAutomation setting overrides this setting.

Default is TRUE.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IsAutoQueue=false

See Also

- NoAutomation

IsAutoSearch

Enables automatic indexing and archive export.

When set to TRUE, Content Server automatically indexes content items or automatically export documents to an archive.

When set to FALSE, Content Server does not automatically index content items or automatically export documents to an archive.

The NoAutomation setting overrides this setting.

Default is TRUE.

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IsAutoSearch=true

See Also

- NoAutomation

IsContentRefineryPresent

Specifies if Inbound Refinery is installed.

This value is set to FALSE during initial Oracle WebCenter Content installation.

This value is set to TRUE during Inbound Refinery installation.

Default is FALSE.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IsContentRefineryPresent=true

IsDpSubmitErrorFatal

Used with Content Profiles. When set to TRUE, enables Content Server to issue a fatal error when a global rule violation is encountered.

Usage

- Section 2.6, "Content Profiles"

Location

IntradocDir/config/config.cfg

Example

IsDpSubmitErrorFatal=true

See Also

- Oracle Fusion Middleware Managing Oracle WebCenter Content

IsDynamicConverterEnabled

Enables Dynamic Converter.

This value is set to FALSE during initial Oracle WebCenter Content installation.

This value is set to TRUE during Dynamic Converter installation.

Default is FALSE.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

- System Properties, Options tab, Enable Dynamic Converter

- Administration, Admin Server, General Configuration menu option, Enable Dynamic Converter

- IntradocDir/config/config.cfg

Example

As a configuration setting, enables Dynamic Converter functionality:

IsDynamicConverterEnabled=true

As Idoc Script, used to evaluate whether dynamic converter functionality is enabled:

<$if IsDynamicConverterEnabled and isTrue(IsDynamicConverterEnabled)$>
<tr>
<td align="center" width="75">
<a href="<$HttpCgiPath$>?IdcService=GET_TEMPLATE_CONVERSIONS">
<img src="<$HttpImagesRoot$><$admin_conversion_image$>" border="0"
width="<$adminImageWidth$>" height="<$adminImageHeight$>"></a>
</td>
<td width="10">&nbsp;
</td>
<td width="245"><span class=largeTableEntry>
<a href="<$HttpCgiPath$>?IdcService=GET_TEMPLATE_CONVERSIONS">
<$lc("wwTemplateConversions")$></span></a>
</td>
</tr>
<$endif$>

IsFormsPresent

Specifies if the PDF Forms software is installed.

This value is set to FALSE during initial installation.

This value is set to TRUE during PDF Forms installation.

Note:
This variable is deprecated. Use IsContentRefineryPresent instead.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IsFormsPresent=false

See Also

- IsContentRefineryPresent

IsJava

Displays the local data of a Content Server web page.

This variable can be set as a flag on a page or as a parameter to a service call.

Usage

- Section 2.11, "Debugging"

Output

When set to TRUE, returns the local data in the DataBinder.

Example

When included in the code on a Content Server web page, displays the local data of a page:

<$IsJava=1$>

When included in a Content Server URL, displays the local data for the New Checkin page:

http://myinstance.com/idcplg/idc_cgi_isapi-instance.dll?IdcService=CHECKIN_NEW_FORM&IsJava=1

IsJdbcLockTrace

Dumps trace information to the console for database lock activity.

Used only with SQL Server and Oracle databases.

On Solaris, this output also appears in a log file in the IntradocDir/etc/log/ directory.

Default is an empty string.

Note:
This variable is obsolete as of the 7.0 release of Content Server. The functionality is available on the System Audit Information page.

Usage

- Section 2.9, "Database"

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IsJdbcLockTrace=true

See Also

- IsJdbcQueryTrace

IsJdbcQueryTrace

Dumps trace information to the console for database query activity.

Used only with SQL Server and Oracle databases.

On Solaris, this output also appears in a log file in the IntradocDir/etc/log/ directory.

Default is an empty string.

Note:
This variable is obsolete as of the 7.0 release of Content Server. The functionality is available on the System Audit Information page.

Usage

- Section 2.9, "Database"

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IsJdbcQueryTrace=true

See Also

- IsJdbcLockTrace

IsJspServerEnabled

Enables Java Server Page functionality.

Java Server Page support enables developers to access and modify Content Server content, ResultSets, personalization and security definitions, and predefined variables and configuration settings through Java Server Pages rather than through standard Content Server component architecture. Content Server services and Idoc Script functions can also be executed from Java Server Pages, which reside as executable content in Content Server.

Default is FALSE.

Usage

- Section 2.17, "JSP"

Location

- System Properties, Server tab, Execute Java Server Page (Jsp)

- Administration, Admin Server, General Configuration menu option, Enable Java Server Page (Jsp)

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

IsJspServerEnabled=true

See Also

- JspEnabledGroups

IsOverrideFormat

Enables users to select a different conversion format upon checkin.

When set to TRUE, a Format option list is displayed for the Primary File and Alternate File on the checkin page.

Default is FALSE.

Usage

- Section 2.13, "Field Display"

Location

- System Properties, Options tab, Allow override format on check in

- Administration, Admin Server, General Configuration menu option, Allow override format on check in

- IntradocDir/config/config.cfg

Example

As a configuration setting:

IsOverrideFormat=true

As Idoc Script, returns the value of the override format function:

<$IsOverrideFormat$>

IsPageDebug

Enables a trace of all includes and calls to the Idoc Script eval function.

The contents of the eval function and any dynamically assigned includes are also shown as part of the trace. The trace is indented by one + character per nested level of include or eval call. The trace also shows any error messages (without the nested location information) and the output of any calls to the Idoc Script trace function.

Note:
This setting is not supported in Internet Explorer version 6.

Usage

- Section 2.11, "Debugging"

Output

Results of the trace can be viewed through the debug menu toolbar options which are accessed from the debug trace displayed at the bottom of the web page.

Click the debug trace to display the debug menu toolbar, then click any of the following options:

Element

Description

hide all

Hides any open debug popups.

idocscript trace

Displays a tree structure view of all includes being called.

request binder

Displays information on Local Data and ResultSets. Click a heading to expand the view of detailed information.

response binder

Displays information on Local Data and ResultSets. Click a heading to expand the view of detailed information.

final page binder

Displays information on Local Data and ResultSets. Click a heading to expand the view of detailed information.

javascript log

Displays Logger Console window with default setting of Verbose. Select checkboxes to display the following options: info, warn, error, time, window, trace, global, schema, javascript, LogReader. Click Pause or Clear to control the speed and amount of information displayed on the Logger Console.

Example

Used as a configuration setting in the Content Server config.cfg file, so it applies to the entire server:

IsPageDebug=1

In a web browser, added to the end of the page's URL in the Address field:

&IsPageDebug=1

Used on a template page or in an Idoc Script include:

<$IsPageDebug=1$>

See Also

- "eval" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

- "setResourceInclude" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

- "trace" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

isPhysicallySplitDir

Tells the Content Server instance that the vault/ and weblayout/ directories are on different file systems.

When set to TRUE, tells the server that the directories are on different file systems.

Default is FALSE.

Usage

- Section 2.12, "Directories and Paths"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

isPhysicallySplitDir=true

See Also

- WeblayoutDir

IsPrimaryUserBase

Specifies whether the LDAP provider is the primary LDAP server where external users are defined.

When set to TRUE, the provider will be used to authenticate new LDAP users who have not previously logged in to the Content Server instance.

When set to FALSE, the provider will be used to authenticate only LDAP users who have previously logged in using credentials from that provider.

Default is TRUE.

Note:
This setting is obsolete for version 7.0 and later of Content Server. See Priority for information on setting the order in which LDAP providers will be checked.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, Primary User Base

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

IsPrimaryUserBase=false

isRepromptLogin

This workflow configuration entry is a suffix appended to a workflow step, forcing a new authentication challenge.

When set to TRUE, this configuration variable forces a login at a specific step of a workflow. This acts as a digital signature for that step.

This variable can be added at multiple steps of a workflow.

Usage

- Section 2.28, "Workflow"

Location

IntradocDir/config/config.cfg

Example

In the following example, a review step named VPApproval requires a digital signature before continuing in the workflow. Set the isRepromoptLogin configuration entry as follows before initiating the workflow:

VPApproval:isRepromptLogin=true

See Also

- Oracle Fusion Middleware Developing with Oracle WebCenter Content

IsSavedWfCompanionFile

Saves a copy of the companion file that is created when a piece of content enters a workflow. Normally the companion file is deleted when the content is approved and exits the workflow.

To use this variable, insert the variable as shown into the config.cfg file and restart the Content Server instance. The file will be saved in the IntradocDir/data/workflow/saved/ directory.

Usage

- Section 2.28, "Workflow"

Location

IntradocDir/config/config.cfg

Example

As a configuration variable:

IsSaveWfCompanionFiles=true

isValidateFile

Used as a parameter to the Upload applet. This variable verifies that the file to be uploaded exists. In order to be used, a component must be created that overwrites the applet definition as defined in the std_multiupload_applet_definition include in the std_page.htm resource file.

Usage

- Section 2.7, "Content Server"

Example

Used as a configuration entry:

isValidateFile=true

IsWebServerPagesOnly

Used with the ExtranetLook component. This variable determines if cookie-based authentication is used or not. For details about using the ExtranetLook functionality, see Oracle Fusion Middleware Administering Oracle WebCenter Content.

When IsWebServerPagesOnly is set to TRUE, basic authentication is used and cookie-based logon/logoff functionality is disabled. Customized versions of the web server filter are used.

If set to FALSE, cookie-based authentication is used.

Usage

- Section 2.7, "Content Server"

Location

- IntradocDir/config/config.cfg

Example

IsWebServerPagesOnly=FALSE

See Also

- CookieAuthTimeoutInDays

- CookieProxyPassword

JdbcConnectionString

Defines the Java Database Connectivity (JDBC) connection (SQL Server Data Source Name), including the hostname, port number, and instance name.

This setting is automatically configured during installation if there are no network errors that make it impossible for the system to connect to the database. This setting must be changed manually if the database is changed or if the system could not find the database during installation.

If the run time version of Microsoft Access or MSDE is used, there are no database configuration options to set.

Default is JdbcConnectionString=JDBC:ODBC:SQLForInstance_name.

Usage

- Section 2.9, "Database"

Location

- System Properties, Database tab, JDBC Connection String

- IntradocDir/config/config.cfg

Example

Defines the JDBC connection path:

JdbcConnectionString=jdbc:oracle:thin:@hostname:port_number:instance_name

See Also

- JdbcDriver

JdbcDriver

Defines the Java Database Connectivity (JDBC) device driver name.

This setting is automatically configured during installation if there are no network errors that make it impossible for the system to connect to the database. This setting must be manually changed if the database is changed or if the system could not find the database during the installation.

If the run time version of Microsoft Access or MSDE is used, there are no database configuration options to set.

There is no default value.

Usage

- Section 2.9, "Database"

Location

- System Properties, Database tab, JDBC Driver options/JDBC Driver Name

- IntradocDir/config/config.cfg

Example

Defines the JDBC device driver:

JdbcDriver=oracle.jdbc.driver.OracleDriver

See Also

- JdbcConnectionString

JdbcPassword

Defines the SQL Server database password.

There is no default value.

Usage

- Section 2.9, "Database"

Location

- System Properties, Database tab, JDBC User Password

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

JdbcPassword=password

See Also

- JdbcUser

- JdbcPasswordEncoding

JdbcPasswordEncoding

Defines the type of encoding to use when storing the SQL Server database password.

To disable password encryption, set this value to ClearText.

Default is Intradoc.

If any other nonempty value is assigned, no encoding is performed.

Usage

- Section 2.9, "Database"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

JdbcPasswordEncoding=ClearText

JdbcUser

Defines the SQL Server database user name.

Default is sa.

Usage

- Section 2.9, "Database"

Location

- System Properties, Database tab, JDBC User Name

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

JdbcUser=sa

See Also

- JdbcPassword

JspAdminQuery

Defines which files are to be made available as web application files.

This setting is generally used to define the query to find the web application archiver (.war file) when deploying the Oracle JavaBean.

Usage

- Section 2.17, "JSP"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

JspAdminQuery=dExtension <matches> war

See Also

- IsJspServerEnabled

JspDefaultIndexPage

Defines the default page for a web application.

This is a comma-delimited list of file names that defines a search sequence. If the first file is not present, the second file will be the default page, and so on.

Default is index.html,index.htm,index.jsp.

Usage

- Section 2.17, "JSP"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

JspDefaultIndexPage=index.html,index.htm,index.jsp

See Also

- IsJspServerEnabled

JspEnabledGroups

Defines the security groups to be enabled for Java Server Page functionality.

Because Java Server Pages usually have full privileges to any resource on the hosting system, it can be important to restrict Java Server Pages to security groups which allow only contributors with certain permissions.

Usage

- Section 2.17, "JSP"

Location

- System Properties, Server tab, Jsp Enabled Groups

- Administration, Admin Server, General Configuration menu option, Jsp Enabled Groups

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

JspEnabledGroups=jsp,group1

See Also

- IsJspServerEnabled

JvmCommandLine

Defines the location of the executable for the Java Virtual Machine command line.

There is no default value.

Usage

- Section 2.7, "Content Server"

- Section 2.8.1, "Inbound Refinery"

Location

- Content Server: DomainHome/ucm/cs/bin/intradoc.cfg

- Inbound Refinery: DomainHome/ucm/ibr/bin/intradoc.cfg

Example

Used as a configuration entry:

JvmCommandLine="c:/jdk1.3.1/bin/java.exe" -classpath $CLASSPATH $STARTUPCLASS

LatestReleasedTimestampTimeout

Defines the minimum interval in milliseconds at which the timestamp of a converted content item will be checked.

For a particular cached web-viewable file, Dynamic Converter will consult the timestamp again only after the time specified by this setting has passed.

If the timestamp of a cached content item has changed, Dynamic Converter reconverts the file.

Default is 1500 milliseconds (1.5 seconds).

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LatestReleasedTimestampTimeout=60000

LdapAdminDN

Specifies a user name that has Read permission for the LDAP server.

If this setting is not defined, the provider will connect to the LDAP server anonymously.

If the LDAP provider is communicating with Active Directory, a user name and password is required, and must be a valid domain user in the format DOMAIN\username.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, LDAP Admin DN

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

LdapAdminDN=ldap_admin

See Also

- LdapAdminPassword

LdapAdminPassword

Specifies the password for the LdapAdminDN setting, which specifies a user name that has Read permission for the LDAP server.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, LDAP Admin Password

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

LdapAdminPassword=idc2

See Also

- LdapAdminDN

LdapPort

Defines the port number the LDAP server listens on.

Default is 389, unless you are using SSL.

If you are using SSL (see UseSecureLdap), set this value to 636.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, LDAP Port

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

LdapPort=636

See Also

- UseSecureLdap

LdapServer

Host name of the LDAP server.

If the provider is communicating with Active Directory, this should be the host name of a primary domain controller.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, LDAP Server

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

LDAPServer=iplanet_dir

LdapSuffix

Specifies the root suffix (naming context) to use for all LDAP operations (such as o=example.com or dc=example,dc=com).

All mapping of LDAP groups to Content Server roles and accounts will begin at this root.

Do not include spaces before or after commas.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, LDAP Suffix

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

LdapSuffix=dc=example,dc=com

LkDisableOnRebuild

Used with the Link Manager functionality.

This variable controls link extraction during the indexing rebuild cycle.

If set to TRUE, this variable prevents Link Manager from extracting links during the index rebuild cycle. If set to FALSE, Link Manager extracts links during the indexing rebuild cycle.

The default is FALSE.

Because Link Manager does all of its work during the indexing cycle, it will increase the amount of time required to index documents and to rebuild collections. However, the time taken may not be noticeable because most of the time is spent indexing the document into the collection. The amount of time required depends on the type and size of the documents involved. That is, if the file needs to be converted, this requires more time than text-based (HTML) files.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LkDisableOnRebuild=TRUE

See Also

- For details about using Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

LkDisableReferenceInfo

Used with the Link Manager functionality.

This variable enables or disables the Resources section on the Content Information page. If set to TRUE, it configures Content Server to suppress the References section. Link Manager then does not compute the link references for presentation.

If set to FALSE, Content Server displays the Show and Hide toggle switches on the Content Information page. By clicking on the toggle switch, link references are displayed or concealed.

The default is FALSE.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LkDisableReferenceInfo=TRUE

See Also

- For details about using Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

LkDisallowConversionFormats

Used with the Link Manager functionality.

This variable provides a list of file formats that Link Manager will not covert before being processed for link extraction. By default, this is empty.

There are some file formats (such as Word) that must be converted by HtmlExport before links can be extracted. However, links in text-based file formats (HTML) can be extracted by Link Manager without requiring conversion by HtmlExport.

For example, you may have PHP files (or files in some other custom format) that are actually text-based. For such files, conversion by HtmlExport may not be necessary before Link Manager processes them for link extraction. Such formats can be listed in this configuration variable.

Usage

- Section 2.5, "Content Items"

Parameters

The only parameter(s) are the formats.

Location

IntradocDir/config/config.cfg

Examples

In the following example, specifying the full MIME type format limits the variations of the listed types that are excluded. For example, listing application/msword will not exclude application/vnd.msword or other variations. In this case, you must include each specific MIME type variation in the list that you want to exclude.

LkDisallowConversionFormats=application/msword,audio/wav,video/avi

In the following example, all variations of each MIME type in the list are excluded. Using the shortened format of the MIME type is more advantageous in that it allows greater flexibility.

LkDisallowConversionFormats=msword,wav,avi

Important:
Link Manager does not use HtmlExport to convert files that contain any of the following strings in the file format: hcs, htm, image, text, xml, jsp, and asp. These files are handled by Link Manager without need for conversion. To check the current file formats and extension mappings of your system, use the File Formats window in the Configuration Manager.

See Also

- For details about using Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

LkIsSecureSearch

Used with the Link Manager functionality.

This variable is used to manage security restriction checks for non-admin users during a link search.

If set to TRUE, this configures Link Manager to perform a security check on non-admin users while implementing a managed link search. This is the default setting.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LkIsSecureSearch=TRUE

See Also

- For details about using Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

LkReExtractOnRebuild

Used with the Link Manager functionality.

This variable controls link extraction from previously indexed documents during a rebuild. If set to TRUE, it configures Link Manager to extract links from documents as they are indexed into the system during a rebuild. This is the default setting.

If set to FALSE, this prevents Link Manager from extracting links from documents as they are indexed into the system during a rebuild.

Because Link Manager does all of its work during the indexing cycle, it will increase the amount of time required to index documents and to rebuild collections. However, the time taken may not be noticeable since most of the time is spent indexing the document into the collection. Although, the amount of time required does depend on the type and size of the documents involved. That is, if the file needs to be converted, this requires more time than text-based (HTML) files.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LkReExtractOnRebuild=FALSE

See Also

- For details about using Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

LkRefreshBatchSize

Used to control the number of links submitted to Site Studio during a refresh process. By default, the batch size value is set to 100.

Depending on the value, this configuration variable can make the refresh processes more (or less) receptive to an abort request. The calculation for LkRefreshErrorsAllowed is completed after, not during, each batch process. Therefore, the lower the value for LkRefreshBatchSize, the more likely it is that the refresh activity will promptly terminate because the number of allowed errors is more quickly exceeded.

If you are using Site Studio, LkRefreshBatchSize enables you to have better control over the refresh abort option than using the combined LkRefreshErrorPercent and LkRefreshErrorThreshold settings. For example, if you set the percent value to 5 and the threshold value to 20, you would expect the refresh activity to abort after the first error. However, Link Manager might actually process multiple errors before aborting.

The reason for this is that during refresh activities, all the links recognized as Site Studio links (or those requiring Site Studio processing) are grouped and sent to Site Studio as a batch. Consequently, refreshes are more efficient, but abort requests are unresponsive during this time because Site Studio is unaware of aborts and total error counts.

However, Site Studio is aware of the number of errors it has encountered in the current batch. For this reason, the Link Manager's abort calculation can not take place in all situations and the error configuration values (percent and threshold) are simply suggestions to Link Manager for when an abort should occur. Using LkRefreshBatchSize, however, enables you to more accurately control the abort receptivity during refresh activities that involve Site Studio link batches.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LkRefreshBatchSize=200

See Also

- For details about using Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

LkRefreshErrorPercent

Used with Link Manager functionality.

This variable is used with LkRefreshErrorThreshold to compute if the refresh activity should be aborted. When the refresh activity processes more links than the threshold value, Link Manager calculates the proportion of errors. If the number of errors exceeds the percent value, the refresh activity is aborted.

The percent value is set to 10 by default.

Note:
If you choose to set a value for LkRefreshErrorsAllowed, it could override the combination of threshold and percent values. For example, if the value is less than the calculated threshold/percent value for links/errors, then the refresh activity could abort even if the number of links processed does not exceed the threshold limit. Therefore, it is recommended that you use either the LkRefreshErrorsAllowed configuration setting or the combination of the LkRefreshErrorThreshold and LkRefreshErrorPercent configuration settings.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LkRefreshErrorPercent=20

See Also

- For details about using Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

- LkRefreshErrorsAllowed

- LkRefreshErrorThreshold

LkRefreshErrorsAllowed

Used with Link Manager functionality.

This variable sets an absolute error count for refresh processes. When the set number of errors is encountered, the refresh activity aborts. This configuration setting is not used by default.

Note:
If you choose to set a value for LkRefreshErrorsAllowed, it could override the combination of threshold and percent values. For example, if the value is less than the calculated threshold/percent value for links/errors, then the refresh activity could abort even if the number of links processed does not exceed the threshold limit. Therefore, it is recommended that you use either the LkRefreshErrorsAllowed configuration setting or the combination of the LkRefreshErrorThreshold and LkRefreshErrorPercent configuration settings.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LkRefreshErrorsAllowed=10

See Also

- For details about using Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

- LkRefreshErrorPercent

- LkRefreshErrorThreshold

LkRefreshErrorThreshold

Used with Link Manager functionality.

This variable is used with LkRefreshErrorPercent to compute if the refresh activity should be aborted. When the refresh activity processes more links than the threshold value, Link Manager calculates the proportion of errors. If the number of errors exceeds the percent value, the refresh activity is aborted.

The threshold value is set to 100 by default.

Note:
If you choose to set a value for LkRefreshErrorsAllowed, it could override the combination of threshold and percent values. For example, if the value is less than the calculated threshold/percent value for links/errors, then the refresh activity could abort even if the number of links processed does not exceed the threshold limit. Therefore, it is recommended that you use either the LkRefreshErrorsAllowed configuration setting or the combination of the LkRefreshErrorThreshold and LkRefreshErrorPercent configuration settings.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LkRefreshErrorThreshold=200

See Also

- For details about using Link Manager, see Oracle Fusion Middleware Managing Oracle WebCenter Content.

- LkRefreshErrorsAllowed

- LkRefreshErrorPercent

LmDefaultLayout

Defines the default layout to use (for example, Top Menus or Trays).

The default installation value is Trays.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

LmDefaultLayout=Top Menus

LmDefaultSkin

Defines the default skin to use (for example, Oracle, Oracle2).

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

LmDefaultSkin=Oracle

LocaleArchiverDateFormat

Specifies the naming format for Archiver batch file subdirectories. Often used when exporting and importing with different versions of Content Server.

Default is yy-MMM-dd_HH.mm.ss_SSS. For example, 03-feb-04_15.04.14_174.

Usage

- Section 2.1, "Archiver"

- Section 2.18, "Localization"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

LocaleArchiverDateFormat=dd-mm-yy

LogMessagePrefix

Adds a prefix to log entries to designate which the Content Server instance is creating the entry.

There is no default value.

Usage

- Section 2.7, "Content Server"

- Section 2.11, "Debugging"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

LogMessagePrefix=Master

LogName

Specifies the file name of the log file created by the Content Server Analyzer utility.

This log file will be created in the directory specified by the IdcAnalyzeLogDir setting.

Default is IdcAnalyze.log.

Usage

- Section 2.7, "Content Server"

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

LogName=contentserver1_analyze.log

See Also

- IdcAnalyzeLogDir

- "SafeDir" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

- TempDir

MacSupportsSignedApplets

Enables the Upload and Download Applets for Macintosh clients.

Used only when Macintosh clients are used.

When set to TRUE, Macintosh clients can use the Upload and Download Applets for checking multiple files in and out.

When set to FALSE, Macintosh clients cannot use the Upload and Download Applets.

Default is FALSE.

Usage

- Section 2.3, "Clients"

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MacSupportsSignedApplets=true

MailServer

Defines the email server that is used to process emails.

Email support is required for workflow notifications, subscription notifications, and project notifications in Collaboration Server.

There is no default value.

Usage

- Section 2.7, "Content Server"

Location

- System Properties, Internet tab, Mail Server

- Administration, Admin Server, Internet Configuration menu option, Mail Server

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MailServer=mail.example.com

See Also

- SysAdminAddress

- SmtpPort

MajorRevSeq

Defines the major sequence for revision numbers.

Returns the major revision label sequence (returns the value of the configuration setting).

Returns a string.

Default is 1-99.

Usage

- Section 2.5, "Content Items"

Location

- System Properties, Options tab, Major Revision Label Sequence

- Administration, Admin Server, General Configuration menu option, Major Revision Label Sequence

- IntradocDir/config/config.cfg

Example

As a configuration setting:

MajorRevSeq=A-Z

As script, returns the value of the configuration setting:

<$MajorRevSeq$>

See Also

- MinorRevSeq

MaxArchiveErrorsAllowed

Sets the number of errors after which the Archiver stops importing or exporting. Default is 50.

Usage

- Section 2.1, "Archiver"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxArchiveErrorsAllowed=10

MaxCollectionSize

Defines the number of files to be passed to the Indexer in one batch.

Valid range is 1 to 65535.

A value of 2000 is recommended for large index collections. Lower values will result in inefficient indexing performance.

Returns the number of files per batch.

Default is 25.

Usage

- Section 2.16, "Indexing"

Location

- Repository Manager, Indexer tab, Configure, Content Items Per Indexer Batch

- IntradocDir/config/config.cfg

Example

As a configuration setting, defines the batch size:

MaxCollectionSize=25

As script, returns the value from configuration files:

<$MaxCollectionSize$>

MaxConversionCacheSizeInMegs

Defines the maximum size of the Dynamic Converter cache, in megabytes.

When a cleanup scan is run (see DatedCacheIntervalDays), the cache is cleaned up according to this setting as follows:

- If the Dynamic Converter cache is larger than this size, the oldest cached files (determined by last access date) are deleted until the cache is smaller than this size.

- If the Dynamic Converter cache is smaller than this size, only files that are older than the ConversionCacheExpirationPeriodInDays and were not converted using conversion rules (forced or up front conversion) are deleted.

Default is 10,240 (10 gigabytes).

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxConversionCacheSizeInMegs=5,000

See Also

- ConversionCacheExpirationPeriodInDays

- DatedCacheIntervalDays

MaxDocIndexErrors

Sets the number of errors after which the Indexer stops indexing or rebuilding.

Default is 50.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxDocIndexErrors=50

MaxErrorsAllowed

Sets the number of errors after which the Batch Loader stops processing records from the batch load file.

If you plan to run the Batch Loader with a large number of content items overnight, then increase the default value. If you monitor the Batch Loader with a small amount of content items, then decrease the default value.

Default is 50.

Returns value as integer.

Usage

- Section 2.2, "Batch Loader"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

MaxErrorsAllowed=50

MaxIndexableFileSize

Sets the maximum document file size that be indexed. For full-text indexing, the maximum size default is 10 MB unless changed by using this configuration variable.

The default for MaxIndexableFileSize is 10485760. If larger documents require full-text indexing, the value of MaxIndexableFileSize should be increased.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

MaxIndexableFileSize=10485760

MaxIntegerAllowed

Sets the maximum value allowed in custom Integer metadata fields.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

MaxIntegerAllowed=1000000

See Also

- MinIntegerAllowed

MaxNumRecursiveStepDefinitions

Specifies the maximum number of levels that recursion can be used when defining a custom conversion.

A custom conversion engine can call another conversion, but to prevent loops, this setting limits the number of levels of such calls.

Default is 6.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

IntradocDir/ucm/ibr/bin/config.cfg

Example

Used as a configuration entry:

MaxNumRecursiveStepDefinitions=3

MaxQueryRows

Sets the maximum number of rows that are displayed in the Repository Manager, Active Report pages, and the Work In Progress page.

Increasing this value will slow response time.

Default is 200.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxQueryRows=50

See Also

- "IsMaxRows" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

MaxRequestThreadCount

Sets the maximum number of simultaneous request threads.

Default is 100.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxRequestThreadCount=50

MaxResults

Sets the maximum number of content items returned from a search query using the Content Server user interface. If a search request does not specify ResultCount or if ResultCount is greater than MaxResults, MaxResults results will be requested.

Specifying a value overrides the programmed default.

There is no default value. The maximum number of results that can be returned is 200.

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxResults=200

MaxRowsPerTableArchiveExportBatch

Set the maximum number of rows in a table to be archived before exporting Folders structure data.

The maximum number of rows in a table is unlimited. You can specify a positive number.

The default is 100000.

Note:
If MaxRowsPerTableArchiveExportBatch is not set appropriately then the following error message is displayed: csTableArchiveMaxRowExceeded

Usage

- Section 2.1, "Archiver"

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxRowsPerTableArchiveExportBatch=50000

MaxSavedSearchResults

Sets the maximum number of saved searches a user can make. Specifying a value overrides the default (10).

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxSavedSearchResults=25

MaxSearchableSubfolders

Specifies the maximum number of subfolders that will be searched within a hierarchy of Contribution Folders (for example, for searching with a GET_SEARCH_RESULTS query). By default the maximum number of subfolders that will be searched is limited to 500.

Note:
Setting the environment variable to a higher value can result in a significant performance degradation and/or a query larger than the maximum limit allowed in SQL (usually 32,000), in which case the query will fail. This is why the variable exists and is set to a modest value.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

MaxSearchableSubfolders=500

MaxSearchConnections

Sets the maximum number of search connections that are open simultaneously.

This setting only applies when Content Server is configured to use OracleTextSearch for searching. It does not apply if Content Server is configured to use DATABASE.METADATA or DATABASE.FULLTEXT.

For example, if MaxSearchConnections is set to 5 and six search requests are made at the same time, the sixth request goes into a queue until one of the first five requests is completed.

Default is 10.

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxSearchConnections=5

MaxSizeResourceFileCacheMillions

Sets the maximum size of resource files, in millions of double-byte characters.

This value limits the size of files before they are read in and parsed.

Multiply file sizes by 2.5 to get a better estimate of true size in memory.

Default is 10.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxSizeResourceFileCacheMillions=20

MaxStandardDatabaseResults

Sets the maximum number of users displayed.

This is valid for any applet that allows you to select users from a list.

Default is 500.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MaxStandardDatabaseResults=1000

MemoFieldSize

Defines the field size created in the database for memo fields.

Ensure that the database supports whatever size is chosen.

Default is 255 characters.

Usage

- Section 2.9, "Database"

- Section 2.13, "Field Display"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MemoFieldSize=300

See Also

- MinMemoFieldSize

MinIndexableFileSize

Sets the minimum document file size that can be indexed. For full-text indexing, the minimum size default is 5 bytes unless changed by using this configuration variable.

The default for MinIndexableFileSize is 5 bytes.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

MinIntegerAllowed

Sets the minimum value allowed in custom Integer metadata fields.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

MinIntegerAllowed=0

See Also

- MaxIntegerAllowed

MinMemoFieldSize

Defines the size at which a custom metadata field is defined as a memo field rather than a long text field.

If the field sizes of the DocMeta table have been edited directly in the database, Content Server classifies the varchar field types by their lengths.

Default is 255 characters.

The following field type rules apply when this setting is defined.

Field Type

Evaluation Rules

Text

<50

Long Text

>= 50 and < MinMemoFieldSize

Memo

>= MinMemoFieldSize

Usage

- Section 2.9, "Database"

- Section 2.13, "Field Display"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

MinMemoFieldSize=300

See Also

- MemoFieldSize

MinorRevSeq

Defines the minor sequence for revision numbers.

Returns the minor revision label sequence (returns the value of the configuration setting).

Returns a string.

Usage

- Section 2.7, "Content Server"

Location

- System Properties, Options tab, Minor Revision Label Sequence

- Administration, Admin Server, General Configuration menu option, Minor Revision Label Sequence

- IntradocDir/config/config.cfg

Example

As a configuration setting:

MinorRevSeq=a-c

As script, returns the value of the configuration setting:

<$MinorRevSeq$>

See Also

- MajorRevSeq

MSPubexePath

Defines the path for the MS Publisher executable file.

Returns the path as a string.

Default is an empty string.

Usage

- Section 2.8.2.4, "Other Formats"

Location

- Shared Inbound Refinery Configuration screen, Paths tab, MS Publisher Executable Path

- IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

MSPubexePath=c:/Program Files/Microsoft Publisher/mspub.exe

MultiUpload

Enables the multiple file Upload Applet.

When set to TRUE, the Upload Applet is enabled so that multiple files can be zipped and checked in as a single content item.

When set to FALSE, the Upload Applet is disabled.

Default is FALSE.

Usage

- Section 2.7, "Content Server"

- Section 2.3, "Clients"

Location

- System Properties, Options tab, Enable upload applet

- Administration, Admin Server, General Configuration menu option, Enable upload applet

- IntradocDir/config/config.cfg

Example

As a configuration setting, enables the Upload Applet:

MultiUpload=true

As script, evaluates the condition of the Upload Applet:

<$MultiUpload$>

See Also

- DownloadApplet

- UploadApplet

NeverTimeoutForcedConversionsTemplateChange

Defines whether Dynamic Converter will reconvert a file when the template or layout has changed.

When set to TRUE, files that were converted by forced or up front conversion will not be reconverted when the template or layout is changed.

If a conversion rule is changed to use a different template or layout, the normal evaluation logic is used.

Default is FALSE.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

NeverTimeoutForcedConversionsTemplateChange=true

See Also

- TimeoutChangedTemplateForcedConversionsInMins

- TimeoutMismatchedForcedConversionsInMins

NoAutomation

Disables all automated Content Server activity.

This setting overrides the IsAutoArchiver, IsAutoQueue, and IsAutoSearch settings.

Default is FALSE.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

NoAutomation=true

See Also

- IsAutoArchiver

- IsAutoQueue

- IsAutoSearch

noInfoColumn

Defines whether to display the Info column on search results pages.

When set to TRUE, a column containing links to Content Information pages is displayed on the standard search results page.

When set to FALSE, Info links are not displayed on the standard search results page.

Default is FALSE.

Usage

- Section 2.5, "Content Items"

- Section 2.19, "Page Display"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

noInfoColumn=1

See Also

- showDocActions

- showSearchResultsCheckoutColumn

- noRevisionsColumn

noRevisionsColumn

Defines whether to display the Revisions column on search results pages.

When set to TRUE, a column containing links to Revision History pages is displayed on the standard search results page.

When set to FALSE, Revision History links are not displayed on the standard search results page.

Default is FALSE.

Usage

- Section 2.5, "Content Items"

- Section 2.19, "Page Display"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

noRevisionsColumn=1

See Also

- showDocActions

- showSearchResultsCheckoutColumn

- noInfoColumn

NoSearchConnectionCloseOnDocChange

Disables automatic closure of all search connections when a document has been modified (inserted, updated, or deleted).

Caution:
Setting this to TRUE may lead to incorrect search results when the system is under high stress.

When set to TRUE, search connections stay open even when a document is changed.

Default is FALSE.

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

NoSearchConnectionCloseOnDocChange=true

NotationForRequiredFields

Formats how a required metadata field is displayed.

When set, the required field appears with the indicated string in front of the metadata field.

The string is included in a cascading style sheet.

If StyleForRequiredFields is defined, NotationforRequiredFields will be formatted in the style defined by StyleForRequiredFields.

Usage

- Section 2.13, "Field Display"

Parameters

The only parameter is the string.

Location

IntradocDir/config/config.cfg

Example

To set an asterisk in front of a required field:

NotationForRequiredFields=*

See Also

- StyleForRequiredFields

NotificationIntervalInDays

This configuration variable defines how often a notification query is run. Notification queries define the criteria used to search for expired content.

If NotificationIntervalInDays is not set, the default value is one day.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

NotificationIntervalInDays=3

See Also

- EnableExpirationNotifier

- NotificationMaximum

- NotificationQuery

- NotifyExtras

- NotifyTime

NotificationMaximum

This configuration variable defines the maximum number of content items that will be returned by a notification query. Notification queries define the criteria used to search for expired content.

If NotificationMaximum is not set, the default value is 1000.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

NotificationMaximum=500

See Also

- EnableExpirationNotifier

- NotificationIntervalInDays

- NotificationQuery

- NotifyExtras

- NotifyTime

NotificationQuery

This setting defines criteria for the automatic query that searches for expired content.

If NotificationQuery is not set, the default value is all content that expires in the next seven days.

Usage

- Section 2.5, "Content Items"

Parameters

There is one parameter, the query to be used. The query can be one of the following. See the EXAMPLES section for sample queries.

- An Idoc Script query, built from Idoc Script.

- A URL encoded query. This uses the URL displayed in the web browser address when a search is performed.

- A plain text query which defines the search variables.

Location

IntradocDir/config/config.cfg

Example

Idoc Script Example

When used in conjunction with database indexing, the following query provides email notification for all documents that expire in seven days:

NotificationQuery=dOutDate < '<$dateCurrent(7)$>'>

URL Encoded Example

The following query returns all content expiring after August 1, 2007. The URL from the browser address line is copied, beginning with the QueryText portion:

NotificationQuery=QueryText=dOutDate+%3C+%608%2F1%2F06%60&SearchProviders= [...}

Plain Text Query

The following query returns all content expiring after August 1, 2007:

NotificationQuery=8/1/07

See Also

- EnableExpirationNotifier

- NotificationIntervalInDays

- NotificationMaximum

- NotifyExtras

- NotifyTime

NotifyExtras

This configuration variable defines the users who will receive a list of expired content in addition to the authors of each content item. Notification queries define the criteria used to search for expired content.

If the NotifyExtras setting is in the config.cfg file but has no value defined, no extra notification is sent.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

NotificationExtras=jwilson, nadams

See Also

- EnableExpirationNotifier

- NotificationIntervalInDays

- NotificationMaximum

- NotificationQuery

- NotifyTime

NotifyTime

This configuration variable defines the time of day the notification query is run, specified in 24-hour notation. Notification queries define the criteria used to search for expired content.

If NotifyTime is not set, the default value is midnight (00:01).

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

The following example sets the time to 11:30 AM:

NotifyTime=11:30

The following example sets the time to 1:30 PM:

NotifyTime=13:30

See Also

- EnableExpirationNotifier

- NotificationIntervalInDays

- NotificationMaximum

- NotificationQuery

- NotifyExtras

NtlmSecurityEnabled

Enables Windows network authentication for the Content Server instance.

This option is available only when using an IIS web server.

When set to TRUE, users defined on a Windows network (NTLM) or in Active Directory can log in to the Content Server instance using their network credentials.

Default is FALSE.

Usage

- Section 2.24.2, "External Security"

Location

- System Properties, Internet tab, Use Microsoft Security

- Administration, Admin Server, Internet Configuration menu option, Use Microsoft Security

- IntradocDir/config/config.cfg

- IntradocDir/data/users/config/filter.hda

Example

Enables NTLM security:

NtlmSecurityEnabled=true

See Also

- UseNtlm

- UseAdsi

- HasExternalUsers

- IntradocRealm

NumAdditionalRenditions

Used by the Thumbnails program to set the number of renditions of a content item.

When set to 0, thumbnails are not created on search results pages.

When set to 1, thumbnails are created on search results pages.

Default is 0.

Usage

- Section 2.5, "Content Items"

- Section 2.8.2.1, "General Variables"

Location

IntradocDir/config/config.cfg

Example

Used to determine if useThumbnails should be set:

<@dynamichtml searchapi_result_definitions@>
<$if NumAdditionalRenditions and NumAdditionalRenditions > 0$>
<$useThumbnails=1$>
<$endif$>
<@end@>

NumConnections

Sets the number of open connections to the database. Default is 15. The default for standalone applets is 4.

This setting applies to the Content Server instance and any standalone applications and utilities, so each application will use the specified number of connections.

If your database does not allow enough connections to be open at one time, an error will occur when you attempt to start an application or utility.

To avoid this problem, you can isolate the NumConnections setting for the Content Server instance from the setting for applications and utilities as follows:

1. Specify the NumConnections setting for the Content Server instance in the DomainHome/ucm/cs/bin/intradoc.cfg file rather than IntradocDir/config/config.cfg file.

2. Make a copy of the DomainHome/ucm/cs/bin/ directory and give it a unique name (such as DomainHome/ucm/cs/applet_bin/).

3. Set the NumConnections value for application and utilities in the intradoc.cfg file in the new directory (for example, NumConnections=2).

4. Run applications and utilities from the new directory (change any scripts and shortcuts in Windows), but continue to run the Content Server instance from the DomainHome/ucm/cs/bin/ directory.

If necessary, you can create a separate directory and NumConnections setting for each application and utility.

Usage

- Section 2.9, "Database"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

NumConnections=10

OdbcDateFormat

Used in Content Server version 6.x to provide backward compatibility for importation of Content Server 7.x archives.

Content Server 7.x includes a millisecond data format that was not present in earlier versions. When the 6.x Archiver attempts to import the 7.x archives, the millisecond field causes an error.

Usage

- Section 2.1, "Archiver"

Example

To add this entry to the 6.x config.cfg file:

1. Copy the 6.x config.cfg file to another name (to save it as a backup).

2. Edit the config.cfg file in a text editor, adding the following setting:

OdbcDateFormat='{ts' "yyyy-MM-dd HH:mm:ss{.SSS}"'}'

3. Restart the Content Server instance.

OpenOfficeListenerPort

Defines the socket port for the OpenOffice listener.

This setting is used by PDF Converter's OpenOffice connection string:

uno:socket,host=<OpenOfficeListenerURL>, port=<OpenOfficeListenerPort>;urp;StarOffice.ServiceManager

Default is 8100.

Usage

- Section 2.8.2.4, "Other Formats"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

OpenOfficeListenerPort=8110

See Also

- OpenOfficeListenerURL

OpenOfficeListenerURL

Defines the URL (socket hostname) for the OpenOffice listener.

This setting is used by PDF Converter's OpenOffice connection string:

uno:socket,host=<OpenOfficeListenerURL>,port=<OpenOfficeListenerPort>;urp; StarOffice.ServiceManager

Default is localhost.

Usage

- Section 2.8.2.4, "Other Formats"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

OpenOfficeListenerURL=/mycomputer/localhost

See Also

- OpenOfficeListenerPort

OpenOfficePath

Defines the path for the OpenOffice listener.

If PDF Converter cannot connect to the OpenOffice connection, it attempts to open the listener defined by this path.

Default is an empty string.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

OpenOfficePath=C:\Program Files\Open Office.org.1.0.1\program\quickstart.exe

PageMakerExePath

Defines the path for the Adobe PageMaker executable file.

Returns the path as a string.

Default is an empty string.

Usage

- Section 2.8.2.4, "Other Formats"

Location

- Shared Inbound Refinery Configuration screen, Paths tab, PageMaker Executable File Path

- IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

PageMakerExePath=c:/Program Files/Adobe/PageMaker 6.5/pagemaker.exe

PLUGIN_DEBUG

Enables logging of events that occur inside the web server plug-in filters.

When set to TRUE, events that occur inside any plugins that understand this flag will be recorded in the following log file:

- Apache: IntradocDir/data/users/authfilter.log

When changing this setting on Apache on the Content Server instance, only the Content Server instance must be restarted.

Default is FALSE.

Usage

- Section 2.11, "Debugging"

- Section 2.27, "Web Server"

Location

IntradocDir/data/users/SystemFilters.hda

Example

Used as a configuration entry:

PLUGIN_DEBUG=true

PostConversionTimeOut

Defines the default post-conversion timeout.

Returns the post-conversion timeout values.

This variable must be followed by one of these flags.

Flag

Description

#factor

This value is multiplied by the file size to determine the amount of time allowed for post-conversion processing. (The resulting time is limited by the #max and #min flags.) The default value is 1. Increase this value for busy or slow systems.

#max

Specifies the maximum time in seconds that Inbound Refinery waits for any post-conversion processes to complete. The default time is 10 seconds.

#min

Specifies the minimum time in seconds that Inbound Refinery waits for any post-conversion processes to complete. The default time is 1 second.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

- Shared Inbound Refinery Configuration screen, Timeout Values tab, Post PDF Production Timeout

- IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

PostConversionTimeOut#factor=1

PostprocessPDFPath

Defines the path to an executable that is used to process PDF files after conversion.

The PDF file path is the only command line parameter.

The specified file must be a Win32 executable.

This process is invoked after the conversion to PDF and before the optimization of the PDF. Because this process is invoked once for each file that is processed by Inbound Refinery, it could also be used for other events that might need to be synchronized to the conversion of a file. If the value is not empty, Inbound Refinery will attempt to run the process.

Default is an empty string.

Usage

- Section 2.8.2.1, "General Variables"

Location

- Local Inbound Refinery Configuration screen, General tab, Post PDF Production Path

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

PostprocessPDFPath=c:/domain/IdcRefinery/ConversionProcess/IDCWaterPost.exe

PostscriptPrinterName

Specifies the name of the printer that is used to convert files to PostScript.

This must be the name of a valid PostScript printer.

Default is IDC PDF Converter.

Usage

- Section 2.8.2.1, "General Variables"

Location

IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

PostscriptPrinterName=Acrobat Distiller

PowerPointPrintOutput

Defines how Microsoft PowerPoint content items are converted.

When set to slide, each page of the PDF file contains one slide.

When set to notes, each page of the PDF file contains a slide with its notes.

When set to handout, each page of the PDF file contains six slides.

Default is slide.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Convert in PowerPoint format options

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

PowerPointPrintOutput=notes

See Also

- ProcessPowerpointHyperlinks

PreconversionPath

Defines the path to an executable that is used to process files before conversion.

The specified file must be a Win32 executable.

Default is an empty string.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

- Local Inbound Refinery Configuration screen, Legacy Conversions tab, Preconversion Path

- DomainHome/urm/ibr/connections/main/intradoc.cfg

Example

Used as a configuration entry:

PreconversionPath=c:/out/preconversion.bat

PreconversionWaitTime

Defines the preconversion timeout.

Returns the preconversion timeout value.

This variable must be followed by one of these flags.

Flag

Description

#factor

This value is multiplied by the file size to determine the amount of time allowed for preconversion processes. (The resulting time is limited by the #max and #min flags.) The default value is 1. Increase this value for busy or slow systems.

#max

Specifies the maximum time in seconds that Inbound Refinery waits for the preconversion process to complete. The default time is 10 seconds.

#min

Specifies the minimum time in seconds that Inbound Refinery waits for the preconversion process to complete. The default time is 1 second.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

- Local Inbound Refinery Configuration screen, Legacy Conversions tab, Pre-Converter Timeout

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

PreconversionWaitTime#max=60

PreviewOutputExtension

Defines the file extension output from Content Publisher that is to be used in HTML Preview.

Default is HCSP.

Usage

- Section 2.15, "HTML Preview"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

PreviewOutputExtension=jsp

PreviewPath

Defines the path for HTML Preview executable.

The tcpreview.exe file resides in the Content Publisher installation directory.

Usage

- Section 2.15, "HTML Preview"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

PreviewPath=C:/Program Files/Oracle Content Publisher/tcpreview.exe

PrimaryWorkQueueTimeout

Sets the number of seconds until workflow and subscription notification emails are sent.

Set this to a lower number if you do not want emails to be delayed or if you want immediate response during debugging. Note that a small number could use a large amount of resources.

Content Server has an email message buffer of 20000 bytes. If a large number of subscription notification emails are triggered in a short period of time (for example, 40 content items with 40 subscribers each), the buffer can become overloaded and the notification emails will not be sent. The following Content Server error message indicates that the buffer was overloaded: Work queue error: Error while collating work queue (Message to append to queue 'CollatedWorkQueue' was too large.)

The limit to the total size of a subscription notification email sent is 1 GB. The total number of subscription notification emails that can be included in one email sent to n users is 1 GB divided by the size of the subscription notification email.

Default is 600 (10 minutes).

Usage

- Section 2.7, "Content Server"

- Section 2.28, "Workflow"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

PrimaryWorkQueueTimeout=30

PrinterPortPath

Defines the location of the PostScript file created by Inbound Refinery.

This setting must match the port setting of the printer used by Inbound Refinery.

Default is c:/temp/idcoutput.ps.

Usage

- Section 2.8.2.1, "General Variables"

Location

IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

PrinterPortPath=c:/temp/idcrefinery/idcoutput.ps

See Also

- PostscriptPrinterName

Priority

Specifies the order in which LDAP providers will be checked for the user credentials.

This variable is used only when a user has not previously logged into the Content Server instance. If the user has previously requested credentials, the SourcePath will be stored for that user, so the LDAP provider specified by the Source Path will be used.

Each LDAP provider in the Content Server instance must have a unique Priority number.

Default is 1.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, Priority

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

Priority=2

See Also

- SourcePath

- IsPrimaryUserBase

ProcessExcelUrlHyperlinks

Enables the processing of URL hyperlinks in Microsoft Excel content items.

- When set to TRUE, URL hyperlinks in Excel files are processed.

- When set to FALSE, URL hyperlinks in Excel files are not processed.

Default is FALSE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process Excel URL links

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessExcelUrlHyperlinks=true

ProcessInDesignBookMarks

Enables the conversion of internal document links in Adobe InDesign content items.

- When set to TRUE, internal document links in Adobe InDesign files are processed.

- When set to FALSE, internal document links in Adobe InDesign files are not processed.

Default is TRUE.

Usage

- Section 2.8.2.3, "InDesign"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessInDesignBookmarks=false

See Also

- ProcessInDesignHyperlinks

- ProcessInDesignInternalPDFThumbnail

- ProcessInDesignLinkUpdate

- ProcessInDesignPDFCompatibility50

ProcessInDesignHyperlinks

Enables the conversion of URL links in Adobe InDesign content items.

- When set to TRUE, URL links in Adobe InDesign files are processed.

- When set to FALSE, URL links in Adobe InDesign files are not processed.

Default is TRUE.

Usage

- Section 2.8.2.3, "InDesign"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessInDesignHyperlinks=false

See Also

- ProcessInDesignBookMarks

- ProcessInDesignInternalPDFThumbnail

- ProcessInDesignLinkUpdate

- ProcessInDesignPDFCompatibility50

ProcessInDesignInternalPDFThumbnail

Enables the creation of PDF page thumbnails when converting Adobe InDesign content items.

- When set to TRUE, the PDF file will include page thumbnails.

- When set to FALSE, the PDF file will not include page thumbnails.

This setting does not affect the creation of thumbnails on search results pages.

Default is TRUE.

Usage

- Section 2.8.2.3, "InDesign"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessInDesignInternalPDFThumbnail=false

See Also

- ProcessInDesignBookMarks

- ProcessInDesignHyperlinks

- ProcessInDesignLinkUpdate

- ProcessInDesignPDFCompatibility50

ProcessInDesignLinkUpdate

Enables an update of all links in Adobe InDesign content items before conversion.

- When set to TRUE, links in Adobe InDesign files are updated before conversion. If linked objects are not available, the conversion will fail.

- When set to FALSE, links in Adobe InDesign files are not updated before conversion.

Default is FALSE.

Usage

- Section 2.8.2, "PDF Converter"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessInDesignLinkUpdate=true

See Also

- ProcessInDesignBookMarks

- ProcessInDesignHyperlinks

- ProcessInDesignInternalPDFThumbnail

- ProcessInDesignPDFCompatibility50

ProcessInDesignPDFCompatibility50

Sets the version of the PDF files that PDF Converter produces from Adobe InDesign content items.

- When set to TRUE, PDF Converter produces PDF version 1.4 (Acrobat 5.0 compatible) files from Adobe InDesign files.

- When set to FALSE, PDF Converter produces PDF version 1.3 (Acrobat 4.0 compatible) files from Adobe InDesign files.

Default is FALSE.

Usage

- Section 2.8.2.3, "InDesign"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessInDesignPDFCompatibility50=true

ProcessPowerpointHyperlinks

Enables the processing of hyperlinks in Microsoft PowerPoint content items.

- When set to TRUE and the PowerPointPrintOutput setting is set to SLIDE, the following hyperlinks in PowerPoint files are processed:

- URL links

- Next slide

- Previous slide

- When set to FALSE, hyperlinks in PowerPoint files are not processed.

If the PowerPointPrintOutput setting is set to NOTES or HANDOUT, hyperlinks in PowerPoint files are not processed.

Default is FALSE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process PowerPoint Hyperlinks

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessPowerpointHyperlinks=true

See Also

- PowerPointPrintOutput

ProcessVisioInternalHyperlinks

Enables the conversion of internal hyperlinks in Microsoft Visio content items.

- When set to TRUE, internal hyperlinks in Visio files are processed.

- When set to FALSE, internal hyperlinks in Visio files are not processed.

Default is FALSE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process internal Visio links

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessVisioInternalHyperlinks=true

See Also

- ProcessVisioUrlHyperlinks

ProcessVisioUrlHyperlinks

Enables the conversion of URL links in Microsoft Visio content items.

- When set to TRUE, URL links in Visio files are processed.

- When set to FALSE, URL links in Visio files are not processed.

Default is FALSE.

Usage

- Section 2.8.2.3, "InDesign"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process Visio URL links

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessVisioUrlHyperlinks=true

See Also

- ProcessVisioInternalHyperlinks

ProcessWordBookMarks

Enables the conversion of page reference bookmarks in Microsoft Word content items.

- When set to TRUE, page reference bookmarks in Microsoft Word files are converted to PDF bookmarks. (All other types of bookmarks are ignored.)

- When set to FALSE, bookmarks in Microsoft Word files are not processed.

Default is TRUE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process document bookmarks

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessWordBookMarks=false

See Also

- ProcessWordHyperlinks

ProcessWordComments

Enables the conversion of comments in Microsoft Word content items to PDF notes.

- When set to TRUE, comments in Microsoft Word files are converted to PDF notes.

- When set to FALSE, comments in Microsoft Word files are not processed.

Default is FALSE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process document comments to PDF notes

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessWordComments=true

See Also

- ProcessWordHyperlinks

ProcessWordEmailLinks

Enables the conversion of email hyperlinks in Microsoft Word content items.

- The ProcessWordUrlHyperlinks setting must be TRUE for this setting to be valid.

- When set to TRUE, email hyperlinks in Microsoft Word files are processed.

- When set to FALSE, email hyperlinks in Microsoft Word files are not processed.

Default is FALSE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process mailto links

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessWordEmailLinks=true

See Also

- ProcessWordHyperlinks

- ProcessWordUrlHyperlinks

ProcessWordFootEndNote

Enables the conversion of footnotes and endnotes in Microsoft Word content items to hyperlinks.

- When set to TRUE, footnotes and endnotes in Microsoft Word files are converted to hyperlinks.

- When set to FALSE, footnotes and endnotes in Microsoft Word files are not processed.

Default is FALSE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process document links to footnotes and endnotes

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessWordFootEndNote=true

See Also

- ProcessWordHyperlinks

ProcessWordHeadings

Enables the conversion of standard headings in Microsoft Word content items to PDF bookmarks.

- When set to TRUE, standard heading paragraph styles (Heading 1 through Heading 9 and any custom styles based on these standard styles) in Microsoft Word files are converted to PDF bookmarks.

- If a table of contents has already been processed using the ProcessWordToc setting, then this setting is ignored and headings will not be converted to bookmarks.

- When set to FALSE, heading styles in Microsoft Word files are not processed.

Default is TRUE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process heading styles to PDF bookmarks

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessWordHeadings=false

See Also

- ProcessWordHyperlinks

- ProcessWordToc

ProcessWordHyperlinks

Enables the conversion of hyperlinks in Microsoft Word content items.

- When set to TRUE, all types of hyperlinks in Microsoft Word files are processed.

- When set to FALSE, hyperlinks in Microsoft Word files are not processed.

Default is TRUE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessWordHyperlinks=true

See Also

- ProcessWordBookMarks

- ProcessWordComments

- ProcessWordEmailLinks

- ProcessWordFootEndNote

- ProcessWordHeadings

- ProcessWordToc

- ProcessWordUrlHyperlinks

ProcessWordToc

Enables the conversion of tables of contents in Microsoft Word content items to PDF bookmarks.

- When set to TRUE, tables of contents entries that are automatically generated in Microsoft Word files are converted to PDF bookmarks.

- When set to FALSE, tables of contents in Microsoft Word files are not processed. (However, if the table of contents entries have hyperlinks, they will be processed according to the ProcessWordUrlHyperlinks setting.)

Default is FALSE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process Table of Contents to PDF bookmarks

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessWordToc=true

See Also

- ProcessWordHyperlinks

- ProcessWordUrlHyperlinks

- ProcessWordHeadings

ProcessWordUrlHyperlinks

Enables the conversion of URL hyperlinks in Microsoft Word content items.

- When set to TRUE, URL hyperlinks in Microsoft Word files are processed.

- When set to FALSE, URL hyperlinks in Microsoft Word files are not processed.

Default is TRUE.

Usage

- Section 2.8.2.2, "Microsoft Office"

Location

- Local Inbound Refinery Configuration screen, Native Options tab, Process URL links

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

ProcessWordUrlHyperlinks=false

See Also

- ProcessWordHyperlinks

ProviderClass

Specifies the name of a Java class that implements the provider.

The default depends on the type of provider:

Provider Type

Default Value

Outgoing

intradoc.provider.SocketOutgoingProvider

Database

intradoc.jdbc.JdbcWorkspace

Incoming

intradoc.provider.SocketIncomingProvider

Preview

intradoc.provider.SocketOutgoingProvider

Ldapuser

intradoc.provider.LdapUserProvider

Usage

- Section 2.7, "Content Server"

- Section 2.24.2, "External Security"

Location

- Add/Edit Provider pages, Provider Class

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

ProviderConnection=intradoc.provider.SocketOutgoingProvider

ProviderConfig

Specifies the name of a Java class that performs some extra configuration for a provider.

This setting is most useful for database providers, where the connection classes are already providers.

There is no default.

Usage

- Section 2.7, "Content Server"

- Section 2.24.2, "External Security"

Location

- Add/Edit Provider pages, Configuration Class

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

ProviderConfig=intradoc.provider.CustomClass

ProviderConnection

Specifies the name of a Java class that implements the provider connection.

The default depends on the type of provider:

Provider Type

Default Value

Outgoing

intradoc.provider.SocketOutgoingConnection

Database

intradoc.jdbc.JdbcConnection

Incoming

intradoc.provider.SocketIncomingConnection

Preview

intradoc.provider.SocketOutgoingConnection

Ldapuser

intradoc.provider.LdapConnection

Usage

- Section 2.7, "Content Server"

- Section 2.24.2, "External Security"

Location

- Add/Edit Provider pages, Connection Class

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

ProviderConnection=intradoc.provider.SocketOutgoingConnection

ProviderCredentialsMap

Specifies the name of a Credentials Map for use with JpsUserProvider.

There is no default.

Usage

- Section 2.7, "Content Server"

- Section 2.24.2, "External Security"

Location

- IntradocDir/data/providers/jpsuserprovider/provider.hda

Example

Used as a configuration entry. Add the line before the @end line in the file. The last lines of the file should look similar to:

SourcePath=jpsuser
ProviderClass=idc.provider.jps.JpsUserProvider
ProviderCredentialsMap=name_of_map
@end

ProviderDir

Defines the path to the providers/ directory.

Default is DomainHome/ucm/cs/data/providers/.

Usage

- Section 2.12, "Directories and Paths"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

ProviderDir=c:/domain/data/providers

ProviderType

Specifies the type of provider.

The following provider types are available:

Provider Type

Value

Outgoing

outgoing

Database

database

Incoming

incoming

Preview

preview

Ldapuser

ldapuser

Usage

- Section 2.7, "Content Server"

- Section 2.24.2, "External Security"

Location

IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

ProviderType=ldapuser

pucDefaultTime

Specifies how the time is entered into the date/time fields when using the pop-up calendar. If this option is not set, the time defaults to midnight of the selected date.

This is a string value which can be set in the following ways:

- current: sets the time equivalent to the client computer's clock.

- any time, expressed in the system locale format. Missing values are interpreted as a zero. Missing AM/PM designations are interpreted as using 24-hour format. For example, 1:15 PM, 01:15 PM, and 13:15 are interpreted the same within a system locale that designates AM and PM.

Usage

- Section 2.20, "Pop-Up Calendar"

Location

IntradocDir/config/config.cfg

Example

pucDefaultTime=current

pucEnableOnSearch

If set to TRUE, specifies if the pop-up calendar is available on a search page. If set to FALSE, disables the pop-up calendar on the search page.

The default is TRUE.

Usage

- Section 2.20, "Pop-Up Calendar"

Location

IntradocDir/config/config.cfg

Example

pucEnableOnSearch=false

pucHideTimeInDateFields

Specifies if date fields display only the date or the date and time.

- If set to TRUE, disables the display of the time in a date field and forces the Content Server instance to parse the check-in time as midnight of the selected date, regardless of how pucDefaultTime is set.

- If set to false, displays the time in a date field.

The default is FALSE.

Usage

- Section 2.20, "Pop-Up Calendar"

Location

IntradocDir/config/config.cfg

Example

pucHideTimeInDateFields=true

See Also

- pucDefaultTime

pucUseMonthLocale

Determines how the month names are displayed in the pop-up calendar.

This is a string value which can be set in the following ways:

- short: truncates the month name based on user locale. For example, January is truncated to Jan, February to Feb, and so on.

- long: displays the full month name based on user locale.

Default is long.

Usage

- Section 2.20, "Pop-Up Calendar"

Example

pucUseMonthLocale=short

See Also

- pucUseWeekdayLocale

pucUseWeekdayLocale

Determines how the day names are displayed in the pop-up calendar.

This is a string value which can be set in the following ways:

- 1char: uses the first letter of the day. Note that this starts with the numeral '1', not a lower-case 'L'.

- short: uses two characters to represent the day name.

- medium: uses the standard three-character day names

- long: displays the full name based on user locale.

Default is long.

Usage

- Section 2.20, "Pop-Up Calendar"

Example

pucUseWeekdayLocale=short

See Also

- pucUseMonthLocale

pucXOffset

Specifies the horizontal location of the pop-up calendar on the page in pixels, relative to the default position. This is a value set as an integer. The default is 0.

Usage

- Section 2.20, "Pop-Up Calendar"

Example

pucXOffset=10

See Also

- pucYOffset

pucYOffset

Specifies the vertical location of the pop-up calendar on the page in pixels, relative to the default position. This is a value set as an integer. The default is 0.

Usage

- Section 2.20, "Pop-Up Calendar"

Example

pucYOffset=10

See Also

- pucXOffset

pucZIndex

Specifies the z-ordering object position of the pop-up calendar layer. The larger the number, the higher the placement within the page layer positions. Use a positive number greater than any other z-index style attribute specified on the page to ensure the calendar is displayed over other elements.

This is specified as an integer value. Default is 0.

Usage

- Section 2.20, "Pop-Up Calendar"

Example

pucZIndex=10

QueueDir

Defines the path to the working directory for the Inbound Refinery queue.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

QueueDir=x:/domain_refinery/

RecordsManagementDenyAuthorFreePassOnRMSecurity

When a content item is placed in an ACL-restricted Contribution Folder (RW recordsmanager alias), users have only RW access, except for the author who can delete the item. Setting this configuration variable to true disallows deletion of the item by the author, restricting the author to only RW access.

- If set to TRUE, authors are not allowed to delete content they authored.

- If set to FALSE, authors are allowed to delete content they authored.

The default is FALSE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RecordsManagementDenyAuthorFreePassOnRMSecurity=true

RecordsManagementNumberOverwriteOnDelete

Sets the number of disk scrubbing passes used for a destroy action.

The default is 2.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RecordsManagementNumberOverwriteOnDelete=4

RedirectHostsFilter

Used to indicate a filter of allowed redirect hosts. The current host is added to this filter by default.

Use a pipe character | to separate multiple addresses. Make sure there are no spaces on either side of the pipe.

Use wildcards to indicate groups of addresses (* for zero or more characters, ? for a single character).

Default is the URL of the local host.

Usage

- Section 2.24.2, "External Security"

- Section 2.27, "Web Server"

Location

- System Properties, Server tab, IP Address Filter

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

RedirectHostsFilter=*.google.com|www.cnn.com

RequestAuditAdditionalVerboseFieldsList

Used with verbose tracing when the Request Audit trace is activated.

The Request Audit trace appears on the System Audit Information page. This trace creates two separate summaries calculated over two different time intervals. The trace calculates the number of service requests and length of time to perform the requests. After a summary is reported for the specified interval the values are reset and the cumulative totals and averages are computed again for the next interval period.

This configuration variable is a comma-delimited list of additional fields to display when reporting information about the request.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

RequestAuditAdditionalVerboseFieldsList=xComment,dDocType

See Also

- RequestAuditIntervalSeconds1

- RequestAuditIntervalSeconds2

- RequestAuditListDepth1

- RequestAuditListDepth2

- RequestAuditSubClassificationField

RequestAuditIntervalSeconds1

Used to specify the short audit interval for the Request Audit trace.

The Request Audit trace appears on the System Audit Information page. This trace creates two separate summaries calculated over two different time intervals. The trace calculates the number of service requests and length of time to perform the requests. After a summary is reported for the specified interval the values are reset and the cumulative totals and averages are computed again for the next interval period.

Specify the value in seconds.

The default value is 120 seconds (2 minutes).

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

RequestAuditIntervalSeconds1=240

See Also

- RequestAuditAdditionalVerboseFieldsList

- RequestAuditIntervalSeconds2

- RequestAuditListDepth1

- RequestAuditListDepth2

- RequestAuditSubClassificationField

RequestAuditIntervalSeconds2

Used to specify the long audit interval for the Request Audit trace.

The Request Audit trace appears on the System Audit Information page. This trace creates two separate summaries calculated over two different time intervals. The trace calculates the number of service requests and length of time to perform the requests. After a summary is reported for the specified interval period the values are reset and the cumulative totals and averages are computed again for the next interval period.

Specify the value in seconds.

The default value is 3600 seconds (1 hour).

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

RequestAuditIntervalSeconds2=7200

See Also

- RequestAuditAdditionalVerboseFieldsList

- RequestAuditIntervalSeconds1

- RequestAuditListDepth1

- RequestAuditListDepth2

- RequestAuditSubClassificationField

RequestAuditListDepth1

Used to specify the number of services to present in the Request Audit trace.

This configuration value applies only to the short audit period.

The Request Audit trace appears on the System Audit Information page. This trace creates two separate summaries calculated over two different time intervals. The trace calculates the number of service requests and length of time to perform the requests.

This variable is used to specify the number of services to present from a sorted list of requests. The list is sorted in descending order by elapsed time consumed.

The default value is 5.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

RequestAuditListDepth1=7

See Also

- RequestAuditAdditionalVerboseFieldsList

- RequestAuditIntervalSeconds1

- RequestAuditIntervalSeconds2

- RequestAuditListDepth2

- RequestAuditSubClassificationField

RequestAuditListDepth2

Used to specify the number of services to present in the Request Audit trace.

This configuration value applies only to the long audit period.

The Request Audit trace appears on the System Audit Information page. This trace creates two separate summaries calculated over two different time intervals. The trace calculates the number of requests and length of time to perform the requests.

This variable is used to specify the number of services to present. The list is sorted in descending order by elapsed time consumed.

The default value is 20.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

RequestAuditListDepth2=25

See Also

- RequestAuditAdditionalVerboseFieldsList

- RequestAuditIntervalSeconds1

- RequestAuditIntervalSeconds2

- RequestAuditListDepth1

- RequestAuditSubClassificationField

RequestAuditSubClassificationField

Used to specify an internal field, usually a metadata field for documents, whose value is appended to the service name in order to differentiate the name in the Request Audit list.

The Request Audit trace appears on the System Audit Information page. This trace creates two separate summaries calculated over two different time intervals. The trace calculates the number of service requests and length of time to perform the requests.

In some cases, the service name does not create an adequate breakdown of the different types of requests. This entry helps to differentiate the types of entries.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

RequestAuditSubClassificationField=xDepartment

See Also

- RequestAuditAdditionalVerboseFieldsList

- RequestAuditIntervalSeconds1

- RequestAuditIntervalSeconds2

- RequestAuditListDepth1

- RequestAuditListDepth2

ResultsTitle

Defines a title for the search results page.

This variable is used by the Web Layout Editor to name the search results page and display a heading at the top of that page.

Usage

- Section 2.19, "Page Display"

- Section 2.23, "Searching"

Output

Returns the page title as a string.

Example

As an HDA entry, names the search results page:

@Properties LocalData
ResultsTitle=Content Items
@end

As a script, returns the defined name:

<$if ResultsTitle$>ResultsTitle=<$url(ResultsTitle)$>

RmaAddDocWhereClauseForScreening

Allows users with the Oracle WebCenter Content: Records Administrator role to screen for frozen items to which they do not have access (through ACLs) on the screening page or the Freeze Information Page.

- If set to FALSE, frozen items can be screened.

- If set to TRUE, frozen items cannot be screened.

The default is FALSE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RmaAddDocWhereClauseForScreening=true

RmaAllowKeepOrDestroyMetadataOption

This variable enables the option to keep or destroy metadata when using the following disposition actions: Delete All Revisions, Accession, Archive, Move, and Transfer.

- If set to TRUE, enables the use of the keep/destroy option.

- If set to FALSE, disables the use of this option.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RmaAllowKeepOrDestroyMetadataOption=true

RmaEnableFilePlan

This variable enables File Plan Contribution Folder structure functionality.

- If set to FALSE, disables the Contribution Folder structure used with MoReq2 (Model Requirements for the Management of Electronic Records) file plans.

- If set to TRUE, enables Contribution Folder structure for use with MoReq2 file plans.

The default is FALSE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RmaEnableFilePlan=true

RmaEnableFixedClones

This variable enables the fixed clone functionality, which allows the creation of record clones of content revisions.

- If set to FALSE, enables fixed clone functionality.

- If set to TRUE, disables fixed clone functionality.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RmaEnableFixedClones=false

RmaEnablePostFilterOnScreening

This variable enables additional security on screening results. If a user does not have appropriate security for an item in a screening result list, that item is hidden from view.

- If set to TRUE, enables filtering on screening results.

- If set to FALSE, disables additional security on screening results.

The default is TRUE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RmaEnablePostFilterOnScreening=false

RmaFilePlanVolumePrefix and RmaFilePlanVolumeSuffix

These variables are used to define the naming convention for volumes. The usual convention is prefix+timestamp+suffix. Use these variables to define the prefix and suffix. If neither is defined, a prefix of volume_ is used by default.

- RmaFilePlanVolumePrefix=value: Sets the prefix used to value.

- RmaFilePlanVolumeSuffix=value: Sets the suffix used to value.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

RmaFixedClonesTitleSuffix

This variable sets the suffix that is automatically appended to a fixed clone content item.

Default: RmaFixedClonesTitleSuffix=fixed_clone

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

RMAHideExternalFieldsFromCheckInUpdate

Use this variable to hide external fields on the Checkin and Update pages.

- If set to TRUE, hides external fields on the Checkin and Update pages.

- If set to FALSE, displays external fields on the Checkin and Update pages.

The default is TRUE.

Restart WebCenter Content for this variable to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RMAHideExternalFieldsFromCheckInUpdate=false

RMAHideExternalFieldsFromSearchInfo

Specifies whether to hide external fields on the Search and Content Information pages. The default is TRUE.

- If set to TRUE, hides external fields on the Search and Content Information pages.

- If set to FALSE, displays external fields on the Search and Content Information pages.

The default is TRUE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RMAHideExternalFieldsFromSearchInfo=false

RmaNotifyDispReviewerAndCatAuthor

Controls who is notified when events are triggered by a disposition rule.

- If set to TRUE, both the specified notification reviewer and the original category author receive email notifications of the event.

- If set to FALSE, only the category author receives email.

The default is TRUE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RmaNotifyDispReviewerAndCatAuthor=false

RmaNotifyReviewerAndAlternateReviewer

Controls if an alternate user can perform review actions and process assigned disposition events.

- If set to TRUE, both the original user and the alternative reviewer receive email notifications about the action.

- If set to FALSE, only the alternative reviewer receives email.

The default is TRUE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

RmaNotifyReviewerAndAlternateReviewer=false

rule:IsFragmentOnly

Specifies that a particular forced conversion rule creates a fragment in Dynamic Converter.

Fragments are pieces of content that will be included in another content item. Fragments generally do not include <HTML> or <BODY> tags, and are not intended to be viewed by themselves.

When this variable is set to 1, the specified forced conversion rule converts files to fragments.

The specified forced conversion rule must be included in the ForcedConversionRules setting.

There is no default.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Specifies that the RuleA forced conversion rule converts files to fragments:

RuleA:IsFragmentOnly=1
ForcedConversionRules=RuleA

See Also

- ForcedConversionRules

SceUseNativeInDataFeeds

The SESCrawlerExport component generates RSS feeds from its internal indexer. SceUseNativeInDataFeeds enables the SESCrawlerExport component to select a web viewable file or a native file for indexing.

- If set to TRUE, the native file is indexed in the RSS feeds.

- If set to FALSE, the web viewable file is indexed in the RSS feeds.

The default is FALSE.

Usage

- Section 2.7, "Content Server"

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Specifies that a native file is indexed in the RSS feeds:

SceUseNativeInDataFeeds=true

SchemaAllowRecursiveFileMove

If set to TRUE, enables the ability to move files on UNIX systems on an individual basis from a schema publishing location into the production location. This allows swapping of the schema directory into its production directory.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

SchemaAllowRecursiveFileMove=true

SchemaBuildDigestFile

If set to TRUE, builds a file containing digests of all the files published. Setting this to TRUE increases the time required to publish schema.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

SchemaBuildDigestFile=true

See Also

- SchemaPublishCheckInterval

SchemaPublishCheckInterval

Establishes the interval between checks for non-subject-driven schema publishing requests.

This is triggered if the IntradocDir/data/schema/publishlock/publish.dat file is accessed.

Specify the value in seconds.

Default is 120 seconds (two minutes).

Change this setting if there is an external program that modifies data in schema-managed tables and which accesses the file IntradocDir/data/schema/publishlock/publish.dat.

On a development server, use a low value to ensure prompt publishing (for example, SchemaPublishCheckInterval=2).

Lowering the default value on a production server may cause performance problems.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

To set this interval for 10 minutes, use the following:

SchemaPublishCheckInterval=600

SchemaPublishInterval

The interval between unprovoked schema operations (that is, operations that are not caused by an event).

Specify this value in seconds.

Default is 14400 (four hours).

SchemaPublisher will usually publish at least once during this interval.

On a development server, use a low value to ensure prompt publishing (for example, SchemaPublishInterval=30).

Lowering the default value on a production server may cause performance problems.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

To set this interval to one week, use the following:

SchemaPublishInterval=604800

SchemaPublishMaximumInterval

The maximum amount of time between automatic schema publishing cycles.

Specify this value in seconds.

Default is 86400 (one day).

On a development server, set a low value to ensure prompt publishing (for example, SchemaPublishMaximumInterval=30).

Lowering the default value on a production server may cause performance problems.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

To specify this value as four hours, use the following:

SchemaPublishMaximumInterval=14400

SchemaPublishMinimumInterval

The minimum amount of time between automatic schema publishing cycles.

Specify this value in seconds.

Default is four seconds.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

SchemaPublishMinimumInterval=8

SchemaPublishRenameRetryInitialInterval

Specifies the delay before retrying a rename operation.

The rename operation involves renaming of the schema directory to schema.old or the schema.work directory to schema.

After a failed retry, the delay value is doubled.

If SchemaPublishRenameRetryIterations is reached, the publishing operation fails.

Specify the value in milliseconds.

The default value is 100 milliseconds.

This affects behavior on Windows systems only.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

SchemaPublishRenameRetryInitialInterval=50

See Also

- SchemaPublishRenameRetryIterations

SchemaPublishRenameRetryIterations

Specifies the number of times a rename operation will be tried.

This affects operations on Windows systems only.

The operation involves renaming of the schema directory to schema.old or the schema.work directory to schema.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

SchemaPublishRenameRetryIterations=6

See Also

- SchemaPublishRenameRetryInitialInterval

SchemaPublishRetryInterval

Specifies the delay introduced after SchemaPublisher fails to publish the schema.

This delay prevents the SchemaPublisher from continually starting and failing.

After a failed retry, this value is doubled but is never larger than the value of SchemaPublishRetryIntervalMax.

When publishing succeeds, the value is reset to the original value

Default value is three seconds.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

SchemaPublishRetryInterval=4

See Also

- SchemaPublishRetryIntervalMax

SchemaPublishRetryIntervalMax

Specifies the longest length of time for SchemaPublishRetryInterval.

Specify this value in seconds.

Default value is 300 (five minutes).

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

SchemaPublishRetryIntervalMax=120

See Also

- SchemaPublishRetryInterval

SchemaVerifyPublishing

If set to TRUE, digests will be used to verify the files that SchemaPublisher creates before doing the final renaming.

Setting SchemaVerifyPublishing=TRUE will increase the time required to publish schema.

This should be set to TRUE on a production server.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

SchemaVerifyPublishing=true

See Also

- SchemaBuildDigestFile

- SchemaPublishCheckInterval

SchemaWin32RenameDelayInterval

Specifies the size of the delay prior to closing a file before attempting to rename it.

This affects behavior only on Windows systems.

Tune this number as low as possible.

Value should be specified in milliseconds.

The default value is 10 milliseconds.

Usage

- Section 2.22, "Schema"

Location

IntradocDir/config/config.cfg

Example

SchemaWin32RenameDelayInterval=4

SctAutoTruncateDataStrings

Specifies that the reduction process truncates data strings to fit into the corresponding table column for Content Tracker.

The default is FALSE.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctAutoTruncateDataStrings=true

SctComponentDir

Specifies the path to the directory where Content Tracker is installed.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctComponentDir=DomainHome/ucm/cs/data/contenttracker/

SctDebugLogEnabled

Specifies use of Java code execution trace for Content Tracker.

If set to TRUE, enables Java code execution trace for Content Tracker. Used with SctDebugLogFilePath.

The default is FALSE.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctDebugLogEnabled=true

See Also

SctDebugLogFilePath

SctDebugLogFilePath

Specifies the directory for Java code execution trace for Content Tracker. Used with SctDebugLogEnabled.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

DomainHome/ucm/cs/data/contenttracker/log/SCT_DEBUG_TRACE.log

See Also

SctDebugLogEnabled

SctDebugServiceBinderDumpEnabled

Controls if the Content Tracker service handler filter writes out the service DataBinder objects into dump files. These files can be used as diagnostic tools when developing field map sets for extended service logging.

- If set to FALSE, prevents the Content Tracker service handler filter from writing out the DataBinder objects into dump files.

- If set to TRUE, configures the Content Tracker service handler filter to write out the DataBinder objects into dump files. Use the dump files to view what data is available at the time the particular service events are recorded.

The default is FALSE.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctDebugServiceBinderDumpEnabled=true

SctDoNotArchive

Specifies performance optimization for Content Tracker to function as efficiently as possible for use in high-volume production environments. Content Tracker collects and records only content access event data. This excludes information gathering on non-content access events like searches or the collection and synthesis of user profile summaries.

- If set to TRUE, Content Tracker ensures that the database tables contain only the most current data and expired table rows are discarded rather than archived. This applies to all Content Tracker database tables.
By default, only the SctAccessLog table is populated and expired rows are not archived. However, if both SctTrackContentAccessOnly and SctDoNotArchive are disabled, all tables are populated and their expired data archived.

- If set to FALSE, Content Tracker database tables contain all recorded data and expired table rows are not discarded.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctDoNotArchive=true

SctDoNotPopulateAccessLogColumns

Specifies a list of columns that Content Tracker should not populate in the SctAccessLog table. This variable supports performance optimization for Content Tracker to function as efficiently as possible for use in high-volume production environments. Content Tracker collects and records only content access event data. This excludes information gathering on non-content access events like searches or the collection and synthesis of user profile summaries.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctDoNotPopulateAccessLogColumns=SctParentSequence,c_ip,cs_username

SctExternalUserLogEnabled

Specifies whether Content Tracker monitor external user logins and automatically propagate their role and account information to the UserSecurityAttributes table. These authenticated users are qualified based on their user roles and accounts.

Regardless of whether the SctExternalUserLogEnabled configuration variable is enabled or disabled, all the of the content item access information for external users is tracked and recorded. But when this variable is enabled, it ensures that this data is included in reports that explicitly correlate externally authenticated user names with their associated user roles and accounts. Specifically, the Top Content Items by User Role report and the Users by User Role report include all of the content item access activity by external users.

- If set to FALSE, disables replication of external user account and role information to the UserSecurityAttributes table.

- If set to TRUE, enables replications of external user account and role information to the UserSecurityAttributes table.

The default is TRUE.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctExternalUserLogEnabled=true

SctFilterPluginLogDir

Specifies the path to the directory where the filter plugin stores the event logs for Content Tracker.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

DomainHome/ucm/cs/data/contenttracker/data/

SctIgnoreDirectories

Directs the filter plugin to disregard URLs contained within the listed directory node.

The default is DomainHome/ucm/cs/resources/;DomainHome/ucm/cs/common/

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctIgnoreFileTypes

Directs the filter plugin to disregard URLs with the listed file types. The value is a list of comma-delimited file types.

The default is gif,jps,js,css.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctIgnoreFileTypes=gif,jps

SctLogDir

Specifies the path to the directory or directories where Content Tracker looks for raw event logs, such as sctLog. The path can have multiple values, separated by semi-colons. For example, directory1;directory2;...;directoryn

The default is DomainHome/ucm/cs/data/contenttracker/data/

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctLogEnabled

Specifies that service handler filters and web server filter plugin track all events and create event logs. This is the Content Tracker master on/off switch.

- If set to TRUE, the service handler filters and web server filter plugin track all events and create event logs.

- If set to FALSE, the service handler filters and web server filter plugin ignore all events and create no logs.

The default is TRUE.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctLogSecurity

Specifies that the filter plugin record IMMEDIATE_RESPONSE_PAGE events in the sctSecurityLog, and the reduction process to read the event log.

- If set to TRUE, the filter plugin records IMMEDIATE_RESPONSE_PAGE events in the sctSecurityLog, and the reduction process reads the event log.

- If set to FALSE, the filter plugin does not record IMMEDIATE_RESPONSE_PAGE events in the sctSecurityLog, and the reduction process does not read the event log.

The default is TRUE.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctLogSecurity=true

SctMaxRecentCount

Specifies the maximum number of days worth of reduced data kept in the Recent state. Overflow from Recent is moved to the Archive state.

The default is 60.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctMaxRecentCount=3

SctMaxRereadTime

Specifies the maximum number of seconds that can occur between consecutive references by a particular user to a particular content item (for example, a PDF file) and have the adjacent references be considered a single sustained access. Consecutive references that occur further apart in time count as separate accesses.

The default is 3600.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctMaxRereadTime=4200

SctReductionAvailableDatesLookback

Used with SctReductionRequireEventLogs to limit Available Dates range for Content Tracker event logs. Unit equals days. Zero equals unlimited.

The default is 0.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctReductionAvailableDatesLookback=10

SctReductionLogDir

Specifies the path to the directory where the Content Tracker reduction logs are stored.

The default is DomainHome/ucm/cs/data/contenttracker/log/

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctReductionRequireEventLogs

Specifies that Content Tracker performs reduction in association with event logs. Used in Detached configurations.

- If set to TRUE, Content Tracker performs reduction only when event logs are found.

- If set to FALSE, Content Tracker performs reduction even if no event logs are found.

The default is TRUE.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctReductionRequireEventLogs=false

SctrEnableSecurityCheck

Specifies that Content Tracker Reports uses one of two security modes: secure and non-secure. The security checks preference provides the option to employ individual user roles and account information to restrict the visibility of content items information in report results. This option enables you to control what content items (and metadata) that users can see in their generated reports. Ideally, users should not see anything through Content Tracker Reports that they could not find using an Content Server search.

- If set to TRUE, information in any generated report is filtered (made secure) based on the user's role and account privilege.
If Access Control Lists (ACLs) are enabled on your Content Server instance, the secure mode option in Content Tracker Reports does not work. On an ACL-based system, the secure mode must be disabled. In this case, it is possible for users other than a system administrator to see information about content items that they would not otherwise be authorized to access and view.

- If set to FALSE, information in generated reports is the same as what a user would see with a Content Server search.

The default is FALSE.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctrEnableSecurityCheck=true

SctScheduledReductionEnable

Selects which Content Server instance performs data reduction for Content Tracker. Used in multi-JVM configurations.

- If set to TRUE, the owning Content Server instance performs data reduction.

- If set to FALSE, the owning Content Server instance does not perform data reduction.

The default is TRUE.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctScheduledReductionEnable=false

SctSimplifyUserAgents

Specifies performance optimization for Content Tracker to function as efficiently as possible for use in high-volume production environments. Content Tracker collects and records only content access event data. This excludes information gathering on non-content access events like searches or the collection and synthesis of user profile summaries.

- If set to TRUE, Content Tracker minimizes the information that is stored in the cs_userAgent column of the SctAccessLog table.

- If set to FALSE, Content Tracker does not minimize the information that is stored in the cs_userAgent column of the SctAccessLog table.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctSimplifyUserAgents=true

SctSnapshotEnable

Enables Snapshot functions for Content Tracker.

- If set to TRUE, enables Snapshot functions. This is set from the Data Engine Control Center.

- If set to FALSE, disables Snapshot functions.

The default is FALSE.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctSnapshotLastAccessEnable

Enables or disables the Last Access Date Snapshot function for Content Tracker.

- If set to TRUE, enables the Last Access Date Snapshot function. This is set from the Data Engine Control Center.

- If set to FALSE, disables the function.

The default is FALSE.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctSnapshotLastAccessField

Specifies the metadata field name for Last Access Date (xLastAcccessDate) for Content Tracker.

The default is none.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctSnapshotLongCountEnable

Enables or disables the "Long" interval access count Snapshot function for Content Tracker.

- If set to TRUE, enables the Long interval access count Snapshot function. This is set from the Data Engine Control Center.

- If set to FALSE, disables the function.

The default is FALSE.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctSnapshotLongCountField

Specifies the metadata field name for Long Internal Count (xAccessesInLast90Days) for Content Tracker. This field name is set from the Data Engine Control Center.

The default is none.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctSnapshotLongCountInterval

Specifies the number of days for the Long Interval Count (xAccessesInLast90Days) for Content Tracker. This value is set from the Data Engine Control Center.

The default is none.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctSnapshotShortCountEnable

Enables or disables the Short Interval Access Count Snapshot function for Content Tracker. This is set from the Data Engine Control Center.

- If set to TRUE, enables the Short Interval Access Count Snapshot function.

- If set to FALSE, disables the function.

The default is FALSE.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctSnapshotShortCountField

Specifies the metadata field name for Short Internal Count (xAccessesInLast10Days) for Content Tracker. Set from the Data Engine Control Center.

The default is none.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctSnapshotShortCountInterval

Specifies the number of days for Short Internal Count (xAccessesInLast10Days) for Content Tracker. Set from the Data Engine Control Center.

The default is none.

Important:
This variable must be set using the Content Tracker Admin Applet (the Data Engine Control Center), which is accessed through the Content Server interface.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

SctTrackContentAccessOnly

Specifies performance optimization for Content Tracker to function as efficiently as possible for use in high-volume production environments. Content Tracker collects and records only content access event data. This excludes information gathering on non-content access events like searches or the collection and synthesis of user profile summaries.

When enabled, only content access events are recorded. This is the default.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctTrackContentAccessOnly=true

SctUseGMT

Sets Content Tracker to convert logged event times to Universal Coordinated Time.

- If set to TRUE, logged event times are converted to Universal Coordinated Time.

- If set to FALSE, logged event times use local time.

The default is FALSE.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Modify the component's configuration file (IntradocDir/data/components/ContentTracker/config.cfg).

- Update the Component Configuration using Advanced Component Manager.

Usage

- Section 2.4, "Content Tracker"

Location

DomainHome/ucm/cs/data/contenttracker/config/sct.cfg

Example

Used as a configuration entry:

SctUseGMT=true

SearchCacheCleanerInterval

Sets the time between search cache cleanup attempts in seconds.

Default is 120 (2 minutes).

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

SearchCacheCleanerInterval=60

SearchCacheMaxItemAgeInMinutes

Sets the maximum age of an item in the search cache in minutes.

Default is 240 (4 hours).

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

SearchCacheMaxItemAgeInMinutes=30

SearchDebugLevel

Defines the level of detail for entries in the Indexer log files.

The log files are located at /weblayout/groups/secure/logs/.

The following list shows the debug levels:

Level

Description

none

No log is generated. This is the default.

verbose

Displays information for each file accessed. Indicates indexed, ignored, or failed, and generates a full report.

debug

Additional information at the functional level is generated.

trace

Information is logged as each activity is performed.

all

A full report including debug, trace, and verbose information is generated.

Tip:
If you set the debug level to anything but none, a log file will be generated for each index cycle. You may need to perform system maintenance periodically to reduce the number of log files.

Usage

- Section 2.11, "Debugging"

- Section 2.23, "Searching"

Location

- Repository Manager, Indexer tab, Configure, Indexer Debug Level

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SearchDebugLevel=all

SearchDir

Defines the path to the search directory.

The default value is DomainHome/ucm/cs/search/

Usage

- Section 2.12, "Directories and Paths"

- Section 2.23, "Searching"

Location

DomainHome/ucm/cs/bin/intradoc.cfg

Example

Used as a configuration entry:

SearchDir=f:/search/

SearchIndexerEngineName

This variable specifies the name of the search engine to use. Supported values include:

- DATABASE

- DATABASEFULLTEXT

Each search engine uses its own format for query strings. The default uses universal query syntax, but database search requires SQL syntax.

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

SearchIndexerEngineName=DATABASE

SearchQueryFormat

Retrieves search query pages with query syntax that is recognized regardless of supported search engines.

If used dynamically, appends the following to the URL:

SearchQueryFormat=Universal

When used dynamically, the universal search syntax is maintained through one search session. The syntax is maintained on a query page, result page and its navigation link and during actions such as searching within the page or saving the query. It is maintained until the user clicks the menu selection to re-load a search query page.

This can also be added to the config.cfg file so that the universal search query page is always used.

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SearchQueryFormat=Universal

See Also

- UniversalSearchAllowFullText

SearchQueryTrace

This variable is obsolete.

Default is FALSE.

Usage

- Section 2.11, "Debugging"

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SearchQueryTrace=true

SecondaryConversionStepName

Defines the name of the backup conversion step that Inbound Refinery will use if the native step conversion step fails.

Default is OIXConverter (Outside In).

AllowSecondaryConversion must be set to TRUE.

Usage

- Section 2.8.1, "Inbound Refinery"

Location

IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

SecondaryConversionStepName=OIXConverter

See Also

- AllowSecondaryConversion

SelfRegisteredAccounts

Defines the default accounts and permissions to be given to self-registered users.

This is a comma-delimited list.

Permissions for each account must be specified in parentheses after the account name.

The #none entry grants privileges to content items that have no account assigned. The #all entry grants privileges to all accounts.

There is no default value.

Returns the list of accounts as a string.

Usage

- Section 2.24.1, "Internal Security"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

SelfRegisteredAccounts=#none(RWDA),USERS/<$NewUser$>,BOS(R)

As script, returns the defined account information as a string:

<$SelfRegisteredAccounts$>

See Also

- SelfRegisteredAccounts

SelfRegisteredRoles

Defines the default roles to be given to self-registered users.

This is a comma-delimited list.

There is no default value.

Returns the roles as a string.

Usage

- Section 2.24.1, "Internal Security"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting:

SelfRegisteredRoles=guest,salesRole

As script, returns the defined roles as a string:

<$SelfRegisteredRoles$>

See Also

- SelfRegisteredRoles

ServiceStartupTimeout

Sets the Content Server startup timeout value. This configuration setting applies only to Content Server instances running on a Microsoft Windows platform.

Used to modify the server startup timeout value when a service requires more time to start up than is provided by the default Content Server startup timeout value, which is 120 seconds (2 minutes).

The value must be specified in seconds.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

The following example sets the startup timeout value to 240 seconds (4 minutes):

ServiceStartupTimeout=240

ShowContentForStorageBrowse

Defines whether content items are displayed when browsing storage locations for Physical Content Manager (PCM).

- If set to TRUE, permits content items to be displayed. If storage locations contain large numbers of items (that is, more than 100 per location), display time can be slowed.

- If set to FALSE, content items are hidden in storage locations.

Default is TRUE.

Restart WebCenter Content for this settings to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

ShowContentForStorageBrowse=false

ShowCreateExternalMenu

This Content Server configuration variable is specific to the Oracle WebCenter Content: Records system. Set this variable to true to display the following create external source features in your interface:

- Create external_source_name Item option in the External Content, external_source_name submenu. Note that the External Content menu is displayed only if an external source has been created.

- Create external_source_name Record option (record categories) or Check in New external_source_name Item option (non-record categories) in the Actions menu on the Exploring Retention Category page.

- Create external_source_name Record option (record categories only) in the Actions menu on the Exploring Records Folder page.

- Link New external_source_name Item option in the Actions menu on any link page.

When set to false, these features will not be displayed.

The default is FALSE.

Usage

- Section 2.21, "Records"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ShowCreateExternalMenu=true

showDocActions

Defines whether to display checkout links on the search results page.

This variable is also used to evaluate additional code for ODMA applications, such as Oracle Desktop. To display checkout links for a Content Server instance that is not accessed by ODMA clients, use the showSearchResultsCheckoutColumn variable.

- When set to TRUE, a column containing checkout links is displayed on the search results page.

- When set to FALSE, checkout links are not displayed on the search results page.

Default is FALSE.

Usage

- Section 2.3, "Clients"

- Section 2.5, "Content Items"

- Section 2.19, "Page Display"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

showDocActions=1

See Also

- showSearchResultsCheckoutColumn

- noInfoColumn

- noRevisionsColumn

ShowEmailMetadataMenu

Defines whether the administrative UI is displayed when the EmailMetadata component is installed and enabled on an Oracle WebCenter Content: Records instance.

- If set to TRUE, permits the administrative UI to be displayed.

- If set to FALSE, the administrative UI is hidden.

The default is FALSE.

Restart WebCenter Content for this settings to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

IntradocDir/components/EmailMetadata/emailmetadata_environment.cfg

Example

Used as a configuration entry:

ShowEmailMetadataMenu=true

ShowHyperlinkBox

Defines whether a box is placed around hyperlinks in PDF files.

- When set to TRUE, a box is placed around hyperlinks in PDF files.

- When set to FALSE, a box is not placed around hyperlinks in PDF files.

Default is FALSE.

Usage

- Section 2.8.2.1, "General Variables"

Location

IntradocDir/IdcRefinery/shared/idcrefinery.cfg

Example

Used as a configuration entry:

ShowHyperlinkBox=true

IsSimpleProfilesEnabled

This variable enables the Simple Profile functionality.

- When set to TRUE, enables Simple Profile functionality.

- When set to FALSE, disables Simple Profile functionality.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

IsSimpleProfilesEnabled=true

ShowOnlyKnownAccounts

Defines whether to display only predefined accounts on checkin and search pages.

- When set to TRUE, only predefined accounts appear in the Accounts option list on checkin and search pages.

- When set to FALSE, any user-defined accounts that the user belongs to are also displayed in the option list.

Default is an empty string.

Usage

- Section 2.24.1, "Internal Security"

- Section 2.13, "Field Display"

Location

- System Properties, Content Security tab, Show only known accounts

- Administration, Admin Server, Content Security menu option, Show only known accounts

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ShowOnlyKnownAccounts=true

ShowRevisionsColumn

In later versions of Content Server, the revision number of a document is not displayed on the Search Results page while using Classic view. This configuration variable is used to display the revision number.

- When set to TRUE, the revision number of a document is displayed on the Search Results page while using Classic view.

- This setting works in Classic search mode only.

Default is TRUE.

Usage

- Section 2.13, "Field Display"

Location

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

ShowRevisionsColumn=false

showSearchResultsCheckoutColumn

Defines whether to display checkout links on the standard search results page.

- When set to TRUE, a column containing checkout links is displayed on the standard search results page.

- When set to FALSE, checkout links are not displayed on the standard search results page.

Default is FALSE.

Usage

- Section 2.5, "Content Items"

- Section 2.19, "Page Display"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

showSearchResultsCheckoutColumn=1

See Also

- showDocActions

- noInfoColumn

- noRevisionsColumn

SkipMozillaMailToWorkaround

Used to disable an email solution that allows Mozilla mail applications to accurately handle email from the Search Result and Content Info page. If your mailer does not send correctly formatted email, set this variable to TRUE.

Usage

- Section 2.7, "Content Server"

Location

- IntradocDir/config/config.cfg

Example

Disables special email handling:

SkipMozillaMailToWorkaround=true

SmtpPort

Defines the Simple Mail Transfer Protocol (SMTP) port number.

Default is 25.

Usage

- Section 2.7, "Content Server"

Location

- System Properties, Internet tab, SMTP Port

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SmtpPort=25

See Also

- SysAdminAddress

- MailServer

SocketHostAddressSecurityFilter

Defines the IP addresses that are allowed to make calls to the Content Server instance.

Either this setting or SocketHostNameSecurityFilter is required to allow remote IdcCommandX calls to the Content Server instance. (Generally, both settings should not be used at the same time.) For more information, see Oracle Fusion Middleware Developing with Oracle WebCenter Content.

Use a pipe character | to separate multiple addresses. Make sure that there are no spaces on either side of the pipe.

Use wildcards to indicate groups of addresses (* for zero or more characters, ? for a single character).

Default is the IP address of the local host.

Usage

- Section 2.27, "Web Server"

- Section 2.24.2, "External Security"

Location

- System Properties, Server tab, IP Address Filter

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SocketHostAddressSecurityFilter=10.10.3.*|127.0.0.1

See Also

- SocketHostNameSecurityFilter

SocketHostNameSecurityFilter

Defines the server names that are allowed to make calls to the Content Server instance.

Either this setting or SocketHostAddressSecurityFilter is required to allow remote IdcCommandX calls to the Content Server instance. (Generally, both settings should not be used at the same time.) See Oracle Fusion Middleware Developing with Oracle WebCenter Content.

Use a pipe character | to separate multiple server names. Make sure that there are no spaces on either side of the pipe.

Usage

- Section 2.27, "Web Server"

- Section 2.24.2, "External Security"

Location

- System Properties, Server tab, Hostname Filter

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SocketHostNameSecurityFilter=olympus|localhost|zeus

See Also

- SocketHostAddressSecurityFilter

SourcePath

Specifies a unique string that identifies an LDAP provider. The first time a user requests credentials through the provider, this string is stored with the user information so it can be used to match the user with the provider next time the user asks for credentials.

We suggest using the name of the LDAP provider as the Source Path.

There is no default.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, Source Path

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

SourcePath=LdapProvider1

See Also

- Priority

StdPageWidth

Sets the page width in pixels.

Default is 550.

Usage

- Section 2.19, "Page Display"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

StdPageWidth=1000

Returns the page width as a string:

<$StdPageWidth$>

StrConfineOverflowChars

Defines a string padding character.

Defines the character used for padding by the strConfine Idoc Script function.

The default is a period (dot).

Usage

- Section 2.25, "Strings"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

StrConfineOverflowChars=.

See Also

- "strConfine" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

StyleForRequiredFields

Formats how a required metadata field is displayed.

When set, the required field is displayed in the style as defined in a cascading style sheet.

Values for the style can be any of the field caption styles defined for the Content Server.

Usage

- Section 2.13, "Field Display"

Parameters

The only parameter is the specified style.

Location

IntradocDir/config/config.cfg

Example

The following example displays a required field in red:

StyleForRequiredFields=requiredField

See Also

- NotationForRequiredFields

SubjectsDir

Defines the path to the subjects/ directory.

Subjects are subsystems that are notified when a Content Server service makes a change in the system, such as modifying an option list or adding a new user.

Default is DomainHome/ucm/cs/data/subjects/.

Usage

- Section 2.12, "Directories and Paths"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SubjectsDir=c:/domain_temp/data/subjects

SubscriptionCollatedFieldList

Defines a list of fields displayed for subscriptions.

The default fields that are defined at startup are dID and dDocName.

Additional fields can be defined using AdditionalSubscriptionCollatedFieldList.

It is recommended that you use AdditionalSubscriptionCollatedFieldList to add subscription fields to the collated list rather than change SubscriptionCollatedFieldList.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

See Also

- AdditionalSubscriptionCollatedFieldList

SubscriptionMethod

Specifies how subscriptions are processed.

The possible values are:

- SubscriptionOriented: Content Server compares each subscription with the content items that have been indexed.
This value should be used when the number of subscriptions is small relative to the number of content items (for example, 100,000 content items and 1000 subscriptions).

- DocumentOriented: Content Server compares each indexed content item with the active subscriptions.
This value should be used when the number of subscriptions is large relative to the number of content items (for example, 1000 content items and 1000 subscriptions).

Default is SubscriptionOriented.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SubscriptionMethod=DocumentOriented

SysAdminAddress

Defines the system administrator email address.

This is the address used in workflow and subscription notification emails that come from the Content Server instance.

Returns a string.

There is no default value.

Usage

- Section 2.26, "Users"

- Section 2.7, "Content Server"

Location

- System Properties, Internet tab, Administrator Mail Address

- Administration, Admin Server, Internet Configuration menu option, Administrator Mail Address

- IntradocDir/config/config.cfg

Example

As a configuration setting:

SysAdminAddress=admin@example.com

As script, returns the value of the configuration setting:

<$SysAdminAddress$>

See Also

- MailServer

- SmtpPort

SystemDateFormat

Sets the date/time format for the Content Server instance.

Note that there are two types of date formats: one that stores seconds and one that truncates seconds and stores the date up to the minute. If seconds are used, dates can only be stored up to the year 2037.

If SystemLocale is not specified as a configuration setting, the SystemDateFormat will be deduced directly from the operating system settings in the Java VM instead of using the Content Server configuration table settings for the SystemLocale. If SystemLocale is explicitly defined, then the date/time format from the Content Server configuration tables for that locale will be used instead.

The syntax for this format is an extension of the date format functionality provided in the standard Java class libraries.

Usage

- Section 2.10, "Date and Time"

- Section 2.18, "Localization"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry to set the standard US date time using the four digit year format:

SystemDateFormat=M/d{/yyyy} {h:mm[:ss] {aa}[zzz]}

See Also

- SystemLocale

- SystemTimeZone

SystemLocale

Sets the system locale for the Content Server instance.

This setting controls the following:

- localized strings used in Content Server interface

- character encoding for web pages

- date/time format

- time zone

- parameters used for full-text indexing

Any of these individual features can be controlled by separate configuration entries or by changing the settings for the SystemLocale.

This setting can be changed on the Server tab of the System Properties utility. The defaults for a specific locale can be changed on the Localization tab of the System Properties utility.

If SystemLocale is not specified as a configuration setting, the SystemDateFormat will be deduced directly from the OS settings in the Java VM instead of using the Content Server configuration table settings for the SystemLocale. If SystemLocale is explicitly defined, then the date/time format from the Content Server configuration tables for that locale will be used instead.

Usage

- Section 2.18, "Localization"

Location

- System Properties, Server tab, System Locale

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SystemLocale=Deutsch

See Also

- SystemDateFormat

- SystemTimeZone

SystemTimeZone

Sets the default time zone for the Content Server instance.

The SystemTimeZones table in the WC_CONTENT_ORACLE_HOME/shared/config/resources/std_locale.htm file lists the time zones that can be specified.

Default is the time zone set for the local computer's operating system. If the default is used, the variable does not appear in the configuration file.

Usage

- Section 2.10, "Date and Time"

- Section 2.18, "Localization"

Location

- System Properties, Server tab, System Timezone

- IntradocDir/config/config.cfg

Example

Used as a configuration entry:

SystemTimeZone=Europe/Berlin

See Also

- SystemDateFormat

- SystemLocale

TempDir

Specifies the location where the Content Server Analyzer utility duplicates and tests files.

Default is a temp subdirectory in the log directory specified by the IdcAnalyzeLogDir setting.

Usage

- Section 2.11, "Debugging"

- Section 2.12, "Directories and Paths"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

TempDir=f:/domain/analyzer_logs/temp/

See Also

- IdcAnalyzeLogDir

TextIndexerFilterValidateFormats

This variable specifies a comma-delimited list of file types that are verified for unreadable characters. When this variable is used, specified file formats are checked for unreadable characters and those characters are corrected before the text file is passed to be indexed.

Usage

- Section 2.16, "Indexing"

Location

DomainHome/ucm/cs/TextIndexerFilter/textindexerfilter_einviornment.cfg

Example

TextIndexerFilterValidateFormats=application/pdf

TimeoutChangedTemplateForcedConversionsInMins

Defines the minimum interval in minutes at which Dynamic Converter will reconvert a file when the template or layout has changed.

- When set to a positive value, forced or up front conversions will be reconverted because of a change to the template or layout only after the time specified by this setting has passed.

- If a conversion rule is changed to use a different template or layout, the normal evaluation logic is used.

- This setting is ignored if the NeverTimeoutForcedConversionsTemplateChange setting is TRUE.

- When set to 0, the TimeoutMismatchedForcedConversionsInMins setting is used.

Default is 0.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

TimeoutChangedTemplateForcedConversionsInMins=1

See Also

- NeverTimeoutForcedConversionsTemplateChange

- TimeoutMismatchedForcedConversionsInMins

TimeoutMismatchedForcedConversionsInMins

Defines the minimum interval in minutes at which Dynamic Converter will reconvert a file when the source document, template, or layout has changed.

- When set to a positive value, forced or up front conversions will be reconverted because of a change to the source document, template, or layout only after the time specified by this setting has passed.

- If a conversion rule is changed to use a different template or layout, the normal evaluation logic is used.

- If the TimeoutChangedTemplateForcedConversionsInMins is set to a positive value, this setting applies only to changes in the source document.

- When set to 0, forced or up front conversions will not be reconverted because of a change to the source document.

Default is 15 minutes.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

TimeoutMismatchedForcedConversionsInMins=10

See Also

- NeverTimeoutForcedConversionsTemplateChange

- TimeoutChangedTemplateForcedConversionsInMins

TimeoutPerOneMegInSec

Sets the timeout for indexing files into the index collection.

- The size of a bulkload file being indexed is rounded up to the nearest megabyte, and then multiplied by this setting to determine the timeout value in seconds.

- If files have a large amount of numeric data, the timeout should be increased to 3000–6000. Indexing cleanup cycles, which occur after every four or so bulkloads and count toward the timeout, can take longer for numeric data.

Default is 600 seconds per megabyte.

Usage

- Section 2.16, "Indexing"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

TimeoutPerOneMegInSec=3000

TraceConversionCacheCleanup

Outputs a report to the debug trace during the Dynamic Converter cache cleanup cycle.

- When set to TRUE, the debug trace includes a report of which documents were deleted, the conversion type of deleted documents (forced or not), and whether documents were deleted because of cache size constraints.

- See ConversionCacheExpirationPeriodInDays, DatedCacheIntervalDays, and MaxConversionCacheSizeInMegs for more information on the Dynamic Converter cache cleanup cycle.

Default is FALSE.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

TraceConversionCacheCleanup=true

See Also

- ConversionCacheExpirationPeriodInDays

- DatedCacheIntervalDays

- MaxConversionCacheSizeInMegs

TraceResourceConflict

When the Content Server instance is started from a command line, each system resource that is overridden twice by component resources is output to the command line.

When set to TRUE, system resources that are overridden by two or more component resources are output.

Default is FALSE.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

TraceResourceConflict=true

See Also

- TraceResourceLoad

- TraceResourceOverride

TraceResourceLoad

When the Content Server instance is started from a command line, all resource loading activities are output to the command line.

When set to TRUE, all resources loaded, resource overrides, resource conflicts, and resource merges are output.

Default is FALSE.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

TraceResourceLoad=true

See Also

- TraceResourceConflict

- TraceResourceOverride

TraceResourceOverride

When the Content Server instance is started from a command line, system resources and non-system component resources that are overridden by a component resource are output to the command line.

When set to TRUE, system resources and non-system resources that are overridden by one or more component resources are output.

Default is FALSE.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

TraceResourceOverride=true

See Also

- TraceResourceConflict

- TraceResourceLoad

UieHideSearchCheckboxes

Shows or hides the metadata field checkboxes on the search page, which limit the number of metadata fields initially shown on the page.

- When set to TRUE, the metadata field checkboxes are not shown on the search page.

- When set to FALSE, the metadata field checkboxes are shown on the search page.

Default is TRUE.

Restart WebCenter Content for this setting to take effect.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.21, "Records"

Location

DomainHome/ucm/urm/components/RecordsManagement/records_management_environment.cfg

Example

Used as a configuration entry:

UieHideSearchCheckboxes=false

UniversalSearchAllowFullText

Changes the displayed fields when SearchQueryFormat=Universal is used. If UniversalSearchAllowFullText is set to FALSE, the Full Text Search field is not displayed on the Search page.

The default is TRUE.

Usage

- Section 2.5, "Content Items"

Location

IntradocDir/config/config.cfg

Example

UniversalSearchAllowFullText=false

See Also

- SearchQueryFormat

UploadApplet

Enables the multiple file Upload Applet.

Important:
This setting is only for use by custom legacy versions of the Upload Applet. It should not be enabled when the standard MultiUpload variable is enabled.

When set to TRUE, the Upload Applet is enabled so that multiple files can be zipped and checked in as a single content item.

When set to FALSE, the Upload Applet is disabled.

Default is FALSE.

Usage

- Section 2.7, "Content Server"

- Section 2.3, "Clients"

Location

IntradocDir/config/config.cfg

Example

As a configuration setting, enables the Upload Applet:

UploadApplet=true

As script, evaluates the condition of the Upload Applet:

<$UploadApplet$>

See Also

- DownloadApplet

- MultiUpload

UseAccounts

Enables the use of accounts.

When set to TRUE, accounts are enabled.

Default is FALSE.

Usage

- Section 2.24.1, "Internal Security"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UseAccounts=true

UseAdsi

Enables Active Directory (ADSI) authentication for the Content Server instance.

This setting is valid only when NtlmSecurityEnabled is TRUE.

This option is available only when using an IIS w server.

When set to TRUE, users defined in Active Directory can log in to the Content Server instance using their network credentials.

There is no default value.

Usage

- Section 2.24.2, "External Security"

Location

- System Properties, Internet tab, Active Directory Security (ADSI) option

- Administration, Admin Server, Internet Configuration menu option, Active Directory Security option

- IntradocDir/config/config.cfg

Example

Enables ADSI security:

UseAdsi=true

See Also

- NtlmSecurityEnabled

- UseNtlm

UseCascadingStyleSheets

Enables the use of cascading style sheets (CSS) for Dynamic Converter.

When set to TRUE, cascading style sheets are enabled.

When set to FALSE, cascading style sheets are disabled. This option is useful only for older browsers that do not support CSS.

Default is TRUE.

Usage

- Section 2.8.3, "Dynamic Converter"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UseCascadingStyleSheets=false

UseDatabaseWfInQueue

Enables the WebCenter Content user interface to display a filter named "Assigned to you" in the Content in Workflow page. (This filter is automatically displayed in the native 11g interface.)

When set to 1 (or true), the filter is visible in the user interface.

When set to 0 (or false), the filter is not visible in the user interface.

Default is true.

If you have set UseDatabaseWfInQueue=1 in the config.cfg file then perform the following steps:

1. Restart the Content Server.

2. Click the alert message that is displayed on the Content Server home page: Click to complete workflow setup.
Ensure that Content Server returns the following success message: Workflow setup is now complete.

If you have set UseDatabaseWfInQueue=0 in the config.cfg file then perform the following step:

1. Restart the Content Server.

Usage

- Section 2.28, "Workflow"

Location

IntradocDir/config/config.cfg

UseDatabaseShortIndexName

Required if the database in use does not support index names longer than eighteen characters.

When set to TRUE, short index names are used.

When set to FALSE, short index names are not used.

Default is FALSE.

Usage

- Section 2.9, "Database"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UseDatabaseShortIndexName=false

UseFourDigitYear

This string is obsolete. Use SystemDateFormat.

Specifies a four-digit or two-digit year display format.

- When set to TRUE, the Content Server instance displays years with four digits.

- When set to FALSE, the Content Server instance displays years with two digits.

The Content Server supports both two-digit and four-digit years for data entry.

Default is TRUE.

Usage

- Section 2.10, "Date and Time"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UseFourDigitYear=false

See Also

- SystemDateFormat

UseNestedGroups

A JpsUser provider option. Specifies whether Content Server retrieves users' direct and indirect group membership in the authentication provider.

When set to TRUE, both user's direct and indirect group membership is retrieved. This is the default behavior for JpsUser provider.

When set to FALSE, only users' direct group membership is retrieved.

Usage

- Section 2.24.2, "External Security"

Location

- IntradocDir/data/providers/jpsuserprovider/provider.hda

Example

Used as a configuration entry:

UseNestedGroups=false

UseNetscape

Specifies the method used to connect to an LDAP server through a provider.

- When set to TRUE, the Netscape SDK will be used. This is the recommended setting for better performance.

- When set to FALSE, the JNDI connection will be used.

Default is TRUE.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, Use Netscape SDK

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

UseNetscape=0

UseNtlm

Enables NT LAN Manager (NTLM) authentication for the Content Server instance.

- This setting is valid only when NtlmSecurityEnabled is TRUE.

- This option is available only when using an IIS web server.

- When set to TRUE, users defined on a Windows network (NTLM) can log in to the Content Server instance using their network credentials.

There is no default value.

Usage

- Section 2.24.2, "External Security"

Location

- System Properties, Internet tab, NT Domain Security (NTLM) option

- Administration, Admin Server, Internet Configuration menu option, NT Domain Security option

- IntradocDir/config/config.cfg

Example

Enables NTLM security:

UseNtlm=true

See Also

- NtlmSecurityEnabled

- UseAdsi

UserCache

Defines the path to the users directory, which is the location where user personalization information is stored.

Default is DomainHome/ucm/cs/data/users/.

Usage

- Section 2.12, "Directories and Paths"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UserCache=c:/myuserdata/

UserCacheMaxSize

The maximum number of items in the user cache.

Default is 5000.

Usage

- Section 2.7, "Content Server"

- Section 2.26, "Users"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UserCacheMaxSize=5000

See Also

UserCacheClusterSupport

UserCacheMaxSizeMatchInitialSize

UserCacheClusterSupport

Enable or disable user cache clustering support on the user cache.

When set to TRUE, the cache clustering is enabled.

When set to FALSE, the cache clustering is disabled.

Default is FALSE.

Usage

- Section 2.7, "Content Server"

- Section 2.26, "Users"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UserCacheClusterSupport=true

See Also

UserCacheMaxSize

UserCacheMaxSizeMatchInitialSize

A flag to indicate if the user cache memory has to be pre-allocated by the system.

When set to TRUE, the memory is pre-allocated by the system for the user cache.

When set to FALSE, the memory is not pre-allocated by the system for the user cache.

Default is FALSE.

Usage

- Section 2.7, "Content Server"

- Section 2.26, "Users"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UserCacheMaxSizeMatchInitialSize=true

See Also

UserCacheMaxSize

UserCacheTimeout

Sets the timeout in milliseconds for the temporary cache of global and external user information.

Default is 60000 milliseconds (1 minute).

Usage

- Section 2.7, "Content Server"

- Section 2.26, "Users"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UserCacheTimeout=120000

UseRedirectedOutput

Enables the capture of output from the Java Virtual Machine. This includes logging output from any enabled tracing facilities and stack dumps resulting from the VM crash.

Used only on Windows systems and if the Content Server is running as a service.

Usage

- Section 2.11, "Debugging"

Location

IntradocDir/config/config.cfg

Example

UseRedirectedOutput=true

UseRevisionCreateDate

When this variable is set in the system importing an archive, the Archiver uses the dCreateDate for comparisons.

This allows Content Server to differentiate revisions by their initial create date and not by the assigned dInDate.

This is not set by default.

Important:
Use this configuration setting if no legacy content from older versions (before 7.5) of Content Server are being imported.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

UseRevisionCreateDate=true

UserFilteredSubjects

Specifies the subjects that must be refreshed if the current user's security credentials have changed.

- Subjects are subsystems that are notified when a Content Server service makes a change in the system, such as modifying an option list or adding a new user.

- Add any custom security subjects to this setting. Custom subjects are typically created only for unusually complex security integrations.

- This is a comma-delimited list.

Default is users,accounts.

Usage

- Section 2.24.1, "Internal Security"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

UserFilteredSubjects=users,accounts,licenses

UseSearchCache

When set to TRUE, enables the search cache. The search cache improves search performance by caching recent search engine queries.

Default is TRUE.

Usage

- Section 2.23, "Searching"

Location

IntradocDir/config/config.cfg

Example

As a configuration variable:

UseSearchCache=true

If this variable is set to FALSE and used on the CGI line of a browser URL request doing a query, it forces the query to execute each time. This makes it possible to measure the speed of the query being executed and to verify the cache results (because a new search result is generated each time).

http://...?IdcService=GET_SEARCH_RESULTS&...UseSearchCache=false

UseSecureLdap

Specifies whether SSL is used with the LDAP provider.

- When set to TRUE, SSL is used. You must have the appropriate certificates installed on the LDAP server. Once SSL is initiated, the certificates will secure communication between the LDAP server and the Content Server instance.

- When set to FALSE, SSL is not used.

Default is FALSE.

Usage

- Section 2.24.2, "External Security"

Location

- Add/Edit LDAP Provider page, Use SSL

- IntradocDir/data/providers/provider_name/provider.hda

Example

Used as a configuration entry:

UseSecureLdap=true

See Also

- LdapPort

UseSSL

Enables the secure sockets layer (SSL).

- This setting affects the variables HttpWebRoot and HttpCgiPath.

- Use the Secure Sockets Layer only if you are using an SSL-enabled web server.

- When set to TRUE, SSL is used (https instead of http).

Default is FALSE.

Usage

- Section 2.24.2, "External Security"

- Section 2.27, "Web Server"

Location

- System Properties, Internet tab, Use Secure Sockets Layer

- IntradocDir/config/config.cfg

Example

As a configuration setting, enables SSL:

UseSSL=true

As script, returns the value of the configuration setting:

<$UseSSL$>

See Also

- "HttpCgiPath" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

- "HttpWebRoot" in Oracle Fusion Middleware Developing with Oracle WebCenter Content

VaultDir

Defines the path to the vault directory.

- This is the root directory of the Content Server native file repository.

- This setting is required only if the vault directory is not located in the Content Server root directory.

There is no default value.

Usage

- Section 2.12, "Directories and Paths"

- Section 2.8.1, "Inbound Refinery"

Location

- Content Server: DomainHome/ucm/cs/bin/intradoc.cfg

- Inbound Refinery: IntradocDir/ucm/ibr/bin/intradoc.cfg

Example

Used as a configuration entry:

VaultDir=f:/vault

VerboseMode

Specifies the level of logging in the Inbound Refinery log.

- When set to TRUE, the Inbound Refinery log records all messages and configuration information (such as whether the PDF is optimized, where the custom converter path is located, and how much time is allowed for custom conversions).

- When set to FALSE, the Inbound Refinery log records only error messages.

Default is FALSE.

Usage

- Section 2.8.1, "Inbound Refinery"

- Section 2.11, "Debugging"

Location

- Local Inbound Refinery Configuration screen, General tab, Verbose logging

- IntradocDir/IdcRefinery/connections/main/intradoc.cfg

Example

Used as a configuration entry:

VerboseMode=true

WarnAboutTimeZone

Specifies whether the Content Server installer displays a warning if it cannot determine the computer's time zone.

- When set to TRUE, a default time zone is used and a warning is displayed.

- When set to FALSE, a default time zone is used, but no warning is displayed.

Default is FALSE.

Type and Usage

- Section 2.10, "Date and Time"

- Section 2.18, "Localization"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

WarnAboutTimeZone=true

WebBrowserPath

Defines the path to the Web browser that displays the Content Server Help files from stand-alone applications.

There is no default value.

Usage

- Section 2.12, "Directories and Paths"

Location

- System Properties, Paths tab, Browser Executable Path

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

Example

Used as a configuration entry:

WebBrowserPath=c:/Program Files/Internet Explorer/Iexplore.exe

WebDAVMaxInactiveInterval

When a user logs in to the Content Server instance through a WebDAV client application, the WebDAV component sets a cookie in the client. The cookie remains set as long as a WebDAV request is made within the time specified by the WebDAVMaxInactiveInterval parameter.

The cookie remains set even if the WebDAV client application is closed. If the cookie expires, the user must log in to the Content Server instance again to perform WebDAV transactions through Microsoft Word, Microsoft Excel, and Microsoft PowerPoint software.

Default is 7200 seconds, or two hours.

Important:
To ensure this setting remains in effect after a software update, perform one of these tasks:

- Add or edit the setting in the IntradocDir/config/config.cfg file.

- In the Content Server user interface, choose Administration, then Admin Server, then General Configuration, and enter the setting in the Additional Configuration Variables field.

Usage

- Section 2.14, "Folders and WebDAV"

Location

IntradocDir/components/Folders_g/folders_environment.cfg

Example

WebDAVMaxInactiveInterval=7200

WeblayoutDir

Defines the path to the weblayout/ directory.

- This is the root directory of the Content Server web site.

- This setting is required only if the weblayout/ directory is not located in the Content Server root directory.

There is no default value.

Usage

- Section 2.12, "Directories and Paths"

- Section 2.8.1, "Inbound Refinery"

Location

- Content Server: DomainHome/ucm/cs/bin/intradoc.cfg

- Inbound Refinery: DomainHome/ucm/ibr/bin/intradoc.cfg

Example

Used as a configuration entry:

WeblayoutDir=f:/weblayout

WebServerAuthOnly

Specifies whether the web server filter will authenticate users that are defined in the Content Server database.

- When set to TRUE, the web server filter will not validate users against the internal user names and passwords from the Content Server database.

- If Basic Authentication is enabled in IIS, then this setting must be TRUE. This setting enables browsers to use Basic authentication when logging into the Microsoft Network; users can log in using a Windows user name and password using the Netscape browser.

- If this option is enabled, new users can be added only by adding them to a Windows network domain, since users are not authenticated against the Content Server user database. However, if the database happens to have a user of the same name as a Windows network user, then the Content Server security profile is used instead of the Windows network profile.

Default is FALSE.

Usage

- Section 2.27, "Web Server"

- Section 2.24.2, "External Security"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry to enable web server authorization only:

WebServerAuthOnly=true

WorkflowDir

Defines the path to the workflow directory, which contains workflow data.

Default is IntradocDir/data/workflow/.

Usage

- Section 2.12, "Directories and Paths"

- Section 2.28, "Workflow"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

WorkflowDir=c:/workflow_info/

WorkflowIntervalHours

Defines the time between workflow update cycles, in hours.

The update event scripts for any revisions in a workflow are executed at this interval.

Default is 1 hour.

Usage

- Section 2.28, "Workflow"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

WorkflowIntervalHours=2

XMLEncodingMode

Used to specify international characters in URLs in the browser used for Content Server.

Setting this variable to FULL may be useful in the following instances:

- If Content Server is being used in a browser that is using UTF-8 (that is, with the setting Always send URLs as UTF-8 enabled). This usually occurs only in older versions of Microsoft browsers.

- If a custom component is created that puts Content Server URLs into Javascript variables. In that case, the URLs may need to be fully encoded.

- If Content Server is being accessed through a PDA-type device (PALM, handheld computer, and so on). If a component is used that provides accessibility through these devices, then the URLs may need to be fully encoded. These devices may not support non-7-bit characters in their URLs.

Default is PARTIAL.

Usage

- Section 2.7, "Content Server"

Location

IntradocDir/config/config.cfg

Example

Used as a configuration entry:

XMLEncodingMode=full

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.