OpenText Content Server 16.0.0 - Installation Guide English (LLESCOR160000-IGD-EN-02)

OpenText™ Content Server
Installation Guide
Welcome to Content Server! This guide walks you through the

installation and initial configuration of Content Server. 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
Content Server administrator, and a valuable reference guide if
you are an experienced one.
LLESCOR160000-IGD-EN-02
OpenText™ Content Server
Installation Guide
Rev.: 2016-Apr-04
This documentation has been created for software version 16.0.0.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text SA
40 Avenue Monterey , Luxembourg, Luxembourg L-2163
Tel: 35 2 264566 1
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: http://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2016 Open Text SA or Open Text ULC (in Canada). All Rights Reserved.
Trademarks owned by Open Text SA or Open Text ULC (in Canada).
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 Content Server .......................................................... 5
1.1 Overview of Content Server Installation .............................................. 5
1.2 Upgrading Content Server and Installing Updates ............................... 6
2 Designing Your Content Server System ................................. 7

2.1 About Content Server ........................................................................ 7
2.2 Understanding Content Server Architecture ...................................... 12
2.3 Architectural Options ....................................................................... 13
2.4 Best Practices for System Design .................................................... 18
3 Preparing to Install Content Server ....................................... 23

3.1 Configuring the Access Tier ............................................................. 23
3.2 Installing a Database Server ............................................................ 24
3.3 Creating an Operating System User ................................................. 30
3.4 Setting Up Client Web Browsers ...................................................... 32
4 Configuring the Web Server to Run Content Server ............ 35

4.1 General Web Server and Application Server Configuration ................ 35
4.2 Configuring a Web Server to Run Content Server .............................. 36
4.3 Configuring an Application Server to Run Content Server .................. 48
5 Installing Content Server on the Operating System ............ 61

5.1 Installing Content Server on Microsoft Windows ................................ 61
5.2 Installing Content Server on Linux .................................................... 74
6 Configuring Content Server ................................................... 81

6.1 Accessing the Content Server Administration Page ........................... 81
6.2 Configuring Server Parameters ........................................................ 82
6.3 Creating the Content Server Database ............................................. 87
6.4 Installing Optional Content Server Modules ....................................... 98
6.5 Selecting the OTDS Server Type ................................................... 102
6.6 Creating the Enterprise Data Source .............................................. 104
6.7 Licensing Content Server ............................................................... 106
6.8 The Congratulations! Page ............................................................ 110
7 Completing the Installation and Setup of Content Server . 111

7.1 Using Cluster Management to Update Content Server ..................... 111
7.2 Installing Optional Modules ............................................................ 112
7.3 Installing Content Server Language Packs ...................................... 112
7.4 Creating the Help Indexes ............................................................. 113
7.5 Performing Additional Tasks Before Users Connect ......................... 115
8 Installing Additional Instances of Content Server ............. 123
OpenText Content Server – Installation Guide iii

Table of Contents
8.1 Installing an Additional Front-End Server ........................................ 123

8.2 Installing a Secondary Admin Server .............................................. 124
9 Uninstalling Content Server ................................................. 131

9.1 Uninstalling Content Server on Windows ........................................ 131
9.2 Uninstalling Content Server on UNIX/Linux ..................................... 132
10 Appendix A – Content Server Installation Worksheets ..... 133

10.1 Database Installation Worksheets .................................................. 133
10.2 Web Server Worksheets ................................................................ 135
10.3 Content Server Installation Worksheet ............................................ 137
11 Appendix B – Understanding Cascading Stylesheets ....... 139

11.1 Locating the Stylesheets ................................................................ 139
11.2 Modifying Common Elements ........................................................ 139
iv OpenText Content Server – Installation Guide

Chapter 1
Installing Content Server
OpenText™ Content Server 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.
Thanks to its standards-based, open architecture, Content Server can integrate

seamlessly with multiple platforms, information repositories, third-party
applications, and legacy systems. It is scalable, extensible, accessible, and secure.
Content Server users require only a web browser to start using it.
This chapter covers the following topics:
• “Overview of Content Server Installation” on page 5

• “Upgrading Content Server and Installing Updates” on page 6
1.1 Overview of Content Server Installation

This guide walks you through the installation and configuration of Content Server.
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.
If you are new to Content Server, you will likely move through this guide from start
to finish, but 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.
Choosing the operating system, relational database management See “Designing Your
system and web server (or web application server) that you wish to Content Server
use in your Content Server environment, and planning the System“ on page 7.
architecture of your Content Server system.
Preparing the Content Server environment. Installing a web server See “Preparing to
or web application server. Installing a database. Creating operating Install Content Server“
system users. on page 23.
OpenText Content Server – Installation Guide 5

Chapter 1 Installing Content Server
Configuring your web server or web application server to work See “Configuring the
with Content Server Web Server to Run
Content Server“
on page 35.
Running the Content Server installation program, applying See “Installing Content
required patches and starting Content Server for the first time. Server on the
Operating System“
on page 61.
Performing the initial configuration of Content Server. Creating a See “Configuring
Content Server database. Installing optional modules. Connecting Content Server“
to an OpenText™ Directory Services server. Creating the search on page 81.
and indexing infrastructure. Licensing Content Server.
Installing optional modules (if you didn’t install them during the See “Completing the
Content Server installation) and language packs, creating the Help Installation and Setup
indexes, applying the latest Content Server patches and Updates, of Content Server“
and performing various tasks before allowing users to connect to on page 111.
Content Server.
• Information on adding additional instances of Content Server to your

deployment appears in “Installing Additional Instances of Content Server“
on page 123.
• Information on uninstalling Content Server appears in “Uninstalling Content
Server“ on page 131.
1.2 Upgrading Content Server and Installing Updates

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

Chapter 2
Designing Your Content Server 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.

• “About Content Server” on page 7
• “Understanding Content Server Architecture” on page 12
• “Architectural Options” on page 13
• “Best Practices for System Design” on page 18
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

Chapter 2 Designing Your 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
development. This architecture is not recommended for a production Content
Server system. For more architecture options, see “Understanding Content
Server Architecture” on page 12.
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 the Knowledge Center (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:
• SAP® HANA
• Oracle® Database
• Microsoft SQL Server® (on Windows)
• PostgreSQL
• 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)
• Apache™ HTTP Server
• Oracle® iPlanet Web Server (on Oracle Linux, and Red Hat Enterprise Linux)
• 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 servers:

2.1. About Content Server
• Apache™ Tomcat Server

• IBM® WebSphere®
• 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® Internet Explorer® (on Windows)
• 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
• Kazakh
• Portuguese
• Russian
• Spanish
• 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 must 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.

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, and Content Web Services (CWS) and the Content
Server REST API , which allow you to write programs that interact with data in
the repository. All web services are defined in Java, C# and web service APIs are
generated for the clients. The web service APIs can be deployed on Microsoft IIS
using ASP.NET (WCF) or on a Java application server.
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.
Document Conversion Service (DCS)

A Content Server Document Conversion Service (DCS) uses document filters to
convert items from their native file formats (for example, Microsoft Word, Microsoft
Excel, or Adobe PDF) to HTML for viewing in Content Server. Document
Conversion Services are controlled by Admin servers. View as Web Page and hit
highlighting of search results are processes that are both clients of a Document
Conversion Service. To enable View as Web Page and hit highlighting, you must
configure at least one DCS on an Admin server.
For information about configuring a DCS, see “Enabling a Document Conversion

Service (DCS)” on page 118.

Content Server Services and Modules

Content Server has three 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.
• The Content Server Cluster Agent service (otclusteragentservice[.exe])
deploys and manages Content Server patches on a Content Server master system
and replicates the master system configuration to all instances in a Content
Server cluster. It also facilitates the application of Content Server Updates.
Content Server Modules

