xPlore 6.7 Content Server 6.6
When configuring xPlore 6.7 against 6.6 repository (maybe other versions) Documentum server config object will not save with the out-of-the-box file, dmfulltext.ini – if using RedHat Linux.
This is because of an incorrect ini file.
If suitably configured to use xPlore, the Content Server log should properly document the correct plugin which would be something like
Loaded FT Query Plugin: /srv/ecm/dmreach01/product/6.6/bin/libDsearchQueryPlugin.so, API Interface version: 1.0, Build number: HEAD; May 17 2011 05:20:39, FT Engine version: X-Hive/DB 8.2
The dm_server_config_object may fail to update properly when running fulltext_setup_for_dss.ebs with the error message DM_FT_INDEX_E_FULLTEXT_CONFIG_NOT_LOADED when it reaches the function setupFulltextLocation within the script which is used as part of the setup.
The location dsearch should already be setup in file_system_path of dm_location (select file_system_path from dm_location where object_name=’dsearch’ should return /path/to/fulltext/dsearch where dmfulltext.ini is located.
fulltext.ini may well be there and should be but contains an invalid path to the search plugin. This path reads:
[LINUX_FULLTEXT]
bin_location = _ssol26/bin
library_name = libDsearchQueryPlugin.so
but should read
[LINUX_FULLTEXT]
bin_location = bin
library_name = libDsearchQueryPlugin.so
Backup the original file and remove the _ssol26/ from the bin_location parameter as shown.
Once changed run the api against the repository (assuming dsearch is a valid dm_location):
>retrieve,c,dm_server_config
>set,c,l,fulltext_location
SET>dsearch
>save,c,l
Which should be OK now. If the CS can’t find the library file then it is not possible to save the changes to the server_config.
Restart repository and check the loaded FT Query plugin refers to the xhive as shown towards the top of this post.
Make sure the other instructions were followed in the xplore 1.1 installation guide.
Obviously verify the installation and test the search from a WDK app connected to the repository.
