1 Installation and Upgrade Overview 9.6.1

Livelink
ECM Archive Server 9.6.1

Installation and Upgrade Overview

AR090601-IOV-EN-5
Livelink
ECM Archive Server 9.6.1

Installation and Upgrade Overview
AR090601-IOV-EN-5
Rev.: 2008-July-02
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
E-mail: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com
Copyright 2008 by Open Text Corporation
Open Text Corporation is the owner of the trademarks Open Text, The Content Experts, Great Minds Working Together,
Livelink, Livelink ECM, Livelink ECM-eDOCS, Livelink MeetingZone, MeetingZone, B2BScene, B2BScene.com, Client/Surfer,
Collaboration, Creative Desktop, Further Faster, Hyperinnovation, Internet Anywhere ,Livelink IRIMS, IRIMS, IXOS, Livelink
OnTime, OnTime, Livelink Remote Cache, Microstar, MyLivelink, O & Design, Odesta, Odesta Helix, Odesta Livelinke, Open
Text Intranet, Open Text Web Index, Personality +, Putting Knowledge To Work, Techlib, The Hyperlinked Organization, The
Source For Business Knowledge, Worksmart, and World Of E among others. This list is not exhaustive.
ACKNOWLEDGEMENTS
SAP
, R/3
and SAP ArchiveLink
are registered trademarks of SAP AG.

Adobe
is a trademark of Adobe Systems Incorporated.

Lotus
and Lotus Notes
are registered trademarks of Lotus Development Corporation. Domino is a trademark of Lotus

Development Corporation.
Microsoft
and Microsoft SQL
are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Oracle
is a registered trademark of Oracle Corporation.

Netscape and the Netscape N and Ship's Wheel logos are registered trademarks of Netscape Communications Corporation in
the U.S. and other countries.
Firefox
is a registered trademark of the Mozilla Foundation.

Sentry Spelling-Checker Engine Copyright 2000 Wintertree Software Inc.
WordNet 2.0 Copyright 2003 by Princeton University. All rights reserved.
Outside In
Viewing Technology 1992-2002 Stellent Chicago, Inc. All rights reserved. Outside In
HTML Export 2002

Stellent Chicago, Inc. All rights reserved.
Portions of eDOCS DM are copyrighted by DataDirect Technologies, 1991-2002.
All other products or company names are used for identification purposes only, and are trademarks of their respective own-
ers. All rights reserved.
AR090601-IOV-EN-5 Livelink ECM Archive Server 9.6.1 iii

Table of Contents

1 Introduction ............................................................................... 5
2 Common installation topics...................................................... 7
3 Partitioning ................................................................................ 9
3.1 Case 1: Archive Server and database on the same machine, database
created by Open Text............................................................................. 10
3.2 Case 2: Archive Server and database on the same machine, database
created by customer............................................................................... 14
3.3 Case 3: Archive Server and database on different machines, database
created by Open Text............................................................................. 15
3.4 Case 4: Archive Server and database on different machines, database
created by customer............................................................................... 17
3.5 Case 5: New installation of Archive Server and use of existing complete
(with Archive Server tables) database of an identical version............... 17
3.6 Case 6: New standalone installation of Livelink ECM Document
Pipeline .................................................................................................. 18
3.7 Case 7: New installation of Livelink ECM Document Pipelines for
Universal Archive and database on same machine............................... 18
3.8 Case 8: New installation of Document Pipelines for Universal Archive
and database on different machines...................................................... 20
4 Guides...................................................................................... 23
4.1 Guides needed for new installation........................................................ 23
4.1.1 Standard installation of Archive Server.................................................. 23
4.1.2 Remote DB............................................................................................. 24
4.1.3 Document Pipeline Standalone.............................................................. 25
4.1.4 Document Pipelines for Universal Archive............................................. 26
4.1.5 Archive Cache Server ............................................................................ 26
4.1.6 Timestamp Server.................................................................................. 26
4.1.7 Remote Standby Server......................................................................... 26
4.1.8 Cluster installation.................................................................................. 27
4.2 Guides needed for update ..................................................................... 27
5 Platform dependencies........................................................... 29
5.1 AIX (IBM)................................................................................................ 29
5.2 HP-UX 11.23 (PA-RISC 64bit, IA-64) .................................................... 30
5.3 Linux Enterprise Server 9 (SUSE; i386 32-bit) ...................................... 30
Table of Contents
iv Livelink ECM Archive Server 9.6.1 AR090601-IOV-EN-5

