On the Global Settings page of QuickFinder Server Manager, click Manage in the row of the virtual search server that you want to work with.

Under Define a New Index, click New crawled index, then click Define Index.

In the Index Name field, specify a name for your index.

A name can be a word, phrase, or a numeric value. If the virtual search server you are working on contains, or will contain, a large number of indexes, you might want to use a numbering scheme to help you manage multiple indexes more effectively. However, the name you specify here appears on the default search page, so you might want to choose a name that can be understood by users of your search services.

Under Web Sites to Crawl, specify the URL of the Web site that you want indexed.

You can specify just the URL, such as www.mycompany.com, or you can also append a complete path, down to the file level, such as www.mycompany.com/path/index.html.

If desired, add another URL.

To add additional URLs, click Add More URLs.

Click Apply Settings.

On the Global Settings page of QuickFinder Server Manager, click Manage in the row of the virtual search server that you want to work with.

Under Define a New Index, click New crawled index, then click Define Index.

On the Define Crawled Index page, click Advanced Index Definition.

In the Index Name field, specify a name for your new index.

A name can be a word, phrase, or a numeric value. If the virtual search server you are working on contains, or will contain, a large number of indexes, you might want to use a numbering scheme to help you manage multiple indexes more effectively. However, the name you specify here appears on the default search page, so you might want to choose a name that can be understood by users of your search services.

In the Index description field, specify an optional description of the index to be created.

Under Web Sites to Crawl, specify the URL of the Web site to be indexed.

If you specify a filename at the end of the URL, just that file is indexed.

(Optional) Use the Path Weight option to boost or degrade search results based on the path.

A weight of 100 makes the path’s relevance normal. Increasing the weight makes the path more relevant, and lowering the weight makes the path less relevant.

(Optional) Select Use only as a crawl filter if you don't want QuickFinder to use the URL you specified in the URL of Web Site field to begin indexing.

Any subsequent links found that contain a URL matching the one you specified in the URL of Web Site field are followed and subsequently indexed.

(Optional) If you want to mask the actual URL displayed in the search results template, specify an alternate URL in the Show URL in search results as field.

For example, if you want to index a Web server that is used inside of your company but only allow your customers access to some of the data, you could hide the actual internal URL with the URL of your public Web site.

In the Subdirectories to exclude text box, specify the directories that you want QuickFinder not to index.

For example, /marketing or /sales/doc.

To direct QuickFinder to include or exclude specific file types, click Extensions to include or Extensions to exclude and then specify the extensions, such as HTM PDF TXT, separating each one with a single space.

To add additional URLs, click Define More Web Sites.

To delete a URL, select it and click Remove Web Site.

In the Additional URLs text box, specify any other URLs that you want indexed (for example, www.mycompany.com/marketing).

This allows you to specify additional areas of information found on other Web sites, but not include all of the content of those sites to your searches.

When QuickFinder encounters links found in the pages of Additional URLs that point to pages specified in Web Sites to Crawl, QuickFinder follows those links. All other links that go outside of Web Sites to Crawl are not followed.

Use the Off-Site URLs option to determine the maximum number of off-site URLs (those URLs not located within any of the URLs specified in Web Sites to Crawl) that QuickFinder should index.

In the URLs to Exclude field, list the off-site URLs that you want to exclude from indexing.

Use the Adjust Individual URL Relevance option to adjust the relevance of individual items within the index.

Adjustment values can range from 1 to 200. Values higher than 100 increase the calculated relevance of the item on the search results page, and values lower than 100 decrease the calculated relevance of the item. The value specified here is combined with other values to determine the final relevance.

Under Additional Settings, specify the absolute path to where you want the index files stored in the Location of Index Files field.

For example, volume:\searchroot\sites\mysites.

By default, index files are stored at volume:\searchroot\sites\default\indexes\ on Netware and /var/lib/qfsearch/Sites/default/indexes\index_name on Linux.

Changes made to Additional Settings override Default Settings.

From the Level of detail in indexing logs drop-down list, select the amount of information you want included in the index logs.

From the Encoding (if not in META tags) drop-down list, select the encoding to be used by files being indexed that do not contain an encoding specification.

In the Field names to display on Search Results pages field, list any field names that you want to be included on the search results page (for example, author date_created product dc.copyright).

To display the field on the search results pages, add the corresponding $$Variable to the template (for example, $$author $$date_created $$product $$copyright).

Use the Index Weight option to boost or degrade search results based on the item's index.

A weight of 100 makes the item's relevance normal. Increasing the weight makes the item more relevant, and lowering the weight makes the item less relevant.

In the Maximum index depth field, specify the number of jumps (or links) from the starting URL that QuickFinder should crawl.

In the Maximum file size to index field, specify the maximum file size (in bytes) that QuickFinder should index.

Files exceeding this size are not indexed and are not included in search results.

In the Maximum time to download a URL field, specify a number (in seconds) before QuickFinder automatically skips the indexing of the specified URL.

