OpenText Content Server
Quick Start

  1. Check that the Content Web Services are installed, and follow the installation instructions provided by OpenText if not.

  2. If Security Clearance (part of Records Management) is used, check that the Records Management Security Management SOAP API is installed, and follow the installation instructions for the Content Web Services, replacing cws with cs-services-rmsecmanagement as needed, if not.

  3. Create a technical user that has permissions to see the properties, content, and permissions of all nodes that should be traversed. At a minimum, the technical user needs the privileges “Log-in enabled” and “Public Access enabled” in the OpenText Content Server, which in turn means the technical user must not be disabled/deactivated in the underlying user store. The technical user also needs to use the language “English ( United States )”.

  4. If the LiveReport approach to Automated Change Processing will be used, create the required LiveReport. To do this, import this LiveReport if your OpenText Content Server installation uses an MSSQL database or this LiveReport if it uses an Oracle database.

    If the Search approach to Automated Change Processing will be used, ensure that the internal search of the OpenText Content Server to be traversed is working and has a data source that contains all nodes to be traversed.

See OpenText Content Server Setup for more details.