DA

Documentum – DA fail to load if accessed after D2 because of ESAPI

In some specific cases, you might have faced an issue where Documentum Administrator is loading properly but then suddenly it’s not working anymore and all you did in between was accessing D2. I don’t remember seeing that before DA 16.x(…)

Documentum – dm_DMFilescan fails with invalid method_verb?

Recently in a project, one of the Documentum environments we were working on started showing failure on the execution of the dm_DMFilescan job and only this one. After a couple minutes of investigation, I quickly found the root cause of(…)

Documentum – Encryption/Decryption of WebTop 6.8 passwords ‘REJECTED’ with recent JDK

Recently, we had a project to modernize a little bit a pretty old Documentum installation. As part of this project, there were a refresh of the Application Server hosting a WebTop 6.8. In this blog, I will be talking about(…)

Documentum – DA 7.3 showing java.lang.NullPointerException on every actions

Last year, we started to upgrade some Documentum Administrator from 7.2 to 7.3 and directly after, we started to see some NullPointerException on the log files. We are using DA 7.3 on some recent WebLogic Servers versions (12.1.3, 12.2.1.2). We(…)

Documentum – Using DA with Self-Signed SSL Certificate

A few years ago, I was working on a Documentum project and one of the tasks was to setup all components in SSL. I already published a lot of blogs on this subject but there is one I wanted to(…)

DA 7.2 UCF Transfer failing with SSL

This is a blog following the one I already wrote ealier:  https://www.dbi-services.com/blog/documentum-administrator-ucf-troubleshooting/ The first one was for “how to find the error” and not how to resolve it. In this blog I will talk about an(…)

Documentum Administrator UCF Troubleshooting

Maybe you had some issues with UCF in DA as me. I had this for no reason since few days at a customer. The problem was that we use SSL with DA and the Unified Content Facilities (UCF) wasn’t happy(…)

Upgrading to 7.2 created a new ACS. How to remove it and test it?

I had this strange behavior that once upgraded from 6.7 to 7.2 a new ACS was created. I think it’s because the current ACS name didn’t fit the new ACS name pattern. Well it’s not a big issue to have(…)