Have you ever faced an issue where dmqdocbroker, iapi, idql and the likes aren’t able to communicate at all with any Docbroker (connection broker)? Here, I’m not talking about potentially wrong hostname, port or connect modes, which might prevent you to reach a Docbroker if it’s not configured properly because this will still most likely reply to you with an error message… I’m really talking about the utility\/binaries that cannot communicate anymore, it’s like all messages are sent to the void and nothing will ever respond (is that a black-hole I’m seeing?)!<\/p>\n
Earlier this month, I suddenly had this behavior at one of our customer on two out of dozens of Documentum Servers. Everything seemed to be up&running, all the processes were there:<\/p>\n
[dmadmin@cs-0 ~]$ ps -ef\nUID PID PPID C STIME TTY TIME CMD\ndmadmin 7005 1 0 14:11 ? 00:00:00 .\/dmdocbroker -port 1489 -init_file $DOCUMENTUM\/dba\/Docbroker.ini\ndmadmin 7014 1 0 14:11 ? 00:00:00 .\/dmdocbroker -port 1487 -init_file $DOCUMENTUM\/dba\/DocbrokerExt.ini\ndmadmin 7077 1 0 14:11 ? 00:00:07 .\/documentum -docbase_name GR_REPO -security acl -init_file $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\ndmadmin 7087 1 0 14:11 ? 00:00:07 .\/documentum -docbase_name REPO1 -security acl -init_file $DOCUMENTUM\/dba\/config\/REPO1\/server.ini\ndmadmin 7100 7077 0 14:11 ? 00:00:00 $DM_HOME\/bin\/mthdsvr master 0xfd7308a8, 0x7f9f93d81000, 0x223000 1000726 5 7077 GR_REPO $DOCUMENTUM\/dba\/log\ndmadmin 7101 7100 0 14:11 ? 00:00:04 $DM_HOME\/bin\/mthdsvr worker 0xfd7308a8, 0x7f9f93d81000, 0x223000 1000726 5 0 GR_REPO $DOCUMENTUM\/dba\/log\ndmadmin 7102 7087 0 14:11 ? 00:00:00 $DM_HOME\/bin\/mthdsvr master 0xfd7308be, 0x7fe2fe3ac000, 0x223000 1000727 5 7087 REPO1 $DOCUMENTUM\/dba\/log\ndmadmin 7121 7102 0 14:11 ? 00:00:03 $DM_HOME\/bin\/mthdsvr worker 0xfd7308be, 0x7fe2fe3ac000, 0x223000 1000727 5 0 REPO1 $DOCUMENTUM\/dba\/log\ndmadmin 7122 7100 0 14:11 ? 00:00:03 $DM_HOME\/bin\/mthdsvr worker 0xfd7308a8, 0x7f9f93d81000, 0x223000 1000726 5 1 GR_REPO $DOCUMENTUM\/dba\/log\ndmadmin 7123 7077 0 14:11 ? 00:00:00 .\/documentum -docbase_name GR_REPO -security acl -init_file $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\ndmadmin 7124 7077 0 14:11 ? 00:00:00 .\/documentum -docbase_name GR_REPO -security acl -init_file $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\ndmadmin 7144 7102 0 14:11 ? 00:00:04 $DM_HOME\/bin\/mthdsvr worker 0xfd7308be, 0x7fe2fe3ac000, 0x223000 1000727 5 1 REPO1 $DOCUMENTUM\/dba\/log\ndmadmin 7148 7087 0 14:11 ? 00:00:00 .\/documentum -docbase_name REPO1 -security acl -init_file $DOCUMENTUM\/dba\/config\/REPO1\/server.ini\ndmadmin 7149 7087 0 14:11 ? 00:00:00 .\/documentum -docbase_name REPO1 -security acl -init_file $DOCUMENTUM\/dba\/config\/REPO1\/server.ini\ndmadmin 7165 7100 0 14:11 ? 00:00:04 $DM_HOME\/bin\/mthdsvr worker 0xfd7308a8, 0x7f9f93d81000, 0x223000 1000726 5 2 GR_REPO $DOCUMENTUM\/dba\/log\ndmadmin 7166 7077 0 14:11 ? 00:00:00 .\/documentum -docbase_name GR_REPO -security acl -init_file $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\ndmadmin 7167 7102 0 14:11 ? 00:00:03 $DM_HOME\/bin\/mthdsvr worker 0xfd7308be, 0x7fe2fe3ac000, 0x223000 1000727 5 2 REPO1 $DOCUMENTUM\/dba\/log\ndmadmin 7168 7087 0 14:11 ? 00:00:00 .\/documentum -docbase_name REPO1 -security acl -init_file $DOCUMENTUM\/dba\/config\/REPO1\/server.ini\ndmadmin 7169 7100 0 14:11 ? 00:00:04 $DM_HOME\/bin\/mthdsvr worker 0xfd7308a8, 0x7f9f93d81000, 0x223000 1000726 5 3 GR_REPO $DOCUMENTUM\/dba\/log\ndmadmin 7187 7077 0 14:11 ? 00:00:00 .\/documentum -docbase_name GR_REPO -security acl -init_file $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\ndmadmin 7190 7102 0 14:11 ? 00:00:03 $DM_HOME\/bin\/mthdsvr worker 0xfd7308be, 0x7fe2fe3ac000, 0x223000 1000727 5 3 REPO1 $DOCUMENTUM\/dba\/log\ndmadmin 7194 7087 0 14:11 ? 00:00:00 .\/documentum -docbase_name REPO1 -security acl -init_file $DOCUMENTUM\/dba\/config\/REPO1\/server.ini\ndmadmin 7210 7100 0 14:11 ? 00:00:03 $DM_HOME\/bin\/mthdsvr worker 0xfd7308a8, 0x7f9f93d81000, 0x223000 1000726 5 4 GR_REPO $DOCUMENTUM\/dba\/log\ndmadmin 7213 7077 0 14:11 ? 00:00:00 .\/documentum -docbase_name GR_REPO -security acl -init_file $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\ndmadmin 7215 7102 0 14:11 ? 00:00:04 $DM_HOME\/bin\/mthdsvr worker 0xfd7308be, 0x7fe2fe3ac000, 0x223000 1000727 5 4 REPO1 $DOCUMENTUM\/dba\/log\ndmadmin 7225 7087 0 14:11 ? 00:00:00 .\/documentum -docbase_name REPO1 -security acl -init_file $DOCUMENTUM\/dba\/config\/REPO1\/server.ini\ndmadmin 7334 1 0 14:12 ? 00:00:00 \/bin\/sh $JMS_HOME\/server\/startMethodServer.sh\ndmadmin 7336 7334 0 14:12 ? 00:00:00 \/bin\/sh $JMS_HOME\/bin\/standalone.sh\ndmadmin 7447 7336 21 14:12 ? 00:02:57 $JAVA_HOME\/bin\/java -D[Standalone] -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms8g -Xmx8g -XX:MaxMetaspaceSize=512m -XX\ndmadmin 7695 7077 0 14:12 ? 00:00:04 .\/dm_agent_exec -enable_ha_setup 1 -docbase_name GR_REPO.GR_REPO -docbase_owner dmadmin -sleep_duration 0\ndmadmin 7698 7087 0 14:12 ? 00:00:04 .\/dm_agent_exec -enable_ha_setup 1 -docbase_name REPO1.REPO1 -docbase_owner dmadmin -sleep_duration 0\ndmadmin 7908 7077 0 14:13 ? 00:00:00 .\/documentum -docbase_name GR_REPO -security acl -init_file $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\ndmadmin 7918 7087 0 14:13 ? 00:00:00 .\/documentum -docbase_name REPO1 -security acl -init_file $DOCUMENTUM\/dba\/config\/REPO1\/server.ini\ndmadmin 8269 7077 0 14:21 ? 00:00:00 .\/documentum -docbase_name GR_REPO -security acl -init_file $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\ndmadmin 8270 7077 0 14:21 ? 00:00:00 .\/documentum -docbase_name GR_REPO -security acl -init_file $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\ndmadmin 8327 6370 0 14:27 pts\/1 00:00:00 ps -ef\n[dmadmin@cs-0 ~]$<\/pre>\n<\/p>\n
However, I could see the communication issues by looking at the Repository log because it would show that the AgentExec was actually not connected, even after almost 20 minutes:<\/p>\n
[dmadmin@cs-0 ~]$ cd $DOCUMENTUM\/dba\/log\/REPO1\/agentexec\/\n[dmadmin@cs-0 agentexec]$ date\nMon Apr 12 14:29:03 UTC 2021\n[dmadmin@cs-0 agentexec]$\n[dmadmin@cs-0 agentexec]$ tail -8 ..\/..\/REPO1.log\n2021-04-12T14:11:56.453407 7087[7087] 0000000000000000 [DM_WORKFLOW_I_AGENT_START]info: \"Workflow agent worker (pid : 7194, session 010f12345000000c) is started sucessfully.\"\n2021-04-12T14:11:57.455899 7087[7087] 0000000000000000 [DM_SERVER_I_START]info: \"Sending Initial Docbroker check-point \"\n\n2021-04-12T14:11:57.547764 7087[7087] 0000000000000000 [DM_MQ_I_DAEMON_START]info: \"Message queue daemon (pid : 7225, session 010f123450000456) is started sucessfully.\"\n2021-04-12T14:11:58.348442 7223[7223] 010f123450000003 [DM_DOCBROKER_I_PROJECTING]info: \"Sending information to Docbroker located on host (cs-0.domain.com) with port (1490). Information: (Config(REPO1), Proximity(1), Status(Open), Dormancy Status(Active)).\"\n2021-04-12T14:11:58.661666 7223[7223] 010f123450000003 [DM_DOCBROKER_I_PROJECTING]info: \"Sending information to Docbroker located on host (cs-0.domain.com) with port (1488). Information: (Config(REPO1), Proximity(1), Status(Open), Dormancy Status(Active)).\"\n2021-04-12T14:11:58.959490 7223[7223] 010f123450000003 [DM_DOCBROKER_I_PROJECTING]info: \"Sending information to Docbroker located on host (cs-1.domain.com) with port (1490). Information: (Config(REPO1), Proximity(2), Status(Open), Dormancy Status(Active)).\"\nMon Apr 12 14:12:55 2021 [INFORMATION] [AGENTEXEC 7698] Detected during program initialization: Version: 16.4.0200.0256 Linux64\n[dmadmin@cs-0 agentexec]$\n[dmadmin@cs-0 agentexec]$ # Previous startup from the AgentExec logs showing that it didn't start yet\n[dmadmin@cs-0 agentexec]$ tail -2 agentexec.log\nSat Apr 10 19:20:30 2021 [INFORMATION] [LAUNCHER 23135] Detected during program initialization: Version: 16.4.0200.0256 Linux64\nSun Apr 11 19:20:26 2021 [INFORMATION] [LAUNCHER 2890] Detected during program initialization: Version: 16.4.0200.0256 Linux64\n[dmadmin@cs-0 agentexec]$<\/pre>\n<\/p>\n
The interesting part is that the Repositories have all been started properly and projected to the Docbroker. However, any client from the Documentum Server locally wouldn’t be able to connect to the Docbroker. Even more interesting, this was actually a HA environment with 2 CS. The Documentum Server hosting the Primary CS (I will call it cs-0) had the issue while the Documentum Server hosting the Remote CS (I will call it cs-1) had no problem. Executing the dmqdocbroker on the cs-0 to ping the Docbroker of the cs-0 never gave a response, however doing the exact same command to ping the Docbroker of the cs-0 but from the cs-1 host did work without any problem and showed the correct projection of the repositories:<\/p>\n
## on cs-0 (Documentum Server hosting the PCS)\n[dmadmin@cs-0 ~]$ hostname -f\ncs-0.domain.com\n[dmadmin@cs-0 ~]$\n[dmadmin@cs-0 ~]$ time dmqdocbroker -t cs-0.domain.com -p 1489 -c ping\n^C\nreal 0m53.513s\nuser 0m6.132s\nsys 0m0.578s\n[dmadmin@cs-0 ~]$\n[dmadmin@cs-0 ~]$ time echo quit | iapi REPO1.REPO1 -Udmadmin -Pxxx\n^C\nreal 0m46.431s\nuser 0m6.241s\nsys 0m0.575s\n[dmadmin@cs-0 ~]$\n[dmadmin@cs-0 ~]$ time echo quit | iapi REPO1.cs-1_REPO1 -Udmadmin -Pxxx\n^C\nreal 0m35.694s\nuser 0m6.163s\nsys 0m0.582s\n[dmadmin@cs-0 ~]$\n\n## on cs-1 (Documentum Server hosting the RCS)\n[dmadmin@cs-1 ~]$ hostname -f\ncs-1.domain.com\n[dmadmin@cs-1 ~]$\n[dmadmin@cs-1 ~]$ time dmqdocbroker -t cs-0.domain.com -p 1489 -c ping\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 16.4.0200.0080\nUsing specified port: 1489\nSuccessful reply from docbroker at host (cs-0) on port(1490) running software version (16.4.0200.0256 Linux64).\n\nreal 0m3.499s\nuser 0m6.950s\nsys 0m0.469s\n[dmadmin@cs-1 ~]$\n[dmadmin@cs-1 ~]$ time echo quit | iapi REPO1.cs-1_REPO1 -Udmadmin -Pxxx\n\nOpenText Documentum iapi - Interactive API interface\nCopyright (c) 2018. OpenText Corporation\nAll rights reserved.\nClient Library Release 16.4.0200.0080\n\nConnecting to Server using docbase REPO1.cs-1_REPO1\n[DM_SESSION_I_SESSION_START]info: \"Session 010f1234501b635c started for user dmadmin.\"\n\nConnected to OpenText Documentum Server running Release 16.4.0200.0256 Linux64.Oracle\nSession id is s0\nAPI> Bye\n\nreal 0m5.032s\nuser 0m7.401s\nsys 0m0.487s\n[dmadmin@cs-1 ~]$\n[dmadmin@cs-1 ~]$ time echo quit | iapi REPO1.REPO1 -Udmadmin -Pxxx\n\nOpenText Documentum iapi - Interactive API interface\nCopyright (c) 2018. OpenText Corporation\nAll rights reserved.\nClient Library Release 16.4.0200.0080\n\nConnecting to Server using docbase REPO1.REPO1\n[DM_SESSION_I_SESSION_START]info: \"Session 010f1234501b6506 started for user dmadmin.\"\n\nConnected to OpenText Documentum Server running Release 16.4.0200.0256 Linux64.Oracle\nSession id is s0\nAPI> Bye\n\nreal 0m5.315s\nuser 0m7.976s\nsys 0m0.515s\n[dmadmin@cs-1 ~]$<\/pre>\n<\/p>\n
This shows that the issue isn’t the Docbroker or the Repositories themselves but rather the utility\/binaries present on the cs-0 that cannot open communication channels with the local Docbroker, for some reasons… Even after setting debugging on the Docbroker, I could see communications when the dmqdocbroker utility was used on the cs-1 host but nothing was showing-up if the same command was used on the cs-0 host instead. You can enable some logs for the Docbroker by adding “trace=true<\/em><\/strong>” into the Docbroker.ini file and you can also add some other traces by setting the following environment variables (value can be 1 or 10 for example) and then restart the Docbroker: “export DM_DOCBROKER_TRACE=1; export DM_DEBUG_BROKER=1; export DM_TRANS_LOG=1<\/em><\/strong>“. Additionally, you can also add options to the launch script, just like for the Repository part: “-odocbroker_trace -onettrace_all_option -oxxx<\/em><\/strong>“.<\/p>\n
Unfortunately, the dmqdocbroker utility uses the dmawk binary and the iapi\/idql are also binaries so it’s rather difficult to debug further without the source code… After some testing\/debugging, I found something rather hard to believe… All the binaries of the Documentum Server looked OK, they were no changes done in the past few weeks and the files were the same (same hash) than on the cs-1 for example. As you probably know, dmqdocbroker\/iapi\/idql will use the dfc.properties from the folder “$DOCUMENTUM_SHARED\/config\/<\/em>” (with $DOCUMENTUM_SHARED=$DOCUMENTUM forced, starting in 16.4). Therefore, I have been looking into this folder for anything that might disrupt the proper behavior of the utility\/binaries. All the files in this folder were 100% identical between cs-0 and cs-1, except for the encrypted password of the dm_bof_registry as well as the dfc.keystore since both of these are generated once. This would mean that the issue wouldn’t be there, but it was. I started looking into other areas to try to find the root cause but nothing was working. Then, I came back to the config folder and simply tried to empty it… Somehow, the dmqdocbroker was working again, magically! I mean, it printed many errors because the files log4j.properties, dfc.properties and dfc.keystore weren’t there but it replied something… What to do then? Well, I went step by step, putting back the files one by one, as they are supposed to be, and then executing the dmqdocbroker again to see if it stops working.<\/p>\n
The files dfc.properties, log4j.properties, dfcfull.properties, dfc.keystore and all the cache folders were restored properly and the dmqdocbroker was still working without any problem… So what the hell? That’s more or less all of the files, isn’t it? True, that’s all the files, minus the dbor ones: dbor.properties and dbor.properties.lck. At this customer, these files are empty because no configuration was needed. It would be very hard to believe that this could be the issue, right? Well, have a look for yourself:<\/p>\n
[dmadmin@cs-0 ~]$ cd $DOCUMENTUM_SHARED\/config\/\n[dmadmin@cs-0 config]$ ls -l\ntotal 140\ndrwxr-x--- 7 dmadmin dmadmin 4096 Jul 26 2020 ServerApps\ndrwxr-x--- 9 dmadmin dmadmin 4096 Jul 26 2020 Shared\ndrwxr-x--- 7 dmadmin dmadmin 4096 Jul 26 2020 acs\ndrwxr-x--- 7 dmadmin dmadmin 4096 Jul 26 2020 bpm\n-rwxr-x--- 1 dmadmin dmadmin 0 Jul 22 2020 dbor.properties\n-rw-rw-r-- 1 dmadmin dmadmin 0 Jul 26 2020 dbor.properties.lck\n-rw-rw-r-- 1 dmadmin dmadmin 2152 Jul 26 2020 dfc.keystore\n-rw-rw-r-- 1 dmadmin dmadmin 481 Jul 26 2020 dfc.properties\n-rw-rw---- 1 dmadmin dmadmin 70 Jul 22 2020 dfc.properties.bak.0\n-rwxr-x--- 1 dmadmin dmadmin 242 Jul 26 2020 dfc.properties.bak.1\n-rw-rw-r-- 1 dmadmin dmadmin 271 Jul 26 2020 dfc.properties.bak.2\n-rw-rw-r-- 1 dmadmin dmadmin 323 Jul 26 2020 dfc.properties.bak.3\n-rw-rw-r-- 1 dmadmin dmadmin 481 Jul 26 2020 dfc.properties.bak.4\n-rw-rw-r-- 1 dmadmin dmadmin 482 Jul 26 2020 dfc.properties.bak.5\n-rwxrwx--- 1 dmadmin dmadmin 79268 Jul 22 2020 dfcfull.properties\n-rwxr-x--- 1 dmadmin dmadmin 1242 Jul 26 2020 log4j.properties\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ # With the initial content, dmqdocbroker isn't working\n[dmadmin@cs-0 config]$ date; time dmqdocbroker -t cs-0.domain.com -p 1489 -c ping; date\nWed Apr 14 07:43:28 UTC 2021\n^C\nreal 0m22.718s\nuser 0m6.401s\nsys 0m0.853s\nWed Apr 14 07:43:51 UTC 2021\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ mkdir test\n[dmadmin@cs-0 config]$ mv * test\/\nmv: cannot move 'test' to a subdirectory of itself, 'test\/test'\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ ls -l\ntotal 4\ndrwxr-x--- 6 dmadmin dmadmin 4096 Apr 14 07:44 test\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ # With the folder empty, dmqdocbroker is \"working\" (errors but expected ones)\n[dmadmin@cs-0 config]$ date; time dmqdocbroker -t cs-0.domain.com -p 1489 -c ping; date\nWed Apr 14 07:45:15 UTC 2021\n0 [main] ERROR com.documentum.fc.common.impl.logging.LoggingConfigurator - Problem locating log4j configuration\n1 [main] WARN com.documentum.fc.common.impl.logging.LoggingConfigurator - Using default log4j configuration\n3 [main] ERROR com.documentum.fc.common.impl.preferences.PreferencesManager - [DFC_PREFERENCE_LOAD_FAILED] Failed to load persistent preferences from null\njava.io.FileNotFoundException: dfc.properties\n at com.documentum.fc.common.impl.preferences.PreferencesManager.locateMainPersistentStore(PreferencesManager.java:378)\n at com.documentum.fc.common.impl.preferences.PreferencesManager.readPersistentProperties(PreferencesManager.java:329)\n at com.documentum.fc.common.impl.preferences.PreferencesManager.<init>(PreferencesManager.java:37)\n ...\n2862 [main] ERROR com.documentum.fc.client.security.impl.IdentityManager - [DFC_SECURITY_IDENTITY_INIT] no identity initialization or incomplete identity initialization\nDfException:: THREAD: main; MSG: ; ERRORCODE: ff; NEXT: null\n at com.documentum.fc.client.security.impl.JKSKeystoreUtil.creteNewKeystoreFile(JKSKeystoreUtil.java:425)\n at com.documentum.fc.client.security.impl.JKSKeystoreUtil.createNewKeystore(JKSKeystoreUtil.java:209)\n at com.documentum.fc.client.security.impl.DfcIdentityKeystore.applyDfcInitPolicy(DfcIdentityKeystore.java:95)\n ...\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 16.4.0200.0080\nUsing specified port: 1489\nSuccessful reply from docbroker at host (cs-0) on port(1490) running software version (16.4.0200.0256 Linux64).\n\nreal 0m3.763s\nuser 0m6.265s\nsys 0m0.672s\nWed Apr 14 07:45:19 UTC 2021\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ ls -l\ntotal 12\ndrwxr-x--- 8 dmadmin dmadmin 4096 Apr 14 07:45 documentum\n-rw-r----- 1 dmadmin dmadmin 3245 Apr 14 07:45 log4j.log\ndrwxr-x--- 6 dmadmin dmadmin 4096 Apr 14 07:44 test\n-rw-r----- 1 dmadmin dmadmin 0 Apr 14 07:45 trace.log\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ rm -rf documentum\/ log4j.log trace.log\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ mv test\/log4j.properties .\/\n[dmadmin@cs-0 config]$ mv test\/dfc.properties .\/\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ # With the folder empty exept for log4j.properties and dfc.properties files, dmqdocbroker is working\n[dmadmin@cs-0 config]$ date; time dmqdocbroker -t cs-0.domain.com -p 1489 -c ping; date\nWed Apr 14 07:47:17 UTC 2021\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 16.4.0200.0080\nUsing specified port: 1489\nSuccessful reply from docbroker at host (cs-0) on port(1490) running software version (16.4.0200.0256 Linux64).\n\nreal 0m4.280s\nuser 0m8.161s\nsys 0m0.729s\nWed Apr 14 07:47:21 UTC 2021\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ ls -l\ntotal 20\ndrwxr-x--- 8 dmadmin dmadmin 4096 Apr 14 07:47 Shared\n-rw-r----- 1 dmadmin dmadmin 2153 Apr 14 07:47 dfc.keystore\n-rw-rw-r-- 1 dmadmin dmadmin 481 Jul 26 2020 dfc.properties\n-rwxr-x--- 1 dmadmin dmadmin 1242 Jul 26 2020 log4j.properties\ndrwxr-x--- 6 dmadmin dmadmin 4096 Apr 14 07:46 test\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ rm -rf Shared\/ dfc.keystore\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ mv test\/dfc.keystore .\/\n[dmadmin@cs-0 config]$ mv test\/dfcfull.properties .\/\n[dmadmin@cs-0 config]$ mv test\/dfc.properties* .\/\n[dmadmin@cs-0 config]$ mv test\/log4j.properties* .\/\n[dmadmin@cs-0 config]$ mv test\/ServerApps .\/\n[dmadmin@cs-0 config]$ mv test\/Shared .\/\n[dmadmin@cs-0 config]$ mv test\/acs .\/\n[dmadmin@cs-0 config]$ mv test\/bpm .\/\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ ls -l\ntotal 140\ndrwxr-x--- 7 dmadmin dmadmin 4096 Jul 26 2020 ServerApps\ndrwxr-x--- 9 dmadmin dmadmin 4096 Jul 26 2020 Shared\ndrwxr-x--- 7 dmadmin dmadmin 4096 Jul 26 2020 acs\ndrwxr-x--- 7 dmadmin dmadmin 4096 Jul 26 2020 bpm\n-rw-rw-r-- 1 dmadmin dmadmin 2152 Jul 26 2020 dfc.keystore\n-rw-rw-r-- 1 dmadmin dmadmin 481 Jul 26 2020 dfc.properties\n-rw-rw---- 1 dmadmin dmadmin 70 Jul 22 2020 dfc.properties.bak.0\n-rwxr-x--- 1 dmadmin dmadmin 242 Jul 26 2020 dfc.properties.bak.1\n-rw-rw-r-- 1 dmadmin dmadmin 271 Jul 26 2020 dfc.properties.bak.2\n-rw-rw-r-- 1 dmadmin dmadmin 323 Jul 26 2020 dfc.properties.bak.3\n-rw-rw-r-- 1 dmadmin dmadmin 481 Jul 26 2020 dfc.properties.bak.4\n-rw-rw-r-- 1 dmadmin dmadmin 482 Jul 26 2020 dfc.properties.bak.5\n-rwxrwx--- 1 dmadmin dmadmin 79268 Jul 22 2020 dfcfull.properties\n-rwxr-x--- 1 dmadmin dmadmin 1242 Jul 26 2020 log4j.properties\ndrwxr-x--- 2 dmadmin dmadmin 4096 Apr 14 07:51 test\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ ls -l test\/\ntotal 0\n-rwxr-x--- 1 dmadmin dmadmin 0 Jul 22 2020 dbor.properties\n-rw-rw-r-- 1 dmadmin dmadmin 0 Jul 26 2020 dbor.properties.lck\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ # With the full folder except the dbor files, dmqdocbroker is still working\n[dmadmin@cs-0 config]$ date; time dmqdocbroker -t cs-0.domain.com -p 1489 -c ping; date\nWed Apr 14 07:51:30 UTC 2021\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 16.4.0200.0080\nUsing specified port: 1489\nSuccessful reply from docbroker at host (cs-0) on port(1490) running software version (16.4.0200.0256 Linux64).\n\nreal 0m3.501s\nuser 0m6.632s\nsys 0m0.666s\nWed Apr 14 07:51:34 UTC 2021\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ mv test\/dbor.properties* .\/\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ # With the dbor files back, dmqdocbroker isn't working anymore\n[dmadmin@cs-0 config]$ date; time dmqdocbroker -t cs-0.domain.com -p 1489 -c ping; date\nWed Apr 14 07:51:56 UTC 2021\n^C\nreal 0m30.682s\nuser 0m5.001s\nsys 0m0.424s\nWed Apr 14 07:52:27 UTC 2021\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ mv dbor.properties.lck test\/\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ # Removing just the dbor files again, dmqdocbroker is working again\n[dmadmin@cs-0 config]$ date; time dmqdocbroker -t cs-0.domain.com -p 1489 -c ping; date\nWed Apr 14 07:52:36 UTC 2021\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 16.4.0200.0080\nUsing specified port: 1489\nSuccessful reply from docbroker at host (cs-0) on port(1490) running software version (16.4.0200.0256 Linux64).\n\nreal 0m3.185s\nuser 0m5.546s\nsys 0m0.578s\nWed Apr 14 07:52:39 UTC 2021\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ ll\ntotal 140\ndrwxr-x--- 7 dmadmin dmadmin 4096 Jul 26 2020 ServerApps\ndrwxr-x--- 9 dmadmin dmadmin 4096 Jul 26 2020 Shared\ndrwxr-x--- 7 dmadmin dmadmin 4096 Jul 26 2020 acs\ndrwxr-x--- 7 dmadmin dmadmin 4096 Jul 26 2020 bpm\n-rwxr-x--- 1 dmadmin dmadmin 0 Jul 22 2020 dbor.properties\n-rw-r----- 1 dmadmin dmadmin 0 Apr 14 07:52 dbor.properties.lck\n-rw-rw-r-- 1 dmadmin dmadmin 2152 Jul 26 2020 dfc.keystore\n-rw-rw-r-- 1 dmadmin dmadmin 481 Jul 26 2020 dfc.properties\n-rw-rw---- 1 dmadmin dmadmin 70 Jul 22 2020 dfc.properties.bak.0\n-rwxr-x--- 1 dmadmin dmadmin 242 Jul 26 2020 dfc.properties.bak.1\n-rw-rw-r-- 1 dmadmin dmadmin 271 Jul 26 2020 dfc.properties.bak.2\n-rw-rw-r-- 1 dmadmin dmadmin 323 Jul 26 2020 dfc.properties.bak.3\n-rw-rw-r-- 1 dmadmin dmadmin 481 Jul 26 2020 dfc.properties.bak.4\n-rw-rw-r-- 1 dmadmin dmadmin 482 Jul 26 2020 dfc.properties.bak.5\n-rwxrwx--- 1 dmadmin dmadmin 79268 Jul 22 2020 dfcfull.properties\n-rwxr-x--- 1 dmadmin dmadmin 1242 Jul 26 2020 log4j.properties\ndrwxr-x--- 2 dmadmin dmadmin 4096 Apr 14 07:52 test\n[dmadmin@cs-0 config]$\n[dmadmin@cs-0 config]$ diff dbor.properties.lck test\/dbor.properties.lck\n[dmadmin@cs-0 config]$<\/pre>\n<\/p>\n
So as you can see above (it’s rather long but I wanted to put all the evidences I gathered because I still cannot believe this is the cause of the issue), just removing\/renaming the empty file “dbor.properties.lck<\/em>” which was there, untouched, since almost 9 months is sufficient to have the dmqdocbroker\/iapi\/idql working again… Trying to put back the old empty file, the issue will come back. It’s the “same” file, same content (empty), same file format, everything… The only difference would be the Inode of course and the creation\/modification dates.<\/p>\n
After some more investigations, the issue appeared to be on the NAS behind which was still having a lock on the file, somehow. For information, I also had the same behavior on a second environment but with the file “$DOCUMENTUM\/config\/ServerApps\/identityInterprocessMutex.lock<\/em>” this time… So if that even happen to you, take a look at these lock files under $DOCUMENTUM\/config and make sure there are no problems with the storage.<\/p>\n","protected":false},"excerpt":{"rendered":"
Have you ever faced an issue where dmqdocbroker, iapi, idql and the likes aren’t able to communicate at all with any Docbroker (connection broker)? Here, I’m not talking about potentially wrong hostname, port or connect modes, which might prevent you to reach a Docbroker if it’s not configured properly because this will still most likely […]<\/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":[2354,1175,129,233,1790],"type_dbi":[],"class_list":["post-16509","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-dbor","tag-dmqdocbroker","tag-documentum","tag-iapi","tag-idql"],"acf":[],"yoast_head":"\n
Documentum - dmqdocbroker\/iapi\/idql not working because of dbor.properties.lck - 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-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - dmqdocbroker\/iapi\/idql not working because of dbor.properties.lck\" \/>\n<meta property=\"og:description\" content=\"Have you ever faced an issue where dmqdocbroker, iapi, idql and the likes aren’t able to communicate at all with any Docbroker (connection broker)? Here, I’m not talking about potentially wrong hostname, port or connect modes, which might prevent you to reach a Docbroker if it’s not configured properly because this will still most likely […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-06-30T15:10:31+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=\"16 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-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\\\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum – dmqdocbroker\\\/iapi\\\/idql not working because of dbor.properties.lck\",\"datePublished\":\"2021-06-30T15:10:31+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\\\/\"},\"wordCount\":969,\"commentCount\":0,\"keywords\":[\"dbor\",\"dmqdocbroker\",\"Documentum\",\"iapi\",\"iDQL\"],\"articleSection\":[\"Application integration & Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\\\/\",\"name\":\"Documentum - dmqdocbroker\\\/iapi\\\/idql not working because of dbor.properties.lck - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2021-06-30T15:10:31+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum – dmqdocbroker\\\/iapi\\\/idql not working because of dbor.properties.lck\"}]},{\"@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 - dmqdocbroker\/iapi\/idql not working because of dbor.properties.lck - 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-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - dmqdocbroker\/iapi\/idql not working because of dbor.properties.lck","og_description":"Have you ever faced an issue where dmqdocbroker, iapi, idql and the likes aren’t able to communicate at all with any Docbroker (connection broker)? Here, I’m not talking about potentially wrong hostname, port or connect modes, which might prevent you to reach a Docbroker if it’s not configured properly because this will still most likely […]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/","og_site_name":"dbi Blog","article_published_time":"2021-06-30T15:10:31+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"16 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum – dmqdocbroker\/iapi\/idql not working because of dbor.properties.lck","datePublished":"2021-06-30T15:10:31+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/"},"wordCount":969,"commentCount":0,"keywords":["dbor","dmqdocbroker","Documentum","iapi","iDQL"],"articleSection":["Application integration & Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/","name":"Documentum - dmqdocbroker\/iapi\/idql not working because of dbor.properties.lck - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2021-06-30T15:10:31+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-dmqdocbroker-iapi-idql-not-working-because-of-dbor-properties-lck\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum – dmqdocbroker\/iapi\/idql not working because of dbor.properties.lck"}]},{"@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\/16509","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=16509"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/16509\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=16509"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=16509"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=16509"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=16509"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}