5.4 MS Windows Server 2003 platforms (i386 32-bit) ................................. 31
5.5 Solaris (SUN) ......................................................................................... 32
AR090601-IOV-EN-5 Livelink ECM Archive Server 9.6.1 5

Chapter 1

Introduction
This document is intended to give an overview of the most important system
settings, preparations and the order of the appropriate installation or upgrade
guides.
Important
If an update is intended, make sure the installed Livelink ECM Archive
Server has version 9.6.0!
Only for Livelink ECM Archive Server version 9.6.0, the update documents
mentioned in this document can be used.
If the already installed version is older than 9.6.0, please refer to the
following upgrade documents in ESC:
https://esc.ixos.com/1133772519-599
Check out the Compatibility with other Livelink products
For a list of Livelink product versions supported by Livelink ECM Archive Server
9.6.1, see the Products Compatibility Matrix in the ESC
(https://esc.ixos.com/1040043376-722). For information and restrictions concerning
other products, see the corresponding Release Notes in the ESC.

Chapter 2

Common installation topics
Global assumptions
Most disks for the Archive Server should be mirrored with RAID 1, and there
should be at least 3 independent disks. The secure operation of the database
requires 1 disk for the database and 2 separate disks for the online REDO and
offline REDO log files. Archive Server stores all documents temporarily on hard
disk. This disk should be protected by RAID 5 or RAID 1.
The partition sizes listed below are minimal sizes. The recommended sizes are
dependant mainly on the archive size and the number of logical archives. Refer
to the partitioning recommendation given to you by Open Text.
If you are using Livelink ECM Electronic Archiving (UAC), a second database is
needed. If this instance is installed on the Archive Server machine, it is advisable
to adjust the limit parameters (see Additional operating system information
Platform dependencies on page 29). In this case, additional disk space for DB
data and DB index is required.
Unwanted fragmentation of disk partitions
Some file systems tend to unwanted fragmentation of disk partitions. This may lead
to incorrect free space detection and an attempt to write data to the file system will
fail (no space left on device).
This problem can affect the following partitions:
Archive Server:
cache partitions and in case of remote standby scenario the replicated disk buffer
volumes
Archive Cache Server:
cache partitions
To avoid this problem, see the ESC (https://esc.ixos.com/1169658576-394).
Network recommendations/restrictions
The Archive Server requires a static IPv4 address.
Chapter 2 Common installation topics
8 Livelink ECM Archive Server 9.6.1 AR090601-IOV-EN-5

Memory recommendations
The recommended amount of RAM per CPU is at least 1 GB. The following table
shows the relation between total RAM and SWAP or paging space in your
system:

RAM SWAP or paging space
1 GB to 2 GB 1.5 times RAM
> 2 GB and < 8 GB 1 times RAM
> 8 GB 0.75 times RAM
Access rights for directories and partitions (UNIX/Linux)
For the following mount points, directories and partitions, the owners must be
user <archive-user> and group <archive-group>. Access permissions should be 755
(-rwxr-xr-x). See below in the partition table.
For all Oracle directories, the owner must be user <oracle-user> and group <dba-
group>. In all cases, the access permissions should be 755 (-rwxr-xr-x).
Some files will have root permissions like the jbd!

Chapter 3

Partitioning
The partitioning depends on the location of the database. Will the database reside on
the same server as the Archive Server (classical, local) or will it reside on a dedicated
database server (remote DB scenario)? Furthermore, the kind of archive media you
will use (WORM/UDO or DVD/Storage Systems) plays a role.
Database installation possibilities:

Database created by Open
Text
Database created by cus-
tomer
Archive Server and data-
base on same computer
Case 1
(see Case 1: Archive Server
and database on the same
machine, database created
by Open Text on page 10)
Case 2
and database on the same
machine, database created
by customer on page 14)
Archive Server and data-
base on different computer
Case 3
and database on different
machines, database created
by Open Text on page 15)
Case 4
and database on different
machines, database created
by customer on page 17)
Notes:
In the cases 2 and 4, the customer provided database must match several
requirements which are described in the appendix of the following
documents:
Installing Livelink ECM Archive Database 9.6.1 on UNIX with Oracle
ESC: https://esc.ixos.com/1157553245-908
Installing Livelink ECM Archive Database 9.6.1 on Windows with Oracle

