FP97:How to Use FrontPage with Microsoft Index Server on IIS 3.0

ID: q166357

The information in this article applies to:

Microsoft FrontPage 97 for Windows with Bonus Pack

SUMMARY

Microsoft Index Server version 1.1 is a content-indexing and search component included with Microsoft Internet Information Server (IIS) 3.0. When the FrontPage 97 Server Extensions are installed with IIS 3.0, the WebBot Search Component uses the document index and search component of Index Server. When Index Server is used with IIS virtual servers and FrontPage there are special considerations. This article describes the interaction between FrontPage, Index Server, and IIS virtual servers.

MORE INFORMATION

Installing Index Server for Virtual Servers

For information about installing the Index Server, visit the following Microsoft World Wide Web site:

   http://www.microsoft.com/ntserver/search/index2/ixinstal.asp

Creating and Associating a Catalog for Each Virtual Server

Using the Index Server Administration HTML pages, check the list of virtual roots to be indexed in the catalog and remove any virtual roots you do not want to include in the catalog. Common roots (virtual roots without specific IP addresses) are indexed in all catalogs by default.

Force the creation of the catalog by browsing to the virtual server and attempting a search.

Issues

FrontPage creates an Internet data query (.idq) file in the _vti_bin directory for each page that contains a WebBot Search component. To properly associate the query with the catalog for the virtual server, edit the "filename.htm0.idq" file so the CiCatalog parameter correctly specifies the catalog for that virtual server. This file is deleted and recreated automatically when you use the Recalculate Hyperlinks command on the Tools menu in FrontPage Explorer. Because the file is deleted by the SYSTEM account, there is no way to adequately protect it using Windows NT permissions.

If the CiCatalog parameter in the filename.htm0.idq file does not specifically name a catalog for the virtual server, the default catalog is used. The default catalog is identified in the following registry subkey:

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\contentindex
   \IsapiVirtualServerCatalogs\{default}.

By design, only ten files are returned as part of the search results. The search caption lists the total number of files that match the query, but ten is the maximum number of file names that are returned. The number of files returned can be changed by updating the CiMaxRecords InResultSet variable in the filename.htm0.idq file. All changes to the _vti_bin/filename.htm0.idq file will be lost the next time you use the Recalculate Hyperlinks command.

If you want to avoid using the WebBot Search component, you may design a custom form linked to an .idq file in a directory other than _vti_bin.

The catalog can be updated from the Index Server Administration page by performing an incremental directory scan and merging the index. The scan and merge operations are performed automatically as defined by the registry entries ForcedNetPathScanInterval and MasterMergeTime. The default interval for ForcedNetPathScanInterval is 120 minutes and the default for MasterMergeTime is 0:00.

For additional information about using Microsoft Index Server with FrontPage, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q181204
   TITLE     : FP: Using FrontPage Search Engine Instead of MS
               Index Server

Additional query words: 97 tripoli

Keywords          : kbinterop kbdta fpinterop fpext 
Version           : windows:97
Platform          : WINDOWS
Hardware          : x86
Issue type        : kbhowto

Last Reviewed: July 1, 1999