A few weeks ago at a customer, I was installing a completely new sandbox environment for one of our Application Teams. On this environment, we used a new version stack with the most recent patch set (at that time): CS 7.2 P16, D2 4.6 P05, aso… A new patch level means a lot of “fun” trying to install and execute the updated installers of Documentum\/BPM\/D2… And of course a lot of new bugs ;). In this blog I will talk about a new issue we never faced before that is related to the Lockbox libraries.<\/p>\n
<\/p>\n
With the older version stack, when we installed D2, we always kept the D2 Lockbox libraries under $DOCUMENTUM\/d2-lib\/lockbox on the CS and then we referenced these libraries in the environment variable ($PATH, $LD_LIBRARY_PATH and $CLASSPATH) of our Installation Owner. In the documentation, it is not asked to set these variables as “permanent” by adding them in the bash_profile for example or something similar but this is what we used to do to avoid adding them again and again each time we needed to update the D2 Lockbox.<\/p>\n
<\/p>\n
For this new version stack and since the Official Documentation didn’t change, we kept the same approach. After installing D2, we had to restart the Content Server for a maintenance at the OS level. As you probably already know if you are familiar with the CS 7.2, there is also a Lockbox specific to the CS that is normally stored under $DOCUMENTUM\/dba\/secure\/. Whenever you restart the host, you will need to store the lockbox inside the Shared Memory and that’s how it is done:<\/p>\n
[dmadmin@content_server_01 ~]$ pwlockbox=\"L0ckb0xP4ssphr4se\"\n[dmadmin@content_server_01 ~]$ pwaek=\"A3kP4ssphr4se\"\n[dmadmin@content_server_01 ~]$ \n[dmadmin@content_server_01 ~]$ dm_crypto_boot -lockbox lockbox.lb -lockboxpassphrase $pwlockbox -passphrase $pwaek -all\n\nPlease wait. This will take a few seconds ...\n\nPlease wait, this will take a few seconds..\nSetting up the (single) passphrase for all keys in the shared memory region..\nOperation succeeded\n[dmadmin@content_server_01 ~]$ \n[dmadmin@content_server_01 ~]$ \n[dmadmin@content_server_01 ~]$ dm_crypto_manage_lockbox -lockbox lockbox.lb -lockboxpassphrase $pwlockbox -resetfingerprint\nLockbox lockbox.lb\nLockbox Path $DOCUMENTUM\/dba\/secure\/lockbox.lb\nReset host done<\/pre>\n<\/p>\n
These two commands are working properly so the Lockbox has been put in the Shared Memory – normally – and the docbases should now be able to start. As explained before, we are referencing the D2 Lockbox libraries inside the environment variable by default and not the CS specific versions. So I tried to start the docbase as always and checked the logs to ensure that it was running properly:<\/p>\n
[dmadmin@content_server_01 ~]$ $DOCUMENTUM\/dba\/dm_start_GR_DOCBASE\nstarting Documentum server for repository: [GR_DOCBASE]\nwith server log: [$DOCUMENTUM\/dba\/log\/GR_DOCBASE.log]\nserver pid: 7056\n[dmadmin@content_server_01 ~]$\n[dmadmin@content_server_01 ~]$ cat $DOCUMENTUM\/dba\/log\/GR_DOCBASE.log\nThe Lockbox file is newer than the active Lockbox library. Retry with a newer version of the Lockbox library.\nThe Lockbox file is newer than the active Lockbox library. Retry with a newer version of the Lockbox library.\n2016-09-29T12:02:38.314624 7056[7056] 0000000000000000 [DM_CRYPTO_F_KEYSTORE_INIT]fatal: \"Failed to initialize keystore at $DOCUMENTUM\/dba\/secure\/CSaek. Internal error - 1057226514\"\n\n[dmadmin@content_server_01 ~]$\n[dmadmin@content_server_01 ~]$<\/pre>\n<\/p>\n
So that’s the error I wanted to share in this blog. As you can see, the docbase wasn’t able to start because the lockbox file is “newer” than the active Lockbox libraries. So I started to do some tests to try to understand what was happening exactly and how to solve it.<\/p>\n
<\/p>\n
Ok so the first test I did is removing the D2 Lockbox libraries from the environment variables (.bash_profile + reload of shell session) and then try to start the docbase again:<\/p>\n
[dmadmin@content_server_01 ~]$\n[dmadmin@content_server_01 ~]$ exit\nlogout\n[morganpatou@content_server_01 ~]$ su - dmadmin\n[dmadmin@content_server_01 ~]$\n[dmadmin@content_server_01 ~]$\n[dmadmin@content_server_01 ~]$ pwlockbox=\"L0ckb0xP4ssphr4se\"\n[dmadmin@content_server_01 ~]$ pwaek=\"A3kP4ssphr4se\"\n[dmadmin@content_server_01 ~]$ dm_crypto_boot -lockbox lockbox.lb -lockboxpassphrase $pwlockbox -passphrase $pwaek -all\n\nPlease wait. This will take a few seconds ...\n\nPlease wait, this will take a few seconds..\nSetting up the (single) passphrase for all keys in the shared memory region..\nOperation succeeded\n[dmadmin@content_server_01 ~]$ \n[dmadmin@content_server_01 ~]$ \n[dmadmin@content_server_01 ~]$ dm_crypto_manage_lockbox -lockbox lockbox.lb -lockboxpassphrase $pwlockbox -resetfingerprint\nLockbox lockbox.lb\nLockbox Path $DOCUMENTUM\/dba\/secure\/lockbox.lb\nLockbox open failed The Lockbox file is newer than the active Lockbox library. Retry with a newer version of the Lockbox library.\n** Operation failed **\n[dmadmin@content_server_01 ~]$<\/pre>\n<\/p>\n
As you can see, after removing the D2 Lockbox libraries from the environment, the lockbox can’t be stored in the Shared Memory anymore… So based on this information, it is clear that the Content Server Lockbox libraries (stored under $DM_HOME\/bin) are different than the D2 Lockbox libraries (in our case stored under $DOCUMENTUM\/d2-lib\/lockbox)… It’s “fun” that two patches that have been released exactly at the same time are using different versions of the Lockbox libraries… The annoying point here is that the CS Lockbox isn’t readable anymore using the CS Lockbox libraries and that can be checked using the following command:<\/p>\n
[dmadmin@content_server_01 ~]$ dm_crypto_create -lockbox lockbox.lb -lockboxpassphrase $pwlockbox -keyname CSaek -passphrase $pwaek -algorithm AES_256_CBC -check\n\nThe Lockbox file is newer than the active Lockbox library. Retry with a newer version of the Lockbox library.\n** No AEK store exists in lockbox lockbox.lb and got status code returned as '1057226514'.\n[dmadmin@content_server_01 ~]$ \n[dmadmin@content_server_01 ~]$<\/pre>\n<\/p>\n
The problem I can see here is that when installing D2, the CS Lockbox has apparently somehow been corrupted by the D2 Lockbox libraries. The fact is that when a docbase is trying to start, the start script (dm_start_GR_DOCBASE) is setting the environment using the script $DM_HOME\/bin\/dm_set_server_env.sh which overwrites our environment variables because this file is using the CS Lockbox libraries. That’s the reason why the docbase wasn’t able to start earlier: the docbase is trying to start using the CS libraries (older) while the lockbox has been tempered with the D2 libraries (newer).<\/p>\n
<\/p>\n
There are several ways to quickly workaround this specific issue and I will try to describe them below.<\/p>\n
<\/p>\n
First solution:<\/strong> Create a copy of the dm_crypto_create and dm_crypto_create.bin files to force it to use the environment variable defined in the .bash_profile and not reload them based on the dm_set_server_env.sh (removing the 3 lines related to the LD_LIBRARY_PATH):<\/p>\n
[dmadmin@content_server_01 ~]$ cd $DM_HOME\/bin\n[dmadmin@content_server_01 bin]$ cp dm_crypto_create my_dm_crypto_create\n[dmadmin@content_server_01 bin]$ cp dm_crypto_create.bin my_dm_crypto_create.bin\n[dmadmin@content_server_01 bin]$ vi my_dm_crypto_create\n[dmadmin@content_server_01 bin]$ diff dm_crypto_create my_dm_crypto_create\n21,23d20\n< else\n< LD_LIBRARY_PATH=${location}\n< export LD_LIBRARY_PATH<\/pre>\n<\/p>\n
Once this is done, you can compare the result of the check command:<\/p>\n
[dmadmin@content_server_01 bin]$ .\/dm_crypto_create -lockbox lockbox.lb -lockboxpassphrase $pwlockbox -keyname CSaek -passphrase $pwaek -algorithm AES_256_CBC -check\n\nThe Lockbox file is newer than the active Lockbox library. Retry with a newer version of the Lockbox library.\n** No AEK store exists in lockbox lockbox.lb and got status code returned as '1057226514'.\n[dmadmin@content_server_01 bin]$\n[dmadmin@content_server_01 bin]$\n[dmadmin@content_server_01 bin]$ .\/my_dm_crypto_create -lockbox lockbox.lb -lockboxpassphrase $pwlockbox -keyname CSaek -passphrase $pwaek -algorithm AES_256_CBC -check\n\nKey - CSaek uses algorithm AES_256_CBC.\n\n** An AEK store with the given passphrase exists in lockbox lockbox.lb and got status code returned as '0'.\n[dmadmin@content_server_01 bin]$\n[dmadmin@content_server_01 bin]$<\/pre>\n<\/p>\n
=> As you can see, this is now working with the updated script but that’s not really a sexy solution…<\/p>\n
<\/p>\n
<\/p>\n
Second solution:<\/strong> Update the file dm_set_server_env.sh to force it to use the D2 Lockbox libraries instead of the CS ones. You can check the Official Documentation about how to setup environment variables for D2 and then just put that at the end of this file. In our case, this was something like:<\/p>\n
[dmadmin@content_server_01 bin]$ tail -6 $DM_HOME\/bin\/dm_set_server_env.sh\nexport LD_LIBRARY_PATH=$DOCUMENTUM\/d2-lib\/lockbox\/lib\/native\/linux_gcc34_x64:$LD_LIBRARY_PATH\nexport PATH=$DOCUMENTUM\/d2-lib\/lockbox\/lib\/native\/linux_gcc34_x64:$PATH\nexport CLASSPATH=$DOCUMENTUM\/d2-lib\/D2.jar:$DOCUMENTUM\/d2-lib\/LB.jar:$DOCUMENTUM\/d2-lib\/LBJNI.jar:$CLASSPATH\n# The environment that exists after this script executes is output to\n# the dm_set_server_env.log file in $DOCUMENTUM_SHARED\/logs\nenv >> $DOCUMENTUM_SHARED\/logs\/dm_set_server_env.log<\/pre>\n<\/p>\n
This solution is a little bit better but as soon as you will upgrade\/migrate your Content Server, this file might be overwritten by the Patch and therefore you will face this issue again… \ud83d\ude41<\/p>\n
<\/p>\n
The solution N\u00b02 is what EMC recommended us to do so that’s what we did in the first place and we were able to start the docbase, aso… But one week later, we tried to install a new docbase and then the Server Configuration Program wasn’t able to read the lockbox anymore and therefore we weren’t able to create any new docbase! This is an extract from the file Server Configuration Program log file:<\/p>\n
13:58:10,266 INFO [AWT-EventQueue-0] com.documentum.install.server.ui.panels.DiWPServerUseExistingLockBox - UserSelection: \"lockbox.lb\"\n13:58:10,266 INFO [AWT-EventQueue-0] com.documentum.install.server.ui.panels.DiWPServerUseExistingLockBox - UserSelection: \"AES_256_CBC\"\n13:58:10,266 INFO [AWT-EventQueue-0] com.documentum.install.server.ui.panels.DiWPServerUseExistingLockBox - UserInput: \"CSaek\"\n13:58:10,266 INFO [AWT-EventQueue-0] com.documentum.install.server.ui.panels.DiWPServerUseExistingLockBox - UserInputPassword: \"**********\"\n13:58:10,266 INFO [AWT-EventQueue-0] com.documentum.install.server.ui.panels.DiWPServerUseExistingLockBox - UserSelection: \"true\"\n13:58:10,266 INFO [AWT-EventQueue-0] com.documentum.install.server.ui.panels.DiWPServerUseExistingLockBox - UserInput: \"lockbox.lb\"\n13:58:10,266 INFO [AWT-EventQueue-0] com.documentum.install.server.ui.panels.DiWPServerUseExistingLockBox - UserInputPassword: \"**********\"\n13:58:10,507 ERROR [Thread-97] com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase - Check AEK key passphrase failed<\/pre>\n<\/p>\n
Therefore the solutions 1 and 2 are actually not good because we are able to start the docbase but not to install a new one… So we had to find another, better solution and it all started with this question: which component(s) is\/are actually using the D2 Lockbox on the Content Server? Of course the answer to this question is: only the Java Method Server.<\/p>\n
<\/p>\n
Based on this information, we therefore decided to restrict the access to the D2 Lockbox libraries only to the JMS. This has been done by removing the environment variables mentioned above from the bash_profile and\/or from the dm_set_server_env.sh and then by updating the JMS startup script with the same:<\/p>\n
[dmadmin@content_server_01 ~]$ head -6 $DOCUMENTUM_SHARED\/jboss7.1.1\/server\/startMethodServer.sh\n#!\/bin\/sh\n\n#for D2.lockbox\nexport LD_LIBRARY_PATH=$DOCUMENTUM\/d2-lib\/lockbox\/lib\/native\/linux_gcc34_x64:$LD_LIBRARY_PATH\nexport PATH=$DOCUMENTUM\/d2-lib\/lockbox\/lib\/native\/linux_gcc34_x64:$PATH\nexport CLASSPATH=$DOCUMENTUM\/d2-lib\/D2.jar:$DOCUMENTUM\/d2-lib\/LB.jar:$DOCUMENTUM\/d2-lib\/LBJNI.jar:$CLASSPATH<\/pre>\n<\/p>\n
After that, we “simply” regenerated the Content Server Lockbox with the CS libraries (basically you need to remove completely the current encryption inside the docbase and force the CS to recreate it from scratch… Arnaud Berbier will most probably write a blog on this subject in the next few days\/weeks). Then we restarted the whole Content Server and everything was working properly with the right Lockbox libraries and we were able to create new docbases.<\/p>\n","protected":false},"excerpt":{"rendered":"
A few weeks ago at a customer, I was installing a completely new sandbox environment for one of our Application Teams. On this environment, we used a new version stack with the most recent patch set (at that time): CS 7.2 P16, D2 4.6 P05, aso… A new patch level means a lot of “fun” […]<\/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":[915,443,477,991,129,916],"type_dbi":[],"class_list":["post-9355","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management","tag-crypto","tag-d2","tag-d2-lockbox","tag-dm_crypto_boot","tag-documentum","tag-lockbox"],"acf":[],"yoast_head":"\n
Documentum story - Lockbox file is newer than the active Lockbox library - 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-story-lockbox-file-is-newer-than-the-active-lockbox-library\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum story - Lockbox file is newer than the active Lockbox library\" \/>\n<meta property=\"og:description\" content=\"A few weeks ago at a customer, I was installing a completely new sandbox environment for one of our Application Teams. On this environment, we used a new version stack with the most recent patch set (at that time): CS 7.2 P16, D2 4.6 P05, aso… A new patch level means a lot of “fun” […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-11-25T07:00:17+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=\"10 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-story-lockbox-file-is-newer-than-the-active-lockbox-library\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\\\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum story – Lockbox file is newer than the active Lockbox library\",\"datePublished\":\"2016-11-25T07:00:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\\\/\"},\"wordCount\":1139,\"commentCount\":0,\"keywords\":[\"Crypto\",\"D2\",\"D2 lockbox\",\"dm_crypto_boot\",\"Documentum\",\"Lockbox\"],\"articleSection\":[\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\\\/\",\"name\":\"Documentum story - Lockbox file is newer than the active Lockbox library - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2016-11-25T07:00:17+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum story – Lockbox file is newer than the active Lockbox library\"}]},{\"@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 story - Lockbox file is newer than the active Lockbox library - 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-story-lockbox-file-is-newer-than-the-active-lockbox-library\/","og_locale":"en_US","og_type":"article","og_title":"Documentum story - Lockbox file is newer than the active Lockbox library","og_description":"A few weeks ago at a customer, I was installing a completely new sandbox environment for one of our Application Teams. On this environment, we used a new version stack with the most recent patch set (at that time): CS 7.2 P16, D2 4.6 P05, aso… A new patch level means a lot of “fun” […]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/","og_site_name":"dbi Blog","article_published_time":"2016-11-25T07:00:17+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum story – Lockbox file is newer than the active Lockbox library","datePublished":"2016-11-25T07:00:17+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/"},"wordCount":1139,"commentCount":0,"keywords":["Crypto","D2","D2 lockbox","dm_crypto_boot","Documentum","Lockbox"],"articleSection":["Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/","name":"Documentum story - Lockbox file is newer than the active Lockbox library - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2016-11-25T07:00:17+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-lockbox-file-is-newer-than-the-active-lockbox-library\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum story – Lockbox file is newer than the active Lockbox library"}]},{"@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\/9355","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=9355"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9355\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=9355"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=9355"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=9355"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=9355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}