Installing Livelink ECM Archive Database 9.6.1 on Windows with MS
SQL
Moreover, it is possible to perform a new installation of the Archive Server
and to use an existing database (with Open Text tables) of an identical
Chapter 3 Partitioning

version (see Case 5: New installation of Archive Server and use of existing
complete (with Archive Server tables) database of an identical version on
page 17).
Recommended disk partitioning
Each entry is a separate partition, which is to be used exclusively by
Archive Server. The disk sizes given here are minimum requirements; the
mount points are only a suggestion.
3.1 Case 1: Archive Server and database on the
same machine, database created by Open Text
This is the classic installation scheme.
Partitions under Windows:
Build your drives/disks as Basic Disks, not as dynamic ones.
Create primary or extended (with logical) partitions.
For database Oracle: Recommended disk partitioning
The following table is for both UNIX/Linux and Windows. The mount points and
path names are given in UNIX style. For Windows, partitions with drive letters and
appropriate path names have to be used.

Disk 1 System Disk, not mirrored Subdirec-
tories
User and group Recommended
size
Partition 1
Mount point: /archives
Archive Server binaries
<archive-user>:
<archive-group>
5.0 GB

ca. 420 MB
Partition 2
Mount point: /oraclesw
Oracle binaries
<oracle-user>:
<dba-group>
1.7 GB
Partition 3
Mount point: /ora-redo-
logs
Online REDO logs
<oracle-user>:
<dba-group>
ca. 450 MB
Partition 4
Mount point: /archivecache
for local cache
<archive-user>:
<archive-group>
10 GB
e.g. 2 DVDs
Should hold data
from at least the
last two working
weeks
3.1 Case 1: Archive Server and database on the same machine, database created by Open Text
AR090601-IOV-EN-5 Installation and Upgrade Overview 11

Disk 2 Database (RAID 1) Subdirec-
tories
User and Group Recommended
size
Partition 1
Mount point: /dbdata
for Database data files
<oracle-user>:
<dba-group>
3.0 GB
autoextend is on
per default
Partition 2
Mount point: /diskbuffer
Disk buffer
<archive-user>:
<archive-group>
10 GB
e.g. 2 DVDs
Should hold data
from at least the
last two working
weeks
Partition 3
Mount point: /ora-redo-arc

Archive REDO log files
<oracle-user>:
<dba-group>
3.0 GB
Minimum; de-
pends on the
workload on the
database
Partition 4
Mount point:
/archive
_
forms
Forms Management
<archive-user>:
<archive-group>
0.1 GB
Disk 3 STORM database file sys-
tem for WORM/UDO Juke-
box (for medium size)
Subdirec-
tories
size
Partition 1
Mount point: /stormfs
Please note:
For better performance, the
inode files for large databases
should be stored on different
partitions on different hard
disk drives (in this case, the
partitioning would appear
different from that suggested
here). See
/usr/archive/config/stor
m/templates/sectionWORM
_
large.cfg for more details.

/stormfs/
hashdir
/stormfs/
hashname
/stormfs/
hashfile
/stormfs/
inodes
(optional)

<archive-user>:
<archive-group>
6.0 GB

200 MB
200 MB
200 MB
5 x 600 MB
500 MB
tem for ISO file archiving
(DVD, Centera, HDS,
"HSM", IBM DR550)
Subdirec-
tories
size
Partition 2
mirr
Mirrored online redo log
files
<oracle-user>:
<dba-group>
ca. 450 MB

tem for ISO file archiving
(DVD, Centera, HDS,
"HSM", IBM DR550)
Subdirec-
tories
size
Partition 3
Mount point: /burnbuffer
with subdirectories:

/burnbuff
er/tree
/burnbuff
er/image
<archive-user>:
<archive-group>
15 GB
approx. 3 DVDs;
depends on the
size of the images
and amount of log.
archives where
ISOs are archived
tem for WORM/UDO Juke-
box (for medium size)
Subdirec-
tories
size
Partition 1
Mount point: /dbindex
Database Index
<oracle-user>:
<dba-group>
3 GB
autoextend is on
per default
Partition 2
Mount point: /dp
Document Pipeline
(will be created by config)
<archive-user>:
<archive-group>
5 GB
Should hold the
data for at least
one working
week. Depends
also on the size of
the documents
(LargeFiles)
In case hard disk archives are
used:
Partition 3
Mount point: /hdsk1
Hard disk archive 1
<archive-user>:
<archive-group>
5 GB
Depends on the
amount of data
that will be ar-
chived
Partition 4
Mount point: /stormfs-bkp

