Sometimes it is really useful to immediately test a document's ability to be fulltext-indexed on a FAST server. It is possible, of course, to submit the document again and again through the Documentum Administrator (DA) interface. If document has failed you can right click the document (from DA) and click Resubmit. But then you have to wait until the Index Agent listener picks up the document for indexing and this is more time consuming. You can also cause a document resubmission by editing or checking and checking out but the solution using api below is fastest.
To submit a document right away: first get its object id and then go into API Testor in DA or IAPI32.exe to submit this short statement:
queue,c,090008468000289a,dm_fulltext_index_user,dm_force_ftindex,,,,debug
A second advantage to submitting above api command with "debug" option is that you get valuable information about the document AFTER it's fulltext indexed. If you submitted the above command go to this location to locate debugging output:
...\Documentum\bea9.2\domains\DctmDomain\servers\DctmServer_IndexAgent1_DCTMFAST\data\IndexAgent1\
export\IndexAgent\dctmFAST_IndexAgent1\content\debug\090008468000289a_1
Sorry about the path...of course they have to make you look for the output! Remember, some of your server names and index agents will be spelled differently than above; those parts in italics are variable.
There is one interesting file in this location now: an XML file with a listing of most (or all) of the attributes that will be indexed. In other words, the XML file contains all the information on attributes it is sending to the index. See Fig. 1 below.
How are the attributes arranged inside the XML file? Below is a small part of the document...enough to hopefully get you interested. As you can see FAST Instream is converted attribute values into XML elements and classified them by types (date, string, etc.).
In summary, this technique for debugging a single document by forcing fulltext indexing through API is a useful way to debug entries if you have customized fulltext indexing or if you are troubleshooting a problem relating to metadata indexing.
<?xml version="1.0" encoding="UTF-8"?>
<dmftdoc dmftkey="090008468000289a">
<dmftkey>090008468000289a</dmftkey>
<dmftmetadata>
<dm_document>
<r_object_id dmfttype="dmid">090008468000289a</r_object_id>
<object_name dmfttype="dmstring">Product Support Matrix.pdf</object_name>
<r_object_type dmfttype="dmstring">dm_document</r_object_type>
<r_creation_date dmfttype="dmdate">2008-10-23T14:17:54</r_creation_date>
<r_modify_date dmfttype="dmdate">2008-10-23T14:17:54</r_modify_date>
<r_modifier dmfttype="dmstring">Steve Garrison</r_modifier>
<r_access_date dmfttype="dmdate">2008-10-23T08:19:16</r_access_date>
XML file continues
Figure 1. Image of directory where debugging files stored
