OpenText Content Server

OpenText Content Server
Installation Guide
This guide is intended for Content Server administrators. It

provides instructions for installing and configuring new
installations of Content Server.
LLESCOR100012-IGD-EN-1
OpenText Content Server
Installation Guide
LLESCOR100012-IGD-EN-1
Rev.: 2013-Aug-31
This documentation has been created for software version 10.0.0 plus Service Pack 2 Update 12.
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
Email: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com
Copyright © 2013 by Open Text Corporation

OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not
exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names
mentioned herein are property of Open Text SA or other respective owners.
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
PRE Introduction v
i About this document .......................................................................... v
ii Contact information .......................................................................... vi
1 Installing Content Server .......................................................... 9

1.1 Installing Content Server ................................................................... 9
1.2 Upgrading Content Server and Installing Updates ............................. 10
2 Designing Your Content Server System ............................... 11

2.1 About Content Server ...................................................................... 11
2.2 Understanding OpenText Content Server Architecture ....................... 17
2.3 Architecture Configuration Options ................................................... 18
2.4 Best Practices for System Design .................................................... 23
3 Preparing to Install Content Server ....................................... 27

3.1 Installation Worksheets ................................................................... 27
3.2 Configuring the Access Tier ............................................................. 30
3.3 Installing a Database Server ............................................................ 31
3.4 Creating an Operating System User ................................................. 34
3.5 Setting Up Client Web Browsers ...................................................... 35
4 Installing Content Server on Windows .................................. 39

4.1 Installing Content Server ................................................................. 39
5 Installing Content Server on UNIX and Linux ....................... 43

5.1 Installing Content Server ................................................................. 43
6 Configuring Content Server ................................................... 47

6.1 Deploying and Configuring LLServlet ................................................ 47
6.2 Mapping Content Server URL Prefixes in a Web Server .................... 60
6.3 Configuring Microsoft IIS Request Filtering for Use with Content
Server ............................................................................................ 64
6.4 Installing Optional Content Server Modules: Stage 1 ......................... 66
6.5 Performing a Secondary Installation ................................................. 68
6.6 Setting Up and Starting the Content Server Services ......................... 70
6.7 Configuring General Settings ........................................................... 74
7 Creating the Content Server Database .................................. 77

7.1 Creating an Oracle Database ........................................................... 77
LLESCOR100012-IGD-EN-1 OpenText Content Server iii

Table of Contents
7.2 Creating a Microsoft SQL Server Database ....................................... 81
8 Completing the Installation and Setup of Content Server ... 85

8.1 Installing Optional Content Server Modules: Stage 2 ......................... 85
8.2 Registering a Secondary Admin Server ............................................ 87
8.3 Creating the Enterprise Index ........................................................... 89
8.4 Creating the Help Indexes ............................................................... 92
8.5 Additional Tasks to Perform Before Users Connect ........................... 94
9 Installing and Uninstalling Modules .................................... 105

9.1 Installing Modules ......................................................................... 105
9.2 Installing Filter Packs .................................................................... 108
9.3 Uninstalling Modules ..................................................................... 109
9.4 Updating the Help Index to Reflect Changes in Installed Modules ..... 111
10 Uninstalling Content Server ................................................. 113

10.1 Uninstalling Content Server on Windows ........................................ 113
10.2 Uninstalling Content Server on UNIX/Linux ..................................... 114
11 Appendix A – Understanding Cascading Stylesheets ....... 115

11.1 Locating the Stylesheets ................................................................ 115
11.2 Modifying Common Elements ........................................................ 115
IDX Index 119
iv OpenText Content Server LLESCOR100012-IGD-EN-1

Preface
Introduction
i About this document
This guide provides instructions for designing and installing a Content Server
system.
i.i Target readership

This guide is written for Content Server administrators: the person or people
responsible for deploying, administering, and maintaining Content Server.
Organizations differ widely in how they organize administrative responsibility for a
Content Server system. For example, administration of the Content Server database
in a large organization is often handled by a database specialist, who may or may
not be familiar with Content Server.
This guide assumes that you possess the following knowledge and skills:
• An understanding of Content Server's purpose within your organization and

how it will be used.
• Familiarity with each server operating system and any legacy products or
systems that will be integrated with Content Server.
• Web server administration skills.
• Familiarity with Java application servers and servlets.
• Database administration skills (or a database administrator to assist you).
i.ii Documentation conventions

User interface
This format is used for elements in the graphical user interface (GUI), such as
buttons, names of icons, menu items, and fields.
Filenames, commands, and sample data

This format is used for file names, paths, URLs, and commands at the command
prompt. It is also used for example data, text to be entered in text boxes, and
other literals.
Note: If you copy command line examples from a PDF, be aware that PDFs
can contain hidden characters. OpenText recommends that you copy from
the HTML version of the document, if it is available.
KEY NAMES
Key names appear in ALL CAPS, for example:
Press CTRL+V.
LLESCOR100012-IGD-EN-1 OpenText Content Server v

Introduction
<Variable name>
Angled brackets < > are used to denote a variable or placeholder. The user
replaces the brackets and the descriptive content with the appropriate value. For
example, <server_name> becomes serv01.
Internal cross-references
Click the cross-reference to go directly to the reference target in the current
document.
External cross-references
External cross-references are usually text references to other documents.
However, if a document is available in HTML format, for example, in the
Knowledge Center, external references may be active links to a specific section
in the referenced document.
Warnings, notes, and tips
Caution
Cautions help you avoid irreversible problems. Read this information
carefully and follow all instructions.
Important
Important notes help you avoid major problems.
Note: Notes provide additional information about a task.
Tip: Tips offer you quicker or easier ways of performing a task.
ii Contact information
OpenText Online (http://online.opentext.com/) is a single point of access for the
product information provided by OpenText. You can access the following support
sources through OpenText Online:
• Communities
• Knowledge Center
OpenText Online Communities ( https://communities.opentext.com/communities/

cs.dll/open/OpenTextOnlineCommunity) provide the following resources:
• Usage tips, help files, and best practices for customers and partners.
• Information on product releases.
• User groups and forums where you can ask questions to OpenText experts.
The OpenText Knowledge Center (https://knowledge.opentext.com) is OpenText's

corporate extranet and primary site for technical support. The Knowledge Center is
the official source for the following:
vi OpenText Content Server LLESCOR100012-IGD-EN-1

Introduction
• Product downloads, patches, and documentation including Release Notes.

• Discussion forums, Online Communities, and the Knowledge Base.
• OpenText Developer Network (OTDN), which includes developer
documentation and programming samples for OpenText products.
If you need additional assistance, you can find OpenText Corporate Support
Contacts at http://support.opentext.com/.
LLESCOR100012-IGD-EN-1 Installation Guide vii

Chapter 1
Installing Content Server
OpenText Content Server is the leading collaboration and enterprise content

management (ECM) system for global organizations. It provides a single,
comprehensive solution for managing information and makes collaboration a part of
every business process, even across organizational and geographic barriers. Content
Server brings together employees across your organization, as well as partners and
customers throughout your business community.
Content Server is immediately deployable, out of the box. Its standards-based, open
architecture allows Content Server to integrate seamlessly with multiple platforms,
information repositories, third-party applications, and legacy systems. Its modular
design provides your organization with the highest levels of scalability, extensibility,
accessibility, and security. And, because it is entirely web-based, end users need
only a web browser to use it.
This chapter covers the following topics:

• “Installing Content Server” on page 9
• “Upgrading Content Server and Installing Updates” on page 10
1.1 Installing Content Server

This guide explains how to install and configure Content Server in chronological
order from the perspective of a person who is installing Content Server for the first
time.
In general terms, installing Content Server involves the following steps:
1. Choosing the operating system, relational database management system and

web server (or web application server) that you wish to use in your Content
Server environment, and planning the architecture or your Content Server
system. For information on this stage of the installation, see “Designing Your
Content Server System“ on page 11.
2. Preparing the Content Server environment. Installing a web server or web
application server. Installing a database. Creating operating system users. For
information on this stage of the installation, see “Preparing to Install Content
Server“ on page 27.
3. Running the Content Server installation program. For information on this stage
of the installation, see “Installing Content Server on Windows“ on page 39 or
“Installing Content Server on UNIX and Linux“ on page 43.
4. Configuring Content Server to work with a web server or web application
server, performing the initial installation of optional Content Server modules,
and (optionally) installing additional Admin servers. For information on this
stage of the installation, see “Configuring Content Server“ on page 47.
LLESCOR100012-IGD-EN-1 OpenText Content Server 9

Chapter 1 Installing Content Server
5. Creating a Content Server database. For information on this stage of the

installation, see “Creating the Content Server Database“ on page 77.
6. Configuring the Content Server search environment. For information on this
stage of the installation, see “Completing the Installation and Setup of Content
7. Completing the installation of Content Server optional modules. For information
on this stage of the installation, see “Installing and Uninstalling Modules“
on page 105.
Information on uninstalling Content Server appears in “Uninstalling Content

1.2 Upgrading Content Server and Installing Updates

The information about upgrading Content Server and installing Content Server
Updates is covered in a separate document. If you are upgrading Content Server
from a previous version, see OpenText Content Server - Upgrade Guide (LLESCOR-
IUP).
10 OpenText Content Server LLESCOR100012-IGD-EN-1

Chapter 2
Designing Your Content Server System
Content Server can be deployed in a variety of configurations, ranging from simple

to extremely complex. Therefore, your first step in deploying Content Server is to
carefully plan the design of your system, so that it meets the needs of your users in
the best possible way.
The information in this chapter is intended to help you make important decisions
about how to deploy your Content Server system before you begin to build it.
However, because every Content Server deployment is unique and the potential
variability is wide, the architecture and configuration issues addressed in this guide
are discussed in very general terms. Your specific circumstances may require much
more specific approaches. Contact OpenText Global Services at http://
www.opentext.com/services/ for help with specific system-design issues.

• “About Content Server” on page 11
• “Understanding OpenText Content Server Architecture” on page 17
• “Architecture Configuration Options” on page 18
• “Best Practices for System Design” on page 23
2.1 About Content Server

Content Server is a service that sits between a database and a web server. It manages
data through the database server and relies on the 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.

Chapter 2 Designing Your Content Server System
Figure 2-1: Basic Content Server System
Users interact with Content Server through the web server when using the standard
browser interface, or they may communicate directly with the Content Server using
a desktop application, such as OpenText Explorer.
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 OpenText
Content Server Architecture” on page 17.
2.1.1 Required Third-Party Applications

Note: The version numbers of third-party software that OpenText supports
can change for any new version of Content Server. For more 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® (64–bit)
• Sun SPARC Solaris™ (64–bit)
• Red Hat® Enterprise Linux®
• A relational database management system (RDBMS) serves as the Content Server
data repository. Content Server supports the following databases:

2.1. About Content Server
• Oracle Server®
• Microsoft SQL Server®
Note: If your database resides on a separate computer (recommended

by OpenText), then RDBMS client software is required on the computer
that runs Content Server.
• 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)
• Sun Web Server (on Oracle Solaris)
• Apache™ HTTP Server (on Red Hat)
• Oracle® iPlanet Web Server (on Oracle Solaris)
• An application server that handles client requests for Java-based Content Server
functions. Content Server supports the following application servers:
• Apache™ Tomcat Server
• IBM® WebSphere®
Note: For more information about servlets and application servers, see the
section called “The Content Server Java Framework” on page 15.
• Web browsers on client workstations. Content Server supports the following web
browsers:
• Apple Safari™
• Microsoft® Internet Explorer®
• Firefox™; However, because Firefox does not support ActiveX, you will
encounter limitations in using Firefox with Content Server.
• Google Chrome
• An external file system or other data storage system (optional, but
recommended). For example, the OpenText Content Server – Archive Storage
Provider. See the OpenText Content Server – Archive Storage Provider Installation,
Upgrade and Configuration Guide on the Knowledge Center (https://
This guide includes instruction for configuring third-party components to work with
Content Server. However, you should always refer to the documentation for those
products for complete setup and configuration information.
LLESCOR100012-IGD-EN-1 Installation Guide 13

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.
• the section called “Language Support and UTF-8 Character Encoding”
on page 14
• the section called “XML Support in Content Server” on page 14
• the section called “The Content Server Java Framework” on page 15
• the section called “Document Conversion Service (DCS)” on page 16
• the section called “Content Server Services and Modules” on page 16
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.
In addition to U.S. English (the default), the Content Server GUI is available in:
• French
• German
• Japanese
Previous Western-European releases of Content Server (formerly Livelink ECM

Server) were available in Latin-1 and UTF-8 versions. Previous Japanese versions
were available in Shift-JIS (Content Server 9.2 and earlier) and UTF-8 (Content
Server 9.5.x and 9.7.x).
Content Server is now UTF-8 only, regardless of language.
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, this allows Content Server to easily operate
with external applications that also understand XML, without requiring either party
to understand the specific API of the other system. Content Server incorporates XML
in the following important 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

2.1. About Content Server
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 Open Text
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.
The Content Server Java Framework

Content Server can handle web client transactions on any supported web server
using CGI and, on Microsoft Internet Information Services, using ISAPI and
ASP.NET. It can also respond to user requests using a servlet.
A servlet is a Java object that processes requests and generates dynamic content and
responses, providing an environment for Java code to run in cooperation with a web
server. Java servlets offer some advantages over CGI, including security and the
wide acceptance and use of standard Java APIs.
Servlets are run and managed by a process called a servlet container. An application
server is a set of additional features and capabilities packaged with a servlet
container.
To integrate Java functionality into OScript-based Content Server, Content Server

has a Java framework that duplicates the Content Server framework. The Java
framework in Content Server is made up of Java packages and classes that run
within a JVM inside the llserver process. A request dispatcher is used to analyze
incoming requests and route them to the appropriate framework.
Content Server's Java functionality is delivered as an expanded web application,

which means that it is extracted from a Web Archive (WAR) file into a folder.
Deploying Content Server as an expanded web application allows Content Server to
be more easily patched, because it allows OpenText to replace selected elements
instead of having to replace the entire WAR file. It also makes it less likely that a

patch will overwrite any customizations you may have made to your Content Server
system.
Note: If you intend to use the IBM WebSphere application server, the
application must be packaged as a WAR file. It is subsequently extracted by
WebSphere. See “Deploying LLServlet on IBM WebSphere” on page 56
To use Content Server features written in Java, you must add an application server
to your Content Server system configuration. See “Configuring the Access Tier”
on page 30
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 98.
Content Server Services and Modules

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

Server functionality and serves all pages of the Content Server interface through
the web server.
• The Content Server Admin service (admserv[.exe]) handles the processes that
are associated with indexing and searching the Content Server database and the
memcached processes associated with Faceted Browsing.
Content Server features are divided into core modules that deliver the product's
basic functionality (such as document management) and optional modules, which
add such capabilities as electronic forms management or email integration.
Note: Optional modules, which are sold separately, are developed by

OpenText, third parties, or even your own organization. You create Content
Server modules without modifying the objects that are contained in any other
Content Server module. This modularity lets you 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 OpenText Content Server Architecture
2.2 Understanding OpenText 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. In addition, Content Server's open architecture allows external
applications to interact with Content Server services using Content Web Services.
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 ensure that only authorized
personnel can access information. 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.
Note: To deliver Java-based Content Server features, you must add an

application server to your Content Server system configuration. See the section
called “The Content Server Java Framework” on page 15.
2.2.2 Application Tier

The Application Tier provides a high level of performance because of its
multithreaded 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. 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. OpenText Content Server Builder and Content Server SDK
products 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),
plus 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, Lotus Notes™ repositories, and other
enterprise business systems.
2.3 Architecture Configuration 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. 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 (which is
sometimes referred to as 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

2.3. Architecture Configuration Options
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.
Scaling Content Server to meet increased demand is simply a matter of adding

resources. It is never necessary to start 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 a
dedicated server, 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. SANs have become a common
component of enterprise storage systems.)
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.
As the system grows further, the Admin server begins to require more resources.
The next step of the scaling path is to move the Admin server and its managed
processes to a dedicated computer.
This architecture employs a dedicated Admin server to run the Enterprise search
infrastructure on a separate computer. In particular, this architecture improves
search performance by running the Content Server processes that handle search and
update requests on a separate computer. This also gives the Content Server more
resource to handle the operations for which it is responsible, 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, the
computer on which the Content Server service runs is known as the Content Server

host , the first Admin server is known as the primary Admin host), and the computers
on which additional Admin servers run are called secondary Admin host. See
OpenText Content Server Admin Online Help - Search Administration (LLESWBS-H-
AGD).
If you decide to follow this recommendation, you must install and register an
Admin server on each additional computer. To accomplish this, you install Content
Server on a computer as normal, but enable only the Admin server to run on that
computer. See “Registering a Secondary Admin Server” on page 87. For more
information about the tasks involved in installing and setting up an additional
computer, see the following:
• “Performing a Secondary Installation” on page 68

