At one of my customers, I experienced a problem with the Documentum Administrator (DA), which did not display the correct Index Agent status. In this blog post, I will explain how I found the source of this problem and of course also how I solved this issue.<\/p>\n
But first, some background facts: The Documentum Administrator (DA) is displaying “not responding” for the Index Agent, however the Index Agent is running well. No solutions are mentioned in the Documentum support notes.<\/p>\n
Command to use:<\/p>\n
API> apply,c,NULL,FTINDEX_AGENT_ADMIN,NAME,S,,AGENT_INSTANCE_NAME,S,,ACTION,S,start<\/pre>\nIn my case:<\/p>\n
API> apply,s0,NULL,FTINDEX_AGENT_ADMIN,NAME,S,TEST_ftindex_01,AGENT_INSTANCE_NAME,S,ftserver.i_9200_IndexAgent,ACTION,S,status\n...\nq0\nAPI> next,c,q0\n...\nOK\nAPI> get,c,q0,status\n...\n200\nAPI><\/pre>\n“200” means that there is a problem with the Index Agent.<\/p>\n
2) I can find errors in two locations:<\/h4>\n
\n
- by setting the trace for DA, I can find the following error in the trace file:<\/li>\n<\/ul>\n
[!com.documentum.fc.common.DfException: [DM_METHOD_E_JMS_APP_SERVER_NAME_NOTFOUND]error: \"The\n app_server_name\/servlet_name 'ftserver.i_9200_IndexAgent' is not specified in dm_server_config\/dm_jms_config.\"!]<\/pre>\n\n
- In the user session logfile I see the following:<\/li>\n<\/ul>\n
2013-07-18T09:23:06.132697 22991[22991] 0101e2ee80ee8913 [DM_FT_INDEX_T_INIT_INDEX_AGENT_MSG]info: \"Attempting to status Index Agent Instance ftserver.i_9200_IndexAgent\"\n2013-07-18T09:23:06.132766 22991[22991] 0101e2ee80ee8913 [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.\"\n2013-07-18T09:23:06.132791 22991[22991] 0101e2ee80ee8913 [DM_FT_INDEX_T_INIT_INDEX_AGENT_MSG]info: \"HTTP_POST with args -command status -docbase TESTREPO -user dm_fulltext_index_user -ticket DM_TICKET=T0JKIE5......UkxZeXc2cHd3SVc0dz09Cg== -instance ftserver.i_9200_IndexAgent -details false to Index Agent ftserver.i_9200_IndexAgent failed.\"\n2013-07-18T09:24:05.032297 22991[22991] 0101e2ee80ee8913 [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\"<\/pre>\n3) Let’s use the previous output to perform a deeper analysis<\/h4>\n
\n
- In the dm_jms_config the Index Agent app_server_name is not defined – which is normal<\/li>\n
- In DA I can see the name of the Application Server – which is is fine<\/li>\n
- The dm_server_config object is correct:<\/li>\n<\/ul>\n
retrieve,c,dm_server_config\ndump,c,l\nthe relevant data of the output:\napp_server_name [0]: do_method\n [1]: do_mail\n [2]: ftserver.i_9200_IndexAgent<\/pre>\napp_server_uri [0]: http:\/\/localhost:19080\/DmMethods\/servlet\/DoMethod<\/a>
\n[1]: http:\/\/localhost:19080\/DmMail\/servlet\/DoMail<\/a>
\n[2]: http:\/\/ftserver.dummy.com<\/a>:19200\/IndexAgent\/servlet\/IndexAgent<\/p>\nBut then, what is wrong?<\/p>\n
4) Reproducing the error<\/h4>\n
As all seems to be fine, I have to reproduce the error.<\/p>\n
\n
- 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:<\/li>\n<\/ul>\n
API> apply,s0,NULL,FTINDEX_AGENT_ADMIN,NAME,S,TEST_ftindex_01,AGENT_INSTANCE_NAME,S,ftserver.9200_IndexAgent,ACTION,S,status\n...\nq0\nAPI> next,c,q0\n...\nOK\nAPI> get,c,q0,status\n...\n[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\"\n[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.\"<\/pre>\n\n
- The FTINDEX_AGENT_ADMIN method issues an HTTP_POST method that then invokes the servlet used by the IndexAgent Admin Web utility. So using the HTTP_POST method I can also reproduce the error:<\/li>\n<\/ul>\n
1> execute http_post WITH app_server_name='ftserver.i_9200_IndexAgent'
\n2> go
\n[DM_METHOD_E_JMS_APP_SERVER_NAME_NOTFOUND]error: \"The app_server_name\/servlet_name
\n'ftserver.i_9200_IndexAgent' is not specified in dm_server_config\/dm_jms_config.\"<\/code><\/p>\n\n
- 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<\/li>\n<\/ul>\n
1> execute http_post WITH app_server_name='ftserver.i_9200_IndexAgent '\n 2> go\n result http_response_status request_failed response_doc_id time_taken \n timed_out time_out_length app_server_host_name app_server_port \n app_server_uri \n ----------------------------------------------------------------------------------\n 0 HTTP\/1.1 200 OK F 0000000000000000 0 \n F 60 ftserver.dummy.com 9200 \/IndexAgent\/servlet\n \/IndexAgent\n (1 row affected)\n 1><\/pre>\n<\/p>\n
With this positive result, I have found the source of my problem: a wrong app_server_name!<\/p>\n
Solution<\/h3>\n
The issue was solved by creating a new app_server_name entry (without the blank) in the docbase config object.
\nThe final test with API proved successful:<\/p>\nAPI> apply,s0,NULL,FTINDEX_AGENT_ADMIN,NAME,S,TEST_ftindex_01,AGENT_INSTANCE_NAME,S,ftserver.i_9200_IndexAgent,ACTION,S,status\n...\nq0\nAPI> next,c,q0\n...\nOK\nAPI> dump,c,q0\n...\nUSER ATTRIBUTES name [0]: ftserver.i_9200_IndexAgent\n status [0]: 0\nSYSTEM ATTRIBUTES\nAPPLICATION ATTRIBUTES\nINTERNAL ATTRIBUTESAPI><\/pre>\nOnce logged off and signed in again, DA displays the correct status (running) for the Index Agent.
\nI hope this solution will help other people in a situation where the EMC powerlink solution does not work.<\/p>\n","protected":false},"excerpt":{"rendered":"At one of my customers, I experienced a problem with the Documentum Administrator (DA), which did not display the correct Index Agent status. In this blog post, I will explain how I found the source of this problem and of course also how I solved this issue. But first, some background facts: The Documentum Administrator […]<\/p>\n","protected":false},"author":24,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[129,391,392,334],"type_dbi":[],"class_list":["post-3210","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","tag-documentum","tag-enterprise-content-management","tag-index-agent","tag-middleware"],"acf":[],"yoast_head":"\n
Documentum Administrator does not display the correct "Index Agent" status - dbi Blog<\/title>\n<meta name=\"description\" content=\"At one of my customers, I experienced a problem with the Documentum Administrator (DA), which did not display the correct Index Agent status. In this blog post, I will explain how I found the source of this problem and of course also how I solved this issue.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum Administrator does not display the correct "Index Agent" status\" \/>\n<meta property=\"og:description\" content=\"At one of my customers, I experienced a problem with the Documentum Administrator (DA), which did not display the correct Index Agent status. In this blog post, I will explain how I found the source of this problem and of course also how I solved this issue.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2013-08-06T01:16:00+00:00\" \/>\n<meta name=\"author\" content=\"G\u00e9rard Wisson\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"G\u00e9rard Wisson\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-administrator-does-not-display-the-correct-index-agent-status\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-administrator-does-not-display-the-correct-index-agent-status\\\/\"},\"author\":{\"name\":\"G\u00e9rard Wisson\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/ad54b5e621903122c00c6b7921c6ab85\"},\"headline\":\"Documentum Administrator does not display the correct “Index Agent” status\",\"datePublished\":\"2013-08-06T01:16:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-administrator-does-not-display-the-correct-index-agent-status\\\/\"},\"wordCount\":425,\"commentCount\":0,\"keywords\":[\"Documentum\",\"Enterprise Content Management\",\"Index Agent\",\"Middleware\"],\"articleSection\":[\"Application integration & Middleware\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-administrator-does-not-display-the-correct-index-agent-status\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-administrator-does-not-display-the-correct-index-agent-status\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-administrator-does-not-display-the-correct-index-agent-status\\\/\",\"name\":\"Documentum Administrator does not display the correct \\\"Index Agent\\\" status - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2013-08-06T01:16:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/ad54b5e621903122c00c6b7921c6ab85\"},\"description\":\"At one of my customers, I experienced a problem with the Documentum Administrator (DA), which did not display the correct Index Agent status. In this blog post, I will explain how I found the source of this problem and of course also how I solved this issue.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-administrator-does-not-display-the-correct-index-agent-status\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-administrator-does-not-display-the-correct-index-agent-status\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-administrator-does-not-display-the-correct-index-agent-status\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum Administrator does not display the correct “Index Agent” status\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/ad54b5e621903122c00c6b7921c6ab85\",\"name\":\"G\u00e9rard Wisson\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g\",\"caption\":\"G\u00e9rard Wisson\"},\"description\":\"G\u00e9rard Wisson has more than ten years of experience in Enterprise Content Management (ECM) with Documentum as well as in Oracle WebLogic and Java EE \\\/ J2EE infrastructures. He is specialized in ECM infrastructure services such as installation, upgrade, high availability, and administration as well as in Oracle WebLogic services such as installation, configuration, and management. He is very experienced in the monitoring and optimization of Java EE \\\/ J2EE infrastructures with Grid\\\/Cloud Control and JVMD. G\u00e9rard Wisson is certified Oracle Weblogic Server 11g System Administrator and Oracle Certified Associate. Prior to joining dbi services, G\u00e9rard Wisson was Senior Consultant at Solfit in Basel. He holds a diploma in Electrical Engineering from the University of Strasbourg (F). His branch-related experience covers Financial Services \\\/ Banking, Chemicals & Pharmaceuticals, etc.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/gerard-wisson\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Documentum Administrator does not display the correct \"Index Agent\" status - dbi Blog","description":"At one of my customers, I experienced a problem with the Documentum Administrator (DA), which did not display the correct Index Agent status. In this blog post, I will explain how I found the source of this problem and of course also how I solved this issue.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/","og_locale":"en_US","og_type":"article","og_title":"Documentum Administrator does not display the correct \"Index Agent\" status","og_description":"At one of my customers, I experienced a problem with the Documentum Administrator (DA), which did not display the correct Index Agent status. In this blog post, I will explain how I found the source of this problem and of course also how I solved this issue.","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/","og_site_name":"dbi Blog","article_published_time":"2013-08-06T01:16:00+00:00","author":"G\u00e9rard Wisson","twitter_card":"summary_large_image","twitter_misc":{"Written by":"G\u00e9rard Wisson","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/"},"author":{"name":"G\u00e9rard Wisson","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/ad54b5e621903122c00c6b7921c6ab85"},"headline":"Documentum Administrator does not display the correct “Index Agent” status","datePublished":"2013-08-06T01:16:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/"},"wordCount":425,"commentCount":0,"keywords":["Documentum","Enterprise Content Management","Index Agent","Middleware"],"articleSection":["Application integration & Middleware"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/","name":"Documentum Administrator does not display the correct \"Index Agent\" status - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2013-08-06T01:16:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/ad54b5e621903122c00c6b7921c6ab85"},"description":"At one of my customers, I experienced a problem with the Documentum Administrator (DA), which did not display the correct Index Agent status. In this blog post, I will explain how I found the source of this problem and of course also how I solved this issue.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-administrator-does-not-display-the-correct-index-agent-status\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum Administrator does not display the correct “Index Agent” status"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/ad54b5e621903122c00c6b7921c6ab85","name":"G\u00e9rard Wisson","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g","caption":"G\u00e9rard Wisson"},"description":"G\u00e9rard Wisson has more than ten years of experience in Enterprise Content Management (ECM) with Documentum as well as in Oracle WebLogic and Java EE \/ J2EE infrastructures. He is specialized in ECM infrastructure services such as installation, upgrade, high availability, and administration as well as in Oracle WebLogic services such as installation, configuration, and management. He is very experienced in the monitoring and optimization of Java EE \/ J2EE infrastructures with Grid\/Cloud Control and JVMD. G\u00e9rard Wisson is certified Oracle Weblogic Server 11g System Administrator and Oracle Certified Associate. Prior to joining dbi services, G\u00e9rard Wisson was Senior Consultant at Solfit in Basel. He holds a diploma in Electrical Engineering from the University of Strasbourg (F). His branch-related experience covers Financial Services \/ Banking, Chemicals & Pharmaceuticals, etc.","url":"https:\/\/www.dbi-services.com\/blog\/author\/gerard-wisson\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/3210","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=3210"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/3210\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=3210"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=3210"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=3210"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=3210"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}