{"id":10465,"date":"2017-09-23T14:23:20","date_gmt":"2017-09-23T12:23:20","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/"},"modified":"2017-09-23T14:23:20","modified_gmt":"2017-09-23T12:23:20","slug":"documentum-cs-7-3-issue-with-dmqdocbroker","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/","title":{"rendered":"Documentum &#8211; CS 7.3 &#8211; Issue with dmqdocbroker"},"content":{"rendered":"<p>Beginning of this month, I was building a new environment in 7.3 P05 (using silent installation but this isn&#8217;t relevant here) and I found a strange behaviour from the dmqdocbroker so I wanted to share that. You will see below an error message &#8220;Input has special characters &#8230;&#8221;. This is specific to the CS 7.3 for which we opened a SR with EMC\/OTX some months ago (beginning of this year during the first CS 7.3 tests we performed) but the outcome of this SR was that this shouldn&#8217;t have any impact on the proper behaviour of the docbroker so I didn&#8217;t blog about it back then but now, it might very well be linked to the issue I will discuss here.<\/p>\n<p>&nbsp;<\/p>\n<p>So let&#8217;s talk about the issue with the dmqdocbroker. In this new environment, we configured several docbases and several docbrokers so that we can have separated applications. I will create another blog related to the projections (with another issue) so here I&#8217;m directly getting to the point. The issue I faced is that the first (default) docbroker was working properly, responding to the ping, listing all docbases, aso&#8230; But then when I created two additional docbrokers, these two docbrokers weren&#8217;t behaving in the same way&#8230;<\/p>\n<p>&nbsp;<\/p>\n<p>To show that, I can simply execute the ping or getdocbasemap command for each docbrokers (for this example, I will use the following ports: first docbroker on 1489\/1490, second one on 1491\/1492, third one on 1493\/1494). We are always using secure communications so that&#8217;s why you will always see the secure port below in the replies:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [1,8,11,19,29,37]\">[dmadmin@content-server-01 ~]$ dmqdocbroker -p 1489 -c ping\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nTargeting current host\n$DM_HOME\/bin\/dmawk: Input has special characters ...\n source line number 624\nUsing specified port: 1489\nSuccessful reply from docbroker at host (content-server-01) on port(1490) running software version (7.3.0050.0039  Linux64).\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$ dmqdocbroker -p 1491 -c ping\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nTargeting current host\n$DM_HOME\/bin\/dmawk: Input has special characters ...\n source line number 624\nUsing specified port: 1491\ndmqdocbroker: Error returned from docbroker request:\n[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker \":1491\" failed\n\n[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker \":1491\" failed\n\n[DM_SESSION_E_RPC_ERROR]error:  \"Server communication failure\"\n\njava.net.ConnectException: Connection refused\n\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$ dmqdocbroker -p 1493 -c ping\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nTargeting current host\n$DM_HOME\/bin\/dmawk: Input has special characters ...\n source line number 624\nUsing specified port: 1493\ndmqdocbroker: Error returned from docbroker request:\n[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker \":1493\" failed\n\n[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker \":1493\" failed\n\n[DM_SESSION_E_RPC_ERROR]error:  \"Server communication failure\"\n\njava.net.ConnectException: Connection refused\n\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$<\/pre>\n<p>&nbsp;<\/p>\n<p>As you can see, the request to the docbroker &#8220;:&lt;port&gt;&#8221; failed&#8230; But wait, why is there only the port here? Why is the hostname not mentioned in the error message? Well, that&#8217;s a pretty good question! For an unknown reason, the request to the first docbroker is working properly (ping successful) but then the request to the two others isn&#8217;t. It&#8217;s just like if the hostname was known for the first one but not for the others&#8230;<\/p>\n<p>&nbsp;<\/p>\n<p>So since it is possible to specify which host to target, then what happen if you specify that?<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [4,8,11,15,18,22]\">[dmadmin@content-server-01 ~]$ echo `hostname -f`\ncontent-server-01\n[dmadmin@content-server-01 ~]$ \n[dmadmin@content-server-01 ~]$ dmqdocbroker -t `hostname -f` -p 1489 -c ping\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nUsing specified port: 1489\nSuccessful reply from docbroker at host (content-server-01) on port(1490) running software version (7.3.0050.0039  Linux64).\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$ dmqdocbroker -t `hostname -f` -p 1491 -c ping\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nUsing specified port: 1491\nSuccessful reply from docbroker at host (content-server-01) on port(1492) running software version (7.3.0050.0039  Linux64).\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$ dmqdocbroker -t `hostname -f` -p 1493 -c ping\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nUsing specified port: 1493\nSuccessful reply from docbroker at host (content-server-01) on port(1494) running software version (7.3.0050.0039  Linux64).\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$<\/pre>\n<p>&nbsp;<\/p>\n<p>And here all three docbrokers are replying successfully&#8230; And in case you didn&#8217;t notice, even the message &#8220;Input has special characters &#8230;&#8221; isn&#8217;t displayed here. So for me, this shows that this message might very well be linked to this particular behaviour.<\/p>\n<p>&nbsp;<\/p>\n<p>I&#8217;m not 100% sure what the issue is (I didn&#8217;t get time to open a SR for this yet) but if I had to guess, I would suggest you to read carefully the next blogs I will post today because this issue might be linked by the dash (&#8216;-&#8216;) (&lt;&#8211; no this isn&#8217;t a smiley!) in the hostname.<\/p>\n<p>&nbsp;<\/p>\n<p>I only showed the ping above but I can reproduce the same behaviour with the getdocbasemap for example:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [1,9,19,]\">[dmadmin@content-server-01 ~]$ dmqdocbroker -p 1493 -c getdocbasemap\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nTargeting current host\n$DM_HOME\/bin\/dmawk: Input has special characters ...\n source line number 624\nUsing specified port: 1493\ndmqdocbroker: Error returned from docbroker request:\n[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker \":1493\" failed\n\n[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker \":1493\" failed\n\n[DM_SESSION_E_RPC_ERROR]error:  \"Server communication failure\"\n\njava.net.ConnectException: Connection refused\n\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$\n[dmadmin@content-server-01 ~]$ dmqdocbroker -t `hostname -f` -p 1493 -c getdocbasemap\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nUsing specified port: 1493\n**************************************************\n**     D O C B R O K E R    I N F O             **\n**************************************************\nDocbroker host            : content-server-01\nDocbroker port            : 1494\nDocbroker network address : INET_ADDR: 03 52f 91f62f98 content-server-01 156.174.191.17\nDocbroker version         : 7.3.0050.0039  Linux64\n**************************************************\n**     D O C B A S E   I N F O                  **\n**************************************************\n--------------------------------------------\nDocbase name        : DocBase1\nDocbase id          : 1000002\nDocbase description : DocBase1 Repository\nGovern docbase      :\nFederation name     :\nServer version      : 7.3.0050.0039  Linux64.Oracle\nDocbase Roles       :\nDocbase Dormancy Status     :\n--------------------------------------------\nDocbase name        : GR_DocBase\nDocbase id          : 1000001\nDocbase description : GR_DocBase Repository\nGovern docbase      :\nFederation name     :\nServer version      : 7.3.0050.0039  Linux64.Oracle\nDocbase Roles       : Global Registry\nDocbase Dormancy Status     :\n--------------------------------------------\n[dmadmin@content-server-01 ~]$<\/pre>\n<p>&nbsp;<\/p>\n<p>If you don&#8217;t see this issue with a hostname that doesn&#8217;t contain any dash, please let me know! This would confirm that both issues are linked to that&#8230; As mentioned earlier, you will see in the next blog why I think this has something to do with the dash ;).<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Beginning of this month, I was building a new environment in 7.3 P05 (using silent installation but this isn&#8217;t relevant here) and I found a strange behaviour from the dmqdocbroker so I wanted to share that. You will see below an error message &#8220;Input has special characters &#8230;&#8221;. This is specific to the CS 7.3 [&hellip;]<\/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":[525],"tags":[971,1151,1175,1176,129],"type_dbi":[],"class_list":["post-10465","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management","tag-7-3","tag-cs-7-3","tag-dmqdocbroker","tag-docbroker","tag-documentum"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Documentum - CS 7.3 - Issue with dmqdocbroker - 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-cs-7-3-issue-with-dmqdocbroker\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - CS 7.3 - Issue with dmqdocbroker\" \/>\n<meta property=\"og:description\" content=\"Beginning of this month, I was building a new environment in 7.3 P05 (using silent installation but this isn&#8217;t relevant here) and I found a strange behaviour from the dmqdocbroker so I wanted to share that. You will see below an error message &#8220;Input has special characters &#8230;&#8221;. This is specific to the CS 7.3 [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-09-23T12:23:20+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=\"5 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-cs-7-3-issue-with-dmqdocbroker\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum &#8211; CS 7.3 &#8211; Issue with dmqdocbroker\",\"datePublished\":\"2017-09-23T12:23:20+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/\"},\"wordCount\":552,\"commentCount\":0,\"keywords\":[\"7.3\",\"CS 7.3\",\"dmqdocbroker\",\"docbroker\",\"Documentum\"],\"articleSection\":[\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/\",\"name\":\"Documentum - CS 7.3 - Issue with dmqdocbroker - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2017-09-23T12:23:20+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum &#8211; CS 7.3 &#8211; Issue with dmqdocbroker\"}]},{\"@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 &amp; 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 - CS 7.3 - Issue with dmqdocbroker - 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-cs-7-3-issue-with-dmqdocbroker\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - CS 7.3 - Issue with dmqdocbroker","og_description":"Beginning of this month, I was building a new environment in 7.3 P05 (using silent installation but this isn&#8217;t relevant here) and I found a strange behaviour from the dmqdocbroker so I wanted to share that. You will see below an error message &#8220;Input has special characters &#8230;&#8221;. This is specific to the CS 7.3 [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/","og_site_name":"dbi Blog","article_published_time":"2017-09-23T12:23:20+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum &#8211; CS 7.3 &#8211; Issue with dmqdocbroker","datePublished":"2017-09-23T12:23:20+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/"},"wordCount":552,"commentCount":0,"keywords":["7.3","CS 7.3","dmqdocbroker","docbroker","Documentum"],"articleSection":["Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/","name":"Documentum - CS 7.3 - Issue with dmqdocbroker - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2017-09-23T12:23:20+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-cs-7-3-issue-with-dmqdocbroker\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum &#8211; CS 7.3 &#8211; Issue with dmqdocbroker"}]},{"@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 &amp; 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\/10465","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=10465"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10465\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=10465"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=10465"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=10465"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=10465"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}