Documentum Full Text Indexing Using FAST

September 16th, 2009 by Zainab Mantri

I am currently working on a project which involves in upgrade of the existing Documentum 5.2.5sp2 system to 6.5sp2.  We had to re-create the indexes because prior to Documentum 5.3, indexing was done by Verity rather than FAST.

Here are some key points on the changes in 6.5sp2 which I would like to share:

• There is no need to upgrade the Full Text Index Server to an intermediate stage of 5.3, as the version of FAST used in 5.3 is 4.2 and the current version is 4.3 you will have to re-create the indexes. To avoid re-work, install 6.5sp2 FAST Index server and re-index your documents.
• The location of the index agent directory has changed for 6.5sp2 as the method server is now JBoss. The new path is E:\Documentum\jboss4.2.0\server\DctmServer_IndexAgent1\deploy\IndexAgent1.war.
• With 6.5sp2 you are forewarned of the software’s which are not compatible with FAST Index Server which was not listed in the earlier versions.

Useful Tips:

Index Agent Admin Page

The Index Agent Admin is a JSP page accessible at the URL http://hostname:portno/IndexAgentN/login.jsp where hostname is the name of the host where the index agent is running, portno is the port where the index agent is listening, and N is the number designating a particular index agent instance. The port number for 6.5sp2 is 9200 instead of 9081.

Use this page to map file stores, monitor the indexing process and stop or start the index agent and index server on a particular host. All browsers supported by WDK applications are supported for accessing this page.

Execute the following steps to map file stores if the content server and Index server are located on different machines. It definitely increases the Indexing speed. Add the following lines in the IndexAgent.xml file on the Index Server machine. Make a copy of the IndexAgent.xml file before doing the changes. Make sure you can access this content storage path from the Index Server machine.

<all_filestores_local>false</all_filestores_local>
<local_filestore_map>

<local_filestore>

<store_name>filestore_01</store_name>

<local_mount>\\ysj400doccon\F$\Documentum\data\iol_ref2\content_storage_01</local_mount>

</local_filestore>

</local_filestore_map>

When you have made the entry check the Index Agent admin page. You should see the following entries:

Index Server Admin Page

The Index Server admin Page is a JSP page accessible at the URL http://host:<baseport+3000> where hostname is the name of the host where the index agent is running, base port is the starting port which you have assigned for FAST Index Server install. So the port number is for example 13000 + 3000 = 16000. It is very essential to check if all the services other than J2EE & Storage services are running.  We can stop these 2 services as they are not required by Documentum. You can check by going to the System Management Tab of webpage. All of the services listed below should be on especially the Web Server service.

 Tweet

Tags: Documentum, Documentum Full Text Search, Documenum 6.5, FAST Index Server, Full Text Index, Full Text Storage Mapping, Index Agent, Index Server

This entry was posted on Wednesday, September 16th, 2009 at 3:45 PM and is filed under Reva Technical, Vancouver. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Responses to “Documentum Full Text Indexing Using FAST”

 

1. Register Custom Types for Documentum FAST Indexing | Reva Solutions ECM Blog says:

   January 12, 2010 at 3:19 PM

   [...] Stop Index Agent by either going to Windows Services or from the Index Agent Admin Page [...]

    
2. Rowdy Sluga says:

   February 18, 2010 at 5:44 PM

   Nice tips. I always forget the URL to access the Index Agent Admin pages. Thank you for the help.

    
3. Zainab Mantri says:

   February 23, 2010 at 1:03 PM

   You are welcome.