{"id":18840,"date":"2022-09-05T21:05:00","date_gmt":"2022-09-05T19:05:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=18840"},"modified":"2022-09-05T17:04:36","modified_gmt":"2022-09-05T15:04:36","slug":"documentum-xplore-20-2-search-not-working-after-repository-restart","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/","title":{"rendered":"Documentum &#8211; xPlore 20.2 search not working after repository restart"},"content":{"rendered":"\n<p>A little bit more than two years ago, one of our customers started to use Documentum 20.2 (and therefore xPlore 20.2) in custom containers, with all components in SSL\/Secure. At first sight, everything seemed to work. However, in case the Repository restarted (for any reasons), then the searches stopped working completely. Basically, there was no problem if the Docbroker and Repository started first and the xPlore afterwards, but in case it was the other way around, then the searches didn&#8217;t work at all.<\/p>\n\n\n\n<p>Reproducing the issue was rather simple:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; highlight: [1,11,12,14,28,33,66,70,74,75]; title: ; notranslate\" title=\"\">\n&#x5B;dmadmin@cs-0 ~]$ ### At the moment, xPlore started after the Repository\n&#x5B;dmadmin@cs-0 ~]$ alias | grep -E &quot;start|stop|ts&quot;\nalias start=&#039;$DOCUMENTUM\/dba\/dm_start_REPO1&#039;\nalias stop=&#039;$DOCUMENTUM\/dba\/dm_shutdown_REPO1&#039;\nalias ts=&#039;iapi REPO1 -Udmadmin -Pxxx -r\/tmp\/test_search.api&#039;\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ cat \/tmp\/test_search.api\n?,c,select count(*) from dm_document search document contains &#039;test&#039;\nexit\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ curl -k HTTPS:\/\/ft-service.dctm-ns1.svc.cluster.local:9302\/dsearch\/; echo\nThe xPlore instance PrimaryDsearch &#x5B;version=20.2.0000.0015] normal\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ ts\n\nOpenText Documentum iapi - Interactive API interface\nCopyright (c) 2020. OpenText Corporation\nAll rights reserved.\nClient Library Release 20.2.0000.0082\n\nConnecting to Server using docbase REPO1\n&#x5B;DM_SESSION_I_SESSION_START]info: &quot;Session 010f457a80050108 started for user dmadmin.&quot;\n\nConnected to OpenText Documentum Server running Release 20.2.0000.0110 Linux64.Oracle\nSession id is s0\nAPI&amp;gt; count(*)\n----------------------\n                   270\n(1 row affected)\n\nAPI&amp;gt; Bye\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ ### Search is working, restarting the Repository\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ stop\nStopping Documentum server for repository: &#x5B;REPO1]\n\nOpenText Documentum iapi - Interactive API interface\nCopyright (c) 2020. OpenText Corporation\nAll rights reserved.\nClient Library Release 20.2.0000.0082\n\nConnecting to Server using docbase REPO1.REPO1\n&#x5B;DM_SESSION_I_SESSION_START]info: &quot;Session 010f457a8005010a started for user dmadmin.&quot;\n\nConnected to OpenText Documentum Server running Release 20.2.0000.0110 Linux64.Oracle\nSession id is s0\nAPI&amp;gt; shutdown,c,T,T\n...\nOK\nAPI&amp;gt; exit\nBye\nWaiting for 90 seconds for server pid, 2152, to disappear.\n\nMon Aug 3 17:01:49 UTC 2020: Waiting for shutdown of repository: &#x5B;REPO1]\nMon Aug 3 17:01:49 UTC 2020: checking for pid: 2152\n\nrepository: &#x5B;REPO1] has been shutdown\nchecking that all children (2155 2205 2206 2218 2219 2221 2247 2264 2642) have shutdown\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ start\nstarting Documentum server for repository: &#x5B;REPO1]\nwith server log: &#x5B;$DOCUMENTUM\/dba\/log\/REPO1.log]\nserver pid: 2854\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ ts\n...\nConnected to OpenText Documentum Server running Release 20.2.0000.0110 Linux64.Oracle\nSession id is s0\nAPI&amp;gt; &#x5B;DM_FULLTEXT_E_SEARCH_NEW_FAIL]error: &quot;dmFTSearchNew failed with error: ESS_DMSearch::ExecuteSearch: Communication Exception Failed to perform URL: HTTPS:\/\/ft-service.dctm-ns1.svc.cluster.local:9302\/dsearch\/IndexServerServlet?ftRequestHandler=GET-CONFIG, errorcode: 35: SSL connect error,General Exception, error code: -2&quot;\n\nAPI&amp;gt; Bye\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ curl -k HTTPS:\/\/ft-service.dctm-ns1.svc.cluster.local:9302\/dsearch\/; echo\nThe xPlore instance PrimaryDsearch &#x5B;version=20.2.0000.0015] normal\n&#x5B;dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n<p>As you can see above, while the xPlore processes stayed up&amp;running, the issue could be reproduced by just restarting the Repository. This environment was using the supported Oracle OpenJDK 11 with the default &#8220;security.providers&#8221; on both CS (Content Server = Documentum Server) and FT (Full Text = Documentum xPlore). When the Repository started, it would, by default, try to contact the IndexAgent (it can be disabled with &#8220;<em>start_index_agents=F<\/em>&#8221; in server.ini) and it seemed that this was what messed things up in the SSL communications between the CS and the FT.<\/p>\n\n\n\n<p>I worked with OpenText on the <em>SR#4750851<\/em> where we generated a lot of traces\/debugs logs (java SSL debug, tcpdump, Documentum rpc\/fulltext traces, aso\u2026) for the SSL layers but in the end, our suspicions were redirected to the OS (Operating System) libraries. We tried on both RHEL 7.7 and 7.5 with respectively OpenSSL 1.1.1d and 1.0.2k-fips but the same issue was seen. Here are the libraries in play when there is a search on the CS:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n&#x5B;dmadmin@cs-0 ~]$ ldd $DM_HOME\/bin\/libDsearchQueryPlugin.so\n        linux-vdso.so.1 =&amp;gt;  (0x00007ffd22aff000)\n        libcurl.so.4 =&amp;gt; \/lib64\/libcurl.so.4 (0x00007f1ad7b9f000)\n        librt.so.1 =&amp;gt; \/lib64\/librt.so.1 (0x00007f1ad7997000)\n        libxerces-c.so.28 =&amp;gt; $DM_HOME\/bin\/libxerces-c.so.28 (0x00007f1ad73c1000)\n        libssl.so.1.1 =&amp;gt; $DM_HOME\/bin\/libssl.so.1.1 (0x00007f1ad7130000)\n        libcrypto.so.1.1 =&amp;gt; $DM_HOME\/bin\/libcrypto.so.1.1 (0x00007f1ad6c6f000)\n        libstdc++.so.6 =&amp;gt; \/lib64\/libstdc++.so.6 (0x00007f1ad6968000)\n        libm.so.6 =&amp;gt; \/lib64\/libm.so.6 (0x00007f1ad6666000)\n        libgcc_s.so.1 =&amp;gt; \/lib64\/libgcc_s.so.1 (0x00007f1ad6450000)\n        libc.so.6 =&amp;gt; \/lib64\/libc.so.6 (0x00007f1ad6082000)\n        libidn.so.11 =&amp;gt; \/lib64\/libidn.so.11 (0x00007f1ad5e4f000)\n        libssh2.so.1 =&amp;gt; \/lib64\/libssh2.so.1 (0x00007f1ad5c22000)\n        libssl3.so =&amp;gt; \/lib64\/libssl3.so (0x00007f1ad59c9000)\n        libsmime3.so =&amp;gt; \/lib64\/libsmime3.so (0x00007f1ad57a1000)\n        libnss3.so =&amp;gt; \/lib64\/libnss3.so (0x00007f1ad5472000)\n        libnssutil3.so =&amp;gt; \/lib64\/libnssutil3.so (0x00007f1ad5242000)\n        libplds4.so =&amp;gt; \/lib64\/libplds4.so (0x00007f1ad503e000)\n        libplc4.so =&amp;gt; \/lib64\/libplc4.so (0x00007f1ad4e39000)\n        libnspr4.so =&amp;gt; \/lib64\/libnspr4.so (0x00007f1ad4bfb000)\n        libpthread.so.0 =&amp;gt; \/lib64\/libpthread.so.0 (0x00007f1ad49df000)\n        libdl.so.2 =&amp;gt; \/lib64\/libdl.so.2 (0x00007f1ad47db000)\n        libgssapi_krb5.so.2 =&amp;gt; \/lib64\/libgssapi_krb5.so.2 (0x00007f1ad458e000)\n        libkrb5.so.3 =&amp;gt; \/lib64\/libkrb5.so.3 (0x00007f1ad42a5000)\n        libk5crypto.so.3 =&amp;gt; \/lib64\/libk5crypto.so.3 (0x00007f1ad4072000)\n        libcom_err.so.2 =&amp;gt; \/lib64\/libcom_err.so.2 (0x00007f1ad3e6e000)\n        liblber-2.4.so.2 =&amp;gt; $DM_HOME\/bin\/liblber-2.4.so.2 (0x00007f1ad3c60000)\n        libldap-2.4.so.2 =&amp;gt; $DM_HOME\/bin\/libldap-2.4.so.2 (0x00007f1ad3a16000)\n        libz.so.1 =&amp;gt; \/lib64\/libz.so.1 (0x00007f1ad3800000)\n        \/lib64\/ld-linux-x86-64.so.2 (0x00007f1ad804d000)\n        libssl.so.10 =&amp;gt; \/lib64\/libssl.so.10 (0x00007f1ad358e000)\n        libcrypto.so.10 =&amp;gt; \/lib64\/libcrypto.so.10 (0x00007f1ad312b000)\n        libkrb5support.so.0 =&amp;gt; \/lib64\/libkrb5support.so.0 (0x00007f1ad2f1b000)\n        libkeyutils.so.1 =&amp;gt; \/lib64\/libkeyutils.so.1 (0x00007f1ad2d17000)\n        libresolv.so.2 =&amp;gt; \/lib64\/libresolv.so.2 (0x00007f1ad2afd000)\n        libsasl2.so.2 =&amp;gt; \/lib64\/libsasl2.so.2 (0x00007f1ad28e0000)\n        libselinux.so.1 =&amp;gt; \/lib64\/libselinux.so.1 (0x00007f1ad26b9000)\n        libcrypt.so.1 =&amp;gt; \/lib64\/libcrypt.so.1 (0x00007f1ad2482000)\n        libpcre.so.1 =&amp;gt; \/lib64\/libpcre.so.1 (0x00007f1ad2220000)\n        libfreebl3.so =&amp;gt; \/lib64\/libfreebl3.so (0x00007f1ad201d000)\n&#x5B;dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n<p>When we compared the list above to the one coming from containers provided by OpenText that apparently didn&#8217;t have this issue, we saw that there were a few differences, but the two most suspicious candidate were:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n        libnss3.so =&amp;gt; \/lib64\/libnss3.so (0x00007f1ad5472000)\n        libnssutil3.so =&amp;gt; \/lib64\/libnssutil3.so (0x00007f1ad5242000)\n<\/pre><\/div>\n\n\n<p>NSS stands for <a href=\"https:\/\/firefox-source-docs.mozilla.org\/security\/nss\/index.html\" target=\"_blank\" rel=\"noreferrer noopener\">Network Security Services<\/a> and it&#8217;s a set of libraries for cross-platform development of client\/servers with the security aspects taken into account. This appeared to be coming from the base OS image that the customer needed to use (big company, having its own enterprise-wise images). There is a parameter for the NSS that can sometimes help to avoid issues, for more details, look at the definition of &#8220;NSS_STRICT_NOFORK&#8221; <a href=\"https:\/\/firefox-source-docs.mozilla.org\/security\/nss\/legacy\/reference\/nss_environment_variables\/index.html\" target=\"_blank\" rel=\"noreferrer noopener\">here<\/a>. We tried to apply it and got the following behavior:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; highlight: [5,6,19,25]; title: ; notranslate\" title=\"\">\n&#x5B;dmadmin@cs-0 ~]$ ### Defining the environment variable and checking again\n&#x5B;dmadmin@cs-0 ~]$ echo $NSS_STRICT_NOFORK\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ export NSS_STRICT_NOFORK=DISABLED\n&#x5B;dmadmin@cs-0 ~]$ echo $NSS_STRICT_NOFORK\nDISABLED\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ stop\nStopping Documentum server for repository: &#x5B;REPO1]\n...\nrepository: &#x5B;REPO1] has been shutdown\nchecking that all children (2857 2898 2903 2904 2911 2914 2922 2933 2954) have shutdown\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ start\nstarting Documentum server for repository: &#x5B;REPO1]\nwith server log: &#x5B;$DOCUMENTUM\/dba\/log\/REPO1.log]\nserver pid: 3049\n&#x5B;dmadmin@cs-0 ~]$\n&#x5B;dmadmin@cs-0 ~]$ ts\n...\nConnected to OpenText Documentum Server running Release 20.2.0000.0110 Linux64.Oracle\nSession id is s0\nAPI&amp;gt; count(*)\n----------------------\n                   270\n(1 row affected)\n\nAPI&amp;gt; Bye\n&#x5B;dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n<p>As you can see, by defining this environment variable, the issue doesn&#8217;t reproduce anymore and it&#8217;s now safe to restart the Repository while xPlore is running. Going a little bit deeper, it looks like this issue might be a consequence of the libraries defaulting to NSS on some OS (the ones with the issue). As an example, the <a href=\"https:\/\/packages.debian.org\/source\/buster\/curl\" target=\"_blank\" rel=\"noreferrer noopener\">curl source package of Debian<\/a> seems to list three flavours of curl: libcurl3-gnutls (GnuTLS flavour), libcurl3-nss (NSS flavour) and libcurl4 (OpenSSL flavour). In addition, if you look at the <a href=\"https:\/\/packages.debian.org\/buster\/curl\" target=\"_blank\" rel=\"noreferrer noopener\">curl dependencies<\/a>, it appears to be using the OpenSSL one by default. Therefore, depending on the OS (Debian, RHEL, CentOS, \u2026), it looks like there might be issues (or not). In any cases, adding this environment variable for Documentum should be a safe workaround if you do not want to change your OS or rebuild libraries without NSS! If you have more experience with NSS, feel free to share.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A little bit more than two years ago, one of our customers started to use Documentum 20.2 (and therefore xPlore 20.2) in custom containers, with all components in SSL\/Secure. At first sight, everything seemed to work. However, in case the Repository restarted (for any reasons), then the searches stopped working completely. Basically, there was no [&hellip;]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,525],"tags":[2609,2688,474],"type_dbi":[],"class_list":["post-18840","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-documentum-2","tag-nss","tag-xplore"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.6) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Documentum - xPlore 20.2 search not working after repository restart - 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-xplore-20-2-search-not-working-after-repository-restart\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - xPlore 20.2 search not working after repository restart\" \/>\n<meta property=\"og:description\" content=\"A little bit more than two years ago, one of our customers started to use Documentum 20.2 (and therefore xPlore 20.2) in custom containers, with all components in SSL\/Secure. At first sight, everything seemed to work. However, in case the Repository restarted (for any reasons), then the searches stopped working completely. Basically, there was no [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-09-05T19:05:00+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=\"6 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-xplore-20-2-search-not-working-after-repository-restart\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-20-2-search-not-working-after-repository-restart\\\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum &#8211; xPlore 20.2 search not working after repository restart\",\"datePublished\":\"2022-09-05T19:05:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-20-2-search-not-working-after-repository-restart\\\/\"},\"wordCount\":548,\"commentCount\":0,\"keywords\":[\"Documentum\",\"NSS\",\"xPlore\"],\"articleSection\":[\"Application integration &amp; Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-20-2-search-not-working-after-repository-restart\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-20-2-search-not-working-after-repository-restart\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-20-2-search-not-working-after-repository-restart\\\/\",\"name\":\"Documentum - xPlore 20.2 search not working after repository restart - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2022-09-05T19:05:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-20-2-search-not-working-after-repository-restart\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-20-2-search-not-working-after-repository-restart\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-20-2-search-not-working-after-repository-restart\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum &#8211; xPlore 20.2 search not working after repository restart\"}]},{\"@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 15 years of experience in Digitalization &amp; 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 HTTPD\\\/Tomcat, 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:\\\/\\\/www.dbi-services.com\\\/blog\\\/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 - xPlore 20.2 search not working after repository restart - 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-xplore-20-2-search-not-working-after-repository-restart\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - xPlore 20.2 search not working after repository restart","og_description":"A little bit more than two years ago, one of our customers started to use Documentum 20.2 (and therefore xPlore 20.2) in custom containers, with all components in SSL\/Secure. At first sight, everything seemed to work. However, in case the Repository restarted (for any reasons), then the searches stopped working completely. Basically, there was no [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/","og_site_name":"dbi Blog","article_published_time":"2022-09-05T19:05:00+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum &#8211; xPlore 20.2 search not working after repository restart","datePublished":"2022-09-05T19:05:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/"},"wordCount":548,"commentCount":0,"keywords":["Documentum","NSS","xPlore"],"articleSection":["Application integration &amp; Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/","name":"Documentum - xPlore 20.2 search not working after repository restart - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2022-09-05T19:05:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-20-2-search-not-working-after-repository-restart\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum &#8211; xPlore 20.2 search not working after repository restart"}]},{"@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 15 years of experience in Digitalization &amp; 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 HTTPD\/Tomcat, 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:\/\/www.dbi-services.com\/blog\/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\/18840","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=18840"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18840\/revisions"}],"predecessor-version":[{"id":18841,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18840\/revisions\/18841"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=18840"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=18840"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=18840"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=18840"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}