# Connecting to Documentum OpenText

### Log in/out

**To log in to a Documentum Content Server**, start dqMan, enter your login credentials and then select the desired repository from the list. You can save your login credentials by selecting **Save in login history** and use them again in the future by clicking the **History** button. 

![The dqMan Login screen](https://content.gitbook.com/content/Yffe42hx9CVnT3x1mJXJ/blobs/nQsQ9qSznC40JvzQaXSh/Login.png)

### Manage Sessions

dqMan can open multiple sessions to the same or different repositories. You can open a session in several ways:

* Click ***Session** menu**>New Session Window***, or press Ctrl+N.
* Click the **New Session Window** toolbar button <img src="https://content.gitbook.com/content/Yffe42hx9CVnT3x1mJXJ/blobs/2bBfowHfOZuoI6yQ3p28/New%20Session%20button%20toolbar.png" alt="" data-size="line">
* If you already have an open Session window which you would like to duplicate into a second session with the same credentials on the same repository click the **Copy session** toolbar button <img src="https://content.gitbook.com/content/Yffe42hx9CVnT3x1mJXJ/blobs/zzTflVXaY6e78KE8OZDr/Connect%20toolbar%20button.png" alt="" data-size="line">
* Certain API commands can be executed without a connected session (such as `getservermap`, `getdocbrokermap` or `connect`).

Whenever a session is needed but not available, the same login dialog box described in [#2.1-log-in-out](#2.1-log-in-out "mention") is displayed.

Sessions are always bound to a session window. Disconnecting a session window will terminate the session, but will not close the session window.

dqMan enables you to open as many sessions as needed, restricted only by the settings in the Client or Server configuration.

You can manage Sessions using the **Session** menu or the toolbar. The available functions are:

<table><thead><tr><th width="259.66336633663366">Function</th><th>What It Does</th><th data-hidden></th><th data-hidden></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>New Session Window</strong></td><td>Opens a new session window with the login dialog box. For more information on logging in to dqMan, see <a data-mention href="#2.1-dqman-log-in-log-out">#2.1-dqman-log-in-log-out</a>.</td><td></td><td></td><td></td></tr><tr><td><strong>New Jobs Window</strong></td><td>Opens a new Jobs session. For more information about dqMan Jobs, see <a data-mention href="jobs">jobs</a>.</td><td></td><td></td><td></td></tr><tr><td><strong>Copy</strong></td><td>Creates a copy of the current session window and logs you in automatically using the same user credentials.</td><td></td><td></td><td></td></tr><tr><td><strong>Connect/Disconnect</strong></td><td>Opens/terminates a session without closing the session window. The button will show <strong>Connect</strong> or <strong>Disconnect</strong> based on the whether the active session window is currently connected or not.</td><td></td><td></td><td></td></tr><tr><td><strong>Refresh Valuelists</strong></td><td>Reloads session dependent value lists, like users, groups, or object types.</td><td></td><td></td><td></td></tr><tr><td><strong>Session Alias</strong></td><td>Sets an alias name for a session. This name is used instead of default session name @ wherever it is possible.</td><td></td><td></td><td></td></tr><tr><td><strong>Locale</strong></td><td>Switches current session locale to the locale selected from submenu.</td><td></td><td></td><td></td></tr><tr><td><strong>Close</strong></td><td>Closes the current window.</td><td></td><td></td><td></td></tr><tr><td><strong>Exit</strong></td><td>Closes dqMan.</td><td></td><td></td><td></td></tr></tbody></table>

## SSL Configuration

To ensure a secure server connection, follow these instructions:

Connecting Without SSL:

* Verify if the server allows connecting without SSL.
* Open the dfc.properties file used by DqMan.
* Set the value for dfc.session.secure\_connect\_default as follows:

&#x20;       `dfc.session.secure_connect_default=try_native_first`

Connecting via SSL:

To establish a secure connection using SSL, configure the dfc.properties file used by DqMan with the necessary settings. Follow these steps:

a) Configuring dfc.properties for SSL truststore:

* Locate the dfc.properties file used by DqMan.
* Add the following values to the file:

&#x20;        `dfc.security.ssl.truststore=C\:/Documentum/dba/secure/dfc.keystore`

&#x20;        `dfc.security.ssl.truststore_password=......`

&#x20;        `dfc.session.secure_connect_default=secure`

* Note: The path "C:/Documentum/dba/secure/dfc.keystore" is used for demonstration purposes only. To generate the correct value, copy the dfc.keystore file from the Content Server to the machine where DqMan is installed. Update dfc.security.ssl.truststore with the path to this file. Make sure the dfc.keystore file contains the appropriate SSL certificates.

b) Adding SSL certificates to the JDK's cacerts file:

If the previous step does not resolve the issue, follow these instructions:

* Locate the cacerts file of the JDK used by DqMan.
* Add the two SSL certificates to the cacerts file.

Note: Ensure that all configurations and settings are properly followed to establish a secure connection with the server.