OpenText Content Server
- Andrea Harvey
On This Page
Overview
The OpenText Content Server connector in DryvIQ allows you to analyze, migrate, copy, and synchronize files to your OpenText enterprise content management solution from cloud storage repositories and on-premise network file shares. The first step is to create the OpenText Content Server connection by providing the connection information required for DryvIQ to connect to the server. The connector can be created using any OpenText user account with permissions to access the content.
DryvIQ supports OpenText Content Server 10.5 and 16.x.
Creating a Connection
Expand the Manage section in the left navigation menu.
Click Connections.
Click Add connection.
Select OpenText Content Server as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Click Test connection to ensure DryvIQ can connect using the information entered.
You will see a green "Connected” message on the bottom of the modal when DryvIQ establishes connection. (If the connection fails, verify the information you entered.)
Click Done.
Add Connection Modal for OpenText Content Server
Â
Field | Description | Required |
|---|---|---|
Display as | Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists. If you do not add a display name, the connection will automatically be named using the OpenText server URL entered. For example, OpenText (https://{servername}/otcs/cs.exe/). | Optional |
Url | Enter the URL to access the server. This will look similar to the following example: https://{servername}/otcs/cs.exe/. | Required |
User name | Enter the username that should be used to log on to the server. This needs to be an account with permissions to access the content that will be processed. | Required |
Password | Enter the password for the username added in the previous field. | Required |
DS Service name | Enter the directory service name. This defines how DryvIQ can access the user/group directory. DryvIQ will use “otdsws” as the default name. Specify a different name if needed. | Optional |
CS CGI | Enter the connection information for the content services common gateway interface. The entry will look similar to the following example: http://{servername}/otcs/cs.exe. | Optional |
Extension module installed? | Select if the Syntergy extension module is installed. This indicates if you use Syntergy API extensions for managing timestamps and author information. Learn more about Syntergy API Extensions. | Optional |
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.Â
Supported Features | Unsupported Features | Other Features/Limitations |
|---|---|---|
File size maximum: No maximum | ||
Path length maximum: No maximum | ||
No leading spaces in file name/folder name | ||
 | No trailing spaces before or after file extensions | |
 | Invalid characters: | \ / < > : ? * | |
 | Restricted types: none | |
 |  | |
 |  | |
 |  |
Email Folders
OpenText supports email folders (subtype 751). DryvIQ cannot see the email folders and therefore, will not migrate content in these folders.
Invalid Characters and Spaces
DryvIQ verifies file and folder names to identify unsupported characters based on the platform. It then replaces invalid characters with an underscore (_) so the files and folders can be transferred. Similarly, DryvIQ will sanitize file names that contain combined Unicode characters by replacing the characters with an underscore (_).
The logic includes leading and trailing spaces in file and folder names. DryvIQ replaces the space rather than trimming it because trimming the space could cause duplicate file names. Adding the underscore ensures the name remains unique.
Â