# Installation

## Prerequisites

{% hint style="danger" %}
Always install and configure any prerequisite software as per the official instructions published by their respective vendors.
{% endhint %}

### Windows

dqMan OpenText Documentum Edition is officially supported on Windows 64-bit operating systems.

**Operating system**:

Microsoft® Windows® version 10 or later and Windows® Server 2016 or later (64-bit only, 32-bit versions are *<mark style="color:red;">not</mark>* supported!)

**OpenText Documentum Foundation Classes (DFC)**:&#x20;

Documentum 16.4 - 16.7 requires DFC 16.4 with latest patch - DFC 16.7

Documentum 20.x - 24.x requires DFC 20.x - DFC 24.x

**Java**:

Oracle Java SE JDK or supported OpenJDKs  (64-bit only, 32-bit versions are *<mark style="color:red;">not</mark>* supported!)

all versions officially supported by the target Documentum Content Server version and DFC

{% hint style="danger" %}
Always use the DFC and Java versions officially certified by OpenText for the targeted Content Server version, as specified in the respective OpenText Documentum Content Server version's Release Notes document.
{% endhint %}

### Linux

Although there is no native Linux build of dqMan, it is possible to run the Windows version of dqMan on Linux using Wine. This section describes a verified configuration and the steps required to successfully launch dqMan on a Linux environment.

dqMan on Linux was tested using Wine versions 9.0 and 11.0.\
Testing was performed on Ubuntu 22.04.1 LTS and Ubuntu 24.04.4 LTS.

**Environment Setup**

* Install Wine\
  Install the latest stable Wine release for your distribution.
* Prepare Java Runtime\
  Copy a compatible Windows 64-bit JRE/JDK into a local folder.
* Copy Documentum DFC\
  Place the Documentum Foundation Classes (DFC) for your repository version in a subfolder, ensuring that the correct dctm.jar and native libraries are present.
* Copy dqMan Package\
  Place the standalone Windows dqMan package into a working directory.

**Documentum Configuration**

Create a directory for dfc configuration, then ensure dfc.properties and any repository mappings are correctly set under the 'config' directory.

## Launching dqMan

dqMan is distributed as a portable application packaged as a ZIP file. The ZIP file can be extracted anywhere on the installation machine. The folder where dqMan is extracted to can have any name, as per the user's preferences.

### Windows

Please note that deploying the application to the default Program Files folder may require administrative permissions; this is standard Windows behavior when deploying any files to the Program Files folder and not specific to dqMan.

### Linux

When running under Wine, dqMan remains a Windows application. All dependencies (Java, DFC) must be Windows builds and accessible within the Wine environment.

From the directory where dqMan.exe is located, run: `wine dqMan.exe`

Wine will start the dqMan UI. On first run, expected log/output appears in the Wine console               review for missing dependencies (e.g., missing DLLs) and install via winetricks if necessary.

## Command line parameters

You can use the following command line parameters in dqMan:

**For login**:

* `-r<Repository>`- Autoconnect to the supplied repository. The repository name must be given in the same format dqMan is configured to use. If fully qualified server names are activated, repository names need to match this format.
* `-u<Username>` - A valid username to log in with
* `-p<Password>` - The password for the user.
* `-disablelogin` - Disable login to new repositories. Multiple sessions are allowed to the same repository.

#### Profile management:

* `-profile <index|name>` - Start dqMan with a custom Java & DFC profile by specifying a profile index number or profile name

{% hint style="info" %}
See [java-and-dfc-profile-management](https://docs.dqman.com/opentext-documentum-edition-26.1/java-and-dfc-profile-management "mention") for detailed information on managing and loading custom profiles via command line parameters
{% endhint %}

**Other parameters**:

* `-f<Filename>` - The full name (including path) to a scriptfile can be supplied to open this at startup. The scripttype (API or DQL) is determined by the file extension. If the filename contains spaces, it must be enclosed by double quotes”.
* `-execute` - If a file is loaded using `–f<filename>`, it can be executed immediately. This function also needs valid login informations passed with the command line.

  When the execution is finished, dqMan will be closed.

## Glossary and Terms

<table><thead><tr><th width="150">Term</th><th>Explanation</th><th data-hidden></th></tr></thead><tbody><tr><td>ACL </td><td>Access Control List</td><td></td></tr><tr><td>DQL</td><td>Documentum Query Language</td><td></td></tr><tr><td>API </td><td>Documentum API command language/syntax</td><td></td></tr><tr><td>DFC</td><td>Documentum Foundation Classes</td><td></td></tr><tr><td>CS</td><td>Documentum Content Server</td><td></td></tr><tr><td>OT</td><td>OpenText (Documentum vendor)</td><td></td></tr><tr><td>DB</td><td>Database</td><td></td></tr><tr><td>SQL</td><td>Structured Query Language</td><td></td></tr><tr><td>fme</td><td>fme AG (dqMan vendor)</td><td></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dqman.com/opentext-documentum-edition-26.1/installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.