text: If you are document the default token (for example, as a parameter of the FTS Exporter), be 
  aware that the second character of the token value is an uppercase letter I, as in IBM. 
  
  **FTS Exporter errors**
  If you encounter issues with the FTS Exporter, increase the trace level as described in 15.7.3, 
  “Full Text Search Exporter trace” on page 351. Also, ensure that you review the configuration 
  file by opening it in a text editor. Check whether all settings are correct. 
  
  If you encounter errors about ars3wapi in the FTS Exporter output or trace, the FTS Exporter 
  cannot find the native library reference to the ODWEK system libraries. To see how to use the 
  **-D**parameter of Java to include the native library path at application start, see 15.5.4, 
  “Running the FTS Exporter” on page 347. 
  
  If the error relates to a java.lang.UnsatisfiedLinkError error that does not find the 
  ars3wapi32, you are running on a 32-bit JVM. The Java classes of the FTS Exporter try to 
  load the libars3wapi64, which is in the lib64 subdirectory of your Content Manager 
  OnDemand installation. If they cannot load the libars3wapi64, a 32-bit version is searched 
  (which is not present in the lib64 folder). If both attempts fail, they fail with the related error 
  message. 