• “Setting Up and Starting the Content Server Services” on page 70
• “Registering a Secondary Admin Server” on page 87
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 the section called “Content Server
Cluster Architecture ” on page 20.
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.

2.3. Architecture Configuration Options
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 Internal and External Document Storage

Content Server can use either internal (database) or external (file system) document
storage for files that users upload.
• 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.
• With external storage, only the metadata is stored in the database; the actual file
is stored on an external file system.
External document storage normally provides faster read performance than internal
document storage. Most implementations (and virtually every production
implementation) of Content Server should use external document storage, but
internal storage can be appropriate for a test or development implementation of
Content Server, containing a small number of documents that are not frequently
accessed.
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.
The fastest external storage option is to store document content on a separate disk
located on the same computer as Content Server and the web server. If you place the
external store on the Content Server computer, writing and retrieving documents
may be slightly faster because there is no network delay. The improvement may be
more significant if the Content Server computer is located on a network that is

typically very busy. In such an environment, you should consider placing the
components of the Content Server system on their own, isolated subnet.
Implications for Backup and Recovery Strategy

Using internal document storage can simplify your backup and recovery strategy
because you can use the tools of your database manager to back up the Content
Server database. 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.
With external storage, your backup and recovery strategy may be more complex,
because of the necessity of synchronizing your database and file store backups. One
option is to take the Content Server database and external document store offline
when you create backups. This has the benefit of creating a static data set and a
backup that is synchronized with the metadata in the Content Server database.
However, taking the Content Server database offline may not be a viable option for
global organizations that must operate 24 hours a day. In this case, more complex
backup and recovery strategies may be necessary. For example, if you back up the
external document store while it is online, you then need to synchronize the backup
of the database with that of the external file store. Since the database can be backed
up incrementally, you should make sure that the external file store is also backed up
as frequently as the database. Otherwise, when restoring the data, the database may
include documents for which no external file exists.
Setting Up an External Document Store

Before you perform the steps to select the external document storage option and
specify the physical path of the external document store, note the following points:
• 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 UNIX
and Linux, use an NFS mount. For Windows, map a drive to the external
document storage folder.
Note: The external folder that you map to must be specified in the External
Document Storage field. See “Configuring Content Server“ on page 47.
• 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 34.

2.4. Best Practices for System Design
• 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 of the basic issues to consider when designing
your system.
To determine the architecture and configuration options that best suit your needs,
you must consider a number of factors:
• The number of named users that will use Content Server
• The anticipated transaction rate
• The amount of data that needs to be stored in the Content Server database
• The presence of legacy systems or applications that need to integrate with
Content Server
• The Content Server hardware environment, including:
• The state of the existing network architecture
• The CPU speed and memory capacity of the various servers
• System storage capacity, speed, and configuration
• Security best practices
Tip: OpenText Professional Services can help you with specific system-design
issues.
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 Dynamic Thread Loading creates the minimum number of
threads when it starts and then creates additional threads, as needed, up to the
maximum number. The default minimum and maximum values are 8 and 32.
However, creation of new threads is a relatively intense and time-consuming
process, so better performance can be obtained by setting Content Server to start
the maximum number of threads your system requires, once you have
determined that number through monitoring and observation.
• You can determine an optimal number of threads for your system to run by
closely monitoring the system and making adjustments as necessary. A
reasonable number to start with is eight threads, which is the default minimum
number. 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 OpenText Content Server Architecture”
on page 17.
• 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

2.4. Best Practices for System Design
Database Recommendations
The Content Server must be stored in a relational database management system
(RDBMS) that is listed as supported in the Content Server Release Notes. Your RDBMS
must be installed for UTF-8 compliance.
Content Server's database schema is normalized, which means that the schema has
been designed to reduce the chance of having multiple versions of the same data.
Indexes are provided out of the box on the columns that Content Server uses in its
standard operations. In some cases, however, it may be helpful to build indexes on
additional database table columns, which will speed up the retrieval of information
from SELECT statements (at the cost of increasing overhead when new information is
added to the table because both the table and the index will have to be updated).
OpenText recommends that you have an experienced database administrator tune

your database to achieve optimum performance, using the monitoring and
performance tools provided by the database vendor. Common database tuning tasks
include:
• Monitoring disk usage to achieve optimum results
• Determining if more memory is needed for caching data tables
• Adjusting temporary tablespace tables and buffers
• Splitting tables, logs, and indexes across multiple disks and controllers
Security Recommendations
For most customers, maintaining the security of your organization's Content Server
system is a primary concern. While there is no single correct way to secure a Content
Server system, the following are some general recommendations by OpenText:
• OpenText recommends that you configure your web server to serve only HTTPS,
refusing incoming HTTP connections, in order to employ data encryption and
client authentication safeguards.
• OpenText strongly recommends that you restrict read permissions on the
<Content_Server_Home>/config/ folder as much as possible. Ideally, the only
user with read access should be the operating-system user created specifically for
the Content Server and, (if applicable), the Admin server. Also, make sure to
disable browsing the <Content_Server_Home>/config/ folder through the web
server running on the Content Server computer.
• For 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 the section called “OpenText Content Server Secure Extranet Architecture
(SEA)” on page 21.
For detailed recommendations on securing your Content Server installation, see

theOpenText Content Server 10.0.0 Application Hardening Guide (https://
knowledge.opentext.com/go/19282871), available in the Champion Toolkit (https://

knowledge.opentext.com/go/Champion_Toolkit) on the OpenText Knowledge

Center

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.

• “Installation Worksheets” on page 27
• “Configuring the Access Tier” on page 30
• “Installing a Database Server” on page 31
• “Creating an Operating System User” on page 34
• “Setting Up Client Web Browsers” on page 35
3.1 Installation Worksheets

This section contains worksheets on which you can record the user names,
passwords, and other important information required for the installation of Content
Server and its supporting software.
Note: Fields marked with an asterisk (*) represent information you need
before you install Content Server. You generate the information in the other
fields as you install and set up Content Server.
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.
3.1.1 Database Installation Worksheets

Table 3-1: Oracle Database Worksheet
Parameter Default Your Information

Oracle system user name system *
Oracle system password *
Service name (database alias) *
Oracle SID or Oracle HOME directory *
(UNIX/Linux only)
Tablespace name

Chapter 3 Preparing to Install Content Server

Absolute path of tablespace file
Oracle user name used to access the Content
Server database
Password of Oracle user used to access the
Content Server database
Table 3-2: Microsoft SQL Server Worksheet (Windows only)

SQL Server alias *
System administrator user name sa *
System administrator password *
System database master.dat *
Log file name
Absolute path of log file
Data file name
Absolute path of data file
Name of SQL database containing the
Content Server database tables
Microsoft SQL user name used to access the
Content Server database
Password of the Microsoft SQL user used to
access the Content Server database
3.1.2 Web Server Worksheets