Most of the functionality delivered by Content Server is contained in modules. Some
modules are installed and enabled by default. Known as core modules, these modules
deliver basic functionality, such as document management. Numerous optional
modules are also available from OpenText and various third parties. They deliver a
wide variety of additional functions.
In many cases, organizations develop their own 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.
The Knowledge Center (https://knowledge.opentext.com/) contains more

information about optional modules and other OpenText products.
2.2 Understanding 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.

2.3. Architectural Options
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
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.
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 “Installing a Database Server”
on page 24.
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.
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 a secondary Admin server. See OpenText Content
Server Admin Online 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 “Installing Additional Instances of Content Server“ on page 123
Note: You can run multiple Admin servers, but there can be only one instance
of Content Server running at a time unless you configure a server cluster to
serve as the Content Server computer. See “Content Server Cluster
Architecture ” on page 15.
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 Cache

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, the best way to improve
performance may be to use a proxy server to maintain a document cache at the
remote site. Content Server Remote Cache is a document-caching solution that
caches local copies of documents that are managed by Content Server.
Note: Content Server Remote Cache is an optional module that is sold

separately. For more information, contact your OpenText sales consultant.
OpenText Content Server Secure Extranet Architecture (SEA)

A common and useful approach to network security is to isolate each tier into a
dedicated security zone, separated by firewalls. For instance, the Access Tier can be
isolated in what is colloquially known as a DMZ (demilitarized zone). In most cases,
the Application Tier and the Data Tier are also isolated into dedicated zones.
To enable organizations to configure a Content Server client and the Content Server
service on different computers, possibly across a firewall, OpenText provides the
Content Server Secure Extranet Architecture (SEA). The chief component of the SEA
is the OpenText Content Server Servlet. The servlet, also known as LLServlet, is a
J2EE servlet component that enables the successful implementation of the secure
extranet architecture using the recognized security capabilities provided by the J2EE
standard. In this architecture, a Content Server proxy client sends document files to
the Content Server by tunneling through port 2099.
The Content Server Servlet can be deployed using any application server that
implements and conforms to the Java Servlet Specification. For a complete list of the
application servers that have been officially tested by OpenText, consult the Content
Server Release Notes.
2.3.2 Virtualization Platforms

You can install Content Server on supported versions of Windows and Linux, 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.

2.3.3 Internal and External Document Storage

Content Server can use 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.
Most implementations of Content Server use both types of storage and use Storage
Provider rules to store items in the most appropriate location. OpenText
recommends that you use external storage for documents and emails, and internal
storage for system objects, such as forms, category definitions, workflow maps and
so on.
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 the 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
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 “Creating a Windows User” on page 30.
• 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

2.4. Best Practices for System Design
• Security best practices
Tip: OpenText Professional Services can help you with specific system-design
issues.
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 the Knowledge Center (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 “Understanding Content Server Architecture” on page 12.
• 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.
For additional recommendations on optimizing Content Server performance, see

theWeb Server Configuration and High Performance (https://
knowledge.opentext.com/go/14469718) Guide, available in the Champion Toolkit
(https://knowledge.opentext.com/go/Champion_Toolkit) on the OpenText
Knowledge Center
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.

2.4. Best Practices for System Design
• For organizations that want to enable access to Content Server from an external
network (while adhering to most common organizational IT security policies),
OpenText has developed the Content Server Secure Extranet Architecture (SEA).
See “OpenText Content Server Secure Extranet Architecture (SEA)” on page 16.

Chapter 3
Preparing to Install Content Server
Before you can install Content Server, you must 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.

• “Configuring the Access Tier” on page 23
• “Installing a Database Server” on page 24
• “Creating an Operating System User” on page 30
• “Setting Up Client Web Browsers” on page 32
3.1 Configuring the Access Tier

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
3.1.1 Using an Application Server with Content Server

To deliver Java-based Content Server features, you must use an application server in
your Content Server system configuration, either alone or in addition to a web
server.
In addition to the commercial application servers listed in the Release Notes,

OpenText supports Apache Tomcat as a servlet container for use with Content
Server. Tomcat is an open-source servlet container developed by the Apache
Software Foundation (http://www.apache.org/). It is distributed free of charge under
the Apache Software License. Tomcat is the official reference implementation of the
Java servlet API, and is commonly implemented even for enterprise-scale
applications.

Chapter 3 Preparing to Install Content Server
Configuring an Application Server to Work with a Web Server

Tomcat and IBM WebSphere 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.
3.2 Installing a Database Server

Content Server uses third-party database software to create and manage the Content
Server database. You can use install supported versions of SAP HANA, Oracle
Database, PostgreSQL, or Microsoft SQL Server on any operating system that is
supported by the database vendor. It is not required that the database run on the
same operating system as Content Server.
For optimum performance and scalability, OpenText recommends that you install
the database software on its own computer. If you follow this recommendation, you
must install database client software on the Content Server computer so that Content
Server can communicate with the database computer.
In some cases, a database client is not supported on every operating system.

Microsoft SQL Server can be used only by Content Server running on Windows
operating systems, and a PostgreSQL connection is supported only on specific
versions of Linux. Refer to the Content Server Release Notes for detailed information
on supported database servers and database clients.
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.
Choose the installation guidelines that apply to your supported database platform.
• “SAP HANA Installation Guidelines” on page 25
• “Oracle Database Installation Guidelines” on page 25
• “Microsoft SQL Server Installation Guidelines” on page 29
• “PostgreSQL Installation Guidelines” on page 30

3.2. Installing a Database Server
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

The Oracle Database installation guidelines vary depending on whether you install
Oracle Database on Windows or Linux. Choose the guidelines that apply to your
installation.
Oracle Database Installation Guidelines for Windows

Note the following points when you install and configure Oracle Database on
Microsoft Windows:
Notes
• An incorrect character encoding setting can cause unexpected characters to

appear in documents stored in Content Server. To 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)
• To ensure that the sort order used 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.
• Use the AL32UTF8 character set for the NLS, CHAR, and CHARACTERSET settings to
set up the CHAR, VARCHAR, and CLOB data types for UTF-8 compatibility before
installing Oracle Database. The US7ASCII character set is the default for English-
speaking locales.
• 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):
• ENV_NLS_COMP=LINGUISTIC
• ENV_NLS_SORT=BINARY_CI, ENV_NLS_SORT=GENERIC_M_CI or any other
Oracle case-insensitive linguistic definition
• 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 you install Oracle Database on its own computer, you must install an Oracle
client on the Content Server computer so that it can communicate with Oracle
Database on the database computer. Ensure that the client
• exactly matches the version of your Oracle Database
Example: If you use Oracle Database 11.2.0.3, you must use Oracle client 11.2.0.3.
• is a 64–bit client
• communicates using UTF-8 encoding
• Selecting the Typical Configuration option results in an Oracle Database
configuration that is compatible with Content Server.
• To connect to Oracle Database, Content Server requires the following Oracle
services to run on the database computer:
• OracleStartORCL
• OracleServiceORCL
• OracleTNSListener
Set these services to start automatically whenever the database computer is

restarted.
• If the database server resides on its own computer and you have installed an
Oracle client on the Content Server computer, run the Oracle Net8 Easy Config

utility on the Content Server computer to establish the connection to the database
computer.
• Oracle recommends that you change the default passwords of the internal, sys,
and system users immediately following installation.
• Record the password for the user system on Table 10-2: “Oracle Database
Worksheet” on page 134. You will need this user name and password 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 in the Knowledge Center (https://
Oracle Database Installation Guidelines for Linux

Note the following points when you install and configure Oracle Database on Linux:
Notes
• An incorrect character encoding setting can cause unexpected characters to
appear in documents stored in Content Server. To 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)
• To ensure that the sort order used 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.
• To install Oracle Database on supported Linux operating systems, you must be
logged in as root.
• Use the AL32UTF8 character set for the NLS, CHAR, and CHARACTERSET settings to
set up the CHAR, VARCHAR, and CLOB data types for UTF-8 compatibility before
installing Oracle Database. The US7ASCII character set is the default for English-
speaking locales.
• 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):
• ENV_NLS_COMP=LINGUISTIC
• ENV_NLS_SORT=BINARY_CI, ENV_NLS_SORT=GENERIC_M_CI or any other
Oracle case-insensitive linguistic definition
• If you install Oracle Database on its own computer, you must install an Oracle
client on the Content Server computer so that it can communicate with Oracle
Database on the database computer. Ensure that the client
• exactly matches the version of your Oracle Database
Example: If you use Oracle Database 11.2.0.3, you must use Oracle client 11.2.0.3.
• is a 64–bit client
• communicates using UTF-8 encoding
• To connect with Oracle Database, Content Server requires that the Oracle TCP/IP
listener be running on the database computer.
• If the database server resides on its own computer and you have installed an
Oracle client on the Content Server computer, establish the connection to the
database computer.
• Record the Oracle HOME folder or the Oracle SID on Table 10-2: “Oracle
Database Worksheet” on page 134. You will need this information when you
install Content Server on the Content Server computer.
• Oracle recommends that you change the default passwords of the internal, sys,
and system users immediately following installation. The internal user has
privileges to start or stop the database service; the system and sys users have
database administrative privileges. The default password for internal and
system is manager. The default password for sys is change_on_install.

• Record the password for the user system on Table 10-2: “Oracle Database
Worksheet” on page 134. You will need this user name and password 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 in the Knowledge Center (https://
3.2.3 Microsoft SQL Server Installation Guidelines

Note the following points when you install and configure Microsoft SQL Server:
• Select the collation, case-sensitivity and accent sensitivity that is appropriate for
your organization. Content Server does not require a specific collation.
• Record the name of the Microsoft SQL Server master database (by default, it is
master) on Table 10-4: “Microsoft SQL Server Worksheet (Windows only)”
on page 135.
• 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 135.
• After you complete the installation, test the Microsoft SQL Server installation, as
described in the Microsoft SQL Server documentation.
• If Microsoft SQL Server resides on its own computer, OpenText recommends
that you install a Microsoft SQL Server client on the Content Server computer.
• OpenText recommends that you enable 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. 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

3.2.4 PostgreSQL Installation Guidelines

It is not necessary to install a PostgreSQL database client. The connection libraries
for PostgreSQL are included in the Content Server default installation.
3.3 Creating an Operating System User

Content Server (and, in the case of Oracle iPlanet Web Server, the web server) must
run as a particular Windows, or Linux 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.
Tip: For information on configuring Content Server securely, refer to the

Champion Toolkit document “Application Note Configuring for Least
Privilege: OpenText Content Server 10” on the OpenText Knowledge Center
(https://knowledge.opentext.com)
Excluding Content Server Folders from Antivirus Scanning

You must 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.3.1 Creating 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.
Note: The Content Server Cluster Agent service must run as Local System, not
as a specific Windows user.
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.

3.3. Creating an Operating System User
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-10: “Content Server Installation Worksheet” on page 137.
3.3.2 Creating a Linux User

Create Linux user accounts with appropriate profiles to run the web server and
Content Server. You can use the same Linux 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 Linux 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, you must log on to the Content Server computer as
the superuser root.
Tip: Use the same Linux 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.
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 76.
Record the name and password of the Linux user that you create for Content Server
on Table 10-10: “Content Server Installation Worksheet” on page 137. Record the
name and password of the user that you create for Oracle iPlanet Web Server on
Table 10-6: “Oracle iPlanet Web Server Worksheet” on page 136.

3.4 Setting 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 33 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
Content Server. To connect to Content Server, web browsers must be configured
to accept cookies.
• If you choose not to configure your Content Server system with an application
server and you want to use the features Workflow Painter, Text Editor, and Spell
Check, then Content Server requires a supported version of Java (JRE) in client
web browsers.
• To open documents, web browsers must be configured to behave in a certain
manner for specified MIME types. See “Configuring Web Browser Behavior for
Opening Documents” on page 33.
• 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 Online Help - Content Server Administration (LLESWBA-H-AGD)

3.4. Setting Up Client Web Browsers
3.4.1 Configuring 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.
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.

Modifying 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.

Chapter 4
Configuring the Web Server to Run Content Server
Before you can start Content Server, you must configure the Content Server Web or
Application server to work with Content 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.
• “Configuring a Web Server to Run Content Server” on page 36

• “Configuring an Application Server to Run Content Server” on page 48
4.1 General 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 Configuring HTTP Compression Settings for the Smart

UI
To improve performance of the Content Server Smart UI, OpenText recommends
that you enable compression on your web server or application server. Compressing
server responses improves the performance of the Content Server Smart UI,
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 UI landing page and
inspecting the responses. Take note of the responses for /app, *.js, *.css, *.svg,
and /api.

Chapter 4 Configuring the Web Server to Run Content Server
Requests sent by the browser should include in the header Accept-Encoding: gzip,
deflate, sdch (or other algorithms).
Responses received by the browser should include in the header Content-

Encoding: gzip (or other algorithm).
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 Configuring a Web Server to Run Content Server

To deploy Content Server on a supported web server, you must map URL prefixes
(virtual directory aliases) for Content Server's <Content_Server_Home>/cgi/ and
<Content_Server_Home>/support/ folders on your web server.
Note: If you are deploying Content Server using LLServlet and an application
server, you map the Content Server URL prefixes in the servlet’s context files.
See “Configuring an Application Server to Run Content Server” on page 48
• On Windows installations of Content Server, the mappings.tbl file contains the
URL prefix 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 Configuring 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
“Configuring Microsoft IIS Request Filtering for Use with Content Server”
on page 40.
• If you intend to use the Content Server WebDAV module, proceed to
“Configuring Microsoft IIS to Run WebDAV” on page 42.
• If you do not intend to use the Content Server WebDAV module, proceed to
“Configuring Content Server“ on page 81.

4.2. Configuring a Web Server to Run Content Server
To configure Microsoft Internet Information Services manually, complete the steps

in the following procedure.
To map Content Server URL prefixes in Microsoft Internet Information Services
1. Open Internet Information Services (IIS) Manager. In the Connections pane,

expand the Web Sites node.
2. Add the support folder as a virtual folder.
a. Right-click the Default Web Site node, and then click Add Virtual
Directory.
b. In the Add Virtual Directory dialog box, complete the following steps:
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. 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.

4. 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.
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.

5. 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:

• csview.exe
• livelink.exe
• llview.exe
• llisapi.dll
6. 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.
7. 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.
Configuring 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:
• GET
• HEAD
• POST
If you use OpenText WebDAV with Content Server, you should add the
following verbs:
• PROPFIND
• PROPPATCH
• MKCOL
• DELETE
• PUT

• COPY
• MOVE
• LOCK
• UNLOCK
• OPTIONS
• SEARCH
Allow high-bit characters

Content Server uses the UTF-8 character set, so Allow high-bit characters must
be enabled.
Maximum Allowed Content Length (Bytes)

OpenText recommends that you set the value of this setting to 250,000,000 bytes
to permit large files to be uploaded to or downloaded from Content Server.
Cluster Management requires this value to permit drag and drop of Content
Server Updates.
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.
Configuring Microsoft IIS to Run WebDAV

Content Server WebDAV is a Content Server optional core module. A default
installation of Content Server makes it available, but it is not automatically installed.
If you wish to install it, you can enable the installation on the Install Modules
administration page.
If you intend to install Content Server WebDAV, configure Microsoft Internet

Information Services to run WebDAV as follows.
To configure Microsoft IIS to run WebDAV:
1. Create a WebDAV authoring rule.
a. In Internet Information Services (IIS) Manager, expand Sites and then click
the Content Server website.
b. In the IIS section of the middle pane, open WebDAV Authoring Rules.
c. In the Actions pane, click Add Authoring Rule.
d. In the Add Authoring Rule dialog box:
• Enable Specified content, and then enter / in the Specified content

box.
• Enable All users in the Allow access to this content to section.
• Enable Read and Source in the Permissions section.

Click OK to save your changes.
2. Configure Microsoft IIS WebDAV settings.
a. In the Actions pane, click WebDAV Settings.

b. In the WebDAV Settings pane:
• Set Allow Anonymous Property Queries to True.

• Set Allow Property Queries with Infinite Depth options to True.
Click Apply to save your changes.
3. Enable WebDAV
a. In the Actions pane, click WebDAV Authoring Rules.

b. In the Actions pane, click Enable WebDAV.

Tip: If Disable WebDAV appears in the Actions pane, WebDAV is

already enabled.
Configuring Microsoft IIS to Return Meaningful REST API Error

Messages
Using the default configuration, Microsoft IIS returns a generic error message when
interfaces that are based on the Content Server REST API, such as the Content Server
Smart UI, encounter errors. Presenting a more informative error message to users
can aid in troubleshooting any difficulties that they encounter.
Example: With Detailed errors enabled, IIS returns a message similar to An item with
the name <filename.txt> already exists, but if Detailed errors is not enabled,
IIS returns only Error: Bad Request (400).
To enable Content Server to display informative error messages when problems

occur with Content Server REST API interfaces enabled using Microsoft IIS,
OpenText recommends that you enable Detailed Errors in Microsoft IIS
To enable Detailed Errors in Microsoft IIS:
1. Open Internet Information Services (IIS) Manager.

2. On the left, expand the Content Server web site, and click the Content Server
Application.
Tip: The default Application name is OTCS.
3. In the middle pane, double-click Error Pages

4. On the right, under Actions, click Edit Feature Settings
5. On the Edit Error Pages Settings, enable Detailed errors in the Error Responses
section, and then click OK.
4.2.2 Configuring Apache Web Server to Run Content Server

To configure Apache web server to work with Content Server, complete the steps in
the following procedure.
To map Content Server URL prefixes in Apache Web Server
1. Open the /conf/httpd.conf file in a text editor.

2. Add a mapping for the Content Server support folder, as shown in the
following example.
Example: This example presumes that you have installed Content Server on Windows
and accepted the default options:
• /img/ is the URL Prefix for the support directory

• the Content Server Install path is C:\OPENTEXT\

# Content Server support directory mapping

Alias /img "C:/OPENTEXT/support"
<Directory "C:/OPENTEXT/support">
AllowOverride None
Order allow,deny
Allow from all
</Directory>
3. Add a mapping for the Content Server cgi folder, as shown in the following
example.
Example: This example presumes that you have installed Content Server on Windows
and accepted the default options:
• OTCS is the service name and CGI Mapping name for Content Server
• the Content Server Install path is C:\OPENTEXT\
# Content Server CGI directory mapping

ScriptAlias /OTCS "C:/OPENTEXT/cgi"
<Directory "C:/OPENTEXT/cgi">
AllowOverride None
Options ExecCGI
Order allow,deny
Allow from all
</Directory>
On a Linux installation of Content Server, to allow Content Server URLs to use

livelink, rather than livelink.sh, add the FollowSymLinks directive to the
Options line, as shown in the following example.
Example: This example presumes that you have installed Content Server on Linux and
accepted the default options:
• livelink is the CGI alias for Content Server

• tthe Content Server installation directory is /usr/local/contentserver/
# Content Server CGI directory mapping

ScriptAlias /livelink "/usr/local/contentserver/cgi"
<Directory "C:/OPENTEXT/cgi">
AllowOverride None
Options ExecCGI,FollowSymLinks
Order allow,deny
Allow from all
</Directory>

4.2.3 Configuring Oracle iPlanet Web Server to Run Content

Server
To configure Oracle iPlanet Web Server to work with Content Server, complete the
steps in the following procedure.
To map Content Server URL prefixes on Oracle iPlanet Web Server
1. Log onto the Admin console.
2. Click the Configuration tab, and then click the Content Server Configuration.
3. On the Configuration Virtual Servers page, click the Content Server Virtual
Server.
4. Click the Content Handling tab, and then click the CGI subtab.
5. Click New. On the Add CGI Directory dialog box, enter the CGI-BIN Mappings
that appeared at the end of the Content Server installation. (See Step 13.)
6. Click the Document Directories subtab, and then click New. On the Add
Document Directory dialog box, enter the Document Directory Mappings that
appeared at the end of the Content Server installation. (See Step 13.)

7. On the Content Handling – Document Directories page, click Access Control,

and then click the Access Control Lists subtab.
8. Click New. On the Add Access Control List page:
a. Ensure that Path appears in the Resource box.

b. Delete the default rule. (Deny anyone from anyplace).
c. Create a new rule (Allow anyone from anyplace).
d. Click OK.
9. Click New. On the Add Access Control List page:
a. Ensure that URI appears in the Resource box.

b. Click OK.
10. Click Deployment Pending. On the Configuration Deployment dialog box,

click Deploy.
A dialog box appears that displays the message:
Results. The configuration has been deployed successfully to all
available nodes.
11. Open the Configurations page. Enable the Content Server Virtual Server and
click Start.
A dialog box appears that displays the message:
Results. Instance Started Successfully.

4.3 Configuring an Application Server to Run

Content Server
To run Content Server on a supported application server, you must configure the
application server to use the Content Server Servlet (LLServlet).
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, you must ensure that the application server can connect to
Content Server's root installation folder (the <Content_Server_Home> folder). You
must also configure the application server to run the LLServlet Java classes, which
are located in the <Content_Server_Home>/application/WEB-
INF/lib/llservletclient.jar file.
This section describes two methods of deploying Content Server using LLServlet:
• “Deploying the Content Server Servlet (Basic Deployment)” on page 49
In the basic deployment, Content Server is deployed using an application server
and LLServlet, rather than on a web server using CGI or ISAPI. This deployment
uses at minimum a single Content Server host.
• “Deploying the Content Server Servlet (Secure Extranet Architecture
Deployment)” on page 54
In the secure extranet deployment, a Content Server servlet client accesses a full
installation of Content Server on a separate computer. Typically, the two
computers are separated by a firewall. This deployment uses at minimum two
computers:
• The Content Server host: a computer running a full installation of Content
Server
• The servlet client host: a computer running LLServlet and a subset of the full
installation of Content Server

4.3. Configuring an Application Server to Run Content Server
4.3.1 Deploying the Content Server Servlet (Basic

Deployment)
The Content Server Servlet can be deployed on supported versions of Apache
Tomcat and on other supported application servers.
Note: Each time you apply a cumulative patch or a filter patch update, you
must redeploy LLServlet. When it is redeployed, it overwrites the
configuration files with the default files. Before redeploying the LLServlet
WAR file, be certain to back up these configuration files and then reapply them
after redeploying the WAR file.
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).
Deploying the Content Server Servlet on Apache Tomcat
Note: If, when you install Content Server, you select Apache Tomcat as your
HTTP Web Server Type, 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 UNIX 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.
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.
Note: If you are creating context files for the Secure Extranet Architecture,
(see “Deploying the Content Server Servlet (Secure Extranet Architecture
Deployment)” on page 54), start only the Apache Tomcat service.
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

Deploying the Content Server Servlet on IBM WebSphere

The following procedures will configure IBM WebSphere to work with Content
Server.
Deploying the Content Server Web Application
Note: Each time you apply a monthly patch or a filter patch update on the
server side, you must redeploy the LLServlet server. When it is redeployed, it
overwrites the configuration files with the default files. Before redeploying the
LLServlet WAR file, be certain to back up these configuration files and then
reapply them after redeploying the war file.
To deploy the Content Server web application:
1. Create the <Content_Server_Home> directory on the servlet host.
2. Access the WebSphere Administrative console.
3. Expand the Applications menu, and then click Install New Application.
4. Select Local file system or Remote file system and then type the path to the
WAR file in the associated field.
5. In the Context Root field, type the application context path. The context path is
the virtual directory name that you map to the Content Server URL prefix. For

example, if you type /aurora in the Context Path field, access to Content Server
through LLServlet is done through the following URL:
http://<host_name>/aurora/contentserver.exe
where <host_name> is the name of your Content Server installation.
6. Click Next.
7. When the page refreshes, select Generate Default Bindings, and then click
Next.
8. When the page refreshes, leave the default settings and click Next.

9. When the page refreshes, in the Clusters and Servers field, type the servers that
you want to install the WAR file to, and then click Next.
10. When the page refreshes, select the check box for LLServlet, click the
appropriate virtual host from the corresponding drop-down menu, and then
click Next.
11. On the Summary page, click Finish.
12. When the page refreshes, click Save to Master Configuration and then click
Save.
Deploying the Content Server Support Directory

For LLServlet to operate correctly, you must also deploy a web application within
the IBM WebSphere application server with a mapping to the
<Content_Server_Home>/support/ directory. This directory contains all the
support resources required by Content Server, including the images in the Content
Server user interface and the help system.
To deploy the Content Server support directory web application:
1. Open the <Content_Server_Home>/support/ directory on the Content Server

host.
2. Select all of the files inside the directory and compress them as a zip file, using a
WAR extension.
When using IBM WebSphere application server, the Content Server Web
application must be packaged as a WAR file.

3. Paste the WAR file into the <Content_Server_Home>/support/ directory on

the servlet host.
The WAR file will be subsequently be extracted by WebSphere.
4.3.2 Deploying the Content Server Servlet (Secure Extranet

Architecture Deployment)
A Secure Extranet Architecture deployment of Content Server uses at minimum two
computers:
• The Content Server host: a computer running a full installation of Content Server
• The servlet client host: a computer running LLServlet and a subset of the full
installation of Content Server
To create a Secure Extranet Architecture deployment of Content Server, you:
1. Deploy Content Server using the Content Server Servlet on the Content Server
host. (See “Deploying the Content Server Servlet (Basic Deployment)”
on page 49.)
2. Install an application server on the servlet client host.
3. Manually create files and folders on the servlet client host, and copy files and
folders from the Content Server host to the servlet client host, as described in the
following procedure.
To configure a secure Content Server deployment using LLServlet:
1. Create the <Servlet_Home> folder on the servlet client host.
Tip: The <Servlet_Home> folder can have the same name as

the<Content_Server_Home> folder, for example C:\OPENTEXT\, but this is
not a requirement.
2. Create the following subfolders on the servlet client host:
• <Servlet_Home>/config/
• <Servlet_Home>/filters/
• <Servlet_Home>/logs/
• <Servlet_Home>/temp/
• <Servlet_Home>/viewcache/
3. Copy the <Content_Server_Home>/application/ folder from the Content

Server host to the <Servlet_Home> folder on the servlet client host.
4. Copy the <Content_Server_Home>/support/ folder from the Content Server
host to the <Servlet_Home> folder on the servlet client host.
5. Modify the opentext.ini file as follows, and then save it on the servlet client
host in the <Servlet_Home>/config/ folder:

• Throughout the file, replace <Servlet_Home> with the name of the

<Servlet_Home> folder on the servlet client host.
• In the [general] section, change the Server and Port parameters so that
they point to the Content Server host. By default, the value of Port is 2099.
Tip: To determine the correct Port value, open the Content Server
Administration page on the Content Server host, and click Specify
Server Port in the Server Configuration section.
• Copy the htmlImagePrefix= line from the [general] section of the
opentext.ini file on the Content Server host and use it to replace the line
that reads: htmlImagePrefix=<corresponding value from Content Server
host>.
• To use streaming for file uploads, change the value of the useStreaming
parameter to TRUE (the value is FALSE by default).
• To configure a Document Conversion Service (DCS) for use with LLServlet,
specify the host and port parameters of an Admin server in the
[ExternalDCS] section of the opentext.ini file on the client servlet host.
Tip: The Admin server may reside on the Content Server host or on a
different computer.
To find the DCS port, open theContent Server System page on the
Admin server. Click the Functions menu of the Admin server, and then
click Properties > Document Conversion Service.
[general]
Port=<port>
Server=<IP address or domain name of Content Server host>
Logpath=.\logs\
OTHOME=<Servlet_Home>\
UploadDirectory=<Servlet_Home>\temp\
htmlImagePrefix=<corresponding value from Content Server host>
useStreaming=FALSE
Debug=11
[security]
Authentication=Livelink
[filters]
cachePath=<Servlet_Home>\viewcache\
lastIdFile=<Servlet_Home>\viewcache\lastid.dat
filterPath=<Servlet_Home>\filters\
eraseNo=10
autoRecMimeTypes=application/octet-stream
relativeLinkMimeTypes=text/html,application/pdf
[Locale]
Default=_en_US
_en_US=1

[client]
ReceiveBeforeSend=TRUE
[servlet]
wantStreamLogs=TRUE
[ExternalDCS]
host=<IP address or domain name of Content Server Admin
Server>
port=<DCS port on Content Server Admin Server>
viewcache=<Servlet_Home>\viewcache\
cachesize=10
[DCSParameters]
HHdefaulttype=ANSI8
HHhtml=generic
HHgraphics=none
HHinterlace=False
HHquality=100
HHgraphicsizemethod=smooth
HHtimeout=280
HHgraphicoutputdpi=70
Pipeline=View
6. Open the <Servlet_Home>\application\WEB-INF\web.xml file and modify

the path of the opentext.ini so that it points to the <Servlet_Home>\config\
folder on the servlet client host.
Note: The path to the opentext.ini file is referenced three times in the
web.xml file. All three locations must point to the location of the
opentext.ini file on the servlet client host.
7. To enable document uploads, complete the following steps:
• Set useStreaming=TRUE in the [general] section of the opentext.ini file

on the servlet client host.
Note: For more information on file streaming, see “Document File

Streaming Option” on page 58.
• Include the IP addresses of localhost, the Content Server host, and the
servlet client host in the Content Server Client Hosts box on the Configure
Security Parameters administration page, or leave the box empty to allow
any computer to send data to the Content Server host. (To access this page,
click Configure Security Parameters in the Server Configuration section of
the Content Server administration page.)
Tip: If IPv6 is used in the Content Server environment, the format of

the IP addresses should have the following appearance: ::ffff:
127.0.0.1,....
8. Create the Content Server XML context files. For more information, see “To
deploy the Content Server Servlet on Apache Tomcat:“ on page 49.

Important
For the docBase parameter, enter the path to the application or
support folder on the servlet client host, not the Content Server host.
Tip: If you used the Content Server installation program to create the
context files on the Content Server host and your <Servlet_Home> folder
has the same name as the <Content_Server_Home> folder on the Content
Server host, you can copy the Content Server XML context files from your
Content Server host to the servlet host.
Note: If the opentext.ini or web.xml file contains errors, or the Content

Server application folder does not contain the required folders, LLServlet may
fail to initialize. If you receive a Status 500 or
java.lang.NullPointerException message when you attempt to start
Content Server, verify that:
• There are no unnecessary white space characters in the LLServlet-related
parameters specified in the opentext.ini.
Example: The following parameter will prevent LLServlet from initializing because
of the space after the equals sign (=):
OTHOME= C:\SEA\
• All folders are specified with a trailing slash character.
Example: The following parameter will prevent LLServlet from initializing because
it does not have a slash character after SEA:
OTHOME=C:\SEA
• The <Servlet_Home> folder contains all of the following folders:
• application
• config
• filters
• logs
• support
• temp
• viewcache

Document File Streaming Option

LLServlet gives you the additional security option to use file streaming for all
document exchanges between LLServlet and Content Server. Streaming eliminates
the need for the servlet computer to have a file-system mapping to the Content
Server computer for file uploads, allowing for security best practices between
network tiers.
To enable streaming:
• set the value of useStreaming in the [general] section of the servlet client
host's opentext.ini file to TRUE. File streaming is used for both document
uploads to Content Server and for document conversion to HTML for viewing
document content in a client browser. Each item is enabled separately.
• add the following line to the [Filters] section of the opentext.ini file on the
servlet client host:
filterPath=<full_path_to_directory>, where <full_path_to_directory> is the
path to the filters folder on the servlet client host.
Streaming File Uploads

Streaming allows you to add documents to Content Server by streaming files from a
Content Server client to a server through a specific port (2099, by default). The
servlet handles the client side of the streaming, while the Secure Enterprise
Architecture Support module handles the server side.
The Secure Enterprise Architecture Support module reads in a file and saves it to a
temporary folder on the Content Server computer. It then modifies the location
parameter in the request to point to the location in Content Server where the file is to
be stored. Content Server obtains the file from the temporary folder, stores it in the
desired folder, and then deletes the file from the temporary folder when it is finished
processing.
For streaming uploads to function correctly, you must specify the temporary folder
on the servlet client host where streamed files are to be stored during the upload
operation. In the [general] section of the opentext.ini file of the servlet client
host, add the following line:
UploadDirectory=<full_path_to_directory>, where <full_path_to_directory> is a

folder on the servlet client host.
Tip: In the sample files in this guide, that path is C:\SEA\temp\
Streaming Document Conversion

When streaming is enabled, any time a browser client requests to view a document
as HTML, the data is streamed by Content Server to the servlet. Content Server first
streams the file to a Document Conversion Service (DCS) for conversion. The DCS
then streams the converted content to the servlet for delivery to the client browser.

To configure a DCS for use with the servlet, you supply values for the hostname and
port parameters of an Admin server in the [ExternalDCS] section of the
opentext.ini file on the servlet computer.
4.3.3 Sample Secure Extranet Architecture opentext.ini and

Servlet Context Files
The following sample opentext.ini file for the servlet client host presumes that
you have used the default installation settings of Content Server on the Content
Server host, that your <Servlet_Home> folder is C:\SEA\ and that the IP address of
the Content Server host is 10.20.30.40.
Example 4-1: Servlet Client Host opentext.ini File
[general]
Port=2099
Server=10.20.30.40
Logpath=.\logs\
OTHOME=C:\SEA\
UploadDirectory=C:\SEA\temp\
htmlImagePrefix=/img/
useStreaming=TRUE
[security]
Authentication=Livelink
[filters]
cachePath=C:\SEA\viewcache\
lastIdFile=C:\SEA\viewcache\lastid.dat
eraseNo=10
autoRecMimeTypes=application/octet-stream
relativeLinkMimeTypes=text/html,application/pdf
filterpath=C:\SEA\filters\
[Locale]
Default=_en_US
_en_US=1
[client]
ReceiveBeforeSend=TRUE
[servlet]
wantStreamLogs=FALSE
[ExternalDCS]
host=10.20.30.40
port=5863
viewcache=C:\SEA\viewcache\
cachesize=10
[DCSParameters]
HHdefaulttype=ANSI8
HHhtml=generic

HHgraphics=none
HHinterlace=False
HHquality=100
HHgraphicsizemethod=smooth
HHtimeout=280
HHgraphicoutputdpi=70
Pipeline=View
The following sample LLServlet context files for the servlet client host presume that
you have used the default installation settings of Content Server on the Content
Server host and that your <Servlet_Home> folder is C:\SEA\ .
Example 4-2: Servlet Client Host OTCS.xml(LLServlet Context) File

<?xml version="1.0" encoding="UTF-8"?>
<Context
path="/OTCS"
docBase="C:\SEA\application\"
debug="0"
swallowOutput="true"
reloadable="false">
<Logger
className="org.apache.catalina.logger.FileLogger"
prefix="OTCS"
suffix=".txt"
timestamp="true" />
</Context>
Example 4-3: Servlet Client Host img.xml(Content Server Support

Folder Context) File
<?xml version="1.0" encoding="UTF-8"?>
<Context
cookies="false"
docBase="C:\SEA\support\"
path="/img/"
useNaming="false"
workDir="work/Catalina/localhost/img/" />

Chapter 5
Installing Content Server 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.

• “Installing Content Server on Microsoft Windows” on page 61
• “Installing Content Server on Linux” on page 74
5.1 Installing 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 the Content Server
and make sure that the necessary supporting software—including the database
server and client, web server, application server, and web browser—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 “Preparing
to Install Content Server“ on page 23.
If you install multiple Content Server instances on one computer, you must 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.

Chapter 5 Installing Content Server on the Operating System
5.1.1 Running the Content Server Installer on Microsoft

Windows
To start the installation of Content Server installer, download the Content Server
installer from the OpenText Knowledge Center 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 URL prefix (virtual folder alias)
mapped to the <Content_Server_Home>/cgi/ folder in your web
server.
• 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.yourdomain.com).
You must 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.
Tip: If you have a static IP address, you can look up the domain
name by typing nslookup <ip_address> at the Windows
command prompt on the Content Server computer.
• In the HTTP Server Name box, type the host name of the computer on
which the web server resides, or accept the default value.

5.1. Installing Content Server on Microsoft Windows
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 URL prefixes.
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 “Installing

Content Server on Microsoft Internet Information Services on
Windows” on page 63.
• If you enable Apache Tomcat, proceed to “Installing Content Server on
Tomcat on Windows ” on page 66.
• If you enable Other, proceed to “Installing Content Server on Other
Supported Web Servers on Windows ” on page 69.
Installing Content Server on Microsoft Internet Information

Services on Windows
Note: The following instructions are a continuation of “Running the Content

Server Installer on Microsoft Windows” on page 62. 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 web site that will host Content Server. The default is Default
Web Site.
• 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.

The CGI Mapping name and Application pool name cannot be changed on this
dialog box. They are determined by the settings you entered on the OpenText
Content Server Configuration dialog box (Step 2.e).
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
• In the Cluster Agent Port box, type an unused port number for the Cluster
Agent service. Valid port numbers range from 1025 to 65535. The default is
3099.
Tip: After installation, you can change the port that the Cluster Agent
runs on by editing the Cluster Agent config.ini file. See OpenText
Content Server Cluster Management - Admin Online Help (LLESPAT-H-
AGD).
Note: If necessary, the Content Server installation program will install the
Microsoft Visual C++ redistributable package, which is required with the
latest version of Content Server. The Visual C++ Redistributable Package
installs runtime components of Visual C++ Libraries required to run
applications developed with Visual C++ 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 Server
web service, or enable Skip.
Note: Content Server 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 the OpenText
Knowledge Center.

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

message may appear:
Please install the following .NET Framework features on this
server: HTTP Activation, Non-HTTP Activation.
If this message appears, use Add Features in Windows Server Manager to
install WCF Activation. Enable both HTTP Activation and Non-HTTP
Activation when you add the WCF Activation feature.
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.
• Enter the installation path of your Apache Tomcat or accept the default
path (C:\Program Files\Apache Software Foundation\Tomcat 7.0\),
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, Start Content
Server Admin Server, and Start Content Server Cluster Agent, 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 URL prefix
(virtual folder alias) path names 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 “Applying Updates and Patches and Starting the Content
Server Services” on page 71.
Installing Content Server on Tomcat on Windows

you enabled Apache Tomcat in the HTTP Web Server Type dialog box (Step
2.f).
To install Content Server on Tomcat
1. In the Apache Tomcat Install Location dialog box, enter the installation of your
Apache Tomcat, or accept the default path (C:\Program Files\Apache
Software Foundation\Tomcat 7.0\). Click Next.
2. In the Apache Tomcat Web Server Settings 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.
makes for smaller Content Server web pages that render more quickly on
the client.
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
Click Next to continue the installation.
3. Complete the Port Configuration for OpenText Content Server dialog box, and
then click Next.
3099.

AGD).

Server.
Knowledge Center.

message may appear:
Next:

cws.

box appears.
• On the Apache Tomcat Web Server Settings dialog box, enter a Content
Server Web Service Mapping name or accept the default (cws), and then
click Next.
installation.
window.
8. Click Finish.
Important


Installing Content Server on Other Supported Web Servers on

Windows

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.
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:
3099.
AGD).



Server.
Knowledge Center.

message may appear:
Next:
cws.

box appears.
• On the Apache Tomcat Web Server Settings dialog box, enter the
Content Server Web Service Mapping name or accept the default (cws).

installation.
window.
7. Click Finish.
Important

5.1.2 Applying Updates and Patches and Starting 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 Content Server - 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 Content Server
- 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 Cluster Management to update

your Content Server installation. (See “Using Cluster Management to
Update Content Server” on page 111.) 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 “Creating a Windows User” on page 30. Launch the Windows
Services application and perform the following steps for each Content Server
service:
• Content Server (<service_name>)

• Content Server Admin (<service_name>)
• Content Server Cluster Agent (<service_name>)
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.

5.2 Installing Content Server on Linux

This section describes how to install Content Server on computers running
supported versions of Linux operating systems.
Before you install Content Server, you must create a Linux user to run Content
Server. You must also ensure that the database server and client, web server, and
web browser are installed and properly configured. See “Preparing to Install
Content Server“ on page 23.
For optimum performance, OpenText recommends that you install only one Content
Server instance on a given computer, especially for your corporate 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 do install multiple Content Server instances on one computer, make sure that
the installation directory, URL mappings, server ports, and program folder name of
each instance are unique. In addition, verify that all the dataflow 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.
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 Korn Shell

