{"id":14294,"date":"2020-06-17T19:04:11","date_gmt":"2020-06-17T17:04:11","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/"},"modified":"2020-06-17T19:04:11","modified_gmt":"2020-06-17T17:04:11","slug":"documentum-change-rename-of-ldap-config-object","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/","title":{"rendered":"Documentum – Change\/Rename of LDAP Config object"},"content":{"rendered":"

Using an LDAP Server with Documentum (or any ECM for that matter) is pretty common to avoid managing users locally. In this blog, I wanted to talk about something that isn’t very common and that is the change of an LDAP Server. I’m not talking about just changing the server where your LDAP is hosted but rather changing the full LDAP Server Config inside Documentum (including its name). This is probably something that you will not do very often but I had this use case before so I thought it would be interesting to share.<\/p>\n

 <\/p>\n

So the use case I had was the following one: during a migration (including an upgrade in the process) from Virtual Machines to Kubernetes pods of dozens of environments, I had to automate the setup & management of the LDAP Server as well as normalize the configuration (name & other parameters) according to certain characteristics. The source and target LDAP Server was the same (a_application_type: netscape<\/em>) so it was really just a matter of automation and conventions (if the target isn’t the same, it wouldn’t change anything for this blog). As you know if you already came across one of my previous blogs<\/a>, DA is doing some magic, which prevents you to really manage the LDAP Server in the same way between DA and automation.<\/p>\n

 <\/p>\n

Therefore, the first part of the use case could have just been to change the LDAP Config object “certdb_location”<\/em> parameter from the default “ldapcertdb_loc”<\/em> to another “dm_location”<\/em> which is using a “file” “path_type”<\/em> and not a “directory”<\/em> one. If you understood that last sentence, well done! If you didn’t, don’t worry, I would just suggest you to go and read the blog I linked above. It shows why you would need to use a dedicated dm_location with a path_type set to a file (that is the SSL Certificate of the LDAP Server) in order to automate the setup of an LDAP Config object. Of course, this is only needed if you are using SSL communications with the LDAP Server (i.e. LDAPS). Therefore, that would have been the simple part that is easily understandable, however it is another story if you also need to normalize the LDAP Config object setup in the process. Changing parameters of the LDAP Config object is easy and shouldn’t bring any issues or interruptions, but it’s another story if you need to change the name of the LDAP object… If the field is greyed out in DA, it’s for a reason ;).<\/p>\n

 <\/p>\n

The dozens of environments were all using the exact same backend LDAP Server but there were still some small differences in the setup like different names of course, different attributes mapped here and there, things like that. To be sure everything would be aligned on the target, I took the simplest road: removing all the source LDAP Config objects and recreating them in our CI\/CD (JenkinsX pipelines, Ansible playbooks, aso…). Before removing anything, make sure that you understand what it means for your specific setup<\/span>, it might not always be that straightforward! Alright, let’s check the status of the LDAP at the beginning:<\/p>\n

[dmadmin@stg_cs ~]$ export docbase=REPO1\n[dmadmin@stg_cs ~]$\n[dmadmin@stg_cs ~]$ iapi ${docbase} -U${USER} -Pxxx << EOC\n> ?,c,select r_object_id, object_name from dm_ldap_config;\n> ?,c,select ldap_config_id from dm_server_config;\n> ?,c,select user_source, count(*), user_login_domain from dm_user group by user_login_domain, user_source;\n> EOC\n\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\n\nConnecting to Server using docbase REPO1\n[DM_SESSION_I_SESSION_START]info:  \"Session 010f123451ad5e0f started for user dmadmin.\"\n\n\nConnected to Documentum Server running Release 7.3.0050.0039  Linux64.Oracle\nSession id is s0\nAPI> \nr_object_id       object_name\n----------------  ----------------\n080f1234500edaf3  Source_LDAP_Name\n(1 row affected)\n\nAPI> \nldap_config_id\n----------------\n080f1234500edaf3\n080f1234500edaf3\n080f1234500edaf3\n(3 rows affected)\n\nAPI> \nuser_source       count(*)                user_login_domain\n----------------  ----------------------  -----------------\nLDAP                               55075  Source_LDAP_Name\ninline password                      307  \n                                    1466  \n(3 rows affected)\n\nAPI> Bye\n[dmadmin@stg_cs ~]$<\/pre>\n
 <\/p>\n
