As it seems that people are still struggling with configuring fme group‘s dqMan after dmcl support was removed in Documentum 16.4, maybe this will be helpul. I’m doing this with Documentum 20.2, but this works for every other version.
- Install Java:
- You will need x86 Java, x64 won’t work
- If you’re using any Java newer than 1.8.201, you need to enable the anon cipher for the secure mode to work
- Oracle JRE: jre\lib\security\java.security file, you need to remove anon from jdk.tls.disabledAlgorithms entry
- OpenJDK: opendk\conf\security\java.security, you need to remove anon from jdk.tls.disabledAlgorithms entry
- Install DFC
- You need to install DFC using the x86 Java, otherwise dqman won’t work. You can check which Java is DFC using in Windows registry (HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\java).
- Install dqman
- Copy dmcl.dll from a previous Documentum version to dqman’s folder. Be aware that there’s actually two different dcml.dll version (I think one is 32bit and another 64bit). As far as I know, the one that works is the smaller one (~150KB)
That’s it 🙂
If you come from previous versions of dqman, remove any dmcl40.dll / dmcl.ini from dqman’s folder or the PATH/CLASSPATH entries.
This means you are running dqman with x64 Java (which does not work)
If you have multiple Java’s installed, you can force dqman to use a specific one by creating a java.ini file in dqman’s folder including the following:
java_library_path=”c:\java18\bin\client\jvm.dll” -> path to jre’s jvm.dll
#java_classpath = “dfc\lib\dctm.jar;dfc\config” -> this entry is optional (commented with #). If defined, it has to include the folder containing dctm.jar file and a folder with dfc.properties file
If you did everything correctly you should see the following on the about window: