dqMan configuration with Documentum 21.2 and OpenJDK 11 or newer

A while ago you probably saw a statement from fme group saying that dqMan was not compatible with newer Documentum versions:

fmedqman

So, considering that the only “issue” here is using an openJDK x86 / 32bit instead of the x64 (which is the only official one being distributed), these are the steps to get dqMan working with Documentum 21.2 and openJDK 11.

Let’s start

  1. Install Java:
    • You need to download an unofficial openJDK x86/32bit build, you can use for example the ones provided by AdoptOpenJDK here. I suggest you to unzip this on dqMan’s folder
    • Remember that for the native connection to work, you need to remove anon from jdk.tls.disabledAlgorithms entry on the java.security file.
  2. Install DFC
    • I don’t think you need much help for this 🙂 You can also just copy dctm.jar and dfc folder from CS.
  3. Install dqman
  4. 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)
  5. Create a java.ini file on dqMan’s main folder with the following contents:

java_library_path=”<PATH_TO_DQMAN>\jdk-11.0.11+9-jre\bin\client\jvm.dll”
java_classpath=<PATH_TO_DFC_FOLDER>\config;<PATH_TO_DFC_FOLDER>\dctm.jar
java_options = ” -Djava.net.preferIPv4Stack=true -Djava.locale.provider=COMPAT,SPI”
java_tool_options = ” -Djava.locale.provider=COMPAT,SPI”

If you did everything correctly you should see the following on the about window:

dqman212

And this is all you have to do to keep working with dqMan and Documentum 20.x/21.x.

dqMan configuration with Documentum 16.4 or newer

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

  1. 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
  2. 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).
  3. Install dqman
  4. 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:

error1

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:

correctconfig