On the machine that is running the indexing tools, you can install additional iFilters to
allow documents of a set type to be searched using Search 360 and Full-Text search. These
third-party iFilters can support additional document types or metadata from the standard iFilters
that are supplied with the operating system.
About this task
iFilters are used to access documents and store the details in the index. You can see the
iFilters that you currently have installed and associated with specific files using the
Indexing Options in the control panel for your operating system all the files
are listed in .
Note: If an iFilter is installed after the index is built, the index will need to be rebuilt for the
document type fields before the document will be indexed correctly.
Procedure
- Install a supported iFilter on the machine that is running the index.
- For Search 360, this should be the Search Indexer machine.
- For Full Text Search, this should be the SQL Server.
Note: If you have installed the 64-bit Adobe PDF iFilter download, set the SYSTEM PATH environment
variable to the bin directory of the iFilter installation.
- For Full-Text Search you need to complete one or more extra steps depending on which
iFilter you installed:
- If you have installed any PDF iFilter (or other iFilter that does not have a signed
binary) run the following command in SQL Server Management Studio for your instance:
exec sp_fulltext_service 'verify_signature', 0;
- If you have installed any new iFilter, run the following command in SQL Server
Management Studio for your instance:
exec sp_fulltext_service 'load_os_resources', 1;
- Stop and restart the SQL Server service.
- Rebuild the Full Text Search index in iBase Designer to include the
documents.
Note: To determine which file extensions the iBase database currently has iFilters for, you can run
the following SQL
Script:
select document_type, path from sys.fulltext_document_types;
