Advanced Options

This section provides the following configuration options:

  • Database Type - The type of database that your WebCenter Content runs on.
  • Crawl Previous Versions - When enabled, all versions of a document will be crawled. Otherwise, just the latest version of the document will be crawled.
    Note: If you use the Crawl All Versions setting at the same time as the data filter setting, the settings work together in the following ways:
    • The data filter setting is applied before the Crawl All Versions setting. The data filter setting searches only the latest versions of documents to fetch the documents that meet the conditions of the data filter.
    • If the Crawl All Versions setting is enabled in addition to the data filter setting, all versions of documents that meet the conditions of the data filter will be crawled.
  • Previous Version Limit - Maximum number of a document's previous versions to be crawled when Crawl Previous Versions is enabled.
    Note: When set to -1 all previous versions of documents will be crawled. Setting any number greater than -1 will only return up to the specified number of previous versions, starting with the most recent.
  • Query Limit - The maximum number of content ids enqueued by each query URL.
  • Skip Alternate Documents - When enabled, only the primary document on the content server is retrieved
  • Crawl Folders - When enabled, in addition to querying the server for documents, the connector will start from and crawl the root document folder and associated sub-folders.
  • Crawl Websites - Specify a comma separated list of websites. The connector will fetch documents only from the specified websites.
  • Query Format - Query format to be used when retrieving document IDs. Data filters must be written in this format. The default universal uses the Verity format. The database type should be used only with caution for the below reason. As of version 11g, Oracle disabled the ability to use the native, database format for queries by default due to the SQL injection vulnerability inherent in allowing users to write query clauses.
    Note: In order to use the database format in 11g, you must add the following entry into the home\user_projects\domains\webcenter_domain\webcenter\cs\configconfig.cfg file, or through a web browser, by navigating to Administration > Admin Server > General Configuration and adding the following entry into the Additional Configuration Variables section: 
    AllowNativeQueryFormat=true
    You must restart the server for the change to take effect.
    Note: Activating this feature in WebCenter Content can expose a security vulnerability.
  • Data Filter for Initial Crawl - Specify a new line separated list of conditionals in the query format specified above. An example would be xWebsiteObjectType = `Data File` or dReleaseDate > `2009-08-10`. The connector will only fetch documents that meet all of the specified conditionals.
  • SQL Data Filter for Continuous Update Mode - Filling in this filter field is only required if given filter above is of type universal (uses Verity/OracleText syntax). This SQL filter will only be applied in continuous update mode and should be an exact translation of the universal filter given above. Column names need to be prefixed by their relation names. An example would be: DocMeta.xWebsiteObjectType = 'Data File' or: Revisions.dReleaseDate > '2009-08-10'. The connector will only fetch documents that meet *ALL* the specified conditionals.
  • Base ACLs on a Document Property (for late binding security) - When enabled, the value of each ACL is set to the value of a document property (configured below). Enabling this setting is required for some forms of late-binding security.
  • ACL Property - The name of a property to use when generating ACLs. This option is ignored if Base ACLs on a Document Property is disabled.
  • Time offset - The number of seconds to subtract from the Data Explorer Engine server's local time when asking the WCC server for changes since a given date (when running Continuous Update).
  • Maximum java heap size - The maximum size of the Java heap. Use the same format used in the -Xmx argument to the java command. Examples: 
    512m    (for 512 megabytes)
2g      (for two gigabytes)
    Values less than 160m are ignored.
  • Socket Timeout - Sets the timeout value for the socket connection. This setting will be ignored if set to -1.
  • Connection Wait Time - Sets the value for the connection wait time. This setting will be ignored if set to -1.