Backup file system for
STORM
<archive-user>:
<archive-group>
6.2 GB with
WORM filesystem,
or 0.2 GB without.
Same size as
/stormfs plus 200
MB additionally
For database MS SQL: Recommended disk partitioning

Disk 1 System Disk, not mirrored) Logical
Partition
Recommended size
Binaries for MS SQL
Archive Server Binaries
D:\ 5.0 GB
3.1 Case 1: Archive Server and database on the same machine, database created by Open Text

Disk 1 System Disk, not mirrored) Logical
Partition
Recommended size
Local Cache E:\ 10 GB
e.g. 2 DVDs
Should hold data from
at least the last two
working weeks
Disk 2 Database (RAID 1) Logical
Partition
Recommended size
Database data files F:\ 3 GB
autoextend is on per
default
Diskbuffer G:\ 10 GB
e.g. 2 DVDs
Should hold data from
at least the last two
working weeks
Forms Management H:\ 0.1 GB
Disk 3 STORM database file system for
WORM/UDO Jukebox (medium size)
Logical
Partition
Recommended size
WORM Filesystem
Note: For better performance, the inode
files for large databases should be stored
on different partitions on different hard
disk drives (in this case, the partitioning
would appear different from that sug-
gested here). See <archive-inst-
dir>/config/storm/templates/sectio
nWORM
_
large.cfg for more details.
I:\ 6 GB
Transaction log for MS SQL L:\ 2 GB
Minimum; depends on
the workload on the
database
Disk 3 STORM database file system for ISO file
archiving (DVD, Centera, HDS, "HSM", IBM
DR550)
Logical
Partition
Recommended size
Burnbuffer for ISO images and ISO tree build-
ing
J:\ 15 GB
approx. 3 DVDs
Depends on the size of
the images and amount
of log. archives where
ISOs are archived.

Disk 4 Index and Transfer (RAID 1) Logical
Partition
Recommended size
Database index files M:\ 3 GB
default
Document Pipeline N:\ 5 GB
Should hold the data for
at least one working
week. Depends also on
the size of the docu-
ments (LargeFiles)
Hard disk archive 1 O:\ 5 GB
Depends on the amount
of data that will be ar-
chived
Backup file system for STORM K:\ 6.2 GB
with WORM filesystem,
or 0.2 GB without. Same
size as /stormfs plus
200 MB additionally
3.2 Case 2: Archive Server and database on the
same machine, database created by customer
In this case, the database software has been installed and the customer has already
created the database. As a result, no consideration needs to be made for database
software and the database files. The database provided by the customer must meet
several requirements described in the appendix of the following install guides:
Archive Database 9.6.1 on UNIX with Oracle
Archive Database 9.6.1 on Windows with Oracle
Archive Database 9.6.1 on Windows with MS SQL
These settings are identical to the recommended disk partitioning of Case 1 (see
Case 1: Archive Server and database on the same machine, database created by
Open Text on page 10)
3.3 Case 3: Archive Server and database on different machines, database created by Open Text

3.3 Case 3: Archive Server and database on different
machines, database created by Open Text
In this case, the database is provided by Open Text, but is located on a different
machine than the Archive Server.
It is mandatory that you install the database server and create the database first.
Failing to complete this step will result in an unsuccessful installation of the Archive
Server, as a fully operative database is a prerequisite to the Archive Server
installation.
Open Text on page 10) but without the partitions for database data, index, and
REDO log, respectively, transaction log files. This space is needed on the database
server. Instead of space for Database Server binaries, you will need only 200MB for
the database client installation on the system partition of the Archive Server.
For database Oracle: Recommended disk partitioning for Archive Server
database on a dedicated database server
The following table holds for both UNIX/Linux and Windows. The mount points
and path names are given in UNIX style. For Windows logical partitions with drive
letters and appropriate path names have to be used.

