Windchill Index Search Property Setting

[pwilliams-3]

All,
For those of you using FAST indexing, what would you recommend for the following property?

wt.index.maxDocumentSize

10 mb, 25 mb, more?

Patrick Williams | Engineering Systems | Sr. Applications Engineer | Steelcase Inc. | 616.698.4078

[cid:image001.jpg@01CA613F.110DEE40]

[MikeLockwood]

Careful on this particular one...
- We had this value set at 20, then later raised to 50, then unset it. Supposedly there is no practical limit to this as of 9.0.
- If you set it and then later change it to a higher value, there is no way to find those that were not included before, and no way to now include them except to re-bulk index everything.
- The value is actually applied to the indexable text, not to the file size. So, for example a file that includes screen captures could be 100MB but have only 5KB of indexable text.
- The system does not tell you in any way that we've been able to see (after 25 tech support calls) which documents if any are ignored with this property set.

Huge frustrations with FAST for us so far this year (since implementing in Feb). Very poor documentation in general.

[pwilliams-3]

Brilliant! Thanks Mike. The documentation says that if I leave it unset then I should increase the jre heap size and increase a timeout value. Did you do that?

? You can limit the maximum size (in bytes) of the document submitted to
Windchill Index Search with following property:
wt.index.maxDocumentSize
There is no default value set for this property. Although not mandatory, you
should limit the maximum size of documents to index to a reasonable value.
If you decide to not set this property, then the following is recommended:
? increase the operation-timeout parameter from 60 to 600 for contentdistributor
in the <fastsearch>\etc\NodeConf.xml file.
? increase the JVM heap size to 512MB or more to get fewer Out of Memory
errors in the Method Server.

Patrick Williams | Engineering Systems | Sr. Applications Engineer | Steelcase Inc. | 616.698.4078

[cid:image001.jpg@01CA614A.5D4BBFC0]

From: Lockwood,Mike,IRVINE,R&D [

[MikeLockwood]

Yes - we've been fooling w/trying to opitmize within our current 32bit Windows limits. Looking forward to having 64 bit servers by end of the year - should help.

You have to monitor the FAST server quite a bit as well as Windchill. The CPU on the FAST server runs near 100% many times with nothing apparently going on - the processes that are constantly churning are frtsobj.exe and fsearch.

Be sure to set up web UI for FAST (:16000/admin>)">http://<fast%20hostname>:16000/admin>) and to add a password to it (if you don't add a password, any user can access, and can wipe out the entire bulk index in one shot - the delete button is right there next to the drill-down button.

[cid:760370620@09112009-0EF3]