The Content Server installer and the Content Server start and stop scripts require the
presence of the Korn Shell (ksh). If the Korn Shell is not installed on your Linux
system, the following error message appears when you attempt to run ./setup:
bash: ./setup: /bin/ksh: bad interpreter
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 Linux system, you must
install it to ensure Content Server can generate thumbnails, present HTML views of
documents, and perform other tasks.
To install Xvfb on Linux, run the following commands:
yum -I xorg-x11-server-Xvfb
yum -I libXrender

5.2. Installing Content Server on Linux
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>/filters/image/startXVFB.sh to

reflect this Xvfb install location.
Modify startXVFB.sh once the installation completes.
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
The Content Server installer checks for the presence of the following libraries:
• /lib64/libbz2.so.1
• /lib64/libc.so.6
• /lib64/libcrypt.so.1
• /lib64/libdl.so.2
• /lib64/libm.so.6
• /lib64/libnsl.so.1
• /lib64/libpthread.so.0
• /lib64/librt.so.1
• /usr/lib64/libX11.so.6
• /usr/lib64/libXau.so.6
• /usr/lib64/libXrender.so.1
• /usr/lib64/libcairo.so.2
• /usr/lib64/libpixman-1.so.0
• /usr/lib64/libxcb.so.1
If the installer does not find one or more of the libraries, for example, 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:
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: On a computer that runs a Content Server Admin server, but not a
Content Server front-end instance, the same change should be made 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 Running the Content Server Installer 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 137.
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 “Creating a Linux User” on page 31.
2. Using the tools installed with your version of Linux, unzip and unpack the
setup utility.
3. Type ./setup, and then press ENTER.
Notes
• If an error message appears that states bash: ./setup: /bin/ksh: bad
interpreter, install the Korn Shell (ksh) on your copy of Linux. .
• 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 these error messages, see “Content Server

