Recently, I’ve been facing an issue more and more frequently where a Repository cannot register itself to a local\/remote Docbroker. The root cause of the issue is simply that the hostname used for the projection to the Docbroker is too long which prevents the Repository to properly register to it. I’ve seen it recently because when working with Kubernetes, you can pretty quickly end-up with very very long hostnames… The issue isn’t linked to K8s in itself, it just helps to reproduce the issue. Alternatively, you can do the same thing by just tweeking the \/etc\/hosts file to lenghten a name that can then be used for the projection.<\/p>\n
Alright so let’s demonstrate this issue. The simplest way to reproduce the issue is to have a FQDN that is strictly longer than 59 characters and a short hostname that is shorter:<\/p>\n
[dmadmin@documentum-server-0 ~]$ hostname | wc -m\n20\n[dmadmin@documentum-server-0 ~]$ hostname\ndocumentum-server-0\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ hostname -f | wc -m\n63\n[dmadmin@documentum-server-0 ~]$ hostname -f\ndocumentum-server-0.documentum-server.dbi-ns.svc.cluster.local\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ grep \"^host=\" $DOCUMENTUM\/dba\/dm_launch_Docbroker\nhost=documentum-server-0\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ dmqdocbroker -t `hostname` -p 1489 -c ping\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 16.4.0110.0058\nUsing specified port: 1489\nSuccessful reply from docbroker at host (documentum-server-0) on port(1490) running software version (16.4.0110.0167 Linux64).\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ dmqdocbroker -t `hostname -f` -p 1489 -c ping\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 16.4.0110.0058\nUsing specified port: 1489\nSuccessful reply from docbroker at host (documentum-server-0) on port(1490) running software version (16.4.0110.0167 Linux64).\n[dmadmin@documentum-server-0 ~]$<\/pre>\n<\/p>\n
As you can see above, everything seems fine. Let’s see what is the current configuration and if it works properly:<\/p>\n
[dmadmin@documentum-server-0 ~]$ grep \"^host=\" $DOCUMENTUM\/dba\/dm_launch_Docbroker\nhost=documentum-server-0\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ $DOCUMENTUM\/dba\/dm_stop_Docbroker\n.\/dmshutdown 16.4.0000.0248 Linux64 Copyright (c) 2018. OpenText Corporation.\nShutdown request was processed by Docbroker on host documentum-server-0 (INET_ADDR: 01 2d3 01010164 documentum-server-0 1.1.1.100)\nReply status indicates a success: OK\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ $DOCUMENTUM\/dba\/dm_launch_Docbroker\nstarting connection broker on current host: [documentum-server-0]\nwith connection broker log: [$DOCUMENTUM\/dba\/log\/docbroker.documentum-server-0.1489.log]\nconnection broker pid: 19073\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ cat $DOCUMENTUM\/dba\/log\/docbroker.documentum-server-0.1489.log\nOpenText Documentum Connection Broker (version 16.4.0110.0167 Linux64)\nCopyright (c) 2018. OpenText Corporation\n2019-11-16T11:30:44.737512 [DM_DOCBROKER_I_START]info: \"Docbroker has started. Process id: 19073\"\n2019-11-16T11:30:44.747745 [DM_DOCBROKER_I_REGISTERED_PORT]info: \"The Docbroker registered using port (1489).\"\n2019-11-16T11:30:44.747797 [DM_DOCBROKER_I_LISTENING]info: \"The Docbroker is listening on network address: (INET_ADDR: family: 2, port: 1489, host: documentum-server-0 (1.1.1.100, e01234ac))\"\n2019-11-16T11:30:44.747812 [DM_DOCBROKER_I_REGISTERED_PORT]info: \"The Docbroker registered using port (1490).\"\n2019-11-16T11:30:44.747828 [DM_DOCBROKER_I_LISTENING]info: \"The Docbroker is listening on network address: (INET_ADDR: family: 2, port: 1490, host: documentum-server-0 (1.1.1.100, e01234ac))\"\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ grep -A3 \"TARGET]\" $DOCUMENTUM\/dba\/config\/gr_repo\/server.ini\n[DOCBROKER_PROJECTION_TARGET]\nhost = documentum-server-0\nport = 1489\nproximity = 1\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ $DOCUMENTUM\/dba\/dm_start_gr_repo\nstarting Documentum server for repository: [gr_repo]\nwith server log: [$DOCUMENTUM\/dba\/log\/gr_repo.log]\nserver pid: 19245\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ grep broker $DOCUMENTUM\/dba\/log\/gr_repo.log\n2019-11-16T11:31:48.749813 19245[19245] 0000000000000000 [DM_SERVER_I_START]info: \"Sending Initial Docbroker check-point \"\n2019-11-16T11:31:49.008865 19318[19318] 0112d68780000003 [DM_DOCBROKER_I_PROJECTING]info: \"Sending information to Docbroker located on host (documentum-server-0) with port (1490). Information: (Config(gr_repo), Proximity(1), Status(Open), Dormancy Status(Active)).\"\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ dmqdocbroker -t `hostname` -p 1489 -c getdocbasemap\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 16.4.0110.0058\nUsing specified port: 1489\n**************************************************\n** D O C B R O K E R I N F O **\n**************************************************\nDocbroker host : documentum-server-0\nDocbroker port : 1490\nDocbroker network address : INET_ADDR: 01 2d3 01010164 documentum-server-0 1.1.1.100\nDocbroker version : 16.4.0110.0167 Linux64\n**************************************************\n** D O C B A S E I N F O **\n**************************************************\n--------------------------------------------\nDocbase name : gr_repo\nDocbase id : 1234567\nDocbase description : dbi dev k8s gr\nGovern docbase :\nFederation name :\nServer version : 16.4.0110.0167 Linux64.Oracle\nDocbase Roles : Global Registry\nDocbase Dormancy Status :\n--------------------------------------------\n[dmadmin@documentum-server-0 ~]$<\/pre>\n<\/p>\n
So with the above short name on both the Docbroker start script and the Repository projection (server.ini), you can see that it’s all working. Now let’s replicate the issue:<\/p>\n
[dmadmin@documentum-server-0 ~]$ $DOCUMENTUM\/dba\/dm_shutdown_gr_repo\nStopping Documentum server for repository: [gr_repo]\n\n OpenText Documentum iapi - Interactive API interface\n Copyright (c) 2018. OpenText Corporation\n All rights reserved.\n Client Library Release 16.4.0110.0058\n\nConnecting to Server using docbase gr_repo.gr_repo\n[DM_SESSION_I_SESSION_START]info: \"Session 0112d68780012505 started for user dmadmin.\"\n\nConnected to OpenText Documentum Server running Release 16.4.0110.0167 Linux64.Oracle\nSession id is s0\nAPI> shutdown,c,T,T\n...\nOK\nAPI> exit\nBye\nWaiting for 90 seconds for server pid, 19245, to disappear.\n\nSat Nov 16 11:35:35 UTC 2019: Waiting for shutdown of repository: [gr_repo]\nSat Nov 16 11:35:35 UTC 2019: checking for pid: 19245\n\nSat Nov 16 11:35:45 UTC 2019: Waiting for shutdown of repository: [gr_repo]\nSat Nov 16 11:35:45 UTC 2019: checking for pid: 19245\n\nrepository: [gr_repo] has been shutdown\nchecking that all children (19251 19253 19254 19275 19297 19319 19362 19387 19570) have shutdown\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ grep -A3 \"TARGET]\" $DOCUMENTUM\/dba\/config\/gr_repo\/server.ini\n[DOCBROKER_PROJECTION_TARGET]\nhost = documentum-server-0\nport = 1489\nproximity = 1\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ sed -i \"s,^host.*,host = `hostname -f`,\" $DOCUMENTUM\/dba\/config\/gr_repo\/server.ini\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ grep -A3 \"TARGET]\" $DOCUMENTUM\/dba\/config\/gr_repo\/server.ini\n[DOCBROKER_PROJECTION_TARGET]\nhost = documentum-server-0.documentum-server.dbi-ns.svc.cluster.local\nport = 1489\nproximity = 1\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ grep broker $DOCUMENTUM\/dba\/log\/gr_repo.log\n2019-11-16T11:38:34.593108 19715[19715] 0000000000000000 [DM_SERVER_I_START]info: \"Sending Initial Docbroker check-point \"\n2019-11-16T11:38:34.655402 19787[19787] 0112d68780000003 [DM_DOCBROKER_I_PROJECTING]info: \"Sending information to Docbroker located on host (documentum-server-0.documentum-server.dbi-ns.svc.cluster.lo) with port (1489). Information: (Config(gr_repo), Proximity(1), Status(Open), Dormancy Status(Active)).\"\n[dmadmin@documentum-server-0 ~]$<\/pre>\n<\/p>\n
The message seems correct, right? You might be fooled by the message but if you look carefully at it, you can actually see that the host in the parenthesis is cut. The value is “documentum-server-0.documentum-server.dbi-ns.svc.cluster.lo<\/em>” instead of “documentum-server-0.documentum-server.dbi-ns.svc.cluster.local<\/em>“. That’s 59 characters exactly and nothing more. Since our FQDN is longer, then the Repository cut the hostname and keep only the first 59 characters. If you look at the log file directly of if you include the error messages as well in the grep (with the -i option for example for the uppercase BROKER errors), then you can see the failure:<\/p>\n
[dmadmin@documentum-server-0 ~]$ grep -i broker $DOCUMENTUM\/dba\/log\/gr_repo.log\n2019-11-16T11:38:34.593108 19715[19715] 0000000000000000 [DM_SERVER_I_START]info: \"Sending Initial Docbroker check-point \"\n2019-11-16T11:38:34.655141 19787[19787] 0112d68780000003 [DM_DOCBROKER_E_NETWORK_ERROR]error: \"An error occured performing a network operation: ((112) Error opening connection). Network specific error: ( errno: 0, message: Success).\"\n2019-11-16T11:38:34.655364 19787[19787] 0112d68780000003 [DM_DOCBROKER_E_CONNECT_FAILED_EX]error: \"Unable to connect to DocBroker. Clients please check your dfc.properties file for a correct host. Server please check your server.ini or target attributes in server config. Network address: (INET_ADDR: family: 2, port: 1489, host: documentum-server-0.documentum-server.dbi-ns.svc.cluster.lo (0.0.0.0, 00000000)).\"\n2019-11-16T11:38:34.655402 19787[19787] 0112d68780000003 [DM_DOCBROKER_I_PROJECTING]info: \"Sending information to Docbroker located on host (documentum-server-0.documentum-server.dbi-ns.svc.cluster.lo) with port (1489). Information: (Config(gr_repo), Proximity(1), Status(Open), Dormancy Status(Active)).\"\n[dmadmin@documentum-server-0 ~]$\n[dmadmin@documentum-server-0 ~]$ dmqdocbroker -t `hostname` -p 1489 -c getdocbasemap\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 16.4.0110.0058\nUsing specified port: 1489\n**************************************************\n** D O C B R O K E R I N F O **\n**************************************************\nDocbroker host :\nDocbroker port :\nDocbroker network address :\nDocbroker version :\n**************************************************\n** D O C B A S E I N F O **\n**************************************************\n--------------------------------------------\n[dmadmin@documentum-server-0 ~]$<\/pre>\n<\/p>\n
So as you can see above, just putting a hostname too long in the server.ini (or inside the Repository) will prevent it to project itself to the Docbroker and therefore you will never be able to work or even stop the Repository (kill is the only option). Therefore, take care that the hostname you are using for the projection isn’t too long.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Recently, I’ve been facing an issue more and more frequently where a Repository cannot register itself to a local\/remote Docbroker. The root cause of the issue is simply that the hostname used for the projection to the Docbroker is too long which prevents the Repository to properly register to it. I’ve seen it recently because […]<\/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":[1175,1176,129,1180,1760],"type_dbi":[],"class_list":["post-13116","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-dmqdocbroker","tag-docbroker","tag-documentum","tag-projection","tag-repository"],"acf":[],"yoast_head":"\n
Documentum - Beware of long hostnames for the Docbroker - 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-beware-of-long-hostnames-for-the-docbroker\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - Beware of long hostnames for the Docbroker\" \/>\n<meta property=\"og:description\" content=\"Recently, I’ve been facing an issue more and more frequently where a Repository cannot register itself to a local\/remote Docbroker. The root cause of the issue is simply that the hostname used for the projection to the Docbroker is too long which prevents the Repository to properly register to it. I’ve seen it recently because […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-12-07T07:00:45+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=\"7 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-beware-of-long-hostnames-for-the-docbroker\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum – Beware of long hostnames for the Docbroker\",\"datePublished\":\"2019-12-07T07:00:45+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/\"},\"wordCount\":387,\"commentCount\":0,\"keywords\":[\"dmqdocbroker\",\"docbroker\",\"Documentum\",\"Projection\",\"repository\"],\"articleSection\":[\"Application integration & Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/\",\"name\":\"Documentum - Beware of long hostnames for the Docbroker - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-12-07T07:00:45+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum – Beware of long hostnames for the Docbroker\"}]},{\"@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 - Beware of long hostnames for the Docbroker - 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-beware-of-long-hostnames-for-the-docbroker\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - Beware of long hostnames for the Docbroker","og_description":"Recently, I’ve been facing an issue more and more frequently where a Repository cannot register itself to a local\/remote Docbroker. The root cause of the issue is simply that the hostname used for the projection to the Docbroker is too long which prevents the Repository to properly register to it. I’ve seen it recently because […]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/","og_site_name":"dbi Blog","article_published_time":"2019-12-07T07:00:45+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum – Beware of long hostnames for the Docbroker","datePublished":"2019-12-07T07:00:45+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/"},"wordCount":387,"commentCount":0,"keywords":["dmqdocbroker","docbroker","Documentum","Projection","repository"],"articleSection":["Application integration & Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/","name":"Documentum - Beware of long hostnames for the Docbroker - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-12-07T07:00:45+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-beware-of-long-hostnames-for-the-docbroker\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum – Beware of long hostnames for the Docbroker"}]},{"@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\/13116","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=13116"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13116\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=13116"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=13116"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=13116"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=13116"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}