346 IBM Content Manager OnDemand Guide
To connect to your Content Manager OnDemand database by using JDBC, additional driver 
JAR files are required. The FTS Exporter is built to reference two additional JAR files in its 
directory by default: jdbc1.jar and jdbc2.jar. To use JAR file execution capability, you must 
link (or copy) your required JDBC driver JAR files to these locations so that they are 
automatically loaded by the FTS Exporter.
For example, when you use DB2 on AIX or Linux, you can issue the following commands in 
the jars subdirectory of the server to create these two links:
ln -s /opt/IBM/db2/V9.7/java/db2jcc.jar  jdbc1.jar
ln -s /opt/IBM/db2/V9.7/java/db2jcc_license_cu.jar  jdbc2.jar
For the connection with Content Manager OnDemand, the FTS Exporter automatically 
references the Java API ODApi.jar. 
15.5  Running the full text indexing process
Both the FTS Server and the FTS Exporter must be running for the full text indexing requests 
to complete.
If the FTS Exporter and the FTS Server are not running, all full text indexing requests are 
written to the arsftiwork table. They are not processed until the FTS Exporter processes them 
and sends the documents to a running FTS Server.
15.5.1  Automatically indexing new data during the load
Indexing new data is simple with Content Manager OnDemand and FTS. When FTS is 
configured correctly, the result of an arsload operation automatically creates work items in 
the arsftiwork table. Each application group that the FTS is enabled for must be configured 
correctly. For more information, see “Configuring application groups for full text search” on 
page 343.
15.5.2  Indexing existing data through the arsdoc command
The arsdoc command is enhanced with two new options. The first new option is fti_add. 
Parameters for this option control whether the resulting documents are queried through SQL 
(the -i parameter) or if an entire load will be full text indexed (the -X parameter). 
The second new option that is added to arsdoc is fti_release. This option takes the same 
parameters as fti_add to determine the documents that need their indexes removed from 
the full text index.
Both of these options result in work items that are created in the arsftiwork table. 
Example 15-2 shows an example of the command that is used with Bank1.
Example 15-2   Full text indexing all (SQL WHERE 1=1) documents of Bank1
arsdoc fti_add -f "Bank1" -h localhost -i "where 1=1" -u admin -v -G Bank1
Note: Each instance of the FTS Exporter can connect to one Content Manager 
OnDemand instance. Only a single instance of the FTS Exporter for each Content 
Manager OnDemand database is supported.