As you can see above, there is currently one LDAP Config object that is used by around 55k users. There are three rows for the second query because it’s a HA Repository with 3 Content Servers. The first thing I did was therefore to remove the LDAP Config object and change the different references to prepare for the new name of the object (you can put the two last update commands in just one query, it would be better but I split them here for this example):<\/p>\n
[dmadmin@stg_cs ~]$ export old_ldap_name=Source_LDAP_Name\n[dmadmin@stg_cs ~]$ export new_ldap_name=Target_LDAP_Name\n[dmadmin@stg_cs ~]$\n[dmadmin@stg_cs ~]$ iapi ${docbase} -U${USER} -Pxxx << EOC\n> ?,c,delete dm_ldap_config objects where object_name='${old_ldap_name}';\n> ?,c,update dm_server_config object set ldap_config_id='0000000000000000';\n> ?,c,update dm_user object set user_login_domain='${new_ldap_name}' where user_login_domain='${old_ldap_name}' and user_source='LDAP';\n> ?,c,update dm_user object set user_global_unique_id='' where user_login_domain='${new_ldap_name}' and user_source='LDAP';\n> ?,c,update dm_group object set group_global_unique_id='' where group_source='LDAP';\n> EOC\n \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 \n \nConnecting to Server using docbase REPO1\n[DM_SESSION_I_SESSION_START]info:  \"Session 010f123451ad5e11 started for user dmadmin.\"\n \n \nConnected to Documentum Server running Release 7.3.0050.0039  Linux64.Oracle\nSession id is s0\nAPI> \nobjects_deleted\n---------------\n              1\n(1 row affected)\n[DM_QUERY_I_NUM_UPDATE]info:  \"1 objects were affected by your DELETE statement.\"\n \n \nAPI> \nobjects_updated\n---------------\n              3\n(1 row affected)\n[DM_QUERY_I_NUM_UPDATE]info:  \"3 objects were affected by your UPDATE statement.\"\n \n \nAPI> \nobjects_updated\n---------------\n          55075\n(1 row affected)\n[DM_QUERY_I_NUM_UPDATE]info:  \"55075 objects were affected by your UPDATE statement.\"\n \n \nAPI> \nobjects_updated\n---------------\n          55075\n(1 row affected)\n[DM_QUERY_I_NUM_UPDATE]info:  \"55075 objects were affected by your UPDATE statement.\"\n \n \nAPI>\nobjects_updated\n---------------\n            350\n(1 row affected)\n[DM_QUERY_I_NUM_UPDATE]info: \"350 objects were affected by your UPDATE statement.\"\n \n \nAPI> Bye\n[dmadmin@stg_cs ~]$<\/pre>\n
 <\/p>\n
At the moment, the new LDAP Config object wasn’t created yet but to avoid any disturbance, I already changed the “user_login_domain”<\/em> from the old name to the new one. Another point to note is the reset of the “user_global_unique_id”<\/em> parameter to an empty value (and do the same for the “group_global_unique_id”<\/em>). As soon as users are synchronized using an LDAP, for example, they will be assigned with a unique identity. For an LDAP account, the id should be something like “###dm_ldap_config.object_name###:###random_numbers###”<\/em> (E.g.: Source_LDAP_Name:078b1d9f-f4c35cd2-cad867c1-1f4a7872<\/em>) while for an inline account it should be more “###dm_docbase_config.object_name###:###dm_user.user_name###”<\/em> (E.g.: REPO1:Patou Morgan<\/em>). If you just change the LDAP Config object name and update the “user_login_domain”<\/em> of the user without anything else, in the end, the users won’t be able to login and if you try to execute the LDAP Sync, you should see some warnings showing that your users haven’t been synched (skipped). This is because the user already exist with a different identity. The message on the LDAP Sync would be something like “WARNING: A User with same user_name (Patou Morgan) exists in the docbase with a different identity”<\/em>. The identity is generated by Documentum and written in the dm_user<\/em> object under the “user_global_unique_id”<\/em> attribute. Setting this to an empty value will allow Documentum to generate a new identity so that the user can work with the new LDAP.<\/p>\n
 <\/p>\n
