I recently faced another interesting issue (c.f. this one) with Documentum xPlore where the Dsearch would refuse to start because of a stuck online rebuild. It happened on a Kubernetes environment using custom images we built (for security and scalability). The K8s Nodes were split across two DataCenters for DR reasons. However, one of the DataCenter had an important issue…
If you are here, I assume you are looking for some ways to enable traces on Documentum. There are already a few blog posts here and there showing some information but Documentum being what it is, i.e., a quite complex machinery, there are just way too many places/configurations that you can have traces/debug information on. Therefore, I also wanted to…
At a customer using Documentum inside Kubernetes, unusually frequent restarts of xPlore containers were noted a couple weeks after the introduction of CPS Only pods on the different Production environments. The customer had a very simple Standalone xPlore setup, with Dsearch+IndexAgent, but without CPS Only Nodes. It was noticed at this customer that the indexing and search load was reaching…
During an upgrade project of xPlore from 16.4 to 20.2 at a customer, I faced a quite interesting issue with the xPlore CPS (Content Processing Services) that couldn’t start properly and were, therefore, shown as “UNREACHABLE“. The funny thing is that the Java/WildFly processes of the PrimaryDsearch and CPS were properly running, and it was possible to login to the…
A couple year ago at a new customer, I was asked to install a new xPlore IndexAgent on an existing Documentum 16.4 environment. Unfortunately, that installation didn’t succeed, and I ended up with the following install logs: As you probably know, xPlore 16.4 is now quite old and it was still a version that came out-of-the-box with the Oracle JDK…
A few weeks ago, I faced an issue at a customer where xPlore PrimaryDsearch would stop responding to curl/wget/browser requests from time to time. The impacted environments were containers (pods) hosted on Kubernetes. At this customer, we were in progress of migrating their standalone xPlore installations (also on pods) to Multi-Node, meaning that before, there was only 1 pod containing…
Documentum is usually working pretty well with xPlore when it’s about managing its queue on well configured environments and/or with “simple” repositories. Basically, as long as you do not only have very big/complex documents (e.g.: 500Mb excel files with hundreds of thousands of rows) or a lot of customizations that aren’t very optimized or intensive components like a full Life…
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…
Recently at a customer, I faced a new issue I didn’t see before on the xPlore Dsearch component. Basically, the processes appeared to be starting and the “dsearchadmin.war” was deployed properly but it always failed for the “dsearch.war” upon startup of WildFly. However, it was possible to “deploy” it once WildFly was running… This issue wasn’t too complex to debug…
Everybody familiar with Documentum knows that just starting the JBoss/WildFly hosting an IndexAgent isn’t really enough to have the indexing working: the IndexAgent must be started from the UI (or via DA or via the job or via iapi or automatically via the Repository startup or …). Starting the IA in “normal mode” is usually something that takes a few…
In relation to my previous blog about custom facets not showing up after full reindex, a customer was doing a migration that just completed. After the full reindex, there were no facets because of what I explained in the blog. Knowing that the online rebuild is normally faster than a full reindex, I helped to start this operation but after…
Beginning of the year, while performing a migration from a Documentum 7.3 environment on VM to Documentum 16.4 on Kubernetes, a customer had an issue where their custom facets weren’t showing up on D2 after a full reindex. At the end of the migration, since xPlore has been upgraded as well (from xPlore 1.5 to 16.4, from VM to K8s),…
