Oracle WebCenter Interaction Web Service Development Guide

     Previous Next  Open TOC in new window   View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Deploying a Custom Content Crawler (.NET)

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.


  • ContainerProviderImpl
  • DocumentProviderImpl
  • ContainerProviderAssembly
  • DocumentProviderAssembly
... 
<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:


  • DocFetchURL: The URL to the DocFetch servlet or server page. This URL should be relative to the Remote Server object URL configured for the Content Crawler object in the portal to facilitate migration to another portal.
  • IndexFilePath: A writable, web-accessible directory to which the IDK can write temporary files. During crawl-time, the Oracle WebCenter Interaction Development Kit (IDK) calls IDocument.GetDocument and copies the file path returned to this temporary file location, which is returned to the portal. These temporary files should be deleted upon completion of the crawl. (The DocFetch mechanism will clean up its own resources, but you must delete the temporary file you return to GetDocument.)
  • IndexURLPrefix: The public Web address of the IndexFilePath directory. IndexURLPrefix must be an URL accessible from the portal server.
The code below is an example of deploying DocFetch in web.config.
... 
<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.


  Back to Top      Previous Next