OpenText™ Extended ECM

Installation Guide

Welcome to Extended ECM! This guide walks you through the

installation and initial configuration of Content Server, which is
the main component of Extended ECM. It starts with an
overview of Content Server system design, explains how you
should prepare your operating system, provides guidelines for
the configuration of your web and database servers, and then
outlines the correct way to install Content Server. It is the first
guide you should read if you are a new Extended ECM
administrator, and a valuable reference guide if you are an
experienced one.

LLESCOR240100-IGD-EN-01
OpenText™ Extended ECM
Installation Guide
LLESCOR240100-IGD-EN-01
Rev.: 2023-Dec-06
This documentation has been created for OpenText™ Extended ECM CE 24.1.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com

© 2023 Open Text

Patents may cover this product, see https://www.opentext.com/patents.

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
 Table of Contents
1 Installing Extended ECM ........................................................... 5
1.1 Overview of Extended ECM Installation .............................................. 5
1.2 Upgrading Extended ECM and Installing Updates ............................... 6

2 Design Your Extended ECM System ....................................... 7

2.1 About Content Server ........................................................................ 7
2.2 Content Server Architecture ............................................................. 13
2.3 Architectural Options ....................................................................... 14
2.4 Best Practices for System Design .................................................... 19

3 Prepare to Install Extended ECM ........................................... 23

3.1 Prepare the Operating System ......................................................... 23
3.2 Install a Database Server ................................................................. 25
3.3 Set Up Client Web Browsers ............................................................ 31

4 Configure the Web Server to Run Extended ECM ................ 35

4.1 Web Server and Application Server Configuration ............................. 35
4.2 Configure a Web Server to Run Content Server ................................ 36
4.3 Configure an Application Server to Run Content Server ..................... 42

5 Install Extended ECM on the Operating System .................. 47

5.1 Install Content Server on Microsoft Windows .................................... 47
5.2 Install Content Server on Linux ........................................................ 66

6 Configure Extended ECM ....................................................... 75

6.1 The Content Server Administration Page .......................................... 75
6.2 Configure Server Parameters ........................................................... 76
6.3 Create the Content Server Database ................................................ 82
6.4 Create an Admin Server .................................................................. 91
6.5 Create the Enterprise Data Source ................................................... 92
6.6 Install Optional Content Server Modules ........................................... 94
6.7 Configure Storage Providers ............................................................ 97
6.8 Select the OTDS Server Type .......................................................... 97
6.9 Configure Syndication Site Parameters ........................................... 105
6.10 License Content Server ................................................................. 105
6.11 The Congratulations! Page ............................................................ 113

7 Complete the Installation and Setup of Extended ECM ..... 115

7.1 Apply All Available Patches to Content Server ................................. 115
7.2 Install Optional Modules ................................................................ 115
7.3 Installing Extended ECM for SAP Solutions with OpenText System
Center Manager ............................................................................ 116

LLESCOR240100-IGD-EN-01 Installation Guide iii

Table of Contents

7.4 Install Content Server Language Packs .......................................... 132

7.5 Set Up the Help Environment ......................................................... 133
7.6 Perform Additional Tasks Before Users Connect ............................. 135
7.7 Configure Extended ECM Features ................................................ 138

8 Install Additional Instances of Extended ECM ................... 155

8.1 Copy the key.bin file from the First Content Server Instance ............ 155
8.2 Front-End Instances ...................................................................... 156
8.3 Agent Servers ............................................................................... 157
8.4 Admin Servers .............................................................................. 164

9 Uninstall Extended ECM ....................................................... 167

9.1 Uninstall Content Server on Windows ............................................. 167
9.2 Uninstall Content Server on Linux .................................................. 167

10 Appendix A – Extended ECM Installation Worksheets ...... 169

10.1 Database Installation Worksheets .................................................. 169
10.2 Web Server Worksheets ................................................................ 172
10.3 Content Server Installation Worksheet ............................................ 173

11 Appendix B – Installing Content Server as a Syndication

Environment ........................................................................... 175
11.1 Install and configure the primary Syndication .................................. 175
11.2 Install and configure a remote Syndication ...................................... 182

iv OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

Chapter 1

Installing Extended ECM

OpenText™ Extended ECM is the leading collaboration and enterprise content

management (ECM) system for global organizations. It is a comprehensive solution
for managing information and makes collaboration a part of every business process.
The prinicipal component of OpenText™ Extended ECM is Content Server.

Content Server has a standards-based, open architecture and integrates seamlessly

with multiple platforms, information repositories, third-party applications, and
legacy systems. It is scalable, extensible, accessible, and secure. To start using
Extended ECM, users require nothing more than a web browser.

1.1 Overview of Extended ECM Installation

This guide walks you through the installation and configuration of Content Server,
the principal component of Extended ECM. It starts by reviewing information that
will inform the design of your Content Server system, moves on through the
preparation of your Content Server operating system and the installation of the
Content Server web server and database server, and finishes with the installation
and initial configuration of Content Server.

To install Content Server, you will follow the sections of this guide in order, starting
with planning your design and finishing by making Content Server available to
users. The design decisions that you make will determine the exact sections that you
need to read. For example, everyone who installs Content Server will read the
sections on installing a database server and creating an operating system user, but
those who deploy Content Server on Linux and Oracle Database will read different
information from those who use Microsoft Windows and Microsoft SQL Server.

Installing Content Server involves the following steps. Each one is explained in a
separate section of the guide.

• “Design Your Extended ECM System“ on page 7

Choosing the operating system, relational database management system and web
server (or web application server) that you wish to use in your Content Server
environment, and planning the architecture of your Content Server system.
• “Prepare to Install Extended ECM“ on page 23
Preparing the Content Server environment. Installing a web server or web
application server. Installing a database. Creating operating system users.
• “Configure the Web Server to Run Extended ECM“ on page 35
Configuring your web server or web application server to work with Content
Server

LLESCOR240100-IGD-EN-01 Installation Guide 5

Chapter 1 Installing Extended ECM

• “Install Extended ECM on the Operating System“ on page 47

Running the Content Server installation program, applying required patches and
starting Content Server for the first time.
• “Configure Extended ECM“ on page 75
Performing the initial configuration of Content Server. Creating a Content Server
database. Installing optional modules. Connecting to an OpenText™ Directory
Services server. Creating the search and indexing infrastructure. Licensing
Content Server.
• “Complete the Installation and Setup of Extended ECM“ on page 115
Installing optional modules (if you didn’t install them during the Content Server
installation) and language packs, applying the latest Content Server patches and
Updates, and performing various tasks before allowing users to connect to
Content Server.

• Information on adding additional instances of Content Server to your

deployment appears in “Install Additional Instances of Extended ECM“
on page 155.
• Information on uninstalling Content Server appears in “Uninstall Extended
ECM“ on page 167.

1.2 Upgrading Extended ECM and Installing Updates

This guide covers the installation of a new Extended ECM system. If you are
upgrading Content Server from a previous version, you should consult OpenText
Extended ECM - Upgrade Guide (LLESCOR-IUP).

6 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

Chapter 2
Design Your Extended ECM System

Content Server can be deployed in a variety of configurations. The first step in

deploying Content Server is designing a system that meets the needs of your users.

The information in this chapter will help you decide how to deploy your Content
Server system. Every Content Server deployment is unique and the potential
variability is wide, so the architecture and configuration issues in this guide are
discussed in very general terms. Your own circumstances may require more specific
approaches. For help with system design issues, contact OpenText Professional
Services using the online contact form at www.opentext.com.

2.1 About Content Server

Content Server is a service that sits between a database and a web server. It manages
data using a database server and relies on a web server to exchange information
with its users. A servlet container is necessary for delivering Java-based features in
Content Server. Figure 1–1 presents a simple diagram showing all three services
installed on a single computer.

Figure 2-1: Basic Content Server System

Users interact with Content Server through the web server when using the standard
browser interface, or they may communicate directly with the Content Server using
a desktop application, such as Enterprise Connect.

Note: A single-computer architecture as shown here is typical of Content

Server systems that are used for demonstrations, testing, training, or

LLESCOR240100-IGD-EN-01 Installation Guide 7

Chapter 2 Design Your Extended ECM System

development. This architecture is not recommended for a production Content

Server system. For more architecture options, see “Content Server
Architecture” on page 13.

2.1.1 Required Third-Party Applications