In the Delay between URL requests field, specify the amount of time (in milliseconds) QuickFinder should delay before attempting to index a URL.

To direct QuickFinder to pay attention to the case of filenames and directory names, click Yes next to URLs are case sensitive.

To direct QuickFinder to crawl dynamic content (URLs containing the question mark [?]), click Yes next to Crawl dynamic URLs.

For more information about indexing dynamic content, see Section 8.7, Indexing Dynamic Web Content.

Click Yes next to Obey Robots.txt exclusions when crawling if you want QuickFinder to following instructions found in any Robots meta tags.

For more information, see Using the Robots Meta Tag.

Click Yes next to Index may be copied to other clustered servers if you want to allow this index to be copied to other servers in a QuickFinder Synchronization cluster.

For more information about QuickFinder Synchronization, see Section 9.0, Synchronizing Data Across Multiple QuickFinder Servers.

Click Yes to activate the newly generated index irrespective of the size.

The default option is No for the Always activate new index option. If it is set to No, then the newly generated index is compared with the current one. If the size of the new index is small when compared to the existing one, an error message is displayed in the Admin console.

If the URLs to be crawled require authentication, use the Type of Authentication required to crawl web site option to select the methods for providing the correct user credentials.

(Optional) If the Web sites you are indexing require users to log in at a specific URL (such as login.digitalairlines.com), specify the login URLs in the Alternate Login URLs field.

After the session cookies are returned, QuickFinder sends the appropriate cookies as needed to the Web sites being indexed.

Select Yes next to Use Crawler Credentials when Highlighting to use the Crawler Credentials specified Step 31 instead of the search user's credentials when requesting the specified documents.

In the HTTP Headers field, specify any additional headers and values you want included with each HTTP request, placing each header on a separate line.

Some Web sites require specific information in HTTP headers when attempts are made to access them. If your Web site uses form-based or cookie-based authentication, you can specify the information here.

Click Apply Settings.

On the Global Settings page of QuickFinder Server Manager, click Manage in the row of the virtual search server that you want to work with.

Under Define a New Index, select New crawled index, then click Define Index.

On the Define Crawled Index page, click Advanced Index Definition.

Under Rights-based Search Results, configure authorization checking by selecting one of the following options:

From the Unauthorized hits filtered by drop-down list, select one of the following filters:

Click Apply Settings.

On the Global Settings page of QuickFinder Server Manager, click Manage in the row of the virtual search server that you want to work with.

Under Define a New Index, click New file system index, then click Define Index.

In the Index Name field, specify a name for your index.

A name can be a word, phrase, or a numeric value. If the virtual search server you are working on contains, or will contain, a large number of indexes, you might want to use a numbering scheme to help you manage multiple indexes more effectively. However, the name you specify here appears on the default search page, so you might want to choose a name that can be understood by users of your search services.

In the Server Connection field, select Yes if the files to be indexed are on an NCP™ server, then specify the NCP server name, a valid username, password, and the character set of the server.

The user must have at least read rights to all the files. If you want to do rights-based searches, the user must have administrator rights to the NCP server.

The Server Charset option must be set correctly so that the URLs can be properly encoded (according to the server encoding).

This option is useful if you have a local NSS volume on the same machine as your QuickFinder index and you want to create a rights-based search for your users, or if you have a local or remote NCP server (such as a NetWare server, another server with NCP on it, or a local indexing machine) and you want to centralize your indexing.

If you choose this option, make sure that the Corresponding URL Prefix option in the Path Information section contains a complete URL so that your users can access the indexed files from the NCP server. Also, if you are planning on indexing a large number of files (for example, over a million), your system should have at least 2 GB of memory.

In the Server path to be indexed field, specify the absolute path to the folder containing the information that you want indexed (for example, sys:\sales\reports).

In the Corresponding URL prefix field, specify the URL that should be used by the search results page to access the individual files (for example, /sales).

You can also specify a file URL containing the UNC path of the server and path. The syntax is file://///server-dns-name/volume/path.

If the filename contains non-ASCII characters, set the return encoding of the Search Result page to match the encoding of the client's machine. You can set the return encoding on the General Settings page, or the client can set it by specifying the value of the encoding being sent to the search server in the retencoding search parameter. For example, the default English Windows^* encoding is Windows-1252, and Japanese is Shift-Jis. In order for the page to open, the client must already be authenticated to the server that the path points to.

To add additional paths, click Add More Paths.

Click Apply Settings.

On the QuickFinder Server Manager Global Settings page, click Manage in the row of the virtual search server that you want to work with.

Under Define a New Index, click New file system index, then click Define Index.

On the Define File System Index page, click Advanced Index Definition.

In the Index Name field, specify a name for your new index.

A name can be a word, phrase, or a numeric value. If the virtual search server you are working on contains, or will contain, a large number of indexes, you might want to use a numbering scheme to help you manage multiple indexes more effectively. However, the name you specify here appears on the default search page, so you might want to choose a name that can be understood by users of your search services.

