Open Text Content Server Connector Data Sheet

Release Notes

Open Text Content Server Connector Release Notes

Released Versions

• SDK 1.4 (ViaWorks 2.8)
• SDK 1.5 (Locator 2.9)
• SDK 1.6 (Locator 2.10)

Supported Open Text Content Server Versions

Open Text Content Server version 10.5 and version 16.

Limitations

• Personal work spaces are not currently indexed.
• External document storage has not yet been tested, so it's unknown if this will work or not.
• Shortcuts/aliases, collections, generations, reports or workflow maps are not indexed.

Prerequisites

• 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 Locator.

Supported Data Types

The connector supports indexing the following data types:

• Appointment (Project and Task. See Well Known Types)
• 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.

Incremental Crawl: Not supported.

DocumentHandler

Not required.

Other information

None.