After implementing a custom content crawler, you must deploy your code.
To deploy a .NET content crawler, add a line to the deployment file (web.config) that specifies the fully qualified name of the class. For a content crawler, enter values for the following parameters, as shown in the code that follows.
... <appSettings> <add key='ContainerProviderAssembly' value='CompanyStoreCWS'/> <add key='ContainerProviderImpl' value='Plumtree.CompanyStore.CWS.CompanyStoreContainer'/> <add key='DocumentProviderAssembly' value='CompanyStoreCWS'/> <add key='DocumentProviderImpl' value='Plumtree.CompanyStore.CWS.CompanyStoreDocument'/> ...
If the content crawler uses DocFetch, you must also deploy your DocFetch code. Add a line to the deployment file (web.config) that specifies the fully qualified name of your class and the associated assembly (DocFetchImpl and DocFetchAssembly). You must also add three additional parameters to the web.config deployment descriptor:
... <appSettings> <add key='DocFetchAssembly' value='MyDocFetch' /> <add key='DocFetchImpl' value='com.mycompany.MyDocFetchProvider' /> <add key='DocFetchURL' value='iis/docfetch.aspx'/> <add key='IndexFilePath' value='D:\\root\\config\\mydomain'/> <add key='IndexURLPrefix' value='http://yourhost/IISVirtualDirectory'/> ...
For details on configuring your crawler, see Configuring Content Crawlers.