Java & DFC Profile Management

dqMan comes with a profile management feature allowing users to define multiple profiles using different Java and DFC versions.

This can be used by Documentum professionals who need to work with many different Documentum Content Server versions/environments while using just one dqMan installation.

dqMan can be started with any profile, thus providing the respective Java and DFC environment for working with specific Documentum Content Servers.

Managing Profiles

Profiles can be created, edited and deleted using the JRE & DFC Profiles page in the dqMan Options dialog (Extras menu>Options)

On the first launch after deployment dqMan will attempt to auto-detect the default Java and DFC installations present on the maching and if this is successful, it will create a profile called [0] Default. To make sure that dqMan will be able to correctly auto-detect the Java and DFC installations on the local machine please follow the instructions in #prerequisites.

Loading Profiles

dqMan can be launched with any of the available profiles. It is also possible to run multiple dqMan instances using different profiles.

The recommended way for using profiles is to create custom dqMan shortcuts, with each shortcut used to load a specific profile:

1. Hold Alt & drag dqman.exe from your dqMan folder to the Desktop to create a shortcut

2. Rename the shortcut to something suggestive

3. Edit the shortcut's properties and append either of the following to the command line in the shortcut's Target field:

To confirm the expected profile has been loaded, open Help>About and verify the profile name and Java and DFC information in the About window's System information section.

Troubleshooting profiles and editing the dqman.properties file

dqMan saves all profile related information to the %localappdata%\dqMan\Config\dqman.properties file. Although it is not recommended to edit this file directly, it may be required to do so in certain situations.

dqMan fails to detect locally installed Java and/or DFC

if dqMan fails to automatically detect the default Java and/or DFC installed on the local machine it is usually due to either of these not having been installed as per their respective vendor's installation instructions, as outlined in #prerequisites. We recommend following the instructions from the Prerequisites page and then restarting dqMan to allow it to correctly detect the default Java and/or DFC installations.

If it still isn't possible for dqMan to detect the default Java and/or DFC installations despite having followed the instructions outlined in #prerequisites it may be necessary to edit or create the dqman.properties file manually. Please follow the below steps to edit/create the file manually:

1. Open the %localappdata%\dqMan\Config\dqman.properties file with your text editor If the file does not exist, create a new file in your text editor and save it as %localappdata%\dqMan\Config\dqman.properties

2. Copy and paste the template dqman.properties file's content from #template-for-dqman.properties-fileinto the text editor

3. Edit the paths from the template to match your Java and DFC installations

4. Save the dqman.properties file and start dqMan

The default Java and/or DFC detected initially by dqMan has been removed/uninstalled later and now dqMan cannot start

If the Java and/or DFC auto-detected during dqMan's first start is later removed/uninstalled then dqMan will run into errors as it won't find the required prerequisites anymore. To reset dqMan's default profile and re-trigger dqMan's auto-detect functionality, follow the steps below:

1. Open the %localappdata%\dqMan\Config\dqman.properties file with your text editor

2. Delete all lines starting withdqman.profile.....[0]= (pay attention at the [0] (zero) index and do not delete other lines containing non-zero indices)

3. Save the file and start dqMan dqMan should now auto-detect your newly installed Java and/or DFC instead of the previously uninstalled versions

4. If step 3. fails, fall back to #dqman-fails-to-detect-locally-installed-java-and-or-dfc above

Template for dqman.properties file

Use the below template to create a new dqman.properties file if needed.

dqman.profile.name[0]=Default dqman.profile.path.jre[0]=C:\Program Files\openjdk-11.0.14 dqman.profile.path.dfc.program[0]=C:\Program Files\Documentum dqman.profile.path.dfc.user[0]=C:\Documentum