Professional Documents
Culture Documents
Fix IndexAgent Status in Documentum Administrator
Fix IndexAgent Status in Documentum Administrator
Analysis
1) I have to use the API code to find the status.
Command to use:
API>
apply,c,NULL,FTINDEX_AGENT_ADMIN,NAME,S,,AGENT_INSTANCE_NAME,S,,ACTION,S,start
In my case:
API>
apply,s0,NULL,FTINDEX_AGENT_ADMIN,NAME,S,TEST_ftindex_01,AGENT_INSTANCE_NAME,
S,ftserver.i_9200_IndexAgent,ACTION,S,status
...
q0
API> next,c,q0
...
OK
API> get,c,q0,status
...
200
API>
by setting the trace for DA, I can find the following error in the trace file:
[!com.documentum.fc.common.DfException:
[DM_METHOD_E_JMS_APP_SERVER_NAME_NOTFOUND]error: "The
app_server_name/servlet_name 'ftserver.i_9200_IndexAgent' is not
specified in dm_server_config/dm_jms_config."!]
In the dm_jms_config the Index Agent app_server_name is not defined - which is normal
In DA I can see the name of the Application Server - which is is fine
retrieve,c,dm_server_config
dump,c,l
the relevant data of the output:
app_server_name [0]: do_method
[1]: do_mail
[2]: ftserver.i_9200_IndexAgent
app_server_uri [0]: http://localhost:19080/DmMethods/servlet/DoMethod
[1]: http://localhost:19080/DmMail/servlet/DoMail
[2]: http://ftserver.dummy.com:19200/IndexAgent/servlet/IndexAgent
By purposely choosing a wrong AGENT_INSTANCE_NAME ftserver.9200_IndexAgent instead of ftserver.i_9200_IndexAgent (--> I have removed the
"i" ) - I am able to reproduce the error:
API>
apply,s0,NULL,FTINDEX_AGENT_ADMIN,NAME,S,TEST_ftindex_01,AGENT_INSTANCE_NAME,
S,ftserver.9200_IndexAgent,ACTION,S,status
...
q0
API> next,c,q0
...
OK
API> get,c,q0,status
...
[DM_FT_INDEX_E_NO_FTINDEX_AGENT_CONFIG_OBJECTS_FOUND]error: "There were no
dm_ftindex_agent_config object(s) found for the specified arguments"
[DM_METHOD_E_JMS_APP_SERVER_NAME_NOTFOUND]error: "The
app_server_name/servlet_name 'ftserver.9200_IndexAgent' is not specified in
dm_server_config/dm_jms_config."
As I see the same name in the DA, I have to add a blank behind the app_server_name
value, hoping this is the char I cannot see. Again, I am using the http_post
With this positive result, I have found the source of my problem: a wrong app_server_name!
Solution
The issue was solved by creating a new app_server_name entry (without the blank) in the
docbase config object.
The final test with API proved successful:
API>
apply,s0,NULL,FTINDEX_AGENT_ADMIN,NAME,S,TEST_ftindex_01,AGENT_INSTANCE_NAME,
S,ftserver.i_9200_IndexAgent,ACTION,S,status
...
q0
API> next,c,q0
...
OK
API> dump,c,q0
...
USER ATTRIBUTES name [0]: ftserver.i_9200_IndexAgent
status [0]: 0
SYSTEM ATTRIBUTES
APPLICATION ATTRIBUTES
INTERNAL ATTRIBUTESAPI>
Once logged off and signed in again, DA displays the correct status (running) for the Index
Agent.
I hope this solution will help other people in a situation where the EMC powerlink solution does
not work.