dqMan is powerful and feature-rich administration tool for OpenText Documentum.
It offers many Documentum administrative features and functionalities, DQL and API support for single queries/commands as well as extensive code editing and script execution/debugging features, script templates for generating scripts, job management, import/export from/to external data sources, and much more.
The clean user interface allows quick and efficient use of all these features and in addition offers extensive customization with context sensitive actions based on Documentum DQL and API languages (no 3rd party or proprietary scripting languages needed).
dqMan offers a wide range of functionalities for OpenText Documentum professionals (administrators, consultants, developers) to manage OpenText Documentum Content Servers.
dqMan is targeted at IT professionals who are already familiar with the OpenText Documentum platform, especially DQL and API as well as DFC configuration and Documentum Content Server specifics such as the Documentum Object Model.
Send any feedback, questions, feature requests or bug reports to dqman@fme.de.
Always install and configure any prerequisite software as per the official instructions published by their respective vendors.
Operating system:
Microsoft® Windows® version 10 or later (64-bit only, 32-bit versions are not supported!)
OpenText Documentum Foundation Classes (DFC):
Documentum 16.4 - 16.7 requires DFC 16.4 with latest patch - DFC 16.7
Documentum 20.x - 22.x requires DFC 20.x - DFC 22.x
Java:
Oracle Java SE JDK or supported OpenJDKs (64-bit only, 32-bit versions are not supported!)
all versions officially supported by the target Documentum Content Server version and DFC
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.
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.
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.
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 <index|name>
- Start dqMan with a custom Java & DFC profile by specifying a profile index number or profile name
See Java & DFC Profile Management for detailed information on managing and loading custom profiles via command line parameters
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.
Term | Explanation |
---|---|
ACL
Access Control List
DQL
Documentum Query Language
API
Documentum API command language/syntax
DFC
Documentum Foundation Classes
CS
Documentum Content Server
OT
OpenText (Documentum vendor)
DB
Database
SQL
Structured Query Language
fme
fme AG (dqMan vendor)