Release Notes
Open Text Content Server Connector Release Notes
Released Versions
- SDK SDK 1.2 4 (viaworks ViaWorks 2.68)SDK
- SDK 1.3 5 (viaworks Locator 2.79)
- SDK 1.4 6 (viaworks Locator 2.810)
Supported Open Text Content Server Versions
...
- A license for the Open Text Content Server Connector.
- Open Text Content Server integrations web services must be available.
- Username and password authentication are used for Open Text Content Server users.
- Index user must have read access to all nodes.
- If SSO is enabled using Open Text Directory Services (OTDS), the following requirements must be met:
- User has to use one of the following formats
- samAccuntName
- samAccountName@domain.com
- domain\samAccountName
- user.name@domain.com (as per the 'mail' attribute in AD)
- User synchronization is set up using an Active Directory Group, such as APP.Content.Server.Users
- The 'mail' attribute for the user in Active Directory must be set for syncrhonization to work!
- Open Text Content Server needs to be running within the same LAN as viaworksLocator.
- User has to use one of the following formats
Supported Data Types
The connector supports indexing the following data types:
- Appointment (Project and Task. See Well Known Types)
- Document Document (All Well Known Types except Appointment types. See Well Known Types)
- User
Crawl Methods
Full Crawl: The Open Text Content Server Connector supports scheduling periodic full scans of the source system.
...