Table 3-3: Microsoft Internet Information Server Worksheet (Windows only)

TCP port number 80 *
Table 3-4: Oracle iPlanet Web Server Worksheet

Administration server port number *
Administration server access URL *
Administration access user name admin *
Administration access password *

3.1. Installation Worksheets

Web server port number 80 *
Oracle Solaris user created to run the web
server
Password for Oracle Solaris user created to
run the web server
3.1.3 Content Server Installation Worksheets

Table 3-5: Content Server Installation Worksheet

Windows or UNIX/Linux user created to run the
Content Server
Password for the Windows or UNIX/Linux user
created to run the Content Server
Content Server Windows service name and URL OTCS
prefix (virtual folder alias) of
<Content_Server_Home>/cgi/ folder
(Windows only)
URL prefix (virtual directory alias) of contentserver
<Content_Server_Home>/cgi/ directory
(UNIX/Linux only)
URL prefix (virtual folder alias) of img
<Content_Server_Home>/support/ folder
Content Server port number 2099
Admin server port number 5858
Java RMI port number 1099
Administrator password (used to access the livelink
Content Server Administration page)
Password for the Admin user livelink
Note: The 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).
Table 3-6: Additional Content Server Installation Worksheet

Host name of additional Content Server
computer


Content Server service name (Windows only)
Admin server port number 5858
Password of Admin server
3.2 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.2.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.
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.3. Installing a Database Server
3.3 Installing a Database Server

Content Server uses third-party database software to create and manage the Content
Server database. You can use supported versions of Oracle Database or Microsoft
SQL Server. Microsoft SQL Server is available only for Windows operating systems.
Note: 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.
This guide provides guidelines to help ensure that you select the 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.
• “Oracle Database Installation Guidelines” on page 31
• “Microsoft SQL Server Installation Guidelines” on page 33
3.3.1 Oracle Database Installation Guidelines

The Oracle Database installation guidelines vary depending on whether you install
Oracle Database on Windows, UNIX or Linux. Choose the guidelines that apply to
your installation.
• the section called “Oracle Database Installation Guidelines for Windows”
on page 31
• the section called “Oracle Database Installation Guidelines for UNIX and Linux”
on page 32
Oracle Database Installation Guidelines for Windows

Note the following when installing and configuring Oracle Database on Microsoft
Windows:
• 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.
• If you install the database software 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 is set up to
communicate in 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 3-1: “Oracle Database
Worksheet” on page 27. 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 UNIX and Linux

Note the following when installing and configuring Oracle Database on UNIX or
Linux:
• To install Oracle Database on supported UNIX or Linux operating systems, you

must be logged in as the superuser 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.
• If you install the database software 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 is set up to
communicate in 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.

3.3. Installing a Database Server
• Record the Oracle HOME folder or the Oracle SID on Table 3-1: “Oracle Database
Worksheet” on page 27. 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 3-1: “Oracle Database
Worksheet” on page 27. 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.3.2 Microsoft SQL Server Installation Guidelines

Note the following when installing and configuring Microsoft SQL Server:
• Select the Typical installation option, and accept default settings during the
installation.
• Record the master device file name (default is master.dat) on Table 3-2:
“Microsoft SQL Server Worksheet (Windows only)” on page 28.
• During the installation, the system user name and password do not appear. By
default, the system user name is sa. Record this information on the Microsoft
SQL Server Worksheet.
• To connect to Microsoft SQL Server, Content Server requires that the MSSQL
Server service be running.
• 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, you must install a
Microsoft SQL Server client on the Content Server computer.

3.4 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, UNIX, or Linux user. For a first-time installation,
OpenText recommends that you create these operating-system users.
Note: In a single-computer Content Server configuration, it is not necessary to

create Windows users to manage servers. However, when dealing with
multiple instances of Content Server (in a Content Server cluster environment,
for example) you may want to create specific users to manage certain
functions, such as performing searches or managing system administrative
duties.
3.4.1 Creating a Windows User

You must create a Windows user to run the Admin server on the Content Server
computer and all additional computers.
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.
Note: Use an identical Windows user to run all Content Server services on the
Content Server computer and each additional computer. For more information
about assigning user names to Content Server services, see “Setting Up and
Starting the Content Server Services” on page 70. Also, if you are using an
external document store on an additional computer, create an identical user on
that computer to own the external document folder.
Create one or more Windows users to run the Content Server and the web server.
Each user must:
• Be a member of the Administrators group

• Have the Log On As A Service right
• Have a password set to never expire
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)

3.5. Setting Up Client Web Browsers
Record the name and password of the Windows user that you create for Content
Server on Table 3-5: “Content Server Installation Worksheet” on page 29.
3.4.2 Creating a UNIX or Linux User

You need to create UNIX or Linux user accounts with appropriate profiles to run the
web server and Content Server. You can use the same UNIX or 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 UNIX or 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 UNIX user account, you must log in to the Content Server computer as
the superuser root.
Tip: Use the same UNIX 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.
Record the name and password of the UNIX or Linux user that you create for
Content Server on Table 3-5: “Content Server Installation Worksheet” on page 29.
Record the name and password of the Oracle Solaris user that you create for Oracle
iPlanet Web Server on Table 3-4: “Oracle iPlanet Web Server Worksheet” on page 28.
3.5 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-7: “Common Issues When
Opening Documents from Content Server” on page 36 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 36.
• 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.5.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-7: 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.

3.5. Setting Up Client Web Browsers
Issue ... This happens when ...

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
Installing Content Server on Windows
This chapter describes how to perform a Content Server installation on computers

running Windows 2008 Server (64–bit).
Note: For specific platform versions, see the Content Server Release Notes for the
version 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. 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 27.
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.

When you use the Content Server installer, choose the Install a new instance option
to proceed with a Content Server installation.
To install Content Server 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 executable file and then click Run 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, or
click Browse to select a different folder, and then click Next.
e. In the Content Server Configuration dialog box, do the following, 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.

Chapter 4 Installing Content Server on Windows
Note: The service name you provide appends to the server entries
for 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 Service of the Content Server computer.
Use the format <host.domain.suffix> (for example,
intranet.yourdomain.com).
You must provide the fully qualified DNS name if any of your users
want 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. Without the fully qualified DNS name,
these links may not work for remotely connected users.
Tip: To look up the DNS name if you have a static IP address, type
nslookup<hostname> at the Windows command prompt.
• In the HTTP Server Name box, type the host name of the computer on
which the web server resides, or accept the default value.
Note: OpenText recommends using the default value, localhost

because Content Server and the web server must reside on the
same computer. Do not change the default value if the computer
on which you are installing Content Server 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 Content Server Mapping dialog box, accept the default URL prefix (/
img/) for the support folder, or type a new prefix in the URL Prefix box,
and then click Next.
Note: Creating a mapping with few characters improves page size

performance and renders pages faster on the client.
If you change the URL prefix, remember that it must begin and end
with a forward slash (/), must contain only alphanumeric characters,
and must not contain spaces.
g. In the Port Configuration for Content Server window, do the following,
and then click Next:
• In the Service Port box, type an unused port number for the Content
Server service. Valid port numbers range from 1025 to 65535. The
default is 2099.

4.1. Installing Content Server
• In the Admin Port box, type an unused port number for the Admin
server service. Valid port numbers range from 1025 to 65535. The
default is 5858.
• In the RMI Port box, accept the default port number or type a new port
number to be used by RMI to obtain client sockets for RMI calls.
Note: The next consecutive port number must be available for

RMI to use.
If you have multiple instances of Content Server on the same
computer, the RMI registry port must be unique for each instance.
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. This is only
applicable to installations using IIS 7.0.
h. Microsoft Windows Installer (MSI) 2.0 is required to install Visual C++. If
the Content Server computer does not have MSI 2.0 installed, the Content
Server installation program will prompt you to install both the Visual C++
redistributable and MSI upgrade. Both components are packaged with the
Content Server installer.
Note: If the version of Windows on the Content Server computer

includes a Microsoft Installer package that is not recent enough to
install the VC8 Redistributable package, an error will occur. The
workaround for this situation is to manually run the two executables
after the installation program completes. To do this, navigate to the
<Content_Server_Home>/installers/ folder. Then, run the
executable to update the Installer Tool: InstMsiW.exe. Finally, run
the executable to update the Visual C++ Libraries:
vcredist_x86_all.exe.
i. In the Ready to Install dialog box, click Install.
j. When the installation is complete, clear Start Services, 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 that you need to map when you
configure your web server or application server. The mappings.tbl
file is available to view at any time in your <Content_Server_Home>
folder.
k. Click Finish.
Important
Do not start the Content Server services at this point. Apply any
required Updates and Hotfixes first.

Chapter 4 Installing Content Server on Windows
3. Apply the latest Content Server Update, if your Content Server installation file
does not already integrate the latest Update.
4. Apply any required Hotfixes. If there is more the one Hotfix, apply each one in
ascending numerical order. Extract the contents of each Hotfix file into the
<Content_Server_home> folder (C:\OPENTEXT, by default), overwriting any files,
as necessary.
5. Set up and configure the virtual folders for the Content Server web server.
Follow the instructions at “Mapping Content Server URL Prefixes in a Web
Server” on page 60, and then continue to the next step.
6. Set the Content Server Services permissions.

Follow the instructions at the section called “Setting Up and Starting the
Content Server Services on Windows” on page 71, and then continue to the
next step.
7. Start the Content Server services and continue the Content Server installation.
8. Open Content Server and perform the initial configuration.
a. From the Start menu, click OpenText Content Server (OTCS), and then
click Content Server Administration.
b. On the Configure Server Parameters page, type the administrator password
in the Administrator Password and Verify Password boxes.
Note: You should change the Admin password after the initial sign in
to Content Server.
c. In the License Key section, type the company name, license expiration date,
and number of users the license is for, as provided by OpenText, in the
appropriate boxes.
d. Modify any of the other available settings, or accept the default values, and
then click the Save Changes button. For information about the additional
settings, see “Configuring General Settings” on page 74.
e. On the Select Default Metadata Language page, select the language you
want to use with Content Server from the drop-down list and then click
Continue.
f. Proceed to Chapter 7, “Creating the Content Server Database“ on page 77.

Chapter 5
Installing Content Server on UNIX and Linux
This chapter describes how to install Content Server on computers running

supported versions of UNIX and Linux operating systems.
Before you install Content Server, you must create a UNIX/Linux user to run the
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 27.
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, you must 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 data-flow processes,
search servers, and index servers associated with each existing Content Server
installation are running. See System Object Administrator in the Content Server
Administrator Online Help.

When you use the Content Server installer, choose the Install a new instance option
to proceed with a Content Server installation.
Tip: As you complete these installation procedures, be sure to record directory

paths, port numbers, and other information on Section 3.1.3: “Content Server
Installation Worksheets” on page 29.
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, you should not do so. Press
CTRL + C to exit the installation program if your database is not properly
installed and configured.
To install Content Server on UNIX/Linux:
1. Log in as the UNIX or Linux user that you want to run the Content Server. See
“Creating a UNIX or Linux User” on page 35.
2. For the version of UNIX/Linux you are running, unzip and unpack the setup
utility into the appropriate directory.
3. Type ./setup, and then press ENTER.

