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
  LogViewLogView
  FrontPageFrontPage
  UpgradingUpgrading
  Third party extensionsThird party extensions
    <Installing>Installing<Installing>Installing
  PortabilityPortability
  Reporting bugsReporting bugs
  AppendixAppendix
 
Installing

Challenger modules
Challenger modules are installed by installing the module's files somewhere the server can find them. Usually, in local/modules, but, by configuring the Global Variables/Module directories variable they can be placed anywhere. Do not place any third-party modules in the server/modules directories since server is replaced when the Challenger server is upgraded.

After installing the module's files and making sure Challenger can find them, the module can be enabled by the Add module button. It might take a reload on the Add module page before the new module is available.

CGI scripts
Before installing a CGI-script you should consider whether a Challenger module exists that can provide the same functions. If not, you should follow the installation procedure that comes with the script. This will probably describe how you install a CGI-script in another web server, but it shouldn't matter much. Challenger works like any other web server when it comes to CGI-scripts.

Java servlets
A Java servlet is installed by creating a copy of the Java servlet bridge module for that servlet. See the Servlets page in the Scripting chapter for more information.