IntroductionIntroduction
  InstallingInstalling
  HandlingHandling
  Virtual serversVirtual servers
  ModulesModules
  FilesystemsFilesystems
  RXML tagsRXML tags
  GraphicsGraphics
  ProxyProxy
  Miscellaneous modulesMiscellaneous modules
  Security considerationsSecurity considerations
  ScriptingScripting
  DatabasesDatabases
  LDAPLDAP
  SiteBuilderSiteBuilder
  Access ControlAccess Control
  IntraSeekIntraSeek
    <Directories>Directories<Directories>Directories
    <Configuring>Configuring<Configuring>Configuring
    <Creating new profile>Creating new profile<Creating new profile>Creating new profile
    <Indexing>Indexing<Indexing>Indexing
    <Languages>Languages<Languages>Languages
    <Logs>Logs<Logs>Logs
    <Advanced profile>Advanced profile<Advanced profile>Advanced profile
    <Technical document>Technical document<Technical document>Technical document
  LogViewLogView
  FrontPageFrontPage
  UpgradingUpgrading
  Third party extensionsThird party extensions
  PortabilityPortability
  Reporting bugsReporting bugs
  AppendixAppendix
 
Configuring

To configure IntraSeek inside Challenger focus on the Virtual Servers and select the server on which you've installed IntraSeek. Most of the time there is no need to change many of the IntraSeek module variables, unless any of the special cases described below occurs. Here is a listing of the module variables.

Admin Password & Admin user name
The password and name you use to access the Intraseek graphical configuration interface. The default values are the standard roxen administrators user name and password. Will by default be the same as the Challenger configuration interface user and password. You can change these values, or simply keep them as they are.

When used in SiteBuilder a protection point in access control is used instead.

Administrator email
Should contain your own mail address. It will be used by the crawler when presenting itself to the web server. If you wish to be be anonymous it can be left empty. This email address will not be on any web page, but only in the HTTP protocol request header.

Engine home location
Should point to where you have copied your IntraSeek files. This should default to the correct directory.

Mount point for config
Where IntraSeek mounts on the server URL. May be left unchanged.

When used in SiteBuilder IntraSeek is located under the Plugins tab instead.

Profile config location
Is by default the same as Engine home location. If you plan to run IntraSeek on only one virtual server, this is fine.
If you want to share the same IntraSeek code and base directory for several virtual servers, you should change the Profile config location path. The path points to a location where the profile configurations are saved. Several virtual servers can share the same Engine home location, but if Profile config location is left untouched, they will all use the same profiles - which, for example, means that they will all try to auto-launch crawlers at the same time. More on this on the Advanced profile configuration page.

If you are using a port other than port 80, make sure that the Server Variables/Server URL is correct and that it contains the proper port as well.

Go to IntraSeek
When the Challenger configuration is done direct your web browser to IntraSeek's dedicated graphical configuration interface. If you have a SiteBuilder server running focus on the Plugins/IntraSeek tab. If you don't have a SiteBuilder click on the link Go to the administration page inside the IntraSeek module configuration interface.