WebLogic Portal 9.2 MP1 Autonomy BEACMRepoFetch issue

Question

Hi,
I would like to ask you a favor to look into my issue and respond if you have found a way to fix it.
BEACMRepoFetch was not indexing the BEA CM contents with the default portal domain. I went through the documentation and found out that the "Search Indexing Enabled" must be "true" in WebLogic Admin Console | Content Management | BEA Repository. I changed the property value to "true". Now I get the following error. The CM full serach is still not working.
<Mar 14, 2007 9:34:28 PM PDT> <Error> <Search> <BEA-415611> <Unable to create th
e Content FullTextSearch database associated with repository BEA Repository due
FullTextSearch engine error.
com.bea.content.repo.internal.server.logic.search.CommandFailedException: autono
my command did not complete in 300,000 msec, waited 299,985 msec, status=0
at com.bea.content.repo.internal.server.logic.search.AutonomyHelper46.wa
itForServerCommand(AutonomyHelper46.java:179)
at com.bea.content.repo.internal.server.logic.search.AutonomyClient46Man
ager.createDatabase(AutonomyClient46Manager.java:164)
at com.bea.content.repo.internal.server.logic.search.AutonomyClient46Man
ager.connect(AutonomyClient46Manager.java:91)
at com.bea.content.federated.internal.VirtualRepositoryManagerImpl.ensur
eFullTextSearchDatabaseExists(VirtualRepositoryManagerImpl.java:223)
at com.bea.content.manager.internal.ContentListener.postStart(ContentLis
tener.java:59)
Truncated. see log file for complete stacktrace
>

Answer 1

The following need to be configured for CM Full Text Search (and BEACMRepoFetch) to work properly: (note these instructions are for a development box, not a production system)
- this Autonomy integration will work with a BEA Repository
- verify WLP_SEARCH_OPTION is set in the shell/command window before the server is started. This can be set to 'full', 'minimal', or 'none'. Set to 'full' to start up all the Autonomy processes.
- verify the autonomy processes start up and stay running. You should see 8 or so processes like AutonomyIDOLServer.exe, content.exe, AutonomyDiSH.exe, category.exe, community.exe, FileSystemFetch.exe, BEACMRepoFetch.exe, HTTPFetch.exe, etc. I like to use the Process Explorer tool on Windows because it shows the hierarchy of processes.
- check the Autonomy logs in the tree at WL_HOME/portal/thirdparty/autonomy/<os> for any 'error', 'warning', 'fail', 'unable', 'cannot', 'can't' messages. On windows, I like to use a tool like Agent Ransack to scan all *.log files in the entire directory tree for these strings. One semi-common message is that Autonomy sometimes will not start up if there is less than 1 Gb of free disk space.
- verify the following properties/settings are set on the repository config (note some of these default to true): search-enabled=TRUE, fulltext-search-is-enabled=TRUE, search-indexing-is-enabled=TRUE, cm_fireRepositoryEvents=TRUE
- verify your type and any associated properties have indexing enabled.