Installer Dependencies” on page 74
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 on which you want Content
Server to run, 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.
8. At the prompt that asks you for the port number on which you want the
Content Server Admin server to run, type a number between 1025 and 65535, or
accept the default (5858).
9. At the prompt that asks you for the port number on which you want the
Content Server Cluster Agent to run, type a number between 1025 and 65535, or
accept the default (3099).
Tip: After installation, you can change the port that the Cluster Agent runs
on by editing the Cluster Agent config.ini file. See OpenText Content
Server Cluster Management - Admin Online Help (LLESPAT-H-AGD).
10. 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.
11. 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.
12. At the prompt that asks if you will be using an Oracle database, type Y or press
ENTER.
13. At the prompt that asks you to specify the Oracle SID or the Oracle HOME
directory, accept the default value (orcl), specify a different SID, or enter ? to
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.
After you specify the Oracle SID or HOME directory, 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

To Directory Path : /usr/local/contentserver/cgi
Would you like to start Content Server now? [Y]:
14. Make a note of the directory mappings and then type N so that Content Server
does not start right away.
Important
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.
15. To complete the installation of Content Server on Linux, follow the instructions
at “Applying Updates and Patches and Starting the Content Server Processes”
on page 79.
16. Proceed to “Configuring Content Server“ on page 81.
5.2.3 Applying Updates and Patches and Starting 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 Content Server - 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 Content
Server - 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 Cluster Management to update

your Content Server installation. (See “Using Cluster Management to
Update Content Server” on page 111.) 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.
• To start the Content Server Cluster Agent process, run ./

start_otclusteragent in the <Content_Server_home> directory.
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 Linux 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 Linux system
administrator to set this up for you.

Chapter 6
Configuring Content Server
You have configured your web server or application server to run Content Server
(“Configuring the Web Server to Run Content Server“ on page 35), installed Content
Server on the operating system (“Installing Content Server on the Operating
System“ on page 61) and started it for the first time. Now you are ready to configure
Content Server for first use.
• “Accessing the Content Server Administration Page” on page 81
• “Configuring Server Parameters” on page 82
• “Creating the Content Server Database” on page 87
• “Installing Optional Content Server Modules” on page 98
• “Selecting the OTDS Server Type” on page 102
• “Creating the Enterprise Data Source” on page 104
• “Licensing Content Server” on page 106
• “The Congratulations! Page” on page 110
6.1 Accessing the Content Server Administration

Page
The Content Server Administration page is the starting point for most tasks you
perform as a Content Server Administrator. The Administration Pages have a
separate password, which is encrypted and stored in the opentext.ini file. This
password is set when you first configure Content Server, but it can be changed at
any time.
If you have system administration privileges, you can access the Content Server
Administration page in a variety of ways.
You must enter a password to access the Content Server Administration page. The
password for the Content Server Administration page (the Administrator Password) is
not the same as the password of the Admin user. By default, the password for the
Admin user is livelink, but you should reset it immediately.
There are several ways to access the Content Server Administration page:
Note: When connecting to Content Server which uses OpenText Directory

Services authentication, use a fully qualified domain name. Do not use
localhost
• On any Content Server page, click Content Server Administration in the Admin
global menu.

Chapter 6 Configuring Content Server
• At the bottom of most Administration pages is the Admin Home link, which
returns you to the main Content Server Administration page.
• 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>/contentserver.exe?func=admin.index
where:
• <protocol> is either HTTP or HTTPS.
• <server> is the name of the web host.
• <port> is the port on which your web server listens.
• <URL_prefix> is the URL prefix mapped to the <Content_Server_Home>/
cgi/ folder of the new version of Content Server.
• The .exe extension is not used for UNIX/Linux or when Content Server
works with an application server.
6.2 Configuring Server Parameters

The first step in configuring Content Server is to set some basic settings on the
Configure Server Parameters administrative page.
Configuring Basic Server Parameters

You can modify the following settings for the Content Server on the Configure
Server Parameters page:
• URL Prefix for /support Directory
The URL prefix, 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: /installation_path/support.
It is normally not necessary to change URL prefix; however, if you modify it, you
must make the change in Content Server and the web server.
The default value for the URL prefix is /img/.
Note: You must type a forward slash (/) before and after the URL prefix.
• Content Server Administrator Password

The Administrator password is one that you use to access the Administration
pages. Do not confuse this password with the password for the Admin user.
After the initial Content Server installation, you should change the default
Admin password. You can set a new Administrator password on the Configure
Server Parameters page by selecting the Change Administrator Password check
box. The new password takes effect the next time you log in as the administrator.

6.2. Configuring Server Parameters
• Site Name
The Site Name is the name that is displayed throughout Content Server. The site
name should be a simple, user friendly name. The default Site Name is Content
Server.
• Administrator E-mail Address
If you provide an email address for the Administrator, a link to the address
appears on the logon page.
• Categories Upgrade Batch Processing
This parameter enables you to set the refresh rate of the progress window during
batch Category upgrade operations. The default refresh rate is 200 items, which
means the progress window will refresh every time 200 Categories are processed.
• Configure Edit/Organize
This parameter allows you to specify a maximum number of items that users can
put on one page. The default is a maximum of 100 items per page.
Note: This limitation applies only to Edit/Organize pages. Pages that have
an associated Edit/Organize page include the My Favorites and My
Projects pages. When the Maximum Items Per Page limit is exceeded,
Content Server splits the Edit/Organize page into multiple pages. The limit
then applies to each split page individually.
• Default User Start Page
This parameter allows you to select one of the following pages, which is where
users are brought to when they first log 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.
Note: If you select About Content Server, you need to decide if you
want to require that your users login in order to view the page. If you
want to require that your users login, select the "About Content Server"
Requires Login check box. This option is disabled by default.
• Administer Icons for Folders
When enabled, this parameter allows users to select additional icons for Content
Server folders. This parameter is disabled by default.
• Duration of New and Modified Indicators
You can specify the number of days items have the New or Modified icons
next to them when items are added or changed. By default, the New icon
appears for 2 days after an item is added; the Modified icon appears for 7 days
after an item is changed.

• Multiple Address Separator for “mailto:” URL

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 choose a semi-colon ";" for the
address separator; if your organization predominately uses other email
applications, you should choose comma “,”.
• Server Logging Options
You can modify the logging options for the Admin server on the Configure
Server Parameters page or the Configure Debug Settings page. The following
logging options are available:
• No logging, which disables logging for the Content Server server. This is the
default setting.
• Thread logging, which generates the following log files in the
<Content_Server_home>/logs directory: llserver.out, sockserv1.out,
thread<c>.out (one per thread).
• Detailed thread logging, which generates the same log files as Thread
logging, but in verbose mode. Verbose mode includes information about the
relevant environment variables in the thread logs.
• Thread & CGI logging, which generates the following log files in the
<Content_Server_home>/logs directory: llserver.out, sockserv1.out,
thread<n>.out (one per thread), receiver<n>.out (one each per thread),
llclient<nnn>.out (one per request to the CGI program from an end-user
web browser), llindexupdate<nnn>.out (one per start of the Enterprise
Extractor), and indexupdateOut<nnn>.out (one per stop of the Enterprise
Extractor).
Note: When using LLServlet instead of the CGI, llclient<nnn>.out is

replaced by servletclient<nnn>.out. One file is generated for each
thread number as determined by your servlet container's Java Virtual
Machine. Each time a client browser sends LLServlet a request, a new
servletclient<nnn>.out file is created. If a file name with that
number, <nnn>, already exists, the request's information is appended to
the end of the existing file.
• In addition to configuring a Content Server logging setting, you can enable
SQL logging when you want to record the communication, in
connect<n>.log files, that occurs between the Server and the Content Server
database.
The number of connect<n>.log files is equal to the number of threads that
Content Server is running. If you are diagnosing a problem, you can
temporarily set the Content Server to run on a single thread. This allows you
to find diagnostic information in a single file. Because running on a single
thread severely impairs the performance of the Server, OpenText
recommends that you run in single thread mode during periods of low usage
only and that you return the Server to its original thread setting after you
complete your diagnosis.

6.2. Configuring Server Parameters
Note: Database connection logs can increase in size quickly. OpenText

recommends that you enable connection logging if it is required to
diagnose a problem, but that you disable it as soon as you have acquired
the diagnostic information that you need.
• Enhanced Keyboard Accessibility Mode
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.
• Character Set
You can specify the character set web browsers use when displaying the user
interface. For more information, see OpenText Content Server Admin Online Help -
Content Server Administration (LLESWBA-H-AGD) in the [general] section of the
OpenText Content Server Admin Online Help - Content Server Administration
(LLESWBA-H-AGD).
• 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. Open Text
recommends that you specify the full path to the directory in this field.
Note: Open Text strongly 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 “Applying a Content Server License
File” on page 109.)
• Receive Before Send
This setting reduces the amount of time the Server must dedicate to
downloading and opening documents. The default setting for Receive Before
Send is set to TRUE. When ReceiveBeforeSend=TRUE, 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.
• Server Threads
This setting defines the number of threads used by Content Server. The default
Number of Threads is eight. 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
• 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
Online Help - Search Administration (LLESWBS-H-AGD).
Note: Do not set the number of threads higher than the number of
connections supported by your RDBMS.
• Number of Sessions
This setting defines the maximum number of user log-in sessions cached on a
server thread. The default value of the Number of Sessions is set to 100. When
the maximum number of sessions is reached, the oldest user log-in session is
dropped. User log-in sessions are cached independently on each thread. When a
user returns to a thread after their log-in information has been dropped from the
cache, it will take slightly longer to execute their next request. The lower the
maximum number of sessions, the less memory the server must dedicate to
tracking user log-in sessions on each thread. The larger the number, however, the
less often the server will drop user log-in 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 sessions, depending on
how many users are accessing your Content Server system.
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 Content Server Administrator Password page, enter a password in the

Administrator Password and Verify Password boxes.

6.3. Creating the Content Server Database
Tips
• This sets the password that any Content Server administrator must
enter to access the Content Server Administration page. It is not the
password of the Content Server Admin user.
• Record the new Content Server Administrator password on
Section 10.3: “Content Server Installation Worksheet” on page 137.
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 “Applying a Content Server License File”
on page 109.)
5. At the bottom of the page, click Save Changes.
6. On the Select Default Metadata Language page, select a language, and then
click Continue.
7. Proceed to “Creating the Content Server Database” on page 87.
6.3 Creating 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 Content Server - Upgrade Guide (LLESCOR-IUP).
This section covers the following topics:

• “Creating an SAP HANA Database” on page 88
• “Creating an Oracle Database” on page 89
• “Creating a Microsoft SQL Server Database” on page 95
• “Creating a PostgreSQL Database” on page 93

6.3.1 Creating an SAP HANA 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:
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.
6. In the Create a new SAP HANA schema section, create an SAP HANA schema:
a. In the User Name box, select the name of the user that you created in the
above step.
b. In the Schema box, enter the name of the new HANA schema.
c. Click Create Schema.
Note: Record the user name, password, and schema name on the
Table 10-1: “SAP HANA Worksheet” on page 133.
7. Click Return to previous page.
8. 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.
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.
e. Click Create Tables.
9. If 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
“Changing the Admin User Password” on page 118.
The Install Modules page appears. Proceed to “Installing Optional Content Server
Modules” on page 98 to continue the installation.
6.3.2 Creating an Oracle Database

Oracle Database.
To create a new Oracle database:
2. On the Select RDBMS Type page, click 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 onto 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.
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 Windows or
Linux 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 134.
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
the adjacent box.

Note: The directory that you enter must already exist and the
Windows or Linux user that runs Oracle Server must have permission
to write to it.
d. Click Create Tables.
6.3.3 Creating a PostgreSQL Database

PostgreSQL.
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. 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.

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 134.
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.
the adjacent box.

6.3.4 Creating a Microsoft SQL Server Database

Microsoft SQL Server.
To create a new SQL Server database:

2. On the Select RDBMS Type page, click Microsoft SQL Server, and then click
Continue.
3. On the Microsoft SQL Server Administrator Log-in page, log onto SQL Server:
a. In the SQL 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 System User box, type the Microsoft SQL Server administrator user
name (usually sa).
c. In the System Password box, type the password of the Microsoft SQL
Server administrator user.
d. In the Master Database Name box, type the name of the system database
(usually master).
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 field, 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.
b. In the Password and Verify Password boxes, type a password for this user.
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.
c. In the Database Name box, click the name of the database in which you
want to create the Content Server database tables.
d. 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 135.
8. On the Create Content Server Tables page, create the Content Server tables:
a. In the SQL Server Database box, select the database that you created for
use with Content Server in the previous steps.
b. In the Microsoft SQL User Name box, enter the SQL Server user that you
created in the previous steps.
c. In the Password box, enter the password of the SQL Server user.
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.

the adjacent box.
Note: The directory that you enter must already exist and the
Windows user that runs Content Server must have permission to
write to it.
6.4 Installing 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 “Selecting the OTDS
Server Type” on page 102 to continue the Content Server installation.
You install a module in two stages:

6.4. Installing Optional Content Server Modules
• 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
“Installing Optional Content Server Modules: Stage 1” on page 99
• 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 on Content
Server, follow the instructions in “Installing Optional Content Server Modules:
Stage 2” on page 100.
Tip: For detailed information on installing Content Server modules, see

OpenText Content Server - Module Installation and Upgrade Guide (LLESCOR-
IMO).
6.4.1 Installing Optional Content Server Modules: Stage 1

This section describes the first stage of installing a module. The second stage is
described in “Installing Optional Content Server Modules: Stage 2” on page 100.
Depending on the operating system on which Content Server is running, proceed to

one of the following sections:
• “Installing Modules on Windows” on page 99
• “Installing Modules on Linux” on page 100
Installing Modules on Windows

You perform the first stage of a Content Server module installation using an
InstallShield installation program. 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 InstallShield Self-extracting EXE window, click Yes.

3. 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.
4. Select the Content Server installation to which you want to add the module.
(You can select only one.)
5. 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.

6. Click OK, and repeat steps Step 1 to Step 5 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 “Installing Optional Content Server Modules: Stage 2” on page 100.
Installing 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.
When you extract the modules, the extraction has to be done using the same user
and group that you use for running Content Server.
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. At the shell prompt, type the following command, and then press ENTER:
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 “Installing Optional Content Server Modules: Stage 2” on page 100.
6.4.2 Installing Optional Content Server Modules: Stage 2

This section describes how to perform the second stage of installing optional
Content Server modules. It assumes that you have completed the first stage of the
module-installation procedure described in “Installing Optional Content Server
Modules” on page 98.
After you set up the Content Server database, Content Server displays the Install
Modules page, where you perform the second stage of installing optional Content
Server modules.

6.4. Installing Optional Content Server Modules
Figure 6-1: The Install Modules Page
To continue the installation and setup of Content Server from the Install
Modules page:
1. Enable each of the modules displayed in the Installable Modules section 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 as many as nine modules at once, but if you want to install the
modules one at a time, install the required modules first.
2. After Content Server installs the selected modules, 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.
Note: Some Content Server module installations display a module-specific

configuration page before the Restart Content Server page. Consult the
documentation that accompanies such modules for instructions on how to
complete the configuration page.
3. After Content Server restarts, proceed to “Selecting the OTDS Server Type”
on page 102 to continue the initial configuration of Content Server.

6.5 Selecting 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.
6.5.1 Enabling 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 two pieces of information:

• The address of the OTDS Server.
• 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.
For more information on OpenText Directory Services, see OpenText Directory

Services - Installation and Administration Guide (OTDS-IWC).
To enable an external OTDS Server
1. On the Select OTDS Server Type 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. For example, enter dba563af-
b01d-4f88-bc42-2493c97dbc87.
4. Click Continue.
After you successfully connect to the OTDS Server, the Create New Enterprise Data
Source page appears. Proceed to “Creating the Enterprise Data Source” on page 104
to continue the initial configuration of Content Server.

6.5. Selecting the OTDS Server Type
6.5.2 Enabling 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 and servlet server that is built into
Content 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 public Internet. For example, for information on creating a
Java keystore, see http://www.eclipse.org/jetty/documentation/current/
configuring-ssl.html.
To enable an internal OTDS Server
1. On the Select OTDS Server Type page, select Internal OTDS Server in the
Server Type menu.
2. Enter available ports in the boxes in the OTDS Parameters and Jetty
Parameters sections. You can accept the default ports or specify different ones.
Click Check port to verify that the specified ports are not in use.
3. Optional To configure the internal OTDS Server to use a security certificate of

your choice, rather than the default self-signed certificate, enter Java key store
parameters in the HTTPS Configuration section.
4. Click Continue.
5. 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.
6. The User and group migration page appears. Click Continue.
7. The Migration Status page appears. when The migration has completed
successfully appears, click Continue.
After the migration completes, the Create New Enterprise Data Source page
appears. Proceed to “Creating the Enterprise Data Source” on page 104 to continue
the initial configuration of Content Server.

6.6 Creating 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 Online 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.

6.6. Creating the Enterprise Data Source
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).
b. In the Write Base Directory box, type the absolute path of the directory
(relative to the Content Server Admin server on which the Extractor runs)
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 primary Content Server host. You must choose a
directory on a drive on a primary Content Server host, and the directory
must differ from the write directories of other Enterprise data sources.
Tip: The Host 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 whether it is or not. If you do not see the green OK
icon, follow the instructions that appear in red to ensure that the Host
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.
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 an Admin server on the primary Content Server
host.
b. In the Read Base Directory box, type the absolute path of the directory
where you want the Document Conversion process to read data.
Specify the directory path as it is mapped or mounted on the host of the
Admin server on which the Document Conversion process runs. 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 absolute path of the directory
where you want the Document Conversion process to write converted data.
Specify the directory path as it is mapped or mounted on the host of the
Admin server on which the Document Conversion process runs.
Note: OpenText strongly 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. This directory must also differ
from the write base directories of other Enterprise data sources.
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 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
9. Continue the installation by following the instructions in “Licensing Content

Server” on page 106.
6.7 Licensing Content Server

After you complete the installation of the Enterprise Data Source (see “Creating the
Enterprise Data Source” on page 104), the License Setup page appears, and you can
apply a Content Server license file.
You can apply a license to Content Server during the initial installation or after you
have completed the installation. Until you have applied a license, however, Content
Server remains in administrative mode. In administrative mode, only users with the
System administration rights privilege can log onto 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.
You can exit administrative mode any time by applying a valid license to
Content Server.

6.7. Licensing Content Server
6.7.1 Types of License File

Several different types of license exist:
• No license
If you have not applied a license, Content Server operates in administrative
mode. It can be used by users that have the System administration rights
privilege, but other users cannot log on.
• 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 and has a specific expiry date (not a trial period 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 supports a production environment. For example, it is intended for use in a
Development or User Acceptance Testing environment. A non-production
license enables full Content Server functionality and has no expiry date.
6.7.2 Obtaining a 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 logon
for the product activation site (http://productactivation.opentext.com/
ContentServer). 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 appears that 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. Browse to the http://productactivation.opentext.com/ContentServer website. On

the OpenText Product Activation page, click Continue.
3. Log onto OpenText Connect using the logon and password provided to you
when you purchased Content Server.
4. On the My Support page, click Activations.

5. 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.
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.
Tip: If your logon is associated with multiple accounts, you can

temporarily limit your view to the account that concerns you by clicking
Change Account Selections.
6. 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 two new icons are visible:

6.7. Licensing Content Server
•
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.
6.7.3 Applying a Content Server License File

To apply a license file, browse to the license file that you acquired from the Product
Activation site (see “Obtaining a Content Server License File” on page 107), and
apply it to Content Server.
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 the OpenText Knowledge Center 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 Online Help - Content Server Administration (LLESWBA-H-
AGD)).
• The Content Server and web server users have full permissions to the
Content Server Upload directory.
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.

The Congratulations! page appears, indicating that you have completed the
initial configuration and startup of Content Server.
Storing Your Content Server 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.8 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 “Installing

Additional Instances of Content Server“ on page 123
If you do not wish to install additional instances of Content Server, proceed to

“Completing the Installation and Setup of Content Server“ on page 111

Chapter 7
Completing the Installation and Setup of Content
Server
This chapter contains information on a number of tasks that you should perform to
complete the installation and initial configuration of Content Server. You can
perform these tasks at any time, but for reasons of security or consistency, you may
prefer to do them before users first log onto Content Server.
For example, for security, it is important to create groups with appropriate access
permissions before allowing users to log onto Content Server, and for consistency, it
is important to decide which actions will trigger a change to an item’s Modified
Date in Content Server.

• “Using Cluster Management to Update Content Server” on page 111
• “Installing Optional Modules” on page 112
• “Installing Content Server Language Packs” on page 112
• “Creating the Help Indexes” on page 113
• “Performing Additional Tasks Before Users Connect” on page 115
7.1 Using Cluster Management to Update Content

Server
To ensure that your Content Server installation has all of the latest patches available
from OpenText, use Cluster Management to download, stage, and deploy all of the
patches that are currently available.
Content Server Cluster Management manages the application of Content Server

patches, Updates, and core language packs, on a single instance of Content Server
and throughout a Content Server cluster. Cluster Management automatically
handles patch dependencies and removes superseded patches when a newer version
of a patch is applied.
Tip: Use Cluster Management regularly to ensure that Content Server remains
up-to-date with patches, Updates, and core language packs. Run Cluster
Management whenever you make changes to your Content Server
deployment, and whenever you add optional modules to Content Server.
Configuring Cluster Management

Before you use Cluster Management, make sure that it is properly configured.

Chapter 7 Completing the Installation and Setup of Content Server
Open the Cluster Settings administrative page. (Click Cluster Management in the
Server Configuration section of the Content Server Administration page, and then
click Manage Cluster Settings.) Fill out each of the settings and then click Save
Settings.
To determine the correct values for each setting, click Help For This Page and read
the Managing Cluster Settings help topic.
Updating Content Server

After you have configured Cluster Management, use it to update Content Server.
Open the Manage Updates page. (Click Cluster Management in the Server
Configuration section of the Content Server Administration page, and then click
Manage Updates.) Download, stage, and deploy all of the patches that are currently
available.
For information on using Cluster Management to update Content Server, click Help
For This Page and read the Applying Patches, Updates and Language Packs help
topic.
7.2 Installing Optional Modules

Optional modules can be added to Content Server during installation, 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, and you did not install them during
the initial configuration, you can install them now. If you install your optional
modules now, run Cluster Management (see “Using Cluster Management to Update
Content Server” on page 111) afterwards to ensure that Content Server runs with all
of the necessary patches.
For information on installing optional modules, see “Installing Optional Content

Server Modules” on page 98 in this guide, or refer to the OpenText Content Server -
Module Installation and Upgrade Guide (LLESCOR-IMO).
7.3 Installing 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 Online Help - Content Server Administration (LLESWBA-H-AGD).
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.4. Creating the Help Indexes
7.4 Creating the Help Indexes

Content Server includes an extensive help system for users and administrators.
OpenText recommends that you create Help indexes so that users and
administrators can easily find the information they need to use Content Server.
Tip: If you add, uninstall, or upgrade a module after you index the Admin and
User Help, restart the data flow Directory Walker process for each Help index,
so that Content Server can update the Admin and User Help indexes to reflect
the changes.
7.4.1 Creating the User Help Index

You can generate an index of the Content Server User Help to enable users to search
the Help contents, from the Content Server Search page or directly from the Content
Server user help.
Content Server creates the User Help index on the Content Server host, which is
represented by the alias (usually Default) of its Admin server.
To create an index of User Help topics:
1. On the Content Server Administration page, in the Search Administration

section, click Open the System Object Volume.
2. On the Content Server System page, click Add Item, and then click User Help
Data Source.
3. On the Create New User Help Data Source page, in the Base Directory box,
type the absolute path of the folder in which you want to create the Help index.
The default is the <Content_Server_Home>/index/help/ folder.

Note: OpenText recommends that you choose a directory on a drive on

the Content Server host.
4. To change the default process prefix from Help, type a new unique identifier in
the Process Prefix box.
Note: In addition to being used as a label for all objects associated with
this index in the System Objects Volume, the text you type in the Processes
Prefix box is also the name used for this index's search slice in the Search
list on the Quick Search and Advanced Search pages.

Content Server creates the processes that generate the User Help index and
displays a Status page.
6. Click Continue.
The Content Server System page reappears, displaying the contents of the
Content Server System folder.
7.4.2 Creating the Admin Help Index

The Content Server Administration pages have their own Help content. Like the
Administration pages themselves, users cannot access Admin Help content unless
they have the System administration rights privilege.
To create an index of Admin Help topics:
1. On the Content Server Administration page, in the Search Administration

section, click Open the System Object Volume.
2. On the Content Server System page, in the Add Item menu, select Admin Help
Data Source.
3. On the Create New Admin Help Data Source page, in the Base Directory box,
type the absolute path of the directory in which you want to create the Admin
Help index. The default is the <Content_Server_Home>/index/adminhelp/
folder.

7.5. Performing Additional Tasks Before Users Connect
Note: OpenText recommends that you choose a directory on a drive on

the default Content Server host.
4. In the Process Prefix box, type a unique identifier for all the system objects that
are associated with this data source.
Content Server creates the processes necessary to generate the Admin help
index, and then displays a Status page.
6. Click Continue.
7.5 Performing 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.
Note: Content Server allows you to alter the look and feel of certain user
interface elements by modifying system cascade style sheets. See “Appendix B
– Understanding Cascading Stylesheets“ on page 139.
7.5.1 Creating Users and Groups and Setting Permissions

Creating 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.
Setting 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.