Verification after the deletion:<\/p>\n
[dmadmin@stg_cs ~]$ iapi ${docbase} -U${USER} -Pxxx << EOC\n> ?,c,select r_object_id, object_name from dm_ldap_config;\n> ?,c,select ldap_config_id from dm_server_config;\n> ?,c,select user_source, count(*), user_login_domain from dm_user group by user_login_domain, user_source;\n> EOC\n\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\n\nConnecting to Server using docbase REPO1\n[DM_SESSION_I_SESSION_START]info:  \"Session 010f123451ad5e12 started for user dmadmin.\"\n\n\nConnected to Documentum Server running Release 7.3.0050.0039  Linux64.Oracle\nSession id is s0\nAPI> \nr_object_id       object_name\n----------------  ----------------\n(0 rows affected)\n\nAPI> \nldap_config_id\n----------------\n0000000000000000\n0000000000000000\n0000000000000000\n(3 rows affected)\n\nAPI> \nuser_source       count(*)                user_login_domain\n----------------  ----------------------  -----------------\nLDAP                               55075  Target_LDAP_Name\ninline password                      307  \n                                    1466  \n(3 rows affected)\n\nAPI> Bye\n[dmadmin@stg_cs ~]$<\/pre>\n
 <\/p>\n
Once that was done, I simply re-created a new LDAP Config object as described in the blog I linked at the beginning of this post and using the new name “Target_LDAP_Name”<\/em> (including the re-encryption of the password). Then running the LDAP Sync to make sure everything is working properly and checking the user_global_unique_id<\/em> of some LDAP users to make sure it has been regenerated properly (you can do the same for some groups as well). It should be something like “Source_LDAP_Name:078b1d9f-f4c35cd2-cad867c1-1f4a7872”<\/em> before and then updated to something like “Target_LDAP_Name:2d7c130d-84a47969-926907fa-f1649678”<\/em> after the change of LDAP Config object name (+ execution of LDAP Sync) – obviously the names and the IDs will change in your case.<\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
Using an LDAP Server with Documentum (or any ECM for that matter) is pretty common to avoid managing users locally. In this blog, I wanted to talk about something that isn’t very common and that is the change of an LDAP Server. I’m not talking about just changing the server where your LDAP is hosted […]<\/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":[129,1547,1761,1232,1997],"type_dbi":[],"class_list":["post-14294","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-documentum","tag-ldap","tag-ldaps","tag-rename","tag-user_global_unique_id"],"acf":[],"yoast_head":"\nDocumentum - Change\/Rename of LDAP Config object - 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-change-rename-of-ldap-config-object\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - Change\/Rename of LDAP Config object\" \/>\n<meta property=\"og:description\" content=\"Using an LDAP Server with Documentum (or any ECM for that matter) is pretty common to avoid managing users locally. In this blog, I wanted to talk about something that isn’t very common and that is the change of an LDAP Server. I’m not talking about just changing the server where your LDAP is hosted […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-06-17T17:04:11+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=\"8 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-change-rename-of-ldap-config-object\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum – Change\/Rename of LDAP Config object\",\"datePublished\":\"2020-06-17T17:04:11+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/\"},\"wordCount\":1054,\"commentCount\":0,\"keywords\":[\"Documentum\",\"ldap\",\"LDAPs\",\"Rename\",\"user_global_unique_id\"],\"articleSection\":[\"Application integration & Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/\",\"name\":\"Documentum - Change\/Rename of LDAP Config object - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2020-06-17T17:04:11+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum – Change\/Rename of LDAP Config object\"}]},{\"@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 - Change\/Rename of LDAP Config object - 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-change-rename-of-ldap-config-object\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - Change\/Rename of LDAP Config object","og_description":"Using an LDAP Server with Documentum (or any ECM for that matter) is pretty common to avoid managing users locally. In this blog, I wanted to talk about something that isn’t very common and that is the change of an LDAP Server. I’m not talking about just changing the server where your LDAP is hosted […]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/","og_site_name":"dbi Blog","article_published_time":"2020-06-17T17:04:11+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum – Change\/Rename of LDAP Config object","datePublished":"2020-06-17T17:04:11+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/"},"wordCount":1054,"commentCount":0,"keywords":["Documentum","ldap","LDAPs","Rename","user_global_unique_id"],"articleSection":["Application integration & Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/","name":"Documentum - Change\/Rename of LDAP Config object - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2020-06-17T17:04:11+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-change-rename-of-ldap-config-object\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum – Change\/Rename of LDAP Config object"}]},{"@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\/14294","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=14294"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/14294\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=14294"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=14294"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=14294"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=14294"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}