Connector Configuration
OpenText Documentum Configuration
Connection Settings
Configuration Options determining the credentials and target database.
Name | Description |
---|---|
Username |
The account which you want to use to execute your Documentum query |
Password |
The password for the user. |
Database |
The OpenText Documentum repository which hosts the documents. Exactly one repository needs to be configured. |
Documentum Foundation Classes |
This file configures the Documentum Foundation Classes client on how to look up content repositories. It can be found in the OpenText Documentum installation directory, in the config folder as dfc.properties. This file coming from the Documentum installation directory can be used as is in most of the cases. |
Documentum Foundation Classes |
This keystore serves as the identity of the client. The default expects a keystore with a store password of 'dfc' and a certificate under the alias 'dfc' with the password '!!dfc!!'. These defaults can be changed by configuring them as part of the dfc.properties. |
Content Selection
Configuration Options determining which DQL queries are used to request documents from Documentum
Name | Description |
---|---|
Base URI |
This will be the root for Documentum links and must be set to the root web application of the OpenText Documentum UI. |
Queries |
DQL Queries which are requested from Documentum. They are not validated and results should not overlap. Type The type of document that should be queried, i.e. the table for the query. A suitable value would be 'dm_document'. Conditions Restrictions which the documents also have to fulfil. If more than one condition is given, all conditions have to be fulfilled for a document to be indexed. For further reference and more advanced Documentum users, this is the full DQL query that is sent to the OpenText Documentum instance.
|
Tuning Settings (Optional)
Settings for pagination and caching to improve performance at the cost of increased memory.
Name |
Description |
Content Batch Size |
The number of documents which is collected with a single call to Documentum during content synchronization. Only the id and the security and checksum fields are queried. This is an optional value with a default of 1000. |
Security Batch Size |
The number of principals which is collected with a single call to Documentum during principal synchronization. Only the id and the user alias fields are queried. This is an optional value with a default of 10,000. |
Breadcrumb Cache (Optional)
Cache for folders which make up the document breadcrumbs.
Name |
Description |
Maximum size |
The maximum number of elements in this cache before elements are evicted with a least-recently-used strategy. This is an optional value with a default of 10000. |
Maximum Time-To-Live |
Maximum age of a queried element before it is re-queried from Documentum. Changes to an element will only be picked up after the element expired. This is an optional value with a default of 1h. |
ACL Cache (Optional)
Cache for objects from dm_user to determine whether they are users or groups.
Name |
Description |
Maximum size |
The maximum number of elements in this cache before elements are evicted with a least-recently-used strategy. This is an optional value with a default of 10000. |
Maximum Time-To-Live |
Maximum age of a queried element before it is re-queried from Documentum. Changes to an element will only be picked up after the element expired. This is an optional value with a default of 1h. |
ACL Type Cache (Optional)
Cache for objects from dm_user to determine whether they are users or groups.
Name |
Description |
Maximum size |
The maximum number of elements in this cache before elements are evicted with a least-recently-used strategy. This is an optional value with a default of 10000. |
Maximum Time-To-Live |
Maximum age of a queried element before it is re-queried from Documentum. Changes to an element will only be picked up after the element expired. This is an optional value with a default of 1h. |
Documentum Field Mapping (Optional)
This section contains the document fields which, if present, are used to fill the strongly typed Raytion default schema. All metadata that are available in the selected table will be transferred to the source system metadata map.
The list of standard metadata and their default source field is the following:
Name |
Description |
Title |
object_name |
Item type |
r_object_type |
Mime type |
a_content_type |
File extension |
a_content_type |
Keywords |
keywords |
Languages |
language_code |
Author |
r_creator_name |
Contributors |
<empty> |
Creation date |
r_creation_date |
Modification date |
r_modify_date |
Documentum Security Settings (Optional)
Configuration Options determining additional settings for the principal synchronization.
Name |
Description |
Principal Alias |
The field from which the user name for the principal synchronization is taken, so that mapping into other security domains becomes possible. By default this is the field user_name. |
CSM Configuration
Required Configuration Properties
Optional Configuration Properties
CSM Connection Settings
Configuration options for fine-tuning the Http connection parameters.
Name | Description |
---|---|
Concurrent Connections |
Maximum number of concurrent open connections. |
Requests Rate |
Maximum number of requests per second. |
Connect Timeout in Milliseconds |
Timeout of the connect request. |
Socket Timeout in Milliseconds |
Timeout of the socket connected to CSM. |
Request Timeout in Milliseconds |
Timeout of a request to CSM. |
Microsoft Azure Cognitive Search Configuration
Microsoft Azure Cognitive Search Instance Settings
Configuration Options to specify the service and index to feed documents to.
Name | Property Key | Description |
---|---|---|
Service Name |
|
Name of the target service in the Microsoft Azure Cognitive Search Portal. |
Index ID |
|
ID of the target index to feed to. |
API Key |
|
Key for the API requests. |
Microsoft Azure Cognitive Search Connection Settings
Configuration Options related to establish a connection and sending requests to Microsoft Azure Cognitive Search.
Name | Property Key | Description |
---|---|---|
Maximum Connections |
|
Maximum number of open connections to the target instance. |
Maximum Requests Per Second |
|
Maximum number of requests per second to the target instance. |
Request Timeout |
|
Timeout of requests to the target instance. |
Socket Timeout |
|
Timeout of the socket connected to the target instance. |
Use Proxy |
|
Use a proxy server to connect to Microsoft Azure Cognitive Search. |
Microsoft Azure Cognitive Search Proxy Settings
Specify the proxy options for connecting to Microsoft Azure Cognitive Search.
Name | Property Key | Description |
---|---|---|
Endpoint |
|
The proxy endpoint including protocol, host and port. |
General Configuration
Database Configuration
Setting | Description |
---|---|
URL |
JDBC URL for the target database. Out of the box, the connector will use H2 file database. For productive usage, use PostgreSQL specifying the URL in format: |
Username |
Database Username to read and write to database. |
Password |
Database Password for the specified user |
Traversal Configuration
Setting | Description |
---|---|
Traversal History Length |
Max. number of traversals to store in the history. Once the limit is exceeded, the connector will automatically remove oldest entries in the history. (default: 100) |
Number of Traversal Workers |
Number of workers to execute the traversal in parallel. Increasing this value might improve the performance, but will footprint higher memory consumption. It is recommended to keep the default value. (default: 10) |
Traversal Job Poll Interval |
Interval between the workers to be triggered to fetch and process the next tasks. (default: 10ms) |
Completion Timeout |
If the search engine indexes the items asynchronously, there might be some processing still in-flight during the completion process of a traversal. This value specifies the timeout value until all asynchronous callbacks are expected to return before completing the traversal. (default: 10m) |
Principal Aliaser Configuration
Principal Aliasing is applied on user information as part of Content ACL processing during Content Synchronization and Principal processing during Principal Synchronization. It’s purpose is to map external source system user to the corresponding user in search engines domain. You can configure a list of aliasers in the connector which will be applied in sequence and in order on user ACEs and user principals. The Connector supports following custom aliasing mechanism.
Custom Aliaser Disabled
If the Custom Aliaser checkbox is not selected, the connector will process user information on ACE and user principals unchanged to Search Engine. If all relevant users in the source system can be found with the same identifier in the search engine, this setup is sufficient to reflect the same secure search experience in the search engine as defined by the policy in the source system. The connector uses this option as default to process user information.
Custom Aliaser Enabled
If custom aliasing is enable then there are four types of aliaser avaialble:
Simple XML Table Aliaser
Static mapping table which can be uploaded as XML file. The connector uses the uploaded file as lookup table to map a user in the source system to a user in the search engine. Users missing a record in the file will be dropped from the ACE and during Principal Synchronization. This option is only recommended for environment with a manageable amount of users as for each user the corresponding mapping entry needs to be specified in the file.
Setting | Description |
---|---|
XML Mapping File |
Browse and upload or drag and drop. |
Sample XML mapping file:
<?xml version="1.0" encoding="UTF-8"?> <storeddata> <entry keyValue="user1">user1@raytion.com</entry> <entry keyValue="user2">user2@raytion.com</entry> <entry keyValue="user3">user3@raytion.com</entry> </storeddata>
Regex Replacer Aliaser
Regex Replacer Aliaser computes aliases based on a regular expression. Principals that match the regular expression are replaced by the Substitution String.
Setting | Description |
---|---|
Pattern |
The regular expression to match, this is the part that will be replaced. If braces (…) are used in the pattern then the matched value can be retrieved using $1 |
Substitute String |
String to replace the matching part of the find string. Matched value is accessed by employing $1 |
Regex Extractor Aliaser
Regex Extractor Aliaser computes aliases based on a regular expression. Principals that match the regular expression are inserted into the Insert-Into String.
Setting | Description |
---|---|
Pattern |
The regular expression to match, this is the part that will be inserted into the new value. If braces (…) are used in the pattern then the matched value can be retrieved using $$ |
Insert-Into String |
String to replace the matching part of the pattern. Matched value is accessed by employing $$ |
LDAP Aliaser
Ldap Aliaser searches for an LDAP entry with the requested name in the input value and returns the specified output attribute.
Setting | Description |
---|---|
Host |
Fully Qualified Domain Name of an LDAP server |
Port |
Port to use for LDAP connection, defaults are 389/636 or (recommended) 3268/3269 for simple/SSL |
AccountDN |
AccountDN for bind to LDAP |
Password |
Password part of credentials |
Input Field |
The Active Directory attribute name for this equality filter |
Search Root DN |
Distinguished Name of the subtree which is searched. The smaller the subtree the better the performance but the higher the chance of encountering principals which are not part of this subtree |
Output Field |
Attribute that should be returned in result entries |