Setting 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 and Usage
Privileges administration page to restrict the creation of certain types of items to
certain users or groups.
Password Settings
Using OpenText Directory Services, specify password complexity and expiration
settings.
7.5.2 Configuring 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.5.3 Configuring Basic System Parameters

Setting 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)
Creating 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.
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.
The OpenText Archive and Storage Services can be used to connect to Archive
Server. See the OpenText Content Server – Archive Storage Provider Installation,
Upgrade and Configuration Guide in the Knowledge Center (https://
knowledge.opentext.com).
7.5.4 Configuring Basic System Functionality

Notifications
You enable or disable Notifications for the entire system and as well as specify
settings for email, reports, and SMTP.
Configure Search Options

You can set multiple Search options for users, including Find Similar command,
Hit Highlight Summary, Block Size, Common Authors, and others.
Enable a DCS
See “Enabling a Document Conversion Service (DCS)” on page 118.
Configure Workflow Parameters

See “Administering the Workflow Module” on page 119.
Enable Social Collaboration

Collaboration features such as commenting are not available to users until an
administrator enables them. OpenText™ Content Server Pulse is initially
disabled. You can enable it on the Pulse Administration page. You can also
enable and disable collaboration features for specific item types on the
Configure Collaboration Administration page.
You can grant individual users the ability to override global settings and disable
social interaction on specific items. Users could do this, for example, to disable
commenting for documents that they created.
7.5.5 Configuring System Administration

Scheduled Activities
You can set the Content Server to monitor various activities in the system and
give you reports on them. You can also specify whether you want to keep the
data or purge it once a report is generated.

7.5.6 Changing the Admin User Password

Once you have installed Content Server, change the password of the Admin user
account.
To change the password and set the profile for the Admin user:
1. On the global menu bar, click My Account, and then click Change Password.
2. On the password change form, enter Admin in the User name box and livelink
in the Old Password box, then enter a new password in the New password and
Confirm boxes.
3. Click Change.
Tip: Record the new password on Section 10.3: “Content Server Installation
Worksheet” on page 137.
7.5.7 Enabling a Document Conversion Service (DCS)

When you install Content Server, you can enable the DCS for your default Admin
server. Each Admin server can manage only one DCS. Anytime you add a new
Admin server or reconfigure an existing Admin server, you can also enable a DCS
for that server. Enabling multiple DCSs allows you to distribute the document
conversion load, improving the overall performance of your system. If an Admin
server becomes unavailable, the DCS that it manages also becomes unavailable;
however, if other Admin servers are available and manage a DCS, those DCSs can
handle document conversion. You can disable a DCS at your site at any time;
however, at least one DCS must be enabled for document conversion to occur.
Configuring DCS Settings

Each DCS has its own configuration file that reflects the settings that you configure
for it. The DCS configuration file is stored in the <Content_Server_Home>/config/
folder.
When you enable a DCS, Content Server configures most DCS settings for you. You
can change the settings at any time to customize how the DCS operates. An example
of settings that Content Server configures automatically are port numbers. Content
Server selects available ports for the DCS and configures the DCS port number and
the Admin port number. The Admin port number is the number of the port on
which the DCS listens for information from the Admin server; the DCS port number
is the number of the port that Content Server operations use to communicate with
the DCS. Other settings that Content Server may configure automatically include the
log file, which is the location of the file that records logging information for the DCS
you are configuring; the start folder and the filter path, which are the locations
where document-conversion filters are stored; and the rules file location, which is
where the document conversion rules file is stored. The document conversion rules
file is a file that DCS uses to determine which conversion filters to use.

Note: You must specify the temporary file folder. This is a temporary storage
location that is required by conversion filters.
Content Server appends the Admin port number to log file names when it creates
DCS log files. For example, the log file that corresponds to a DCS that listens on
Admin port number 5868 has the file name dcs_5868.log. The start folder location
and the filter path should match; on Windows operating systems, they must match.
7.5.8 Administering the Workflow Module

The Content Server Administrator can control access to powerful features included
in the Content Server Workflow module.
Workflow Module Administration Pages

You can administer the Content Server Workflow module in the Workflow
Administration section of the Content Server Administration page by clicking the
following links:
• Open the Workflow Volume, which allows you to work with the items stored in
the workflow attachments volume, and to administer access for users without
bypass privileges and Content Server services that are using domains
• Configure Workflow Agent Parameters, which allows you to set the Workflow
Agent schedule and other parameters
• Configure Workflow Parameters, which allows you to set privacy for audit
trails, set defaults for status, and control the use of proxies
Administer Access to the Item Handler Step and Workflow Agent
To administer access to the Workflow Agent and Item Handler step, open the
Content Server Administration page, navigate to the System Administration
section, and then click Administer Object and Usage Privileges. See OpenText
Content Server Admin Online Help - Workflow Administration (LLESWFW-H-AGD).
About The Item Handler Step

The primary feature of Content Server workflow is the Item Handler step, a
workflow step that provides a powerful environment in which you can program
simple or complex document operations and other functions to be automatically
performed when a workflow reaches the step.
Users must take great care when using the Item Handler step because they can
automatically create, modify, and remove multiple Content Server items. For
example, the Item Handler step's Move/Copy tab allows users to move and rename
Content Server items, and the Versioning tab can be configured to create Versions,
Releases, and Generations of Content Server documents or compound documents. If
users are not familiar with the Item Handler step capabilities or do not take care in
configuring the step, Content Server items may be permanently deleted or altered.

The Content Server Administrator must grant permission to users who want to use
the Item Handler step before they can add an Item Handler step to a workflow. Also,
the Content Server Administrator has the ability to control which Item Handler step
features are available to users.
Logging Item Handler Step Information
If you encounter an error or another problem using the Item Handler step and
would like more information about step processing, you can enable Content Server
Workflow to write Item Handler information to the Content Server thread log file,
<Content_Server_Home>/logs/thread<x>.out.
To enable or disable Item Handler step logging:
1. Open the Content Server configuration file, <Content_Server_Home>/

config/opentext.ini.
2. Locate the [Workflow] section. If it does not exist, create it.
3. Locate the IHLogging parameter. If it does not exist, create it.
4. Set the IHLogging parameter to one of the following values:
• 1, to enable Item Handler logging
• 11, to enable Item Handler logging with time stamps
• 0, to disable Item Handler logging
About The Workflow Agent

The Workflow Agent is a Content Server workflow feature that transparently
processes Item Handler step tasks and sends the workflow on to the next step. It also
performs send-on processing for User, Initiator, and Form Task steps that are
configured to use send-on processing. By default, the Workflow Agent is configured
to gather and perform background tasks every 10 minutes, but the Content Server
Administrator can specify a custom schedule that controls when the Workflow
Agent runs.
When the Workflow Agent processes an Item Handler step, it impersonates the user
assigned to the step. The audit trail for all items affected by the step will show the
user\qs name even though the user does not initiate the Content Server operations.
Also, you must be sure that the step assignee has the required privileges to complete
all requests defined in the step, or else errors will occur. For example, if you create
an Item Handler step that moves a document from one folder to another folder that
the user does not have privileges to update, the move document request fails.
If the Workflow Agent encounters an error during processing, it sends the step to
the Assignments page of the user assigned to the step. Also, it makes an attempt to
send an email message that alerts Workflow managers and the step performer to the
error, and requests action to correct the problem. In order to send error messages,
the Workflow Agent requires the following:

• The Content Server Administrator must specify the email server SMTP settings
and the sender email address.
• Workflow managers and step assignees must specify their email address in their
Content Server profiles.
Administering the Item Reference Attribute

When users build a workflow, they can create attributes that store information to be
tracked throughout the work process. For example, a workflow can contain a date
attribute that allows workflow performers to specify a task's projected due date.
An attribute can contain one of the following types of information: text, dates,
integers, real numbers, Boolean values (represented by a check box), and Content
Server item references. The item reference attribute is a special attribute that allows
workflow participants to browse Content Server and select an item. When an item is
selected, the attribute stores the item's unique Content Server object ID. For example,
you can create an item reference named “Item to Review” and specify that
documents and compound documents are the only valid types users can specify.
When a workflow is initiated, a workflow participant can identify information they
want another participant to review by selecting a document or compound
document.
The Content Server Administrator can limit the type of Content Server items users
can select in an item reference by excluding Content Server items by node type ID
from the item reference attribute. “Common Node Type IDs” on page 122 displays a
list of common Content Server node type IDs.
To exclude Content Server items from the item reference attribute:
1. Edit the Content Server configuration file, <Content_Server_Home>/

config/opentext.ini.
2. Locate the [Workflow] section. If it does not exist, create it.
3. Locate the ExcludedNodeSubTypes parameter. If it does not exist, create it.
4. Set the value of the ExcludedNodeSubTypes parameter to the node type ID of

the Content Server item you want to exclude from the item reference attribute.
Separate node type IDs with a comma.
For example, ExcludedNodeSubTypes={141, 142} excludes the Enterprise
Workspace and My Workspace from the list of items that can be stored in an
item reference attribute.
5. Save your changes to the file.
6. Restart Content Server.
Note: By default, the Content Server Workflow module always excludes all
system volumes and non-displayable containers.

Table 7-1: Common Node Type IDs
Item Node Type ID

Shortcut (alias) 1
Category 131
Channel 207
Compound Document 136
Discussion 215
Document 144
Enterprise Workspace 141
Folder 0
Generation 2
LiveReport 299
Milestone 212
News 208
My Workspace 142
Poll 218
Project 202
Project Template 543
Task 206
Task Group 205
Task List 204
URL 140
Workflow Map 128
Workflow Status 190

Chapter 8
Installing Additional Instances of Content Server
You can scale your Content Server environment by adding additional instances of
Content Server and connecting them to the database that you created in “Creating
the Content Server Database” on page 87.
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 “Installing an Additional Front-End Server”
on page 123.
To increase the capacity of your Search infrastructure, you can install additional
instances of Content Server and deploy them as secondary Admin servers. To do
this, follow the instructions in “Installing a Secondary Admin Server” on page 124
• “Installing an Additional Front-End Server” on page 123

• “Installing a Secondary Admin Server” on page 124
8.1 Installing an Additional Front-End Server

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)

Chapter 8 Installing Additional Instances of Content Server
8.1.1 Setting up Perspective Manager in a Clustered

Deployment of Content Server
Perspective Manager allows you to customize the Content Server Smart View user
interface to create workspaces tailored to specific user roles. After you have installed
your first instance of Content Server, additional steps are required to ensure that
Perspective Manager works on each additional instance of Content Server that you
install.
Perform the following steps after you have installed and performed your initial
configuration of every Content Server instance in the cluster, including connecting
each one to the Content Server database.
To set up Perspective Manager in a clustered Content Server deployment:
1. Copy the folder named OTPERSPECTIVEMGR from the ...

\<Content_Server_home>\csapplications\ folder on the initial instance of
Content Server to the same folder on each additional instance of Content Server
in the cluster.
2. Copy the folder named OTPERSPECTIVEMGR from the ...

\<Content_Server_home>\support\csapplications\ folder on the initial
instance of Content Server to the same folder on each additional instance of
Content Server in the cluster.
8.2 Installing a Secondary Admin Server

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 secondary hosts for a production deployment of Content Server.
Installing a secondary 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 secondary host. The secondary Admin server should
run only the Content Server Admin and the Content Server Cluster Agent services.
Depending on your computer’s operating system, proceed to one of the following

sections:
• “Installing a Secondary Admin Server on Windows” on page 125
• “Installing a Secondary Admin Server on Linux” on page 126

8.2. Installing a Secondary Admin Server
8.2.1 Installing a Secondary 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 secondary Admin server on Section 10.3:
“Content Server Installation Worksheet” on page 137.
To install a secondary Admin server on Windows:
1. On the computer that you want to make a secondary Admin server, log in as a
user that belongs to the Administrators group.
2. Install a new instance of Content Server, as described in “Installing an
Additional Front-End Server” on page 123, 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.
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.
c. Set the Content Server Cluster Agent (<service_name>) service to start
automatically.
i. In the right pane, right-click the Content Server Cluster Agent

(<service_name>) service, and then choose Properties.
ii. In the Startup type drop-down list, click Automatic.
iii. Click OK.
Note: If you create the secondary Admin server on the same

computer as a running instance of Content Server, the Content Server
Cluster Agent (<service_name>) service for the secondary Admin
server is disabled. Only one Content Server Cluster Agent can run on
a single computer.
After you create a secondary Admin server, you need to register it on the Default
Admin server. For information on this step, see “Registering a Secondary Admin

8.2.2 Installing a Secondary 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 137.
To install a secondary Admin server on Linux :
1. On the host computer that you want to use as a secondary Content Server host,
log on as the user that runs.
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 configure the Content Server processes, as follows.
a. Stop the Content Server process by running ./stop_llserver.

