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.
Let’s start
- 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.
Usual Error:
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:
Thank you for the guide. I successfully got it set up to connect to Documentum 20.2 using DCTM Client 20.0.
I do however quite unstable, often crashes on login og when running command. I also get an error when using fetch as example.
Any ideas on how to resolve it so all features work correctly?
LikeLike
This error means that you’re running dqman with a lower Java version than the one used to compile the DFC (probably you’re running dqman with Java 8), while DFC is compiled with a newer version. Use a newer JDK to run dqman and it should be ok (there are unofficial openjdk 11 x86 builds to use, as I think it is the supported version on 20.x)
LikeLike
Have you tried dqMan with Documentum 20.2 repositories?
LikeLike
Yes, It works
LikeLike
Dear Alvaro, thank you for the guide!
Just a few comments, because from the beginning I got an error with a red cross.
In my case, it wasn’t necessary to install DFC with 32 JAVA. I regularly installed DFC with JDK 11.0.5.
Also, my dmcl.dll is ~256kb and I had to put 32bit java on the machine.
java.ini in dqMan folder resolved problem to me
This is my java.ini:
java_library_path=”C:\dev_tools\Java\jre1.8.0_151\bin\client\jvm.dll”
JAVA_OPTIONS=” -Xcheck:jni -XX:+RestoreMXCSROnJNICalls -Xmx256m”
java_classpath = “C:\Program Files\Documentum\Shared\dfc.jar;C:\Documentum\config”
LikeLike
Java 32 has nothing to do with DFC, probably I could have redacted that part in a better way 😀 dqMan cannot run with Java x64. You can use whatever Java you want with DFC but dqMan can only be run with a 32-bit Java (unless fme decides to recompile it with x64 support)
LikeLike
I am getting Áccess Denied pop up after executing the query.
LikeLike
Thank you so much for this blog . It was very helpful.
I was able to get my DQMan 6 version work against Documentum CS 16.4.as a standalone package.
Download the DQman 6 and Install the license.
Then …
1. I just needed to copy the dmcl.dll to the Dqman Home folder C:\dqMan
2. I have installed DFC 16.4 .
3. Then copied the “Java 1.8 32 bit ” that come bundled with DFC16.4 from C:\Documentum to C:\dqMan
I also copied the DFC.properties file into C:\dqMan\config
4. I created a java.ini file inside C:\dqMan
This is what it is inside my java.ini. ( all jars are taken from 1.6 DFc installation shared folder)
java_library_path=”C:\dqMan\java\1.8.0_152\jre\bin\client\jvm.dll”
JAVA_OPTIONS=” -Xcheck:jni -XX:+RestoreMXCSROnJNICalls -Xmx256m”
java_classpath=”C:\dqMan\config\aspectjrt.jar;C:\dqMan\config\commons-codec-1.10.jar;C:\dqMan\config\commons-lang-2.6.jar;C:\dqMan\config\dctm.jar;C:\dqMan\config\dfc.jar;C:\dqMan\config\log4j.jar;C:\dqMan\config”
Nothing else is need DQman will now work seamlessly without any issues.
LikeLike