Morgan Patou has over 15 years of experience building and deploying Java/J2EE applications. He specializes in Enterprise Content Management (ECM) solutions such as Alfresco and Documentum, covering open-source (Apache, OpenLDAP, Kerberos) and proprietary (WebLogic) technologies, with deep expertise in business requirement analysis, ECM architecture, and high-availability infrastructure for mission-critical environments. He oversees knowledge management and technology direction for the ECM practice. He holds Alfresco Content Services Certified Administrator (ACSCA) and Certified Engineer (ACSCE) credentials, plus an Engineering degree in Computer Science from ENSISA Mulhouse. His industry experience covers the public sector, IT, financial services/banking, and pharmaceutical industries.
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…
At a customer having a lot of Documentum environments, I recently faced an interesting issue while upgrading an RCS/CFS to 20.2. The same could potentially reproduce during a standard installation of a RCS/CFS, under certain circumstances (in case there are still some things left in the repository after a removal of the said RCS/CFS and then reinstallation for example, you…
There could be several reasons why a Linux process gets killed. Of course, it could be someone using the kill command but, in this blog, I will talk about the Kernel Panic triggered by the Operating System in case it runs out of RAM. I had a case recently, at a customer, where a nginx process going wild caused such…
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…
Security is and will always be a very important aspect of IT. Enterprise Content Management (or Document Management Systems or Content Services Platform or whateveryoucallit) is obviously not an exception to that. One of our main goals as a consultant is to add improvements to our customers’ installations for stability, security, and ease of management. However, it happens that not…
Documentum is an inexhaustible source of issues and that’s great because I can continuously write blogs on it, and I always have materials for that. In this blog, I will talk about the ACS not being able to start on the MethodServer because of an ActiveMQ error. As you might know, WildFly has been coming with an integrated ActiveMQ for…
Nowadays, with DevOps and containers approaches, you will often see components or software that try to go on a diet, to reduce the size needed to deploy them and therefore the images/containers associated to it. I was recently asked to do something similar on a very specific feature that the Documentum DFC jar files provide: extract and minimize the jar…
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…
A few weeks ago, an issue was identified at a customer which would cause the value of “dm_server_config.r_server_version” to be reset to the GA version number (16.4 P00) instead of the currently deployed patch (which is 16.4 P26) and that would happen randomly on some of the Content Servers but not all. The different Content Servers are all deployed on…