How FTS indexing works for attachments

Full text search (FTS) indexing for attachments is done on a per-field basis and is not based on the attachment pool. This means you can index specific attachment fields within a pool, which allows for better organization and efficiency.

Identify all the attachment fields you want to index for FTS and group them under a single attachment pool for clarity.

Avoid setting the FTS index property on those attachment fields that will never be used for searching. For example, all the attachments containing documents with textual content, such as PDF or Word, can be enabled for FTS indexing and grouped under a single attachment pool. All the attachments that hold non-textual data, such as images or other formats holding binaries (media files or zip files containing media content), should not be set for FTS indexing and should be grouped together in a separate attachment pool.


Related topics

How-FTS-indexing-works

Full-text-search-indexer-logging

Handling unsupported formats

Attachments in unsupported formats are not indexed successfully. If an attachment cannot be indexed, the Full Text Indexer log indicates this issue, not the error log. For more information, see Full-text-search-indexer-logging.


Supported File Formats for FTS Indexing

The following formats are supported for FTS of attachment files:

  • Hypertext markup language (HTML) format
  • XML and derived formats
  • Microsoft Office document formats (Word 97 and later--see the note that follows)
  • OpenDocument format (OpenOffice 1.0 and later--see the note that follows)
  • Portable document format (PDF) (versions 1.0 through 9.0)
  • Electronic publication format (digital books)
  • Rich text format (RTF)
  • Compression and packaging formats (.zip, .tar, .bzip2, .ar, .cpio )
  • Text formats (Most Unicode and ISO 8859 documents in plain text)

New versions of file formats for vendor products are assumed to be compatible with previously supported versions. In the event that a vendor does not provide backward compatibility, BMC reserves the right to rescind support for a specified version of a vendor's product and document such incompatibilities once confirmed. BMC might, at BMC's discretion, attempt to address a discovered incompatibility by modifying the current version of AR System server. However, if major architectural changes in a vendor product require significant BMC development to achieve tolerance, support for the vendor product may be deferred to a later version of AR System server.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*