Note: The version numbers of third-party software that Content Server
supports can change for any new version of Content Server. Platform support
may be added in Updates for Content Server. For detailed information about
certified and supported products and product combinations (including specific
software versions and releases), see the Release Notes that accompany this
documentation. The most recent version of the Content Server Release Notes is
maintained on My Support (https://knowledge.opentext.com/).

A complete Content Server system includes the following components:

• A server operating system. Content Server supports the following operating

systems:

– Microsoft Windows®
– Red Hat® Enterprise Linux®
– Oracle Linux
• A relational database management system (RDBMS) serves as the Content Server
data repository. Content Server supports the following databases:

– Microsoft Azure SQL

– Microsoft SQL Server® (on Windows)
– Oracle® Database
– PostgreSQL (on Linux, Google Cloud Platform, and Amazon Web Services)
– SAP® HANA
• A web server for exchanging data between Content Server and its clients.
Content Server supports the following web servers:

– Microsoft Internet Information Services (on Windows)

• An application server can be used instead of a web server, or in addition to a web
server, to handle client requests for Java-based Content Server functions. Content
Server supports the following application server:

– Apache™ Tomcat Server

• Web browsers on client workstations. Content Server supports the following web
browsers. Some limitations may apply to specific browsers. Refer to the Content
Server Release Notes for details.

– Apple Safari™ (on OS X)

– Microsoft® Edge (on Windows)

8 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 2.1. About Content Server

– Mozilla® Firefox®
– Google Chrome™
• An external file system or other data storage system (optional, but
recommended). For example, OpenText™ Archive Center

This guide includes advice for configuring third-party components to work with
Content Server. Refer to the documentation for these products for complete setup
and configuration information.

2.1.2 Content Server Components

Content Server is designed to be multi-tiered, standards-based, and modular to
achieve maximum flexibility, scalability, and performance. This section describes
some of the important standards and modules used by Content Server.

Language Support and UTF-8 Character Encoding

Content Server employs the UTF-8 Unicode™ encoding standard. Unicode is an
international standard designed to allow text and symbols from all of the writing
scripts of the world to be consistently represented and manipulated by computers.
Unicode supports many languages equally well, regardless of the character set they
use.

When Content Server is installed, English is the default language. After installation,
you can allow users to change the language of the GUI by installing one or more
Content Server Language Packs.

In addition to U.S. English (the default), the Content Server GUI is available in:

• Arabic
• Catalan
• Simplified Chinese
• Dutch
• Finnish
• French
• German
• Italian
• Japanese
• Korean
• Kazakh
• Portuguese
• Russian
• Spanish

LLESCOR240100-IGD-EN-01 Installation Guide 9

Chapter 2 Design Your Extended ECM System

• Swedish
• Ukrainian

XML Support in Content Server

Content Server native XML support enables the system to exchange document
content, metadata, and other information with third-party systems that also support
XML. Because XML is an open standard, Content Server works with other
applications that understand XML, without using the specific APIs of either system.
Content Server incorporates XML in numerous areas.

• An XML parser and XSLT engine are part of the Content Server core. Several of
the features in Content Server are built on this powerful XML foundation.
• XML Import and Export functions are available for all Content Server object
types (including custom types) using a standard Content Server Document Type
Definition (DTD). This allows data to be exported and imported as XML,
including category and attribute information, version information, document
contents, and XSL/XSLT processing. For more information, see the OpenText
Content Server - XML Import and Export Guide (LLESCOR-PGD).
• Content Server indexes regions in XML documents automatically. To allow users
to search XML regions, you can add an XML DTD file and set the related Content
Server search regions to queryable. When you add an XML DTD file to Content
Server, Content Server analyzes the elements and attributes that the XML DTD
defines, and extracts XML regions based on those elements or attributes.
• An XML Interchange Step is available in Content Server Workflows. This step
allows the data in a work package to be exported as XML to an external system
using a URL. In addition, the XML Interchange Step can be configured to wait for
a response (in the form of XML data) from the external system. This functionality
makes it possible for processes that are external to Content Server to be
integrated into Content Server Workflows.
• Any external data source that can be represented in XML can be indexed by the
Content Server Index engine using an XML Activator that is included as a
standard component of the data flow architecture. This enables you to configure
the indexing process for data maintained outside of Content Server without
having to customize Content Server.

10 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 2.1. About Content Server

Content Server Extensibility

Content Server is extensible through configuration and customization. A number of
powerful developer tools allow developers to integrate existing applications with
Content Server and to extend Content Server’s capabilities.

Developer tools include:

Content Server SDK

The Content Server SDK includes:

• The Content Server IDE (CSIDE) Plug-in for Eclipse, which allows you to
program in OScript (a proprietary coding language used by Content Server).
• Content Web Services (CWS), which allows you to write programs that
interact with Content Server over SOAP. Web services are defined in Java, C#
and web service APIs are generated for the clients. Content Web Services is
installed by the Content Server installer and can be deployed on Microsoft
IIS using ASP.NET (WCF) or on a Java application server.
• The Content Server REST API, which allows you to interact with Content
Server using a RESTful interface.

Registered customers and partners can use the OpenText Developer Network
(https://knowledge.opentext.com/knowledge/cs.dll/Open/OTDN) to access code
samples, best practices, API documentation, and guidance.
OpenText™ WebReports
WebReports brings together content of all forms including documents, email,
workflow and databases, delivering management dashboards and integrated
reporting, and creating process-driven applications.
OpenText™ ActiveView
ActiveView allows you to configure simplified role-based interfaces that display
the information that is relevant to users and the actions that they need to
perform their work.
OpenText™ AppWorks
AppWorks is OpenText's enterprise application development and management
platform. In-depth information is available at https://developer.opentext.com.

LLESCOR240100-IGD-EN-01 Installation Guide 11

Chapter 2 Design Your Extended ECM System

Content Server Services

Content Server has two services:

• The Content Server service (llserver[.exe]) controls or directs all Content

Server functionality and serves all pages of the Content Server interface through
the web server.
• The Content Server Admin service (admserv[.exe]) handles the processes that
are associated with indexing and searching the Content Server database and the
memcached processes associated with Faceted Browsing.

Content Server Modules

Most of the functionality delivered by Content Server is contained in modules. Core
modules deliver basic functionality, such as document management; they are
installed and enabled by default. In addition, numerousoptional modules that deliver
a wide variety of additional functions are available from OpenText and third parties.

In many cases, organizations develop their own custom modules to expand Content
Server’s capabilities. Content Server’s modular architecture allows you to add
functionality without modifying the objects that are contained in other Content
Server modules, so you can add custom functionality to Content Server without
modifying OpenText's source code.

My Support (https://knowledge.opentext.com/) contains more information about

optional modules and other OpenText products.

Content Server Data Directories

When you upgrade Content Server by applying a Content Server Update, the
Update deletes the contents of most of the folders in the Content Server application
directory, and then replaces them with up-to-date application files. For this reason,
program data is stored in specific folders in the Content Server application directory.
There are two main directories where Content Server stores program data:

appdata
The <Content_Server_home>\appdata\ stores persistent data written by Content
Server modules. Data stored in this folder is managed by Content Server. It will
remain in place when an Update is applied and any time Content Server is
restarted.

temp
The <Content_Server_home>\temp\ stores temporary data written by Content
Server modules. Data stored in this folder does not remain in place when an
Update is applied or Content Server is restarted.

In addition to the above folders, there is a special location for storing files used in
local customizations.

12 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 2.2. Content Server Architecture

The Support Asset Volume

Many Content Server installations include customizations such as Custom
Views, Appearances, Perspectives, and custom applications. The files that
support these customizations can be stored in the Support Asset Volume, a
special Volume with user interface controls that allow you to add, delete,
modify, track, and version the files that support your local customizations. By
default, the Support Asset Volume stores its files in the <Content_Server_home>
\appdata\supportasset\ but you can configure the location of this directory.
Files in the Support Asset Volume remain in place when an Update is applied
and any time Content Server is restarted.

2.2 Content Server Architecture

Content Server uses a three-tiered architecture that comprises an Access Tier, an
Application Tier, and a Data Tier.

2.2.1 Access Tier

The Access Tier provides a single point of access to content, legacy applications, and
structured information. It is an extensible environment that supports many standard
web browsers, allowing anyone with authorization to access your Content Server
intranet or extranet.

Content Server can handle web client transactions using CGI, a Java servlet, or ISAPI
(Internet Server API, an API for Microsoft Internet Information Services web server).

The Secure Sockets Layer (SSL) protocol can be used to encrypt data transmitted
between Content Server and the browser.

Desktop applications can also interact with Content Server. For example, OpenText
Enterprise Connect is an optional module that enables you to access Content Server
using Windows Explorer.

2.2.2 Application Tier

The Application Tier provides a high level of performance because of its multi-
threaded and highly scalable architecture. This tier is made up of Content Server's
services, including document and knowledge management, project team
collaboration, information retrieval and search, enterprise group scheduling, and
business process automation.

Programmers can access and customize these services using Content Web Services
and the Content Server REST API. Customers and partners can use the OpenText™
Content Server SDK to add new features and capabilities to Content Server.
Optional modules can be added or removed through Content Server's
administration facilities.

Content Server is developed in a proprietary coding language called OScript and

uses proprietary APIs written in C++. Content Web Services APIs expose all of

LLESCOR240100-IGD-EN-01 Installation Guide 13

Chapter 2 Design Your Extended ECM System

Content Server's functions and can be deployed on IIS using ASP.NET (WCF) or on
a Java application server. CSIDE (Content Server Integrated Development
Environment) and the Content Server SDK provide a complete development
environment for Content Server.

2.2.3 Data Tier

The Data Tier consists of the Content Server database, the external file system, the
Enterprise index (a searchable index of all the data that is stored in Content Server),
and any additional search indexes. It supports the most popular relational databases
and file-storage systems. The system is open-architected, allowing you to maximize
current and future technology investments. Content Server seamlessly supports
most desktop applications and file formats. It also brings together corporate data
from ERP applications, such as SAP®, IBM® Notes® repositories, and other
enterprise business systems.

2.3 Architectural Options

Because it is designed to offer maximum flexibility, a production Content Server
system presents you with a broad range of options when designing your system.

2.3.1 Multihost Architectures

In most cases, a production Content Server system is rolled out in phases,
encompassing more users and more workload with each successive phase. Content
Server is designed to be a highly scalable solution: you can extend its capacity and
its capabilities in cost-effective increments, with minimal impact on the existing
system or disruption of service.

For test and development systems, all components of a three-tier architecture may
reside on a single server, as shown in Figure 2-2. This single-server architecture
(sometimes called a monolithic architecture) may be suitable for small pilot programs,
but is not commonly recommended for even small production deployments.

14 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 2.3. Architectural Options

Figure 2-2: Monolithic Content Server Architecture

Scaling Content Server to meet increased demand is a matter of adding resources. It

is never necessary to restart from scratch or rebuild the Content Server system.
Content Server is scalable both vertically and horizontally.

• Vertical scaling refers to the use of more than one instance of Content Server on a
single computer. It is achieved using more powerful servers or by adding more
processors and memory.

• Horizontal scaling refers to the addition of computers running Content Server. It is

achieved by distributing processes among more servers.

As the number of users increase, the Data Tier begins to require more resources to
provide adequate performance. The standard scaling path in this case is to move
Content Server components, such as the database server, to a dedicated computer.

The database, external file store, and search indexes can each be moved to one or
more dedicated servers, possibly located on a storage area network or SAN. (A SAN
is a dedicated subnetwork that connects storage devices and servers in a pool,
providing consolidated storage and storage management.)

Note: If you install the Content Server database on a separate computer, you
must install the necessary RDBMS client software (transaction handlers) on the
Content Server computer. See the documentation supplied by your database
software vendor and also the information in “Install a Database Server”
on page 25.

As a system grows further, the Admin server (which handles Content Server
indexing and search infrastructure) may require more resources. The next step of the
scaling path is to move the Admin server and its managed processes to a dedicated
computer, and to add additional Admin servers.

LLESCOR240100-IGD-EN-01 Installation Guide 15

Chapter 2 Design Your Extended ECM System

Moving the Admin server to a dedicated computer also frees up resources on the
user-facing (or Front-End) Content Server that can then be dedicated to operations
such as user log-ins, page serves, file uploads and downloads, and so on.

For optimum performance and scalability, OpenText recommends that you design
your Content Server system with multiple Admin servers running on dedicated
computers, with each handling particular indexing and searching processes. As with
the Enterprise index, you can place other indexes (such as the Directory Walker and
the Index Engine) on one or more additional computers. In such configurations, any
computer that runs the Content Server service is called a Content Server host
computer, the first Admin server is known as the primary Admin server, and each
additional Admin server is called an Additional Admin server. See OpenText Content
Server Admin Help - Search Administration (LLESWBS-H-AGD).

Information on scaling your Content Server by adding additional Admin servers

and Content Server hosts is covered in this guide after the basic installation
instructions, in “Install Additional Instances of Extended ECM“ on page 155

From this point, further scaling is accomplished by adding multiple Content Server
instances and using a network load balancer.

Content Server Cluster Architecture

In order to provide a highly available service to a large number of users, you can
deploy Content Server in a configuration that employs a combination of network
load balancing and operating system cluster services. Multiple Content Server Front-
End servers are deployed with a load balancer to provide high availability end-user
services.

An operating system cluster provides high availability database services, and is

typically also used to cluster indexing and search functions handled by the Content
Server Admin server. While Content Server does not support operating system
clustering, it can be used for database servers to provide high availability.

OpenText Content Server Remote Deployment Options

Content Server is deployed as a centralized repository, with all users accessing a
single Content Server system—that is, all Content Server users log onto and use a
common Content Server. When a location is physically separated from your Content
Server installation and has a low-bandwidth connection, users can experience slow
response times.

OpenText provides two options for remote deployment:

• Content Server Remote Cache is a document-caching solution that caches local

copies of documents that are managed by Content Server. This option uses a
proxy server to maintain a document cache at the remote site. However, this
option is highly dependent on the primary installation of Content Server to
execute essential tasks such as authentication, permissions checking, search, and
auditing.

16 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 2.3. Architectural Options

Note: Content Server Remote Cache is an optional module that is sold

separately. For more information, contact your OpenText sales consultant.
• Content Server Syndication is a distributed solution for remote sites that deploys
as a global model with multiple, remote site installations. Each remote site will be
a full Content Server installation capable of coordinating its operation will all
other sites.
Content Server Syndication is an integral part of core Content Server. It must be
configured during the installation of your primary instance of Content Server.

Important
If you intend setting up a Syndication solution, you must install your first
instance of Content Server by following the instructions found in
“Appendix B – Installing Content Server as a Syndication Environment“
on page 175. See also OpenText Content Server - Syndication Administration
Guide (LLESQDS-AGD)

2.3.2 Virtualization Platforms

You can install Content Server on supported versions of Linux and Windows, which
you can install on a physical or virtual host computer. If you install on a virtual host
computer, you should select a virtualization platform that is intended for production
systems and that is supported by the server operating system vendor.

Bear in mind that, for a given level of performance, Content Server requires at least
the same amount of resources in a virtual environment as it would in a physical
environment. When you virtualize a physical environment, additional computing
resources may be required to obtain the same level of performance. Assign static
(reserved) resources to the Content Server virtual machine. The use of dynamic
resources within the Content Server virtual machine is not supported.

2.3.3 Internal and External Document Storage

Content Server uses both internal (database) and external (file system) Storage
Providers for files that users upload and system files that are created during its
normal operation.

• With internal storage, Content Server stores both an item (such as a text file) and
its metadata (such as the file’s creation date) in a database. Content Server creates
an Internal Storage Provider when it is installed.
• With external storage, only the metadata is stored in the database; the file is
stored on an external file system, or on OpenText™ Archive Center. The use of
an External Storage Provider is optional, but recommended. External document
storage provides faster performance than internal document storage.

Production implementations of Content Server normally use both types of storage.

Storage Provider rules determine which storage provider is responsible for storing
any given item. OpenText recommends that you use external storage for documents

LLESCOR240100-IGD-EN-01 Installation Guide 17

Chapter 2 Design Your Extended ECM System

and emails, and internal storage for system objects, such as forms, category
definitions, and workflow maps.

Note: When using external storage, Content Server assigns files a numeric file
name. For example, if a user adds a file called ExpenseReport.xls, its name in
the external storage folder may become 2934856.dat. Content Server uses a
numbering algorithm so that it can keep track of multiple versions of the same
file.

Implications for Backup and Recovery Strategy

Using only internal document storage can simplify your backup and recovery
strategy. Having all of your content and metadata stored in the database allows you
to use the tools of your database manager to back up Content Server. Each database
server supported by Content Server has sophisticated database backup and recovery
tools that enable you to generate backups without taking the database offline.
However, using only internal storage is typically not suitable for a production
implementation of Content Server.

When you enable external storage, you need to take backups of both your database
and your file store and ensure that the backups are synchronized. (If they are not,
the database backup may contain metadata for documents that do not exist on the
external file store backup, or vice-versa.) You can ensure that they are synchronized
by taking Content Server offline when you back up the database and external
document store. This prevents updates to Content Server during your backup
process and ensures that the content in your file store backup is synchronized with
the metadata in your Content Server database backup.

However, taking the Content Server database offline may not be a viable option for
global organizations that operate 24 hours a day. In this case, more complex backup
and recovery strategies are necessary to ensure that backups of the external
document store and database, taken while Content Server is online, are in synch
with each other.

Setting Up an External Document Store

During the installation of Content Server on the operating system, you can enable
external document storage and specify the physical path of the external document
store. Before you do, several preparatory steps are necessary:

• You must create the folder that you want to use as the external document store
before you create the Content Server database. Content Server does not create the
folder if it does not exist.
• If the external document storage folder is not on the Content Server computer,
you must map or mount the folder on the Content Server computer. For Linux,
use an NFS mount. For Windows, use an UNC path. (Do not map a drive.)
• A remote external document store on Windows must be owned by the user who
runs Content Server. To achieve this, you need to create a user with the same
name, password, and privileges on both the Content Server computer and the

18 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 2.4. Best Practices for System Design

remote computer where the external document store is located. Content Server
and Admin server need to run as this user, and the document store folder on the
additional computer must be owned by this user. A good practice is to set up a
domain user account for this purpose. For more information about the privileges
that the Windows user must have, see “Create a Windows User” on page 24.
• After you create and map or mount the external document store folder on an
additional computer, test whether you can access and write to it by connecting to
it from the Content Server computer as the operating-system user that you
created to run Content Server. If you encounter permission or ownership
problems when performing this test, correct the problems before you create the
Content Server database.

2.4 Best Practices for System Design

The following sections outline some issues to consider when you design your
system.

To determine the architecture and configuration options that best suit your needs,
consider the following factors:

• The number of named users that will use Content Server

• The anticipated transaction rate
• The amount of data that needs to be stored in the Content Server database
• The presence of legacy systems or applications that need to integrate with
Content Server
• The Content Server hardware environment, including:

– The state of the existing network architecture

– The CPU speed and memory capacity of the various servers
– System storage capacity, speed, and configuration
• Security best practices

Tip: OpenText Professional Services can help you with specific system-design
issues.

LLESCOR240100-IGD-EN-01 Installation Guide 19

Chapter 2 Design Your Extended ECM System

2.4.1 Deployment Recommendations

To deploy Content Server optimally, you must consider a number of factors,
including performance, security, and file storage and backup strategies.

Performance Recommendations
Different Content Server system architectures support different transaction rates,
which are expressed as transactions per second (TPS). In general, a capacity of one
transaction per second is sufficient to support 500 named users and 50 active users at
a rate of one transaction per user per second.

The following list contains some of the most basic and widely applicable tips that
will help achieve this level of performance:

• The key bottlenecks to performance of a Content Server system are the CPU
power allocated to Content Server and to the database server, the amount of
RAM available, and network bandwidth and latency. These are the best
performance factors in which to invest.
• Content Server installs with a default number of eight threads, but you can adjust
this number to suit your system on the Configure Server Parameters
administration page. The optimum number of threads depends on the
environment in which the Content Server instance is running (such as number
and speed of CPUs, amount of physical memory, speed of network connection,
and whether disks are local or accessed over the network). It also depends on the
usage profile for your Content Server instance (such as what types of requests are
made and the frequencies at which each of those types of requests is made).
You can determine an optimal number of threads for your system to run by
closely monitoring the system and making adjustments as necessary. The
Content Server Monitoring Agent is a useful tool for performing a performance
analysis in real time, while the Content Server Performance Analyzer is suited for
performance analysis using Content Server log files collected over a period of
time. For more information about these tools, see My Support (https://
knowledge.opentext.com/).
• When installing Content Server, it is usually best to run the database server,
Content Server, and the Admin server each on its own, dedicated computer.
Most large organizations deploy Content Server using a load-balanced cluster
architecture. See “Content Server Architecture” on page 13.
• OpenText recommends that you consistently monitor your database, your
network, and your web server with their own supplied monitoring tools. This is
especially useful when you first roll out your system. As you monitor the system
and notice peaks in usage, you can use Content Server's audit trail, logs, and
LiveReports to determine what was happening at the time the peaks occurred.
Then, you can make any necessary adjustments.

20 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 2.4. Best Practices for System Design

Database Recommendations
The Content Server database must be stored in a relational database management
system (RDBMS) that is listed as supported in the Content Server Release Notes. Your
RDBMS must be installed for UTF-8 compliance.

Content Server's database schema is normalized, which means that the schema has
been designed to reduce the chance of having multiple versions of the same data.
Indexes are provided out of the box on the columns that Content Server uses in its
standard operations. In some cases, however, it may be helpful to build indexes on
additional database table columns, which will speed up the retrieval of information
from SELECT statements (at the cost of increasing overhead when new information is
added to the table because both the table and the index will have to be updated).

OpenText recommends that you have an experienced database administrator tune

your database to achieve optimum performance, using the monitoring and
performance tools provided by the database vendor. Common database tuning tasks
include:

• Monitoring disk usage to achieve optimum results

• Determining if more memory is needed for caching data tables
• Adjusting temporary tablespace tables and buffers
• Splitting tables, logs, and indexes across multiple disks and controllers

Security Recommendations
For most customers, maintaining the security of your organization's Content Server
system is a primary concern. While there is no single correct way to secure a Content
Server system, the following are some general recommendations by OpenText:

• OpenText recommends that you configure your web server to serve only HTTPS,
refusing incoming HTTP connections, in order to employ data encryption and
client authentication safeguards.
• OpenText strongly recommends that you restrict read permissions on the
<Content_Server_Home>/config/ folder as much as possible. Ideally, the only
user with read access should be the operating-system user created specifically for
the Content Server and, (if applicable), the Admin server. Also, make sure to
disable browsing the <Content_Server_Home>/config/ folder through the web
server running on the Content Server computer.

For detailed recommendations on securing your Content Server installation, refer to

the Content Server Application Security Hardening Guide, available in the Champion
Toolkit (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
Champion_Toolkit) area of My Support.

LLESCOR240100-IGD-EN-01 Installation Guide 21

Chapter 3

Prepare to Install Extended ECM

Before you can install Content Server, prepare the environment for installation.
Content Server must be installed on a supported operating system, and requires the
presence of a supported web or application server, and a supported database. This
information in this chapter helps you to prepare for installing Content Server by
providing recommendations on the installation and configuration of web servers,
database servers, your operating system, and client web browsers.

3.1 Prepare the Operating System

In preparation for installing Content Server, ensure that you do not use a distributed
file system for storing the Content Server search index. Content Server’s search
system components require accurate file locking to function correctly. Distributed
File Systems are not suitable for storing the search index. In particular, Microsoft
DFS is known to fail for search.

In addition, exclude the Content Server application folders from antivirus scanning,
and create an operating system user to run Content Server.

3.1.1 Exclude Content Server Folders from Antivirus

Scanning
Configure your antivirus software to exclude the <Content_Server_home> folder and
subfolders and the folders that contain the Content Server search index files.

3.1.2 Create an Operating System User

Content Server must run as a particular Linux or Windows user. OpenText
recommends that you create an operating system user to run Content Server and the
Admin server.

Note: When dealing with multiple instances of Content Server (in a Content
Server cluster environment, for example) you may want to create additional
users to manage certain functions, such as performing searches or managing
system administrative duties.

The user that runs the Content Server services must have at least Modify permission
for the <Content_Server_home> folder, and for any other folders that Content Server
accesses, including (if applicable), the index folder, external file store folder, and
upload folder. The exact folders and permissions required depend on your specific
environment.

LLESCOR240100-IGD-EN-01 Installation Guide 23

Chapter 3 Prepare to Install Extended ECM

Create a Windows User

In a single-computer Content Server configuration, it is not necessary to create a
Windows user to run Content Server and the Admin server but, in a clustered
environment, OpenText recommends that you create a Windows user to run the
Content Server and Content Server Admin services on each of your Content Server
instances.

Create a Windows User for the Content Server Services

You should use the same Windows user to run all Content Server services on the
Content Server computer and each additional computer. Also, if you are using an
external document store on an additional computer, use the same user on that
computer to own the external document folder.

On a Content Server computer, you can use the same user for Content Server and
the web server, or you can use different users. (It is not necessary to create a
Windows user for Microsoft Internet Information Services, because this is done
automatically during the installation of Microsoft Internet Information Services.)

Any Windows user that you create to run the Content Server and the web server
must:

• Be a member of the Administrators group

• Have the Log On As A Service right
• Have a password set to never expire

Record the name and password of the Windows user that you create for Content
Server on Table 10-7: “Content Server Installation Worksheet” on page 173.

Create a Linux User

Create Linux user accounts with appropriate profiles to run the web server and
Content Server. You can use the same user for all servers or use one user to run the
web server and another to run Content Server. If you choose to use two different
users, they must be in the same group.

Note: If you do not use the same user to run the web server as you use to run
the Content Server, you must make sure that the user that runs the web server
has Write permissions for the Content Server directory tree.

To create a Linux user account, log on to the Content Server computer as the
superuser root.

Tip: Use the same user name and password to run all servers on the Content
Server computer and each additional computer. The servers run as the user
that invoked them, so you must always start the servers as the user that you
created for them.

24 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 3.2. Install a Database Server

OpenText recommends that you run the Content Server installation logged on as the
user that runs Content Server. The user that runs the installation of Content Server
should be able to create and modify the Landscape Directory, if you require it in
your environment to enable integration with other OpenText products. For more
information, see “The Landscape Directory” on page 69.

Record the name and password of the Linux user that you create for Content Server
on Table 10-7: “Content Server Installation Worksheet” on page 173.

3.2 Install a Database Server

Content Server uses third-party database software to create and manage the Content
Server database. You can use supported versions of SAP HANA, Oracle Database,
PostgreSQL, or Microsoft SQL Server. The Content Server database is not required to
run on the same operating system as Content Server.

Note: The supported database clients are not necessarily supported on every
operating system supported by Content Server. Refer to the Content Server
Release Notes for detailed information on supported database servers and
database clients.

For optimum performance and scalability, OpenText recommends that you install
the database software on its own computer, and install database client software on
the Content Server computer so that Content Server can communicate with the
database. Be sure to synchronize the system time on the Content Server and the
Content Server database host computers.

This section of the Content Server Installation Guide discusses the database
installation options that Content Server requires to work with your database
software and configuration. For information about how to install and configure your
database software, refer to the documentation supplied by your database software
vendor.

Tip: Additional documents that list best practices and provide advice on
configuring your Content Server database for best performance are available in
the Champion Toolkit (https://knowledge.opentext.com/go/Champion_Toolkit)
on OpenText My Support.

Choose the installation guidelines that apply to your supported database platform.

• “SAP HANA Installation Guidelines” on page 26

• “Oracle Database Installation Guidelines” on page 26
• “Microsoft SQL Server Installation Guidelines” on page 28
• “PostgreSQL Installation Guidelines” on page 30

LLESCOR240100-IGD-EN-01 Installation Guide 25

Chapter 3 Prepare to Install Extended ECM

3.2.1 SAP HANA Installation Guidelines

To connect to SAP HANA, ensure that you install both the SAP HANA database
client and the SAP HANA ODBC driver.

3.2.2 Oracle Database Installation Guidelines

Note the following points when you install and configure Oracle Database:

• During installation, selecting the Typical Configuration option results in an

Oracle Database configuration that is compatible with Content Server.
• Create the Oracle database with a block size of at least 8K.

Tip: If the block size is too small, a maximum key length exceeded error
message appears during creation of the Content Server database.
• If Oracle Database is not installed on the Content Server host computer, install an
Oracle client on the Content Server computer so that it can communicate with
Oracle Database. Ensure that the client:

– is compatible with your version of Oracle Database

– is a 64-bit client
– communicates using UTF-8 encoding
• On Windows, Set the following Oracle Database services to start automatically
whenever the database computer is restarted.

– OracleStartORCL

– OracleServiceORCL

– OracleTNSListener

• Configure Content Server for UTF-8 character encoding in an Oracle database.

Ensure that the character encoding setting in the opentext.ini file is:

– Microsoft Windows
ENV_NLS_LANG=.AL32UTF8 (not ENV_NLS_LANG=.UTF8)

– Linux
NLS_LANG=.AL32UTF8, (not NLS_LANG=.UTF8)

An incorrect character encoding setting can cause unexpected characters to

appear in documents stored in Content Server.
• In Oracle 12C and later, you can create a Container Database (CDB), which
contains one or more Pluggable Databases (PDB), which have local users. If you
install Oracle as a CDB, the Content Server database must run as a PDB.

26 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 3.2. Install a Database Server

Important
In an Oracle 12C database or later, do not use a common user as the
Content Server database user.
• To ensure that the sort order in the Oracle database is correct for your language,
change the value of ENV_NLS_SORT (on Windows) or NLS_SORT (on Linux) in the
opentext.ini file from Generic_M to an appropriate value. Be sure to make the
same change within Oracle too.
For example, set ENV_NLS_SORT='German' for a German implementation of
Content Server.
• By default, Oracle is case-sensitive in its character comparisons and ordering.
Content Server works well with the Oracle default settings, but if you want to
configure Oracle for case-insensitive character comparisons and ordering,
configure Oracle with the following NLS settings.
Character comparison
NLS_COMP=LINGUISTIC

Case-insensitive sorting
NLS_SORT=BINARY_CI, NLS_SORT=GENERIC_M_CI, or any other Oracle case-
insensitive linguistic definition

Important
To force unique case-insensitive names in a folder in Content Server when
using an Oracle database it is necessary to have both NLS_COMP set to
LINGUISTIC and NLS_SORT set to a case-insensitive linguistic definition. It is
not sufficient to set NLS_SORT to a case-insensitive linguistic definition
without setting NLS_COMP to LINGUISTIC.

Alternatively, you can configure an Oracle Content Server database for case-
insensitivity by entering the following settings in the opentext.ini configuration
file, under the [Lang_<xx_XX>] section (where<xx_XX> is your locale, for
example en_US):

– Microsoft Windows
ENV_NLS_COMP=LINGUISTIC

ENV_NLS_SORT=BINARY_CI, ENV_NLS_SORT=GENERIC_M_CI or any other Oracle

case-insensitive linguistic definition
– Linux
NLS_COMP=LINGUISTIC

NLS_SORT=BINARY_CI, NLS_SORT=GENERIC_M_CI or any other Oracle case-

insensitive linguistic definition
• Content Server does not support Oracle database compression. Disable Oracle
compression before installing or upgrading Content Server.
• Oracle recommends that you change the default passwords of the internal, sys,
and system users immediately following installation.

LLESCOR240100-IGD-EN-01 Installation Guide 27

Chapter 3 Prepare to Install Extended ECM

• Record the password for the system user on Table 10-2: “Oracle Database
Worksheet” on page 170. You will need the system user and password, and the
database SID, when you create the Content Server database.
• Refer to the Content Server Release Notes for information about any Oracle
software patches that may be required to use your version of Oracle Database or
client software with Content Server. If patches are required, additional
information and support may be available on My Support (https://
knowledge.opentext.com/).
• For additional Oracle Database configuration recommendations, see the Best
Practices Oracle for OpenText Content Server Champion Toolkit document available
on My Support (https://knowledge.opentext.com/)

3.2.3 Microsoft SQL Server Installation Guidelines

Note the following points when you install and configure Microsoft SQL Server:

Collation
Content Server does not require a specific collation. You can select a collation
that is appropriate for your organization. For best compatibility with other
OpenText products, OpenText recommends that you choose a collation that is
case-sensitive and accent-sensitive, and that the Content Server database uses
the database server default collation, so that its collation is the same one used by
system databases, for example tempdb.
Compatibility Level
Use the default (maximum) compatibility level for your version of Microsoft
SQL Server.
Legacy Cardinality Estimator
The Legacy Cardinality Estimator was introduced in Microsoft SQL Server 2014.
OpenText recommends that you activate it to improve Content Server database
performance. To activate the Legacy Cardinality Estimator, run the following
SQL statement:
ALTER DATABASE SCOPED CONFIGURATION

SET LEGACY_CARDINALITY_ESTIMATION = ON;

When you follow the instructions in this guide to create a SQL Server database
for Content Server, LEGACY_CARDINALITY_ESTIMATION is automatically set to ON
in the Content Server database.
Master database
Record the name and collation of the Microsoft SQL Server master database (by
default, it is master) on Table 10-4: “Microsoft SQL Server Worksheet (Windows
only)” on page 171. The master database is the template, and determines the
collation, for any database that you create, including the Content Server
database.

28 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 3.2. Install a Database Server

System user
During the installation, the system user name and password do not appear. By
default, the system user name is sa. Record this information on Table 10-4:
“Microsoft SQL Server Worksheet (Windows only)” on page 171.
Verify before installing Content Server
After you complete the installation, test the Microsoft SQL Server installation, as
described in the Microsoft SQL Server documentation.
Microsoft SQL Server Client Software
If Microsoft SQL Server and Content Server are not installed on the same server,
Microsoft SQL Server client software is required on the Content Server
computer. If you use the Content Server installer, you do not need to take any
action. The Content Server installer automatically installs the Microsoft SQL
Server client software.
If you install the Microsoft SQL Server client software manually, refer to the
Content Server Release Notes for the supported version. OpenText recommends
that you install the optional ODBC Driver for SQL Server SDK when you
install the Microsoft SQL Server ODBC driver, so that Bulk Copy Protocol (BCP)
is supported.
Isolation Levels
Content Server requires the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_
ISOLATION SQL Server isolation levels in the Content Server database.

When you follow the instructions in this guide to create a SQL Server database
for Content Server, the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_
ISOLATION SQL Server isolation levels are set automatically in the Content
Server database.

Note: You cannot use Content Server’s built-in database utility to create an
Azure SQL database. You must enable the READ_COMMITTED_SNAPSHOT and
ALLOW_SNAPSHOT_ISOLATION SQL Server isolation levels manually when
you create a Content Server database on Azure SQL.

To enable these settings manually on an existing database, complete the

following steps.

To set the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_

ISOLATION SQL Server isolation levels, run the following commands:

1. Open Microsoft® SQL Server® Management Studio.

2. Verify that no users or processes are accessing the Content Server database.

3. Run the following commands:

• ALTER DATABASE <DB_Name> SET ALLOW_SNAPSHOT_ISOLATION ON

• ALTER DATABASE <DB_Name> SET READ_COMMITTED_SNAPSHOT ON

LLESCOR240100-IGD-EN-01 Installation Guide 29

Chapter 3 Prepare to Install Extended ECM

Microsoft SQL Server on Microsoft® Azure®

If you deploy Microsoft SQL Server on Microsoft Azure, follow the guidelines in
“Microsoft SQL Server Installation Guidelines” on page 28 and note the following
points:

Manual Database Creation

Typically OpenText recommends that you use the tools available in Content
Server to create the Content Server database and database user, but on Azure
SQL, you must create them on the Azure Portal. After you have created the
database and user, you can use Content Server’s built-in tools to create the
database schema. For more information, see “Create an Azure SQL Content
Server Database” on page 85.

Geographic Location
Microsoft recommends that you select a server location that is as close as
possible to your Content Server deployment.

SQL Server Management Studio

If you use SQL Server Management Studio to manage a SQL Server database
deployed on Azure, you must use SQL Server Management Studio 2016 or later.
Earlier versions of SQL Server Management Studio do not have the capability to
manage Azure resources.

Note: Not all features are available in SQL Server Management Studio for
SQL Server deployed on Azure. Some features are available only on the
Microsoft Azure Portal.

3.2.4 PostgreSQL Installation Guidelines

Note the following points when you install and configure PostgreSQL:

• Content Server requires the pg_trgm, pgcrypto, and unaccent extensions in the
Content Server database.

Tip: To verify whether or not your PostgreSQL database has the pg_trgm,
pgcrypto, and unaccent extensions, log on to the Content Server database
using psql, and run the following command:

– SELECT * FROM pg_extension;

The output that is returned should include rows for pg_trgm, pgcrypto, and
unaccent.

When you follow the instructions in this guide to create a PostgreSQL database
for Content Server, the pg_trgm, pgcrypto, and unaccent extensions are installed
automatically. To enable these extensions manually on an existing database,
complete the following steps.

30 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 3.3. Set Up Client Web Browsers

To install the pg_trgm, pgcrypto, and unaccent extensions:

1. Open the psql command prompt and log onto the Content Server database
as a superuser.

a. Open a terminal window and change directory to the bin subfolder of

the PostgreSQL application directory.
b. Enter ./psql -U <PostgreSQL_superuser> <Content_Server_
database>. For example enter ./psql -U postgres csdb
c. Enter the password of the PostgreSQL superuser.
2. Run the following commands:

– CREATE EXTENSION IF NOT EXISTS pg_trgm SCHEMA public;

– CREATE EXTENSION IF NOT EXISTS pgcrypto SCHEMA public;
– CREATE EXTENSION IF NOT EXISTS unaccent SCHEMA public;
3. Exit psql by typing \q

Tip: To ensure that any database that you create in the future has the pg_
trgm, pgcrypto, and unaccent extensions enabled, repeat the above steps on
the template1 database.

3.3 Set Up Client Web Browsers

Each Content Server user and the Content Server Administrator needs a supported
web browser on their computer.

Content Server typically does not require custom configuration settings for web
browsers. If you are using the latest version of a supported browser, you may be
able to use Content Server without changing any default browser settings. However,
if you have special requirements, you may need to make some configuration
changes. If you want to display and enter data in a language different from your
default system language, you must install fonts and input methods for the language.
For example, to view and edit Japanese documents on English Windows, you should
install Japanese fonts and input methods.

You may also wish to tailor your browser’s behavior if Content Server does not open
documents in the manner you expect. See Table 3-1: “Common Issues When
Opening Documents from Content Server” on page 32 for information about
configuring browsers to work with Content Server.

Note: When making configuration changes to web browsers, refer to the

appropriate vendor documentation for specific instructions.

Web browsers on all client computers need to meet the following requirements for
use with Content Server:

• Content Server uses an encrypted cookie to store connection information. This

cookie is discarded when users exit their web browsers or when they log out of

LLESCOR240100-IGD-EN-01 Installation Guide 31

Chapter 3 Prepare to Install Extended ECM

Content Server. To connect to Content Server, web browsers must be configured

to accept cookies.
• To open documents, web browsers must be configured to behave in a certain
manner for specified MIME types. See “Configure Web Browser Behavior for
Opening Documents” on page 32.
• When the Enable Time Zone Offset option is selected, the web browser's time
and time zone settings must be configured correctly. See OpenText Content Server
Admin Help - System Administration (LLESWBA-H-AGD)

3.3.1 Configure Web Browser Behavior for Opening

Documents
When a user adds a document to Content Server, the web browser sends a MIME
type to be stored with the document. The MIME type defines the type of file. When a
user opens a document, Content Server sends the document's MIME type to the web
browser, along with the file. The web browser uses the computer's MIME types
settings to determine what to do with documents that users open and which MIME
type to send when adding a document to Content Server. Users must check the web
browser MIME type settings to verify that the proper settings exist for each type of
document that is used. The settings also verify that the MIME types specify the
proper action to perform when documents are opened, such as save to disk, open
with an external application, or prompt to save or open.

How MIME type options are set depends on the web browser version. Microsoft
Internet Explorer and Mozilla Firefox include an extensive set of default settings,
which you can modify as required. OpenText recommends that users open files of
the different types they use and note the default behavior. To change the default
behavior, users can adjust either their web browser settings (Mozilla Firefox) or their
operating system settings (Microsoft Internet Explorer). The following table
describes common issues when opening documents from Content Server.

Table 3-1: Common Issues When Opening Documents from Content Server

Issue ... This happens when ...

When I attempt to open a document, it doesn't File-handling options are set to always ask you
open. A dialog box appears and asks me what I how to handle the file, rather than to perform
want to do with the file. an action by default.
I do not want to open the document. I just want File-handling options are set to automatically
to save the file on my desktop. launch an application and open the file, rather
than to prompt for an action.
When I open this kind of document, it always Microsoft Internet Explorer and certain file-
opens in my web browser, not in the native handling settings are configured to do a quick
application. view or to browse in the same window.

32 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 3.3. Set Up Client Web Browsers

Issue ... This happens when ...

When I open this kind of document, my web You are using an older version of Microsoft
browser shows me an unusual version of the Internet Explorer. Make sure that you have a
Content Server Log-in page. supported version of the Microsoft Internet
Explorer web browser.
People complain that they have problems You may be adding files whose MIME type
opening the documents that I add. settings are incorrect or nonexistent.

Modify Web Browser Behavior

OpenText assumes you know how to add or modify MIME types for common web
browsers. Refer to the vendor documentation for instructions.

LLESCOR240100-IGD-EN-01 Installation Guide 33

Chapter 4

Configure the Web Server to Run Extended ECM

Before you can start Content Server, you must configure the Content Server web or
application server to work with Content Server.

You can configure Content Server to handle web client transactions using:

• CGI, with any supported web server

• ISAPI with Microsoft Internet Information Services
• a Java Servlet in combination with any supported application server

Note: The steps provided in this chapter are the minimum necessary to allow a
web or application server to run Content Server. They are not comprehensive
instructions on configuring your web or application server to run securely and
optimally in your environment.

4.1 Web Server and Application Server

Configuration
This section contains general recommendations on how to configure your web
server or application server to run Content Server. Because the recommendations are
general, refer to the documentation for your specific web server or application server
for instructions on implementing the recommendations.

4.1.1 Configure HTTP Compression Settings for Smart View

To improve performance of Content Server Smart View, OpenText recommends that
you enable compression on your web server or application server. Compressing
server responses improves the performance of Content Server Smart View,
especially on networks where latency is a significant factor.

In your web server configuration, you should ensure that the following is set:

• Static compression of text files in the <Content_Server_home>/support/

directory, including text/*, application/javascript, and image/svg+xml.
• Dynamic compression of REST API responses. Ensure that application/json is
enabled.

After you have enabled and configured compression, you can verify that it is
working properly by opening the Content Server Smart View landing page and
inspecting the responses. Take note of the responses for /app, *.js, *.css, *.svg,
and /api.

LLESCOR240100-IGD-EN-01 Installation Guide 35

Chapter 4 Configure the Web Server to Run Extended ECM

Requests sent by the browser should include in the header Accept-Encoding: gzip,
deflate, sdch (and possibly other algorithms).

Responses received by the browser should include in the header Content-Encoding:

gzip (and possibly other algorithms).

Tip: If, after you make the changes to HTTP compression, you see that the
requests and responses are not compressed, it is likely the effect of a network
proxy that is modifying the requests and responses and preventing the
compression. If so, refer to your proxy documentation to determine how to
configure it to retain the compression.

4.2 Configure a Web Server to Run Content Server

To deploy Content Server on a supported web server, create mappings (virtual
directory aliases) for Content Server's <Content_Server_Home>/cgi/, <Content_
Server_Home>/support/, and <Content_Server_Home>/appData/supportasset/
folders on your web server.

You can verify the folders that you need to map by running a trial installation of
Content Server:

• On Windows installations of Content Server, the installer produces a mappings.

tbl file that contains virtual folder mappings for your web server. It is located in
the root of the Content Server installation directory (C:\OPENTEXT\, by default ).
• For Linux versions of Content Server, the URL Prefix mappings are written to the
screen at the end of the Content Server installation.

Note: Your web server should have:

• Read permission to the <Content_Server_Home>/support/ directory.

• Read, Run, and Execute permissions to the <Content_Server_Home>/cgi/
directory.

4.2.1 Configure Microsoft Internet Information Services to

Run Content Server
To prepare to use Microsoft Internet Information Services to run Content Server,
review the information in this section and set any configurations that are required
for your deployment of Content Server.

Map Content Server virtual directories in Microsoft Internet Information Services

This step is performed automatically by the Content Server Windows installer,
so it is generally not necessary to do this manually. To perform the steps
manually, follow the instructions at “Prepare Microsoft Internet Information
Services to Run Content Server” on page 37.

36 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 4.2. Configure a Web Server to Run Content Server

Configure IIS Request Filtering for use with Content Server

This step is performed automatically by the Content Server Windows installer,
so it is generally not necessary to do this manually. To perform the steps
manually, follow the instructions at “Configure Microsoft IIS Request Filtering
for Use with Content Server” on page 40.
Enable Anonymous Authentication
Applications like System Center Manager and OpenText Tempo Box require IIS
Anonymous authentication to connect to Content Server. For more information,
see “Enable IIS Anonymous Authentication” on page 41

Enable CGI or ISAPI

Microsoft Internet Information Services can run Content Server using CGI or ISAPI.
Be sure to enable whichever one you need.

CGI
In Windows Server Manager, enable the Web Server role (IIS). In Role Services >
Application Development, select the CGI check box.
ISAPI
In Windows Server Manager, enable the Web Server role (IIS). In Role Services >
Application Development, select the ISAPI extensions and ISAPI Filters check
boxes.

Prepare Microsoft Internet Information Services to Run Content

Server

Note: If you select Internet Information Services (IIS) as your HTTP Web
Server Type when you install Content Server, the installation program
configures Microsoft Internet Information Services automatically, and you do
not need to perform the steps in this section or the steps described in
“Configure Microsoft IIS Request Filtering for Use with Content Server”
on page 40.

If you intend to have Content Server configure Microsoft Internet Information

Services automatically, proceed to “Configure Extended ECM“ on page 75.

To configure Microsoft Internet Information Services manually, complete the steps

in the following procedure.

Note: The mappings.tbl file referred to in this procedure is generated by the

Content Server installer based on the values that you enter during installation
of Content Server.

To prepare Microsoft Internet Information Services to run Content Server:

1. Open Internet Information Services (IIS) Manager. In the Connections pane,

expand the Sites node.

LLESCOR240100-IGD-EN-01 Installation Guide 37

Chapter 4 Configure the Web Server to Run Extended ECM

2. Add the <Content_Server_home>\support\ folder as a virtual folder.

a. Right-click the Content Server web site node, and then click Add Virtual
Directory.
b. In the Add Virtual Directory dialog box:

i. In the Alias box, type the Directory Name that appears in the
Document Directory Mapping section of the mappings.tbl file. By
default, the alias is img.
ii. In the Physical Path box, type the Directory Path that appears in the
Document Directory Mapping section of the mappings.tbl file.
iii. Click OK.

3. Add the <Content_Server_home>\appData\supportasset\ folder as a virtual

folder.

a. Right-click the Content Server web site node, and then click Add Virtual
Directory.
b. In the Add Virtual Directory dialog box:

i. In the Alias box, type the mapping name. By default, the alias is
appimg.
ii. In the Physical Path box, enter a location for the virtual folder. By
default, it is <Content_Server_home>\appdata\supportasset.

Tip: In the Support Asset Volume configuration in Content

Server, the default Deployment Path of the Support Asset
Directory is <Content_Server_home>\appdata\supportasset.
You can locate the deployment path wherever you want, but the
IIS configuration must match the configuration in your
installation of Content Server.
iii. Click OK.

4. Create an application pool for Content Server.

a. In the Connections pane, click Application Pools.

b. In the Actions pane, click Add Application Pool. Enter a name, for
example, Content Server. Select the applicable .NET Framework version in
the .NET Framework version menu, and then click OK.

5. Add the CGI folder as an Application.

a. In the Connections pane of IIS Manager, right-click Default Web Site, and
then click Add Application.
b. In the Add Application dialog box, complete the following steps:

i. In the Alias field, type the Directory Name that appears in the CGI BIN
Mapping section of the mappings.tbl file. By default, the alias is OTCS.

38 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 4.2. Configure a Web Server to Run Content Server

ii. Click the Select button and choose Content Server in the Application
Pool drop-down list, and then click OK.
iii. In the Physical Path field, type the Directory Path associated with the
CGI BIN Mapping found in the mappings.tbl file.

iv. Click OK.

6. Allow the Content Server binary files to execute.

a. In the Connections pane of the IIS Manager, click the <server_name>.

b. In the <server_name> pane, double-click the ISAPI and CGI Restrictions
icon, and then click Add in the Actions pane.
c. In the Add ISAPI or CGI Restriction window, do the following:

i. Type (or browse to) the path to the cs.exe file in the ISAPI or CGI
path field.
ii. In the Description field, type a description for the executable.
iii. Select the Allow extension path to execute check box.

Note: Repeat the above steps for the following files:

• livelink.exe
• llisapi.dll

7. Edit the Handler Mappings.

a. In the Connections pane of the IIS Manager, click the <server_name>, and
then double-click Handler Mappings.
b. In the Actions pane, click Edit Feature Permissions.
c. In the Edit Feature Permissions window, select the Read, Script, and
Execute check boxes, and then click OK.

8. Add .properties files as a permitted MIME type in Microsoft Internet

Information Services

a. In the Connections pane of the IIS Manager, click the Content Server
<support> folder, and then double-click MIME Types in the center pane.

b. In the Actions pane, click Add.

c. In the Add MIME Type dialog box:

• Enter .properties in the File name extension box.

• Enter application/octet-stream in the MIME type box.

Click OK to save your changes.

LLESCOR240100-IGD-EN-01 Installation Guide 39

Chapter 4 Configure the Web Server to Run Extended ECM

Configure Microsoft IIS Request Filtering for Use with Content

Server
Note: If you select Internet Information Services (IIS) as your HTTP Web
Server Type when you install Content Server, the installation program
configures Microsoft Internet Information Services automatically, and you do
not need to perform the steps in this section.

Request Filtering is a security feature of Microsoft Internet Information Services that

restricts the types of HTTP requests that IIS handles.

To access the Request Filtering settings that apply to Content Server, open IIS
Manager, click the Content Server website on the left, and then click Request
Filtering in the middle pane. In the right pane, click Open Feature, and then click
Edit Feature Settings. The Edit Request Filter Settings dialog appears:

OpenText recommends that you configure Request Filtering as follows:

Allow unlisted verbs

If you select Internet Information Services (IIS) as your HTTP Web Server Type
when you install Content Server, the installation program sets Allow unlisted
verbs automatically. If you clear Allow unlisted verbs, you must allow the
following verbs:

40 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 4.2. Configure a Web Server to Run Content Server

• GET
• HEAD
• POST

Allow high-bit characters

Content Server uses UTF-8 character encoding, so Allow high-bit characters
must be enabled.
Maximum Allowed Content Length (Bytes)
OpenText recommends that you set the value of this setting to 2 GB
(2,147,483,648 bytes) to permit large files to be uploaded to or downloaded from
Content Server.

Note: The installation program for Content Server sets this value to
2,147,483,648 bytes.
Maximum URL Length
This option sets a maximum length for a URL used in a request to IIS. The
default setting of 4096 means that any URL longer than 4096 characters is
blocked. This is typically an acceptable value for Content Server.

Enable IIS Anonymous Authentication

Content Server does not require Anonymous Authentication to be enabled in IIS, but
other applications that connect to Content Server do. OpenText™ System Center
Manager and OpenText™ Tempo™ Box, Content Server Edition are examples of
applications that require Anonymous Authentication to be enabled so they can
connect to Content Server.

OpenText™ Directory Services provides Content Server with single sign-on and
strong logon security, so typically you do not need to enable Windows
Authentication or other additional types of IIS logon security. If you do enable
Windows Authentication, you should also enable Anonymous Authentication.
System Center Manager, which is used for applying updates to Content Server,
requires Anonymous Authentication to be enabled so that it can connect to Content
Server using the Content Server REST API. If Anonymous Authentication is not
enabled, System Center Manager cannot connect to Content Server to apply updates.

LLESCOR240100-IGD-EN-01 Installation Guide 41

Chapter 4 Configure the Web Server to Run Extended ECM

4.3 Configure an Application Server to Run Content

Server
To run Content Server on a supported application server, configure an application
server to use the Content Server Servlet (LLServlet).

Important
Content Server 16.2.8 and later uses OpenJDK. For compatibility reasons, the
application server that runs Content Server must be configured to run using
the same version of OpenJDK that Content Server uses.

An application server can host multiple web applications. Each web application
consists of at least one servlet and resides in its own folder. Every web application
has a configuration file named web.xml located in a folder named WEB-INF. This file
defines one or more servlets and a URL that maps information to a virtual folder. In
Content Server's case, the web.xml file also contains the location of the opentext.ini
file, from which the web application obtains other configuration information.

To run LLServlet, ensure that the application server can connect to Content Server's
root installation folder (the <Content_Server_Home> folder), and configure the
application server to run the LLServlet Java classes that are located in the <Content_
Server_Home>/application/WEB-INF/lib/llservletclient.jar file.

Configure an Application Server to Work with a Web Server

Tomcat can use a redirector to enable integration with a web server. A redirector
enables a web server to recognize servlet requests and pass them to the application
server for processing. In such an environment, the web server handles requests for
static files from the <Content_Server_Home>/support/ folder, but passes requests for
servlet content to the application server. An advantage of such a configuration is
that you can locate the application server behind a domain firewall.

Consult your application server vendor to obtain the specific plug-in and
documentation for configuring a redirector.

4.3.1 Deploy the Content Server Servlet

The Content Server Servlet can be deployed on supported versions of the Apache
Tomcat application server. To configure an application server to work with Content
Server, you create two context XML files (one for the servlet, and one for the support
files).

42 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 4.3. Configure an Application Server to Run Content Server

Deploy the Content Server Servlet on Apache Tomcat

Note: If you select Apache Tomcat as your HTTP Web Server Type when you
install Content Server, the configuration of Tomcat is performed automatically,
and you do not need to use the following instructions to create the Content
Server context files manually.

To deploy the Content Server Servlet on Apache Tomcat:

Note: Entries in XML files are case-sensitive.

Replace variable names, such as <Content_Server_Home> and

<Content_Server_virtual_folder>, in the sample XML files where necessary. For
example, change path="/<Content_Server_virtual_folder>" to path="/
OTCS".

The value of the docBase parameter in the sample XML files is a Windows
path. For a Linux installation, use forward slashes to separate folder names.
For example, docBase="/home/opentext/support/"

1. Stop the Content Server and Apache Tomcat services.

2. Ensure that the web.xml file has correct references to the opentext.ini file.

a. Open the <Content_Server_Home>/application/WEB-INF/web.xml file in a

text editor. Verify that each reference to the opentext.ini file points to the
correct file location.
b. Save and close the web.xml file.

3. Create the context XML files.

a. Create a file named <context_name>.xml using the following sample XML

code.

Tip: For a default Windows installation of Content Server, name this

file OTCS.xml.

<?xml version="1.0" encoding="utf-8"?>

<Context
path="/<Content_Server_virtual_folder>"
docBase="<Content_Server_Home>\application\"
debug="0"
swallowOutput="true"
reloadable="false">
<Logger
className="org.apache.catalina.logger.FileLogger"
prefix="<Content_Server_virtual_folder>"
suffix=".txt"
timestamp="true" />
</Context>

b. Save this file in the <TOMCAT_HOME>\conf\Catalina\localhost\ folder.

c. Create a file named <Content_Server_virtual_folder>.xml using the
following sample XML code.

LLESCOR240100-IGD-EN-01 Installation Guide 43

Chapter 4 Configure the Web Server to Run Extended ECM

Tip: For a default Windows installation of Content Server, name this

file img.xml.

<?xml version="1.0" encoding="utf-8"?>

<Context
cookies="false"
docBase="<Content_Server_Home>\support\"
path="/<Content_Server_Support_virtual_folder>"
useNaming="false"
workDir="work/Catalina/localhost/<Content_Server_virtual_folder>/" />

d. Save this file in the <TOMCAT_HOME>\conf\Catalina\localhost\ folder.

4. Start the Content Server and Apache Tomcat services.

To test the configuration, open the following URL in a browser: http://<server>:

8080/<context_name>/cs, using the <context_name> from step 3 above. The Content
Server logon page should appear.

Tip: If the logon page appears, but has no images, verify that the <Content_
Server_virtual_folder>.xml file is correctly configured.

Apache Tomcat URLs are case-sensitive. For example, Apache Tomcat

considers the following URLs to be different:

• https://my_host_name/path_name/cs.exe
• https://my_host_name/Path_Name/cs.exe

Configure the Support Asset Volume Virtual Directory (Tomcat)

The Support Asset Volume is a Content Server container that is used to store
Support Assets (files that are used in Content Server customizations, such as Custom
Views and Perspectives). To use the Support Asset Volume, you need to add a
Virtual Directory to the Content Server web site.

Content Server can be installed without a Support Asset Volume virtual directory,
but you may wish to set it up while you are preparing (Tomcat to run Content
Server. For more information on the Support Asset Volume, see OpenText Content
Server Admin Help - Support Asset Administration (LLESSAM-H-AGD).

To create the Support Asset Volume virtual directory:

1. Stop the Apache Tomcat service.

2. Create the Support Asset Volume context XML file.

a. Create a file named appimg.xml as in the following example.

<?xml version="1.0" encoding="utf-8"?>
<Context
cookies="false"
path="/appimg/"
docBase="C:\opentext\appdata\supportasset\"
useNaming="false"
workDir="work/Catalina/localhost/appimg/" />

44 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 4.3. Configure an Application Server to Run Content Server

Tip: The above example presumes that you are using the default
name and deployment directory of the Support Asset Volume.
In the Support Asset Volume configuration in Content Server, the
default URL Prefix for deployment path of the Support Asset
Directory is appimg and the default deployment path is <Content_
Server_home/appdata/supportasset>. You can name the URL Prefix
whatever you want and locate the deployment path wherever you
want, but your web server configuration must match the
configuration in your installation of Content Server.
b. Save this file in the <TOMCAT_HOME>\conf\Catalina\localhost\ folder.

3. Start the Apache Tomcat service.

LLESCOR240100-IGD-EN-01 Installation Guide 45

Chapter 5

Install Extended ECM on the Operating System

Once you have installed a supported web server or application server and a
supported relational database management system on a supported operating
system, you are ready to run the Content Server installation on your Content Server
computer.

The Content Server installer installs program files for Content Server and Content
Web Services. The Microsoft Windows installer for Content Server configures
Content Web Services automatically. The Linux installer does not, but instructions
for deploying Content Web Services on Tomcat are available on OpenText My
Support (https://knowledge.opentext.com/knowledge/cs.dll/Open/OTDN).

Notes

• Refer to the latest available Content Web Services (CWS) documentation.

The CWS documentation is updated only when it changes, so the latest
documentation may not have a version number that matches the current
Content Server version.
• This chapter explains how to install Content Server by launching the Content
Server installer for Linux or Windows, either interactively or from a
command line. You can also install and configure Content Server
automatically using OpenText™ System Center Manager. System Center
Manager installs, configures, patches, and updates multiple OpenText
software applications. For more information, see OpenText System Center
Manager - Installation and Configuration Guide (SYSCM-IGD).

5.1 Install Content Server on Microsoft Windows

This section describes how to perform a Content Server installation on computers
running Windows Server.

Note: See the Content Server Release Notes to determine the specific Windows
versions that are supported for the version of Content Server that you are
installing.

Before you install Content Server, create a Windows user to run Content Server and
make sure that the necessary supporting software, including a database server and
client, and a web server or application server, is installed and properly configured.
Configure your antivirus software to exclude the <Content_Server_home> folder and
subfolders and the folders that contain the Content Server search index files.
Detailed information about these and other tasks that you need to perform before
you install Content Server is provided in “Prepare to Install Extended ECM“
on page 23.

LLESCOR240100-IGD-EN-01 Installation Guide 47

Chapter 5 Install Extended ECM on the Operating System

When you install Content Server on Microsoft Windows, the installer can configure
Content Web Services automatically for use on Microsoft Internet Information
Services or on Apache Tomcat. The automatic installation generates a valid
configuration of Content Web Services running on the same web server as Content
Server. If you intend to run Content Web Services on a different web server, you can
use the automatic configuration, but you will need to copy the Content Web Services
program files to the other server and edit configuration files afterwards. For more
information on installing Content Web Services, refer to the instructions that are
available on OpenText My Support (https://knowledge.opentext.com/knowledge/
cs.dll/Open/OTDN).

Tip: To obtain detailed information about the installation of Content Server on

Microsoft Windows, refer to the Content Server Installer log files that are
written to your system temp folder.

5.1.1 Run the Content Server Installer on Microsoft Windows

You can perform an interactive installation or you can run a silent installation by
providing all required information in the installation command.

Interactive Installation of Content Server on Microsoft Windows

To start the installation of Content Server installer, download the Content Server
installer from OpenText My Support and run it on the computer where you want to
install Content Server.

To run the Content Server Installer on Windows:

1. Log on to Windows as a user who is a member of the Administrators group.

2. Run the Content Server installation.

a. Double-click the Content Server installation file to begin the installation.

b. In the Welcome dialog box, click Next.
c. In the License Agreement dialog box, enable I accept the terms in the
License Agreement, and then click Next.
d. In the Install Location dialog box, accept the default destination folder (C:
\OPENTEXT) or click Browse to select a different folder, and then click Next.
e. Enter the following information in the OpenText Content Server
Configuration dialog box, and then click Next:

• In the Service Name box, type a unique name for the Content Server
services. The default is OTCS. Use only alphanumeric characters, and do
not include spaces.

Note: The service name you provide is appended to the names of

the Content Server and Admin services in the Windows Services
window. It also becomes the name (alias) of the virtual folder
mapped to the <Content_Server_Home>/cgi/ folder in your web
server.

48 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.1. Install Content Server on Microsoft Windows

• In the DNS Name box, accept the default value, localhost, or type the
fully qualified domain name of the Content Server computer. Use the
format <host.domain.suffix> (for example, intranet.example.com).

Important

– Provide the fully qualified domain name to permit users to

connect to Content Server from outside your network. Content
Server uses this name to create links to items in Content Server
notifications and elsewhere. If you do not specify the fully
qualified domain name, these links may not work for remotely
connected users.
– If you are installing this instance of Content Server as part of a
Syndication environment, you must enter the fully qualified
domain name of the server. Once Content Server is installed,
there is no option to change this setting from the UI. If you
have localhost in the DNS Name box, you cannot enable a
Syndication environment, and you will have to re-install.
• In the HTTP Server Name box, type the host name of the computer on
which the web server resides, or accept the default value.

Note: OpenText recommends using the default value, localhost,

because Content Server and the web server must reside on the
same computer. Do not change the default value if the Content
Server computer has a dynamic IP address assigned by a Dynamic
Host Configuration Protocol (DHCP) server instead of a static IP
address.
• In the HTTP Port Number box, type the port number of the web server
where you intend to map Content Server's virtual directories.

Note: For HTTP servers, the default port is 80. For HTTPS servers,
the default port is 443.
f. In the HTTP Web Server Type dialog box, enable Internet Information
Services (IIS), Apache Tomcat, or Other, and then click Next.

• If you enable Internet Information Services (IIS), proceed to “Install

Content Server on Microsoft Internet Information Services on
Windows” on page 50.
• If you enable Apache Tomcat, proceed to “Install Content Server on
Tomcat on Windows” on page 52.
• If you enable Other, proceed to “Install Content Server on Other
Supported Web Servers on Windows” on page 55.

LLESCOR240100-IGD-EN-01 Installation Guide 49

Chapter 5 Install Extended ECM on the Operating System

Install Content Server on Microsoft Internet Information Services on Windows

Note: The following instructions are a continuation of “Run the Content Server
Installer on Microsoft Windows” on page 48. Follow these instructions if you
enabled Internet Information Services (IIS) in the HTTP Web Server Type
dialog box (step 2.f).

To install Content Server on Microsoft Internet Information Services

1. In the IIS Web Server Settings dialog box:

• Select the IIS website that will host Content Server. The default is Default
Web Site.
• Note the CGI Mapping name. The CGI Mapping name and Application
pool name cannot be changed on this dialog box. They are determined by
the settings that you entered on the OpenText Content Server
Configuration dialog box (step 2.e).
• Enter a mapping name for the Content Server support directory or accept
the default mapping name (/img/). The mapping name must begin and end
with a forward slash (/), must contain only alphanumeric characters, and
must not contain spaces.

Tip: Content Server web pages make numerous references to the

support directory. A support directory mapping with few characters
makes for smaller Content Server web pages that render more quickly
on a client application.
• Enter a mapping name for the Content Server support asset directory or
accept the default mapping name (/appimg/). The mapping name must
begin and end with a forward slash (/), must contain only alphanumeric
characters, and must not contain spaces.
• Note the Application pool name for CGI and the support mappings.

Click Next to continue the installation.

2. Complete the Port Configuration for OpenText Content Server dialog box, and
then click Next.

• In the Service Port box, type an unused port number for the Content Server
service. Valid port numbers range from 1025 to 65535. The default is 2099.
• In the Admin Port box, type an unused port number for the Admin server
service. Valid port numbers range from 1025 to 65535. The default is 5858.

Note: If necessary, the Content Server installation program will install the
Microsoft Visual C++ redistributable package. The Visual C++
Redistributable Package installs runtime components of Visual C++
Libraries that allow Visual C++ applications to run on a computer that
does not have Visual C++ installed.

50 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.1. Install Content Server on Microsoft Windows

3. In the HTTP Web Server Type dialog box, select the Web Server Type (Internet
Information Services (IIS) or Apache Tomcat) that will host Content Web
Services, or enable Skip.

Note: Content Web Services is a set of service-oriented web service APIs

for OpenText Content Server.
Your response on this step determines whether Microsoft Internet
Information Services or Apache Tomcat is configured to run Content
Server Web Services. If you choose Skip, neither one is configured to run
Content Server Web Services.
Content Server Web Services is installed regardless of your selection. If
you choose Skip, you can configure a supported web or application server
to run Content Server Web Services after you finish installing Content
Server.
For more information, see the Content Web Services (https://
knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=17990637&
objAction=browse&sort=name&viewType=1) page on OpenText My
Support. Refer to the latest available Content Web Services (CWS)
documentation.

Tip: If you enable Internet Information Services (IIS), the following

message may appear:
Please install the HTTP Activation .NET Framework feature on this
server.
If this message appears, use Add Features in Windows Server Manager to
install WCF Activation: HTTP Activation (.NET 4).
4. The dialog box that appears now depends on the selection that you made in the
previous step. Follow the instructions that apply to you.

• If you enabled Internet Information Services (IIS), the IIS Web Server
Settings dialog box appears. Enter the following information and then click
Next:

– Select the IIS website that will host the Content Server web service. The
default is Default Web Site.
– Enter a Web Service Mapping name for Content Server. The default is
cws.

The Application pool name cannot be changed on this dialog box. It is

determined by the setting you entered on the OpenText Content Server
Configuration dialog box (step 2.e).
• If you enabled Apache Tomcat, the Apache Tomcat Install Location dialog
box appears.

– The installer attempts to display the correct path of your Apache Tomcat
installation. Correct it if necessary, and then click Next.

LLESCOR240100-IGD-EN-01 Installation Guide 51

Chapter 5 Install Extended ECM on the Operating System

– On the Apache Tomcat Web Server Settings dialog box, enter the
Content Server Web Service Mapping name or accept the default (cws).
• If you enabled Skip, there is no Content Server Web Service configuration to
perform. Proceed to the next step.

5. In the Ready to Install dialog box, click Install. The Installing the product
dialog box appears and a progress bar shows the status of the Content Server
installation.

6. When the installation is complete, clear Start Content Server and Start Content
Server Admin Server, enable View Mapping File, and then click Next to open
the mappings.tbl file in a separate window.

Note: The mappings.tbl file is a text file that contains the mappings
(virtual folder aliases) used to configure your web server or application
server. The mappings.tbl file is available to view at any time in your
<Content_Server_Home> folder.

7. Click Finish.

Important
If there are required Updates and patches that you need to apply to
Content Server to complete the installation, do not start the Content Server
services at this point.

8. To complete the installation of Content Server on Microsoft Windows, follow

the instructions at “Apply Updates and Patches and Start the Content Server
Services” on page 64.

Install Content Server on Tomcat on Windows

Note: The following instructions are a continuation of “Run the Content Server
Installer on Microsoft Windows” on page 48. Follow these instructions if you
enabled Apache Tomcat in the HTTP Web Server Type dialog box (step 2.f).

To install Content Server on Tomcat

1. The installer attempts to display the correct path of your Apache Tomcat
installation in the Apache Tomcat Install Location dialog box. Correct it if
necessary, and then click Next.

2. In the Apache Tomcat Web Server Settings dialog box:

• Note the CGI Mapping name. The CGI Mapping name cannot be changed
on this dialog box. It is determined by the settings that you entered on the
OpenText Content Server Configuration dialog box (step 2.e).
• Enter a mapping name for the Content Server support directory or accept
the default mapping name (/img/). The mapping name must begin and end
with a forward slash (/), must contain only alphanumeric characters, and
must not contain spaces.

52 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.1. Install Content Server on Microsoft Windows

Tip: Content Server web pages can make numerous references to the
support directory. A support directory mapping with few characters
makes for smaller Content Server web pages that render more quickly
on the client.
• Enter a mapping name for the Content Server support asset directory or
accept the default mapping name (/appimg/). The mapping name must
begin and end with a forward slash (/), must contain only alphanumeric
characters, and must not contain spaces.

Click Next to continue the installation.

3. Complete the Port Configuration for OpenText Content Server dialog box, and
then click Next.

• In the Service Port box, type an unused port number for the Content Server
service. Valid port numbers range from 1025 to 65535. The default is 2099.
• In the Admin Port box, type an unused port number for the Admin server
service. Valid port numbers range from 1025 to 65535. The default is 5858.

If necessary, the Content Server installation program will install the Microsoft
Visual C++ redistributable package. The Visual C++ Redistributable Package
installs runtime components of Visual C++ Libraries that allow Visual C++
applications to run on a computer that does not have Visual C++ installed.
4. In the HTTP Web Server Type dialog box, select the Web Server Type (Internet
Information Services (IIS) or Apache Tomcat) that will host Content Web
Services, or enable Skip.

Note: Content Web Services is a set of service-oriented web service APIs

for OpenText Content Server.
Your response on this step determines whether Microsoft Internet
Information Services or Apache Tomcat is configured to run Content
Server Web Services. If you choose Skip, neither one is configured to run
Content Server Web Services.
Content Server Web Services is installed regardless of your selection. If
you choose Skip, you can configure a supported web or application server
to run Content Server Web Services after you finish installing Content
Server.
For more information, see the Content Web Services (https://
knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=17990637&
objAction=browse&sort=name&viewType=1) page on OpenText My
Support. Refer to the latest available Content Web Services (CWS)
documentation.

Tip: If you enable Internet Information Services (IIS), the following

message may appear:
Please install the HTTP Activation .NET Framework feature on this
server.

LLESCOR240100-IGD-EN-01 Installation Guide 53

Chapter 5 Install Extended ECM on the Operating System

If this message appears, use Add Features in Windows Server Manager to

install WCF Activation: HTTP Activation (.NET 4).

5. The dialog box that appears now depends on the selection that you made in the
previous step. Follow the instructions that apply to you.

• If you enabled Internet Information Services (IIS), the IIS Web Server
Settings dialog box appears. Enter the following information and then click
Next:

– Select the IIS website that will host the Content Server web service. The
default is Default Web Site.
– Enter a Web Service Mapping name for Content Server. The default is
cws.

The Application pool name cannot be changed on this dialog box. It is

determined by the setting you entered on the OpenText Content Server
Configuration dialog box (step 2.e).
• If you enabled Apache Tomcat, the Apache Tomcat Install Location dialog
box appears.

– The installer attempts to display the correct path of your Apache Tomcat
installation. Correct it if necessary, and then click Next.
– On the Apache Tomcat Web Server Settings dialog box, enter a Web
Service Mapping name or accept the default (cws), and then click Next.
• If you enabled Skip, there is no Content Server Web Service configuration to
perform. Proceed to the next step.

6. In the Ready to Install dialog box, click Install. The Installing the product
dialog box appears and a progress bar shows the status of the Content Server
installation.

7. When the installation is complete, clear Start Content Server and Start Content
Server Admin Server, enable View Mapping File, and then click Next to open
the mappings.tbl file in a separate window.

Note: The mappings.tbl file is a text file that contains the mappings
(virtual folder aliases) used to configure your web server or application
server. The mappings.tbl file is available to view at any time in your
<Content_Server_Home> folder.

8. Click Finish.

Important
If there are required Updates and patches that you need to apply to
Content Server to complete the installation, do not start the Content Server
services at this point.

54 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.1. Install Content Server on Microsoft Windows

9. To complete the installation of Content Server on Microsoft Windows, follow

the instructions at “Apply Updates and Patches and Start the Content Server
Services” on page 64.

Install Content Server on Other Supported Web Servers on Windows

Note: The following instructions are a continuation of “Run the Content Server
Installer on Microsoft Windows” on page 48. Follow these instructions if you
enabled Other in the HTTP Web Server Type dialog box (step 2.f).

To install Content Server on other supported web servers on Windows

1. In the OpenText Content Server Mapping dialog box, enter a URL Prefix for
the Content Server support directory or accept the default URL Prefix (/img/).
The URL Prefix must begin and end with a forward slash (/), must contain only
alphanumeric characters, and must not contain spaces.

Tip: Content Server web pages can make numerous references to the
support directory. A support directory mapping with few characters
makes for smaller Content Server web pages that render more quickly on
the client.

2. In the Port Configuration for OpenText Content Server window, do the

following, and then click Next:

• In the Service Port box, type an unused port number for the Content Server
service. Valid port numbers range from 1025 to 65535. The default is 2099.
• In the Admin Port box, type an unused port number for the Admin server
service. Valid port numbers range from 1025 to 65535. The default is 5858.

Note: If necessary, the Content Server installation program will install the
Microsoft Visual C++ redistributable package. The Visual C++
Redistributable Package installs runtime components of Visual C++
Libraries that allow Visual C++ applications to run on a computer that
does not have Visual C++ installed.

3. In the HTTP Web Server Type dialog box, select the Web Server Type (Internet
Information Services (IIS) or Apache Tomcat) that will host the Content Web
Services, or enable Skip.

Note: Content Web Services is a set of service-oriented web service APIs

for OpenText Content Server.
Your response on this step determines whether Microsoft Internet
Information Services or Apache Tomcat is configured to run Content
Server Web Services. If you choose Skip, neither one is configured to run
Content Server Web Services.
Content Server Web Services is installed regardless of your selection. If
you choose Skip, you can configure a supported web or application server

LLESCOR240100-IGD-EN-01 Installation Guide 55

Chapter 5 Install Extended ECM on the Operating System

to run Content Server Web Services after you finish installing Content
Server.
For more information, see the Content Web Services (https://
knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=17990637&
objAction=browse&sort=name&viewType=1) page on OpenText My
Support. Refer to the latest available Content Web Services (CWS)
documentation.

Tip: If you enable Internet Information Services (IIS), the following

message may appear:
Please install the HTTP Activation .NET Framework feature on this
server.

If this message appears, use Add Features in Windows Server Manager to

install WCF Activation: HTTP Activation (.NET 4).

4. The dialog box that appears now depends on the selection that you made in the
previous step. Follow the instructions that apply to you.

• If you enabled Internet Information Services (IIS), the IIS Web Server
Settings dialog box appears. Enter the following information and then click
Next:

– Select the IIS website that will host the Content Server web service. The
default is Default Web Site.
– Enter a Web Service Mapping name for Content Server. The default is
cws.

The Application pool name cannot be changed on this dialog box. It is

determined by the setting you entered on the OpenText Content Server
Configuration dialog box (step 2.e).
• If you enabled Apache Tomcat, the Apache Tomcat Install Location dialog
box appears.

– The installer attempts to display the correct path of your Apache Tomcat
installation. Correct it if necessary, and then click Next.
– On the Apache Tomcat Web Server Settings dialog box, enter the
Content Server Web Service Mapping name or accept the default (cws).
• If you enabled Skip, there is no Content Server Web Service configuration to
perform. Proceed to the next step.

5. In the Ready to Install dialog box, click Install. The Installing the product
dialog box appears and a progress bar shows the status of the Content Server
installation.

6. When the installation is complete, clear Start Content Server and Start Content
Server Admin Server, enable View Mapping File, and then click Next to open
the mappings.tbl file in a separate window.

56 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.1. Install Content Server on Microsoft Windows

Note: The mappings.tbl file is a text file that contains the mappings
(virtual folder aliases) used to configure your web server or application
server. The mappings.tbl file is available to view at any time in your
<Content_Server_Home> folder.

7. Click Finish.

Important
If there are required Updates and patches that you need to apply to
Content Server to complete the installation, do not start the Content Server
services at this point.

8. To complete the installation of Content Server on Microsoft Windows, follow

the instructions at “Apply Updates and Patches and Start the Content Server
Services” on page 64.

Unattended Installation of Content Server on Microsoft Windows

To run an unattended installation of Content Server, open a command shell as an
Administrator, and then run the Windows Installer file, providing the required
information in the options of the Windows Installer file. Select the required installer
parameters from “Content Server Installer Parameters” on page 57

For sample commands, see “Examples of Content Server Installation Commands”

on page 63.

Table 5-1: Content Server Installer Parameters

Parameter Description Values Example Notes

INSTALLDIR The full path of A path name. INSTALLDIR=C: Place the path
the directory \OpenText\ name in
where Content otcs quotation marks
Server will be if it contains
installed. spaces.
LES_SERVICEN The name of the A service name. LES_ The LES_
AME Content Server SERVICENAME= SERVICENAME
services. otcs determines the
names of two
different
Content Server
services. If LES_
SERVICENAME is
set to otcs, the
Content Server
service is named
otcs and the
Content Server
Admin service is
named
otcsAdmin.

LLESCOR240100-IGD-EN-01 Installation Guide 57

Chapter 5 Install Extended ECM on the Operating System

Parameter Description Values Example Notes

HTTP_WEB_SE The type of Web IIS, Tomcat, or HTTP_WEB_ • If you specify
RVER_TYPE server that Skip SERVER_TYPE= HTTP_WEB_
Content Server IIS SERVER_
will be installed TYPE=IIS,
on: Microsoft IIS, you must
Tomcat, or also provide
another the
supported web WEBSITE_
server. NAME
parameter to
the installer.
• If you specify
HTTP_WEB_
SERVER_
TYPE=
Tomcat you
must also
provide the
TOMCATINST
ALLDIR
parameter to
the installer.
• Specify
HTTP_WEB_
SERVER_
TYPE=Skip
to install on a
supported
web server
other than IIS
or Tomcat.

58 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.1. Install Content Server on Microsoft Windows

Parameter Description Values Example Notes

HTTP_WEB_SE The type of web IIS, Tomcat, or HTTP_WEB_ • If you specify
RVER_WS_TYP server that Skip SERVER_WS_ HTTP_WEB_
E Content Server TYPE=IIS SERVER_WS_
Web Services TYPE=IIS,
will be installed you must
on. also provide
the WS_
WEBSITE_
NAME
parameter to
the installer.
• If you specify
HTTP_WEB_
SERVER_WS_
TYPE=
Tomcat you
must also
provide the
TOMCATWSIN
STALLDIR
parameter to
the installer.
• Specify
HTTP_WEB_
SERVER_WS_
TYPE=Skip
to install
Content
Server Web
Services on a
supported
web server
other than IIS
or Tomcat.
START_CS Indicates Yes, No START_CS=Yes
whether you
want the
Content Server
installer to start
Content Server
once the
installation is
complete.

LLESCOR240100-IGD-EN-01 Installation Guide 59

Chapter 5 Install Extended ECM on the Operating System

Parameter Description Values Example Notes

START_CSADM Indicates Yes, No START_
IN whether you CSADMIN=Yes
want the
Content Server
installer to start
the Content
Server Admin
server once the
installation is
complete.
WS_APP_NAM The Content A mapping WS_APP_NAME=
E Server Web name. cws
Services
mapping name.
LES_SUPPORT The name of the A mapping LES_
MAPPINGPREF mapping for the name that starts SUPPORTMAPPIN
IX Content Server and ends with a GPREFIX=/img/
support slash.
directory.
LES_SUPPORT The name of the A mapping LES_
ASSETMAPPIN mapping for the name that starts SUPPORTASSETM
G Content Server and ends with a APPING=/
Support Asset slash. appimg/
Volume..
LES_ADMINPO The port A positive LES_ In an interactive
RT assigned to the integer ADMINPORT= installation, the
Content Server representing a 5858 default port is
Admin server. TCP port. 5858. In an
unattended
installation, you
must specify the
Admin port
explicitly.
LES_SERVICEP The port A positive LES_ In an interactive
ORT assigned to integer SERVICEPORT= installation, the
Content Server. representing a 2099 default port is
TCP port. 2099. In an
unattended
installation, you
must specify the
Content Server
port explicitly.

60 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.1. Install Content Server on Microsoft Windows

Parameter Description Values Example Notes

TOMCATINSTA The Tomcat A Tomcat TOMCATINSTALL • You must
LLDIR directory where directory name. DIR=C:\tomcat specify this
Content Server parameter if
will be installed. you set
HTTP_WEB_
SERVER_WS_
TYPE=
Tomcat. It is
not necessary
otherwise.
• Place the
path name in
quotation
marks if it
contains
spaces.
TOMCATWSIN The Tomcat A Tomcat TOMCATWSINSTA • You must
STALLDIR directory where directory name. LLDIR=C: specify this
Content Server \tomcat parameter if
Web Services you set
will be installed. HTTP_WEB_
SERVER_WS_
TYPE=
Tomcat. It is
not necessary
otherwise.
• Place the
path name in
quotation
marks if it
contains
spaces.
LES_HTTP_POR The port of the A positive LES_HTTP_
T Content Server integer PORT=80
website. representing a
TCP port.
LES_HTTP_SER The name of the A server name. LES_HTTP_
VERNAME HTTP server SERVERNAME=
that hosts the server.
Content Server corporate.com
website.

LLESCOR240100-IGD-EN-01 Installation Guide 61

Chapter 5 Install Extended ECM on the Operating System

Parameter Description Values Example Notes

LES_DNSNAME The name of the A server name. LES_DNSNAME= • Defaults to
server that runs server. localhost,
Content Server. corporate.com if not
specified.
• If you are
setting up a
Syndication
environment,
see the
important
notes and tip
associated
with the
DNS Name
box in
“Interactive
Installation
of Content
Server on
Microsoft
Windows”
on page 48.
WEBSITE_NAM The name of the An IIS website WEBSITE_NAME= • The website
E Microsoft IIS name. otcs must exist in
website where Microsoft IIS
Content Server before you
will be installed. run the
installer.
• You must
specify this
parameter if
you set
HTTP_WEB_
SERVER_WS_
TYPE=IIS. It
is not
necessary
otherwise.
WS_WEBSITE_ The name of the An IIS website WS_WEBSITE_ • You must
NAME Microsoft IIS name. NAME=cws specify this
website where parameter if
Content Server you set
Web Services HTTP_WEB_
will be installed. SERVER_WS_
TYPE=IIS. It
is not
necessary
otherwise.

62 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.1. Install Content Server on Microsoft Windows

Examples of Content Server Installation Commands

Install Content Server on Microsoft IIS

The following command installs Content Server <##.#.#> in the C:\OpenText\
otcs folder. It installs Content Server on a Microsoft IIS website called otcs. It
uses the default ports for the Content Server and Content Server Admin
services. And it uses the default names mapped to the support directory, the
Support Asset Volume, and Content Server Web Services. When the installation
completes, the Windows Installer does not start any of the Content Server
services.
<##.#.#>_CS64_WIN.exe INSTALLDIR=C:\OpenText\otcs LES_SERVICENAME=otcs
HTTP_WEB_SERVER_TYPE=IIS HTTP_WEB_SERVER_WS_TYPE=IIS START_CS=No START_
CSADMIN=No LES_SERVICEPORT=2099 LES_ADMINPORT=5858 LES_
SUPPORTMAPPINGPREFIX=/img/ LES_SUPPORTASSETMAPPING=/appimg/ WS_APP_
NAME=cws WEBSITE_NAME=otcs WS_WEBSITE_NAME=otcs

Install Content Server on Tomcat

The following command installs Content Server <##.#.#> in the C:\OpenText\
otcs folder. It installs Content Server on a Tomcat server located at C:\tomcat. It
uses the default ports for the Content Server and Content Server Admin
services. And it uses the default names mapped to the support directory, the
Support Asset Volume and Content Server Web Services. When the installation
completes, the Windows Installer starts the Content Server and Content Server
Admin services.
<##.#.#>_CS64_WIN.exe INSTALLDIR=c:\OpenText\otcs LES_SERVICENAME=otcs
HTTP_WEB_SERVER_TYPE=Tomcat HTTP_WEB_SERVER_WS_TYPE=Tomcat START_CS=Yes
START_CSADMIN=Yes LES_SERVICEPORT=2099 LES_ADMINPORT=5858 LES_
SUPPORTMAPPINGPREFIX=/img/ LES_SUPPORTASSETMAPPING=/appimg/ WS_APP_
NAME=cws TOMCATINSTALLDIR=C:\tomcat TOMCATWSINSTALLDIR=C:\tomcat

Install a second instance of Content Server on Microsoft IIS

The following command installs a second instance of Content Server <##.#.#> in
the C:\OpenText\otcs2 folder. It installs Content Server on a Microsoft IIS
website called otcs2 running on TCP port 81. It uses non-default ports for the
Content Server and Content Server Admin services. And it uses the default
names mapped to the support directory, the Support Asset Volume, and
Content Server Web Services. When the installation completes, the Windows
Installer starts the Content Server service, but does not start the Content Server
Admin service.
<##.#.#>_CS64_WIN.exe INSTALLDIR=c:\OpenText\otcs2 LES_SERVICENAME=
otcs2 HTTP_WEB_SERVER_TYPE=IIS HTTP_WEB_SERVER_WS_TYPE=IIS START_CS=Yes
START_CSADMIN=No LES_HTTP_PORT=81 LES_SERVICEPORT=22099 LES_ADMINPORT=
25858 LES_SUPPORTMAPPINGPREFIX=/img/ WS_APP_NAME=cws WEBSITE_NAME=otcs2
WS_WEBSITE_NAME=otcs2

Note: The above command would also work if it were used to install a first
instance of Content Server on a Content Server host machine. In Content
Server 16.2.7 and earlier, it was necessary to extract the installer and
specify TRANSFORMS and MSINEWINSTANCE command options when installing

LLESCOR240100-IGD-EN-01 Installation Guide 63

Chapter 5 Install Extended ECM on the Operating System

an additional instance of Content Server on the same Content Server host

machine. It is no longer necessary to extract the installer or specify these
parameters in Content Server 16.2.8 and later.

5.1.2 Apply Updates and Patches and Start the Content

Server Services
To complete the installation of Content Server, you may need to apply an Update
and one or more patches to Content Server before you start the Content Server
services.

Tip: Consult the Content Server Release Notes for information on required
Updates and patches.

To apply Updates and Patches and start the Content Server services

1. If an Update is available for your version of Content Server, apply the latest
Content Server Update. For more information on applying Content Server
Updates, see OpenText Extended ECM - Upgrade Guide (LLESCOR-IUP).
When you have finished installing the Content Server Update, copy the files
from the <Content_Server_home>\config\config_reference\ folder to the
<Content_Server_home>\config\ folder, overwriting files as necessary. For
more information on the config_reference folder, see OpenText Extended ECM -
Upgrade Guide (LLESCOR-IUP).

Tip: For most Updates, OpenText releases an integrated installer that

installs Content Server and the Update. If you use an integrated installer,
you do not need to install an Update separately, and you do not need to
copy the files from the config_reference folder, but you do need to apply
required and recommended patches.

2. Apply any required patches. If there is more than one patch, apply each one in
ascending numerical order. Extract the contents of each patch file into the
<Content_Server_home> folder (C:\OPENTEXT, by default), overwriting any files,
as necessary.

Note: OpenText recommends that you use System Center Manager to

update your Content Server installation. (See “Apply All Available
Patches to Content Server” on page 115.) Apply patches manually only if
the Release Notes identify a patch that must be applied before you start
Content Server for the first time.

3. Set the Content Server services to run as the Content Server user that you
created in “Create a Windows User” on page 24. Launch the Windows Services
application and perform the following steps for the Content Server services:

• Content Server (<service_name>)

• Content Server Admin (<service_name>)

64 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.1. Install Content Server on Microsoft Windows

a. In the right pane, double-click Content Server (<service name>). In the

Content Server (<service name>) Properties dialog box, click the General
tab.

b. If you automatically started the Content Server services at the end of the
installation procedure, the Service status field reads Started. Click Stop to
stop the Content Server <service name> service.

c. Click the Log On tab.

d. In the Log on as tab section, click This account, and then click Browse.

e. Add the user that you created to run Content Server, and then click OK.

f. Type a password for this user in the Password and Confirm password
boxes, and then click Apply.

g. Open the General tab.

4. Start each of the Content Server services.

LLESCOR240100-IGD-EN-01 Installation Guide 65

Chapter 5 Install Extended ECM on the Operating System

5.2 Install Content Server on Linux

This section describes how to install Content Server on computers running
supported versions of Linux.

Note: There are separate installers for Linux 8 and Linux 9. The instructions in
this section apply to both installer versions. Be sure you use the correct installer
for your Linux version.

Before you install Content Server, create a user to run Content Server, and ensure
that the database server and client, web server, and web browser are installed and
properly configured. See “Prepare to Install Extended ECM“ on page 23.

5.2.1 Content Server Installer Dependencies

Before the Content Server installer begins the installation of Content Server, it
verifies that a number of required files and libraries are present on your system in
the expected location. If it does not find them, you must specify the actual location of
the required item (if it is present, but not at the expected location) or install it before
running the Content Server installer.

The X Virtual Frame Buffer (Xvfb)

Content Server depends on the presence of the Virtual Frame Buffer (xvfb) on Linux.
If the Virtual Frame Buffer is not installed on your system, you must install it to
ensure Content Server can generate thumbnails, present HTML views of documents,
and perform other tasks.

Note: Xvfb is not part of the default installation of Red Hat 5.7 and later. To
install Xvfb, run the following command(s):

Linux
yum install xorg-x11-server-Xvfb

yum install libXrender

The Content Server installer verifies that the X Virtual Frame Buffer is present at /
usr/bin/Xvfb. If it is not, the following message appears:

Xvfb has not been detected in the default location:

Do you have Xvfb installed to a location other than the default? [Y]:

If you answer Y, the installer prompts you to enter the location of Xvfb. Once you do,
the installer informs you that

You MUST modify <Installation Directory>/config/filters/startXVFB.sh to

reflect this Xvfb install location.

Modify startXVFB.sh once the installation completes.

66 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.2. Install Content Server on Linux

Example: If your copy of Xvfb is located at /another/place/Xvfb, on the first

uncommented line of the shell script, change x11_path="/usr/bin/" to x11_path="/
another/place/"

Required Libraries for Linux

On Linux, the Content Server installer checks for the presence of the following
libraries:

• /usr/bin/Xvfb
• /lib64/libX11.so.6
• /lib64/libXau.so.6
• /lib64/libXext.so.6
• /lib64/libXrender.so.1
• /lib64/libbz2.so.1
• /lib64/libc.so.6
• /lib64/libcairo.so.2
• /lib64/libcrypt.so.1
• /lib64/libdl.so.2
• /lib64/libk5crypto.so.3
• /lib64/libkeyutils.so.1
• /lib64/libkrb5.so.3
• /lib64/libkrb5support.so.0
• /lib64/libm.so.6
• /lib64/libnsl.so.2 (for Linux 8)
• /lib64/libnsl.so.3 (for Linux 9)
• /lib64/libpcre2-8.so.0
• /lib64/libpixman-1.so.0
• /lib64/libpng16.so.16
• /lib64/libpthread.so.0
• /lib64/libresolv.so.2
• /lib64/librt.so.1
• /lib64/libselinux.so.1
• /lib64/libtirpc.so.3
• /lib64/libuuid.so.1
• /lib64/libxcb-render.so.0

LLESCOR240100-IGD-EN-01 Installation Guide 67

Chapter 5 Install Extended ECM on the Operating System

• /lib64/libxcb-shm.so.0
• /lib64/libxcb.so.1
• /usr/lib64/libX11.so.6
• /usr/lib64/libXau.so.6
• /usr/lib64/libXext.so.6
• /usr/lib64/libXrender.so.1
• /usr/lib64/libbz2.so.1
• /usr/lib64/libc.so.6
• /usr/lib64/libcairo.so.2
• /usr/lib64/libcrypt.so.1
• /usr/lib64/libdl.so.2
• /usr/lib64/libm.so.6
• /usr/lib64/libpixman-1.so.0
• /usr/lib64/libpng16.so.16
• /usr/lib64/libpthread.so.0
• /usr/lib64/librt.so.1
• /usr/lib64/libuuid.so.1
• /usr/lib64/libxcb-render.so.0
• /usr/lib64/libxcb-shm.so.0
• /usr/lib64/libxcb.so.1

If the installer does not find one or more of the libraries, a warning message appears.
For example, if the installer does not find libbz2.so.1, the following message
appears:

WARNING Content Server requires libbz2.so.1 to be installed. libbz2.so.1 has

not been detected in the default location:/lib64/libbz2.so.

Do you have libbz2.so.1 installed to a location other than the default? [Y]

If you answer Y, the installer prompts you to enter the location of the missing
library. Once you do, the installer informs you that:

You MUST modify the LD_LIBRARY_PATH variable in <Installation Directory>/

start_llserver to reflect this install location.

Modify start_llserver once the installation completes.

Example: If libc.so.6 is located at /another/place/libc.so.6 (not /lib64/libc.so.

6), find the line in the start_llserver script that reads as follows:

68 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.2. Install Content Server on Linux

LD_LIBRARY_PATH=$LLDBHOME/lib${DB32SFX}:$LLHOME/lib:$LLHOME/filters/
image:$LD_LIBRARY_PATH

Add the location of libc.so.6 to the end of this line, as follows:

LD_LIBRARY_PATH=$LLDBHOME/lib${DB32SFX}:$LLHOME/lib:$LLHOME/filters/
image:$LD_LIBRARY_PATH:/another/place

Note: For a computer that runs only a Content Server Admin server (not a
Content Server Front-End instance), make the change to the start_lladmin
script.

The Landscape Directory

During the installation of Content Server, the installer attempts to write a solution
registry file to the /etc/opentext/landscape/ directory. This solution registry file is
used by other OpenText products to obtain information about Content Server. In
particular, it is used by OpenText products that integrate with SAP.

The installer does not verify that the user running the Content Server installation has
access to this folder, but if the user does not, the following message appears after the
Content Server installation is complete:
Unable to create the landscape directory '/etc/opentext/landscape'.
The solution registry file is saved in <Content_Server_home> instead.
It's recommended that the solution registry file be copied to '/etc/opentext/landscape'
directory for use by other OpenText products.

This message does not indicate an installation failure, but you can prevent it from
appearing by ensuring that the user that runs the Content Server installer can create
the /etc/opentext/landscape/ directory and write to it. If the message does appear,
however, you can copy the solution registry file from your <Content_Server_home>
directory to the /etc/opentext/landscape/ directory after the installation
completes. This produces the same result as having the Content Server installer
create the file in the /etc/opentext/landscape/ directory during the installation.

Tip: The solution registry file has a name similar to 20150918155349–

OTCONTENTSERVER-Install.ini.

5.2.2 Run the Content Server Installer on Linux

You can perform an interactive installation or you can run a silent installation by
providing all required information in the installation command.

LLESCOR240100-IGD-EN-01 Installation Guide 69

Chapter 5 Install Extended ECM on the Operating System

Interactive Installation of Content Server on Linux

The Content Server installer for supported Linux operating systems is delivered as a
compressed TAR file. Once you have expanded the file and extracted its component
files, you run a setup executable to install Content Server.

Tip: As you complete these installation procedures, record directory paths,

port numbers, and other information on Section 10.3: “Content Server
Installation Worksheet” on page 173.

Note: OpenText recommends that you run the installation program only after
installing and configuring your database. Although the installer will install
Content Server without a database being present, OpenText does not
recommend this. Press CTRL + C to exit the installation program if your
database is not properly installed and configured.

To install Content Server on Linux:

1. Log on as the Linux user that you created to run Content Server. For
information, see “Create a Linux User” on page 24.

2. Using the tools installed with your version of Linux, unzip and unpack the
setup utility.

3. Type ./setup, and then press ENTER.

Note: If an error message appears that states Content Server requires

<filename> to be installed. <filename> has not been detected in the
default location:, you will have an opportunity to specify the correct
location of <filename>.
For more information on such error messages, see “Content Server
Installer Dependencies” on page 66

4. Type Y to accept the license agreement.

5. When you are prompted to enter the Content Server installation directory, enter
the path of the directory you wish to use or press ENTER to accept the default
installation directory (/usr/local/contentserver/).

Tip: If the directory you specify does not exist, type Y when you are
prompted to create it.

6. When you are prompted to install Content Server, type Y.

7. At the prompt that asks you for the port number to run Content Server on, type
a number between 1025 and 65535 or accept the default (2099).

Tip: The port number you choose must not be in use by any other process.
To find out which port numbers are currently in use on the computer, use
the command netstat -a.

70 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.2. Install Content Server on Linux

8. At the prompt that asks you for the port number to run the Content Server
Admin server on, type a number between 1025 and 65535, or accept the default
(5858).

9. At the prompt that asks you for the default CGI alias for the <Content_Server_
Home>/cgi/ directory, type a prefix or accept the default prefix, livelink.

10. At the prompt that asks you to specify a Filter Engine temp directory, type the
absolute path of a directory or accept the default (/tmp).

Tip: OpenText recommends that you accept the default value because this
improves the performance of the document conversion processes that
generate full-text indexes in Content Server.

11. A prompt appears that asks you to specify the kind of database that you will be
using with Content Server. Your next steps depend on your answer to this
question.

Oracle
To use an Oracle database, enter 1, and then enter the SID of your local
Oracle installation. Alternatively, you can enter ? and then provide the path
of your Oracle home directory.

Tip: If you specify a nonexistent Oracle home directory, the

installation program asks you to confirm that you want to use it
anyway.
SAP HANA
To use a SAP HANA database, enter 2, and then enter the path of your
HANA HOME directory.

Tip: The HANA HOME directory must contain a Linux client for SAP
HANA. If it does not, the following message appears: expected to
find libodbcHDB.so in <HANA_HOME_directory>.

Other
To use a supported database other than Oracle or SAP HANA (PostgreSQL,
for example), enter 3 and press ENTER.

12. After you specify your database server, the Content Server installation begins.
The terminal shows files being copied to the <Content_Server_Home> directory.
When the installation completes, the following message appears:
Open Text Content Server sucessfully installed.
Please ensure that you make the following mappings in your HTTP server:

Document Directory Mappings

---------------------------

From Directory Name : OTCSsupport

To Directory Path : /usr/local/contentserver/support

CGI-BIN Mappings
----------------

From Directory Name : OTCS

LLESCOR240100-IGD-EN-01 Installation Guide 71

Chapter 5 Install Extended ECM on the Operating System

To Directory Path : /usr/local/contentserver/cgi

Would you like to start Content Server now? [Y]:

13. Make a note of the directory mappings and then type N so that Content Server
does not start right away.

Important
If there are required Updates and patches that you need to apply to
Content Server to complete the installation, do not start the Content Server
services at this point. If you do not have any Updates or patches to apply,
type Y when you are prompted to start Content Server.

14. To complete the installation of Content Server on Linux, follow the instructions
at “Apply Updates and Patches and Start the Content Server Processes”
on page 73.

Unattended Installation of Content Server on Linux

To perform an unattended installation of Content Server on Linux, provide the
answers to the installer prompts in a file, and then pass the contents of the file to the
installer when you execute setup.

For example, create a file called installParamsFile that contains the answers to the
Content Server installer prompts, and run the installation using this command: ./
setup < installParamsFile.

If the installParamsFile has the following content, it will install an instance of

Content Server in the /usr/opentext/cs directory that uses the default ports for the
Content Server services and uses an Oracle Database that has a SID of oracle. At the
conclusion of the installation, the installer will start Content Server.
Y
/usr/opentext/cs
Y
Y
2099
5858
img
/tmp
1
oracle
Y

72 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 5.2. Install Content Server on Linux

5.2.3 Apply Updates and Patches and Start the Content

Server Processes
To complete the installation of Content Server, you may need to apply an Update
and one or more patches to Content Server before you start the Content Server
processes.

Tip: Consult the Content Server Release Notes for information on required
Updates and patches.

To apply Updates and Patches and start the Content Server processes

1. If an Update is available for your version of Content Server, apply the latest
Content Server Update. For more information on applying Content Server
Updates, see OpenText Extended ECM - Upgrade Guide (LLESCOR-IUP).
When you have finished installing the Content Server Update, copy the files
from the <Content_Server_home>/config/config_reference/ directory to the
<Content_Server_home>/config/ directory, overwriting files as necessary. For
more information on the config_reference directory, see OpenText Extended
ECM - Upgrade Guide (LLESCOR-IUP).

Tip: For most Updates, OpenText releases an integrated installer that

installs Content Server and the Update. If you use an integrated installer,
you do not need to install an Update separately, and you do not need to
copy the files from the config_reference directory, but you do need to
apply required and recommended patches.

2. Apply any required patches. If there is more than one patch, apply each one in
ascending numerical order. Extract the contents of each patch file into the
<Content_Server_home> directory (/usr/local/contentserver/, by default),
overwriting any files, as necessary.

Note: OpenText recommends that you use System Center Manager to

update your Content Server installation. (See “Apply All Available
Patches to Content Server” on page 115.) Apply patches manually only if
the Release Notes identify a patch that must be applied before you start
Content Server for the first time.

3. Start each of the Content Server processes.

• To start the Content Server and Content Server Admin process, run ./
start_llserver in the <Content_Server_home> directory.

Tip: To start only the Content Server Admin process, run ./start_
lladmin.

LLESCOR240100-IGD-EN-01 Installation Guide 73

Chapter 5 Install Extended ECM on the Operating System

Tip: On Linux systems, there are different ways to set up Content Server
services to start automatically after restarting the computer. One method is
to add the path <Content_Server_Home>/start_llserver to the boot script
of the computer running the Content Server services. The start_llserver
script automatically starts the Content Server and Admin servers. Since
you need to log in as the superuser root to make changes to the boot script,
you may need to ask your system administrator to set this up for you.

74 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

Chapter 6
Configure Extended ECM

You have configured your web server or application server to run Content Server
(“Configure the Web Server to Run Extended ECM“ on page 35), installed Content
Server on the operating system (“Install Extended ECM on the Operating System“
on page 47) and started it for the first time. Now you are ready to configure Content
Server for first use.

Note: This chapter explains how to configure Content Server interactively

using the Content Server Administration pages. You can also install and
configure Content Server automatically using OpenText™ System Center
Manager. System Center Manager installs, configures, patches, and updates
multiple OpenText software applications. For more information, see OpenText
System Center Manager - Installation and Configuration Guide (SYSCM-IGD).

6.1 The Content Server Administration Page

To perform the initial configuration of Content Server, open the Content Server
Administration page, and log on as Admin using its default password of livelink.

The Content Server Administration page is the starting point for most tasks you
perform as a Content Server administrator. Under normal circumstances, it opens to
a number of sections containing Content Server pages, and you can decide your next
step based on the task at hand. The first time you open it, however, is different. You
are presented with a series of pages, and you are prompted to enter the initial
configurations that allow Content Server to operate.

To open the Content Server Administration page, use one of the following methods:

• On Windows, click Start, point to Programs, point to the program folder name
that was entered for Content Server (the default is OpenText Content Server),
and then click Content Server Administration.
• Open the following URL:
<protocol>://<server>:<port>/<URL_prefix>/cs[.exe]?func=admin.index
where:

– <protocol> is either HTTP or HTTPS.

– <server> is the name of the server that runs Content Server.
– <port> is the port on which your web server listens. It is not required if you
are using the default port for HTTP (80) or HTTPS (443).
– <URL_prefix> is the name mapped to the <Content_Server_Home>/cgi/ folder
of the new version of Content Server.

LLESCOR240100-IGD-EN-01 Installation Guide 75

Chapter 6 Configure Extended ECM

– The .exe extension is not used for Linux or when Content Server works with
an application server.
Windows
Use cs.exe.
Linux
Use cs.

Example:

Windows
On Windows, using Microsoft IIS, enter a URL similar to the following: http://server.
domain.com/OTCS/cs.exe?func=admin.index

Linux
On Linux, using Apache Tomcat, enter a URL similar to the following: http://server.
domain.com:8080/otcs/cs?func=admin.index

6.2 Configure Server Parameters

The first step in configuring Content Server is to set some basic settings on the
Configure Server Parameters and Select Default Metadata Language
administrative pages.

Configure Basic Server Parameters

You can modify the following settings for Content Server on the Configure Server
Parameters page:

• In the Web Administrator area:

– Password
The first time you open the Configure Server Parameters page, you must set
a Web Administrator password.
The Web Administrator password is the password that you use to access the
Content Server Administration page:

○ If Content Server cannot connect to its database.

○ If Content Server cannot connect to OpenText Directory Services.

It is not the same as the password of the Admin user.

When Content Server is able to connect to its database and to OTDS, you do
not need to use the Content Server Administrator password to access the
Content Server Administration page. Instead, your user ID requires a suitable
usage privilege (either the Web Admin usage privilege or a Business
Administration usage privilege). In addition, to see an Admin global menu
that provides a link to the Content Server Administration page, you require
the Show Admin Menu usage privilege. For more information on these and

76 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.2. Configure Server Parameters

other usage privileges, see OpenText Content Server Admin Help - System
Administration (LLESWBA-H-AGD).
Content Server may prompt you to provide the Web Administrator password
if you perform an important administrative action, such as changing the
Content Server database. For this reason, the Web Administrator password
should only be known by a small set of trusted system administrators.
– Email
If you provide an email address for the Administrator, a link to the address
appears on the Content Server sign in page.
• In the System Configuration area:

– Site Name
The Site Name is displayed throughout Content Server. The site name should
be a simple, user friendly name. The default Site Name is Content Server.
– Upload Directory
The Upload Directory parameter is used to restrict the location from which
Content Server accepts Documents for upload. The directory specified in this
field must be accessible to both the web server and the Admin server.
OpenText recommends that you specify the full path to the directory in this
field.

Important

○ OpenText strongly recommends that you specify an upload

directory. Leaving this field blank poses a security risk. It can also
prevent you from applying a license file. See OpenText Content Server
Admin Help - System Administration (LLESWBA-H-AGD).
○ Content Server blocks uploads from the following directories (and all
of their subdirectories). If your web server’s default directory is set to
one of the following, and you have not configured a Content Server
upload directory, Content Server prevents files from being uploaded.
Windows
<Drive>:\Windows\
<Drive>:\Program Files\
<Drive>:\Program Files (x86)\
<Drive>:\ProgramData\

Linux
/etc/
/boot/
/usr/bin/
/usr/sbin/

– Support Directory, the mapping name for the support/ directory.

LLESCOR240100-IGD-EN-01 Installation Guide 77

Chapter 6 Configure Extended ECM

The mapping name, also known as the virtual directory alias, is mapped to the
support/ directory during the installation of Content Server. By default, the
support/ directory is located at the root installation level: <Content_Server_
home>/support. It is normally not necessary to change the mapping name;
however, if you modify it, you must make the change in Content Server and
the web server.
The default mapping name is /img/.

Note: You must type a forward slash (/) before and after the mapping
name.
– Syndication
Syndication is a collection of many Content Server installations in different
locations, all connected and communicating with each other.

Important
OpenText recommends that you do not edit this section unless you are
following the directions in “Appendix B – Installing Content Server as a
Syndication Environment“ on page 175. A Content Server Syndication
environment needs to be installed by following a specific set of steps, as
more fully documented in the OpenText Content Server - Syndication
Administration Guide (LLESQDS-AGD).

In general, you begin to set up a Content Server Syndication environment by

selecting Enable. Once enabled, you set whether this Content Server
installation is designated as your primary installation or as a remote
installation of Content Server. The Site ID field requires a unique number
that identifies this installation in the Content Server Syndication environment.
• In the User Interaction area:

– Keyboard
Enhanced Keyboard Accessibility Mode permits the user interface to be
manipulated using keyboard commands. However, certain features that
depend on Java, such as the Text Editor, are disabled when Enhanced
Keyboard Accessibility Mode is used. This option is disabled by default.
When you enable this option, all users are required to use this mode.
– User Pages
This parameter allows you to select one of the following pages, which is
where users land when they first sign in:

○ Enterprise Workspace, which displays your organization's home page

when users sign in.
○ My Workspace, which displays each user's Personal Workspace when
users sign in.
○ About Content Server, which displays the About Content Server page
when users sign in.

78 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.2. Configure Server Parameters

Note: If you select About Content Server, you need to decide if

users should be required to sign in before they view the page. If you
want to require that your users sign in, select the Require Log-in to
Access the About Page box. This option is cleared by default.
○ Personal Frontpage, which displays the user's individual frontpage. This
page can also be viewed by the user by selecting Personal > Personal
Frontpage from the global menu bar.
○ Pulse, which displays the Content Server Pulse page.
– Mail Separator
You can change the character that is inserted between multiple recipient
addresses in message composition windows. If your organization
predominately uses Microsoft email applications, you should select semi-
colon ";" for the address separator. For other email applications, you might
need to select comma ",".
• In the Connection Settings area:

– Response Buffering
This setting reduces the amount of time the Server must dedicate itself to
downloading and opening documents. By default, Response Buffering is
enabled. When Response Buffering is enabled, the Server's responses are
buffered to the web server, which then assumes control of sending the
contents to the browser. This allows the available server threads to move on
to other requests more quickly. From an end-user perspective, fetching and
downloading documents will still take the same amount of time.
– Socket Timeouts
Socket Timeout settings govern socket communications on the current
Content Server instance. In a clustered installation of Content Server, it is
possible to set different network socket timeout values on different Content
Server instances.

○ Enable Send Timeouts sets the maximum time in seconds that Content
Server will wait for a receiver response after sending data. The default
value is 30 seconds.
○ Enable Receive Timeouts sets the maximum time in seconds that Content
Server will wait for data from a sender. The default value is 2 seconds.

Set each value to a positive integer greater than zero. To disable either
network socket timeout, set its value to Never.
– Threads
This setting defines the number of threads used by Content Server. The
default Number of Threads is 8. You may want to increase or decrease the
number of threads, depending on:

○ The speed of individual request execution times.

○ The amount of capacity needed.

LLESCOR240100-IGD-EN-01 Installation Guide 79

Chapter 6 Configure Extended ECM

○ Your usage profile.

○ The availability of CPU and RAM resources on your Content Server
hardware.

The optimum number of threads depends on the characteristics of your

Content Server environment. Items that can be considered include:

○ The number, speed, and architecture (for example, NUMA) of the CPUs.
○ The amount of physical memory in your servers.
○ The speed of network connections.
○ Whether storage is local or accessed over the network.

It also depends on the usage profile for your Content Server instance (the
frequency and variety of the types of user requests).
To determine the number of threads that your server can support, OpenText
recommends that you experiment with different thread values. You can
measure your results by using Content Server logs and utilities that are
available from the operating system. For more information, see OpenText
Content Server Admin Help - System Administration (LLESWBA-H-AGD).

Note: Do not set the number of threads higher than the number of
connections supported by your RDBMS.
– Sessions
The Maximum number of sessions used to cache user login information
setting defines the maximum number of user logon program contexts cached
on a server thread. (In Content Server, a program context is a data structure
that stores user and application values.) The default value of the number of
program contexts is set to 100. When the maximum number of program
contexts is reached, the oldest user session is dropped. User logon program
contexts are cached independently on each thread. When a user returns to a
thread after their logon information has been dropped from the cache, it will
take slightly longer to execute their next request. The lower the maximum
number of program contexts, the less memory the server must dedicate to
tracking user program contexts on each thread. The larger the number,
however, the less often the server will drop user logon information from the
cache. A server's memory consumption can be large for a system running
many threads. You may want to try different values for the maximum
number of program contexts, depending on how many users are accessing
your Content Server system.
– Server Logging Options
When you install Content Server, you can use this setting to enable or disable
server logging during installation. By default, logging is enabled, and Content
Server generates thread and connect logs at the Info level.
Once the installation is complete, Content Server stops the generation of
thread and connect logs, and this setting is no longer available on the

80 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.2. Configure Server Parameters

Configure Server Parameters page. To configure log settings after

installation, use the Configure Log Settings page. For more information, see
OpenText Content Server Admin Help - System Administration (LLESWBA-H-
AGD).

To Configure Basic Server Parameters

To continue with the installation, you need only enter a Content Server
Administrator password, but OpenText recommends that you also set an upload
directory during the initial configuration of Content Server. You can configure the
other settings on this page at this time, or return to it later to set them.

To configure basic Content Server parameters:

1. In your web browser, open the Content Server Administration page.

Because you have not yet configured Content Server, Content Server redirects
you to the Configure Server Parameters page.

2. In the Web Administrator area, enter a password in the Administrator

Password and Verify Password boxes.

Tips

• This sets the password that you must enter to access the Content Server
Administration page if Content Server cannot connect to its database or
to the instance of OpenText Directory Services that manages its users.
Do not confuse this password with the password of the Admin user.
• Record the new Content Server Administrator password on
Section 10.3: “Content Server Installation Worksheet” on page 173.

3. Set any other parameters as determined by your installation plans.

4. Set an upload directory, unless you have determined that you do not want to
use one in your Content Server deployment.

Note: OpenText recommends that you specify an upload directory.

Leaving this field blank poses a security risk, and can prevent you from
applying a license file. (See “Apply an Extended ECM or Content Server
License File” on page 110.)

5. At the bottom of the page, click Save Changes. Your selections are saved and
the Select Default Metadata Language page opens.

6. On the Select Default Metadata Language page, select a language, and then
click Continue.

LLESCOR240100-IGD-EN-01 Installation Guide 81

Chapter 6 Configure Extended ECM

6.3 Create the Content Server Database

For a new installation, you now create a new empty database for use with Content
Server.

Note: You can also connect your new Content Server installation to an existing
Content Server database. For information on doing this, follow the instructions
in the OpenText Extended ECM - Upgrade Guide (LLESCOR-IUP).

This section of the Installation Guide describes how to create a Content Server
database on the various supported database platforms. Proceed by following the
instructions for your database server.

6.3.1 Create a Microsoft SQL Server Content Server Database

You can connect to an on-premises Microsoft SQL Server or to Azure SQL.

Create a Microsoft SQL Server Content Server Database

Complete the following instructions to set up a new Content Server database on
Microsoft SQL Server.

To create a new SQL Server database:

1. On the Database Administration page, click Create New Database.

2. On the Create New Database page, select SQL Server, and then click Continue.
3. On the Microsoft SQL Server Administrator Log-in page, log onto SQL Server:

a. In the Server Name box, type the Microsoft SQL Server alias.

Notes

• The server alias is typically the name of the computer where the
Microsoft SQL Server resides. You may need to consult your
Microsoft SQL Server administrator to obtain this information.
• If your installation of Microsoft SQL Server does not run on the
default port (1433), enter the SQL Server port after the server alias,
separated by a comma, with no space.
Example: For a SQL Server installation with an alias of MySQLsrv running
on port 1456, enter the following in the SQL Server Name box:
MySQLsrv,1456
b. In the Master Database Name box, type the name of the system database
(usually master).
c. In the System User box, type the Microsoft SQL Server administrator user
name (usually sa).
d. In the System Password box, type the password of the Microsoft SQL
Server administrator user.

82 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.3. Create the Content Server Database

e. Click Log-in.
4. On the Create Content Server Tables page, click the Microsoft SQL Server
Maintenance link.
5. On the Microsoft SQL Server Maintenance page, in the Create a New
Microsoft SQL Server Database section, create a SQL Server database:

a. In the Database Name box, type the name that you want to assign to the
database. For example, CSprod.

Important
Do not start the name with a number. SQL Server allows this, but
Content Server does not.
b. In the Data File Specification box, type a path and file name. For example,
C:\Store\CSprod.mdf.
c. In the Data File size box, type a size in megabytes for the data file. The
minimum is 5 MB.

Tip: You can estimate an appropriate data file size using the following
formula:
# documents X # versions X # KB avg-doc-size = tablespace size
d. Optional Enable Automatically extend data file.

e. In the Log File Specification box, type a path and file name. For example,
C:\Store\CSprod.ldf.
f. In the Log File Size box, type a size in megabytes for the file (minimum is 5
MB). Use the Data File Size example as a guide.
g. Optional Enable Automatically extend log file.

h. Click Create Database.

6. In the Create A New User section, create a SQL Server user for Content Server:

a. In the User Name box, type a name for the SQL Server user who will own
the database. If the database user will log on to SQL Server using Windows
Authentication, enter the name of the Windows user that runs the Content
Server service.
In the Authentication Method section, select Windows Authentication or
SQL Server Authentication

Windows Authentication
If you select Windows Authentication, you do not specify the
Password.
SQL Server Authentication
Enter the user’s password in the Password and Verify Password boxes.
Note: The password must not contain a semicolon (;). Using a
password that contains a semicolon causes Microsoft SQL Server
to issue an Invalid connection string attribute error message.

LLESCOR240100-IGD-EN-01 Installation Guide 83

Chapter 6 Configure Extended ECM

b. In the Database Name menu, select the database that you created in step
step 5.
c. Click Create User.

Tip: Record the name and path of the data and log files, and the name
and password of the SQL Server user who owns the Content Server
database on Table 10-4: “Microsoft SQL Server Worksheet (Windows
only)” on page 171.

7. Click Return to previous page.

8. On the Create Content Server Tables page, create the Content Server tables:

a. In the SQL Server Database menu, select the Microsoft SQL Server
database that you created in step step 5.
b. In the Credentials section, select Windows Authentication or SQL Server
Authentication

Windows Authentication
If you select Windows Authentication, there is no need to specify the
User Name or Password. The name of the Windows user that runs the
Content Server service is automatically selected.
SQL Server Authentication
If the Content Server database user logs on to SQL Server using SQL
Server Authentication, select the Microsoft SQL Server user that you
created in step step 6, and enter the user’s password in the Password
box.

Tip: The SQL Server Database, Microsoft SQL User Name, and
Password boxes are automatically populated with the data you
provided on the Microsoft SQL Server Maintenance page.

c. Optional Select External Document Storage if you want Content Server to

store documents and other items outside the database, and enter the
absolute path of the folder where you want Content Server to store items in
the adjacent box.

Note: The directory that you enter must exist and the Content Server
user must have permission to write to it.
d. Click Create Tables.

9. The Content Server Administrator User Log-in page appears. Enter the
password of the Admin user, and then click Log-in.

Tip: The default password of the Admin user is livelink. Once you have
completed the setup, OpenText recommends that you change it. See
“Change the Password of the Admin and System Support Users”
on page 137.

84 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.3. Create the Content Server Database

The Add: Admin Server page appears. Proceed to “Create an Admin Server”
on page 91 to continue the installation.

Create an Azure SQL Content Server Database

Content Server cannot create a new database in a Microsoft Azure SQL database. To
create the Content Server database, first create an empty database and a database
user account on the Microsoft Azure Portal, then follow the instructions below to
create the Content Server tables in that database.

For recommendations on preparing a SQL Server database on Azure for use with
Content Server, see “Microsoft SQL Server on Microsoft® Azure®” on page 30.

To create a new SQL Server database:

1. On the Database Administration page, click Create Tables in Existing

Database.

2. On the Select RDBMS Type page, enable Microsoft SQL Server.

3. On the Specify Content Server Database Owner page, enter the connection
parameters, as follows, and then click Connect:

Tip: The SQL Server name, Microsoft SQL Server user name, and SQL
database name can be found in the Connection strings that appear in the
Essentials of the SQL Server database server on your Azure dashboard.

SQL Server Name

Type the fully qualified domain name of the SQL Server database server
deployed on Azure. For example, enter csdb.database.windows.net.
Microsoft SQL Server User Name
Enter the name of a user with administrative privileges. OpenText
recommends that you use the name of the Server admin login that was
created when the virtual SQL Server database server was created.
Password
Enter the password of the user that appears in the Microsoft SQL Server
User Name box.
SQL Database Name
Enter the name of the empty database that you created for Content Server.
External Document Storage
The External Document Storage box does not appear until you complete
the above boxes and click Connect. Enable External Document Storage if
you want Content Server to store documents and other items outside the
database, and enter the absolute path of the folder where you want Content
Server to store items in the adjacent box.

Click Create Tables to create the tables in the Content Server database.

LLESCOR240100-IGD-EN-01 Installation Guide 85

Chapter 6 Configure Extended ECM

4. The Content Server Administrator User Log-in page appears. Enter the
password of the Admin user, and then click Log-in.

Tip: The default password of the Admin user is livelink. Once you have
completed the setup, OpenText recommends that you change it. See
“Change the Password of the Admin and System Support Users”
on page 137.

The Add: Admin Server page appears. Proceed to “Create an Admin Server”
on page 91 to continue the installation.

6.3.2 Create an Oracle Content Server Database

Complete the instructions in this section to set up a new Content Server database on
Oracle Database.

To create a new Oracle database:

1. On the Database Administration page, click Create New Database.

2. On the Select RDBMS Type page, select Oracle Server, and then click
Continue.

Tip: If the option to create an Oracle database does not appear on the
Select RDBMS Type page, ensure that you have installed Oracle client
software on the Content Server computer.

3. On the Oracle Server Administrator Log-in page, log on to Oracle :

a. In the System User Name box, type the Oracle administrator user name.

Tip: The Oracle administrator user name is usually system.

b. In the Password box, type the password for the Oracle administrator user.
c. In the Service Name field, type the service name (database alias) of Oracle
Server.

Tip: The service name is typically the same as the host name of the
computer on which Oracle Server is installed. You can find the service
name (database alias) in the tnsnames.ora file. You may need to
consult your Oracle administrator to obtain this information.
d. Click Log-in.

4. On the Create Content Server Tables page, click the Oracle Server
Maintenance link.

5. On the Oracle Server Maintenance page, in the Create New Tablespace

section, create an Oracle tablespace.

a. In the Tablespace Name box, type a unique name for the tablespace.

86 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.3. Create the Content Server Database

Tip: You can find out which tablespace names are already in use by
looking at the Default Tablespace menu in the Create New User
section of this page.
b. In the File Specification box, type the absolute path of the tablespace data
file that you want to create. For example, C:\oracle\database\filename.
ora or /usr/oracle/database/filename.dbf.

The directory that you specify must already exist, and the operating system
user that runs Oracle Server must have permission to write to it.
c. In the Size box, type a size in megabytes for the tablespace data file,
following the guidelines on the Oracle Server Maintenance page. The
minimum is 5 MB.

Tip: You can estimate an appropriate size using the following

formula:
documents X versions X KB-per-avg-doc-size = tablespace-size
d. Optional Enable Automatically extend tablespace.
e. Click Create Tablespace.

6. In the Create New User section, create an Oracle user for Content Server:

a. In the User Name box, type a name for the Oracle user who will own the
tables.
b. In the Password and Verify Password boxes, type a password for this user.
c. In the Default Tablespace menu, select the name of the tablespace in which
you want to create the tables of the new Content Server database.

Note: Record the Content Server user name, password, and tablespace on
the Table 10-2: “Oracle Database Worksheet” on page 170.

7. Click Return to previous page.

8. On the Create Content Server Tables page, create the Content Server tables:

a. In the User Name box, enter the Oracle user that you created in the
previous steps.
b. In the Password box, enter the password of the Oracle user.

Tip: The User Name and Password boxes are automatically

populated with the data you provided on the Oracle Server
Maintenance page.
c. Optional Enable External Document Storage if you want Content Server to
store documents and other items outside the database, and enter the
absolute path of the folder where you want Content Server to store items in
the adjacent box.

Note: The directory that you enter must exist and the Content Server
user must have permission to write to it.

LLESCOR240100-IGD-EN-01 Installation Guide 87

Chapter 6 Configure Extended ECM

d. Click Create Tables.

9. The Content Server Administrator User Log-in page appears. Enter the
password of the Admin user, and then click Log-in.

Tip: The default password of the Admin user is livelink. Once you have
completed the setup, OpenText recommends that you change it. See
“Change the Password of the Admin and System Support Users”
on page 137.

The Add: Admin Server page appears. Proceed to “Create an Admin Server”
on page 91 to continue the installation.

6.3.3 Create a PostgreSQL Content Server Database

Complete the instructions in this section to set up a new Content Server database on
PostgreSQL. You can connect to an on-premises deployment of PostgreSQL or to an
instance of PostgreSQL mounted on Google Cloud Platform.

To create a PostgreSQL database:

1. On theDatabase Administration page, click Create New Database.

2. On the Select RDBMS Type page, click PostgreSQL Server, and then click
Continue.
3. On the PostgreSQL Server Administrator Log-in page, log onto PostgreSQL.

a. Enter the host name or IP address of a PostgreSQL server in the

PostgreSQL Server Name box. For example, enter PostgreSQLserver.
domain.com or 192.168.10.20.
b. Enter the name of a PostgreSQL user with administrator privileges in the
System User box.
c. Type the password of the system user in the System Password box.
d. Click Log-in.
4. On the Create Content Server Tables page, click the PostgreSQL Server
Maintenance link.
5. In the Create a New PostgreSQL Database section, create a PostgreSQL
database:

a. In the Database Name box, enter a name for your Content Server database.
b. Select a PostgreSQL tablespace from the Tablespace menu, or accept the
default: pg_default.
c. Click Create Database.
6. In the Create A New User section, create a PostgreSQL database user for
Content Server:

a. Type the name of the new PostgreSQL user in the User Name box.

88 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.3. Create the Content Server Database

b. Type a password for the new PostgreSQL user in the Password and Verify
Password boxes.

c. In the Database Name box, select the name of the database that you created
in the previous step.

d. Click Create User.

Note: Record the user name, password, and database name on the
Table 10-3: “PostgreSQL Worksheet” on page 170.

7. Click Return to previous page.

8. Create the tables in the PostgreSQL database.

a. In the PostgreSQL Database box, select the name of the PostgreSQL

database that you created in the steps above.

b. In the PostgreSQL User Name box, select the name of the PostgreSQL user
that is associated with the PostgreSQL database that you selected.

c. Enter the password of the PostgreSQL user in the Password box.

Tip: The PostgreSQL Database, PostgreSQL User Name and

Password boxes are automatically populated with the data you
provided on the PostgreSQL Server Maintenance page.

d. Optional Enable External Document Storage if you want Content Server to

store documents and other items outside the database, and enter the
absolute path of the folder where you want Content Server to store items in
the adjacent box.

Note: The directory that you enter must exist and the Content Server
user must have permission to write to it.

e. Click Create Tables.

9. The Content Server Administrator User Log-in page appears. Enter the
password of the Admin user, and then click Log-in.

Tip: The default password of the Admin user is livelink. Once you have
completed the setup, OpenText recommends that you change it. See
“Change the Password of the Admin and System Support Users”
on page 137.

The Add: Admin Server page appears. Proceed to “Create an Admin Server”
on page 91 to continue the installation.

LLESCOR240100-IGD-EN-01 Installation Guide 89

Chapter 6 Configure Extended ECM

6.3.4 Create an SAP HANA Content Server Database

Complete the instructions in this section to set up a new Content Server database on
SAP HANA.

Important
Install the SAP HANA database client on your Content Server computer before
you connect to the SAP HANA server to create a new Content Server database.

To create an SAP HANA database:

1. On the Database Administration page, click Create New Database.

2. On the Select RDBMS Type page, click SAP HANA, and then click Continue.

3. On the SAP HANA Server Administrator Log-in page, log onto HANA.

a. Enter the host name and port, or IP address and port, of an SAP HANA
server in the SAP HANA Server (IP:Port) box. For example, enter
HANAserver.domain.com:30115 or 192.168.10.20:30115.
b. Enter the name of an SAP HANA user with administrator privileges (for
example, SYSTEM) in the System User box.
c. Type the password of the system user in the System Password box.
d. Click Log-in.

4. On the Create Content Server Tables page, click the HANA Server
Maintenance link.

5. On the SAP HANA Maintenance page, in the Create A New User section,
create a SAP HANA database user for Content Server. When you create an SAP
HANA user, a database schema that has the same name as the user is also
created.

a. Type the name of the new SAP HANA user in the User Name box.
b. Type a password for the new SAP HANA user in the Password and Verify
Password boxes.
c. Click Create User.

Note: Record the user name, password, and schema name (which has the
same name as the user) on the Table 10-1: “SAP HANA Worksheet”
on page 169.

6. Click Return to previous page.

7. Create the tables in the HANA database.

a. In the SAP HANA Schema box, select the name of the SAP HANA schema
that you created in the above steps.
b. In the HANA User Name box, select the name of the SAP HANA user that
is associated with the schema.

90 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.4. Create an Admin Server

c. Enter the password of the user in the Password box.

Tip: The HANA User Name and Password fields are automatically
populated with the data you provided on the SAP HANA
Maintenance page.
d. Optional Enable External Document Storage if you want Content Server to
store documents and other items outside the database, and enter the
absolute path of the folder where you want Content Server to store items in
the adjacent box.

Note: The directory that you enter must exist and the Content Server
user must have permission to write to it.
e. Click Create Tables.
8. The Content Server Administrator User Log-in page appears. Enter the
password of the Admin user, and then click Log-in.

Tip: The default password of the Admin user is livelink. Once you have
completed the setup, OpenText recommends that you change it. See
“Change the Password of the Admin and System Support Users”
on page 137.

The Add: Admin Server page appears. Proceed to “Create an Admin Server”
on page 91 to continue the installation.

6.4 Create an Admin Server

Every Content Server deployment requires at least one Admin server. The first
Admin server that you create is the default Admin server, AdminServer-01, which
has special duties, including communicating with all of the Content Server front-end
instances.

On the Add: Admin Server page, you create the default Admin server.

To create the default Admin server:

1. In the Admin Server area of the Add: Admin Server page, configure the new
default Admin server:

a. In the Alias Name box, accept the default alias, AdminServer-01. (This
setting cannot be changed.)
b. In the Host Name box, the name of the Content Server host computer
appears by default. (The default Admin server must be installed on the
same computer as Content Server.) You can accept the default Host Name,
enter localhost, or enter the IP address of the Content Server host
computer. OpenText recommends that you enter the fully qualified domain
name of the Content Server server computer in the Host Name box.
c. Accept the default Port Number (5858) or specify a different port.
d. Optional Add a Description of the new default Admin server.

LLESCOR240100-IGD-EN-01 Installation Guide 91

Chapter 6 Configure Extended ECM

2. In the File Cache area of the Add: Admin Server page, the default Admin
server is configured to use a File Cache.

Tip: For the default Admin server, the Enable File Cache option is
selected by default and cannot be disabled. If you create additional Admin
servers, you can opt not to create a File Cache.

3. Click Add. The Create New Enterprise Data Source page appears.

6.5 Create the Enterprise Data Source

At this point in the installation of Content Server, you create the processes that
create the Enterprise index. Once created, the Enterprise index is continuously
updated to reflect the latest changes in the Content Server database. For more
information about the Enterprise index and indexing, see OpenText Content Server
Admin Help - Search Administration (LLESWBS-H-AGD).

To create an Enterprise index:

1. On the Create New Enterprise Data Source page, type a unique identifier for all
the system objects that are associated with this indexing data flow in the
Processes Prefix box or accept the default Processes Prefix (Enterprise).

Note: This identifier appears in Content Server as:

• The display name for objects associated with this index on the Content
Server System page.
• The index's search slice in the Scope list on the Content Server Search
page.

2. Optional To specify the number of partitions into which this index should be
divided, type a number in the Partitions box.

3. In the Port box, accept the default value (8500) or type a value representing the
first of a series of 12 port numbers on which you want the processes that are
associated with this data source to listen. For example, if you enter 2500, the
ports 2500 through 2511 are used.

Note: The port number that you specify and (at least) the next 11
consecutive port numbers must be unused in your system. The number of
consecutive port numbers that you require depends on the number of
partitions that you specify in the Partitions box. Creating an Enterprise
index requires eight port numbers, and for each partition, four additional
port numbers. Valid values range from 1025 to 65535.

4. In the Producer Information area:

a. In the Host menu, select the Content Server Admin server on which you
want the Enterprise Extractor process to run or accept the default (the local
machine that you are installing Content Server on).

92 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.5. Create the Enterprise Data Source

b. In the Write Base Directory box, type the network name or path (relative to
the Content Server Admin server on which the Extractor runs) of the
directory where you want the Enterprise Extractor process to write data. By
default, the write directory is the <Content_Server_Home>/index/
enterprise/ directory on the default Content Server Admin server.

Tip: The Admin server that you assign to manage the Enterprise Data
Source must be running and available. A green OK icon in the
Producer Information and Intermediate and Consumer Information
sections indicates that it is. If you do not see the green OK icon, follow
the instructions that appear in red to ensure that the Admin server is
running and available. Once you have resolved any underlying
problem, click Check Host Admin Server to perform a new
verification of its availability.
If you are installing a first instance of Content Server, the Admin
server and Content Server services are both running on the local host
computer. See “Content Server Services” on page 12.

5. In the Intermediate and Consumer Information section:

a. In the Host menu, select the Admin server on which you want the
Document Conversion and Update Distributor processes to run. By default,
these processes run on the default Content Server Admin server.
b. In the Read Base Directory box, type the network name or path (relative to
the Content Server Admin server on which the Document Conversion
process runs) of the directory where you want the Document Conversion
process to read data. This directory must be the same directory as the write
base directory that you specified in the Producer Information section.
c. In the Write Base Directory box, type the network name or path (relative to
the Content Server Admin server on which the Document Conversion
process runs) of the directory where you want the Document Conversion
process to write converted data.

Note: For fastest performance, OpenText recommends that you

choose a directory on a drive that is on the same computer as the
Admin server that runs the Document Conversion process.

6. To start the data flow processes as soon as they are created, leave Start
Processes in Data Flow enabled (the default option). However, if you intend to
make configuration changes to your search environment before you use it, you
may prefer to clear this option.

7. Click Create Processes.

The Status page now appears and updates the page as Content Server creates
processes in the Enterprise Data Source.

8. When the following message appears, click Continue:

All processes have been created successfully
Please click the Continue button to complete the setup

LLESCOR240100-IGD-EN-01 Installation Guide 93

Chapter 6 Configure Extended ECM

9. The Install Modules page appears. Continue the installation by following the
instructions in “Install Optional Content Server Modules” on page 94.

6.6 Install Optional Content Server Modules

After you create the Content Server database, the Install Modules page appears.
You can install optional modules now or after you complete the initial configuration
of Content Server.

If you do not have optional Content Server modules to install, click Continue on the
Install Modules page and proceed to “Configure Storage Providers” on page 97 to
continue the Content Server installation.

You install a module in two stages:

• First, you install the software on your operating system. At the completion of the
operating system installation, the module software components are located in the
<Content_Server_Home>/staging/ folder of your Content Server installation. To
install a module on your operating system, follow the instructions in “Install
Modules on the Operating System” on page 94
• Next, you install the software on Content Server. At the completion of the
Content Server installation, the module software components are located in the
<Content_Server_Home>/module/ folder. To install a module on Content Server,
follow the instructions in “Install Modules on Content Server” on page 96.

6.6.1 Install Modules on the Operating System

This section describes the first stage of installing a module. The second stage is
described in “Install Modules on Content Server” on page 96.

Depending on the operating system on which Content Server is running, proceed to

one of the following sections:

Install Modules on Windows

You perform the first stage of a Content Server module installation using a Windows
Installer. This program loads the module's files in a subfolder of the <Content_
Server_Home>/staging/ folder.

To install a Content Server module on Windows:

1. On the host computer where Content Server is installed, run the module's
module_name.exe file.

2. In the Welcome window, click Next.

If the installer detects more than one Content Server instance on the host
computer, the Select Content Server Service window lists their Windows
service names.

94 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.6. Install Optional Content Server Modules

3. Select the Content Server installation to which you want to add the module.
(You can select only one.)

4. Click Next.
The installation program copies files to the <Content_Server_Home>\staging\
folder, and then informs you that this part of the installation is complete.

5. Click OK, and repeat steps step 1 to step 4 for each module you want to install.
The modules now reside in the <Content_Server_Home>\staging\ folder. Later
in the installation process, you integrate them into your Content Server system.
See “Install Modules on Content Server” on page 96.

Note: If you have a clustered installation of Content Server, complete the

above procedure on each Content Server instance in the cluster.

If your Content Server system uses languages other than English, install the
language packs for the module that you installed.

To install a module language pack on Windows, extract all files in the module
language pack file to the <Content_Server_home> folder. If you are prompted to
confirm that you want to merge the contents of the compressed folder, click Yes.

Install Modules on Linux

For Linux versions of Content Server modules, you perform the first stage of an
installation using a zipped TAR archive file. The extraction of this TAR file loads the
module's files in a subdirectory of the <Content_Server_Home>/staging/ directory.

Extract the modules logged on as the Content Server user.

To install a Content Server module on Linux:

1. Copy the module's <module_name>.tar file to <Content_Server_Home>/

staging/ directory of the Content Server installation to which you want to add
the module.

2. Using the tools installed with your version of Linux, unzip and unpack the
module. For example, type tar xvf <module_name>.tar
All necessary files are extracted in the <Content_Server_Home>/staging/
directory.

3. Repeat the previous steps for each module that you want to install.
The modules now reside in the <Content_Server_Home>/staging/ directory.
Later in the installation process, you integrate them into your Content Server
system. See “Install Modules on Content Server” on page 96.

If your Content Server system uses languages other than English, install the
language packs for the module that you installed.

LLESCOR240100-IGD-EN-01 Installation Guide 95

Chapter 6 Configure Extended ECM

To install a module language pack on Linux, extract all files in the module language
pack file to the <Content_Server_home> folder. If you are prompted to confirm that
you want to merge the contents of the compressed folder, click Yes.

6.6.2 Install Modules on Content Server

This section describes how to complete the installation of optional modules on
Content Server. It presumes that you have done the first stage of the module
installation described in “Install Modules on the Operating System” on page 94.

The installation of Content Server modules proceeds in two stages: installation and
configuration. If any of the modules that you install changes the Content Server
database, you will see configuration pages related to the database change.
Otherwise, you will see a minimal number of configuration pages.

On the Install Modules page, you can perform the second stage of installing
optional Content Server modules.

To install optional modules on Content Server:

1. In the Installable Modules section, select each of the modules that you want to
install, and then click Install.

Note: When you enable a module that requires the installation of other
modules, Content Server automatically selects the required modules if
they have been installed on the operating system. Content Server can
install numerous modules at once, but if you want to install the modules
one at a time, install the required modules first.

2. Optional Content Server installs the modules and advances you to the next page
(usually the Configure Storage Providers page). If you want to install another
module, use your browser’s Back button to return to the Install Modules page,
and click Refresh to update the information on the page.

3. Review the information on the Configure Storage Providers page, and make
changes if necessary. (For information on the Configure Storage Providers
page, see “Configure Storage Providers” on page 97.) Click Next.

4. Optional If a module that you are installing modifies the Content Server database,
the Content Server Database Upgrade Confirmation page appears. Perform
the following steps

a. Click Perform Upgrades to initiate the database upgrade.

b. The Restart Content Server page appears. Click Restart to restart
automatically, or click Continue if you prefer to restart Content Server
using the operating system.
c. Content Server displays Restart Successful. Click Continue.
d. When the Database Upgrade Status page displays The database upgrade
has completed successfully, click Continue.

96 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.7. Configure Storage Providers

e. Content Server automatically restarts and you are returned to the Database
Upgrade Status page. Click Continue.
5. The Configure Modules page appears. Click Continue. Content Server
configures your modules.
6. Restart Content Server to commit the module configurations.

a. The Restart Content Server page appears. Click Restart to restart

automatically, or click Continue if you prefer to restart Content Server
using the operating system.
b. Content Server displays Restart Successful. Click Continue.
7. The Configure Storage Providers page appears. Proceed to “Configure Storage
Providers” on page 97.

6.7 Configure Storage Providers

Content Server Storage Providers store user files and system objects. On the
Configure Storage Providers page, you can review the Storage Providers that
Content Server has, and add new ones if you wish.

Tip: You can add Storage Providers at any time, not just during the initial
configuration of Content Server. Use the Configure Storage Providers
administration page to add Storage Providers after your initial configuration of
Content Server. Certain types of Storage Provider, for example the AWS
Storage Provider, can only be added after the initial configuration of Content
Server is complete.

For more information about Storage Providers, see the topic Storage Providers and
Storage Management in the Item Administration section of the Content Server
admin help.

Click Next on the Configure Storage Providers page to continue the installation.
After you click Next, Content Server restarts automatically to finalize the changes
that you made on the previous configuration pages. When it completes the restart,
you are automatically redirected to theConfigure OTDS Integration Settings page.

6.8 Select the OTDS Server Type

Content Server uses OpenText Directory Services to manage its users. You can
choose to use an internal instance of OTDS that is embedded in Content Server or
connect to an external OTDS server. OpenText recommends that you use an external
OTDS server for a production deployment of Content Server.

Directory Services requires a database to store its data. This is a requirement if you
are using an internal or an external version of OTDS. For more information, see
“About the OTDS database requirement” on page 98.

1. It is possible to use an internal instance of OTDS upon initial installation

and later to change to using an external OTDS server. For more

LLESCOR240100-IGD-EN-01 Installation Guide 97

Chapter 6 Configure Extended ECM

information, see OpenText Content Server - Directory Services Integration

Administration Guide (LLESDSI-AGD).

2. If you change your Content Server database or if you are upgrading

Content Server, you will be prompted to reconfigure OTDS.
If you are using an internal version of OTDS, you need to provide a
database that corresponds to the Content Server database.

About the OTDS database requirement

Directory Services requires a separately installed and configured database server to
store all OTDS data, including configuration, partitions, and user data. For
supported database servers and specific requirements for the database, see the
Directory Services Release Notes.

Important
The database username and password that you supply to OTDS during
installation requires full permissions to the OTDS database that you created.
An example of a database user with full permissions is the database owner.

OpenText recommends that the userID designated as the database owner is the
userID you enter in the Database Username field in the JDBC Parameters
window during installation.

Each of the supported databases has their own requirements for permissions
when writing to a database. Whether installing or upgrading OTDS, check
your database's documentation for those requirements.

You can use your database server to create a separate database that will be used
exclusively by OTDS. For more information, see the documentation for your chosen
database server.

Examples showing the information you need to give OTDS during installation can
be found in “Format for the Database JDBC connection string” on page 99.

If you are using OTDS with Content Server:

• You can use Content Server's database management tools to create and manage a
separate database that will be used exclusively by OTDS. For more information,
see OpenText Extended ECM - Installation Guide (LLESCOR-IGD).
• Although you can connect OTDS to the same database that you created for
Content Server, OpenText does not recommend this option because OTDS and
Content Server may have different database configuration requirements.

Note: By default, OTDS creates its tables upon first startup in a schema named
'OTDS'. In order to use the default schema of the database user instead, set the
environment variable OTDS_USEDEFAULTDBSCHEMA=true, or the JVM system
property otds.usedefaultdbschema=true.

98 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.8. Select the OTDS Server Type

Format for the Database JDBC connection string

During installation, the form in which you type information in the Database JDBC
connection string box depends on the database that you installed and configured.
See the following examples for the forms required by each supported database.

MS SQL Server

Example 6-1: A basic MS SQL Server database JDBC connection

string
jdbc:sqlserver://<hostname>:1433;databaseName=<MyDBname>

Example 6-2: An MS SQL example showing an included instance

name
jdbc:sqlserver://<hostname>:1433;instanceName=<MyInstance>;databaseName=<MyDBname>

Oracle

Example 6-3: A basic “sid” Oracle database JDBC connection string

jdbc:oracle:thin:@//<hostname>:1521:<MyDBname>

Example 6-4: A basic “service” Oracle database JDBC connection

string
jdbc:oracle:thin:@//<hostname>:1521/<MyDBname>

Example 6-5: Oracle database JDBC connection strings that require

setting the TNS_ADMIN* environment variables
If you need to set the TNS_ADMIN* environment variables, TNS_ADMIN should
specify the location of the TNSNAMES.ORA file. For example: %ORACLE_HOME%
\network\admin.
jdbc:oracle:thin:@<tns_entry>

jdbc:oracle:thin:@<network_service_name>

Example 6-6: An Oracle database JDBC connection string that uses a

connect descriptor
jdbc:oracle:thin:@<connect_descriptor>

An example of <connect_descriptor> could be:

LLESCOR240100-IGD-EN-01 Installation Guide 99

Chapter 6 Configure Extended ECM

(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.1.1.1)(PORT=1521))(CONNECT_DATA=(SID =
test)))

PostgreSQL

Example 6-7: A basic PostgreSQL database JDBC connection string

jdbc:postgresql://<hostname>:5432/<MyDBname>

SAP HANA

Example 6-8: A basic SAP HANA database JDBC connection string

jdbc:sap://<hostname>:30077

Example 6-9: A basic SAP HANA database JDBC connection string

with database name
jdbc:sap://<hostname>:30015/?databaseName=<MyDBname>

If you need to change your database connection string after installation, see “How
do I change my database connection information after I have installed OTDS?” in
OpenText Directory Services - Installation and Administration Guide (OTDS-IWC).

6.8.1 Use an External OTDS Server

For a production deployment of Content Server, OpenText recommends that you
connect to an external OTDS Server for user management.

To connect to an external OTDS Server, you need the following:

1. An installation of OTDS as an external, stand-alone application. For more

information, see OpenText Directory Services - Installation and Administration Guide
(OTDS-IWC).
2. The address of the OTDS Server.
3. The ID of the Resource that has been set up in OTDS for use with Content
Server.

Tip: The Resource Identifier is available in OpenText Directory Services in

the Properties of the Resource.

In addition, if you use a proxy or have a containerized environment, you have the
option of providing an explicit OTDS login URL.

100 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.8. Select the OTDS Server Type

For more information on OpenText Directory Services, see OpenText Content Server -
Directory Services Integration Administration Guide (LLESDSI-AGD) and OpenText
Directory Services - Installation and Administration Guide (OTDS-IWC).

To use an external OTDS Server

1. On the Configure OTDS Integration Settings page, select External OTDS

Server in the Server Type menu.

2. In the Server URL box, enter the host name (or IP address) and port of your
OTDS server. For example, enter: http://MyOtdsServer.corp.com:8080/

3. In the Resource ID box, enter the Resource Identifier of the OTDS Resource that
has been set up for use with Content Server. An example of a Resource ID is:
dba563af-b01d-4f88-bc42-2493c97dbc87

4. Optional You might want to enable Set OTDS login URL if you want to explicitly
set the OTDS URL to which users should be redirected. If so, enter that URL in
this field.
If you have structured either a proxy or a containerized environment, then you
will need to ensure that the Login URL box contains that URL. If you do not
have either a proxy or a containerized environment, then you do not need to
enable this setting.
The following are two examples of the format of the URL that you will enter to
this field:

• https://servername.domain.com
• https://servername.domain.com:8443

You may need to put the port number after the base URL depending on how
you set up your proxy.

5. You can choose to click Test Settings to confirm that the URL entered in the
Server URL box is valid.

Note: The connection test does not check whether the OpenText Directory
Server is configured properly with Content Server. It only checks that the
URL provided in the Server URL box is valid.

6. Click Continue.

7. If you are in the process of changing your Content Server database, or if you are
upgrading your Content Server installation, you will see the User and group
migration page. Follow the instructions in “The user and group migration
page” on page 103.

8. After you successfully connect to the OTDS Server, the Create New Enterprise
Data Source page appears. Proceed to “Create the Enterprise Data Source”
on page 92 to continue the initial configuration of Content Server.

LLESCOR240100-IGD-EN-01 Installation Guide 101

Chapter 6 Configure Extended ECM

6.8.2 Use an Internal OTDS Server

An internal OTDS server is suitable for a test deployment of Content Server or for a
limited production deployment. For production deployments of Content Server,
OpenText recommends that you use an external OTDS server for user management
in Content Server.

The internal OTDS server uses a Jetty web server. By default, the internal OTDS
server uses a self-signed certificate for HTTPS communications, but you can
configure it to use a different certificate by entering appropriate values in the Java
Key Store settings in the HTTPS Configuration section. For more information on
configuring Jetty to use a specific certificate, refer to the Jetty documentation.

Tip: Documentation for Jetty, which is a third-party software component, is

available on the Internet. For example, for information on creating a Java
keystore, see http://www.eclipse.org/jetty/documentation/current/configuring-
ssl.html.

For information on logging onto an internal installation of OTDS, see OpenText

Content Server Admin Help - Directory Services Integration Administration
(LLESDSI-H-AGD).

To use an internal OTDS Server

1. On the Configure OTDS Integration Settings page, select Internal OTDS

Server in the Server Type menu.

2. In the JDBC URL box, you need to inform Content Server about the location of
the database that you set up to store OTDS data. In the Username and Password
boxes you will be providing sign-in access to this database.
The form in which you type this information depends on the database that you
installed and configured. For examples, see “Format for the Database JDBC
connection string” on page 99.

Important
You must take care when entering values to the three JDBC boxes. These
values cannot be validated at the time you enter them. Any error in one of
these three values will result in OTDS being unable to access your
database.

3. In the JDBC Username box, enter the userid of a user with the required
privileges to access the database that you entered in the step above.

4. In the JDBC Password box, enter the password for the userid that you entered
in the step above.

5. Enter available ports in the boxes in the Jetty Parameters area. You can accept
the default ports or specify different ones. Click Check port to verify that the
specified ports are not in use.

102 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.8. Select the OTDS Server Type

6. Optional To configure the internal OTDS Server to use a security certificate of

your choice instead of the default self-signed certificate, enter Java key store
parameters in the Jetty HTTPS Configuration section.

7. Optional You might want to enable Set OTDS login URL if you want to explicitly
set the OTDS URL to which users should be redirected. If so, enter that URL in
this field.
If you have structured either a proxy or a containerized environment, then you
will need to ensure that the Login URL box contains that URL. If you do not
have either a proxy or a containerized environment, then you do not need to
enable this setting.
The following are two examples of the format of the URL that you will enter to
this field:

• https://servername.domain.com
• https://servername.domain.com:8443

You may need to put the port number after the base URL depending on how
you set up your proxy.

8. Click Continue.

9. The OTDS Deployment Status page appears. Click Show Details to view log
information that shows the progress of the deployment. When the OTDS
deployment has completed successfully message appears, click Continue.

10. If you are in the process of changing your Content Server database, or if you are
upgrading your Content Server installation, you will see the User and group
migration page. Follow the instructions in “The user and group migration
page” on page 103.

11. After the migration completes, and if you did not enable Content Server
Syndication, proceed to “Create the Enterprise Data Source” on page 92.
If you did enable Content Server Syndication, proceed to “Configure
Syndication Site Parameters” on page 105.

6.8.3 The user and group migration page

After you configure the OTDS integration, the User and group migration page
appears. Complete thhefollow these instructions:

To migrate OTDS users and groups

1. In the OTDS Partition box, you need to enter the name of the OTDS partition
that stores users and groups that were either created in Content Server or
migrated from the Content Server database:

a. If you have enabled an internal OTDS server, enter a name or accept the
default: Content Server members.

LLESCOR240100-IGD-EN-01 Installation Guide 103

Chapter 6 Configure Extended ECM

b. If you have enabled an external OTDS server, you must first sign in to your
external installation of OTDS and create your Content Server non-
synchronized partition.

2. Select the Migrate box to migrate users and groups from the Content Server
database to OTDS. Enable any migration options that apply.
The migrate option applies if you have an installation of Content Server with
CSDS, if you have an internal installation of OTDS, or if you have an external
installation of OTDS:

a. If you are using an external installation of OTDS, and prior to beginning

the migration, you must ensure that the access role has been created in
OTDS correctly.
For example, make certain that the Content Server members partition has
been added to the Content Server access role. You must also ensure that the
Include groups option has been selected on that Content Server access role.
Because this is the default behavior in an internal installation of OTDS, you
need to perform this check only if you are using an external installation of
OTDS.
b. If OTDS has never been used with Content Server, select the Migrate box to
migrate users and groups from the Content Server database to OTDS. The
Migrate option applies to migration of users and groups only.

Important
The migration function cannot distinguish users synchronized from
OTDS from internal Content Server users. If you have already
synchronized new users and/or groups from OTDS to Content Server,
and you use the migration option, you will end up with duplicate
users and groups.
In a new installation of Content Server, these options are not relevant
and you should click Continue without enabling any options.

If you are installing Content Server for the purposes of upgrading an

existing installation, your choices on this page depend on how users and
groups are managed in your source environment. See OpenText Extended
ECM - Upgrade Guide (LLESCOR-IUP).

i. Enable Migrate internal users and groups if you want to migrate

internal users and groups. All existing users and groups in OTDS
contained in the partition you entered in step 1 will be replaced with
users and groups in the current database.
ii. Enable Migrate (Tempo) external users and groups if you want to
migrate external (Tempo) users and groups. This options relates to the
OpenText Tempo product.
All existing users and groups in OTDS contained in the partition you
entered in step 1 will be replaced with users and groups in the current
database.

104 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.9. Configure Syndication Site Parameters

iii. Any Content Server Directory Services synchronization sources that

Content Server detects appear on this page. Enable Content Server
Directory Services users and groups to migrate those Content Server
Directory Services users and groups.

Note: The migration function does not directly migrate CSDS

users and groups. It migrates the CSDS sync profile into OTDS.
You can use the sync profile to import users and groups into
OTDS

3. Click Continue.

4. The Migration Status page appears. when the migration has completed
successfully message appears, click Continue.

6.9 Configure Syndication Site Parameters

If you chose to enable Content Server Syndication in “Configure Server Parameters”
on page 76, then you will see the Configure Syndication Site Parameters page. For
information about how to correctly enter required information on this page, see one
of the following, depending on whether you are setting up your primary installation
or a remote installation:

• “Configure primary Syndication parameters” on page 178

• “Configure remote Syndication parameters” on page 186

If you did not enable Content Server Syndication, this page will not appear during
your installation of Content Server.

Once you have completed the instructions for the Syndication configuration,
proceed to “Create the Enterprise Data Source” on page 92.

6.10 License Content Server

After you configure the OTDS integration (see “Select the OTDS Server Type”
on page 97), the License Setup page appears. You can now apply a license to
Content Server. (If applicable, you can also apply a Content Server module license.)
However, you are not required to apply a license to Content Server during
installation. If you prefer, you can apply any required licenses after you have
completed the installation.

Until you apply a Content Server license, Content Server operates in administrative
mode. In administrative mode, only users with the System administration rights
privilege can log on to Content Server.

Note: Content Server runs in administrative mode if:

• It is unlicensed. (No license of any kind has been applied.)

• It has a Temporary License that has expired.

LLESCOR240100-IGD-EN-01 Installation Guide 105

Chapter 6 Configure Extended ECM

• It has a license with an obsolete format.

You can exit administrative mode any time by applying a valid license to
Content Server.

6.10.1 License Types

There are two types of license for Content Server. The kind that you use depends on
your agreement with OpenText.

• Extended ECM license. For information on Extended ECM licenses, see

“Extended ECM Licenses” on page 106.
• Content Server license. For information on Content Server licenses, see “Content
Server Licenses” on page 106.

Extended ECM Licenses

Extended ECM licenses simplify license management.

Before the introduction of Extended ECM licenses, Content Suite Platform and
Extended ECM products were licensed as different products and modules, often
requiring multiple licenses. In contrast, a single Extended ECM license entitles you
to a unified product that contains numerous features and modules. Furthermore,
using an Extended ECM license prevents license overuse and gives you full control
over your current license allocation.

A variety of Extended ECM X-Plan licenses are available. Refer to the Extended
ECM Release Notes for more information.

Extended ECM licenses are fully managed by OpenText Directory Services (OTDS),
where you enter the license key, allocate users and monitor usage counts. Note that
an Extended ECM X-Plan license always has [EXTENDED_ECM] in its header, whereas
a Content Server license always has Content_Server.

Content Server Licenses

Content Server licenses are tied to a System Fingerprint that is generated from
information in your Content Server database. The information is encrypted and
hashed so that it is not human-readable. A single license file is sufficient to license
numerous Content Server instances that connect to the same database.

Important
Content Server has a requirement that its License Key Name begins with
Content_Server. For example, Content Server will recognize the following
license key names:

• Content_Server
• Content_Server Temporary
• Content_Server Production

106 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.10. License Content Server

Types of Content Server License File

There are two main kinds of license that can be applied in Content Server: an overall
license for Content Server itself, and module licenses that are for specific Content
Server modules.

Note: Certain products, such as WebReports, may require additional licensing

but do not require you to apply a license file in Content Server. Instead, you
must be licensed and enable the product on the product administration page
before you can use it.

Content Server license

A Content Server license is applied to Content Server as a whole. Several
different types of license exist:

• No license
If you have not applied a license, Content Server operates in administrative
mode and has a license status of Unlicensed. Users with the System
administration rights privilege can use it, but other users cannot log on.

Tip: Content Server 16.2.7 and later use a license format that is different
from the licenses used in Content Server 16.2.6 and earlier. If you apply
an obsolete license to Content Server 16.2.7 and later, the license status
appears as Unlicensed.
• Production License
A Production license enables full Content Server functionality for a specified
number of licensed users. It applies to a specific version of Content Server. It
does not have an expiry date.
• Temporary License
A Temporary license enables full Content Server functionality for a specified
number of licensed users. A Temporary license expires on a specific date. (It
does not expire a specified number of days that is calculated from the date it
is applied.)
• Non-production License
A non-production license is intended for use in a non-production
environment that exists to support a production environment. For example, a
non-production license could be used in a Development or User Acceptance
Testing environment. A non-production license enables full Content Server
functionality and has no expiry date.

Module license
Module licenses are applied to individual Content Server modules or
applications. Like Content Server licenses, module licenses can be issued as
Production, Temporary, or Non-production licenses. There is no equivalent of
administration mode for an unlicensed module.

LLESCOR240100-IGD-EN-01 Installation Guide 107

Chapter 6 Configure Extended ECM

Some Content Server modules do not function unless you apply a module
license. Other modules provide limited functionality if they are not licensed and
full functionality only after you apply a module license. Many modules do not
require a license at all.

6.10.2 Obtain an Extended ECM or Content Server License File

When you purchase Content Server, you are provided with a link to download the
installation software, a SUID associated with your software purchase, and a My
Support logon allowing access to the product activation site. You use this logon to
obtain your Content Server license file.

You may need to acquire license files for optional modules too, if you have
purchased optional modules that require licenses. (Not every optional module
requires a license.) You can download module licenses when you download your
Content Server licenses, or whenever you install the optional module.

To obtain a license file:

1. On the License Setup page, a System Fingerprint uniquely identifies your

Content Server installation. Copy the System Fingerprint so that you can use it
to generate a license file for Content Server.

2. Log on to My Support using the logon and password provided to you when
you purchased Content Server. Click My Accounts and then click Activations/
Keys browse to open the Product Activation page.

Tip: If your logon is associated with multiple accounts, make sure that you
are associated with the correct account. If you are not, click Change
Account Selections and select the correct account.

3. The Product Activation page displays the entitlements that are associated with
your logon, arranged according to SUID. (A SUID typically corresponds to a
distinct application environment.) If you have more than one Content Server
environment, you can hide the licenses that you do not wish to generate during

your current session by clicking the Up Arrow icon beside any SUID that
does not concern you.

108 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.10. License Content Server

If you are not sure which SUID is associated with the license that you want to
generate, refer to the email that you received from OpenText or contact
OpenText Customer Support for assistance.

4. Select the appropriate product and license file type, and click the Produce

License Key icon

• If you are generating a Production license, the Produce License Key dialog
box appears. Enter the System Fingerprint that appears on your Content
Server License Setup page, and then click Save. A message appears,
indicating that your license file is being generated.
• If you are not generating a Production license, a dialog box appears
immediately, indicating that your license file is being generated.

Click Download File to immediately download your license file, or OK to

return to the Product Activation page.

Tip: Only one license is required for multiple instances of Content Server
that connect to the same database.

After the license file is generated, a number appears in the Activated column on the
Product Activation page, and new icons may be visible:

•
The Download File icon
Use the Download File icon to download a new copy of your license file at any
time.
•
The Rehost License File icon
Use the Rehost License File icon if significant changes in your environment
invalidate your license file. For example, if you connect your Content Server
installation to a new database. You will be prompted to enter your new System
Fingerprint when you rehost your license file.

LLESCOR240100-IGD-EN-01 Installation Guide 109

Chapter 6 Configure Extended ECM

•
The Upgrade icon
Use the Upgrade icon to request a license file for a newer version of Content
Server. When you click the Upgrade icon, you are prompted to select the Content
Server version that you want to license.

6.10.3 Apply an Extended ECM or Content Server License File

To apply a license file, browse to the license file that you acquired from the Product
Activation site (see “Obtain an Extended ECM or Content Server License File”
on page 108), and apply it to Content Server.

How you proceed depends on the type of license that you are applying, an Extended
ECM License or a Content Server license.

Apply and Allocate an Extended ECM License

Before you can apply an Extended ECM license in Content Server, you need to add it
in OTDS. You can do this as you are performing the initial configuration of Content
Server or you can do it in advance. For information on adding licenses, and
allocating license counters to users, see OpenText Directory Services - Installation and
Administration Guide (OTDS-IWC).

The instructions in this document presume that you are adding the license to OTDS
during the initial configuration of Content Server.

Add an Extended ECM License to OTDS

To add an Extended ECM License to OTDS, perform the following steps:

To apply an Extended ECM license:

1. On the License Setup page, click the OTDS hyperlink in Use Extended ECM
license framework in OTDS. OTDS opens to the License Keys page.

2. Click Add. The New License page opens.

3. On the General tab, enter a License Key Name and click Next.

4. On the License Key tab, click Get License File, and then browse to and select
your license file. TheLicense Key box is populated with the information from
your license file.

5. Click Save to complete the addition of your Extended ECM License to OTDS.

Apply an Extended ECM License

Now that your Extended ECM license has been added to OTDS, you can apply it in
Content Server. Perform the following steps.

110 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.10. License Content Server

To apply an Extended ECM license:

1. On the License Setup page, select the Use Extended ECM license framework
in OTDS check box.

2. A warning message appears: You are about to change to the Extended ECM
license model. Make sure that users and groups are allocated to the respective
license counters. If users are not allocated to a license counter, they will not
be able to login to Content Server. Click Save Changes. (You will be able to
allocate users and groups to license counters once the initial configuration of
Content Server is complete.)

3. You are returned to the License Setup page, which now displays only the
enabled Use Extended ECM license framework in OTDS setting. (The Content
Server License Overview, System Fingerprint, and License Management
sections of the page do not appear if an Extended ECM license is applied.) Click
Continue.

Allocate Users to your Extended ECM License

To allow a user to log on and use Extended ECM, allocate the user to your Extended
ECM License.

Tip: You can allocate users to your Extended ECM license any time, but a user
needs to exist before you can allocate it to a license. If you intend to create
users after you complete the installation, you can allocate them to your
Extended ECM license after you create the Extended ECM users.

To allocate a user or group to an Extended ECM license:

1. On the OTDS Users & Groups page, click Actions > Allocate to License beside
the user or group that you would like to allocate to your Extended ECM license.

2. The Allocate to License dialog box appears. Enter the following information:

a. Select your Extended ECM license from the License menu.

b. Select the appropriate Counter from the Counter menu.
c. Select Occasional or Full from the License Type menu.
d. Click Allocate to License.

LLESCOR240100-IGD-EN-01 Installation Guide 111

Chapter 6 Configure Extended ECM

Apply a Content Server License File

During the initial configuration, you can apply a Content Server license file on the
License Setup page. If you do not, you can continue to configure Content Server in
administrative mode. After the initial configuration is complete, you can add the
license in OTDS. To add a Content Server license file to OTDS, follow the steps in
“Apply and Allocate an Extended ECM License” on page 110.

Tip: If Content Server displays a Could not read license content or Could not
read license content error message when you attempt to apply a license file,
ensure that:

• The file is not corrupted. If you suspect that it is, download another copy of
the license file from OpenText My Support and attempt to apply that one.
• The file has a .lic file extension.
• You have created a Content Server Upload directory (see OpenText Content
Server Admin Help - System Administration (LLESWBA-H-AGD)).
• The Content Server and web server users have full permissions to the
Content Server Upload directory.

If Content Server displays the error message License Error: License key not
valid. It may be an older version of the license file format, or the file
may be corrupt, it is likely that you are attempting to apply a license that
applies to Content Server 16.2.6 and earlier to an installation of Content Server
16.2.7 or later. If so, you should obtain an up-to-date license file and apply that
one instead.

To apply a Content Server license file:

1. On the License Setup page, click Choose File.

2. On the Open dialog box, browse to the location of your license file, select the
license file, and then click Open.
The page refreshes and a section entitled New License File Details appears.

3. Click Apply License File.

4. If you have applied a module license, restart Content Server.

Tip: If you have applied an overall Content Server license, it is not

necessary to restart Content Server.

5. Click Continue.

112 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 6.11. The Congratulations! Page

6.10.4 Store Your License File

When you apply your license file, its information is written to the Content Server
database. Any instance of Content Server that connects to the same database is
covered by the applied license. It is not necessary to keep the license file in place
after you apply it. OpenText recommends that, after you apply the license file, you
store it in a secure location.

6.11 The Congratulations! Page

After you have successfully completed the steps involved in the initial configuration
of Content Server, the Congratulations! page appears. The appearance of this page
indicates that your initial configuration is complete. You have:

• Set the Content Server Administration password and default metadata language
• Created the Content Server database
• Viewed the Install Modules page and, optionally, installed additional Content
Server modules
• Created the Enterprise Data Source
• Applied a license to Content Server

If you wish to install additional instances of Content Server, proceed to “Install

Additional Instances of Extended ECM“ on page 155

If you do not wish to install additional instances of Content Server, proceed to

“Complete the Installation and Setup of Extended ECM“ on page 115

LLESCOR240100-IGD-EN-01 Installation Guide 113

Chapter 7
Complete the Installation and Setup of Extended
ECM

This chapter contains information about a number of tasks that you should perform
to complete the installation and initial configuration of Extended ECM. You can
perform these tasks at any time, but for reasons of security or consistency, you may
prefer to do them before users first sign in to Extended ECM.

For example, for security, it is important to create groups with appropriate access
permissions before allowing users to sign in to Extended ECM, and for consistency,
it is important to decide which actions will trigger a change to an item’s Modified
Date in Content Server.

7.1 Apply All Available Patches to Content Server

Before you make Content Server available for general use, you should apply all of
the available Content Server patches. To ensure that your Content Server installation
has all of the latest patches available from OpenText, use System Center Manager to
download, stage, and deploy all of the patches that are currently available. System
Center Manager is a standalone application that installs, configures, patches, and
updates multiple OpenText software applications. You can find a link to download
System Center Manager on the Cluster Management administration page.

7.2 Install Optional Modules

Optional modules can be added to Content Server during its initial configuration or
any time afterwards.

If you have additional modules that you want to install before you make your
Content Server deployment available to users, you can install them now. If you
install your optional modules now, run System Center Manager (see “Apply All
Available Patches to Content Server” on page 115) afterwards to ensure that Content
Server runs with all of the necessary patches.

For information on installing optional modules, see “Install Optional Content Server
Modules” on page 94 in this guide.

LLESCOR240100-IGD-EN-01 Installation Guide 115

Chapter 7 Complete the Installation and Setup of Extended ECM

7.3 Installing Extended ECM for SAP Solutions with

OpenText System Center Manager
OpenText System Center Manager helps you download the respective software. As a
direct customer of OpenText, you find OpenText System Center Manager on
OpenText My Support. Customers of SAP find it in SAP Store.

Prerequisites You need a user login to OpenText My Support.

To download installation software with OpenText System Center:

1. Login in to OpenText My Support. Search and download the OpenText System

Center Manager for SAP installable OpenText_SystemCenter_Manager.msi file.
As an SAP customer, download the OpenText_SystemCenter_Manager_S.msi file
from SAP Software Download Center.

2. Install the OpenText System Center Manager for SAP on your computer or
server. Follow the install instructions.

You can install certain scenarios. For more information, see “Scenarios and their
components” on page 117 and “List of all components by scenario” on page 120.

After you installed OpenText System Center Manager for SAP, you can use the
predefined execution plan (extended_ecm_plan.pln) to install an all-in-one scenario
for OpenText Extended ECM for SAP Solutions including all basic software and
modules. The execution plan conducts the following installations in 19 steps:

• Installing and setting up OpenText Directory Services:

– Installing OpenText Directory Services

– Setting up OpenText Directory Services
• Installing and configuring OpenText Content Server

– Installing OpenText Content Server

– Configuring OpenText Content Server
• Deploying OpenText Extended ECM WebServices

– Deploying OpenText Extended ECM WebServices

– Deploying OpenText Extended ECM CMIS WebServices
• Installing OpenText Archive Center and related modules

– Installing Monitoring Agent

– Installing OpenText Archive Center
– Installing OpenText Administration Client
– Installing Archive Monitoring Server

116 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.3. Installing Extended ECM for SAP Solutions with OpenText System Center Manager

– Installing OpenText Document Pipelines Base

– Installing OpenText Document Pipelines CMIS
– Installing OpenText Document Pipeline DocuLink
– Installing OpenText Document Pipelines File Archiving
– Installing OpenText Document Pipelines Info
– Installing OpenText Document Pipeline Perl
– Installing OpenText Document Pipeline Remote Interface
– Installing Document Pipeline for SAP products

The installations require certain prerequisites. For more information, see

“Prerequisites for running the execution plan for an all-in-one scenario”
on page 130.

Note: You can also create an execution plan on your own. If you do, take care
that the execution plan still has to follow the above-mentioned order.

7.3.1 Scenarios and their components

OpenText Directory Services (OTDS) deployment
Installation information – OpenText Directory Services - Installation and
Administration Guide (OTDS-IWC)

Component Order Windows Linux

Directory Services 1 OTDS-<version>-
WIN.msi

Archive Center deployment

Installation information

• OpenText Archive Center - Amazon S3 Installation and Configuration Guide (AR-

IAM)
• OpenText Archive Center - Installation Guide for Windows (Extended Component
Installer) (AR-IASW)
• OpenText Archive Center - Microsoft Azure Installation and Configuration Guide
(AR-IAZ)
• OpenText Archive Center - EMC Centera Installation and Configuration Guide
(AR-ICE)
• OpenText Archive Center - Compliant File System Installation and Configuration
Guide (AR-ICF)
• OpenText Archive Center - Cluster Installation Guide (AR-ICLU)
• OpenText Archive Center - IBM TSM SSAM Installation and Configuration Guide
(AR-IDR)

LLESCOR240100-IGD-EN-01 Installation Guide 117

Chapter 7 Complete the Installation and Setup of Extended ECM

• OpenText Archive Center - Dell EMC Elastic Cloud Storage Installation and
Configuration Guide (AR-IECS)
• OpenText Archive Center - Google Cloud Storage Installation and Configuration
Guide (AR-IGCS)
• OpenText Archive Center - Installation Guide for Linux (AR-IGU)
• OpenText Archive Center - Installation Guide for Windows (Integrated Archive
Installer) (AR-IGW)
• OpenText Archive Center - HCP Installation and Configuration Guide (AR-IHC)

Component Order Windows Linux

Archive Center 1 archive_server- archive_server_<vers
<version>.msi ion>.tar.gz
Archive Monitoring 2 archive_monitoring archive_monitoring
Server _server- _server_<version>.tar
<version>.msi .gz
Solution Registry 3 solution_registry_ag solution_registry_ag
Agent ent-<version>.msi ent_<version>.tar.gz
Archive Cache optional archive_cache_serve archive_cache_serve
Server r-<version>.msi r_<version>.tar.gz

Archive Cache Server deployment

Installation information

• OpenText Archive Center - Installation Guide for Windows (Extended Component

Installer) (AR-IASW)
• OpenText Archive Center - Installation Guide for Linux (AR-IGU)

Component Order Windows Linux

Archive Cache 1 archive_cache_serve archive_cache_serve
Server r-<version>.msi r_<version>.tar.gz
Solution Registry 2 solution_registry_ag solution_registry_ag
Agent ent-<version>.msi ent_<version>.tar.gz
Archive Center optional archive_server- archive_server_<vers
<version>.msi ion>.tar.gz
Archive Monitoring optional archive_monitoring archive_monitoring
Server _server- _server_<version>.tar
<version>.msi .gz

Content Server deployment

Installation information

• OpenText Extended ECM - Installation Guide (LLESCOR-IGD)

118 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.3. Installing Extended ECM for SAP Solutions with OpenText System Center Manager

Component Order Windows Linux

Content Server 1 <version>_CS64_WI <version>_CS64_LN
N.exe X6.tar.gz
Monitoring Agent optional monitoring_agent_< monitoring_agent_<
version>_win.msi version>_LNX.tar.gz
Content Server optional CSMobile_<version>.
Mobile zip
Imaging Web optional OT_DOCVW_<versi OT_DOCVW_20.3.is
Viewer Service on>.iso (WebViewer- o (WebViewer-20.3-
<version>- Linux64.sh)
Win64.msi)

SAP packages deployment

Installation information

• OpenText Extended ECM for SAP Solutions - Installation and Upgrade Guide
(ERLK-IGD)
• OpenText Extended ECM for SAP Solutions - Installation and Upgrade Guide
(ERLK-IGD)

Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRL <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLC <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLE <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLF <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLO <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLS <version>
Extended ECM for SAP Solutions - SAP Add-on Packages - OTEXRLSA <version>
Vendor Invoice Management Foundation - SAP Add-on Packages - OTBCBAS <version>
Vendor Invoice Management Foundation - SAP Add-on Packages - OTBCWUI <version>

Document Pipelines deployment

Installation information – OpenText Document Pipelines - Installation and Upgrade
Guide (AR-IDPDP)

Component Order Windows Linux

Document Pipeline 1 dp_base-
Base <version>.msi
Document Pipeline 2 DPCS_<version>_PL
for Content Server AIN.iso
(dp_content_server-
<version>.msi)

LLESCOR240100-IGD-EN-01 Installation Guide 119

Chapter 7 Complete the Installation and Setup of Extended ECM

Component Order Windows Linux

Document Pipeline 3 dp_doculink-
for DocuLink <version>.msi
Document Pipeline 4 dp_sap-
for SAP Solutions <version>.msi
Document Pipeline 5 dp_info-
Info <version>.msi
Document Pipeline 6 dp_perl-
Perl <version>.msi
Document Pipeline 7 dp_remote_interface
Remote Interface -<version>.msi
Solution Registry optional solution_registry_ag solution_registry_ag
Agent ent-<version>.msi ent_<version>.tar.gz

Remote Cache Module with Smart Cache Services deployment

Installation information – OpenText Remote Cache - Installation, Configuration, and
Administration Guide (LLESRCA-IGD)

Component Order Windows Linux

Remote Cache <version>_RCACHE
Module MODULE64_WIN.e
xe
Remote Cache <version>_RCACHE
Server SERVER64_WIN.exe
Smart Cache <version>_SMARTC
Services for Primary ACHESERVICES_P
Server RIMARY_WIN64.ex
e
Smart Cache <version>_SMARTC
Services for Remote ACHESERVICES_R
Server EMOTE_WIN64.exe

7.3.2 List of all components by scenario

Installation Name Description Windows Linux Binaries
Scenario Binaries
Archiving Archive Cache Provide the archive_cache_se archive_cache_se
Server ability to rver- rver_<version>.ta
support remote <version>.msi r.gz
Archive Center
(not installable
for local Archive
Center).

120 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.3. Installing Extended ECM for SAP Solutions with OpenText System Center Manager

Installation Name Description Windows Linux Binaries

Scenario Binaries
Archiving Archive Center Provide archive_server- archive_server_<
compliant long- <version>.msi version>.tar.gz
term archiving
for documents
incorporating:
the ability to
store and
retrieve content,
storage
virtualization,
caching and
cache servers,
long-term
preservation and
more.
Archiving Archive Provide the archive_monitori archive_monitori
Monitoring ability to ng_server- ng_server_<versi
Server monitor Archive <version>.msi on>.tar.gz
Center locally or
remotely.
Archiving Core Archive Provide access to CoreArchiveCon
Connector the archiving nector-
services of <version>.msi
Archive Center
in the OpenText
Cloud.
Archiving Solution Deliver solution_registry solution_registry
Registry Agent information to _agent- _agent_<version>
Solution <version>.msi .tar.gz
Registry Server
regarding
installed
OpenText
software.

LLESCOR240100-IGD-EN-01 Installation Guide 121

Chapter 7 Complete the Installation and Setup of Extended ECM

Installation Name Description Windows Linux Binaries

Scenario Binaries
Clients Administration Allow administration_c
Client configuration lient-
and <version>.msi
administration
of OpenText
Services
installed on
different
operating
systems. It is
based on
Microsoft
Management
Console (MMC)
and can be
installed only on
Windows
systems.
Clients AppWorks Provide a opentextappwor
Desktop Client seamless, ksdesktop-
interactive view <version>x64.msi
of content and
functionality
from the
AppWorks
server.
Clients Content Server Provide back- CSMobile_<versi
Mobile end AppWorks on>.zip
application that
brings Content
Server
functionality to
mobile clients.
Clients Enterprise Provide a EnterpriseConne
Connect seamless, ct_Framework_<
Framework (32- interactive view version>.msi
bit version) of content and
functionality
from many
Enterprise
systems.
Clients Enterprise Provide a EnterpriseConne
Connect seamless, ct_Framework_<
Framework (64- interactive view version>_x64.msi
bit version) of content and
functionality
from many
Enterprise
systems.

122 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.3. Installing Extended ECM for SAP Solutions with OpenText System Center Manager

Installation Name Description Windows Linux Binaries

Scenario Binaries
Clients Imaging Quickly and Desktop Link
Desktop Link easily archive <version>- 64
and retrieve files bit.msi
from your
workstation.
Clients Imaging Bring scanning OT_SCAN_<vers
Enterprise Scan capacity to the ion>.iso
Content Server (Enterprise Scan
user interface. <version>.msi)
The indexing
feature is also
available. Users
can scan an
image and run
an indexing
session in the
same user
interface.
Clients Imaging Quickly and ExchangeLink
ExchangeLink easily archive <version>.msi
(32-bit version) and retrieve files
from your
workstation.
Clients Imaging Enable linking ExchangeLink
ExchangeLink and archiving <version>- 64
(64-bit version) Exchange bit.msi
documents into
other
applications by
selecting them
and using the
respective menu
option.
Clients Imaging Archive OutlookLink
OutlookLink Microsoft <version>.msi
Outlook objects,
such as emails,
attachments, and
calendar events
and link them to
other
applications by
selecting them
and using the
task pane
against each
email to archive
email and
attachments.

LLESCOR240100-IGD-EN-01 Installation Guide 123

Chapter 7 Complete the Installation and Setup of Extended ECM

Installation Name Description Windows Linux Binaries

Scenario Binaries
Clients Imaging OpenText Windows
Windows Imaging Viewer
Viewer Windows <version>.msi
Viewer is the
basic package
for Viewer.
Clients Office Editor Offer users a OFFICEEDITOR
Client (32-bit seamless instant _CLIENT_<versio
version) editing n>.msi
experience,
Clients Office Editor providing the OFFICEEDITOR
Client (64-bit performance of _CLIENT_<versio
version) editing files on a n>_x64.msi
local hard drive
without
installing any
special add-ons
to applications.
Clients Searchable PDF Allow rendering DPOCR_<version
DocTool of scanned >.iso
documents to (dt_ocr_<version>
searchable PDF .msi)
documents.
Content Server Content Server Forms the <version>_CS64_ <version>_CS64_
document WIN.exe LNX6.tar.gz
management
cornerstone of
the OpenText
Content Suite
and provide
secure,
enterprise-wide
control over any
type of content -
from contracts to
engineering
drawings,
system reports,
email messages,
images rich
media and much
more.

124 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.3. Installing Extended ECM for SAP Solutions with OpenText System Center Manager

Installation Name Description Windows Linux Binaries

Scenario Binaries
Content Server Imaging Bring scanning SCAN_MODUL SCAN_MODUL
Enterprise Scan - capacity to the E_<version>.iso E_<version>.iso
Web Interface Content Server (<version>_escan (<version>_escan
<version> user interface. webinterface64_ webinterface64_
The indexing WIN.exe) LNX.tar)
feature is also + ESWS.war + ESWS.war
available. Users
can scan an
image and run
an indexing
session in the
same user
interface
Content Server Monitoring Provide real- monitoring_agen monitoring_agen
Agent time information t_<version>_win. t_<version>_LNX
about multiple msi .tar.gz
Content Servers.
Document Document Provide the basic dp_base- dp_base-
Pipelines Pipeline Base package for <version>.msi <version>.tar.gz
Document
Pipelines.
Document Document Provide the DPCS_<version>_ DPCS_<version>_
Pipelines Pipeline for Document PLAIN.iso PLAIN.iso
Content Server Pipeline for (dp_content_ser (dp_content_ser
archiving ver- ver-
documents to <version>.msi) <version>.tar.gz)
Content Server.
Document Document Provide the dp_doculink- dp_doculink-
Pipelines Pipeline for Document <version>.msi <version>.tar.gz
DocuLink Pipeline for
DocuLink.
Document Document Provide the dp_sap- dp_sap-
Pipelines Pipeline for SAP Document <version>.msi <version>.tar.gz
Solutions Pipeline for SAP
document
archiving. May
require
additional
licenses.
Document Document Provide a tool dp_info- dp_info-
Pipelines Pipeline Info for monitoring <version>.msi <version>.tar.gz
Document
Pipelines.
Document Document Provide a Perl dp_perl- dp_perl-
Pipelines Pipeline Perl package for <version>.msi <version>.tar.gz
Document
Pipelines.

LLESCOR240100-IGD-EN-01 Installation Guide 125

Chapter 7 Complete the Installation and Setup of Extended ECM

Installation Name Description Windows Linux Binaries

Scenario Binaries
Document Document Document dp_remote_inter dp_remote_inter
Pipelines Pipeline Remote Pipeline Remote face- face-
Interface Interface 20.2 <version>.msi <version>.tar.gz
Remote Cache Remote Cache Remote Cache <version>_RCAC
Module Module HEMODULE64_
WIN.exe
Remote Cache Remote Cache Remote Cache <version>_RCAC
Server Server 16.2.10 HESERVER64_
WIN.exe
Remote Cache Smart Cache Smart Cache <version>_SMAR
Services for Services for TCACHESERVI
Primary Server Primary Server CES_PRIMARY_
16.2.10 - WIN64.exe
Requires JCE!
Remote Cache Smart Cache Smart Cache <version>_SMAR
Services for Services for TCACHESERVI
Remote Server Remote Server CES_REMOTE_
<version> - WIN64.exe
Requires JCE!
SAP Add-on OTEXBAS Archiving and XECM_INTEGR XECM_INTEGR
Packages Document ATION_TO_SA ATION_TO_SA
Access for SAP P_<version>.iso P_<version>.iso
Solutions base
package
SAP Add-on OTEXBASB Archiving and XECM_INTEGR XECM_INTEGR
Packages Document ATION_TO_SA ATION_TO_SA
Access for SAP P_<version>.iso P_<version>.iso
Solutions base
package
SAP Add-on OTEXBASF Archiving and XECM_INTEGR XECM_INTEGR
Packages Document ATION_TO_SA ATION_TO_SA
Access for SAP P_<version>.iso P_<version>.iso
Solutions
package for SAP
Fiori
SAP Add-on OTEXBASO Archiving and XECM_INTEGR XECM_INTEGR
Packages Document ATION_TO_SA ATION_TO_SA
Access for SAP P_<version>.iso P_<version>.iso
Solutions
package for
OData Services

126 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.3. Installing Extended ECM for SAP Solutions with OpenText System Center Manager

Installation Name Description Windows Linux Binaries

Scenario Binaries
SAP Add-on OTEXCRM Archiving and XECM_INTEGR XECM_INTEGR
Packages Document ATION_TO_SA ATION_TO_SA
Access for SAP P_<version>.iso P_<version>.iso
Solutions
package for SAP
CRM
SAP Add-on OTEXERP Archiving and XECM_INTEGR XECM_INTEGR
Packages Document ATION_TO_SA ATION_TO_SA
Access for SAP P_<version>.iso P_<version>.iso
Solutions
package for SAP
ERP
SAP Add-on OTEXRL Extended ECM XECM_INTEGR XECM_INTEGR
Packages for SAP ATION_TO_SA ATION_TO_SA
Solutions base P_<version>.iso P_<version>.iso
package
SAP Add-on OTEXRLC Extended ECM XECM_INTEGR XECM_INTEGR
Packages for SAP ATION_TO_SA ATION_TO_SA
Solutions P_<version>.iso P_<version>.iso
package for SAP
CRM
SAP Add-on OTEXRLE Extended ECM XECM_INTEGR XECM_INTEGR
Packages for SAP ATION_TO_SA ATION_TO_SA
Solutions P_<version>.iso P_<version>.iso
package for SAP
ERP, S/4HANA,
OTEXRLE adds
SAP DMS
support.
Customers not
using SAP DMS
do not need to
install
OTEXRLE.
SAP Add-on OTEXRLF Extended ECM XECM_INTEGR XECM_INTEGR
Packages for SAP ATION_TO_SA ATION_TO_SA
Solutions P_<version>.iso P_<version>.iso
package for SAP
Fiori
SAP Add-on OTEXRLO Extended ECM XECM_INTEGR XECM_INTEGR
Packages for SAP ATION_TO_SA ATION_TO_SA
Solutions P_<version>.iso P_<version>.iso
package for
OData Services

LLESCOR240100-IGD-EN-01 Installation Guide 127

Chapter 7 Complete the Installation and Setup of Extended ECM

Installation Name Description Windows Linux Binaries

Scenario Binaries
SAP Add-on OTEXRLS Extended ECM XECM_INTEGR XECM_INTEGR
Packages for SAP ATION_TO_SA ATION_TO_SA
Solutions P_<version>.iso P_<version>.iso
package for SAP
SRM
SAP Add-on OTEXRLSA Extended ECM XECM_INTEGR XECM_INTEGR
Packages for SAP ATION_TO_SA ATION_TO_SA
Solutions P_<version>.iso P_<version>.iso
Business
Scenarios
SAP Add-on OTBCBAS Vendor Invoice XECM_INTEGR XECM_INTEGR
Packages Management ATION_TO_SA ATION_TO_SA
Foundation base P_<version>.iso P_<version>.iso
package
SAP Add-on OTBCWUI Vendor Invoice XECM_INTEGR XECM_INTEGR
Packages Management ATION_TO_SA ATION_TO_SA
Foundation User P_<version>.iso P_<version>.iso
Interface
package
Server AppWorks Allows quickly otag-gateway-
Gateway and easily <version>.zip
<version> building
purpose-specific
apps for the
Enterprise using
well-established
Web
technologies like
HTML5, CSS,
and JavaScript.
Server Directory Integrate OTDS-<version>- OTDS-<version>-
Services OpenText WIN.msi LNX.tar
<version> products with an
enterprise
directory
infrastructure
(based on
Microsoft AD
and/or LDAPv3)
to enable Single
Sign On (SSO)
across all
components.

128 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.3. Installing Extended ECM for SAP Solutions with OpenText System Center Manager

Installation Name Description Windows Linux Binaries

Scenario Binaries
Viewing Services Brava! Server Offers a BravaEnterprise BravaEnterprise
Components customized _ServerCompon _ServerCompon
component ents_<version>.ex ents_<version>.tg
delivery system e z
intended for
select
integrators.
Administrators
of Content
Server
(deploying
Content Suite
Viewer) and
Brava! for
Content Suite
are primary
consumers of
this product.
Viewing Services Imaging Web Provides a web Imaging_Web_V Imaging_Web_V
Viewer application for iewer_CE_<versi iewer_CE_<versi
displaying and on>.msi on>.tar.gz
printing
documents in
web-based
scenarios and for
appending
comments to
these
documents.
Viewing Services Intelligent Provide a cloud intelligent- intelligent-
Viewing first product viewing- viewing-
built for file packaging- packaging-linux-
viewing and windows- <version>.zip
transformation <version>.zip
at scale.

LLESCOR240100-IGD-EN-01 Installation Guide 129

Chapter 7 Complete the Installation and Setup of Extended ECM

7.3.3 Prerequisites for running the execution plan for an all-

in-one scenario
Before you can start running the extended_ecm_plan.pln execution plan for the all-
in-one scenario to completely install OpenText Extended ECM for SAP Solutions
including all basic software and modules, all of the following prerequisites have to
be fulfilled.

General prerequisites

• System Center Manager for SAP needs to be configured with System Center
Agent.
• Java has to exist on the system or needs to be installed. To be able to install it
with the execution plan, upload the Java installer to System Center Manager for
SAP under Settings > External Vendor Files. It is then available for the execution
plan.
• Apache Tomcat has to exist on the system or needs to be installed. To be able to
install it with the execution plan, upload the Tomcat installer to System Center
Manager under Settings > External Vendor Files. It is then available for the
execution plan. For more information, see OpenText Archive Center - Installation
Guide for Windows (Integrated Archive Installer) (AR-IGW).

Prerequisites for installing and setting up OpenText Directory Services

The extended_ecm_plan.pln execution plan will install OpenText Directory Services

(OTDS) on a specific agent first. For installing and setting up OTDS the following
prerequisites apply:

• OTDS product has to be downloaded from the Catalog tab in System Center
Manager.
• Since System Center Manager does not install OTDS on Windows, the agent
should have Windows Server OS as a base.
• Details on OTDS have to be defined. For example, it has to be defined whether to
use an internal or an external OTDS.

Note: An external OTDS can be configured in the following ways:

– Using ResourceId by selecting the External option

– Using Resource name by selecting External Lookup option

For configuring an OTDS migration, keep all values as 0. Otherwise, the

plan might fail with errors. For more information, see OpenText Directory
Services - Installation and Administration Guide (OTDS-IWC).

Prerequisites for installing and configuring OpenText Content Server

The extended_ecm_plan.pln execution plan will continue with installing and

configuring Content Server on a specific agent. The following prerequisites apply:

130 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.3. Installing Extended ECM for SAP Solutions with OpenText System Center Manager

• Content Server product has to be downloaded from the Catalog tab in System
Center Manager.
• Details on the database on which Content Server will be deployed must be
defined.

Note: You can optionally add a Content Server license by uploading it

to System Center Manager under Settings > External Vendor Files. The license
is needed in order to allow users to sign-in to Content Server.

Prerequisites for installing and setting up OpenText Extended ECM modules

In this part, the extended_ecm_plan.pln execution plan will install the relevant
OpenText Extended ECM modules on the specific agent. The following prerequisites
apply:

• OpenText Content Server has to be installed and configured on the agent.

Prerequisites for installing OpenText Archive Center and related modules

In the last step, the extended_ecm_plan.pln execution plan will install OpenText
Archive Center and related modules on the specific agent. The following
prerequisites apply:

• OpenText Archive Center, OpenText Administration Client, and Archive

Monitoring Server have to be downloaded from the Catalog tab in System Center
Manager.
• OpenText Document Pipelines Base, OpenText Document Pipelines CMIS,
OpenText Document Pipeline DocuLink, OpenText Document Pipelines File
Archiving, OpenText Document Pipelines File Archiving, OpenText Document
Pipelines Info, OpenText Document Pipeline Perl, OpenText Document Pipeline
Remote Interface, and Document Pipeline for SAP products have to be
downloaded from the Catalog tab in System Center Manager.
• A database for Archive Center is already installed and configured. For more
information about the necessary steps, see OpenText Archive Center - Installation
Guide for Windows (Integrated Archive Installer) (AR-IGW).

LLESCOR240100-IGD-EN-01 Installation Guide 131

Chapter 7 Complete the Installation and Setup of Extended ECM

7.3.4 Running installation with the execution plan for an all-

in-one scenario
To run the installation for an all-in-one Scenario of OpenText Extended ECM for
SAP Solutions including all basic software and modules with the extended_ecm_
plan.pln execution plan, certain prerequisites apply. For more information, see
“Prerequisites for running the execution plan for an all-in-one scenario” on page 130.

As soon as these prerequisites are fulfilled, you can start the execution plan.

Note: Running the installation with the extended_ecm_plan.pln System Center

execution plan takes about half an hour time. It cannot be rolled back.

To run the installation with the predefined execution plan

1. In OpenText My Support search for the extended_ecm_plan.pln file and

download the execution plan.

2. Import the downloaded plan into System Center. To do so, in System Center
navigate to the Plans tab, In Plans Overview page, click on the Import plan.
Then select the downloaded plan.

3. To open the plan, in the Plan Overview select extended_ecm_plan, and click
Edit. You can see the details of the execution plan with the separate steps of the
complete installation.

4. Optional: If Java and Apache Tomcat do not yet exist on the system yet, you can
define to install them in the first step Install Directory Services for Windows of
the plan. For this, open the Step. In the Apache Tomcat tab rsp. the Java tab in
Installation Type, select New Install.

5. Click Execute to start installing.

6. If passwords are required, a dialog opens. Enter the necessary passwords and
click Yes.

7. After you started the execution plan, the Execution Plans view in the Activities
tab opens. Here, you can monitor the progress of the execution plan.

7.4 Install Content Server Language Packs

Content Server allows users to specify their preferred language for the user interface
and item metadata. As an administrator, you enable this functionality by installing
Content Server Language Packs and module Language packs.

For information on installing Content Server Language Packs, see OpenText Content
Server Admin Help - System Administration (LLESWBA-H-AGD).

132 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.5. Set Up the Help Environment

Tip: To display this Admin Help topic, click Install Language Packs in the
Languages section of the Content Server Administration page and then, on the
Install Language Packs page, click Help for this Page.

7.5 Set Up the Help Environment

Help for the Content Server is delivered as OpenText Global Help Server help,
which is available over the Internet. Global Help Server help is updated by
OpenText. Updates can occur at any time without requiring any action on your part.
However, if your organization restricts access to the public Internet, you may need
to implement the OpenText Private Help Server: a local installation of the Global
Help Server. See “Providing the online help on a local help server (Private Help
Server)” on page 133.

7.5.1 Providing the online help on a local help server (Private

Help Server)
The online help for this module is delivered using the OpenText Global Help Server
(GHS) system, which provides your users with live access to the latest version of the
help. If you cannot use the GHS system, for example, if your site does not have
Internet access, you can install the OpenText Private Help Server (PHS), a local
version of the help system that can host your OpenText online help on your
organization’s network. After the PHS is installed, you can then configure your
OpenText module(s) to forward all online help requests to your PHS. For detailed
information about installing the PHS, see OpenText Help System - Private Help Server
Administration Guide (OTHS-AGD).

Notes

• The Private Help Server can support multiple OpenText modules. If the
Private Help Server has already been installed within your organization to
support another OpenText module, you can add additional OpenText
module online helps to that installation.
• If you are replacing a previous PHS installation, see OpenText Help System -
Private Help Server Administration Guide (OTHS-AGD).
• If the server you want to use for the PHS installation cannot connect to the
Internet, see OpenText Help System - Private Help Server Administration Guide
(OTHS-AGD).

Once the PHS is installed or upgraded, you can use its Online Help Deployer to
download online helps from the GHS system by entering the help deployment codes
listed in “Help deployment codes” on page 134. For more information about using
the codes, see OpenText Help System - Private Help Server Administration Guide (OTHS-
AGD).

LLESCOR240100-IGD-EN-01 Installation Guide 133

Chapter 7 Complete the Installation and Setup of Extended ECM

Table 7-1: Help deployment codes

Code Product
LLESCOR240100-IGD OpenText™ Extended ECM CE 24.1

Configuring Content Server to use the Private Help Server

Note: This section, and the previous section “Providing the online help on a
local help server (Private Help Server)” on page 133, apply only to the
OpenText Global Help Server help, which is available over the Internet.

For information about the built-in online help that is included in the Content
Server application directory, see “Set Up the Help Environment” on page 133.

To have your Content Server installation call the help topics on your Private Help
Server:

1. Follow the instructions to download the Private Help Server and install the
product online help. See the Private Help Server Administration Guide (https://
knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=74951271&
objAction=browse&viewType=1) for more information. Specifically, see
OpenText Help System - Private Help Server Administration Guide (OTHS-AGD) and
OpenText Help System - Private Help Server Administration Guide (OTHS-AGD).
To download the online help files you will require the help deployment code for
that online help. To find this code, see the “Help deployment codes” section of
that module's guide.
2. Set the URL Root of your Private Help Server on the Configure Smart View
administration page.

To configure Content Server to use the Private Help Server:

1. On the Content Server Administration page, in the Core System - Server

Configuration section, click Server Parameters.

2. On the Configure Server Parameters page, in the System Configuration area,

select the Enable check box beside Custom or Local Help Server.

3. Enter the base URL of your Private Help Server in the URL Root box, as
follows:
http://<Private_Help_Server_url>/OTHelpServer/mapperpi

For example, enter http://tomcat.example.com:8080/OTHelpServer/mapperpi

4. In the Type box, enter a custom help type. The default value is ofh1.

5. In the Tenant box, enter a custom help tenant value. If you do not require a
custom help tenant value, leave this box blank.

6. Click Save Changes.

134 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.6. Perform Additional Tasks Before Users Connect

7.6 Perform Additional Tasks Before Users Connect

Content Server is now functional, but there are a number of administrative tasks that
you should consider before you allow users to access Content Server. This section
describes some of these additional tasks.

7.6.1 Create Users and Groups and Set Permissions

Create Users and Groups
Using OpenText Directory Services, create a Content Server user for each
member of your organization who will use Content Server. Organize the users
into groups.

Tip: Users who will have responsibility for managing the look and feel of
Content Server or for configuring Content Server applications can be
added to the Business Administrators group, which is created on
installation of Content Server. The default Volume, Object, and Usage
privileges of this group allow its users to access various administrative
functions without having the System Administration Rights user
privilege. For more information, see OpenText Content Server Admin Help -
System Administration (LLESWBA-H-AGD).
Set Permissions
OpenText recommends that you create a folder hierarchy in the Enterprise
Workspace for the various departments in your organization and set the base
permissions on these folders accordingly. For example, create a folder called
Legal and configure it so that only members of the Legal department can view
its contents.
Set Item Creation Privileges
By default, all users have the ability to create all types of Content Server items
except for Content Server LiveReports. Use the Administer Object Privileges
and Administer Usage Privileges administration pages to restrict the creation of
certain types of items to certain users or groups.
Define Password Settings
Using OpenText Directory Services, specify password complexity and expiration
settings.

LLESCOR240100-IGD-EN-01 Installation Guide 135

Chapter 7 Complete the Installation and Setup of Extended ECM

7.6.2 Configure Security Settings

Configure Access Control

Access Control settings govern the ability of users with Edit permissions to
provide item access to other users and groups.

Set Audit Interests

Specify that you want audit information generated for certain item types.
Content Server will record such details as when the item is created, viewed, or
modified, when its permissions are changed, and so on.

7.6.3 Configuring Basic System Parameters

Set the Date Format

Content Server allows you to modify the default date and time formats used for
entering dates and displaying short- and long-format dates. The default date
format is as follows:

• Month/day/year

• Month displayed as two digits (for example, June is 06)

• Year displayed as four digits (for example, 1998)

• Time displayed according to the 12-hour clock (for example, 1:45 PM)

Create Attributes and Categories

Each type of item in the Content Server database has a default set of attributes,
and all items are part of the system category. You may want to create custom
attributes and categories for the items that users add to the Content Server
database, as this can assist in managing and searching the contents of the
database.

Set the User Display Name Format

You can set the format that Content Server uses to display user names. You can
choose between the user's logon ID, the first name and last name, or the first and
last names and middle initial.

Administer Modified Date Triggers

You can specify events that trigger an update to an item's modified date stamp
in Content Server.

Specify Document Compose Settings

Content Server lets you set preferred text editors for MIME types or for enabling
or disabling creation types for new documents.

Configure Storage Provider Settings

Adding Storage Providers to Content Server lets you store documents and other
items in various storage media according to rules that you establish.

136 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.6. Perform Additional Tasks Before Users Connect

The OpenText Archive and Storage Services can be used to connect to Archive
Server. Refer to the documentation available for OpenText™ Archive Center on
My Support (https://knowledge.opentext.com).

7.6.4 Configure System Administration

Scheduled Activities
You can set Content Server to monitor various activities in the system and
provide you with reports. You can also specify whether you want to keep the
data or purge it once a report is generated.

7.6.5 Change the Password of the Admin and System

Support Users
Admin is a powerful user that can perform numerous administrative tasks. To
perform the initial configuration of Content Server, you log on as the Admin user.
(See “The Content Server Administration Page” on page 75.)

The System Support user (sys_support) is another built-in user that can perform
important administrative tasks. It is intended to be used in a deployment where the
Admin user has been disabled. When Content Server is installed, the password of
the System Support is the same as the password of the Admin user: livelink.

Tip: For information on how to disable the Admin user and how to use the
System Support user, see OpenText Content Server Admin Help - System
Administration (LLESWBA-H-AGD).

For security reasons, OpenText recommends that you change the default passwords
of the Admin and System Support users after you have installed and performed the
initial configuration of Content Server.

Tip: Record the new passwords on Section 10.3: “Content Server Installation
Worksheet” on page 173.

To change the password of the Admin user:

1. Logged on as the Admin user, click the My Account menu, and then click
Change Password.

2. On the Content Server Admin User Password Change page, enter livelink in
the Old Password box, then enter a new password in the New Password and
Verify New Password boxes.

3. Click Save Changes.

To change the password of the System Support user:

1. Logged on as the Admin user, (or as a user who has both the System
Administration rights and the User administration rights user privileges and

LLESCOR240100-IGD-EN-01 Installation Guide 137

Chapter 7 Complete the Installation and Setup of Extended ECM

the Web Admin usage privilege), open the Change sys_support Password
administration page. It is located in the User and Groups section of the Content
Server Administration page.

2. In the sys_support Password area, enter livelink in the Enter Current

Password box, then enter a new password in the New Password and Verify
New Password boxes. Note that you must respect the password complexity
rules that are shown on this page.

3. Click Save Changes.

7.7 Configure Extended ECM Features

This section lists Extended ECM features and components you can configure. Your
license determines which features are available to you.

7.7.1 Document Management

Many Document Management features are available in Extended ECM. The
following section highlights key features. For information about other Document
Management features, see the Content Server Classic Administration Help.

Search
You can use the search capabilities in Extended ECM to create indexes and
maintain their integrity, providing a way for your users to find relevant
information stored in Extended ECM. Users can locate Documents, Folders,
Discussions, and more. Users can also locate items that have a language
associated with them. A search can be as basic as finding Documents that are
similar to a Document in a Workspace. Users can also create more complex
searches using Queries.
Administrators can set multiple Search options for users, including the Find
Similar command, Hit Highlight Summary, Block Size, and Common Authors.
For information about configuring Search, see OpenText Content Server - Search
Administration Guide (LLESWBS-AGD) and OpenText Content Server - Advanced
Indexing and Searching Guide (LLESSRC-GGD).
Collaboration
Features such as Wikis, Wiki Pages, Forums, and Pulse allow users to
collaborate by publishing online content and sharing information. Collaboration
features such as commenting are not available to users until an administrator
enables them. Administrators can also enable and disable collaboration features
for specific item types on the Configure Collaboration Administration page.
For information about configuring Collaboration features, see OpenText Content
Server - Wiki Administration Guide (LLESWIK-AGD) and OpenText Content Server -
Pulse Administration Guide (LLESSOC-AGD).

138 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.7. Configure Extended ECM Features

Properties and Category Attributes

Categories and Attributes organize Content Server items and make them easier
to find. Document properties can be synchronized with object attributes, and
object attributes can be synchronized with document properties.
For information about configuring Properties and Attributes features, see
OpenText Content Server - Category and Attribute Administration Guide (LLESWAT-
AGD) and OpenText Content Server - Document Properties Synchronization
Administration Guide (LLESDPS-AGD).
Document Handling
Documents and Text Documents: Users can add, edit, and add versions of
Documents, text documents, and Compound Documents to Extended ECM.
Users can create facets, facet folders, and facet trees and use them to filter
documents.
Document Templates Volume: The Document Templates Volume allows users to
create document templates for different item types. For information, see
OpenText Content Server - Document Templates Volume Administration Guide
(LLESDTV-AGD).
Collections: Users can add Collections to store pointers to multiple items in a
single location to quickly access the original items. For information, see
OpenText Content Server - Collections Administration Guide (LLESCL-AGD).
Multi-File Output: Users can download, email, and print multiple items in a
single operation when Multi-File Output is configured. For information, see
OpenText Content Server - Multi-File Output Administration Guide (LLESMFO-
AGD).
Syndication: If you have offices or sites in multiple locations, you can configure
syndication. Syndication provides a distributed solution for remote sites so that
Extended ECM users have a similar experience and similar performance
regardless of whether users are accessing the primary installation location or a
remote installation. For information about configuring Syndication, see OpenText
Content Server - Syndication Administration Guide (LLESQDS-AGD) and OpenText
Quick Data Synchronization for use with OpenText Content Server Syndication -
OpenText Content Server (LLESQDS-AWC).
Mobile App
Users access Extended ECM features on a mobile device running the iOS or
Android operating systems. With the Mobile App, users can access and share
Extended ECM content, manage documents and files, complete Workflow
assignments that are designed for Smart View, and view documents that are
marked for offline viewing when a device is not connected to Extended ECM.
For information about configuring the Mobile App, see OpenText Extended ECM
Mobile - Configuration Guide (CSMOB-CGD).

LLESCOR240100-IGD-EN-01 Installation Guide 139

Chapter 7 Complete the Installation and Setup of Extended ECM

7.7.2 Business Workspaces

Business Workspaces
The Business Workspaces module supports enterprise information management
and collaboration centered around business objects. You can define any
meaningful entity in your organization as a business object, for example,
customers and sales orders, processes and projects, material and products,
production plants and facilities, or even a community of people with common
interests.
For information about how to configure Business Workspaces, see OpenText
Business Workspaces - Configuration Guide (CSCWS-CGD).

Intelligent Filing
Closely integrated with Business Workspaces, Intelligent Filing uses OpenText™
Core Capture to automatically file documents into destination subfolders in
Business Workspaces.
For information about how to configure Intelligent Filing, see OpenText Content
Server - Business Workspaces Administration Guide (LLESCWS-AGD).

7.7.3 Business Process Library

OpenText provides pre-configured Business Scenarios as part of Extended ECM.
Business Scenarios can reduce project complexity and implementation efforts by
providing features such as document templates and workspace pre-configurations
for specific lines of business.

For more information about Business Scenarios, see OpenText Extended ECM Business
Scenarios - User Guide (EEBS-UGD).

7.7.4 Viewing and Transformation

OpenText Viewing and Intelligent Viewing

Administrators can enable OpenText Viewing as the default document viewing
application in Extended ECM. OpenText Viewing lets users view, annotate,
search, and print document and image files. OpenText Viewing provides a
subset of Intelligent Viewing functionality.
Intelligent Viewing and Transformation provides a cloud-designed
collaboration viewer and file conversion engine for Extended ECM. The fully
licensed viewer supports extensive document file types and lets users view,
annotate, redact, publish, compare, and convert those documents. Functionality
is provided through cloud micro-services.
For information about how to configure viewing in Extended ECM, see
OpenText Content Server - Viewing and Transformation Administration Guide
(LLESVWX-AGD). For information about how to install Intelligent Viewing, see
OpenText Intelligent Viewing - Windows Install Guide (CLIVSA-IGD) and OpenText
Intelligent Viewing - Linux Install Guide (CLIVSA-IGL).

140 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.7. Configure Extended ECM Features

Renditions
The Renditions module lets users generate and maintain Renditions of
Documents. A Rendition is closely related to a Document or Version but is
different from the original Document in one of two ways. A Rendition might
contain the same content as the original Document but present the information
in a different file format. For example, a Microsoft® Excel® spreadsheet could be
rendered as a PDF file. Optionally, a Rendition could have the same file format
as the original Document, but its contents can be different. For example, the
content of a Microsoft® Word file is localized into a different language and is
still rendered as a Word file.
For information about how to configure Renditions, see OpenText Content Server
- Renditions Administration Guide (LLESRND-AGD).

7.7.5 Document Generation

You can configure Extended ECM to integrate with Extended ECM PowerDocs.
When integrated, users can generate documents from document templates that are
created and maintained by the Content Manager.

To learn more about the Document Generation functionality available in Extended

ECM and for information about how to configure Document Generation features,
see the following documents:

• OpenText Extended ECM - Enterprise Applications Integration and Configuration

Guide (EEP-CGI)
• OpenText Extended ECM PowerDocs - Server Installation Guide (CRMSRV-IGD)
• OpenText Extended ECM PowerDocs - Server Manager Administration Guide
(CRMSRV-AGD)
• OpenText Extended ECM PowerDocs - Content Manager Administration Guide
(CRMCM-AGD)

7.7.6 Integration with Microsoft Office 365

Extended ECM integrates with various Microsoft® applications, including
Microsoft® Office Online and Office 365®.

Content Suite Platform Add-on for Microsoft® Office Online

OpenText™ Content Suite Platform Add-on for Microsoft® Office Online
integrates Extended ECM with Microsoft Office Online. It enables users to work
with Office Online applications, including Microsoft® Word Online, Microsoft®
Excel Online, and Microsoft® PowerPoint Online to edit and open documents
directly in the browser while connected to Extended ECM, without requiring
Office to be installed on the desktop. Users can also co-author documents with
other Extended ECM users. Multiple users can make changes to the same
document at the same time.
For information about how to configure the Content Suite Platform Add-on for
Microsoft® Office Online, see OpenText Content Suite Platform Add-on for Microsoft

LLESCOR240100-IGD-EN-01 Installation Guide 141

Chapter 7 Complete the Installation and Setup of Extended ECM

Office Online - Configuration Guide (CSOO-CGD) and OpenText Content Server -

Content Suite Platform Add-on for Microsoft Office Online Administration Guide
(CSOO-AGD).

Enterprise Connect and Office Editor

OpenText Enterprise Connect provides integrated, interactive access to content
and functionality from supported Enterprise systems. Using Enterprise Connect,
you can work with content from various repositories directly in the applications
that you use on a daily basis, including Windows® Explorer, Microsoft®
Outlook®, and Microsoft Office applications such as Microsoft Word and
Microsoft Excel. Each integration exposes Enterprise Connect functionality in
the application user interface.
For information about how to configure Enterprise Connect and Office Editor,
see OpenText Enterprise Connect and OpenText Office Editor - Installation Guide
(NGDCORE-IGD) and OpenText Content Server - Enterprise Connect Administration
Guide (NGDLLES-AGD).

Extended ECM for Microsoft Office 365

Extended ECM for Microsoft Office 365 lets users work with Office 365 Groups
or Microsoft Teams content within Business Workspaces, add Office 365
documents or emails, and synchronize content between Microsoft Teams and
Extended ECM.
For information about how to configure Extended ECM for Microsoft Office 365,
see OpenText Extended ECM for Microsoft Office 365 - Installation and
Administration Guide (EEMSO-IGD).

7.7.7 Workflow and Automation

Workflows
A Workflow is a predefined business process that can involve multiple users
and tasks and allows users to participate in work processes that run
automatically. Workflows can be simple and consist of a handful of steps or they
can be complex and involve numerous steps, some automated and some
requiring the participation of dozens of users.
For information about how to configure Workflows, see OpenText Content Server
- Workflow Administration Guide (LLESWFW-AGD).

XML Workflow Extensions

XML Workflow Extensions offer additional steps to specify the work, events,
and participants in a Workflow process. The steps in the XML Workflow
Extensions module provide a way to automate certain processes and extend the
functionality of a standard Workflow in Extended ECM.
For information about how to configure XML Workflow Extensions, see
OpenText Content Server - XML Workflow Extensions Administration Guide
(LLESXWE-AGD). For information about how to configure XML Workflow
Extensions in the Cloud, see “Configure XML Workflow Extensions”
on page 144.

142 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.7. Configure Extended ECM Features

LiveReports
LiveReports provide access to information in your organization's Extended ECM
database and enable you to find, organize and present the information stored
there. LiveReports obtain information by issuing Structured Query Language
(SQL) statements to the database.
For information about how to configure LiveReports, see OpenText Content
Server - LiveReports Administration Guide (LLESREP-AGD).
WebReports
WebReports allow you to create reports within Extended ECM that deliver
information from any standard or custom Extended ECM database tables with a
presentation format that you choose. WebReports can use parameters and tags
to manipulate and render the data output and launch additional actions.
For information about how to configure WebReports, see OpenText Content
Server - WebReports Administration Guide (LLESWEBR-AGD).
Notification Center
The Notification Center automates the delivery of notifications about events
users are interested in. Administrators configure notification providers and
details about notification messages such as delivery method, expiry time, and
the number of messages that display in the Notification Center.
For information about how to configure the Notification Center, see OpenText
Content Server - Notification Center Administration Guide (LLESMCT-AGD).
Notifications
Notifications allow users to subscribe to items and processes of interest and then
receive notifications when changes occur.
For information about enabling Notifications and configuring delivery methods,
see OpenText Content Server - Notifications Administration Guide (LLESWBN-AGD).
Reminders
Reminders are scheduled actions that send automated email messages at
specified times. Users can use Reminders to receive alerts and manage the status
of upcoming action items such as renewals and cancellations, required
payments, and product shipments.
For information about how to configure Reminders, see OpenText Content Server
- Reminders Administration Guide (LLESRSB-AGD).
Event Action Center
Extended ECM supports event actions that are triggered in Extended ECM
either by events in external business applications or by internal events. Business
Administrators configure events from different sources.
For information about how to configure the Event Action Center, see OpenText
Extended ECM - Enterprise Applications Integration and Configuration Guide (EEP-
CGI).

LLESCOR240100-IGD-EN-01 Installation Guide 143

Chapter 7 Complete the Installation and Setup of Extended ECM

Configure XML Workflow Extensions

The XML Workflow Extensions module provides steps to automate XML export,
transformation, and import processes with Workflows in Content Server. The
module also provides steps for controlling schedules, sending emails, changing
permissions, or deleting objects in a Content Server Workflow.

When the XML Workflow Extensions module is used in a cloud deployment, there
are specific directories, paths, and file names you must configure when installing
Content Server. An example of a valid XML Workflow Extensions directory in a
cloud deployment is: C:\OPENTEXT\AppData\xmlwfextensions, where C:\OPENTEXT
is the default install path for Content Server.

Information about configuring XML Workflow Extensions administration settings

for a cloud deployment is provided in several topics in OpenText Content Server -
XML Workflow Extensions Administration Guide (LLESXWE-AGD) and in OpenText
Content Server - XML Workflow Extensions User Guide (LLESXWE-UGD). To find these
topics, search for “cloud”. You can perform these tasks at any time, but for reasons
of security or consistency, you may prefer to perform them before users first sign in
to Content Server.

For more information, see OpenText Content Server - System Administration Guide
(LLESWBA-AGD).

7.7.8 Information Governance and Protection

Records Management
Enable Records Management to classify, protect, and manage the lifecycle of
your organization’s documents and physical objects to help reduce litigation risk
and ensure data compliance. Manage documents using RM classifications,
holds, and disposition schedules.
For information about enabling and configuring Records Management, see
OpenText Content Server - Records Management Administration Guide (LLESRCM-
AGD).

Physical Objects
Create virtual objects to represent physical objects such as paper documents,
folders, and boxes to help manage their storage, circulation, and lifecycle.
For more information, see the following documents:

• OpenText Content Server - Physical Objects Administration Guide (LLESPOB-

AGD)
• OpenText Physical Objects - Label Design Guide (LLESPOB-RGD)

Security Clearance
Use Security Clearance settings and Supplemental Markings to manage access to
documents and other items.

144 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.7. Configure Extended ECM Features

For more information, see OpenText Content Server - Security Clearance

Administration Guide (LLESRCS-AGD).

Classifications
Classifications adds taxonomic Classification capabilities to Extended ECM,
providing an alternative way to organize, manage, and browse items.
Administrators can classify items, such as Documents, Compound Documents,
Text Documents, and Folders. When items are classified, users can browse
Classification Trees in addition to the traditional folder hierarchy.
For information about configuring Classifications, see OpenText Content Server -
Classifications Administration Guide (LLESCLS-AGD).

Controlled Viewing and Printing

Used with Classifications or Records Management Classifications, Controlled
Viewing and Printing lets you control the appearance of electronic and printed
copies, and track the printed copies of regulated documents in circulation. When
a Classification is assigned to a document, a configured Control Rule adds
stamps, watermarks, cover pages, and security features to the Controlled
Document when it is viewed or printed. Rule actions can vary, depending on the
user, the document, or other conditions.
For information about how to set up Controlled Viewing and Printing, see
OpenText Content Server - Controlled Viewing and Printing Administration Guide
(LLESCVP-AGD).

7.7.9 Integration with Enterprise Applications

Extended ECM supports integration with enterprise business applications, including
SAP Solutions, SAP SuccessFactors, and Salesforce. Integration between business
applications and Extended ECM lets you use the enterprise information features
available in Extended ECM with the business data and business processes in the
enterprise application.

OpenText Extended ECM Platform

Provides Extended ECM archiving and collaboration functionality for the
enterprise application’s business processes.
For information about how to configure the Extended ECM Platform, see
OpenText Extended ECM - Enterprise Applications Integration and Configuration
Guide (EEP-CGI).

OpenText Extended ECM for SAP Solutions

Includes Extended ECM modules, web services, and an SAP package that allow
you to integrate functionality such as document and records management,
archiving, Workflow, and collaboration into your SAP business processes.
For information about how to configure Extended ECM for SAP Solutions, see
OpenText Extended ECM for SAP Solutions - Installation and Upgrade Guide (ERLK-
IGD) and OpenText Extended ECM for SAP Solutions - Customizing Guide (ERLK-
CGD).

LLESCOR240100-IGD-EN-01 Installation Guide 145

Chapter 7 Complete the Installation and Setup of Extended ECM

OpenText Extended ECM for SAP SuccessFactors

Combines the information and document management features of Extended
ECM with employee records maintained in SuccessFactors. It adds extended
document archiving and collaboration functionality to the employee
management processes of SAP SuccessFactors.
For information about how to configure Extended ECM for SAP SuccessFactors,
see OpenText Extended ECM for SAP SuccessFactors - Installation Guide (EESU-
IGD) and OpenText Extended ECM for SAP SuccessFactors - Customizing Guide
(EESU-CGD).
OpenText Extended ECM for Salesforce
Combines the enterprise information management features of Extended ECM
with business data maintained in Salesforce extending the archiving and
collaboration functionality into Salesforce business processes.
For information about how to configure Extended ECM for Salesforce, see
OpenText Extended ECM for Salesforce - Installation Guide (EESA-IGD) and
OpenText Extended ECM for Salesforce - Configuration Guide (EESA-CGD).

Complete the following procedures to use Extended ECM with enterprise

applications:

• “Deploying Extended ECM Web Services into the application server”

on page 146
• “Deploying Content Web Services” on page 148
• “Configuring host and port for Content Server in Tomcat” on page 149

Deploying Extended ECM Web Services into the application

server
Install the Extended ECM Web Services on your Apache Tomcat server.

Notes

• Use the Content Server Tomcat.

• Make sure that Tomcat has enough initial memory pool. See OpenText
Enterprise Library - Installation and Upgrade Guide (EL-IGD) for memory pool
size recommendations.
• The Tomcat service must be running during the installation.
• Use the default service name for Tomcat. Otherwise, the installer may be
unable to find the service.
• Restart Tomcat manually after the installation.

To deploy Extended ECM Web Services:

1. Download the otsapxecm.war file from OpenText My Support (https://

knowledge.opentext.com/knowledge/llisapi.dll/Open/76755705).

146 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.7. Configure Extended ECM Features

2. Stop the Tomcat service.

3. Copy the otsapxecm.war file into the <Tomcat home>/webapps/ directory.
4. Start the Tomcat service.
5. After deploying the services, change the directory of the log files.

a. Open the <Tomcat home>/webapps/otsapxecm/WEB-INF/classes/log4j.xml

file in an editor.
b. Change the line
<param name="File" value="logs/ecmlink.log" />
to
<param name="File" value="../logs/ecmlink.log" />

6. Optional: changing parameter values in web.xml file

Check if you need to change the parameter values in the web.xml file.

a. Open the <Tomcat Home >/webapps/otsapxecm/WEB-INF/web.xml file for

editing.
b. You can change the following parameter values:
<param-name>LivelinkServer</param-name>
<param-value>localhost</param-value>

<param-name>LivelinkServerPort</param-name>
<param-value>2099</param-value>

<param-name>LivelinkEncoding</param-name>
<param-value>UTF8</param-value>

Deploying Extended ECM CMIS Web Services into the application

server
Install the Extended ECM CMIS Web Services on your Apache Tomcat server.

Notes

• Use the Content Server Tomcat.

• Make sure that Tomcat has enough initial memory pool. See OpenText
Enterprise Library - Installation and Upgrade Guide (EL-IGD) for memory pool
size recommendations.
• The Tomcat service must be running during the installation.
• Use the default service name for Tomcat. Otherwise, the installer may be
unable to find the service.
• Restart Tomcat manually after the installation.

To deploy Extended ECM CMIS Web Services:

1. Download the xecm-cmis.war file from OpenText My Support (https://

knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=76753614&
objAction=browse&viewType=1).

LLESCOR240100-IGD-EN-01 Installation Guide 147

Chapter 7 Complete the Installation and Setup of Extended ECM

2. Stop the Tomcat service.

3. Copy the xecm-cmis.war file into the <Tomcat home>/webapps/ directory.

4. Start the Tomcat service.

5. After deploying the services, change the directory of the log files.

a. Open the <Tomcat home>/webapps/otsapxecm/WEB-INF/classes/log4j2.

xml file in an editor.

b. Change the line

<param name="File" value="logs/ecmlink.log" />
to
<param name="File" value="../logs/ecmlink.log" />

6. Open the <Tomcat home>/webapps/xecm-cmis/WEB-INF/classes/xecm_cmis.

properties file for editing. Check whether you must change the following
parameters:

• If Tomcat runs on a different machine than Content Server, set the server.
url parameter to the URL of Content Server.

• If the Content Server base URL is different from /OTCS/cs.exe, set the url.
base parameter accordingly.

7. Restart Tomcat manually after the installation.

Deploying Content Web Services

Extended ECM Platform requires OpenText Content Web Services. During the
installation of Content Server, the Content Web Services WAR file is placed in the
<Content Server home>/webservices/java/webapps directory.

Deploy the web service cws to the Tomcat installation on the server where you also
installed Archive Center.

To deploy Content Web Services:

1. Copy the cws.war file from <Content Server home>/webservices/java/webapps

to your <Tomcat home>/webapps directory.

2. UNIX/Linux systems only: After deploying the services, change the directory of
the log files.

a. Open the <Tomcat home>/webapps/cws/WEB-INF/classes/log4j.xml file in

an editor.
b. Change the line
<param name="File" value="logs/cws.log" />
to
<param name="File" value="../logs/cws.log" />

148 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.7. Configure Extended ECM Features

Configuring host and port for Content Server in Tomcat

After the installation of Apache Tomcat and the deployment of the Extended ECM
Web service, the server name is localhost with port 2099. You can change these
settings, for example, if you need to address more than one Content Server instance.

To change host name and port of Content Server:

1. Open the <Tomcat home>\webapps\otsapxecm\WEB-INF\web.xml file in an editor.

2. Find the following elements and change the values according to your needs:
<context-param>
<param-name>LivelinkServer</param-name>
<param-value>cs.example.com</param-value>
</context-param>
<context-param>
<param-name>LivelinkServerPort</param-name>
<param-value>2099</param-value>
</context-param>
<context-param>
<param-name>LivelinkEncoding</param-name>
<param-value>UTF8</param-value>
</context-param>

3. Restart the Tomcat service to apply the changes.

7.7.10 External Sharing and Collaboration

The Content Sharing module lets users share Emails, Documents, Folders, Email
Folders, or Business Workspaces that reside in Extended ECM with other users who
are inside or outside of the organization. Users select the items that they want to
share in Smart View, and then specify who they want to share them with in an
external share provider, such as OpenText™ Core Share or Microsoft® Teams .

For information about how to configure this feature, see OpenText Content Server -
Content Sharing Administration Guide (LLESEFS-AGD).

7.7.11 Digital Signature

DocuSign® or OpenText™ Core Signature
You can configure signature providers, such as DocuSign or Core Signature, so
that users can electronically sign documents as part of a Workflow or
independent of a Workflow. When you use DocuSign or Core Signature, you
can send Documents to be signed by people outside of your organization.
For information about how to configure signature providers, see OpenText
Content Server - Signature Providers Administration Guide (LLESSIG-AGD).
Electronic Signatures
You can configure and use the OpenText Electronic Signatures module to extend
Workflow capabilities to provide a secure way of managing Document review
and approval processes. Electronic Signatures allows you to initiate signing
Workflows in which Documents or Forms circulate and are either approved and
signed or rejected by authorized users, called Signing Authorities. Information

LLESCOR240100-IGD-EN-01 Installation Guide 149

Chapter 7 Complete the Installation and Setup of Extended ECM

associated with each signing event, such as who approved a Document and
when, is recorded and displayed through audit trails.
If you want to use the Electronic Signatures Robot step to convert documents to
PDF format, you must use and configure a rendition engine. OpenText
recommends you use OpenText™ Intelligent Viewing. If Electronic Signatures is
not deployed in the Cloud, you can also use OpenText™ Blazon™ for Content
Suite.
For information about how to configure Electronic Signatures features, see
OpenText Content Server - Electronic Signatures Administration Guide (LLESESN-
AGD). Before you begin, also see “Configure Electronic Signatures” on page 150

Configure Electronic Signatures

After the Electronic Signatures module is installed as part of your Extended ECM
installation, you might need to complete the following tasks:

• “Install the Appligent products” on page 150

• “Configure the Electronic Signatures agents” on page 151

Install the Appligent products

If your Extended ECM installation is on a computer running Microsoft Windows,

you must install Appligent products in your Windows environment.

Note: This information is only applicable if Extended ECM is not deployed in

the Cloud.

From 24.1, if you are using Electronic Signatures or Controlled Viewing and
Printing, you must download the supporting Appligent libraries from My Support.

To install Appligent products on Windows:

1. Download the libraries from My Support (https://support.opentext.com/csm?

sys_kb_id=3b6385494721f950fd2258e5536d43da&id=kb_article_view&
sysparm_rank=1&sysparm_tsqueryId=c6bb5901db213d10e27c7f93e2961901).

2. Right-click the downloaded library file and select 7-zip > Extract here.
The Appligent folder with Appligent libraries is created.

3. Copy the Appligent folder and place it in C:\ProgramData.

4. If you want to place the Appligent folder at some other location, then set the
complete path of the Appligent folder in the <APPLIGENT_HOME>
environment variable.

Note: If you are upgrading from an older version and Electronic Signatures
was already configured on that version, you need not perform the above steps.

150 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.7. Configure Extended ECM Features

Configure the Electronic Signatures agents

Electronic Signatures uses agents to perform tasks on a schedule. You must enable
only one instance of each Electronic Signatures agent in a Content Server cluster.

The following table lists and describes the tasks performed by Electronic Signatures
agents.

Table 7-2: Electronic Signatures agents

Name AgentID Function

SignatoryAgent 2501 Completes Electronic
Signatures Robot Workflow
steps, if the steps require
conversion of Workflow
attachments to PDF
documents. This agent runs
every 5 minutes.
GenerationAgent 2502 Completes Electronic
Signatures Generation
Workflow tasks. This agent
runs every 5 minutes.
Signing Password Expired 2503 Sends email notifications
about the expiration of
signing passwords. This
agent runs once a day.

You can modify these

settings on the following
administration pages:
• Configure Signing
Password Settings – see
OpenText Content Server -
Electronic Signatures
Administration Guide
(LLESESN-AGD)
• Configure Scheduled
Activities – see OpenText
Content Server -
Notifications
Administration Guide
(LLESWBN-AGD)

LLESCOR240100-IGD-EN-01 Installation Guide 151

Chapter 7 Complete the Installation and Setup of Extended ECM

Name AgentID Function

Clear undolabelinfo Table 2504 Removes records that are no
longer needed.
• For completed and
archived Workflows, it
removes their records in
the undolabelinfo
table.
• For completed and
archived Workflows, it
removes their records in
the fieldinfo table.
• For completed
Workflows, it removes
their records in the
itemrefinfo and
itemrefdata tables.
This agent runs once a week.

7.7.12 Perspectives
Perspectives are used to customize the Smart View interface. For information about
how to administer Perspectives, see OpenText Content Server - Perspectives
Administration Guide (LLESPRSP-AGD).

7.7.13 Add-on Engineering

Extended ECM for Engineering is an add-on to the Extended ECM solution.
Extended ECM for Engineering provides you with a secure, collaborative repository
to create, share, review, and manage your engineering documents.

For information about how to configure Extended ECM for Engineering, see
OpenText Extended ECM for Engineering - Administration Guide (CSENG-AXE).

Before you configure Extended ECM for Engineering, you must set environment
variables that allow the system to extract metadata from two-dimensional CAD
drawings. Depending on your environment, see either “Set environment variables
for CAD metadata extraction on Windows” on page 153 or “Set environment
variables for CAD metadata extraction on Linux” on page 153.

152 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 7.7. Configure Extended ECM Features

Set environment variables for CAD metadata extraction on

Windows
To configure metadata extraction of 2D CAD files on Microsoft® Windows®, set up
environment variables by performing the following actions:

1. Add the Teigha path to the existing environment path variable: <OT-HOME>/
core/module/xeng/teigha.

2. Restart Content Server.

Set environment variables for CAD metadata extraction on Linux

To configure metadata extraction of 2D CAD files on a Linux machine, set up
environment variables by performing the following actions:

1. Modify the LD_LIBRARY_PATH variable in <Installation Directory>/start_

llserver to make the metadata extraction work.

2. After the module installation completes, find theif[ "$LLDBHOME" ]; then line in
the start_llserver script.
3. Add LD_LIBRARY_PATH=$LLHOME/core/module/xeng/Teigha:$LD_LIBRARY_PATH
above the previous line.

7.7.14 Add-on Government

Extended ECM for Government is an add-on to the Extended ECM solution. It is an
Enterprise Content Management solution for modern, digital administration in
central and local government, and other public sector areas. Extended ECM for
Government adds value in all areas where users require digital file management,
case management, content lifecycle management, and integration capabilities into
various environments and leading applications.

For information about how to administer and configure Extended ECM for
Government, see the following guides:

• OpenText Extended ECM for Government - Installation Guide (EEFGDE-IGD)

• OpenText Extended ECM for Government - Configuration Guide (EEFGDE-CGD)

LLESCOR240100-IGD-EN-01 Installation Guide 153

Chapter 8
Install Additional Instances of Extended ECM

You can scale your Content Server environment by adding instances of Content
Server and connecting them to the database that you created in “Create the Content
Server Database” on page 82.

To accommodate larger numbers of users, you can install new Front-End instances
of Content Server, deploy them behind a load-balancer, and let users access them
with a single URL. For more information, see “Front-End Instances” on page 156.

To handle the load of Content Server agent processing without affecting the overall
responsiveness of your Content Server deployment, you can install one or more
Agent Servers. See, “Agent Servers” on page 157

To increase the capacity of your Search infrastructure, you can install additional
instances of Content Server and deploy them as Additional Admin servers. To do
this, follow the instructions in “Admin Servers” on page 164

Note: The Content Server installer does not let you install more than ten
instances of Content Server on a single Windows server.

8.1 Copy the key.bin file from the First Content

Server Instance
Content Server uses the key.bin file to store the data encryption key used by
Content Server throughout a cluster. This file must be the same on each instance in
your Content Server cluster. To ensure that it is, copy the key.bin file from your first
Content Server instance to any additional instance that you install. You must do this
before you start the Content Server service on the additional instance.

To copy the key.bin file to new instances of Content Server:

1. Stop the Content Server service on the first instance of Content Server.

2. Make a copy of the <Content_Server_home>/config/secrets/key.bin file.

3. Restart the Content Server service on the first instance of Content Server.

4. Install an additional instance of Content Server, following the instructions in

this document.

Caution
Do not start Content Server until you have completed the following
step.

LLESCOR240100-IGD-EN-01 Installation Guide 155

Chapter 8 Install Additional Instances of Extended ECM

5. Take your saved key.bin file, and copy it to the <Content_Server_home>/

config/secrets/ directory of your new Content Server instance, overwriting
the existing key.bin file at that location.

8.2 Front-End Instances

To install additional Front-End instances of Content Server for scaling purposes,
follow the instructions in this guide, with the following exceptions:

• Connect to the database that you created during the initial Content Server
installation. Do not create a new database.
• Install exactly the same modules that you installed during the initial Content
Server installation.
• On the Admin Server Configuration page, confirm that the initial Content
Server installation houses the default Admin server.
• When the Configure and Migrate the Search System page appears, click
Continue.
• You will not see the following pages:

– the Create New Enterprise Data Source page (because the Enterprise Data
Source already exists on the primary Admin server)
– the Status page that displays the progress of the database creation (because
the database has already been created)
– the License Setup page (because you have already applied a valid license to
your entire Content Server environment)

For optimum performance, OpenText recommends that you install only one Content
Server instance on a given computer, especially for a production deployment of
Content Server system. For testing and prototyping with Content Server, you may
find it convenient to install more than one Content Server instance on a given
computer.

If you install multiple Content Server instances on one computer, ensure that the
installation folder, URL mappings, server ports, and program folder name of each
instance are unique. In addition, verify that all the data flow processes, search
servers, and index servers associated with each existing Content Server installation
are running. See System Object Administrator in the Content Server Administrator
Online Help.

156 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 8.3. Agent Servers

8.3 Agent Servers

Content Server agents perform a variety of background tasks, such as gathering and
sending user Notifications, creating PDF renditions of documents, creating System
Object Volume messages, and so on. A default installation configures Content Server
to run every agent. This is a good configuration for a single instance of Content
Server, but not for a clustered installation. You should not run the same agent on
multiple Content Server instances because multiple instances of the same agent can
come into conflict with each other.

A typical practice in a new clustered Content Server deployment is to designate one

server to run the Content Server agents. Often, that server is an Admin server. More
complicated agent deployments, where different Content Server instances are each
configured to run particular agents, are also possible.

You can also configure a dedicated Content Server instance to run only the Content
Server agents (without acting as a front-end instance or Admin server). You can do
this during your initial setup of Content Server, or later. It is a common performance
improvement to make to a Content Server implementation that has been running for
some time.

Tip: Agents require the Content Server service to be running, so you cannot
run agents on a standalone Admin server that does not run the Content Server
service.

A Content Server instance that runs the agents for a Content Server cluster is
referred to in this document as an agent server.

Running agents requires additional CPU and memory. It is best to run agents on a
server that is not heavily used. In a highly-scaled environment, you could distribute
the agents and run them on specialized agent servers. A specialized agent server is a
Content Server instance that runs one or several agents, but not every agent that is
used by Content Server. For example, in a workflow-heavy environment, you could
run the wfagent (workflow agent) on a specialized agent server and the rest of the
agents on a different server.

Notes

• Although the Content Server Distributed Agent and its workers run as
Content Server agents, agents and Distributed Agents are not synonymous.
A Distributed Agent runs Distributed Agent workers that are also
configured as agents in the opentext.ini file. Only one Distributed Agent
can run at a time in a Content Server cluster, but the Distributed Agent
workers that it controls can run on numerous instances in the cluster. For
information on Distributed Agents, see OpenText Content Server Admin Help -
Distributed Agent Administration (LLESDA-H-AGD).
• Processes that run as agents normally have a Content Server administration
page where the process can be configured. As much as possible, you should
perform any configurations using the administration page. This section deals

LLESCOR240100-IGD-EN-01 Installation Guide 157

Chapter 8 Install Additional Instances of Extended ECM

only in the configurations that are necessary to run Content Server agents on
a specific Content Server instance.

8.3.1 Install an Agent Server

To set up an agent server, you take a normal Content Server installation and
configure it to act as an agent server.

The settings that affect agents are found both in the opentext.ini file and in the
Content Server database. In practice, you should only change the settings in the
opentext.ini file. Under normal circumstances, you do not need to make changes to
the database and, in general, OpenText recommends that you do not directly update
the Content Server database.

Opentext.ini File Settings

The settings that enable and disable agents are in the opentext.ini file. Unlike the
Content Server database, whose settings affect every instance in a Content Server
cluster, the settings in the opentext.ini file affect only the current instance. If you
are configuring multiple agent servers, you must edit each opentext.ini file
separately.

Several sections of the opentext.ini file are involved:

[options]
For any agent to run, EnableAgents must be TRUE in the [options] section of the
opentext.ini file.

Note: OpenText recommends that you do not modify the value of

EnableAgents. EnableAgents must be TRUE on all instances for the eLink
module to work. It is not necessary to set EnableAgents=FALSE to prevent
agents from running on a Content Server instance.
[loader]
For an agent to run, it must be loaded in the [loader] section of the opentext.
ini file. It can appear after the load= line, for example: load=sockserv;agents;
notify, or it can appear after a specialized loader line, for example load_
relagent=relagent or load_daagent=daagent. See “Generic Agents and
Specialized Agents” on page 161.
[<Agent_Name>]
For each agent that appears in the [loader] section, there is a named section of
the opentext.ini file that contains parameters for the agent.
For example, in a default installation of Content Server, the loader section reads
load=sockserv;agents;notify;wfagent;wrscheduleagent;
wrcollectionagent;commagent. Each of the named agents has its own section in
the opentext.ini file, such as this one for wfagent (the workflow agent):
[wfagent]
lib=./lib/lljob.so
name=lljob
prio=critical

158 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 8.3. Agent Servers

timeout=5000
info=./config/opentext.ini;wfagent
StartScript=./scripts/llfull.lxe
JobScript=./scripts/wfagent_run.e
SleepIntervalSec=600
WSessionCleanSeconds=604800
AgentOffsetSeconds=86400
FIFOProcessingOrder=false
SendEmailOnErrors=true

Some parameters in an [<agent_name>] section, such as StartScript and prio

are always present, whereas others, such as WSessionCleanSeconds (above)
appear only for the specific agent being configured.
Typically you should not change any of these parameters, unless advised to by
OpenText Customer Support.
[scheduleactivity]
The [scheduleactivity] section of the opentext.ini file governs jobs that run
in the agents and notify threads. For an agent to run in one of those threads, its
agent ID must have a value of 1 (enabled). If the agent ID of an agent that runs
in the agents or notify thread does not appear in this section, its value defaults
to 1. If an agent ID appears in this section with a value of 0, it does not run in the
agents or notify thread, regardless of any settings elsewhere in the opentext.
ini file.

ActivityIDs and ExcludeActivityIDs

Agents can be added to or removed from the agents and notify threads by
using the ActivityIDs and ExcludeActivityIDs parameters. See “Generic
Agents and Specialized Agents” on page 161.

Content Server Database Settings

The AgentSchedule table in the Content Server database has entries that affect the
operation of agents.

AgentSchedule
For an agent to run, it must appear in the AgentSchedule table in the Content
Server database, with a value of 1 in the Enabled column. This database table is
updated programmatically, so you should not make changes to it directly,
unless OpenText Customer Support advises you to.

LLESCOR240100-IGD-EN-01 Installation Guide 159

Chapter 8 Install Additional Instances of Extended ECM

Agent Names and IDs

When you work on configuring agents, you may need to determine the ID that
belongs to a given agent. There are a few ways to find this information. Bear in mind
that an agent may be referred to in several ways.

Example 8-1: Finding information on the verifyAgent

[loader]
In the [loader] section of the opentext.ini file, the verifyAgent is loaded
by its own specialized loader:
[loader]
load_verify=verifyAgent

[<Agent_Name>]
The verifyAgent has an agent ID of 12568 that appears in its configuration
section of the opentext.ini file.
[verifyAgent]
lib=./lib/lljob.so
name=lljob
prio=critical
timeout=5000
info=./config/opentext.ini;verifyAgent
StartScript=./scripts/llfull.lxe
JobScript=./scripts/agent_run.e
CRON=0,5,10,15,20,25,30,35,40,45,50,55 * * * *
SleepIntervalSec=60
ActivityIDs=12568

Documentation
The verifyAgent is referred to in the Content Server user interface and
documentation as the Index Verifier.

Information on agent names and IDs can also be found in other places:

Content Server Database

Query the Content Server database with Select agentname, agentid from
agentschedule. This will return a list of agent names and numeric agent IDs.
(Not all of the agent IDs appear with an agentname however.)
My Support
The Registered AgentIDs list on My Support is a list of agent IDs registered by
third-party developers.
Content Server Logs
Agent IDs, names, and friendly names appear in the agent logs: agents_
run<####>.html, notify_run<####>.html and so on.

160 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 8.3. Agent Servers

Generic Agents and Specialized Agents

Agents can run in a thread that aggregates multiple agents (the agents or notify
thread) or a specialized agent thread, such as wrscheduleagent (the WebReports
scheduling agent).

The agents and notify threads run multiple specialized agents one after the other.
You can change the collection of agents that the agents and notify threads run by
using the ExcludeActivityIDs and ActivityIDs settings.

agents
The agents thread runs a default set of agents. You cannot add to the default set,
but you can remove an agent from it by adding its agent ID to the
ExcludeActivityIDs setting in the [agents] section of the opentext.ini file.

notify
The notify thread runs the agents whose agent IDs appear after the
ActivityIDs setting in the [notify] section of the opentext.ini file.

Take care when you adjust these parameters. You should use the
ExcludedActivityIDs and ActivityIDs settings to run an agent in either the agents
or notify thread, but it is possible to inadvertently set it to run in both or neither.
The following four combinations are possible, but only the top and bottom ones are
reasonable configurations:

Table 8-1: Results of combined ExcludedActivityIDs and ActivityIDs settings

Agent ID appears Agent ID appear Agent runs in Agent runs in

after the after the notify thread agents thread
ExcludedActivityI ActivityIDs
Ds setting in the setting in the
[agents] section [notify] section?
Yes Yes Yes No
Yes No No No
No Yes Yes Yes
No No No Yes

LLESCOR240100-IGD-EN-01 Installation Guide 161

Chapter 8 Install Additional Instances of Extended ECM

Agent Server Configuration Examples

The following are sample agent server configurations.

General Agents Server

To designate a single Content Server host to run every agent, configure it so that it
loads all of the agents that appear in the [loader] section.

Example 8-2: Agent server running all agents

Agents server, opentext.ini excerpts

[loader]
load=sockserv;agents;notify;wfagent;wrscheduleagent;wrcollectionagent;commagent
load_relagent=relagent
load_distributedagent=distributedagent
load_daagent=daagent
load_verify=verifyAgent

In the [scheduleactivity] section of the opentext.ini file, ensure that

every agent that you want to run has its agent ID set to 1. If there are agents
that you do not want to run, set their agent ID to 0.
[scheduleactivity]
1000=1
4000=1
4100=0
4101=0
4102=0
8900=1
8999=1
9000=1
9001=1
3502=1
8000=1
3601=1

All other Content Server instances, opentext.ini excerpt

On every other Content Server in the cluster, load only the sockserv and
notify agents.
load=sockserv;notify

Specialized Agent Server

A specialized agent server runs one or several agents, but not every agent. In the
examples below, the first one shows how to configure a single Content Server
instance to run only the Index Verifier. The second example shows how to configure
an instance to run only the Content Move agent in the notify thread. In both cases,
an additional agent server that is configured similarly to the one in the above
example runs all of the remaining agents.

Example 8-3: verifyAgent running on a specialized agent server

In this example, a single Content Server instance runs the verifyAgent, and a
different instance, acting as a general agent server, runs all the other agents.

162 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 8.3. Agent Servers

Specialized agent server, opentext.ini excerpts

[loader]
load_verify=verifyAgent

General agent server, opentext.ini excerpts

[loader]
load=sockserv;agents;notify;wfagent;wrscheduleagent;wrcollectionagent;commagent
load_relagent=relagent
load_distributedagent=distributedagent
load_daagent=daagent

All other Content Server instances, opentext.ini excerpt

On every other Content Server in the cluster, load only the sockserv agent.
load=sockserv

Example 8-4: Content Move running on the Notify thread of a specialized

agent server

In this example, the Content Move agent (which normally runs in the agents
thread) has been removed from the general agent server. Is is configured to run
in the notify thread on a separate Content Server instance.

Specialized agents server, opentext.ini excerpts

[loader]
load=sockserv;notify
# Other than sockserv, run only the notify thread.
# Additional configurations below will ensure that only Content Move (agentid=1964)
runs on the notify thread.

[notify]
lib=./lib/lljob.so
name=lljob
prio=critical
timeout=5000
info=./config/opentext.ini;notify
StartScript=./scripts/llfull.lxe
JobScript=./scripts/agent_run.e
SleepIntervalSec=300
ActivityIDs=1964
# 1964 is the Content Move agent. On this machine, run only the Content Move agent
on the Notify thread.
# Every other agentID that the Notify thread would normally run is handled by the
general agent server.

General agent server, opentext.ini excerpts

[loader]
load=sockserv;agents;notify;wfagent;wrscheduleagent;wrcollectionagent
load_relagent=relagent
load_distributedagent=distributedagent
load_daagent=daagent
load_verify=verifyAgent

[agents]
[…]
ExcludeActivityIDs=3000,3501,5000,8999,9000,9001,9999,12568,20201,20200,1964

LLESCOR240100-IGD-EN-01 Installation Guide 163

Chapter 8 Install Additional Instances of Extended ECM

#1964 = Content Move agent. It is excluded from running in the agents thread on
this instance.

[notify]
[…]
ActivityIDs=3000,3501,5000,8999,9000,9001,9999
#1964 has been removed from ActivityIDs on this instance so Content Move does not
run in the notify thread.

All other Content Server instances, opentext.ini excerpt

load=sockserv

8.4 Admin Servers

A single Content Server computer is capable of maintaining the entire search
infrastructure if it is not large, but OpenText recommends that you create indexes on
one or more additional hosts for a production deployment of Content Server.

Installing an additional Admin server is similar to performing a primary installation.

The difference is that, once you have completed the installation, you disable the
Content Server service on the additional host. The additional Admin server should
run only the Content Server Admin service.

Depending on your computer’s operating system, proceed to one of the following

sections:

• “Install an Additional Admin Server on Windows” on page 164

• “Install an Additional Admin Server on Linux” on page 165

8.4.1 Install an Additional Admin Server on Windows

On the secondary Content Server host, map the drive that houses the Content Server
installation folder. Record the host name, service name, Admin server port number,
and Admin server password for the Additional Admin server on Section 10.3:
“Content Server Installation Worksheet” on page 173.

To install an Additional Admin server on Windows:

1. On the computer that you want to make an Additional Admin server, log in as a
user that belongs to the Administrators group.

2. Install a new instance of Content Server, as described in “Front-End Instances”

on page 156, but do not start the services when installation is complete.

3. In the Services Control Panel item, configure the Content Server services, as
follows:

a. Disable the Content Server (<service_name>) service.

164 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 8.4. Admin Servers

i. In the right pane, right-click the Content Server (<service_name>)

service, and then choose Properties.
ii. In the Startup type drop-down list, click Disabled.
iii. Click OK.
b. Set the Content Server Admin (<service_name>) service to start
automatically.

i. In the right pane, right-click the Content Server Admin

(<service_name>) service, and then choose Properties.
ii. In the Startup type drop-down list, click Automatic.
iii. Click OK.

After you create an Additional Admin server, you need to register it on the Default
Admin server. For information on this step, see “Register an Additional Admin
Server” on page 166.

8.4.2 Install an Additional Admin Server on Linux

On the secondary Content Server host, mount the drive that houses the Content
Server installation folder. Record the host name, service name, Admin server port
number, and Admin server password for the secondary Admin server on
Section 10.3: “Content Server Installation Worksheet” on page 173.

To install an Additional Admin server on Linux:

1. On the host computer that you want to use as an Additional Content Server
host, log on as the user that runs Content Server.

2. Follow the instructions in this guide to install Content Server, but do not start
the Content Server processes when the installation is complete .

3. At the operating system prompt, change to the directory where Content Server
is installed, and start the Content Server Admin process by running ./start_
lladmin.

After you create an Additional Admin server, you need to register it on the Default
Admin server. For information on this step, see “Register an Additional Admin
Server” on page 166.

LLESCOR240100-IGD-EN-01 Installation Guide 165

Chapter 8 Install Additional Instances of Extended ECM

8.4.3 Register an Additional Admin Server

After you have installed an Additional Admin server, you need to register it with
the Default Admin server. This section describes how to register an Additional
Admin server so that you can create indexes and related dataflow processes on that
host.

For additional information on registering the Admin server of an Additional

Content Server host after the installation and initial setup of Content Server, see
OpenText Content Server Admin Help - System Administration (LLESWBA-H-AGD).

Note: Do not register an Admin server with more than one Content Server
host.

To register an Additional Admin server on the Default Admin server:

1. Ensure that the Admin server service is running on the secondary Admin server
computer.

2. In the Search Administration section of the Content Server Administration

page, click Open the System Object Volume.
On the Content Server System page, click Add Item, and then click Admin
Server.

3. Enter the following information on the Add: Admin Server page.

a. In the Alias Name box, type a name for the secondary Admin server .

b. In the Host Name box, type the name of the computer where the secondary
Admin server is installed.

c. In the Port Number field, type the port number on which the secondary
Admin server listens.

Tip: The Port Number is the number of the Admin Port that you
entered during installation. (See “Install Extended ECM on the
Operating System“ on page 47.) Content Server records this port
number in the <Content_Server_Home>/config/opentext.ini file as
the value of the port parameter in the [OTAdmin] section.

d. Type the Admin server password in the Password and Verify Password
boxes.

e. To have this Admin server manage the storage folder, select the Enable
check box located in the File Cache section and enter the address of the file
cache In the Directory box.

f. Click Add.

166 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

Chapter 9
Uninstall Extended ECM

This chapter describes how to remove Content Server from a host computer. If you
are upgrading to a newer version of Content Server, it may not be necessary to
uninstall the older version. For more information, see OpenText Extended ECM -
Upgrade Guide (LLESCOR-IUP).

9.1 Uninstall Content Server on Windows

Content Server uses Windows Installer to remove components from a Windows
platform. The program is designed to remove all program files installed at the time
of the Content Server installation, but it will not remove files that have been added
or modified after the initial installation. In addition, Content Server’s indexes are not
removed. This is beneficial because you can retain the indexes for use if you upgrade
your Content Server software.

After the uninstallation process completes, Windows Installer advises you of files or
folders that it could not remove.

To uninstall Content Server on Windows:

1. Stop the Content Server services. Stop your application server, if you have been
using one to run Content Server.

2. Using the Windows application for removing programs (for example, Programs
and Features), select the Content Server installer, and then click Uninstall.

3. Use the utility's Automatic method to remove the Content Server program.
After the uninstallation process completes, Windows Installer advises you of
files or folders that it could not remove.

9.2 Uninstall Content Server on Linux

Note: When you uninstall Content Server in a Linux environment, Content
Server's indexes are also removed. You should consider backing up the index
information so that it can be retained if you upgrade Content Server.

To uninstall Content Server or a Content Server secondary installation on

Linux:

1. Log in to the Linux host as the user that runs Content Server.

2. At the operating system prompt, change to the <Content_Server_Home>

directory and then type the following command to stop the Content Server and
Admin servers:

LLESCOR240100-IGD-EN-01 Installation Guide 167

Chapter 9 Uninstall Extended ECM

./stop_llserver

3. Delete the directory tree of the Content Server installation.

168 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

Chapter 10

Appendix A – Extended ECM Installation

Worksheets

This Appendix contains worksheets on which you can record user names,
passwords, and other important information required for the installation of Content
Server and its supporting software. Select the worksheets that apply to your
database and web server, and then use the Content Server installation worksheet to
track Content Server installation settings. Save the information you record on these
worksheets and store them in a secure place. You will need this information if you
upgrade Content Server.

10.1 Database Installation Worksheets

In the following tables:

• Items that have a check mark ( ) in the Required for Installation Column must
be set before you can start the installation of Content Server.

• Items that have a check mark ( ) in the Configured in Content Server are set
during the initial configuration of Content Server.

• If a default value exists for an item, it is listed in the Value column.

Table 10-1: SAP HANA Worksheet

Setting Value Required for Configured in

Installation Content Server
SAP HANA server name

SAP HANA server port 30115

SAP HANA administrator SYSTEM

account
SAP HANA administrator
account password
Name of SAP HANA user
that accesses the Content
Server database
Password of SAP HANA
user that accesses the
Content Server database

LLESCOR240100-IGD-EN-01 Installation Guide 169

Chapter 10 Appendix A – Extended ECM Installation Worksheets

Setting Value Required for Configured in

Installation Content Server
Name of SAP HANA <Same_As_User_Name>
schema for Content Server
database

Table 10-2: Oracle Database Worksheet

Setting Value Required for Configured in

Installation Content Server
Oracle System User name system

Oracle System User manager

password
Service name (database
alias)
Oracle SID or Oracle
HOME directory (Linux only)
Tablespace name

Absolute path of
tablespace file
Name of Oracle user that
accesses the Content
Server database
Password of Oracle user
that accesses the Content
Server database

Table 10-3: PostgreSQL Worksheet

Setting Value Required for Configured in

Installation Content Server
PostgreSQL server name

PostgreSQL administrator
account
Password of PostgreSQL
administrator account
Name of PostgreSQL user
that accesses the Content
Server database
Password of PostgreSQL
user that accesses the
Content Server database

170 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 10.1. Database Installation Worksheets

Setting Value Required for Configured in

Installation Content Server
Name of PostgreSQL
Content Server database
Name of PostgreSQL
Content Server tablespace

Table 10-4: Microsoft SQL Server Worksheet (Windows only)

Setting Value Required for Configured in

Installation Content Server
SQL Server Name

System administrator user sa

name
System administrator
password
master database master

master database collation

Name of SQL Server

database containing the
Content Server database
tables
Data file name

Path of data file

Log file name

Path of log file

Name of SQL Server user

that accesses the Content
Server database
Password of the SQL
Server that accesses the
Content Server database

LLESCOR240100-IGD-EN-01 Installation Guide 171

Chapter 10 Appendix A – Extended ECM Installation Worksheets

10.2 Web Server Worksheets

In the following tables:

• Items that have a check mark ( ) in the Required for Installation Column must
be set before you can start the installation of Content Server.
• If a default value exists for an item, it is listed in the Value column.

HTTP Server Worksheets

Table 10-5: Microsoft Internet Information Services Worksheet (Windows only)

Setting Value Required for

Installation
TCP port number 80

IIS Request Filter settings:

Allowed Verbs

IIS Request Filter settings: 4096

Maximum URL length

IIS Request Filter settings: 250000000

Maximum Allowed Content
Length (bytes)

Application Server Worksheets

Table 10-6: Apache Tomcat Worksheet

Setting Value Required for

Installation
TCP port number 8080

Operating system user created to

run the web server
Password for operating system
user created to run the web
server

172 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 10.3. Content Server Installation Worksheet

10.3 Content Server Installation Worksheet

Table 10-7: Content Server Installation Worksheet

Setting Default Value Required for Configured

Installation during
installation of
Content Server
Operating system user
created to run Content
Server
Password of the operating
system user created to run
Content Server
Content Server Windows OTCS
service name (Windows
installations only)
Mapping name (virtual Windows
directory alias) of OTCS1
<Content_Server_
Home>/cgi/ directory Linux
(Linux only) livelink

Mapping name (virtual Windows

directory alias) of appimg
<Content_Server_
Home>/appdata/ Linux
supportasset/ folder No default value

Mapping name (virtual Windows

directory alias) of img
<Content_Server_
Home>/support/ folder Linux
<CGI
alias>support

Content Server port 2099

number
Admin server port 5858
number
Administrator password2 livelink

Password of the Admin livelink

user3
Password of the System livelink
Support user4

1. On Windows, the Content Server service name and the Content Server
mapping name are the same.

LLESCOR240100-IGD-EN-01 Installation Guide 173

Chapter 10 Appendix A – Extended ECM Installation Worksheets

2. The Administrator password is set on the Configure Server Parameters

page during initial configuration of Content Server. Do not confuse the
Administrator password and the password of the Admin user! The
Administrator password is sometimes required to access the Content
Server Administration page or to perform certain sensitive activities, like
changing the Content Server database. It is not a user password.
3. The Admin user’s default password should be changed after the initial
installation. For information about changing the Administrator password,
see OpenText Content Server Admin Help - System Administration (LLESWBA-
H-AGD).
4. The password of the System Support user should be changed after the
intial installation. For information about changing the System Support
user, see OpenText Content Server Admin Help - Users, Groups, and Domains
Administration (LLESWBU-H-AGD).

174 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

Chapter 11
Appendix B – Installing Content Server as a
Syndication Environment

This chapter details the requirements for enabling Syndication as part of your
Content Server installation.

11.1 Install and configure the primary Syndication

Choose the site for your primary installation of Content Server, and then begin the
installation by following these steps:

Tip: If you have already installed and licensed Content Server, you can choose
to enable that installation as a primary installation of Syndication by accessing
the Configure Server Parameters page, see i on page 176. Once you enable
Syndication, you will need to apply a Syndication license in OTDS. For more
information, see the OTDS (https://knowledge.opentext.com/knowledge/cs.dll/
open/OTDS) documentation.

1. Install the pre-requisite OpenText™ Directory Services product, and ensure the
following:
a. You must install OTDS as an external installation.
Do not install this instance of OTDS as a replication server. The instance you
install on the primary must be a stand-alone version.
b. Create an OTDS resource for Content Server. In the OTDS documentation
referenced below, see “Configuring a synchronized resource for Content
Server”.
c. Create a synchronized user partition using Content Web Services. In the
OTDS documentation referenced below, see “Creating a synchronized user
partition”.
For more information, see the documentation at OpenText Directory Services
(https://knowledge.opentext.com/knowledge/cs.dll/open/OTDS). You will need
to follow these instructions in order to configure your Content Server installation
with OTDS.
2. Begin the Content Server installation process as documented in the Content
Server Installation Guide (https://knowledge.opentext.com/knowledge/
llisapi.dll?func=ll&objId=18091763&objAction=browse&viewType=1). Ensure
that you include these next steps during this installation:
a. Syndication does not support the use of a HANA database on the primary
installation of Content Server. Make sure you are using a supported database
for the primary installation, and that the database you choose is not HANA.

LLESCOR240100-IGD-EN-01 Installation Guide 175

Chapter 11 Appendix B – Installing Content Server as a Syndication Environment

b. During the installation you will see the Configure Server Parameters page.
In the System Configuration area, in the Syndication area, do the following:
i. Select the Enable box.
ii. The Remote Site ID field must not be edited. As you are setting up your
primary installation, this field is set by default to zero, 0.
iii. Return to the Content Server Installation Guide to complete the Content
Server instructions necessary to create your database and complete your
installation.
c. When, later in the installation of Content Server, you reach the Configure
OTDS Integration Settings page, you must select and configure an external
installation of Directory Services.
d. On the License Setup page, apply your Syndication license.
e. Once the primary installation of Content Server has been completed, sign in
to the admin page, and then proceed to “The primary installation of
Syndication” on page 176. Specifically, you will need to follow the
instructions in “To set primary Syndication parameters” on page 181.

11.1.1 The primary installation of Syndication

This section details the configuration required after you install your primary
installation of Syndication. The following pages describe the configuration tasks you
need to perform when setting up your primary Syndication installation.

Setting up the primary Syndication

You need to configure the primary system according to the information below:

Upload Directory
OpenText recommends that you enter an upload directory in your primary
installation of Content Server Syndication, and that you then create an identical
upload directory in each remote installation of Content Server Syndication.

Content Server Notifications

After you install any instance of Content Server Syndication, it is a good idea to
check to verify that Content Server Notification is enabled.

Content Server Syndication Process

When a Content Server installation is enabled as part of a Content Server
Syndication environment, a new Content Server Syndication process is created
in the System Object Volume's Process Folder, called “Syndication”. All
Content Server Syndication installations, the primary and each remote, will have
this process.
Important
OpenText recommends that you do not edit this process.

176 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 11.1. Install and configure the primary Syndication

To configure a primary upload directory

To configure an upload directory:

1. Beginning on the primary installation of Content Server Syndication, and later

on every site at which you have installed an instance of Content Server
Syndication, on the Content Server administration page, in the Core System -
Server Configuration section, click Server Parameters.

2. On the Configure Server Parameters page, in the System Configuration area,

in the Upload Directory field, type the temporary directory from which Content
Server will add uploaded files. For example, type:
C:\temp\

Note: OpenText recommends that you create an identical upload directory

in each Content Server Syndication instance.

3. Click Save Changes.

To configure primary notification for Syndication

To configure notification for Content Server Syndication:

• On an installation of Content Server Syndication, on the Content Server

administration page:

a. Under the Notification Administration section, click Configure

Notification.
In the Enable Notifications section, ensure the Enable button is selected,
and then click Submit.
See OpenText Content Server Admin Help - Notifications Administration
(LLESWBN-H-AGD) for information about the other fields on this page that
you may need to configure.
b. Under the Notification Center Administration section, click Configure
Notification Center.
In the Providers section, select Syndication, and then click Save Changes.
For more information, see OpenText Content Server Admin Help - Notification
Center Administration (LLESMCT-H-AGD).

LLESCOR240100-IGD-EN-01 Installation Guide 177

Chapter 11 Appendix B – Installing Content Server as a Syndication Environment

To access the primary Syndication process

To access the primary Syndication process:

1. On an installation of Content Server Syndication, on the Content Server

administration page, under the Search Administration section, click Open the
System Object Volume.

Important
OpenText recommends that you do not edit the Content Server
Syndication process.
2. On the Content Server System page, click Process Folder.
3. On the Process Folder page, from the Syndication functions menu, choose any
of the following:

a. If you want to start or stop or restart the Content Server Syndication

process, click Start or Stop or Restart.
b. If you want to resynchronize the Content Server Syndication process, click
Properties --> Specific. In the Actions area, click Resynchronize.

Configure primary Syndication parameters

The Configure Syndication Site Parameters page lets you specify the configuration
requirements for this Content Server installation of your Content Server Syndication
environment. This page needs to be completed on your primary installation and on
each of your remote installations.

Whether the fields on this page are available for input depends on if you are setting
up a primary or a remote installation of Content Server Syndication.

Local Syndication Process

In the Local Syndication Process area, you need to enter the information that
defines your installation of Content Server, either primary or remote. This
includes the following fields:
Local Base URL and Port
This field is mandatory and relevant if you are configuring either a primary
or a remote installation of Content Server.
Enter the base URL and port to access this installation of Content Server.
The Local Base URL and Port can be entered in the form: https://
<fully_qualified_domain_name>:<port_number>

Important
The <fully_qualified_domain_name> must be the name of the default
Admin server. A Content Server service must run on that machine.
You must select a port number that is not in use. If you select a port
number that is in use by another service, clicking Test on this page will
result in a failure.

178 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 11.1. Install and configure the primary Syndication

Two examples of the form you should use for the Local Base URL and Port
are:

• https://mymachine.opentext.net:18080
• https://10.16.12.120:18081

Local Content Server Admin Username

This field is mandatory and relevant if you are configuring either a primary
or a remote installation of Content Server.
Enter the username for a user with administrative privileges and access to
this installation of Content Server. The Content Server Admin user has the
access that is required.

Local Content Server Admin Password

This field is mandatory and relevant if you are configuring either a primary
or a remote installation of Content Server.
Enter the password for the user that you entered in the Local Content
Server Admin Username field above.
Important
1. If the password you entered in this field is ever changed, you must
re-submit that new password on this Configure Syndication Site
Parameters page, click Test Connection and then, if successful,
click Save Changes.
2. OpenText recommends that the password you choose for this field
be the same password that you entered as the OTDS administrator
password. If the password in this field is different from the OTDS
administrator password, the import users and groups step might
fail during the installation of Syndication.
For more information, see “Why can I not import users and
groups?” in OpenText Content Server Admin Help - Syndication
Administration (LLESQDS-H-AGD).

Primary Authorization
The Primary Syndication Service Information area is only relevant if you are
configuring a remote installation of Content Server. If you are configuring a
remote installation of Content Server, the fields in this area are mandatory.

Primary Base URL and Port

Enter the base URL and Port to access the primary installation of Content
Server. The Primary Base URL and Port can be entered in the form: https://
<fully_qualified_domain_name>:<port_number>
Two examples of the form you should use for the Primary Syndication
Service Base URL are:

• https://mymachine.opentext.net:18080
• https://10.16.12.120:18080

LLESCOR240100-IGD-EN-01 Installation Guide 179

Chapter 11 Appendix B – Installing Content Server as a Syndication Environment

Activation Pass Key

Enter a unique pass key that will, when entered to a remote site, permit
access to the primary installation of Content Server.
This pass key is found on your primary installation of Content Server
Syndication when you add a Syndication site to the Manage Syndication
Sites page. For more information, see C on page 183 in “Install and
configure a remote Syndication” on page 182.
Primary Content Server Admin Username
Enter the username for a user with administrative privileges and access to
the primary installation of Content Server. The Content Server “Admin”
user has the access that is required.
Primary Content Server Admin Password
Enter the password for the user that you entered in the previous field.

HTTPS Configuration
When you set up a Content Server Syndication environment, a new internal
process is installed to Content Server. The Syndication process is installed to the
System Object Volume. The internal Content Server Syndication environment
uses a Jetty web and servlet server that is built into Content Server. By default,
the internal Content Server Syndication server uses a self-signed certificate for
HTTPS communications, but you can configure it to use a different certificate by
entering appropriate values in the Java Key Store settings in the HTTPS
Configuration area.
For information about the default internal process, see OpenText Content Server -
Syndication Administration Guide (LLESQDS-AGD). For information on
configuring Jetty to use a specific certificate, refer to the Jetty documentation.
Documentation for Jetty, which is a third-party software component, is publicly
available.

Tip: For an example of the steps you should follow, see “How do I set up
Syndication to use HTTPS?” in OpenText Content Server Admin Help -
Syndication Administration (LLESQDS-H-AGD).

Java Key Store Location

This field is optional and relevant if you are configuring either a primary or
a remote installation of Content Server.
To configure the internal Content Server Syndication environment to use a
security certificate of your choice instead of the default self-signed
certificate, you need to provide the Java key store location.
Java Key Store Password
This field is optional and relevant if you are configuring either a primary or
a remote installation of Content Server.
To configure the internal Content Server Syndication environment to use a
security certificate of your choice instead of the default self-signed
certificate, you need to provide the Java key store password.

180 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 11.1. Install and configure the primary Syndication

To set primary Syndication parameters

To set primary Syndication parameters:

1. On the primary installation of Syndication, on the Content Server

Administration page, under the Syndication Administration heading, click the
Configure Syndication Site Parameters link. On the Configure Syndication
Site Parameters page, do the following:

2. In the Local Syndication Process area, do the following:

a. In the Local Base URL and Port field, type the complete URL to this
primary installation of Content Server in your Syndication environment.
For example, type: http://mymachine.opentext.net:18080
If you use https, the HTTPS Configuration area below will be mandatory.

Note: OpenText recommends that you use the fully qualified host
name when providing the syndication service base URL, and that you
do not use localhost.
b. In the Local Content Server Admin Username field, type the userid of a
user with administrative access and privileges to this primary installation
of Content Server.
c. In the Local Content Server Admin Password field, type the password for
the userid you typed in the field above.
d. Optional In the Test Connection Parameters field, you can click Test. This
will display information, under each field, to inform you if you have
correctly entered:

• The local base URL and port.

• the Content Server username.
• The Content Server password.

If you see errors, correct those errors and then click Test.

3. The Primary Authorization area is only applicable if you are configuring this
installation of Content Server as a remote Syndication. As this procedure
documents setting up a primary installation, this area is not active.

4. In the HTTPS Configuration area, if you will be configuring the internal

Syndication process on this installation to use a security certificate of your
choice instead of the default self-signed certificate, you will need to complete
the following fields.
If you typed https in the Local Base URL and Port box above, the following two
fields are mandatory:

a. In the Java Key Store Location field, type the Java key store location.
b. In the Java Key Store Password field, type the Java key store password.

LLESCOR240100-IGD-EN-01 Installation Guide 181

Chapter 11 Appendix B – Installing Content Server as a Syndication Environment

5. Click Save Changes to save the values you entered and return to the
administration page. Click Reset if you want to reset all fields to the previously
saved values.

11.2 Install and configure a remote Syndication

At any of the sites that will host one of your remote installations of Content Server,
begin the installation by following these steps:

1. Install the pre-requisite OpenText™ Directory Services product, and ensure the
following:
a. You must install Directory Services as an external installation on each remote
system. See the OTDS documentation referenced below.
b. The Content Server-required stand-alone OTDS installation must be
configured for replication. During the installation of OTDS, you must
designate it as a replication server of the OTDS product that you installed on
the primary. For more information, see “Replication” in the OTDS
documentation referenced below.
c. Create an OTDS resource for Content Server.
d. Create a non-synchronized user partition.

i. Because you have installed a replication server of OTDS on your

remote site, and once OTDS replicates users and groups across all
replicated sites in your environment, the non-synchronized user
partition created above will be populated.
ii. For more information, see the documentation at OpenText
Directory Services (https://knowledge.opentext.com/knowledge/
cs.dll/open/OTDS).
2. Begin the Content Server installation process as documented in the Content
Server Installation Guide (https://knowledge.opentext.com/knowledge/
llisapi.dll?func=ll&objId=18091763&objAction=browse&viewType=1) Ensure
that you include these next steps during this installation:
a. During the installation of Content Server, you are directed to the Configure
Server Parameters page. Do not proceed immediately on this page. Open a
new browser window to sign in to the primary installation of Content Server,
and then do the following:
i. On your primary installation of Content Server, on the administration
page, under the Syndication Administration heading, click Manage
Syndication Sites.
ii. On the Manage Syndication Sites page, under the Actions column, click
the Add Syndication Site button.
iii. On the Add Syndication Site page, do the following:
A. The Site ID field cannot be edited. It is controlled by the primary
installation of Content Server and it is a unique number in your
global Content Server environment.

182 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 11.2. Install and configure a remote Syndication

You will copy this number exactly to enter it into your remote
installation in the B on page 183 step below.
B. In the Site Name field, type a unique name that will identify this
installation in your global environment.
You will copy this name exactly to enter it into your remote
installation in the i on page 183 step below. This field is case
sensitive.
C. In the Pass Key field, type a unique string of letters, numbers, and/or
symbols that will be required by your new remote installation in
order to access this primary. This field is case sensitive.

Important
Make an exact note of the string that you enter in this field as
you will need it for the Activation Pass Key field in the “To set
remote Syndication parameters” on page 189.
Once the remote installation is authenticated using the pass
key, the pass key string is deleted from the primary server.
D. Click Save Changes.
iv. If you have copied the information, you can sign out of your primary
installation of Content Server.
b. Return to your new remote installation, on the Configure Server Parameters
page of the Content Server installation process, in the System Configuration
area do the following:
i. In the Site Name field, type the unique name that you chose to identify
this remote installation in your Syndication environment in the B
on page 183 step.
This field is case sensitive. You must enter the name exactly as you
entered it on the primary.
ii. In the Syndication field, do the following:
A. Select the Enable box.
B. In the Remote Site ID field, type the number that was generated on
your primary in the A on page 182 step.
C. When you reach the Configure OTDS Integration Settings page,
you must select an external installation of Directory Services. You
must also choose to install and configure Directory Services as a
replication server of the Directory Services server that you installed
on the primary. For information about Directory Services replication,
see “Replication” in the OpenText Directory Services - Installation and
Administration Guide (OTDS-IWC) in OpenText My Support (https://
knowledge.opentext.com/knowledge/cs.dll/open/OTDS).
D. On the remote installation, return to the OpenText Extended ECM -
Installation Guide (LLESCOR-IGD) to complete the Content Server

LLESCOR240100-IGD-EN-01 Installation Guide 183

Chapter 11 Appendix B – Installing Content Server as a Syndication Environment

instructions necessary to create your database and complete your

installation.
E. During the installation of Content Server, you do not need to apply a
license to this remote site. The next step in this process will apply the
Syndication license from the primary to this remote site.
c. Once the installation of Content Server has completed you need to restart the
Content Server servers on this remote installation. This is required in order
for the remote site to pick up the Syndication license that was applied at the
primary site. For information about restarting the servers, see OpenText
Content Server Admin Help - System Administration (LLESWBA-H-AGD).
d. Proceed to “A remote installation of Syndication” on page 184 to complete
the setup of this remote installation.

11.2.1 A remote installation of Syndication

This section details the configuration required after you install a remote installation
of Syndication. The following pages describe the configuration tasks you need to
perform when setting up your remote Syndication installations.

Setting up a remote Syndication

You need to configure each remote system according to the information below:

Upload Directory
OpenText recommends that you enter an upload directory in your primary
installation of Content Server Syndication, and that you then create an identical
upload directory in each remote installation of Content Server Syndication.
Content Server Notifications
After you install any instance of Content Server Syndication, it is a good idea to
check to verify that Content Server Notification is enabled.
Content Server Syndication Process
When a Content Server installation is enabled as part of a Content Server
Syndication environment, a new Content Server Syndication process is created
in the System Object Volume's Process Folder, called “Syndication”. All
Content Server Syndication installations, the primary and each remote, will have
this process.
Important
OpenText recommends that you do not edit this process.

184 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 11.2. Install and configure a remote Syndication

To configure a remote upload directory

To configure an upload directory:

1. Beginning on the primary installation of Content Server Syndication, and later

on every site at which you have installed an instance of Content Server
Syndication, on the Content Server administration page, in the Core System -
Server Configuration section, click Server Parameters.

2. On the Configure Server Parameters page, in the System Configuration area,

in the Upload Directory field, type the temporary directory from which Content
Server will add uploaded files. For example, type:
C:\temp\

Note: OpenText recommends that you create an identical upload directory

in each Content Server Syndication instance.

3. Click Save Changes.

To configure remote notification for Syndication

To configure notification for Content Server Syndication:

• On an installation of Content Server Syndication, on the Content Server

administration page:

a. Under the Notification Administration section, click Configure

Notification.
In the Enable Notifications section, ensure the Enable button is selected,
and then click Submit.
See OpenText Content Server Admin Help - Notifications Administration
(LLESWBN-H-AGD) for information about the other fields on this page that
you may need to configure.
b. Under the Notification Center Administration section, click Configure
Notification Center.
In the Providers section, select Syndication, and then click Save Changes.
For more information, see OpenText Content Server Admin Help - Notification
Center Administration (LLESMCT-H-AGD).

LLESCOR240100-IGD-EN-01 Installation Guide 185

Chapter 11 Appendix B – Installing Content Server as a Syndication Environment

To access the remote Syndication process

To access the remote Syndication process:

1. On an installation of Content Server Syndication, on the Content Server

administration page, under the Search Administration section, click Open the
System Object Volume.

Important
OpenText recommends that you do not edit the Content Server
Syndication process.
2. On the Content Server System page, click Process Folder.
3. On the Process Folder page, from the Syndication functions menu, choose any
of the following:

a. If you want to start or stop or restart the Content Server Syndication

process, click Start or Stop or Restart.
b. If you want to resynchronize the Content Server Syndication process, click
Properties --> Specific. In the Actions area, click Resynchronize.

Configure remote Syndication parameters

The Configure Syndication Site Parameters page lets you specify the configuration
requirements for this Content Server installation of your Content Server Syndication
environment. This page needs to be completed on your primary installation and on
each of your remote installations.

Whether the fields on this page are available for input depends on if you are setting
up a primary or a remote installation of Content Server Syndication.

Local Syndication Process

In the Local Syndication Process area, you need to enter the information that
defines your installation of Content Server, either primary or remote. This
includes the following fields:
Local Base URL and Port
This field is mandatory and relevant if you are configuring either a primary
or a remote installation of Content Server.
Enter the base URL and port to access this installation of Content Server.
The Local Base URL and Port can be entered in the form: https://
<fully_qualified_domain_name>:<port_number>

Important
The <fully_qualified_domain_name> must be the name of the default
Admin server. A Content Server service must run on that machine.
You must select a port number that is not in use. If you select a port
number that is in use by another service, clicking Test on this page will
result in a failure.

186 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 11.2. Install and configure a remote Syndication

Two examples of the form you should use for the Local Base URL and Port
are:

• https://mymachine.opentext.net:18080
• https://10.16.12.120:18081

Local Content Server Admin Username

This field is mandatory and relevant if you are configuring either a primary
or a remote installation of Content Server.
Enter the username for a user with administrative privileges and access to
this installation of Content Server. The Content Server Admin user has the
access that is required.

Local Content Server Admin Password

This field is mandatory and relevant if you are configuring either a primary
or a remote installation of Content Server.
Enter the password for the user that you entered in the Local Content
Server Admin Username field above.
Important
1. If the password you entered in this field is ever changed, you must
re-submit that new password on this Configure Syndication Site
Parameters page, click Test Connection and then, if successful,
click Save Changes.
2. OpenText recommends that the password you choose for this field
be the same password that you entered as the OTDS administrator
password. If the password in this field is different from the OTDS
administrator password, the import users and groups step might
fail during the installation of Syndication.
For more information, see “Why can I not import users and
groups?” in OpenText Content Server Admin Help - Syndication
Administration (LLESQDS-H-AGD).

Primary Authorization
The Primary Syndication Service Information area is only relevant if you are
configuring a remote installation of Content Server. If you are configuring a
remote installation of Content Server, the fields in this area are mandatory.

Primary Base URL and Port

Enter the base URL and Port to access the primary installation of Content
Server. The Primary Base URL and Port can be entered in the form: https://
<fully_qualified_domain_name>:<port_number>
Two examples of the form you should use for the Primary Syndication
Service Base URL are:

• https://mymachine.opentext.net:18080
• https://10.16.12.120:18080

LLESCOR240100-IGD-EN-01 Installation Guide 187

Chapter 11 Appendix B – Installing Content Server as a Syndication Environment

Activation Pass Key

Enter a unique pass key that will, when entered to a remote site, permit
access to the primary installation of Content Server.
This pass key is found on your primary installation of Content Server
Syndication when you add a Syndication site to the Manage Syndication
Sites page. For more information, see C on page 183 in “Install and
configure a remote Syndication” on page 182.
Primary Content Server Admin Username
Enter the username for a user with administrative privileges and access to
the primary installation of Content Server. The Content Server “Admin”
user has the access that is required.
Primary Content Server Admin Password
Enter the password for the user that you entered in the previous field.

HTTPS Configuration
When you set up a Content Server Syndication environment, a new internal
process is installed to Content Server. The Syndication process is installed to the
System Object Volume. The internal Content Server Syndication environment
uses a Jetty web and servlet server that is built into Content Server. By default,
the internal Content Server Syndication server uses a self-signed certificate for
HTTPS communications, but you can configure it to use a different certificate by
entering appropriate values in the Java Key Store settings in the HTTPS
Configuration area.
For information about the default internal process, see OpenText Content Server -
Syndication Administration Guide (LLESQDS-AGD). For information on
configuring Jetty to use a specific certificate, refer to the Jetty documentation.
Documentation for Jetty, which is a third-party software component, is publicly
available.

Tip: For an example of the steps you should follow, see “How do I set up
Syndication to use HTTPS?” in OpenText Content Server Admin Help -
Syndication Administration (LLESQDS-H-AGD).

Java Key Store Location

This field is optional and relevant if you are configuring either a primary or
a remote installation of Content Server.
To configure the internal Content Server Syndication environment to use a
security certificate of your choice instead of the default self-signed
certificate, you need to provide the Java key store location.
Java Key Store Password
This field is optional and relevant if you are configuring either a primary or
a remote installation of Content Server.
To configure the internal Content Server Syndication environment to use a
security certificate of your choice instead of the default self-signed
certificate, you need to provide the Java key store password.

188 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 11.2. Install and configure a remote Syndication

To set remote Syndication parameters

To set remote Syndication parameters:

1. On a remote installation of Syndication, on the Content Server Administration

page, under the Syndication Administration heading, click the Configure
Syndication Site Parameters link. On the Configure Syndication Site
Parameters page, do the following:

2. In the Local Syndication Process area, do the following:

a. In the Local Base URL and Port field, type the complete URL to this remote
system. For example, type: https://mymachine-rmt01.opentext.net:
18080

Note: OpenText recommends that you use the fully qualified host
name when providing the synchronization service base URL, and that
you do not use localhost.
b. In the Local Content Server Admin Username field, type the userid of a
user with administrative access and privileges to this remote installation of
Content Server.
c. In the Local Content Server Admin Password field, type the password for
the userid you typed in the field above.
d. Optional In the Test Connection Parameters field, you can click Test. This
will display information, under each field, to inform you if you have
correctly entered:

• The local base URL and port.

• the Content Server username.
• The Content Server password.

If you see errors, correct those errors and then click Test.

3. In the Primary Authorization area, because you are configuring this installation
of Content Server as a remote system, do the following:

a. In the Primary Base URL and Port field, type the base URL that will access
the primary installation of Content Server. For example, type: https://
mymachine-prm00.opentext.net:18080
b. In the Activation Pass key field, type the unique pass key that allows
access by this remote installation to the primary installation of Content
Server.
You can find this information in C on page 183.
c. In the Primary Content Server Admin Username field, type the username
of a user with administrative access and privileges on the primary
installation of Content Server.
d. In the Primary Content Server Admin Password field, type the password
for the user you entered above.

LLESCOR240100-IGD-EN-01 Installation Guide 189

Chapter 11 Appendix B – Installing Content Server as a Syndication Environment

e. Optional In the Test Connection Parameters field, you can click Test. This
will display information, under each field, to inform you if you have
correctly entered:

• The local base URL and port.

• the Content Server username.
• The Content Server password.

If you see errors, correct those errors and then click Test.
4. In the HTTPS Configuration area, if you will be configuring the internal
Syndication process on this installation to use a security certificate of your
choice instead of the default self-signed certificate, do the following:

a. In the Java Key Store Location field, type the Java key store location.
b. In the Java Key Store Password field, type the Java key store password.
5. Click Save Changes to save the values you entered and return to the
administration page. Click Reset if you want to reset all fields to the previously
saved values.
6. Because all users and groups are created on the primary installation of Content
Server, you must now import user and group data from the primary to this
remote installation. See “Importing users and groups on a remote system”
on page 190.

Important
If you intend installing any optional Content Server modules, and if any of
these optional modules extend the user schema, you must install and
configure those modules before you import user and group data.

Importing and consolidating users and groups on a remote

system
All users and groups are created on the primary installation of Content Server. As a
result, each remote installation in your environment must import users and groups
from the primary to that remote. The option to consolidate is provided for
troubleshooting purposes.

Importing users and groups on a remote system

On a remote installation of Syndication, once you have completed your initial setup
and configuration of this remote installation, you must import users and groups
from the primary installation of Content Server. You only need to perform this
action once, at the outset. After this initial import, Syndication will maintain all users
and groups on this remote system concurrently with your environment's primary
installation.

Consolidating users and groups on a remote system

The option to consolidate any one user or group is provided for troubleshooting
purposes. You should not access this option regularly. In the event that a user or

190 OpenText™ Extended ECM LLESCOR240100-IGD-EN-01

 11.2. Install and configure a remote Syndication

group experiences difficulties signing in to Content Server, you can, as part of your
troubleshooting options, consolidate that specific user or group. Consolidating will
update that specific user's or specific group's data on this remote installation.

Importing users and groups on a remote system

1. On a remote installation of Syndication, on the Content Server Administration

page, under the Syndication Administration heading, click the Import Users
and Groups link.

Note: This action will import all user and group data from your
environment's primary installation of Content Server to this remote
installation. Depending on the number of users and groups on your
primary installation, an import could take some time. This action should
only be performed once, during the initial setup of this remote installation.

2. On the Users and Groups Data Import page, if you want to import user and
group data from the primary installation of Content Server, select the box, and
then click Next.

Consolidating users and groups on a remote system

1. On a remote installation of Syndication, on the Content Server Administration

page, under the Syndication Administration heading, click the Consolidate
Users and Groups link.

Note: Only consolidate a user or group if that user or group is

experiencing a problem.

2. On the Consolidate a User or Group page, in the User or Group ID field, type
the ID of the user or group you want to consolidate, and then click Next.

LLESCOR240100-IGD-EN-01 Installation Guide 191