The relevant content cannot be found during full-text retrieval of 11-xplore in Documentum FAQ

Recently, I helped my colleagues solve a question about full-text search. I recorded it as my reference.

Problem 1 some files in cabinet can be searched in full text, but some files in cabinet cannot be retrieved in full text.

A new docbase-aadctm is created, and the corresponding index service and index agent are installed and configured.

1. First, upload a local file in the xplore administrator and perform a test. You can view the previously uploaded data in the search results of test search.

2. Return to the DA operation interface and manually import a dm_document document to the aadctm document cabinet. After the file is uploaded successfully, you can view the awaiting index status in the index queue on the administrator management interface.

3. After the index is created, search for the corresponding keyword in the quick search in the upper left corner to view the uploaded file.

4. In the same step, import a new file to the temp file cabinet and create a full-text index. The file information cannot be found in dmsearch and DA of xplore. The corresponding file cannot be found.

 

Solution:

1. After searching, the index agent comes with a filter that filters specified types, folders, and file cabinets. No index is created for the content of these objects.

2. Modify the filter in index agent. The procedure is as follows:

1) login http://192.168.1.XX: 9200/indexagent/login_dss.jsp management interface;

2) Select Check or update filter settings.

3) Click 'submit 'to view the existing filter settings in the system. All filtered file cabinets can be seen in 'cabinets to exclude '. The full-text index engine does not create indexes for the contents under these file cabinets.

4) Check 'Update filters 'and enter the file cabinet to be removed under 'remove Cabinet (s)'. Enter temp here, which means you want to include the data in the temp file cabinet into the full-text index range.

5) after setting, click 'save filter change' to save the Modification result. The system prompts the user to restart the index service after the modification.

3. After the filter is modified, restart the Index Service. The Startup File Path is in the C: \ xplore \ jboss7.1.1 \ Server Path on the xplore server.

When terminating the service, execute stopindexagent. CMD and stopprimarydsearch. cmd, and start startprimarydsearch. CMD and startindexagent. CMD in sequence.

4. log on to the indexagent Management page and select reindex to recreate the index.

5. After the index is created, query the index again in the quick search. You can see the relevant files under the temp and aadctm file cabinets.

 

Question 2: How to specify several types for full-text search.

For example, you only need to retrieve data of the list_doc \ fina_doc \ dm_document types during full-text search, because the data does not specify the parent type, and it is very tangled at the moment. I forgot an important thing.

The same company gave a simple and practical method.

It is easy to specify the type dm_sysobject, which is the parent type of all objects. Then, select type in the condition and enter the range to be searched as the type.

When the search is executed, the full-text search engine automatically filters the corresponding conditions and the results are limited to the required types.