text: A call to configure the FTS Exporter is similar to the call that is shown in Example 15-1. 
  
  *Example 15-1 Configuring the FTS Exporter*
  
  java -jar ODFTIExporter.jar configure -configFile odfts.cfg -dbEngine DB2 
  -dbHostname localhost -dbPort 60004 -dbUser ondemand -dbPassword ondemand -dbName 
  ondemand -odInstallDir /opt/ibm/ondemand/V9.0 -pollDelay 60 -tempDir /tmp 
  -traceDir /tmp -ftiToken "fIqBxTQ=" -odUser admin -odPassword ondemand -dbOwner 
  ondemand -odInstance ONDEMAND 
  
  Example 15-1 writes the configuration file odfts.cfg and configures a connection to the 
  Content Manager OnDemand instance ONDEMAND with the user admin and to the Content 
  Manager OnDemand instance DB2 database ondemand. The FTS Exporter polls for work 
  items in the arsftiwork table every 60 seconds and processes them against the FTS Server 
  that is configured with this Content Manager OnDemand instance. 
  
  Content Manager OnDemand supports running the FTS Exporter on a system other than 
  your library and object server. In certain instances, this separation is highly recommend. If the 
  FTS Exporter is installed on a remote system, the Content Manager OnDemand server code 
  must be installed on this system because the FTS Exporter requires part of the binary and 
  supporting files from the Content Manager OnDemand server installation. The FTS Exporter 
  also gets part of its connection information from the ars.ini file that is installed with the 
  Content Manager OnDemand server or from the Windows registry. 