How to Set Up the Notification Index
ID: Q163469
|
The information in this article applies to:
-
Microsoft Site Server version 3.0
SUMMARY
This article explains how to set up the notification index, using Site
Server 3.0 Content Deployment as the notification source.
MORE INFORMATION- Save the Setpropdest.vbs file to your <siteserver dir>\bin directory.
The Setpropdest.vbs file is available at the end of this article.
- Start Notepad.
- Copy and paste the SetPropDest.vbs information below.
- The beginning of the line is:
Sub Usage
The end of the line is:
call Main
- Save the file as SetPropDest.vbs in the <siteserver dir>\bin
directory.
- Start the Microsoft Management Console (MMC). Go to Search, select
Catalog Build Server property, and then select <Catalog>. Select
Propagation.
- Add the name of your search server and enable it by selecting the check
box.
- Go to a command prompt and create a directory called c:\prop (or a
different directory of your choice).
- Go to <siteserver dir>\bin and run the following:
cscript setpropdest.vbs <catalogname> <search server name> c:\prop.
NOTE: Your search server name is the one you added in step 3.
- Rebuild the catalog. This will put all the related indexed files in
c:\prop.
- Go to the MMC. Click Publishing, click Projects, and click Project
Wizard. This creates a Content Deployment project that will prop the
catalog from c:\prop to ..\drop directory on your search server.
- Specify the source directory, which is c:\prop.
- Specify the destination directory, which is
<siteserver dir>\data\search\projects\<catalog name>\search\drop.
Please consult the Site Server online documentation for more
information about creating a content deployment project.
- Go to your search server.
- Go to <siteserver dir>\bin and run the following command:
cscript sssadmin.vbs add catalog /catalog:<catalog> /build:false
/search:true
NOTE: This creates the directory structure for Content Deployment to
replicate to.
- If the deployment is through a firewall, make sure the port 507 is
open on the firewall.
- Go back to the gatherer server and run the Content Deployment project.
- Go back to the search server, go to the MMC, and press F5 to refresh
and manually enable the catalog.
SetPropDest.vbs Starts Here
Sub Usage
WScript.Echo "Usage: setpropdest <catalog> <search server>
<destinationdir>"
WScript.Quit(1)
end Sub
Sub Main
On Error Resume Next
if WScript.Arguments.Count <> 3 then
Usage
end if
Set objHost = WScript.CreateObject("Search.SearchAdmin.1")
if not IsObject(objHost) then
WScript.echo "Cannot connect to host"
WScript.Quit(1)
end if
Set objBuildServer = objHost.BuildServer
if not IsObject(objBuildServer) then
WScript.echo "Cannot connect to build server"
WScript.Quit(1)
end if
Set objBuildCatalogs = objBuildServer.BuildCatalogs
if not IsObject(objBuildCatalogs) then
WScript.echo "Cannot connect to catalogs"
WScript.Quit(1)
end if
Set objBuildCatalog = objBuildCatalogs.Item( WScript.Arguments(0) )
if not IsObject(objBuildCatalog) then
WScript.echo "Cannot obtain catalog " & WScript.Arguments(0)
WScript.Quit(1)
end if
Set objSearchServers = objBuildCatalog.SearchServers
if not IsObject(objSearchServers) then
WScript.echo "Cannot obtain Search Servers"
WScript.Quit(1)
end if
set objSearchServer = objSearchServers.Item( WScript.Arguments(1) )
if not IsObject(objSearchServer) then
WScript.echo "Cannot obtain Search Server : " &
WScript.Arguments(1)
WScript.Quit(1)
end if
wscript.echo "Search Server Name :" &
objSearchServer.Name
wscript.echo "Search Server Prop Destination :" &
objSearchServer.PropDestination
wscript.echo "Setting destination to : " & WScript.Arguments(2)
objSearchServer.PropDestination = WScript.Arguments(2)
wscript.echo "Search Server Prop Destination :" &
objSearchServer.PropDestination
End Sub
call Main
NOTE: The above sample code is provided for demonstration purposes only.
Additional query words:
Keywords : prodsitesrv3 prodsrch prodCD
Version : WinNT:3.0
Platform : WINDOWS
Issue type : kbhowto
|