Chapter 5 Installing Content Server on UNIX and Linux
4. Type Y to accept the license agreement.
5. At the prompt that asks about the installation directory, do one of the following:
To accept the default installation directory, press ENTER.
To specify a different directory, type the absolute path of the installation
directory, and then press ENTER.
6. If the directory you specified in step 5 does not exist, type Y at the prompt that
asks whether you want to create it.
7. At the prompt that asks if you want to install Content Server, type Y.
8. At the prompt that asks you for the port number on which you want the
Content Server to run, type a number between 1025 and 65535, or accept the
default number, 2099.
Tip: The port number you choose must not be in use by any other process.
To find out what port numbers are currently in use on a given computer,
use the command netstat –a.
9. At the prompt that asks you to specify the RMI port number, type a number or
accept the default value, 1099.
Note: The next consecutive port number must be available as well.
10. At the prompt that asks you for the port number on which you want the Admin
server to run, type a number between 1025 and 65535, or accept the default,
5858.
11. At the prompt that asks you for the default URL prefix for the
<Content_Server_Home>/cgi/ directory, type the prefix or accept the default
prefix, OTCS.
If you have multiple instances of Content Server on the same computer, the RMI
registry port must be unique for each instance.
12. At the prompt that asks you to specify a temporary directory for document
conversion, type the absolute path of the 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.
13. At the prompt that asks if you will be using an Oracle database, type Y.
14. At the prompt that asks you to specify the Oracle SID or the Oracle HOME
directory, accept the default value, ORCL, or specify the SID or alternate HOME
directory.
15. If you specified a nonexistent Oracle HOME directory in the previous step, the
installation program asks you to verify that you still want to use the supplied
value.

5.1. Installing Content Server
16. After the core Content Server software installs, the installation program asks
whether you want to start the Content Server. Type Y to start the service.
17. Proceed to Chapter 6, “Configuring Content Server“ on page 47.

Chapter 6
Configuring Content Server
After you install Content Server, you must map two Content Server folders to your
web server and configure your Content Server system.
• “Deploying and Configuring LLServlet” on page 47

• “Mapping Content Server URL Prefixes in a Web Server” on page 60
• “Installing Optional Content Server Modules: Stage 1” on page 66
• “Performing a Secondary Installation” on page 68
• “Setting Up and Starting the Content Server Services” on page 70
• “Configuring General Settings” on page 74
6.1 Deploying and Configuring LLServlet

Adding an application server to your Content Server system configuration allows
you to deploy Content Server using LLServlet and to deliver Java-based Content
Server features. If you do not use an application server, you can still deploy Content
Server using CGI, ISAPI or ASP.NET, but you cannot use Content Server's Java-
based features.
Note: The instructions in the chapter presume that you have already installed
an application server listed as Supported or Certified in the Content Server
Release Notes.
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 it 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 Content Server Normally using LLServlet ” on page 48

Chapter 6 Configuring Content Server
In this deployment, Content Server is installed with an application server and

deployed using LLServlet, instead of CGI, ISAPI or ASP.NET. This deployment
uses at minimum a single Content Server host.
• “Deploying Content Server in a Secure Extranet Architecture using LLServlet”
on page 49
In this deployment, a Content Server servlet client accesses a full installation of
Content Server on a separate computer. 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
Typically, the two computers are separated by a firewall.
6.1.1 Deploying Content Server Normally using LLServlet

To configure a basic Content Server deployment Content Server using LLServlet,
you create two XML context files: one for LLServlet and the other for the Content
Server support folder.
To create the Content Server XML context files:
Note: Entries in the XML context files are case-sensitive.
Replace variable names, such as <Content_Server_Home> and <Content Server

virtual folder name>, 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. Create a file named <context_name>.xml using the following sample XML

code.
Tip: For a default installation of Content Server, name this file OTCS.xml.
<?xml version="1.0" encoding="utf-8"?>

<Context
displayName="Content Server 10"
docBase="<Content_Server_Home>\application\"
path="/<Content Server virtual folder>"
reloadable="false"
swallowOutput="true"
workDir="work\Catalina\localhost\<Content Server virtual
folder name>">
<Logger
className="org.apache.catalina.logger.FileLogger"

6.1. Deploying and Configuring LLServlet
prefix="<Content Server virtual folder name>"

suffix=".txt"
timestamp="true">
</Context>
2. Save this file in the <TOMCAT_HOME>\conf\Catalina\localhost\ folder.

3. Create a file named <context_name>support.xml using the following sample
XML code.
Tip: For a default installation of Content Server, name this file

OTCSsupport.xml.

<Context
displayName= "Content Server 10"
docBase="<Content_Server_Home>\support\"
path="/<Content Server virtual folder>"
reloadable="false"
workDir="work\Catalina\localhost\<Content Server virtual
folder name>">
<Logger
prefix="<Content Server virtual folder name>"
suffix=".txt"
timestamp="true">
</Context>
4. Save this file in the <TOMCAT_HOME>\conf\Catalina\localhost\ folder.

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

8080/<context_name>/livelink. The Content Server logon page should appear.
Tip: If the logon page appears, but has no images, verify that the
<context_name>support.xml file is correctly configured.
6.1.2 Deploying Content Server in a Secure Extranet

Architecture using LLServlet
For a secure deployment, you 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.
Note: The following procedure presumes that you have already installed
Content Server on the Content Server host.
To configure a secure Content Server deployment using LLServlet:
1. Create the <Content_Server_Home> folder on the servlet client host.

2. Create the following subfolders on the servlet client host:

• <Content_Server_Home>/temp/
• <Content_Server_Home>/viewcache/
• <Content_Server_Home>/config/
• <Content_Server_Home>/filters/
• <Content_Server_Home>/logs/
3. Copy the <Content_Server_Home>/application/ folder from the Content

Server host to the <Content_Server_Home> folder on the servlet client host.
4. Copy the <Content_Server_Home>/support/ folder from the Content Server

host to the <Content_Server_Home> folder on the servlet client host.
5. Copy the following files from the <Content_Server_Home>/config/ folder on

the Content Server host to the <Content_Server_Home>/config/ folder on the
servlet client host.:
• javaserver.stubs.xml
• javaserver.login.config
• view.tpt
6. Modify the following opentext.ini file and save it on the servlet client host in
the <Content_Server_Home>/config/ folder:
• 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.
To verify the correct value, open the Content Server Administration page,
and then click the Specify Server Port link in the Server Configuration
section.
• In the filters section, replace <Content_Server_Home> with the
<Content_Server_Home> folder on the servlet client host.
• 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 hostname 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 the Content 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=<Content_Server_Home>
UploadDirectory=<Content_Server_Home>\temp\
htmlImagePrefix=<corresponding value from Content Server host>
useStreaming=TRUE
Debug=11
[security]
Authentication=Livelink
[filters]
tptFile=<Content_Server_Home>\temp\config\view.tpt
cachePath=<Content_Server_Home>\viewcache\
lastIdFile=<Content_Server_Home>\viewcache\lastid.dat
filterPath=<Content_Server_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=<Content_Server_Home>\filters\viewcache\
cachesize=10
[DCSParameters]
HHdefaulttype=ANSI8
HHhtml=generic
HHgraphics=none
HHinterlace=False
HHquality=100
HHgraphicsizemethod=smooth
HHtimeout=280
HHgraphicoutputdpi=70
Pipeline=View
7. Open the <Content_Server_Home>\application\WEB-INF\web.xml file and

modify the path of the opentext.ini so that it points to the
<Content_Server_Home>\config\ folder on the servlet client host.

Note: The path to the opentext.ini file is referenced four times in the
web.xml file. All four locations must point to the location of the
opentext.ini file on the servlet client host.
8. To enable document uploads, complete the following steps:
• Ensure that the Secure Enterprise Architecture Support Module is installed

on the Content Server host.
• Set useStreaming=TRUE in the [general] section of the opentext.ini file
on the servlet client host.
Tip: For more information on file streaming, see “Document File

Streaming Option” on page 55.
• Include the IP addresses of localhost, the Content Server host, and the
servlet client host in the value of the CGIHosts parameter in the
opentext.ini file on the Content Server host.
Tip: If IPv6 is used in the Content Server environment, the format of

the IP addresses should have the following appearance:
CGIHosts=::ffff:127.0.0.1,....
9. Create the Content Server XML context files. For more information, see “To
create the Content Server XML context files:“ on page 48.
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:
• LLServlet-related parameters specified in the opentext.ini file do not
contain unnecessary white space characters. For example, the following
parameter will prevent LLServlet from initializing because of the space after
the equals sign (=):
OTHOME= C:\OPENTEXT\SEA\
• All folders are specified with a trailing slash character. For example, the
following parameter will prevent LLServlet from initializing because it does
not have a slash character after SEA:
OTHOME=C:\OPENTEXT\SEA
• The Content Server application folder contains all of the following folders:
• application
• config
• filters
• logs
• support

• temp
• viewcache
6.1.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, and that the IP
address of the Content Server host is 10.20.30.40.
Example 6-1: Servlet Client Host opentext.ini File

[general]
Port=2099
Server=10.20.30.40
Logpath=.\logs\
OTHOME=C:\OPENTEXT
UploadDirectory=C:\OPENTEXT\temp
[filters]
tptFile=C:\OPENTEXT\config\view.tpt
cachePath=C:\OPENTEXT\viewcache\
lastIdFile=C:\OPENTEXT\viewcache\lastid.dat
eraseNo=10
autoRecMimeTypes=application/octet-stream
relativeLinkMimeTypes=text/html,application/pdf
[XML]
LogPath=C:\XMLlogs\
[Locale]
Default=_en_US
_en_US=1
[client]
ReceiveBeforeSend=TRUE
[servlet]
wantStreamLogs=FALSE
[ExternalDCS]
host=10.20.30.40
port=5863
viewcache=C:\OPENTEXT\viewcache
cachesize=10
[DCSParameters]
HHdefaulttype=ANSI8
HHhtml=generic
HHgraphics=none
HHinterlace=False
HHquality=100
HHgraphicsizemethod=smooth

HHtimeout=280
HHgraphicoutputdpi=70
Pipeline=View
[JavaModulesConfig]
rmiPort=1099
baseURL=/OTCS/livelink
urlPath=/OTCS
The following sample LLServlet context files for the servlet client host presume that
you have used the default installation settings of Content Server.
Example 6-2: Servlet Client Host OTCS.xml(LLServlet Context) File

<Context
displayName="Content Server 10"
docBase="C:\OPENTEXT\application\"
path="/OTCS"
reloadable="false"
workDir="work\Catalina\localhost\OTCS">
<Logger
prefix="OTCS"
suffix=".txt"
timestamp="true">
</Context>
Example 6-3: Servlet Client Host OTCSsupport.xml(Content Server

Support Folder Context) File
<Context
displayName= "Content Server 10"
docBase="C:\OPENTEXT\support\"
path="/OTCSsupport"
reloadable="false"
workDir="work\Catalina\localhost\OTCSsupport">
<Logger
prefix="OTCSsupport"
suffix=".txt"
timestamp="true">
</Context>

6.1.4 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, change the value of the useStreaming parameter in the

[general] section of the servlet computer's opentext.ini file to TRUE. When
enabled, 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.
You must add the following line to the [Filters] section of the SEA opentext.ini:
filterPath=xxxx, where xxxx is the path to the filters folder for the Content
Server installation.
Streaming File Uploads

Streaming file uploads 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 computer where streamed files are to be stored during the upload
operation. In the [general] section, of the opentext.ini file of the servlet
computer, add the following line:
UploadDirectory=<full_path_to_directory>

Streaming Document Conversion

When streaming is enabled, all browser client requests to view a document as
HTML are retrieved from Content Server by the servlet through streaming. Content
Server 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 requesting
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.
6.1.5 Deploying LLServlet on Apache Tomcat

To configure Apache Tomcat to work with Content Server, you must create two
context XML files (one for the CGI or servlet, and one for the support files), to the
<TOMCAT_HOME>/conf/Catalina/localhost/ folder.
For instructions on adding the context files, see “To create the Content Server XML
context files:“ on page 48.
Note: Each time you apply a cumulative patch or a filter patch update, 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.
6.1.6 Deploying LLServlet 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. Create the following subdirectories under the <Content_Server_Home>

