Source code of Windows XP (NT5)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

175 lines
14 KiB

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<title>Microsoft Index Server Guide: Installing Microsoft Index Server</title>
<meta name="FORMATTER" content="Microsoft FrontPage 1.1">
<meta name="GENERATOR" content="Microsoft FrontPage 1.1">
</head>
<body bgcolor="#FFFFFF">
<!--Headerbegin--><p align=center><a name="TOP"><img src="onepix.gif" alt="Space" align=middle width=1 height=1></a> <a href="default.htm#Top"><img src="toc.gif" alt=" Contents" align=middle border=0 width=89 height=31></a> <a href="intro.htm"><img src="previous.gif" alt="Previous" align=middle border=0 width=32 height=31></a> <a href="queryhlp.htm"><img src="next.gif" alt="Next" align=middle border=0 width=32 height=31></a> </p>
<hr>
<!--Headerend--><p><a name="InstallingMicrosoftIndexServer"><font size=6><strong>Installing Microsoft Index Server</strong></font></a></p>
<p align=left><!--Chaptoc--></p>
<blockquote>
<p><a href="install.htm#InstallationRequirements">Installation Requirements</a> <br>
<a href="install.htm#InstallationNotes">Installation Notes</a> <br>
<a href="install.htm#RecommendedConfiguration">Recommended Configuration</a> <br>
<a href="install.htm#Samples">Samples</a> <br>
<a href="install.htm#PerformanceNotes">Performance Notes</a> <br>
</p>
</blockquote>
<hr>
<!--ChaptocEnd--><p align=left>This page describes how to install Microsoft Index Server and get it quickly setup to work for you. Just start the installation
program, point to the <a href="/samples/search/query.htm">sample search page</a> from your home page, and issue a query.</p>
<hr>
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="InstallationRequirements">Installation Requirements</a></h1>
<ul>
<li><p align=left>Before installing Index Server, you must have successfully installed: </p>
<ul>
<li><p align=left>Microsoft&#174; Internet Information Server (IIS) version 2.0 on Microsoft&#174; Windows NT&#174; Server version 4.0 </p>
<p align=left>&#151;Or&#151; </p>
</li>
<li><p align=left>Microsoft Peer Web Services (PWS) on Microsoft Windows NT Workstation version 4.0 </p>
</li>
</ul>
</li>
<li><p align=left>On Microsoft Windows NT Server, the minimum hardware required for Index Server is same as that for IIS. On
Microsoft Windows NT Workstation, you need 16 megabytes of RAM minimum. </p>
</li>
<li><p align=left>Index Server program files require anywhere from 3 to 12 megabytes of disk space, depending upon the number of
languages installed. Index Server can index documents in several different languages. </p>
</li>
<li><p align=left>Disk space needed for storing Index Server data depends upon the size of the corpus and type of documents. The free
disk space must be roughly 40 percent of the size of the corpus. </p>
</li>
<li><p align=left>For security reasons, it is recommended that Index Server data be stored on a Windows NT File System (NTFS)
drive. For more information on security, see the <a href="sechelp.htm">Security</a> page in the Microsoft Index Server Guide. </p>
</li>
<li><p align=left>The optimum configuration depends upon the size of the corpus, number of documents, and the search load on the
server. More memory and faster processors make indexing and querying faster. For details on configuring your
computer for Index Server, see <a href="#RecommendedConfiguration">Recommended Configuration</a> later on this page. </p>
</li>
</ul>
<hr>
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="InstallationNotes">Installation Notes</a></h1>
<h2 align=left>Downloading from the Web</h2>
<p align=left>You can download the following self-extracting executable files (program files):</p>
<div align=left>
<table border=1 cellpadding=5 cellspacing=0 width=100%>
<tr><th align=left valign=bottom width=40%><font size=2>Executable File Name</font></th><th align=left valign=bottom width=60%><font size=2>Contains Executable Files and Language Resources For</font></th></tr>
<tr><td valign=top width=40%><font size=2>Idxsvall.exe</font></td><td valign=top width=60%><font size=2>All the supported languages</font></td></tr>
<tr><td valign=top width=40%><font size=2>Idxsvenu.exe</font></td><td valign=top width=60%><font size=2>U.S. English</font></td></tr>
<tr><td valign=top width=40%><font size=2>Idxsveng.exe</font></td><td valign=top width=60%><font size=2>International English</font></td></tr>
<tr><td valign=top width=40%><font size=2>Idxsvdeu.exe</font></td><td valign=top width=60%><font size=2>German</font></td></tr>
<tr><td valign=top width=40%><font size=2>Idxsvesn.exe</font></td><td valign=top width=60%><font size=2>Spanish</font></td></tr>
<tr><td valign=top width=40%><font size=2>Idxsvita.exe</font></td><td valign=top width=60%><font size=2>Italian</font></td></tr>
<tr><td valign=top width=40%><font size=2>Idxsvnld.exe</font></td><td valign=top width=60%><font size=2>Dutch</font></td></tr>
<tr><td valign=top width=40%><font size=2>Idxsvsve.exe</font></td><td valign=top width=60%><font size=2>Swedish</font></td></tr>
</table>
</div>
<p align=left>After downloading one or more of the above self-extracting executable files, you can then run the program.</p>
<h2 align=left>Installation Parameters</h2>
<p align=left>When setting up Index Server, you will be asked where to put the following components of Index Server:</p>
<ul>
<li><p align=left>Sample query pages. The sample pages will be referenced by the virtual path /Samples/Search. </p>
</li>
<li><p align=left>Sample query scripts. The sample scripts that work with the sample pages are referenced by the virtual path
/Scripts/Samples/Search. </p>
</li>
<li><p align=left>Data (the indexes). There must be <a href="#diskspace">sufficient free space</a> on this drive. </p>
</li>
</ul>
<p align=left>To take full advantage of Windows NT security, you should put all these paths on an NTFS drive. The location is very
important because that is where Index Server data is stored. If you choose an NTFS drive, Setup automatically sets the
appropriate security on Index Server catalog pages. For more information on security, please refer to the Index Server
<a href="sechelp.htm">Security</a> page.</p>
<p align=left>The drive on which Index Server data is stored must have enough free space. The default installation will configure all
<em>readable</em> virtual paths to be indexed, which implies that the free space must be roughly 40% of <em>all</em><em><strong> </strong></em>the virtual paths. <a href="adminhlp.htm#AddVRoot">To
selectively enable indexing</a> on particular roots only, see the <a href="adminhlp.htm">Basic Administration</a> page.</p>
<h2 align=left><a name="StartAndStop">Starting and Stopping </a>Index Server</h2>
<p align=left>After installing Index Server, you can start by issuing a query. The <a href="/samples/search/query.htm">sample query</a> pages are a good starting point.</p>
<ol>
<li><p align=left>Click Start and then choose Programs. </p>
</li>
<li><p align=left>Choose Microsoft Index Server, and point to Sample Query Form. </p>
</li>
<li><p align=left>On the sample query form, type a word or phrase to seach for and click the Execute Query button. </p>
</li>
</ol>
<p align=left><font color="#FF0000"><em>Please note that Index Server is not started automatically when IIS or PWS is started.</em> </font><font color="#400040">The first query against a particular
</font><a href="cathlp.htm"><font color="#400040">Index Server configuration</font></a><font color="#400040"> starts the indexing process for that data set. Index Server is stopped when IIS or PWS is stopped.
There is no way to stop only Index Server.</font></p>
<hr>
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="RecommendedConfiguration">Recommended Configuration</a></h1>
<p align=left>The minimum configuration requirements for Index Server are basically same as for Microsoft Windows NT Server but the
configuration for optimum performance depends upon the number of documents, size of the data corpus, and the rate of
queries. A 486/DX4-100 computer with 32 megabytes of memory running Windows NT Server 4.0 serviced queries well if
the number of simultaneous queries is not too high. For a small organization, this may be sufficient; but for a larger group
serving more users, better hardware is recommended.</p>
<p align=left>The recommended configuration for Index Server depends upon the following factors:</p>
<ul>
<li><p align=left>Number of documents in the corpus </p>
</li>
<li><p align=left>Size of the corpus </p>
</li>
<li><p align=left>Rate of search requests arriving at the server </p>
</li>
<li><p align=left>Kind of queries. Complex queries will run faster on a computer with a faster CPU </p>
</li>
</ul>
<p align=left>The following table shows recommended memory configuration based on the number of documents. The size of the corpus
affects the disk space needed for storing Index Server data. The <a name="diskspace"><em>disk space</em></a> needed for Index Server data in all the cases is
approximately<strong> </strong><em>40% of the size of the corpus</em>. While the <em>average usage</em> is less than <em>30% of the corpus</em>, the <em>peak usage</em> of
disk space can be <em>40%</em>.</p>
<table border=1 cellpadding=5 cellspacing=0 width=100%>
<tr><th align=left valign=bottom width=33%><font size=2>Number of Documents </font></th><th align=left valign=bottom width=33%><font size=2>Minimum Memory <br>
(in megabytes)</font></th><th align=left valign=bottom width=33%><font size=2>Recommended Memory <br>
(in megabytes)</font></th></tr>
<tr><td valign=top width=33%><font size=2>Fewer than 10,000</font></td><td valign=top width=33%><font size=2>16 for Workstation<br>
32 for Server</font></td><td valign=top width=33%><font size=2>Same as minimum</font></td></tr>
<tr><td valign=top width=33%><font size=2>Fewer than 100,000</font></td><td valign=top width=33%><font size=2>32 </font></td><td valign=top width=33%><font size=2>32 </font></td></tr>
<tr><td valign=top width=33%><font size=2>100,000-250,000</font></td><td valign=top width=33%><font size=2>32 </font></td><td valign=top width=33%><font size=2>64-128 </font></td></tr>
<tr><td valign=top width=33%><font size=2>250,000-500,000</font></td><td valign=top width=33%><font size=2>64 </font></td><td valign=top width=33%><font size=2>128-256 </font></td></tr>
<tr><td valign=top width=33%><font size=2>500,000 or more</font></td><td valign=top width=33%><font size=2>128</font></td><td valign=top width=33%><font size=2>256 or more</font></td></tr>
</table>
<p align=left>A faster CPU and more memory improves the performance of indexing as well as speed of queries. If the number of
documents is very large, not having enough memory will seriously affect performance. If you see that performance is slow
when Index Server is running, add more memory to improve the situation.</p>
<hr>
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="Samples">Samples</a></h1>
<p align=left>With Index Server, you can design sophisticated query forms. Take a look at the default samples to see how to write query
forms.</p>
<blockquote>
<p align=left><strong>Note</strong>&#160;&#160;&#160;<em>Sample sites, applications, and pages included in this software are provided as examples only,
and are not intended for use as, or as the basis for creation of, production-quality server applications.</em></p>
</blockquote>
<p align=left>The <a href="/samples/search/query.htm">simple query</a> form query the entire corpus. See the <a href="qrylang.htm">Query Language</a> page for details on creating complex queries.</p>
<p align=left>In addition to the simply query form, other sample pages show the power of Index Server to do <a href="qrylang.htm">complex queries</a>. With
complex queries, you can search for keywords, phrases, proximity, and also restrict the results based on properties such as <a href="/samples/search/filesize.htm">file
size</a>, <a href="/samples/search/filetime.htm">last write time</a>, and so on. You can configure the <a href="/samples/search/author.htm">author sample page</a> to restrict the results to documents written by a
particular author or authors.&#160;</p>
<hr>
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="PerformanceNotes">Performance Notes</a></h1>
<p align=left>This section answers some technical questions about Index Server and how it works.</p>
<ul>
<li><p align=left>Index Server will index roots that do not have read permissions, but that are physically located beneath a root with read
permission enabled. A workaround is to append the root to a restriction. For example, you can mask an unreadable
root named /_unreadable by setting the CiRestriction in the .idq file to: CiRestriction=(%UserRestriction%) &amp;! #vpath
*\_unreadable\*. </p>
</li>
<li><p align=left>Index Server does not support physical paths longer than the Windows NT shell limit (260 characters). &#160; </p>
</li>
<li><p align=left>A Uniform Resource Locator (URL) or a form-based query can send up to 4 kilobytes (K) of data. If a query larger
than 4K is sent, the behavior is unpredictable. The query size includes all variables sent from the browser to the .idq file. </p>
</li>
</ul>
<!--Footerbegin--><hr>
<p align=center><a href="default.htm#Top"><img src="toc.gif" alt=" Contents" align=middle border=0 width=89 height=31></a> <a href="intro.htm"><img src="previous.gif" alt="Previous" align=middle border=0 width=32 height=31></a> <a href="#TOP"><img src="up_end.gif" alt="To Top" align=middle border=0 width=32 height=31></a> <a href="queryhlp.htm"><img src="next.gif" alt="Next" align=middle border=0 width=32 height=31></a></p>
<hr>
<p align=center><em>&#169; 1996 by Microsoft Corporation. All rights reserved.</em> <!--Footerend--></p>
</body>
</html>