Documentum

dqMan configuration with Documentum 16.4 or newer

Alvaro de Andres18 Comments

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

18 thoughts on “dqMan configuration with Documentum 16.4 or newer”

  1. 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?

    Like

    Reply

    • 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)

      Like

      Reply

  3. 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”

    Liked by 2 people

    Reply

    • 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)

      Like

      Reply

  5. 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.

    Like

    Reply

    • Thanks for the guide Alvaro…
      Even I followed same steps which you provided am still getting the red cross Error while running Dqman.Kindly provide resolution for the issue.
      Below are the things I followed and used for dqman application.
      1.Uisng Documentum content server 20.2 version and installed dfc with version of 20.2
      2.Install dqman6 and added dmcl.dll files inside dqman folder
      3.Using open jdk11 32 bit version
      4.Added class path in environment variables as below:
      C:\Program Files (x86)\dqMan\Jars\aspectjrt.jar;C:\Program Files (x86)\dqMan\Jars\certjFIPS.jar;C:\Program Files (x86)\dqMan\Jars\commons-codec-1.12.jar;C:\Program Files (x86)\dqMan\Jars\commons-collections4-4.3.jar;C:\Program Files (x86)\dqMan\Jars\commons-compress-1.18.jar;C:\Program Files (x86)\dqMan\Jars\commons-io-1.2.jar;C:\Program Files (x86)\dqMan\Jars\commons-lang-2.4.jar;C:\Program Files (x86)\dqMan\Jars\commons-logging-1.2.jar;C:\Program Files (x86)\dqMan\Jars\commons-math3-3.6.1.jar;C:\Program Files (x86)\dqMan\Jars\dfc.jar;C:\Program Files (x86)\dqMan\Jars\jaxb-api-2.3.0.jar;C:\Program Files (x86)\dqMan\Jars\jaxb-core-2.3.0.1.jar;C:\Program Files (x86)\dqMan\Jars\jaxb-impl-2.3.0.1.jar;C:\Program Files (x86)\dqMan\Jars\jcmFIPS.jar;C:\Program Files (x86)\dqMan\Jars\jsafeFIPS.jar;

      5.Created java.ini file inside dqman and include the below things in dqman:

      java_library_path=”C:\Program Files (x86)\AdoptOpenJDK\jdk-11.0.11.9-hotspot\bin\client\jvm.dll”
      JAVA_OPTIONS=” -Xcheck:jni -XX:+RestoreMXCSROnJNICalls -Xmx256m”
      java_classpath = “C:\Program Files (x86)\dqMan\Jars\commons-codec-1.12.jar;C:\Program Files (x86)\dqMan\Jars\commons-lang-2.4.jar;C:\Program Files (x86)\dqMan\Jars\dfc.jar;C:\Program Files\Documentum\Shared\dctm.jar;C:\Program Files\Documentum\Shared\log4j.jar;C:\Program Files (x86)\dqMan\config”

      6.Added dfc.property file in dqman/config folder

      Like

      Reply

      • I’ve just tested same configuration and works fine for me. Try manually installing DFC because you might be missing some registry entry for DFC, as jdk 11.0.11 works just fine

        Like

  6. Thanks for your reply..
    It would be great if you can help me for the below issue for dqman software..Kindly checl
    I have installed dfc manually and check the version in cmd wiht command ,it shows dfc 20.2 version. Now am getting another issue regarding “DM_DOCBROKER_E_DMCL_INI_WIN32_MISSING” and “DM_API_E_EXISTING”errors
    Actually I am using dmcl.dll file for 20.2 version and copied into dqman folder. Later I put my dfc.properties file in both dqman/config and dqman folder as well.I changed java.ini and add the below statament in that file
    C:\Program Files (x86)\Java\jre1.8.0_291\bin\client\jvm.dll”
    Now am tring that above steps but still getting below issue while opening Dqman. Kindly check the screenshot and guide me

    Like

    Reply

  7. Just managed to get dqman working on 21.2 – so beware one little gotcha. You need the 32 bit version of the dmcl.dll – thats the larger one – with a date of 2008 and size about 56k. If in doubt use the very excellent sysinternals tool – sigcheck which tells you which architecture its for.

    C:\Users\dmadmin>sigcheck.exe C:\Documentum\product\21.2\bin\dmcl.dll

    Sigcheck v2.82 – File version and signature viewer
    Copyright (C) 2004-2021 Mark Russinovich
    Sysinternals – http://www.sysinternals.com

    c:\documentum\product\21.2\bin\dmcl.dll:
    Verified: Unsigned
    Link date: 07:10 16/04/2021
    Publisher: n/a
    Company: n/a
    Description: n/a
    Product: n/a
    Prod version: n/a
    File version: n/a
    MachineType: 64-bit

    C:\Users\dmadmin>sigcheck.exe c:\dev\tools\dqMan\dmcl.dll

    Sigcheck v2.82 – File version and signature viewer
    Copyright (C) 2004-2021 Mark Russinovich
    Sysinternals – http://www.sysinternals.com

    c:\dev\tools\dqman\dmcl.dll:
    Verified: Unsigned
    Link date: 03:57 12/07/2008
    Publisher: n/a
    Company: n/a
    Description: n/a
    Product: n/a
    Prod version: n/a
    File version: n/a
    MachineType: 32-bit

    Like

    Reply

  9. Back in December 2021, fme AG announces development of a new dqMan commercial version for administration of OpenText Documentum. With the new dqMan, users can expect the release of a revised version providing compatibility to current OpenText Documentum applications and feature enhancements like a new user interface offering an improved user experience. In addition, also full native support for x64 and Citrix support is planned. The release is planned for July 2022 and you can find the first information and a early bird discount for the upcoming dqMan here: http://www.dqman.com

    Like

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.