directory:
/config
/filters
/logs

/support
/temp
/viewcache
/WEB-INF
3. Access the WebSphere Administrative console.
4. Expand the Applications menu, and then click Install New Application.
5. Select Local file system or Remote file system and then type the path to the
WAR file in the associated field.
6. 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.

7. Click Next.
8. When the page refreshes, select Generate Default Bindings, and then click
Next.
9. When the page refreshes, leave the default settings and click Next.

10. 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.
11. 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.
12. On the Summary page, click Finish.
13. 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.
6.2 Mapping Content Server URL Prefixes in a Web

Server
After you complete the basic Content Server installation, you must map URL
prefixes (virtual directory aliases) on a 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 “Deploying and Configuring LLServlet” on page 47
• For Windows versions of Content Server, the mappings.tbl file that is generated
at the end of the primary Content Server installation contains the URL prefix
mappings for your web server for Content Server's <Content_Server_Home>/
cgi/ and <Content_Server_Home>/support/ folders.
After Content Server is installed on the server, you will need to open the
mappings file. This file is located in the root of the Content Server install
directory. By default, this location is C:\OPENTEXT\ (in Windows).
• For UNIX or Linux versions of Content Server, the URL prefix mappings are
written to the screen at the end of the Content Server installation.
Note: The <Content_Server_Home>/support/ directory should have Read

permission.
The <Content_Server_Home>/cgi/ directory should have Read,Run, and

Execute permissions.
6.2.1 Mapping Content Server URL prefixes in Microsoft

Internet Information Services
Complete the following procedure to map Content Server URL prefixes in Microsoft
Internet Information Services.
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:

6.2. Mapping Content Server URL Prefixes in a Web Server
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.

6.2. Mapping Content Server URL Prefixes in a Web Server
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.
6.3 Configuring Microsoft IIS Request Filtering for

Use with Content Server
Request Filtering is a security feature of Microsoft Internet Information Services 7
and later that restricts the types of HTTP requests that IIS handles. It replaces much
of the functionality that was available through the UrlScan add-on for IIS 6.0.
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:

6.3. Configuring Microsoft IIS Request Filtering for Use with Content Server
OpenText recommends that you configure Request Filtering as follows:
Allow High Bit Characters

Content Server uses the UTF-8 character set, so Allow high-bit characters must
be enabled.
HTTP Verbs
If you do not enable 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
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.
Maximum Allowed Content Length

The default value of 30000000 bytes means that documents that are larger than
28 MB cannot be uploaded to or downloaded from Content Server. You should
set the number to whatever you want the limit to be in your Content Server
environment.
6.4 Installing Optional Content Server Modules:

Stage 1
You can install optional modules at any time, even after the initial installation of
Content Server. However, if you have optional modules (such as Content Server
Explorer or Content Server Forms) that you intend to use with Content Server, it is
most efficient to install them at this point of an initial Content Server installation.
If you do not have optional Content Server modules to install, proceed to one of the
following sections:
• If you want to set up a secondary Content Server host, proceed to “Performing a
Secondary Installation” on page 68.
• If you do not want to set up a secondary Content Server host, proceed to “Setting
Up and Starting the Content Server Services” on page 70.
Note: You may receive an optional Content Server module on a CD-ROM, or

you may download it from an OpenText website. In either case, specific
instructions for installing the module will accompany it.
You install a module in two stages:

• First, you load the module software components into the
<Content_Server_Home>/staging/ folder of your new Content Server
installation.
• Next, you instruct Content Server to move the module from the
<Content_Server_Home>/staging/ folder and integrate it into the Content
Server system.

6.4. 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 85.
Depending on the operating system on which Content Server is running, proceed to

one of the following sections:
• “Installing Modules on Windows” on page 67
• “Installing Modules on UNIX/Linux” on page 68
6.4.1 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 85.
7. Do one of the following:

If you want to set up a secondary Content Server host, proceed to “Performing a
If you do not want to set up a secondary Content Server host, proceed to
“Setting Up and Starting the Content Server Services” on page 70.

6.4.2 Installing Modules on UNIX/Linux

For UNIX/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/
group that you use for running Content Server.
To install a Content Server module on UNIX/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 85.

If you want to set up a secondary Content Server host, proceed to “Performing a
If you do not want to set up a secondary Content Server host, proceed to
“Setting Up and Starting the Content Server Services” on page 70.
6.5 Performing a Secondary Installation

If you decide to maintain all your indexes on the Content Server host, you do not
require a secondary (additional) installation. However, it is recommended that you
create indexes on one or more secondary hosts. If you decide to do so, you must
perform each secondary installation at this point. Otherwise, proceed to “Setting Up
and Starting the Content Server Services” on page 70.
Performing a secondary Content Server installation is virtually identical to

performing a primary installation. The difference is that, once you have completed
the installation, you must disable the Content Server on the secondary host. The
secondary computer should run only the Admin server and optionally the Extractor
and Importer processes.
Note: This guide is structured so that you install a secondary Content Server
host at the proper time during a first-time installation of your overall Content

6.5. Performing a Secondary Installation
Server system. You can use the following procedures to perform a secondary
Content Server installation at any time after the initial setup of your Content
Server system. If you are doing so, you must also:
• Set the startup options of the Admin server on the secondary Content Server
host, as described in “Setting Up and Starting the Content Server Services”
on page 70.
• Register the Admin server on the secondary Content Server host, as
described in “Registering a Secondary Admin Server” on page 87.

• “Secondary Content Server Installations on Windows” on page 69

• “Secondary Content Server Installations on UNIX/Linux” on page 70
6.5.1 Secondary Content Server Installations on Windows

On the secondary Content Server host, you must map/mount the drive on the
Content Server host on which Content Server is installed. Record the host name,
service name, Admin server port number, and Admin server password for the
secondary Content Server host on Section 3.1.3: “Content Server Installation
Worksheets” on page 29.
To perform a secondary installation on Windows:
1. On the host computer that you want to make a secondary Content Server host,
log in as a user that belongs to the Administrators group.
2. Install Content Server as described previously in this guide, but do not start the
services.
3. Right-click the My Computer icon on your desktop, and then choose Manage.
4. In the left pane of the Computer Management window, expand the Services
and Applications node, and then click Services.
5. Double-click Services.
6. In the right pane, right-click the name of the Content Server, and then choose
Properties.
7. In the Startup type drop-down list, click Disabled.
8. Click OK.
9. Repeat this procedure on each computer that you want to set up as a secondary
Content Server host.
10. Proceed to “Setting Up and Starting the Content Server Services” on page 70.

6.5.2 Secondary Content Server Installations on UNIX/Linux

On the secondary Content Server host, you must map/mount the drive on the
Content Server host. Record the host name, service name, Admin server port
number, and Admin server password for the secondary Content Server host on
Section 3.1.3: “Content Server Installation Worksheets” on page 29.
To perform a secondary installation on UNIX/Linux:
1. On the host computer that you want to use as a secondary Content Server host,
log on with the user name that the Content Server service uses.
2. Install Content Server as described previously in this guide, but do not start the
services.
3. At the operating system prompt, change to the directory where Content Server
is installed, and then type ./stop_llserver.
4. At the operating system prompt, type ./start_lladmin.
5. Repeat this procedure on each computer that you want to set up as a secondary
Content Server host.
6. Proceed to “Setting Up and Starting the Content Server Services” on page 70.
6.6 Setting Up and Starting the Content Server

Services
• “Setting Up and Starting the Content Server Services on Windows” on page 70

• “Setting Up and Starting the Content Server Services on UNIX/Linux”
on page 72
6.6.1 Setting Up and Starting the Content Server Services on

Windows
Before you continue setting up Content Server, you must:
• Set up the two Content Server services on the Content Server host to run as the
Windows user that you created for Content Server.
• Start the Content Server services.
Note: On each Windows computer, use the same user name and password to
run all Content Server services.

6.6. Setting Up and Starting the Content Server Services
Setting Up and Starting the Content Server Services on Windows

To set up and start the Content Server service to run as a particular Windows
user:
1. On the Windows 2003 or Windows 2008 desktop, right-click the My Computer

icon, and then click Manage.
2. In the left pane of the Computer Management window, expand the Services
and Applications directory, and then click Services.
3. In the right pane, double-click the Content Server <service name>, and then click
the General tab.
4. 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.
5. Click the Log On tab.
6. In the Log on as tab section, click This account, and then click Browse.

7. In the Names list on the Add User window, click the user that you created to
run Content Server, click Add, and then click OK.
The Add User window closes, and the selected user name appears in the This
account field.
8. Type a password for this user in the Password and Confirm password fields,
and then click OK.
9. Open the General tab.
10. Click Start, which is located under Service status.
After the window refreshes, the Service status changes to Started.
Setting Up and Starting the Admin Service on Windows

To set up and start the Admin service to run as a particular Windows user:
• Follow steps 2 to 10 in the procedure described in the section called “Setting Up

and Starting the Content Server Services on Windows” on page 71, for the
Content Server Admin <service_name> on each computer where you performed
an additional Content Server installation.
6.6.2 Setting Up and Starting the Content Server Services on

UNIX/Linux
If you did not start the Content Server servers at the end of the Content Server
installation for UNIX/Linux, you must start them on the Content Server host and all
additional Content Server hosts before continuing to set up Content Server.
On UNIX/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 UNIX/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
UNIX/Linux system administrator to set this up for you.
To start all Content Server services on the Content Server host, or to start the
Admin server on a secondary Content Server host:
1. Log in to the primary or additional (secondary) Content Server host as the

UNIX/Linux user that you created to install and run Content Server.
2. At the operating system prompt, navigate to the <Content_Server_Home>
directory, and then do one of the following:
• If you are starting the Content Server services on the Content Server host,
type the following command, and then press ENTER:
./start_llserver
This command starts both the Content Server and the Admin server.

6.6. Setting Up and Starting the Content Server Services
• If you are starting the Admin server on an additional (secondary) host, type
the following command, and then press ENTER:
./start_lladmin
Note: Do not start the Content Server service on the additional

(secondary) host.
6.6.3 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.
6.7 Configuring General Settings

Before you can create or select a Content Server database, you must set the Content
Server Administration password and enter your Content Server license key.
Note: This procedure documents only the settings that you need to specify to
initially configure Content Server. For details about all Content Server settings,
see OpenText Content Server Admin Online Help - Content Server Administration
(LLESWBA-H-AGD).
Administrators have a special interface to administer the Content Server system. It is

accessible only by administrators. You will use the Content Server Administration
page at various times during this process and as you design your Content Server
system. To access the Content Server Administration page, enter the Content Server
URL:
<protocol>://<host>:<port>/<URL_prefix>/cs.exe?func=admin.index
where <protocol> is either HTTP or HTTPS, <host> is the name of the web server host,
<port> is the port on which your web server listens, and <URL_prefix> is the URL
prefix (virtual directory alias) mapped to the <Content_Server_Home>/cgi/ folder
in the web server (or application server).
Note: UNIX and Linux deployments (and most deployments that use an
application server) do not use the EXE extension.
For more information, see “Accessing the Content Server Administration Page”
on page 97.
To set the Content Server Administrator password and enter license key
information:
1. Launch your web browser, and type the URL for the Content Server
Administration page.
Because Content Server is not configured yet, the system redirects you to the
Configure Server Parameters page.

6.7. Configuring General Settings
2. On the Configure Server Parameters page, enter the password that you want the
Administrator to use to log in to the Content Server.
Tip: Record the new Content Server Administrator password on

Section 3.1.3: “Content Server Installation Worksheets” on page 29.
3. In the License Key section, enter the Company Name, Expiration Date,
Number of Users.
4. Click Save Changes.

The Database Administration page appears. From this page, you will create a
new Content Server database.
5. Proceed to “Completing the Installation and Setup of Content Server“

on page 85.

