Recently, I was doing some sanity checks on a Documentum Server and I saw a Java exception stack while logging in using iAPI\/iDQL to a Repository. It was reproducible for all Repositories. I’ve never seen something like that before (or at least I don’t remember it) so I was a little bit surprised. Whenever there are errors upon login, it is usually Documentum error messages that are printed and there is no exception stack. Since it took me some efforts finding the root cause, I thought about sharing it.<\/p>\n
The exception stack displayed was the following one:<\/p>\n
[dmadmin@cs-0 ~]$ echo \"quit\" | iapi gr_repo -Udmadmin -Pxxx\n\n EMC Documentum iapi - Interactive API interface\n (c) Copyright EMC Corp., 1992 - 2016\n All rights reserved.\n Client Library Release 7.3.0040.0025\n\nConnecting to Server using docbase gr_repo\nDfException:: THREAD: main; MSG: [DM_SESSION_I_SESSION_START]info: \"Session 0112d687800c9214 started for user dmadmin.\"; ERRORCODE: 100; NEXT: null\n at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57)\n at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException(MessageEntry.java:39)\n at com.documentum.fc.client.impl.connection.docbase.DocbaseMessageManager.getExceptionForAllMessages(DocbaseMessageManager.java:176)\n at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.getExceptionForAllMessages(DocbaseConnection.java:1518)\n at com.documentum.fc.client.impl.session.Session.getExceptionsForAllMessages(Session.java:1603)\n at com.documentum.fc.client.impl.session.SessionHandle.getExceptionsForAllMessages(SessionHandle.java:1301)\n at com.documentum.dmcl.impl.ApiContext.addMessages(ApiContext.java:423)\n at com.documentum.dmcl.impl.ApiContext.collectExceptionsForReporting(ApiContext.java:370)\n at com.documentum.dmcl.impl.GetMessageHandler.get(GetMessageHandler.java:23)\n at com.documentum.dmcl.impl.DmclApi.get(DmclApi.java:49)\n at com.documentum.dmcl.impl.DmclApiNativeAdapter.get(DmclApiNativeAdapter.java:145)\n at com.documentum.dmcl.impl.DmclApiNativeAdapter.get(DmclApiNativeAdapter.java:130)\n\n\nConnected to Documentum Server running Release 7.3.0050.0039 Linux64.Oracle\nSession id is s0\nAPI> Bye\n[dmadmin@cs-0 ~]$<\/pre>\n<\/p>\n
The login was successful but still, a strange exception stack appeared. The first thing I did was checking the Repository log file but there was nothing out of the ordinary inside it except for one thing:<\/p>\n
[dmadmin@cs-0 ~]$ cd $DOCUMENTUM\/dba\/log\n[dmadmin@cs-0 log]$\n[dmadmin@cs-0 log]$ grep -A3 \"Agent Exec\" gr_repo.log\nWed Sep 11 10:38:29 2019 [INFORMATION] [AGENTEXEC 1477] Detected during program initialization: Agent Exec connected to server gr_repo: DfException:: THREAD: main; MSG: [DM_SESSION_I_SESSION_START]info: \"Session 0112d687800c8904 started for user dmadmin.\"; ERRORCODE: 100; NEXT: null\n at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57)\n at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException(MessageEntry.java:39)\n at com.documentum.fc.client.impl.connection.docbase.DocbaseMessageManager.getExceptionForAllMessages(DocbaseMessageManager.java:176)\n at com.documentu\n[dmadmin@cs-0 log]$<\/pre>\n<\/p>\n
While starting, the Agent Exec was therefore facing the same behavior with the exact same stack (which is cut at the 4th line but it’s the same stack until then so it’s safe to assume it’s the same). Therefore, to dig deeper and to find when the issue started exactly, I checked the logs from the agentexec\/jobs since this will be kept until cleanup from the log purge and since it does login to the Repository:<\/p>\n
[dmadmin@cs-0 log]$ cd $DOCUMENTUM\/dba\/log\/gr_repo\/agentexec\n[dmadmin@cs-0 agentexec]$\n[dmadmin@cs-0 agentexec]$ # Check the last file\n[dmadmin@cs-0 agentexec]$ cat $(ls -tr job_* | tail -1)\nWed Sep 11 18:00:21 2019 [INFORMATION] [LAUNCHER 3184] Detected while preparing job dm_ConsistencyChecker for execution: Agent Exec connected to server gr_repo: DfException:: THREAD: main; MSG: [DM_SESSION_I_SESSION_START]info: \"Session 0112d687800c8974 started for user dmadmin.\"; ERRORCODE: 100; NEXT: null\n at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57)\n at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException(MessageEntry.java:39)\n at com.documentum.fc.client.impl.connection.docbase.DocbaseMessageManager.getExceptionForAllMessages(DocbaseMessageManager.java:176)\n at com.documentu\n[dmadmin@cs-0 agentexec]$\n[dmadmin@cs-0 agentexec]$ # Finding the first file with the error\n[dmadmin@cs-0 agentexec]$ for f in $(ls -tr); do r=$(grep \"_I_SESSION_START.*ERRORCODE\" \"${f}\"); if [[ \"${r}\" != \"\" ]]; then echo \"${r}\"; break; fi; done\nTue Sep 10 18:00:06 2019 [INFORMATION] [LAUNCHER 31113] Detected while preparing job dm_ConsistencyChecker for execution: Agent Exec connected to server gr_repo: DfException:: THREAD: main; MSG: [DM_SESSION_I_SESSION_START]info: \"Session 0112d687800c8827 started for user dmadmin.\"; ERRORCODE: 100; NEXT: null\n[dmadmin@cs-0 agentexec]$<\/pre>\n<\/p>\n
In all the job’s sessions files, there were the same stack (or rather a piece of the stack). At first, I didn’t understand where this was coming from, all I know was that it was linked somehow to the login inside the Repository and that it appeared for the first time on the date returned by my last command above. It was not really an error message since it wasn’t showing any “_E_<\/strong>” messages but it was still printing an exception.<\/p>\n
Knowing when it appeared the first time, I looked at all the files that have been modified on that day and among log files, which are expected and can be ignored, there were the dfc.properties file. This provided me the reason for this message: it was actually due to enabling the diagnostic mode on the dfc.properties of the Documentum Server. To be exact, it was due to the “dfc.diagnostics.exception.include_stack=true<\/strong>” entry:<\/p>\n
[dmadmin@cs-0 agentexec]$ tail -5 $DOCUMENTUM_SHARED\/config\/dfc.properties\ndfc.session.secure_connect_default=secure\ndfc.time_zone=UTC\ndfc.diagnostics.resources.enable=true\ndfc.diagnostics.exception.include_stack=true\ndfc.tracing.print_exception_stack=true\n[dmadmin@cs-0 agentexec]$\n[dmadmin@cs-0 agentexec]$ echo \"quit\" | iapi gr_repo -Udmadmin -Pxxx\n\n EMC Documentum iapi - Interactive API interface\n (c) Copyright EMC Corp., 1992 - 2016\n All rights reserved.\n Client Library Release 7.3.0040.0025\n\nConnecting to Server using docbase gr_repo\nDfException:: THREAD: main; MSG: [DM_SESSION_I_SESSION_START]info: \"Session 0112d687800c9235 started for user dmadmin.\"; ERRORCODE: 100; NEXT: null\n at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57)\n at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException(MessageEntry.java:39)\n at com.documentum.fc.client.impl.connection.docbase.DocbaseMessageManager.getExceptionForAllMessages(DocbaseMessageManager.java:176)\n at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.getExceptionForAllMessages(DocbaseConnection.java:1518)\n at com.documentum.fc.client.impl.session.Session.getExceptionsForAllMessages(Session.java:1603)\n at com.documentum.fc.client.impl.session.SessionHandle.getExceptionsForAllMessages(SessionHandle.java:1301)\n at com.documentum.dmcl.impl.ApiContext.addMessages(ApiContext.java:423)\n at com.documentum.dmcl.impl.ApiContext.collectExceptionsForReporting(ApiContext.java:370)\n at com.documentum.dmcl.impl.GetMessageHandler.get(GetMessageHandler.java:23)\n at com.documentum.dmcl.impl.DmclApi.get(DmclApi.java:49)\n at com.documentum.dmcl.impl.DmclApiNativeAdapter.get(DmclApiNativeAdapter.java:145)\n at com.documentum.dmcl.impl.DmclApiNativeAdapter.get(DmclApiNativeAdapter.java:130)\n\n\nConnected to Documentum Server running Release 7.3.0050.0039 Linux64.Oracle\nSession id is s0\nAPI> Bye\n[dmadmin@cs-0 agentexec]$\n[dmadmin@cs-0 agentexec]$ sed -i sed 's,^dfc.diagnostics.exception.include_stack,#&,' $DOCUMENTUM_SHARED\/config\/dfc.properties\n[dmadmin@cs-0 agentexec]$\n[dmadmin@cs-0 agentexec]$ echo \"quit\" | iapi gr_repo -Udmadmin -Pxxx\n\n EMC Documentum iapi - Interactive API interface\n (c) Copyright EMC Corp., 1992 - 2016\n All rights reserved.\n Client Library Release 7.3.0040.0025\n\nConnecting to Server using docbase gr_repo\n[DM_SESSION_I_SESSION_START]info: \"Session 0112d687800c9237 started for user dmadmin.\"\n\nConnected to Documentum Server running Release 7.3.0050.0039 Linux64.Oracle\nSession id is s0\nAPI> Bye\n[dmadmin@cs-0 agentexec]$<\/pre>\n<\/p>\n
As you can see above, commenting the line “dfc.diagnostics.exception.include_stack=true<\/strong>” (meaning setting it to false, the default value) caused the exception stack to disappear. Since I was curious about this stack and wanted confirmation that this is “expected”, I opened a case with the OpenText Support (#4331438<\/em>) and they confirmed me after a few days that it wasn’t considered an “ERROR<\/strong>“, it was more of an “INFO<\/strong>” message. It’s a strange way to display informative messages but hey, who am I to judge!<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Recently, I was doing some sanity checks on a Documentum Server and I saw a Java exception stack while logging in using iAPI\/iDQL to a Repository. It was reproducible for all Repositories. I’ve never seen something like that before (or at least I don’t remember it) so I was a little bit surprised. Whenever there […]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,525],"tags":[1788,129,1789,233,1790],"type_dbi":[],"class_list":["post-13214","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-_e_","tag-documentum","tag-exception","tag-iapi","tag-idql"],"acf":[],"yoast_head":"\n
Documentum - Java exception stack on iAPI\/iDQL login - dbi Blog<\/title>\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-java-exception-stack-on-iapi-idql-login\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - Java exception stack on iAPI\/iDQL login\" \/>\n<meta property=\"og:description\" content=\"Recently, I was doing some sanity checks on a Documentum Server and I saw a Java exception stack while logging in using iAPI\/iDQL to a Repository. It was reproducible for all Repositories. I’ve never seen something like that before (or at least I don’t remember it) so I was a little bit surprised. Whenever there […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-01-05T07:00:35+00:00\" \/>\n<meta name=\"author\" content=\"Morgan Patou\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@MorganPatou\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Morgan Patou\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 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-java-exception-stack-on-iapi-idql-login\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum – Java exception stack on iAPI\/iDQL login\",\"datePublished\":\"2020-01-05T07:00:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/\"},\"wordCount\":479,\"commentCount\":0,\"keywords\":[\"_E_\",\"Documentum\",\"Exception\",\"iapi\",\"iDQL\"],\"articleSection\":[\"Application integration & Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/\",\"name\":\"Documentum - Java exception stack on iAPI\/iDQL login - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2020-01-05T07:00:35+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum – Java exception stack on iAPI\/iDQL login\"}]},{\"@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\/c4d05b25843a9bc2ab20415dae6bd2d8\",\"name\":\"Morgan Patou\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"caption\":\"Morgan Patou\"},\"description\":\"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.\",\"sameAs\":[\"https:\/\/blog.dbi-services.com\/author\/morgan-patou\/\",\"https:\/\/x.com\/MorganPatou\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Documentum - Java exception stack on iAPI\/iDQL login - dbi Blog","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-java-exception-stack-on-iapi-idql-login\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - Java exception stack on iAPI\/iDQL login","og_description":"Recently, I was doing some sanity checks on a Documentum Server and I saw a Java exception stack while logging in using iAPI\/iDQL to a Repository. It was reproducible for all Repositories. I’ve never seen something like that before (or at least I don’t remember it) so I was a little bit surprised. Whenever there […]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/","og_site_name":"dbi Blog","article_published_time":"2020-01-05T07:00:35+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum – Java exception stack on iAPI\/iDQL login","datePublished":"2020-01-05T07:00:35+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/"},"wordCount":479,"commentCount":0,"keywords":["_E_","Documentum","Exception","iapi","iDQL"],"articleSection":["Application integration & Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/","name":"Documentum - Java exception stack on iAPI\/iDQL login - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2020-01-05T07:00:35+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-java-exception-stack-on-iapi-idql-login\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum – Java exception stack on iAPI\/iDQL login"}]},{"@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\/c4d05b25843a9bc2ab20415dae6bd2d8","name":"Morgan Patou","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","caption":"Morgan Patou"},"description":"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.","sameAs":["https:\/\/blog.dbi-services.com\/author\/morgan-patou\/","https:\/\/x.com\/MorganPatou"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13214","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\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=13214"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13214\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=13214"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=13214"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=13214"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=13214"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}