Opentext eDocs integration GUIDE
Step by step guide to integratie Opentext eDocs with Lexis® Create DMS
Integration Requirements
The OpenText eDOCS DMS is always hosted on-premise. This means that the server needs to be made available over the public internet to Lexis® Create DMS.
-
OpenText eDOCS version >= 23.X
(The integration was thoroughly tested against 22.3)
-
eDOCS REST API Server must be installed
- HTTPS is required. Ensure the following requirements are taken into account for the https certificate:
- Signed by a recognized certificate authority. The certificate chain must contain a root certificate from an established root CA (= Certificate Authority).
- Ensure the full certificate chain is returned by your server. In most cases this translates to returning the following:
-
- the server certificate
- the intermediate CA certificate
- and the root CA certificate
openssl s_client -verify_return_error -connect <host>:<port>
The eDOCS REST API Server instance must be exposed on a secure URL (Ex.: https://edocs-server.customer-name.com). A secure URL means that https must always be used, unsecured http is not allowed.
-
-
Strongly advised: To make the connection a bit more secure, customers can configure IP allowlisting on their instance. Please reach out to your CS contact to receive our outbound IP addresses.
- Adding a custom Henchman search form
- Enabling Henchman search form for Service Account
- Connect via Lexis® Create DMS Portal
- Deploy Word/Outlook Add-In
By following the above steps your OpenText eDocs will be integrated with Lexis® Create DMS.
If you experience issues/problems, please reach out to you CS contact.
If you want to learn more about our SSO setup, read this article.
Important: Please ensure that your DMS API endpoint is accessible on port 443, port 8443, or port 9443.