tories
size
Partition 1
Mount point: /archivesw
Binaries for Archive Server
(DB package)
<archive-user>:
<archive-group>
1.0 GB
Partition 2
Oracle binaries
<oracle-user>:
<dba-group>
1.7 GB
Partition 3
logs
Online REDO logs
<oracle-user>:
<dba-group>
ca. 450 MB
tories
size
Partition 1
<oracle-user>:
<dba-group>
3 GB
autoextend is on
per default

tories
size
Partition 2
mirr
files
<oracle-user>:
<dba-group>
ca. 450 MB
Disk 3 Index and Transfer (RAID 1) Subdirec-
tories
size
Partition 1
Database Index
<oracle-user>:
<dba-group>
3 GB
autoextend is on
per default
Partition 2

<oracle-user>:
<dba-group>
3 GB
minimum, de-
pends on the
workload on the
database
For database MS SQL: Recommended disk partitioning for Archive Server

Disk 1 System Disk, not mirrored Logical
Partition
Recommended size
Binaries for MS SQL
Binaries for Archive Server (DB package)
D:\ 5.0 GB
Partition
Recommended size
default
Disk 3 Transaction Log (RAID 1) Logical
Partition
Recommended size
minimum, depends on
the workload on the
database
Partition
Recommended size
default
3.4 Case 4: Archive Server and database on different machines, database created by customer

Note: If you want several Archive Servers to share a single database server
with more than one database provided by Open Text, please contact Open Text
Customer Support before you install the database server.
3.4 Case 4: Archive Server and database on different
machines, database created by customer
This case is similar to case 3, but instead of providing the database server, you only
need to check the database provided by the customer to ensure it meets the
requirements in the appendix of the following install guides:
Open Text on page 10) but without the partitions for db data, db index, and REDO
log, respectively, transaction log files because the space is needed on the database
server. Instead of space for the Database Server binaries, you will need only 200 MB
for the database client installation on the system partition of the Archive Server.
3.5 Case 5: New installation of Archive Server and
use of existing complete (with Archive Server
tables) database of an identical version
A precondition is that the (Archive Server) tables of the database to be used have the
identical version as the Archive Server to be installed.
If the database is on a different machine than the Archive Server, the partitioning is
identical to case 3.
If the database is on the same machine as Archive Server, an Archive Server must
already have been installed on the machine which is to be reinstalled. Please contact
Open Text Customer Support before you begin, as several files need to be moved or
saved before uninstalling and reinstalling Archive Server.

3.6 Case 6: New standalone installation of Livelink
ECM Document Pipeline
Recommended disk partitioning UNIX/Linux and Windows

tories
size
Partition 1
Document Pipeline bina-
ries
<archive-user>:
<archive-group>
5.0 GB

ca. 300 MB
Partition 2
Mount point: /dp
Document Pipeline
<archive-user>:
<archive-group>
5 GB
should hold the
data for at least
one working
week. Depends
also on the size of
the documents
(LargeFiles)
3.7 Case 7: New installation of Livelink ECM
Document Pipelines for Universal Archive and
database on same machine
It is mandatory that the database software be installed and the database be created
before the Document Pipelines for Universal Archive be installed. Failing to complete
this step will result in an unsuccessful installation of the Document Pipelines for
Universal Archive, as the Document Pipelines for Universal Archive installation requires
a fully operative database.
For database Oracle: Recommended disk partitioning
and path names are given in UNIX style. For Windows, logical partitions with drive

tories
size
Partition 1
ries
<archive-user>:
<archive-group>
5.0 GB

ca. 300 MB
Partition 2
Oracle binaries
<oracle-user>:
<dba-group> 1.7 GB
3.7 Case 7: New installation of Livelink ECM Document Pipelines for Universal Archive and database on
same machine

tories
size
Partition 3
logs
Online REDO logs
<oracle-user>:
<dba-group>
ca. 450 MB
tories
size
Partition 1
<oracle-user>:
<dba-group>
3 GB
autoextend is on
per default
Partition 2
mirr
files
<oracle-user>:
<dba-group>
ca. 450 MB
Partition 3

<oracle-user>:
<dba-group>
3 GB
Minimum; de-
pends on the
workload on the
database
tories
size
Partition 1
Database Index
<oracle-user>:
<dba-group>
3 GB
autoextend is on
per default
Partition 2
Mount point: /dp
Document Pipeline

