Considerations for Using OracleTextSearch Configuring OracleTextSearch for Oracle Content Server

7 Managing Search Tools 7-1 7 Managing Search Tools This chapter describes concepts and tasks for managing Oracle Content Server search tools: ■ Section 7.1, OracleTextSearch ■ Section 7.2, Oracle Secure Enterprise Search

7.1 OracleTextSearch

If you have a license to use OracleTextSearch software with Oracle Database 11g, then you can configure the OracleTextSearch feature to use Oracle Text 11g as the primary full-text search engine for Oracle Universal Content Management Oracle UCM. Oracle Text 11g offers state-of-the-art indexing capabilities and provides the underlying search capabilities for Oracle Secure Enterprise Search Oracle SES. However, Oracle Text 11g has its own query syntax, which is intended more for use by applications or information professionals rather than casual end-users. OracleTextSearch enables administrators to specify certain metadata fields to be optimized for the search index and to customize additional fields. This feature also enables a fast index rebuild and index optimization. This section covers the following topics: ■ Section 7.1.1, Considerations for Using OracleTextSearch ■ Section 7.1.2, Configuring OracleTextSearch for Oracle Content Server ■ Section 7.1.3, Oracle Text 11g Features and Benefits ■ Section 7.1.4, Managing OracleTextSearch ■ Section 7.1.5, Searching with OracleTextSearch ■ Section 7.1.6, Metadata Wildcards ■ Section 7.1.7, Search Results with OracleTextSearch

7.1.1 Considerations for Using OracleTextSearch

The following items are important when considering use of OracleTextSearch: ■ Oracle UCM version 11g Release 1 11.1.1 supports all languages supported by Oracle Text 11g. OracleTextSearch can filter and extract content from different document formats in different languages. It supports a large number of document formats, including Microsoft Office file formats, Adobe PDF, HTML, and XML. It can render search results in various formats, including unformatted text, HTML with term highlighting, and original document format. 7-2 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server ■ Oracle Text 11g runs on Oracle Database 11g. The Oracle Content Server system database can be Oracle Database 11g, Microsoft SQL Server, or other databases as listed in the UCM 11g Release 1 11.1.1 Certification Matrix. However, if the system database is not Oracle Database 11g, then an external provider for OracleTextSearch must be configured. See Section 7.1.2, Configuring OracleTextSearch for Oracle Content Server. ■ When using OracleTextSearch, Oracle Database version 11.1.0.7.0 or higher is required, and any SDATA field is limited to a maximum of 249 characters. All Optimized Fields are SDATA fields, which by default include dDocName, dDocTitle, dDocType, and dSecurityGroup. The total number of sdata fields is limited to thirty-two 32 fields. Note that without Folders_g enabled, the dDocTitle field is limited to 80 characters by default. ■ While Oracle UCM provides numerous search options using a variety of databases Oracle, Microsoft SQL Server, IBM DB2, by default the database that serves as the search index is the same system database used by Oracle UCM to manage metadata and other configuration information users, security groups, and so on.. The OracleTextSearch feature enables Oracle Text 11g as a separate search collection instance on Oracle Database 11g for Oracle UCM, which allows the search collection to reside on a separate computer and not compete with Oracle UCM for processors and memory. This can improve indexing and search response time. ■ The OracleTextSearch collection instance can be installed on a different platform than the Oracle UCM installation. ■ If the OracleTextSearch feature is configured and running, and metadata fields are pushed into the Oracle Content Server instance either by the administrator or by a component requiring that the Oracle Content Server instance be restarted, then the OracleTextSearch index must be rebuilt before content using the new metadata fields can be checked in to the Oracle Content Server instance.

7.1.2 Configuring OracleTextSearch for Oracle Content Server

1. Open the config.cfg file for the Oracle Content Server instance in a text editor. 2. Set the following property values: Required: SearchIndexerEngineName=OracleTextSearch Optional: IndexerDatabaseProviderName=SystemDatabase Note: If the Oracle UCM system database used with OracleTextSearch is not Oracle Database 11g, then an external provider for OracleTextSearch must be configured. The driver jar ojdbc6.jar is provided by Oracle in the MW_HOMEwlserver_ 10.3serverlib directory. You can specify a separate Oracle Database as the value of IndexerDatabaseProviderName, instead of SystemDatabase. Managing Search Tools 7-3 3. Save the file. 4. Restart the Oracle Content Server instance. 5. Rebuild the search index. For more information on rebuilding the index, see Section 4.2.2, Working with the Search Index. For more information on configuring Oracle Content Server and OracleTextSearch during installation, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.

7.1.3 Oracle Text 11g Features and Benefits