In the Index description field, specify an optional description of the index to be created.

In the Server Connection field, select Yes if the files to be indexed are on an NCP server, then specify the NCP server name, a valid username, password, and the character set of the server.

The user must have at least read rights to all the files. If you want to do rights-based searches, the user must have administrator rights to the NCP server.

The Server Charset option must be set correctly so that the URLs can be properly encoded (according to the server encoding).

This option is useful if you have a local NSS volume on the same machine as your QuickFinder index and you want to create a rights-based search for your users, or if you have a local or remote NCP server (such as a NetWare server, another server with NCP on it, or a local indexing machine) and you want to centralize your indexing.

If you choose this option, make sure that the Corresponding URL Prefix option in the Path Information section contains a complete URL so that your users can access the indexed files from the NCP server. Also, if you are planning on indexing a large number of files (for example, over a million), your system should have at least 2 GB of memory.

Under Path Information, specify the absolute path to the folder containing the information that you want indexed in the Server path field (for example, sys:\sales\reports).

(Optional) Use the Path Weight option to boost or degrade search results based on the path.

A weight of 100 makes the path’s relevance normal. Increasing the weight makes the path more relevant, while lowering the weight makes the path less relevant.

In the Corresponding URL prefix field, specify the URL that should be used by the search results page to access the individual files (for example, /sales).

You can also specify a file URL containing the UNC path of the server and path. The syntax is file://///server-dns-name/volume/path.

If the filename contains non-ASCII characters, set the return encoding of the Search Result page to match the encoding of the client's machine. You can set the return encoding on the General Settings page, or the client can set it by specifying the value of the encoding being sent to the search server in the retencoding search parameter. For example, the default English Windows encoding is Windows-1252, and Japanese is Shift-Jis. In order for the page to open, the client must already be authenticated to the server that the path points to.

To exclude specific subdirectories from being indexed, specify their relative paths in the Subdirectories to exclude field.

To direct QuickFinder to include or exclude specific file types, click Extensions to include or Extensions to exclude and then type the extensions, separating each one with a single space, such as HTM PDF TXT.

(Optional) To add additional paths, click Define More Paths.

(Optional) To delete a path, select it and click Remove Path.

Use the Adjust Individual File Relevance option to adjust the relevance of individual items within the index.

Adjustment values can range from 1 to 200. Values higher than 100 increase the calculated relevance of the item on the search results page, and values lower than 100 decrease the calculated relevance of the item. The value specified here is combined with other values to determine the final relevance.

In the Location of index files field, specify the absolute path to where you want the index files stored.

For example, sys:\qfsearch\sites\mysites on NetWare or /var/lib/qfsearch/sites/mysites on Linux.

By default, index files are stored at volume:\searchroot\sites\site_name\ indexes\.on NetWare or /var/lib/qfsearch/Sites/default/indexes/index_name on Linux

From the Level of detail in indexing logs drop-down list, select the amount of information you want included in the index logs.

From the Encoding (if not in META tags) drop-down list, select the encoding to be used when indexing files that do not contain an encoding specification.

For example, HTML files can specify their encoding with a Content-Type meta tag.

In the Field names to display on Search Results pages field, list any field names that you want to be included on the search results page (for example, author date_created product dc.copyright).

To display the field on the search results pages, add the corresponding $$Variable to the template (for example, $$author $$date_created $$product $$copyright).

The field data is stored in the index and causes the index size to increase.

Use the Index Weight option to boost or degrade search results based on the item's index.

A weight of 100 makes the item's relevance normal. Increasing the weight makes the item more relevant, and lowering the weight makes the item less relevant.

In the Maximum index depth field, specify the number of directories from the starting directory QuickFinder should search.

This lets you limit how far (or deep) into a file server QuickFinder should search.

In the Maximum file size to index field, specify the maximum file size (in bytes) that QuickFinder should index.

Files exceeding this size are not indexed and are not included in search results.

(Optional) Click Yes next to Index may be copied to other clustered servers if you want this index shared with other QuickFinder servers in a QuickFinder Synchronization cluster.

For more information about QuickFinder Synchronization, see Section 9.0, Synchronizing Data Across Multiple QuickFinder Servers.

Click Yes to activate the newly generated index irrespective of the size.

The default option is No for the Always activate new index option. If it is set to No, then the newly generated index is compared with the current one. If the size of the new index is small when compared to the existing one, an error message is displayed in the Admin console.

Click Apply Settings.

On the QuickFinder Server Manager Global Settings page, click Manage in the row of the virtual search server that you want to work with.

Under Define a New Index, select New file system index, then click Define Index.

On the Define File System Index page, click Advanced Index Definition.

Under Rights-based Search Results, configure authorization checking by selecting from one of the following options:

From the Unauthorized hits filtered by drop-down list, select one of the following filters:

Click Apply Settings.