{"id":9921,"date":"2017-04-01T11:09:55","date_gmt":"2017-04-01T09:09:55","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/"},"modified":"2017-04-01T11:09:55","modified_gmt":"2017-04-01T09:09:55","slug":"documentum-wrong-dfc-versions-after-installation-upgrade-or-patch","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/","title":{"rendered":"Documentum &#8211; Wrong dfc versions after installation, upgrade or patch"},"content":{"rendered":"<p>If you are familiar with Documentum or if you already read some of my blogs, then you probably already know that EMC has sometimes issues with libraries. In a previous blog (<a title=\"Documentum story \u2013 Lockbox file is newer than the active Lockbox library\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/\" target=\"_blank\" rel=\"noopener\">this one<\/a>), I talked about the Lockbox versions which caused us an issue and in this blog, I will talk about DFC versions.<\/p>\n<p>Whenever you install a CS patch or another patch, it will probably\u00a0have its own DFC libraries simply because EMC fixed something in it or because it was needed. Whenever you install D2, it will also have its own DFC libraries in the JMS and the WAR files. The problem is that the DFC libraries are everywhere&#8230; Each and every DFC client has its own DFC libraries which come when you install it, patch it, aso&#8230; Basically that&#8217;s not a wrong approach, it ensure that the components will work wherever they are installed so it can always talk to the Content Server.<\/p>\n<p>The problem here is that the DFC libraries are changing at every patch almost and therefore it is kind of complicated to keep a clean environment. It already happened to us that two different patches (CS and D2 for example), released on the exact same day, were using different DFC versions and you will see below another example coming from the same package&#8230;\u00a0 You can live with a server having\u00a0five different DFC versions but this also means that whenever a bug impact one of your DFC library, it will be hard to fix that because you then need to deploy the next official patch which is always a pain. It also multiplies the number of issues that impact your DFC versions since you are running several versions at the same time.<\/p>\n<p>I&#8217;m not saying that you absolutely need to always use only the latest DFC version but if you can properly and quickly perform the appropriate testing, I believe it can brings you something. A few weeks ago for example, one of the Application Teams we are supporting had an issue with some search functionalities in D2. This was actually caused by the DFC version bundled with D2\u00a0(DFC 7.2P03 I think) and we solved this issue by simply using the DFC version coming from our Content Server (DFC 7.2P05)\u00a0which was only\u00a0two patch above.<\/p>\n<p>To quickly and efficiently see which versions of the DFC libraries you are using and where, you can use:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">find &lt;WHERE_TO_FIND&gt; -type f -name dfc.jar -print0 | while read -d $'' file; do echo \"DFC: `$JAVA_HOME\/bin\/java -cp \"$file\" DfShowVersion`  ===  Size: `ls -ks \"$file\" | awk '{print $1}'` kb  ===  Location: $file\"; done\n\nor\n\nfind &lt;WHERE_TO_FIND&gt; -type f -name dfc.jar -print0 | while IFS= read -r -d '' file; do echo \"DFC: `$JAVA_HOME\/bin\/java -cp \"$file\" DfShowVersion`\u00a0 ===\u00a0 Size: `ls -ks \"$file\" | awk '{print $1}'` kb\u00a0 ===\u00a0 Location: $file\"; done<\/pre>\n<p>&nbsp;<\/p>\n<p>You can execute these commands on a Content Server, Application Server (<span style=\"text-decoration: underline\">Note:<\/span> dfc.jar files might be on the D2\/DA war files if you aren&#8217;t using exploded deployments), Full Text Server or any other Linux Servers for what it matters.\u00a0These commands\u00a0handle the spaces in the paths even if normally you shouldn&#8217;t have any for the dfc files. To use them, you can just replace &lt;WHERE_TO_FIND&gt; with the\u00a0base folder\u00a0of your installation.\u00a0This can be $DOCUMENTUM for a Content Server, $XPLORE_HOME for a Full Text Server, aso&#8230; Of course you still need to have the proper permissions to see the files otherwise it will be quite useless to execute this command.<\/p>\n<p>A small example on a Content Server 7.3 (no patches are available yet) including xCP 2.3 P05 (End of February 2017 patch which is supposed to be for CS 7.3):<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [4,6,7,8]\">[dmadmin@content_server_01 ~]$ find $DOCUMENTUM -type f -name dfc.jar -print0 | while read -d $'' file; do echo \"DFC: `$JAVA_HOME\/bin\/java -cp \"$file\" DfShowVersion`  ===  Size: `ls -ks \"$file\" | awk '{print $1}'` kb  ===  Location: $file\"; done\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $DOCUMENTUM\/product\/7.3\/install\/composer\/ComposerHeadless\/plugins\/com.emc.ide.external.dfc_1.0.0\/lib\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $DOCUMENTUM\/shared\/temp\/installer\/wildfly\/dctmutils\/templates\/dfc\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $DOCUMENTUM\/shared\/dfc\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $DOCUMENTUM\/shared\/wildfly9.0.1\/modules\/system\/layers\/base\/emc\/documentum\/security\/main\/dfc.jar\nDFC: 7.2.0210.0184  ===  Size: 15212 kb  ===  Location: $DOCUMENTUM\/shared\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/bpm.ear\/lib\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $DOCUMENTUM\/shared\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/ServerApps.ear\/lib\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $DOCUMENTUM\/shared\/wildfly9.0.1\/server\/DctmServer_MethodServer\/deployments\/acs.ear\/lib\/dfc.jar\nDFC: 7.2.0210.0184  ===  Size: 15212 kb  ===  Location: $DOCUMENTUM\/shared\/wildfly9.0.1\/server\/DctmServer_MethodServer\/tmp\/vfs\/deployment\/deploymente7c710bab402b3f7\/dfc.jar-7ac143a725d0471\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $DOCUMENTUM\/shared\/wildfly9.0.1\/server\/DctmServer_MethodServer\/tmp\/vfs\/deployment\/deploymente7c710bab402b3f7\/dfc.jar-bc760ece35b05a08\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $DOCUMENTUM\/shared\/wildfly9.0.1\/server\/DctmServer_MethodServer\/tmp\/vfs\/deployment\/deploymente7c710bab402b3f7\/dfc.jar-35c79cfe4b79d974\/dfc.jar<\/pre>\n<p>&nbsp;<\/p>\n<p>As you can see above, it looks like there are two different versions of the DFC library on this Content Server which has just been installed: one\u00a0coming from the CS 7.3 which is therefore in 7.3 P00 build number 205 and another version which is still in 7.2 P21 build number 184. This second version has been put on the Content Server by the xCP 2.3 P05 installer. Therefore using a 7.2 library on a 7.3 Content Server is a little bit ugly but the good news is that they are both in a pretty recent version since these two libraries were released almost at the same time (end of 2016\/beginning of 2017). Therefore here I don&#8217;t think it would be\u00a0a big problem even if as soon as the CS 7.3 P01 is out (normally end of this month), we will replace all dfc.jar files with the 7.3 P01 versions.<\/p>\n<p>Another example on a Full Text Server using xPlore 1.6 (same as before, no patches are available yet for xPlore 1.6) including one Primary Dsearch and two IndexAgents for DOCBASE1 and DOCBASE2:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1; highlight: [3,5,7,9]\">[xplore@fulltext_server_01 ~]$ find $XPLORE_HOME -type f -name dfc.jar -print0 | while read -d $'' file; do echo \"DFC: `$JAVA_HOME\/bin\/java -cp \"$file\" DfShowVersion`  ===  Size: `ls -ks \"$file\" | awk '{print $1}'` kb  ===  Location: $file\"; done\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $XPLORE_HOME\/temp\/installer\/wildfly\/dctmutils\/templates\/dfc\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $XPLORE_HOME\/dfc\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $XPLORE_HOME\/wildfly9.0.1\/server\/DctmServer_Indexagent_DOCBASE1\/tmp\/vfs\/deployment\/deployment5417db9ca7307cfc\/dfc.jar-aa1927b943be418f\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $XPLORE_HOME\/wildfly9.0.1\/server\/DctmServer_Indexagent_DOCBASE1\/deployments\/IndexAgent.war\/WEB-INF\/lib\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $XPLORE_HOME\/wildfly9.0.1\/server\/DctmServer_Indexagent_DOCBASE2\/tmp\/vfs\/deployment\/deploymentbb9811e18d147b6a\/dfc.jar-7347e3d3bbd8ffd\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $XPLORE_HOME\/wildfly9.0.1\/server\/DctmServer_Indexagent_DOCBASE2\/deployments\/IndexAgent.war\/WEB-INF\/lib\/dfc.jar\nDFC: 7.3.0000.0196  ===  Size: 15220 kb  ===  Location: $XPLORE_HOME\/wildfly9.0.1\/server\/DctmServer_PrimaryDsearch\/tmp\/vfs\/deployment\/deployment5fd2cff2d805ceb2\/dfc.jar-29edda1355c549b8\/dfc.jar\nDFC: 7.3.0000.0196  ===  Size: 15220 kb  ===  Location: $XPLORE_HOME\/wildfly9.0.1\/server\/DctmServer_PrimaryDsearch\/deployments\/dsearchadmin.war\/WEB-INF\/lib\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $XPLORE_HOME\/wildfly9.0.1\/modules\/system\/layers\/base\/emc\/documentum\/security\/main\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $XPLORE_HOME\/watchdog\/lib\/dfc.jar\nDFC: 7.3.0000.0205  ===  Size: 15236 kb  ===  Location: $XPLORE_HOME\/setup\/qbs\/tool\/lib\/dfc.jar<\/pre>\n<p>&nbsp;<\/p>\n<p>Do you see something strange here? Because I do! This is a completely new xPlore 1.6 server which has just been installed and yet we have two different versions of the DFC libraries&#8230; It&#8217;s not a difference on the minor version but it&#8217;s a difference on the build number! As you can see above, it looks like the PrimaryDsearch uses a DFC 7.3 P00 build number 196 while all other DFC versions\u00a0are in 7.3 P00 build number 205 (so just like the Content Server). The problem here is that each xPlore modules (IA, Dsearch, aso&#8230;) are built by different xPlore Teams. Therefore the team that package the Dsearch libraries\u00a0isn&#8217;t the same that the one that package the IndexAgent libraries.<\/p>\n<p>Since there is a difference here, it probably means that the Dsearch team\u00a0built their\u00a0package some days\/weeks before the other teams (from IA, CS, aso&#8230;)\u00a0and therefore the DFC libraries included in the Dsearch are older&#8230; Is\u00a0it an issue or not? According to EMC, it&#8217;s not, BUT I wouldn&#8217;t be so categorical. If EMC built this library 9 additional times, it&#8217;s not for nothing&#8230; There must be a reason behind those builds and therefore not having the latest build seems a little bit risky to me. Since this is just a sandbox environment, I will most probably just wait for the P01 of the xPlore 1.6 which will be release in a few days and I will implement it to have an aligned version of the DFC for all components.<\/p>\n<p>&nbsp;<\/p>\n<p>Have fun finding issues in the EMC releases :).<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you are familiar with Documentum or if you already read some of my blogs, then you probably already know that EMC has sometimes issues with libraries. In a previous blog (this one), I talked about the Lockbox versions which caused us an issue and in this blog, I will talk about DFC versions. Whenever [&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":[567,129,1059],"type_dbi":[],"class_list":["post-9921","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management","tag-dfc","tag-documentum","tag-libraries"],"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 - Wrong dfc versions after installation, upgrade or patch - 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-wrong-dfc-versions-after-installation-upgrade-or-patch\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - Wrong dfc versions after installation, upgrade or patch\" \/>\n<meta property=\"og:description\" content=\"If you are familiar with Documentum or if you already read some of my blogs, then you probably already know that EMC has sometimes issues with libraries. In a previous blog (this one), I talked about the Lockbox versions which caused us an issue and in this blog, I will talk about DFC versions. Whenever [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-04-01T09:09:55+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-wrong-dfc-versions-after-installation-upgrade-or-patch\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum &#8211; Wrong dfc versions after installation, upgrade or patch\",\"datePublished\":\"2017-04-01T09:09:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/\"},\"wordCount\":1000,\"commentCount\":0,\"keywords\":[\"dfc\",\"Documentum\",\"Libraries\"],\"articleSection\":[\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/\",\"name\":\"Documentum - Wrong dfc versions after installation, upgrade or patch - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2017-04-01T09:09:55+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum &#8211; Wrong dfc versions after installation, upgrade or patch\"}]},{\"@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 - Wrong dfc versions after installation, upgrade or patch - 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-wrong-dfc-versions-after-installation-upgrade-or-patch\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - Wrong dfc versions after installation, upgrade or patch","og_description":"If you are familiar with Documentum or if you already read some of my blogs, then you probably already know that EMC has sometimes issues with libraries. In a previous blog (this one), I talked about the Lockbox versions which caused us an issue and in this blog, I will talk about DFC versions. Whenever [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/","og_site_name":"dbi Blog","article_published_time":"2017-04-01T09:09:55+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-wrong-dfc-versions-after-installation-upgrade-or-patch\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum &#8211; Wrong dfc versions after installation, upgrade or patch","datePublished":"2017-04-01T09:09:55+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/"},"wordCount":1000,"commentCount":0,"keywords":["dfc","Documentum","Libraries"],"articleSection":["Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/","name":"Documentum - Wrong dfc versions after installation, upgrade or patch - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2017-04-01T09:09:55+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-wrong-dfc-versions-after-installation-upgrade-or-patch\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum &#8211; Wrong dfc versions after installation, upgrade or patch"}]},{"@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\/9921","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=9921"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9921\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=9921"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=9921"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=9921"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=9921"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}