Chapter 7
Creating the Content Server Database
After you successfully configure Content Server, you must set up the Content Server
database. You can create a new database for use with Content Server or connect
your new Content Server installation with an existing Content Server database. This
section describes how to create a new database. If you have an existing Content
Server database that you want to use with the new Content Server version you
installed, see the OpenText Content Server Upgrade Guide.

• “Creating an Oracle Database” on page 77
• “Creating a Microsoft SQL Server Database” on page 81
7.1 Creating an Oracle Database

This procedure assumes that you are continuing from the procedure described in
“Configuring General Settings” on page 74.
To create a new Oracle database:
1. On the Database Administration page, click Create New Database.
2. On the Select RDBMS Type page, click Oracle Server, and then click Continue.
3. On the Oracle Server Administration sign in page, do the following:
• In the System User Name field, type the Oracle administrator user name.
This is usually system.

Chapter 7 Creating the Content Server Database
• Type the password for the Oracle administrator user.

• In the Service Name field, type the service name (database alias) of Oracle
Server.
Note: The service name is typically the same as the host name of the
computer on which Oracle Server is installed. If you installed Oracle
Server using the guidelines in this guide, you recorded this information on
the “Database Installation Worksheets” on page 27. 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.
4. Click Log-in.
5. On the Create Content Server Tables page, click Oracle Server Maintenance
link.
6. On the Oracle Server Maintenance page, click Create New Tablespace.
7. In the Create New Tablespace section, do the following:

7.1. Creating an Oracle Database
• In the Create New Tablespace section, in the Tablespace Name field, type a
unique name for the tablespace.
You can find out what tablespace names are already in use by looking at the
Oracle Server Maintenance page. Look in the Create New User section, in
the Default Tablespace drop-down list.
• In the File Specification field, type the absolute path of the tablespace data
file that you want to create. For example, c:\oracle\database
\filename.ora or /user/oracle/database/filename.dbf.
The directory that you specify must already exist. The Windows or UNIX/
Linux user that runs the Oracle Server must have permission to write to it.
• In the Size field, type a size in MB 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
8. Click Create Tablespace.
9. Click Create New User.
10. In the Create New User section, do the following:
• In the User Name field, type a unique name for the Oracle user who will
own the tables.
• Type a password for this user.

• In the Default Tablespace drop-down list, click the name of the tablespace
in which you want to create the tables of the new Content Server database.
Note: Record the user name, password, and the default table space name
on the “Database Installation Worksheets” on page 27.
11. Click Create User.
12. Click Return to previous page.
The Create Content Server Tables page reappears. The User Name and
Password fields are automatically populated with the data you provided on the
Oracle Server Maintenance page.
13. Do one of the following to specify whether you want to use internal or external
document storage:
Tip: Before you specify internal or external document storage, consider the
implications of each option. See “Internal and External Document Storage”
on page 21.
• To store documents and other Content Server items inside the database,
clear the External Document Storage check box.
• To store documents and other Content Server items outside the database on
the file system, select the External Document Storage check box, and then
type the absolute path of the directory where you want the Content Server
database to store items in the adjacent field.
Note: The directory that you type in the External Document Storage
field must already exist and the Windows or UNIX/Linux users under
which the Oracle Server and Content Server run must have permission
to write to it.
14. Click Create Tables.
15. Type the password for the Admin user, and then scroll to the bottom of the
page.
16. Click Continue.
• If you want to install any optional modules, proceed to “Installing Optional

Content Server Modules: Stage 2” on page 85.
• If you do not want to install any of the modules displayed under Installable
Modules (or none are displayed), do one of the following:
• To create the Enterprise index (or other indexes) on a secondary Content

Server host, proceed to “Registering a Secondary Admin Server”
on page 87.
• To create the Enterprise index (or other indexes) on the Content Server
host, see “Creating the Enterprise Index” on page 89.

7.2. Creating a Microsoft SQL Server Database
Note: To configure Content Server for UTF-8 character encoding in an Oracle

database, ensure that the character encoding setting in the opentext.ini file
isENV_NLS_LANG=.AL32UTF8 (not ENV_NLS_LANG=.UTF8) under Microsoft
Windowsor NLS_LANG=.AL32UTF8 under UNIX, (not NLS_LANG=.UTF8) . An
incorrect character encoding setting can cause unexpected characters to appear
in documents stored in Content Server.
7.2 Creating a Microsoft SQL Server Database

This procedure assumes that you are continuing from the procedure described in
“Configuring General Settings” on page 74.
To create a new SQL Server database:
1. On the Database Administration page, click Create New 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, do the following:

In the SQL Server Name field, type the Microsoft SQL Server alias.
Note: The server alias is typically the same as 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.

• In the System User field, type the Microsoft SQL Server administrator user
name (usually sa ), and then type the corresponding password in the
System Password field.
• In the Master Database Name field, type the name of the system database
(usually master).
4. Click Log-in.
5. On the Create Content Server Tables page, click the Microsoft SQL Server
Maintenance link.
6. On the Microsoft SQL Server Maintenance page, click the Create a New
Microsoft SQL Server Database link.
7. In the Create a New Microsoft SQL Server Database section, do the following:
• In the Database Name field, type the name that you want to assign to the
database. For example, Content Server.
Note: Do not start the name with a number. While SQL Server allows
this, Content Server does not.

7.2. Creating a Microsoft SQL Server Database
• In the Data File Specification field, type a path and file name. For example,
C:\Store\ContentServer.mdf.
• In the Data File Size field, type a size in MB 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
• In the Log File Specification field, type a path and file name. For example,
C:\Store\ContentServer.ldf.
• In the Log File Size field, type a size in MB for the file (minimum is 5 MB).
Use the Data File Size example as a guide.
Tip: Record this information on Table 3-2: “Microsoft SQL Server

Worksheet (Windows only)” on page 28.
8. Click the Create Database button.
9. On the Microsoft SQL Server Maintenance page, click the Create a New User
link.
10. In the Create a New User section, provide the following information:
• The name that you want to use for the new Microsoft SQL Server user.
• A password for the new Microsoft SQL Server user.
In the Database Name drop-down list, select the name of the Microsoft SQL
Server database (for example, Content Server) in which you want the
Microsoft SQL Server user to store its tables.
Tip: Record the SQL user name and password and the SQL database name
on Table 3-2: “Microsoft SQL Server Worksheet (Windows only)”
on page 28.

11. Click Create User button.
12. Click the Return to previous page link.

On the Create Content Server Tables page, the necessary fields are
automatically populated with the data you provided on the Microsoft SQL
Server Maintenance page.
• To store documents and other Content Server items inside the database,
clear the External Document Storage check box.
• To store documents and other Content Server items outside the database on
the file system, select the External Document Storage check box, and then
type the absolute path of the directory where you want the Content Server
database to store items in the following field.
14. Click the Create Tables button.
15. Type the password for the Admin user, and then scroll to the bottom of the
page.
16. If you want to install optional modules, see “Installing Optional Content Server
Modules: Stage 2” on page 85 before continuing.
17. If you do not want to install any of the modules displayed under Installable
Modules (or none are displayed), do one of the following:
• To create the Enterprise index (or other indexes) on a secondary Content

Server host, see “Registering a Secondary Admin Server” on page 87.
• To create the Enterprise index (or other indexes) on the Content Server host,
see “Creating the Enterprise Index” on page 89.
18. Click the Continue button.
Note: OpenText recommends that you enable the READ_COMMITTED_SNAPSHOT

and ALLOW_SNAPSHOT_ISOLATION SQL Server isolation levels in the Content
Server database.
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

Chapter 8
Completing the Installation and Setup of Content
Server
This chapter explains how to complete the installation and setup of Content Server.
It assumes that you have successfully completed the tasks described in “Creating the
Content Server Database“ on page 77.
To complete your installation of Content Server, perform the tasks described in the
following sections in the order shown:
• “Installing Optional Content Server Modules: Stage 2” on page 85
• “Registering a Secondary Admin Server” on page 87
• “Creating the Enterprise Index” on page 89
• “Creating the Help Indexes” on page 92
• “Additional Tasks to Perform Before Users Connect” on page 94
8.1 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: Stage 1” on page 66.
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.

Chapter 8 Completing the Installation and Setup of Content Server
Figure 8-1: The Install Modules Page

8.2. Registering a Secondary Admin Server
To continue the installation and setup of Content Server from the Install
Modules page:
• If you do not want to install any of the modules displayed in the Installable
Modules section (or none are displayed), click Continue.
The Create New Enterprise Data Source page appears. Proceed to Step 5.
• If you want to install any of the modules displayed in the Installable
Modules section, select each module that you want to install.
Note: When you select a module that requires the installation of other
modules, Content Server automatically selects the check boxes of its
dependent modules.
2. Click Install.
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 installs the selected modules and displays the Restart
Content Server page, stop and then restart the Content Server.
4. Return to the Restart Content Server page and click Continue.
5. On the Create New Enterprise Data Source page, do one of the following:
• To create the Enterprise index (or other indexes) on an additional Content

Server host, see “Registering a Secondary Admin Server” on page 87.
• To create the Enterprise index (or other indexes) on the Content Server host,
see “Creating the Enterprise Index” on page 89.
8.2 Registering a Secondary Admin Server

For optimum search performance, OpenText recommends that you place the
Enterprise index and other large, frequently searched indexes on a secondary
(additional) host. This section describes how to register an Admin server that resides
on a secondary Content Server host so that you can create indexes (including the
Enterprise index) and related data-flow processes on that host.
The procedure in this section assumes that you are registering a secondary Content
Server host during the installation of Content Server, continuing from the end of the
procedure described in “Installing Optional Content Server Modules: Stage 2”
on page 85. It also assumes that the Create New Enterprise Data Source page is
displayed in your web browser.
To register 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).

Before you perform the following procedure, make sure that the Admin server is
running on the secondary host, as described in “Setting Up and Starting the Content
Server Services” on page 70.
Do not register a particular Admin server with more than one Content Server host.
Note: If you want to create all indexes and related data-flow processes on the
Content Server host, see “Creating the Enterprise Index” on page 89.
To register an Admin server on a secondary host:
1. Leave the current web browser window open, and open a new web browser
window.
2. In the new web browser window, open the Content Server Administration
page.
3. In the Search Administration section, click Open the System Object Volume.
On the System Objects Volume page, the Content Server Admin server host
(named Default) appears in the Admin Servers table.
4. On the Add Item menu, click Admin Server.

8.3. Creating the Enterprise Index
5. On the Content Server Add: Admin Server page, in the Alias Name field, type a
name for the secondary Admin server .
6. In the Host Name field, type the name of the computer where the secondary
Admin server is installed.
7. In the Port Number field, type the port number on which the secondary Admin
server listens.
Content Server records this port number in the <Content_Server_Home>/
config/opentext.ini file on the secondary host. It is in the port parameter in
the [OTAdmin] section.
8. If prompted, type the Admin server password.
9. To have this Admin server manage the storage folder, select the Enable check
box located in the File Cache section.
10. To enable the file cache, enter the address of the file cache In the Directory field.
11. To enable the Document Conversion Service for this server to manage, select the
Enable check box.
12. Click Add.
13. Proceed to “Creating the Enterprise Index” on page 89.
8.3 Creating the Enterprise Index

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 the Creating the Enterprise
Index topic in the Content Server Administrator Online Help.
The information in this section assumes that you are continuing from the end of the
procedure described in “Creating the Content Server Database“ on page 77, if you
intend to create the Enterprise index on the Content Server host. It also applies if
you are continuing from the end of the procedure described in “Registering a
Secondary Admin Server” on page 87, where you intend to create the Enterprise
index on a secondary Content Server host. At the end of either of these procedures,
the Create New Enterprise Data Source page is displayed in your web browser.
Note: The Create New Enterprise Data Source page does not appear if you
connected this new Content Server installation to an existing Content Server
database. If this is the case, proceed to “Changing the Admin User Password
and Profile” on page 96.
If other primary Content Server installations already exist on this host, make sure
that the servers and data-flow processes of those existing installations are running
before you create the data-flow processes of the new Enterprise index. This allows
Content Server to automatically detect the port numbers that are already in use. See
the System Object Administration section of the Content Server Administrator help.