b. Start the Content Server Admin process by running ./start_lladmin.
c. Start the Content Server Cluster Agent process by running ./
start_otclusteragent.
Note: If you create the secondary Admin server on the same computer as
a running instance of Content Server, do not attempt to start the Content
Server Cluster Agent process for the secondary Admin server. Only one
Content Server Cluster Agent can run on a single computer.
After you create a secondary Admin server, you need to register it on the Default
Admin server. For information on this step, see “Registering a Secondary Admin
8.2.3 Registering a Secondary Admin Server

After you have installed a secondary Admin server, you need to register it with the
Default Admin server. This section describes how to register a secondary Admin
server so that you can create indexes (including the Enterprise index) and related
dataflow processes on that host.
For additional information on registering the Admin server of a secondary Content

Server host after the installation and initial setup of Content Server, see the OpenText
Content Server Admin Online Help - Content Server Administration (LLESWBA-H-AGD).
Note: Do not register a particular Admin server with more than one Content
Server host.
To register a secondary 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 “Installing Content Server on the
Operating System“ on page 61.) 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. To enable the Document Conversion Service on the secondary Admin

server, select the Enable check box.
g. Click Add.

8.2.4 Configuring Logging on Secondary Hosts

Upon initial startup of the Admin server on a primary or secondary (additional)
Content Server host, Content Server creates the admserv.log file in the
<Content_Server_Home>/logs/ directory. For the Admin server on the primary
Content Server host, you can use the Configure Debug Settings page to modify the
logging settings. However, to configure Admin server logging on secondary Content
Server hosts, you must edit the opentext.ini file on each of the secondary hosts.
You can modify the following Admin server logging settings for each additional
Content Server host:
• Location and name of Admin server log file
• Admin server logging level
• Whether or not you want to log the data stream between the Content Server and
the Admin server
The logging level does not apply to the default admserv.log file, which is always at
the default (level 1) logging level. You can only modify the logging level if you
specify a custom log file name and/or location.
To configure Admin server logging on an additional Content Server host:
1. Stop the Admin server.
2. Open the <Content_Server_Home>/config/opentext.ini file on the

additional Content Server host in a text editor.
3. Scroll to the [OTAdmin] section.
4. To write the Admin server logs to a file other than the default, do the following:
Add the following line to the [OTAdmin] section:
logfile=<path>
where <path> is the absolute path of the file that you want to use for Admin
server logging on the secondary Content Server host.
Add the following line:
loglevel=<n>
where <n> is the desired log level (1 = default, 2 = verbose, 3 = debug).
5. To log the data stream flowing into the Admin server from the Content Server,
add the following line to the [OTAdmin] section:
logoutput=<path>
where <path> is the absolute path of the file that you want to use for logging the
data output of the Admin server on the secondary Content Server host.
To log the data stream flowing from the Admin server to the Content Server,
add the following line to the [OTAdmin] section:

loginput=<path>
where <path> is the absolute path of the file that you want to use for logging the
data input to the Admin server on the secondary Content Server host.
6. Save and close the opentext.ini file.
7. Restart the Admin server.

Chapter 9
Uninstalling Content Server
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 Content Server -
Upgrade Guide (LLESCOR-IUP).

• “Uninstalling Content Server on Windows” on page 131
• “Uninstalling Content Server on UNIX/Linux” on page 132
9.1 Uninstalling Content Server on Windows

Content Server uses the InstallShield program 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, the InstallShield program advises you of
files or folders that it could not remove.
To uninstall Content Server on Windows:
1. Stop the Content Server services.
2. Click Start, point to Settings, and then click Control Panel.
3. Open Add/Remove Programs.
4. Use the utility's Automatic method to remove the Content Server program.
After the uninstallation process completes, the InstallShield program advises
you of files or folders that it could not remove.

Chapter 9 Uninstalling Content Server
9.2 Uninstalling Content Server on UNIX/Linux

Note: When you uninstall Content Server in a UNIX/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.
9.2.1 Uninstalling Content Server or a Content Server

Secondary Installation on UNIX/Linux
To uninstall Content Server or a Content Server secondary installation on
UNIX/Linux:
1. Log in to the UNIX/Linux host as the user that the Content Server or servers run
as.
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:
./stop_llserver
3. If the directory tree of the Content Server installation that you are removing
does not contain vital data, you can delete it.

Chapter 10
Appendix A – Content Server 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

Chapter 10 Appendix A – Content Server Installation Worksheets

Name of SAP HANA
schema for Content Server
database
Table 10-2: Oracle Database Worksheet

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
Server database
Table 10-3: PostgreSQL Worksheet

PostgreSQL server name
PostgreSQL administrator
account
Password of PostgreSQL
administrator account
Name of PostgreSQL user
Server database
Password of PostgreSQL
user that accesses the

10.2. Web Server Worksheets

Name of PostgreSQL
Table 10-4: Microsoft SQL Server Worksheet (Windows only)

SQL Server Name
System administrator user sa

name
System administrator
password
System database master
Name of SQL Server

database containing the
tables
Data file name
Path of data file
Log file name
Path of log file
Name of SQL Server user

Server database
Password of the SQL
Server that accesses the
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)
Table 10-6: Oracle iPlanet Web Server Worksheet

Installation
TCP port number 80
Administration server port

number
Administration server access
URL
Administration access user name admin
Administration access password
User created to run the web

server
Password for user created to run
the web server
Table 10-7: Apache HTTP Server Worksheet

Installation
TCP port number 80
Operating system user created to

run the web server
Password for operating system
user created to run the web
server

10.3. Content Server Installation Worksheet
Application Server Worksheets
Table 10-8: Apache Tomcat Worksheet

Installation
TCP port number 8080

run the web server
server
Table 10-9: IBM® WebSphere® Worksheet

Installation
TCP port number 8080
WebSphere Administrative
console user name
WebSphere Administrative
console user password
run the web server
server
10.3 Content Server Installation Worksheet

Table 10-10: Content Server Installation Worksheet
Setting Value Required for Configured

Installation during
installation of
Content Server
Windows or Linux user
created to run Content
Server
Password of the Windows
or Linux user created to
run Content Server

Setting Value Required for Configured

Installation during
installation of
Content Server
Content Server Windows OTCS
service name (Windows
installations only)
URL prefix (virtual Windows
directory alias) of OTCS1
<Content_Server_Hom
e>/cgi/ directory (Linux Linux
only) livelink
URL prefix (virtual Windows

directory alias) of img
<Content_Server_Hom Linux
e>/support/ folder livelinksupport
Content Server port 2099
number
Admin server port 5858
number
Cluster Agent port 3099
number
Administrator password2 livelink
Password of the Admin livelink

user3
1. On Windows, the Content Server service name and the Content Server
URL prefix are the same.
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 used to access the Content Server
Administration page. 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 Online Help - Content Server
Administration (LLESWBA-H-AGD).

Chapter 11
Appendix B – Understanding Cascading
Stylesheets
Content Server allows you to alter the look and feel of certain user interface elements
by modifying system cascading style sheets. For example, you can customize fonts,
point sizes, colors and spacing by modifying style sheets based on the type of
browser your organization uses.
Note: This guide assumes you have knowledge of cascading style sheets.
11.1 Locating the Stylesheets

In the <Content_Server_Home>/support/style/ folder, you will find multiple
style sheets. There are three primary style sheets:
• screen.css is the default style sheet that Content Server uses to apply styles to
all web pages.
• ie6.css allows you to ensure the page renders correctly in IE6 (only if that is the
browser being used to render the page).
• otfunc.css is part of the UI Toolkit project.
11.2 Modifying Common Elements

The following example changes the font type and size by creating a class. It does this
on the General tab of the Properties page for a Content Server item. The following
code sample depicts typical tags and values for the font face and size:
<TD CLASS="LABEL" NOWRAP>Type:</TD>

<TD CLASS="labelVerticalDividerRight" BACKGROUND="/img/tbl-
divider-ver.gif" STYLE="background-
repeat: repeat-y:"><IMG HEIGHT="1" ALT=""SRC="/img/spacer.gif"
WIDTH="2" BORDER="0"></TD>
<TD CLASS="valueStatic" NOWRAP >
<IMG SRC="/img/8space.gif" WIDTH="8" HEIGHT="8" BORDER="0"
ALT=""TITLE=""><IMGlivelinksupport/webdoc/folder.gif WIDTH="16"
HEIGHT="16" BORDER="0" ALT="F SRC="/img/webdoc/folder.gif"
WIDTH="16" HEIGHT="16" BORDER="0" ALT="Folder"> Folder</TD>
>
The code displays as:

Chapter 11 Appendix B – Understanding Cascading Stylesheets
In the screen.css file, define the style and values for font face and size:
/*
The style to use for the label part of the label/value pair.
Use with:
<td>
*/
.label {
width: 1%;
background-color: #e2e2e2;
font-family: Tahoma, Verdana, Geneva, Arial,
Helvetica, sans-serif;
text-align: left;
font-weight: normal;
font-size: 11px;
}/*
/*
Defines the style of static text next to the label. The second
part of the label/value pair.
Use with:
All input types other than "TEXT"
In some cases it may be used as the class for the enclosing
table division (<TD>), this is
useful when you have multiple elements with static text and
a single label, e.g. several radio
buttons.
*/
.valueStatic {
font-size: 11px;
font-weight: normal;
}
The label text color is magenta, which is the result of the cascade styles set on the
<BODY> tag. If you set a color on the label class, it would override the style from the
<BODY> tag.
This is the edited HTML as it refers to the screen.css file:

11.2. Modifying Common Elements
.label {
width: 15%;
white-space: nowrap;
color: #CD00CD;
background-color: #e2e2e2;
border-left: 1px solid #ffffff;
border-top: 1px solid #ffffff;
border-right: 1px solid #999999;
text-align: left;
font-weight: bold;
font-size: 11px;
}
The code displays as:


OpenText Content Server 16.0.0 - Installation Guide English (LLESCOR160000-IGD-EN-02)

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

OpenText Content Server 16.0.0 - Installation Guide English (LLESCOR160000-IGD-EN-02)

Загружено:

Авторское право:

Доступные форматы

OpenText™ Content Server

Welcome to Content Server! This guide walks you through the

40 Avenue Monterey , Luxembourg, Luxembourg L-2163

Open Text Corporation

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

No Warranties and Limitation of Liability

2 Designing Your Content Server System ................................. 7

3 Preparing to Install Content Server ....................................... 23

4 Configuring the Web Server to Run Content Server ............ 35

5 Installing Content Server on the Operating System ............ 61

6 Configuring Content Server ................................................... 81

7 Completing the Installation and Setup of Content Server . 111

8 Installing Additional Instances of Content Server ............. 123

OpenText Content Server – Installation Guide iii

8.1 Installing an Additional Front-End Server ........................................ 123

9 Uninstalling Content Server ................................................. 131

10 Appendix A – Content Server Installation Worksheets ..... 133

11 Appendix B – Understanding Cascading Stylesheets ....... 139

iv OpenText Content Server – Installation Guide

Installing Content Server

OpenText™ Content Server is the leading collaboration and enterprise content

Thanks to its standards-based, open architecture, Content Server can integrate

This chapter covers the following topics:

• “Overview of Content Server Installation” on page 5

1.1 Overview of Content Server Installation

OpenText Content Server – Installation Guide 5

• Information on adding additional instances of Content Server to your

1.2 Upgrading Content Server and Installing Updates

6 OpenText Content Server – Installation Guide

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

This chapter covers the following topics:

2.1 About Content Server

Figure 2-1: Basic Content Server System

OpenText Content Server – Installation Guide 7

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

2.1.1 Required Third-Party Applications

A complete Content Server system includes the following components:

8 OpenText Content Server – Installation Guide

• Apache™ Tomcat Server

2.1.2 Content Server Components

Language Support and UTF-8 Character Encoding

OpenText Content Server – Installation Guide 9

XML Support in Content Server

10 OpenText Content Server – Installation Guide

Content Server Extensibility

Developer tools include:

Content Server SDK

Document Conversion Service (DCS)

For information about configuring a DCS, see “Enabling a Document Conversion

OpenText Content Server – Installation Guide 11

Content Server Services and Modules

Content Server Modules

The Knowledge Center (https://knowledge.opentext.com/) contains more

2.2 Understanding Content Server Architecture

2.2.1 Access Tier

12 OpenText Content Server – Installation Guide

2.2.2 Application Tier

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

2.2.3 Data Tier

2.3 Architectural Options

OpenText Content Server – Installation Guide 13

2.3.1 Multihost Architectures

Figure 2-2: Monolithic Content Server Architecture

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