/dp/DPDIR
<archive-user>:
<archive-group>
5 GB
Should hold the
data for at least
one working
week. Depends
also of the size of
the documents
(LargeFiles)
For database MS SQL: Recommended disk partitioning

Partition
Recommended size
Binaries for MS SQL
Binaries for Document Pipeline
D:\ 5.0 GB

Partition
Recommended size
default
Partition
Recommended size
Minimum; depends on
the workload on the
database
Partition
Recommended size
default
Document Pipeline N:\ 5 GB
Should hold the data for
at least one working
week. Depends also of
the size of the docu-
ments (LargeFiles)
3.8 Case 8: New installation of Document Pipelines
for Universal Archive and database on different
machines
For database Oracle : Recommended disk partitioning for Universal Archive
and path names are given in UNIX style. For Windows logical partitions with drive

tories
size
Partition 1
Binaries for Archive Server
(DB package)
<archive-user>:
<archive-group>
1.0 GB
Partition 2
Oracle binaries
<oracle-user>:
<dba-group>
1.7 GB
3.8 Case 8: New installation of Document Pipelines for Universal Archive and database on different machines

tories
size
Partition 3
logs
Online REDO logs
<oracle-user>:
<dba-group>
ca. 450 MB
tories
size
Partition 1
<oracle-user>:
<dba-group>
3 GB
autoextend is on
per default
Partition 2
mirr
files
<oracle-user>:
<dba-group>
ca. 450 MB
tories
size
Partition 1
Database Index
<oracle-user>:
<dba-group>
3 GB
autoextend is on
per default
Partition 2
Mount point: /dp
Document Pipeline

/dp/DPDI
R
<oracle-user>:
<dba-group>
3 GB
Minimum; de-
pends on the
workload on the
database
For database MS SQL: Recommended disk partitioning for Universal Archive

Partition
Recommended size
Binaries for MS SQL
Binaries for Archive Server (DB package)
D:\ 5.0 GB
Partition
Recommended size
default

Partition
Recommended size
minimum, depends on
the workload on the
database
Partition
Recommended size
default
Recommended disk partitioning UNIX/Linux and Windows for Document
Pipelines for Universal Archive
and path names are given in UNIX style. For Windows partitions with drive letters
and appropriate path names have to be used.

tories
size
Partition 1
ries
<archive-user>:
<archive-group>
2.0 GB

ca. 300 MB
Partition 2
Mount point: /dp
Document Pipeline
<oracle-user>:
<dba-group>
ca. 300 MB
Partition 3
Mount point: /dp
Document Pipeline

/dp/DPDIR
<archive-user>:
<archive-group>
5 GB
Should hold the
data for at least
one working
week. Depends
also on the size of
the documents
(LargeFiles)

Chapter 4

Guides
This chapter describes which guides are needed and in which order you have to
perform the installations or upgrades.
4.1 Guides needed for new installation
A separate guide exists for each package: database installation, Archive Server
installation and for several Document Pipeline installations.
The main order of performing them is the following:
1. Guide for database installation
2. Guide for Archive Server installation
3. Guides for Document Pipelines
It is possible to install each package separately or all at once. If several packages are
installed at once the associated guides must be consulted. Please keep this in mind!
4.1.1 Standard installation of Archive Server
A standard installation of an Archive Server consist of installing the database
binaries, configuring them, installing further Archive Server packages like the
Archive Server software, administration tools, Document Pipelines (e.g. for SAP)
and timestamp server. After installation of the Archive Server packages, you must
configure them via the browser as mentioned in the guides.
Guide for installation and configuration of database systems Oracle or MS
SQL
Chapter 4 Guides

Guide for installation and configuration of Archive Server
Archive Server 9.6.1 on UNIX with Oracle
Archive Server 9.6.1 on Windows with Oracle
Archive Server 9.6.1 on Windows with MS SQL
Guide for installation of Archive Administration Utilities
Archive Administration Utilities 9.6.1 (Unix/Windows)
Guide for installation and configuration of Open Text Document Pipeline SAP,
DocuLink (DL), Universal Archive (DPAPP, in case you want to use Universal
Archive)
Open Text Document Pipeline SAP 9.6.1
Open Text Document Pipeline DocuLink 9.6.1
Document Pipelines for Universal Archive 9.6.1
Document Pipelines for BPM 9.6.1
Open Text Document Pipeline Base 9.6.1
Open Text Document Pipeline Remote Interface 9.6.1
4.1.2 Remote DB
It is possible to create and use the Archive Server specific database files on a
dedicated database server.
Guide for installation and configuration of the database systems Oracle or MS
SQL on a dedicated database server and installation of the appropriate
database client software on the Archive Server machine
Installation and configuration of database server and client itself
4.1 Guides needed for new installation