Note: Default values for all fields are provided on the Create New Enterprise
Data Source page. It is not necessary to change them for a default Admin
server deployment.
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 field.
Note: This identifier is used in two places. It is:

• 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.
Tip: If you are not continuing a new Content Server installation, you can
access the Create New Enterprise Data Source page from the System
Object Volume administration pages.
Refresh your webpage to display new hosts in the Host drop-down list.
2. Optional To specify the number of partitions into which this index should be
divided, type a number in the Partitions field.
3. In the Port field, 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 the next 11 (at least)
consecutive port numbers must not be used by another data source in your
system. The number of consecutive port numbers that will be used
depends on the number of partitions that you specify in the Partitions
field. Creating an Enterprise index requires eight port numbers, and for
each partition, four additional port numbers. Valid values range from 1025
to 65535.

8.3. Creating the Enterprise Index
4. In the Producer Information area, in the Host menu, select the Content Server
Admin server on which you want the Enterprise Extractor process to run.
5. In the Producer Information section, 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.
6. In the Intermediate and Consumer Information section, 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.
7. 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.
8. In the Intermediate and Consumer Information section, 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.
9. To start the data flow processes as soon as they are created, enable Start
Processes in Data Flow.
10. Click Create Processes.
11. On the Data Flow Creation Status page, click the Continue button.

8.4 Creating the Help Indexes

Content Server includes an extensive help system for both end users and
administrators. Although this step is optional, it is recommended that you create
these indexes to help users and administrators work with Content Server more
effectively by searching the help content for the information they need.
8.4.1 Creating the User Help Index

Content Server user help allows users to access information about the tasks that they
can perform. You can generate an index of the Content Server user help if you want
all users to be able to search the help text from the Content Server Search page or
directly from the Content Server user help.
If you add, uninstall, or upgrade a module after you create the user help index, you
must restart the data flow Directory Walker process so that Content Server indexes
the help files that are associated with the new module.
Content Server creates the user help index on the Content Server host, which is
represented by the alias (usually Default) of its Admin server.
The procedure in this section assumes that you are continuing from the end of the
procedure described in “Creating the Enterprise Index” on page 89, and that the
Congratulations page is displayed in your web browser.
To create an index of user help topics:
1. On the Congratulations page, click Admin Home.
2. On the Content Server Administration page, in the Search Administration

section, click Open the System Object Volume.
3. On the Content Server System page, in the Add Item menu, select User Help
Data Source.
4. On the Create New User Help Data Source page, in the Base Directory field,
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.

8.4. Creating the Help Indexes
Note: OpenText recommends that you choose a directory on a drive on

the Content Server host.
5. To change the default process prefix from Help, type a new unique identifier in
the Process Prefix field.
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 field 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 necessary to generate the user help index
and displays a Status page.
7. Click Continue.
The System Objects Volume page reappears, displaying the contents of the
Content Server System folder.
8. Proceed to “Creating the Admin Help Index” on page 93.
8.4.2 Creating the Admin Help Index

The Content Server Administration pages have their own, separate help content.
Like the Administration pages themselves, the Admin help is not accessible by end
users.
If you add, uninstall, or upgrade a module after you create the Admin help index,
you must restart the data flow Directory Walker process so that Content Server
indexes the help files that are associated with the new module.
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 field,
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.
Note: OpenText recommends that you choose a directory on a drive on

the default Content Server host.
4. In the Process Prefix field, 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.
8.5 Additional Tasks to Perform Before Users

Connect
The installation of Content Server is now complete. However, before you allow your
users to connect, there are a number of administrative tasks to consider. “Tasks to
Perform Before Users Connect” on page 94 describes 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 A
– Understanding Cascading Stylesheets“ on page 115.
Table 8-1: Tasks to Perform Before Users Connect
Task Description
Creating Users and You must create a Content Server user for each member of your
Groups organization who will use Content Server, and then organize these users
into groups.

8.5. Additional Tasks to Perform Before Users Connect
Task Description
Setting Permissions OpenText recommends that you create a Folder hierarchy in the Enterprise
Workspace for the various departments in your organization. When you
do this, you need to set the base permissions on these Folders. For
example, if you create a Folder called “Contracts”, you may want to
configure it so that only members of the Legal department have
permission to view its contents.
Setting the Date Content Server allows you to modify the default date and time formats
Format 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 Each type of item in the Content Server database has a default set of
and Categories 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.
Setting Item By default, all users have the ability to create all types of Content Server
Creation Privileges items (with the exception of Content Server LiveReports). If you want to
restrict the creation of certain types of items to certain users or groups, you
should do this before users connect.
Configuring If you installed optional modules, consult the documentation that
Optional Modules accompanies those modules to see if you need to configure them before
they can be used.
Configuring Access You can set access right restrictions in the system that prevents certain
Control events from updating an item's modified date stamp.
User Display Name You can set the format in which Content Server displays user names in the
Format system for others to see. The format that displays is the user's log-in ID, a
combination of the first name and last name, or a combination of the first
and last names and middle initial.
Set Audit Interests Allows you to specify the item types that you want audited in the Content
Server database.
Administer You can specify events that trigger an update to an item's modified date
Modified Date stamp in Content Server.
Triggers
Password Settings You can specify password settings for users who are new to the system
and or existing users who must change their password based on an
expiration date you set.
Notifications You enable or disable Notifications for the entire system and as well as
specify settings for email, reports, and SMTP.
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.

