Content Server Connector Prerequisites

User Accounts and Application Permissions

Required Permission Description
Active Directory account

A valid Active Directory account with READ access to the Content Server (LiveLink) file shares.
Database account

Oracle: Separate Oracle database login and password with READ access to all of the content.

SQL: Separate database login and password with READ access to all of the content.
Content Server account Valid Content Server account with full READ permissions.
Domain Accounts
  • Service Account
Windows Authentication: If you installed your Web service on a machine that is in a different domain, you must set up trust between the domains.
  • Impersonate
Basic Authentication: If you deployed Content Server to a remote domain, BA Insight recommends that you manually configure your authentication in IIS. For more information, go to Configure Basic Authentication (IIS 7).

Connector Features and Requirements

Features Supported Additional Information
Supported version Supported Content Server versions:
  • 9.7+
  • 10+
  • RM v4.2+
  • OpenText Content Server v16.x and later
 Content Server connector supports Content Server v16.x to the latest version.
Searchable content types Yes All content types.
Content Update Full and Incremental All BA Insight Connectors support both Full and Incremental crawls, unless noted.
Permission Types Yes

All BA Insight Connectors support fetch ACLs from the source system.

To make items public or restricted to a single user/set of users, you can do so within the Connector Framework.
Required Software

PowerShell v2

.NET Framework v4.7.2

BA Insight Connector Framework

PowerShell v2 is installed from Windows Server Manager.

Navigate to Server Manager> Manage> Add Roles and Features.

Connector Framework must be installed before installing the Content Server connector.
Required Extensions EXE (or DLL)
  • When you generate the URL that end users will click on in their search results, this URL has an extension that is usually blocked by SharePoint.
    • For example:
      http://host/livelink.livelink.exe
      or
      http://host//ecm/llisapi.dll
  • For SharePoint Search: Add EXE (or DLL) to the allowed extensions.
  • The default extension that is used during crawl enumeration is lvl. For this reason, you must add the lvl extension to the SharePoint allowed extensions list.
Optional Software Microsoft Visual J# Version 2.0 Redistributable Package To use LAPI as the file retrieval model, install the Microsoft Visual J# Version 2.0 Redistributable Package on the same machine where the Content Server connector is installed.