Guide for installation and configuration of Archive Server
Archive Server 9.6.1 on UNIX with Oracle
Archive Server 9.6.1 on Windows with Oracle
Archive Server 9.6.1 on Windows with MS SQL
Guide for installation of Archive Administration Utilities
Archive Administration Utilities 9.6.1 (Unix/Windows)
Guide for installation and configuration of Open Text Document Pipeline SAP,
DocuLink (DL), Universal Archive (DPAPP, in case you want to use Universal
Archive)
Open Text Document Pipeline Base 9.6.1
4.1.3 Document Pipeline Standalone
Guide for installation and configuration of Open Text Document Pipeline SAP and DocuLink
(DL)
Chapter 4 Guides

4.1.4 Document Pipelines for Universal Archive
Guide for installation and configuration of the database systems Oracle or MS SQL on
dedicated database server or on the Archive Server and installation of the appropriate
database client software on the Document Pipeline machine
Installation and configuration of database itself
Guide for installation and configuration of Document Pipelines for Universal
Archive
4.1.5 Archive Cache Server
Guide for installation and configuration of Archive Cache Server
Archive Cache Server 9.6.1 (Unix/Windows)
4.1.6 Timestamp Server
Guide for installation of Timestamp Server
Timestamp Server 9.6.1 (Unix/Windows)
4.1.7 Remote Standby Server
Use the same guides and order for each Archive Server as mentioned in Standard
installation of Archive Server on page 23. Information about the configuration of
Remote Standby scenario can be found in Livelink ECM Archive Server
Administration Guide https://esc.ixos.com/1166032743-064.
4.2 Guides needed for update