Task Description
Specify Document Content Server lets you set preferred text editors for MIME types or for
Compose Settings enabling or disabling creation types for new documents.
Configure Search You can set multiple Search options for users, including Find Similar
Options command, Hit Highlight Summary, Block Size, Common Authors, and
others.
Configure Storage By adding Storage Providers to Content Server, you can let users decide
Provider Settings where they want to store documents, based on a location you set up along
with rules and associations.
The OpenText Archive and Storage Services can be used to connect to the
OpenText Archive Server. See the OpenText Content Server – Archive Storage
Provider Installation, Upgrade and Configuration Guide in the Knowledge
Center (https://knowledge.opentext.com).
Enable a DCS See “Enabling a Document Conversion Service (DCS)” on page 98.
Configure Workflow See “Administering the Workflow Module” on page 99.
Parameters
8.5.1 Changing the Admin User Password and Profile

Once you have installed Content Server, change the password and profile of the
Admin user account. This account is created specifically for the Content Server
Administrator.
To change the password and set the profile for the Admin user:
1. On the Personal menu, click My Profile.
2. On the My Profile page, on the General tab, select the Change Password check
box.

3. Type the new password.
4. In the Verify Password field, type the password again.
5. Optionally, add or modify other information for the administrator.
6. Click Update.
Tip: Record the new password on Section 3.1.3: “Content Server Installation
Worksheets” on page 29.
8.5.2 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.
There is no link to the Content Server Administration page from the end-user
interface. Users who have system administration privileges need the URL for the
Content Server Administration page and the password to access the administration
pages.
Note that the password for the Admin user is different from the Administration
password. 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
• 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.
8.5.3 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.
8.5.4 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 102 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 the Content Server.
Note: By default, the Content Server Workflow module always excludes all
system volumes and non-displayable containers.
Table 8-2: 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

Item Node Type ID

Task Group 205
Task List 204
URL 140
Workflow Map 128
Workflow Status 190

Chapter 9
Installing and Uninstalling Modules
Instructions for installing optional modules during the installation of Content Server
are provided in “Configuring Content Server“ on page 47. This chapter tailors that
information for situations where you want to install and uninstall modules after the
initial installation of Content Server.
Content Server’s functionality is organized into software modules. There are two
types of modules: core modules and optional modules.
• Core modules, such as Channels, Discussions, Tasks, and Projects, are
automatically installed when Content Server is installed.
• Optional modules, such as Content Server Directory Services, and Content Server
EPS Integration, must be installed by the Content Server administrator. Optional
modules allow you to extend the functionality of Content Server to meet your
organization's specific needs.
Most Content Server modules include help files. Therefore, after you install or
uninstall a module, you should update the Help index so that it includes the
information in the new module's help files.

• “Installing Modules” on page 105
• “Uninstalling Modules” on page 109
• “Updating the Help Index to Reflect Changes in Installed Modules” on page 111
9.1 Installing Modules

You can install modules at any time after the initial installation of Content Server.
These may be new modules that you purchased at a later time or modules available
at installation time that you chose not to install.
When you purchase an optional Content Server module, you may receive it on a CD-
ROM or you may download it from an OpenText website. In either case, specific
instructions for installing the module accompany it.
You install a module in the following two stages:

• First, you must use the module's InstallShield program or TAR file to place its
files in the <Content_Server_Home>/staging/ folder. See “Installing Modules
on Windows” on page 106 or “Installing Modules on UNIX/Linux” on page 106.
• Second, you must install the module in Content Server using the Install Modules
page. See “Completing a Module Installation” on page 107.

Chapter 9 Installing and Uninstalling Modules
9.1.1 Installing Modules on Windows

For Windows versions of Content Server modules, you perform the first stage of an
installation using an InstallShield program. This installation copies the module's
files to a subfolder of the <Content_Server_Home>/staging/ folder.
To install a Content Server module on Windows:
1. 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.
Note: If there is more than one Content Server installation present on the
host computer, the Select Content Server Service window lists the
Windows service names of all primary and secondary Content Server
installations currently installed on this host. In this case, select the check
box of the primary Content Server installation to which you want to add
the module (you can select only one), and then click Next.
The installation program copies the appropriate files to the

<Content_Server_Home>/staging/ folder and displays a window informing
you that this part of the installation is complete.
4. Click OK, and repeat the previous steps for each module that you want to
install.
5. Proceed to the second stage of the module installation, as described in

“Completing a Module Installation” on page 107.
9.1.2 Installing Modules on UNIX/Linux

For UNIX/Linux versions of Content Server modules, you perform the first stage of
an installation using a TAR compressed archive file. The extraction of this TAR file
places the module's files in a subdirectory of the <Content_Server_Home>/
staging/ directory.
To install a Content Server module on UNIX/Linux:
1. Copy the module's TAR file to the <Content_Server_Home> directory of the

primary Content Server installation to which you want to add the module.
2. At the operating system prompt, type the following command, substituting the
correct file name for <module_name>, and then press ENTER:
tar -xvf <module_name>.tar
All necessary files are extracted from the <module_name>.tar file into the
<Content_Server_Home>/staging/ directory.
3. Repeat the previous steps for each module that you want to install. for each
module that you want to install.

9.1. Installing Modules
4. Proceed to the second stage of the module installation, as described in

“Completing a Module Installation” on page 107.
9.1.3 Completing a Module Installation

You perform the second stage of a module installation using the Install Modules
page of theContent Server Administration page.
To perform the second stage of installing a Content Server module:
1. In your web browser, open the Content Server Administration page.
Note: If you have already logged in to the Content Server Administration

page during the current web browser session, you are not prompted to log
in again at this point.
2. On the Content Server Administration page, under Module Administration,
click Install Modules.
The Install Modules page appears. The modules available for installation are
listed in the Installable Modules section.
3. Select the check box of each module that you want to install, and then click
Install.
Note: To install a module that lists dependencies (a module that requires

other modules to be installed), you must also install the modules listed as
dependencies. When you select the check box of a module that lists
dependencies, Content Server automatically selects the check boxes of its
dependent modules.
4. If prompted, type the password for the Admin, and then click Log-in.
Content Server installs each selected module, and then displays the Restart
Content Server page.

Note: For most optional module installations, the Restart Content Server
page is the first page that appears after you click Install. However, some
modules may have different configuration parameters that need to be
configured separately after the installation. Also, some module
installations display a configuration page before the Restart Content
Server page. Consult the documentation that accompanies such modules
for instructions on how to complete the configuration page.
5. Restart the Content Server, and then click Continue on the Restart Content
Server page.
Note: After you install a module that has help files associated with it, update
the Help index so that it includes the module's help files. See “Updating the
Help Index to Reflect Changes in Installed Modules” on page 111.
9.2 Installing Filter Packs

Content Server's Document Conversion Service (DCS) uses filter packs to convert
documents from their native file formats (such Word, PDF, or ASCII text) to a simple
text format. Document conversion is central to Content Server Search's advanced
document-conversion and text-extraction functionality, including “find similar”,
recommender synopsis generation, classification profile generation, and hit
highlighting. It is also used to perform the View as Web Page function on
documents in Content Server. To take advantage of these features, you must obtain
and install a filter pack, either from OpenText or a third-party vendor.
See the section called “Document Conversion Service (DCS)” on page 16.
Information about installing and configuring a filter pack in Content Server is also
available in the Knowledge Center (https://knowledge.opentext.com).

9.3. Uninstalling Modules
9.3 Uninstalling Modules

Content Server allows you to uninstall any optional modules that have been
installed, such as Content Server Explorer. It also allows you to uninstall some pre-
installed modules, such as Discussions, Projects, or Workflow.
Note: Even though Content Server allows you to uninstall some core modules,
OpenText strongly recommends that you do not uninstall them unless
instructed to do so by OpenText Customer Support.
To uninstall a module:
1. In your web browser, open the Content Server Administration page.
2. If prompted, type the Content Server Administrator password, and then click
Log-in.
3. On the Content Server Administration page, under Module Administration,

click Uninstall Modules.
4. On the Uninstall Modules page, click the Uninstall button of the module that
you want to remove.

Note: If a module is depended on by other modules, it has no Uninstall

button. You must uninstall all the modules listed in the Dependencies
column before you can uninstall the module on which they depend.
5. If prompted, type the password for the Admin user, and then click Log-in.
Content Server uninstalls the selected module, and then displays the Restart
Content Server page when the module removal is complete.
When you uninstall a module, Content Server moves the module's files back
into the <Content_Server_Home>/staging/ directory, so that it is available to
be reinstalled on the Install Modules page.

9.4. Updating the Help Index to Reflect Changes in Installed Modules
6. Restart the Content Server, and then click Continue on the Restart Content
Server page.
7. Repeat this procedure for each module that you want to uninstall.
Note: After you uninstall a module that has help files associated with it,
update the Help index so that the module's help files are removed from the
index. See “Updating the Help Index to Reflect Changes in Installed Modules”
on page 111.
9.4 Updating the Help Index to Reflect Changes in

Installed Modules
You can create an index of the help files in Content Server, including those help files
that relate to Content Server modules. Indexing Content Server's help gives all users
the ability to perform full-text searches on help topics. See “Creating the Help
Indexes” on page 92.
Most Content Server modules have their own help files. When you add, remove, or
upgrade a module, you also add, remove, or change the corresponding help files.
Therefore, you must update the Help index to reflect these changes, otherwise,
inaccurate search results may be displayed. For example, if you uninstall a module
without updating the Help index, a search for terms that occur in the removed
module's help files results in those files being listed on the Search Result page, even
though they can no longer be viewed.
To update the Help Index to reflect changes in installed modules:
Note: This procedure is only required for the search module.
1. On the Content Server Administration page, under System Administration,

click Open the System Object Volume.
2. On the Content Server System page, click Help Data Source Folder.
3. Click Help Data Flow Manager.
4. On the Help Data Flow page, click the Functions icon of the Help Data Flow
object, and then click Start.
5. To update the index of help topics for Content Server Administrators, repeat
steps Step 2 to Step 4 for the Admin Help Data Source Folder.

Chapter 10
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 113
• “Uninstalling Content Server on UNIX/Linux” on page 114
10.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 10 Uninstalling Content Server
10.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.
10.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 11
Appendix A – 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 A – 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:

Index security 25
configuring
Content Server 47
A Content Server
access tier about 16
configuring 30 configuration 47
Content Server architecture 17 creating a user for UNIX/Linux 35
additional Admin server for Content Server creating a user for Windows 34
registering 87 preparing to install 27
additional Content Server computer Content Server Cluster Architecture
creating indexes on 19 load balancing 20
worksheet 29 Content Server Remote Cache
admin help about 20
indexing 92 conventions v
Admin server conversion filters
about 16 about 16
administrators
changing email address 97 D
Apache Tomcat data flow processes
configuration 56 about 16
using with Content Server 30 data tier
application servers Content Server architecture 18
configuring to work with a web server 30 databases
Java framework 15 creating a SQL Server database 81
supported 13 creating an Oracle database 77
using with Content Server 30 creating for Content Server 77
application tier installing 31
Content Server architecture 17 installing on an additional computer 20
architecture recommendations 25
configuration options 18 supported 12
Content Server 17 DCA
extranet 21 document conversion 16
multihost 19 DCS
authentication configuring 98
changing the admin user password 96 enabling 98
designing
B Content Server system 11
backups Document Conversion Service
external document storage 22 about 16
bottlenecks document file streaming
avoiding 23 security option 55
document storage
C
internal versus external 21
CGI
documentation
configuring the access tier 30
indexing 92
supported 17
documents
understanding the Java framework 15
trouble opening 36
clusters
load balancing 20
config directory

Index
E logging 100
enterprise index 19 item reference attribute
creating 89 administering 101
external document storage
backup and recovery 22 J
setting up 22 Java framework
extranet architecture about 15
about 21
L
F Livelink Secure Extranet Architecture (SEA)
file streaming about 21
security option 55 LLServlet
filter packs deploying and configuring 47
document conversion 16 deployment options 47
installing 108 extranet architecture 21
file streaming 55
G
GlassFish Enterprise Server M
worksheet 28 Microsoft SQL Server
creating the database 81
H MIME types
help about 36
indexing 92 modules
help index about installing 105
creating for Admin Help 93 installing after Content Server setup 105
creating for user Help 92 installing during Content Server setup (stage
updating for new modules 111 1) 66
HTTPS installing on UNIX/Linux 106
recommended 25 installing on Windows 106
uninstalling 109
I monitoring
IBM WebSphere recommendations 23
configuration 56
IIS N
worksheet 28 nodes
indexing common node type IDs 101
enterprise index 89
help for new modules 111 O
online help 92 online help
installing indexing 92
additional tasks to perform before users operating system user
connect 94 about 34
creating a UNIX/Linux user 35 creating for UNIX/Linux 35
creating a Windows user 34 creating for Windows 34
database servers 31 operating systems
first-time installation flow chart 27 supported 12
prerequisites 27 Oracle
worksheets 29 creating the database 77
item handler step UNIX/Linux installation guidelines 32
about 100 Windows installation guidelines 31

Index
worksheets 27 optimal number 23

Tomcat
P configuration 56
passwords transaction rates
changing for admin user 96 optimal 23
performance tuning your database
effect of creating indices on additional recommended 25
computers 19 typography v
recommendations 23
primary computer 19 U
profiles uninstalling
changing for admin user 96 Content Server 113
Content Server on UNIX/Linux 114
R Content Server on Windows 113
RDBMSs UNIX/Linux
supported 12 Content Server installation 43
registering URL prefix 29, 74
additonal Admin server for Content Server created from Content Server service name
87 40
remote cache setting during UNIX/Linux install 44
performance 20 URLScan
configuring for use with Content Server 64
S
configuring for use with WebDAV 64
security
user help
changing the admin user password 96
indexing 92
recommendations 25
users
SQL Server
additional tasks to perform before users
creating the database 81
connect 94
installation guidelines 33
creating a UNIX/Linux user 35
worksheets 28
creating a Windows user 34
streaming
UTF-8
about 55
about 14
document conversion 56
file uploads 55
W
Sun GlassFish Enterprise Server
web browsers
worksheet 28
configuring for users 35
Sun Java web server
supported 13
worksheet 28
web servers
supported components
creating a user for UNIX/Linux 35
in Content Server 12
creating a user for Windows 34
system components
Java framework 15
about 11
supported 13
system design
WEB-INF directory 47
best practices 23
web.xml file 47
Content Server 11
WebDAV
T configuring for use with URLScan 64
third party components WebSphere
supported 12 configuration 56
threads Windows

Index
Content Server installation 39

workflow
administering the workflow module 99
workflow agent
about 101
workflows
configuring parameters 96
XML Interchange Step 15
worksheets
about 27
Content Server 29
Microsoft Internet Information Server 28
Oracle 27
SQL Server 28
Sun Java System Web Server 28
X
XML
support in Content Server 14

OpenText Content Server - Installation Guide PDF

Uploaded by

Copyright:

Available Formats

OpenText Content Server - Installation Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Content Server - Installation Guide PDF

Uploaded by

Copyright:

Available Formats

This guide is intended for Content Server administrators. It

40 Avenue Monterey , Luxembourg, Luxembourg L-2163

Open Text Corporation

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

Copyright © 2013 by Open Text Corporation

No Warranties and Limitation of Liability

1 Installing Content Server .......................................................... 9

2 Designing Your Content Server System ............................... 11

3 Preparing to Install Content Server ....................................... 27

4 Installing Content Server on Windows .................................. 39

5 Installing Content Server on UNIX and Linux ....................... 43

6 Configuring Content Server ................................................... 47

7 Creating the Content Server Database .................................. 77

LLESCOR100012-IGD-EN-1 OpenText Content Server iii

7.2 Creating a Microsoft SQL Server Database ....................................... 81

8 Completing the Installation and Setup of Content Server ... 85

9 Installing and Uninstalling Modules .................................... 105

10 Uninstalling Content Server ................................................. 113

11 Appendix A – Understanding Cascading Stylesheets ....... 115

IDX Index 119

iv OpenText Content Server LLESCOR100012-IGD-EN-1

i.i Target readership

• An understanding of Content Server's purpose within your organization and

i.ii Documentation conventions

Filenames, commands, and sample data

LLESCOR100012-IGD-EN-1 OpenText Content Server v

Note: Notes provide additional information about a task.

Tip: Tips offer you quicker or easier ways of performing a task.

OpenText Online Communities ( https://communities.opentext.com/communities/

The OpenText Knowledge Center (https://knowledge.opentext.com) is OpenText's

vi OpenText Content Server LLESCOR100012-IGD-EN-1

• Product downloads, patches, and documentation including Release Notes.

LLESCOR100012-IGD-EN-1 Installation Guide vii

OpenText Content Server is the leading collaboration and enterprise content

This chapter covers the following topics:

1.1 Installing Content Server

In general terms, installing Content Server involves the following steps:

1. Choosing the operating system, relational database management system and

LLESCOR100012-IGD-EN-1 OpenText Content Server 9

5. Creating a Content Server database. For information on this stage of the

Information on uninstalling Content Server appears in “Uninstalling Content

1.2 Upgrading Content Server and Installing Updates

10 OpenText Content Server LLESCOR100012-IGD-EN-1

Content Server can be deployed in a variety of configurations, ranging from simple

This chapter covers the following topics:

2.1 About Content Server

LLESCOR100012-IGD-EN-1 OpenText Content Server 11

Figure 2-1: Basic Content Server System

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:

12 OpenText Content Server LLESCOR100012-IGD-EN-1

Note: If your database resides on a separate computer (recommended

LLESCOR100012-IGD-EN-1 Installation Guide 13

2.1.2 Content Server Components

Language Support and UTF-8 Character Encoding

Previous Western-European releases of Content Server (formerly Livelink ECM

Content Server is now UTF-8 only, regardless of language.