For a general introduction to the connector, please refer to RheinInsights OpenText Content Server Enterprise Search and RAG Connector.

Crawl User Permissions

You need to create a crawl user which has the following permissions:

1. It needs to have read permissions to the nodes, their metadata, the node ACLs below a given start node

2. The crawl user needs to have read access to all users, groups and group memberships

3. If you use supplemental markings and security clearances (from the records management module), then the crawl user needs to have (read) access to

   1. the supplemental markings and security clearances per node

   2. the supplemental markings and security clearances for each user (member)

Content Source Configuration

The content source configuration of the connector comprises the following mandatory configuration fields.

Within the connector’s configuration please add the following information:

1. Instance base URL. The base url to up to before the API endpoint of your OTCS instance

2. Login. The user name for fetching user-group relationships

3. Password. The password for this

4. Public keys for SSL certificates: this configuration is needed, if you run the environment with self-signed certificates, or certificates which are not known to the Java key store.
   We use a straight-forward approach to validate SSL certificates. In order to render a certificate valid, add the modulus of the public key into this text field. You can access this modulus by viewing the certificate within the browser.

   

5. Fetch SCLs and SMs. Determines if for each document and the users security clearances and supplemental markings should be fetched

6. Use a specific report to fetch user SCLs and SMs. If enabled, you can define a specific report which needs to expose the supplemental markings (as list of strings) and security clearance level as integer per user

7. Report id for SCLs and SMs. Provide the id of this report.

8. Start configuration. This is a list of start configurations, which allows for using different crawl users for different branches of your OTCS instance.

9. Unique id. Is a unique identifier which is needed for internal reasons. Leave the autofilled value.

10. Login. This is the crawl user for this branch.

11. Password. This is the user’s password for this branch.

12. Root node ids. This is a list of node ids which is used to start crawling the subtrees from.

13. Excluded files from crawling: here you can add file extensions to filter attachments which should not be sent to the search engine.

14. Rate limit: You can specify the number of API calls per second.

15. Category mapping: here you can specify metadata field names for categories which are in use in your OTCS instance

16. Custom HTTP headers. Here you add additional http header information which the connector sends with each REST call

17. Verbose logging of API responses. Logs all REST API responses from OTCS

After entering the configuration parameters, click on validate. This validates the content crawl configuration directly against the content source. If there are issues when connecting, the validator will indicate these on the page. Otherwise, you can save the configuration and continue with Content Transformation configuration.

Recommended Crawl Schedules

Content Crawls

As of now the connector does not support incremental crawls. Therefore, full scans should run on a daily basis.

For more information see Crawl Scheduling .

Principal Crawls

Depending on your requirements, we recommend to run a Full Principal Scan every day or more often.

For more information see Crawl Scheduling .