4.1.8 Cluster installation
In case you want to install a cluster, please contact Open Text Global Services.
4.2 Guides needed for update
This section describes the update of the Archive Server version 9.6.0 to Archive
Server version 9.6.1.
See the hardware recommendations at https://esc.ixos.com/1173437775-907.
Note that an upgrade may increase the size of the database significantly. Take
care to provide enough additional disk space.
Updating Livelink ECM Archive Server 9.6.0 to 9.6.1 on UNIX
Updating Livelink ECM Archive Server 9.6.0 to 9.6.1 on Windows
Updating Livelink ECM Archive Cache Server (old) 9.6.0 to 9.6.1
Same update procedure as described in Archive Server guide. The order of the
updates is irrelevant.
Guides for upgrade to version 9.6.0
See the following sources to upgrade Archive Server versions before 9.6.0 to version
9.6.0.
If you would like to verify the upgrade path for your current Archive Server
version 5.5 or 9.5, please refer to the Upgrade Matrix
(https://esc.ixos.com/1142502499-852).
Which preparations are necessary for the upgrade? See
https://esc.ixos.com/1112968927-002.
If you have checked and prepared your current system for the upgrade, you can
continue and start the upgrade by following the instructions in the Upgrade
Guides referenced in this document: https://esc.ixos.com/1142502210-850

Chapter 5

Platform dependencies
This chapter describes the recommended Operating System parameters for the
Archive Server.
Since Oracle version 10g, Oracle itself checks the recommended OS parameters like
kernel parameters, recommended packages, and patch levels. All requirements of
Oracle can be found here:
https://www.metalink.oracle.com/metalink/plsql/f?p=130:14:119823325210179988
07::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_fram
e,p14_font:NOT,169706.1,1,1,1,helvetica
If this link returns an error, please copy them into the browser's address bar and try
it from there.
If the Archive Server needs other or special system parameters, they will be listed
here under the special chapter for the appropriate OS.
Caution
To avoid data loss due to power failure or other OS crashes, we strongly
recommend the use of journaling file systems on all OS.

5.1 AIX (IBM)
AIX 5.3 must have maintenance level 4 or higher.
Oracle validates and shows the recommended parameters, packages and OS patches
during the installation of Oracle itself. It is recommended to adjust your OS
parameters before this installation and just let Oracle check it again during
installation. To do that, run the validation tool from Oracle (Note: 334562.1):
1::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,
p14_font:NOT,334562.1,1,0,1,helvetica
Direct download (to use this link, you have to login in Oracle MetaLink):
https://www.metalink.oracle.com/cgi-
bin/cr/getfile.cgi?p_attID=334562.1:HCVEAIX_100705
If those links return an error, please copy them into the browser's address bar and
try it from there.
Chapter 5 Platform dependencies

Please also refer to the current installation guide of Oracle which can be found on
the Oracle web page
http://www.oracle.com/technology/documentation/database10gR2.html.
5.2 HP-UX 11.23 (PA-RISC 64bit, IA-64)
For HP-UX 11.23, apply QPKAPPS B.11.23 and QPKBASE B.11.23 dated from
December 2005.
1::::p14_data-
base_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:N
OT,334563.1,1,0,1,helvetica
bin/cr/getfile.cgi?p_attID=334563.1:HCVE022506
try it from there. Please also refer to the current installation guide of Oracle which
can be found on the Oracle web page
Kernel parameters:
Note: Be careful using much larger values, they might cause problems when
installing Oracle.

Kernel Parameter Minimum values
MAXFILES 2048
MAXFILES
_
LIM 2048
MAXUSERS Standard
NCALLOUT Standard
SEMUME 30
SHMMAX 1073741824
5.3 Linux Enterprise Server 9 (SUSE; i386 32-bit)
Online update must be from February 02, 2006, or later.
5.4 MS Windows Server 2003 platforms (i386 32-bit)

bin/cr/getfile.cgi?p_attID=334531.1:HCVE031106
try it from there.
the Oracle web page
The following packages have to be installed:
glibc-2.3.3, gcc-3.3.3, gcc-c++-3.3.3, libaio-0.3.98, libaio-devel-
0.3.98, make-3.80, openmotif-libs-2.2.2-519.1, orarun-1-8-31, compat
Kernel parameter for data seg size (ulimit) must be at least 256 MB (for jbd with
more than one jukebox, resp. big ISO cache).
5.4 MS Windows Server 2003 platforms (i386 32-bit)
Only for the Windows Server 2003 Standard Edition, Enterprise Edition and Datacenter
Edition.
installation. To do that, please refer to the current installation guide of Oracle which
can be found on the Oracle web page
Windows update must be from March 01, 2006, or later.
We recommend using the US version of Windows Server 2003 Editions.
Installing the Archive Server via Windows Terminal Server is not supported, as
you may encounter problems within Disk-Administrator or with Database-
Connectivity.
The system can only be used with Intel compatible 32-bit processors.
If HP Systems Insight Manager is running on your computer, make sure the HP
Systems Insight Manager is uninstalled or at least deactivated. This tool may
cause the Archive Server to hang.
Chapter 5 Platform dependencies

5.5 Solaris (SUN)
Solaris is only supported on SPARC architectures.
Use the latest kernel patch from Sun Microsystems. Sun provides patch information
at http://sunsolve.sun.com (January 2006 or newer).
installation.
To do that, run the validation tool from Oracle (Note: 334567.1):
https://www.metalink.oracle.com/cgi-bin/cr/getfile.cgi?p_attID=334567.1:HCVE
If those links return an error, please copy them into the browsers' address bar and
try it from there.
the Oracle web page
The following packages have to be installed:
SUNWarc, SUNWbtool, SUNWlibm, SUNWlibms, SUNWsprot, SUNWtoo, SUNWhea,
SUNWzlib, SUNWbzip
Kernel parameter for data seg size (ulimit) must be at least 256 MB (for jbd with
more than one jukebox, resp. big ISO cache).

1 Installation and Upgrade Overview 9.6.1

Uploaded by

Document Information

Original Description:

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

1 Installation and Upgrade Overview 9.6.1

Uploaded by

Copyright:

Available Formats

Livelink

ECM Archive Server 9.6.1

ECM Archive Server 9.6.1

and SAP ArchiveLink

are registered trademarks of SAP AG.

is a trademark of Adobe Systems Incorporated.

and Lotus Notes

are registered trademarks of Lotus Development Corporation. Domino is a trademark of Lotus

and Microsoft SQL

is a registered trademark of Oracle Corporation.

is a registered trademark of the Mozilla Foundation.

HTML Export 2002

You might also like