OpenText Archive Center 16 2 Installation Guide For UNIX Linux English AR160200 00 IGU en 02 PDF

OpenText™ Archive Center
Installation Guide for UNIX/Linux
This guide describes the setup of OpenText Archive Center 16

EP2, including Archive Server and additional components, on
UNIX® or Linux® systems.
Further, the installation of OpenText™ Archive Cache Server is

included.
AR160200-00-IGU-EN-02
OpenText™ Archive Center
Installation Guide for UNIX/Linux
AR160200-00-IGU-EN-02
Rev.: 2017-Apr-25
This documentation has been created for software version 16.2.
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 Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2017 Open Text. All Rights Reserved.

Trademarks owned by Open Text.
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 About OpenText Archive Center v
1 Prerequisites for Archive Center ............................................. 9

1.1 Configuring basic settings ................................................................ 10
1.1.1 Hardware and software recommendations ........................................ 10
1.1.2 Network recommendations and restrictions ....................................... 11
1.1.3 Testing network environment ........................................................... 12
1.1.4 Checking computer name ................................................................ 12
1.1.5 Setting access rights and exporting mount points .............................. 12
1.2 Installing Java ................................................................................. 13
1.3 Setting up Apache Tomcat ............................................................... 14
1.3.1 Installing Tomcat ............................................................................. 14
1.3.2 Configuring the connector and securing Tomcat ................................ 14
1.3.3 Configuring options and paths for Tomcat ......................................... 16
1.4 Setting up Directory Services ........................................................... 18
1.4.1 Configuring OTDS ........................................................................... 19
1.4.2 Scenario-specific settings ................................................................ 21
1.5 Further preparations ........................................................................ 21
2 Setting up the database .......................................................... 23

2.1 Setting up Oracle Database ............................................................. 23
2.1.1 Database characteristics ................................................................. 23
2.1.2 Remote database on Oracle RAC .................................................... 24
2.1.3 Testing the database ....................................................................... 24
2.1.4 Required database parameters ........................................................ 25
2.2 Setting up PostgreSQL .................................................................... 26
2.2.1 Installing and configuring PostgreSQL .............................................. 26
2.2.2 Creating the database ..................................................................... 27
2.3 Setting up SAP HANA ..................................................................... 28
3 Installing Archive Center and additional components ........ 29

3.1 Obtaining and running the setup files using System Center ................ 29
3.2 Using the Content Suite Platform Installer ......................................... 30
3.3 Installing Archive Center .................................................................. 32
3.4 Installing Archive Monitoring Server .................................................. 36
3.5 Installing Document Pipeline Base ................................................... 37
3.6 Installing Document Pipeline for Archive Center CMIS ....................... 38
3.7 Installing Document Pipeline Info ..................................................... 39
OpenText Archive Center – Installation Guide for UNIX/Linux iii

AR160200-00-IGU-EN-02
Table of Contents
3.8 Installing Solution Registry Agent ..................................................... 40

3.9 Concluding the installation ............................................................... 40
3.9.1 Setting the ECM_VAR_DIR variable ................................................. 41
3.9.2 Setting the directory for the search index .......................................... 41
3.9.3 Configuring for Application Layer usage ............................................ 41
3.9.4 Adjusting non-default ports .............................................................. 43
3.9.5 Executing the schema script manually (SAP HANA only) ................... 43
3.9.6 Installing patches ............................................................................ 44
3.9.7 Starting Apache Tomcat and Archive Spawner .................................. 44
3.9.8 Final steps ...................................................................................... 45
4 Configuring Archive Center .................................................... 47

4.1 Signing in to Archive Server in Administration Client .......................... 47
4.2 Changing the dsadmin password ..................................................... 47
4.3 Changing the password of the database user .................................... 48
4.3.1 Oracle Database only: Checking the expiry date of the password ....... 48
4.4 Configuring different internal and external hostname ......................... 49
4.5 Configuring certificate authentication for Archive Center Proxy ........... 49
5 Setting up Archive Cache Server ........................................... 51

5.1 Prerequisites .................................................................................. 51
5.2 Installing Archive Cache Server ....................................................... 53
5.3 Concluding the installation ............................................................... 55
5.4 Enabling certificates ........................................................................ 55
6 Appendix: Setting up the database in Oracle Database ...... 57

6.1 Setting up Oracle Database server ................................................... 57
6.1.1 Creating the test database ............................................................... 57
6.1.2 Creating the database user .............................................................. 60
6.1.3 Configuring the Oracle Listener ........................................................ 62
6.1.4 Configuring Oracle TNS Service Names ........................................... 63
6.1.5 Post-installation tasks ...................................................................... 64
6.2 Oracle Database and Archive Spawner on one computer .................. 64
7 Appendix: Special commands and other OS-specific

topics ........................................................................................ 65
7.1 Special issues of Red Hat Linux systems .......................................... 65
7.1.1 Stopping or starting Archive Center .................................................. 65
7.1.2 Solving problem with dsh command validUser ................................... 66
7.2 Special issues of SUSE Linux systems ............................................. 66
iv OpenText Archive Center – Installation Guide for UNIX/Linux

AR160200-00-IGU-EN-02
Preface
About OpenText Archive Center
OpenText Archive Center is a lean, easy-to-install, easy-to-maintain archiving
solution based on the well-established core component Archive Server. It offers basic
metadata handling using a CMIS interface and supports various data sources, for
example, SAP systems and file archiving.
Note: Archive Center 16 EP2 can be used with or without the services
provided by the Application Layer. In the latter case, Archive Center continues
the feature set of previous Archive Server versions (10.5.0 and before).
For more information, see also OpenText Archive Center - Administration Guide
(AR-ACN).
Archive Center OpenText™ Archive Center Administration is a web-based, easy-to-use client

Administration included in Archive Center.
OpenText Archive Center customers, called tenants, administrate the archiving of

content and documents from their system to Archive Center. The archiving activities
are defined and controlled by specific collections.
DPs Archive Center uses Document Pipelines (and their “DocTools”) to import
documents in various scenarios. For more information, see also OpenText Document
Pipelines - Overview and Import Interfaces (AR-CDP).
Access OpenText™ Archive Center Access is a web-based, easy-to-use client included in

Archive Center, which allows access to the archive independently from the
archiving application.
This can, for example, be important in case of impending litigation. Using the
Archive Center Administration client, collections can be put on hold to protect all
currently archived documents from modification and deletion. The archived
documents within the collection can then be searched and all relevant documents
can be exported.
My Archive OpenText™ My Archive, similar to Access, is an easy-to-use web client that allows
access to the archive. In contrast, it allows individual users to access their archived
documents. Users can view, search, and download the documents only if they have
appropriate rights.
Proxy OpenText™ Archive Center Proxy is an easy to set up and maintain client, which
securely connects the customer’s network with the cloud-based Archive Center and
also provides caching functionality. For more information, see OpenText Archive
Center Proxy - Installation Guide (ARPRX-IGD).
Archive Cache This guide also covers the installation of OpenText™ Archive Cache Server; see
Server “Setting up Archive Cache Server“ on page 51. If you want to use the Application
Layer of Archive Center in multi-tenant configuration, you must use Archive Center
OpenText Archive Center – Installation Guide for UNIX/Linux v

AR160200-00-IGU-EN-02
Proxy. Do not use Archive Cache Server in this case. Archive Cache Server continues
the caching features of previous Archive Server versions (10.5.0 and before).
Related documentation
Product docu- The following documentation is available for Archive Center on OpenText My
mentation Support (https://knowledge.opentext.com/docs):
• OpenText Content Suite Platform - Installation Overview (SULC-IGD)
This guide provides an overview of the installation and deployment process for
OpenText™ Content Suite Platform.
• OpenText Archive Center - Administration Guide (AR-ACN)
This guide describes all configuration-related and administration-related aspects
of OpenText™ Archive Center.
• OpenText Archive Center - Scenario Configuration Guide (AR-CGD)
This guide describes the setup of scenarios for Archive Center, including
prerequisites and the usage of the applications OpenText™ Archive Center
Administration and OpenText™ Archive Center Access.
• OpenText Archive Center - Cluster Installation Guide (AR-ICLU)
This guide describes how to set up Archive Center as a highly-available and
data-secure active-active cluster.
• OpenText Archive Center Proxy - Installation Guide (ARPRX-IGD)
This guide describes the installation and usage of OpenText Archive Center
Proxy.
• OpenText Archive Center Administration - Online Help (ARBA-H-AGD), OpenText
Archive Center Access - Online Help (ARAC-H-AGD), OpenText My Archive - Online
Help (ARMA-H-UGD)
Online help is available for Archive Center Administration, Archive Center
Access, and for My Archive.
• OpenText Document Pipeline - Installation and Upgrade Guide (AR-IDPDP)
This guide describes the installation and upgrade of the Document Pipeline
components not covered by this guide: OpenText Document Pipeline for SAP
Solutions, OpenText Document Pipeline for DocuLink, and OpenText Document
Pipeline for Enterprise Library.
• OpenText Document Pipelines - Overview and Import Interfaces (AR-CDP)
This guide describes concepts, tools, and scenarios of OpenText™ Document
Pipeline and gives detailed information on the standard DocTools.
Release Notes The Release Notes describe the following aspects in detail:
• The software supported by the product.
• Requirements.
vi OpenText Archive Center – Installation Guide for UNIX/Linux

AR160200-00-IGU-EN-02
• Restrictions.
• Important dependencies.
• Last-minute changes regarding the documentation.
• Identification codes of the current documentation.
The Release Notes are continually updated. The latest version of the Archive Center
Release Notes is available on OpenText My Support (https://
knowledge.opentext.com/knowledge/llisapi.dll/Overview/52230169).
OpenText Archive Center – Installation Guide for UNIX/Linux vii

AR160200-00-IGU-EN-02
Chapter 1
Prerequisites for Archive Center
3rd-party The following software has to be installed on the computer before you install the
software Archive Center components:
Database
Archive Center requires Oracle® Database 12c, PostgreSQL 9.6, or SAP® HANA.
Except for SAP HANA, the database can be installed locally or on a remote
system.
Java
Archive Center requires Java™ Development Kit 8.0 or Java™ Runtime
Environment 8.0.
Application server
Archive Center requires Apache® Tomcat™, version 8.5.8 or later.
Cluster
If you plan to install a clustered Archive Center environment, see OpenText
Archive Center - Cluster Installation Guide (AR-ICLU) before you continue.
Tip: The following marker is used to indicate when you must deviate for a
cluster installation:
Cluster topic
General Do the following to ensure a successful installation of Archive Center:

settings
Basic settings
See “Configuring basic settings” on page 10 for recommended settings.
OpenText Directory Services

Directory Services (OTDS) can either be installed locally or remotely, and you
can either use an existing instance or install a new one. Depending on which
landscape you want to use, the installation paths differ. For more information,
see “Setting up Directory Services” on page 18.
Cluster topic: OTDS must be installed (locally or remote) before you can install
the cluster nodes as the OTDS resource identifier is required for installation.
For more information, see Section 1.2 “Prerequisites for the cluster installation” in
OpenText Archive Center - Cluster Installation Guide (AR-ICLU).
Windows® system
OpenText™ Administration Client is required to perform the administrative and
configuration tasks of Archive Center.
OpenText Archive Center – Installation Guide for UNIX/Linux 9

AR160200-00-IGU-EN-02
Chapter 1 Prerequisites for Archive Center
Administration Client can only be installed on Windows systems. Any

supported, remote Windows system will do as long as it can access the Archive
Center host.
Administration Client is a snap-in for Microsoft Management Console (MMC).
Administration Client requires the Microsoft products .NET Framework 4.5.1,
and MMC 3.0 installed on the same computer. On Windows Server 2012, check
whether these features are enabled.
Conventions The following variables are conventions for this documentation:

• The installation directory for Archive Center is called <OT install AC>.
The default value is /opt/opentext/ArchiveServerSoftware_16_2_0.
• The directory for configuration data is called <OT config AC>.
The default value is /opt/opentext/ArchiveServerConfig_16_2_0.
Procedure
• “Installing Java” on page 13
• “Setting up Apache Tomcat” on page 14
• “Setting up Directory Services” on page 18
1.1 Configuring basic settings

Do the following to avoid problems during installation or runtime.
1.1.1 Hardware and software recommendations

Paging space The amount of paging space should be about the same as the amount of RAM.
Prerequisites for hard disk systems

• Enterprise-ready disk arrays are used.
• High-performance and random access to data and file system metadata (for
example, directory structures) is provided.
• Multi-threaded access is provided.
• Standard file system calls (read, write, stat, delete, etc.) always return results
comparable to locally attached hard disks.
• Disks are protected against data loss by backup or similar technologies.
Hard disk layout Most disks for Archive Center must be mirrored with RAID 1, and there must be at
least three independent disks. The secure operation of the database requires one disk
for the database and two separate disks for the log files. Archive Center stores all
documents temporarily on hard disk. This disk must be protected by RAID 5 or
RAID 1.
For the disk layout of an Oracle Database, see the Oracle documentation (http://
www.oracle.com/pls/db112/homepage).
10 OpenText Archive Center – Installation Guide for UNIX/Linux

AR160200-00-IGU-EN-02
1.1. Configuring basic settings
Unwanted frag- Be aware that the file system may fragment disk partitions in an undesirable
mentation manner, depending on the used type of file system. This can lead to incorrect free
space detection, causing attempts to write data to the file system to fail, resulting in
a “no space left on device” message.
1.1.2 Network recommendations and restrictions

Static IP The Archive Center host requires a static IPv4 or IPv6 address. In particular, the
address local hostname must not be resolved to the loopback addresses (::1 or 127.0.0.1)
but the full IP address.
To verify correct resolving of IP addresses:
1. On the Archive Center host, run

ping <Archive Center hostname>
The configuration is correct if the external IP address shows up in the output.
2. If only the loopback addresses are resolved, edit the /etc/hosts file.
Remove the <Archive Center hostname> entry from lines starting with ::1 or 127.
0..
Keep the 127.0.0.1 localhost entry.
Ports to open Archive Center requires the following ports, which must be configured in the
firewall:
RPC
Tools and administration interface: 4020, 4027, 4030, 4032, 4033, 4034
TCP
HTTP/HTTPS ports for Tomcat as defined in the server.xml file (default: 8080,
8090)
Cluster topic:
Default Hazelcast cluster ports for three nodes: 5701, 5702, 5703
Port for the load balancer: 8009 (in case of Apache mod_jk)
Enforcing In mixed IPv4/IPv6 environments, you may need to enforce preferred usage of one
protocol of the protocols.
After the installation, see “Enforcing protocol” on page 45 for more information.

AR160200-00-IGU-EN-02
1.1.3 Testing network environment

Test the connections between Archive Server and your leading application on <server
name> (ensure that lookup and reverse lookup are working in your network):
ping <server name>

and on <server name>
ping <archive server name>
Do the same for the connection to the Enterprise Scan, if you use the mass scanning
scenario. Make sure that lookup and reverse lookup are working. If you are using a
remote database, do the same for the database server.
1.1.4 Checking computer name

Important
Ensure that the name of the computer hosting Archive Center does not
contain any underscores (“_”).
1.1.5 Setting access rights and exporting mount points

Prerequisites The following prerequisites must be met:
• root has to use a Bourne shell or compatible (ksh, msh, or bash. Do not use csh!).
To find out, use root>> echo $SHELL
• For all directories and partitions used for Archive Center, the owners must be
user <otuser> and group <otgroup>: OpenText binaries, disk buffer, DP directory,
cache, burn buffer, WORM file system and partitions for hard disk pools. The
access permissions should be 755 (drwxr-xr-x).
• Oracle Database only: For all Oracle directories, the owners must be the user and
group that are used for Oracle software installation (default: oracle or oinstall
user and dba group.
In all cases, the access permissions should be 755 (drwxr-xr-x).
• The directories /views_raw and /views_hs have been created. They must be
owned by <otuser>:<otgroup> with permissions 750 (drwxr-x---).
Exporting The mount points (/views_raw and /views_hs) for the Storage Manager have to be
mount points exported to NFS.
To export the mount points:
1. Add the two following lines in the /etc/exports file:
SUSE
/views_hs *(insecure,no_subtree_check,rw,root_squash,sync)
/views_raw *(insecure,no_subtree_check,rw,root_squash,sync)

AR160200-00-IGU-EN-02
1.2. Installing Java
RED HAT
/views_hs *(insecure,rw,root_squash,sync)
/views_raw *(insecure,rw,root_squash,sync)
2. Export all file systems for the current session.
Note: On SUSE, you first need to install the “exportfs” package. Run the
following command:
zypper install nfs-kernel-server
Run the following command:
root>> /usr/sbin/exportfs -a
3. Check with showmount -e if the file systems are shared correctly. If there are
errors, restart the NFS service and try it again. The command to run depends on
the operating system and its version.
Example:
systemctl enable nfs-server.service

systemctl start nfs-server.service
systemctl status nfs-server.service
4. If you have changed any of the settings described above, reboot the system.
1.2 Installing Java

To install Java:
1. Download the Java Development Kit (JDK), version 8 Update 71 (64-bit) or later,
from the Oracle website (http://www.oracle.com/technetwork/java/javase/
downloads/index.html).
Note: Oracle only offers the latest version over the above link. When Java
8 is no longer available, you can get it from the Oracle Support pages
(https://support.oracle.com/epmos/faces/DocumentDisplay?id=1439822.1).
OpenText recommends running Archive Center with the current JDK update
version to avoid security and stability issues.
2. Install the JDK according to the instructions.
3. For known issues concerning the installation of Java and troubleshooting

information, see also this article in the OpenText Knowledge Base (https://
knowledge.opentext.com/knowledge/cs.dll/kcs/kbarticle/view/KB2851395).

AR160200-00-IGU-EN-02
1.3 Setting up Apache Tomcat

Cluster topic: For more information, see Section 1.2 “Prerequisites for the cluster
installation” in OpenText Archive Center - Cluster Installation Guide (AR-ICLU).
OpenText recommends the following steps to install and configure Tomcat before
installing Archive Center on UNIX or Linux:
• Create the installation user <otuser> and group <otgroup> to be used with Tomcat.
See also “User for Archive Center” on page 21.
• Install Tomcat.
• Configure the connectors and SSL/TLS for Tomcat.
• Configure options, paths, and further Tomcat components.
1.3.1 Installing Tomcat

To install Tomcat:
1. Download the Apache Tomcat software version 8.5.8 or later from https://
tomcat.apache.org/download-80.cgi.
2. If necessary, create the operating system user and group to be used with
Tomcat.
Important
Do not use root. It can create security vulnerabilities when running the
application server using a root (or equivalent) user.
3. Log on as this user.
4. Install the Tomcat software according to the documentation.
5. Open the $CATALINA_HOME/conf/logging.properties file in an editor.
6. In the line starting with .handlers = ..., remove the entry java.
util.logging.ConsoleHandler and save the file.
1.3.2 Configuring the connector and securing Tomcat

To use secure connections with TLS (Transport Layer Security; often also referred to
as SSL, Secure Sockets Layer), add a connector for HTTPS in the Tomcat
configuration. You may have to open ports on your routers when adding ports for
SSL/TLS. Further, automatically redirect clients that access a page with a security
constraint requiring SSL/TLS.

AR160200-00-IGU-EN-02
1.3. Setting up Apache Tomcat
Important
When enabling SSL/TLS, OpenText recommends using a server certificate
from a Certificate Authority. The root certificate must be trusted by the JRE
or JDK and correctly installed in the keystore (for example, <JAVA_HOME>/
lib/security/cacerts).
For information about enabling SSL/TLS, see the Tomcat SSL Configuration
HOW-TO (https://tomcat.apache.org/tomcat-8.0-doc/ssl-howto.html).
To configure Tomcat for SSL/TLS:
1. From the <Tomcat_home>/conf directory, open server.xml in an editor.

2. Ensure that APR Listener is commented out, for example:

3. After the line <Service name="Catalina">, define an HTTP connector port

according to the example.
Example:

<Connector port="8080"
protocol="HTTP/1.1"
redirectPort="8090"
connectionTimeout="20000"
disableUploadTimeout="true"
enableLookups="false"
/>
Note: protocol must be set to HTTP/1.1 (default).

disableUploadTimeout must be set to true (default).
enableLookups must be set to false (default).
4. After the line <Service name="Catalina">, define an SSL connector port.

Ensure that the redirectPort from the previous step matches the SSL
connector port, as shown in the following example.
Example:

<Connector port="8090"
SSLEnabled="true"
scheme="https"
secure="true"
sslProtocol="TLS"
sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"
protocol="HTTP/1.1"
acceptCount="100"
maxHttpHeaderSize="8192"

AR160200-00-IGU-EN-02
maxThreads="150"
minSpareThreads="25"
algorithm="SunX509"
clientAuth="false"
disableUploadTimeout="true"
enableLookups="false"
keystoreFile="<path to keystore file>"

keystorePass="<password for the keystore>"
keyAlias="<yourKeyalias>"
keystoreType="<pkcs12 OR jks>"
/>
Notes
• If you want installations of Archive Center Proxy to use a certificate to
authenticate against Archive Center (rather than user and password), set
clientAuth to want.
• protocol must be set to HTTP/1.1 (default).
Do not use protocol="org.apache.coyote.
http11.Http11AprProtocol".
• disableUploadTimeout must be set to true (default).
enableLookups must be set to false (default).
5. Save the file and restart Tomcat.
Further For more information, see the Tomcat SSL Configuration HOW-TO (https://
information tomcat.apache.org/tomcat-8.0-doc/ssl-howto.html).
1.3.3 Configuring options and paths for Tomcat

setenv.sh Configure the setenv.sh file to achieve a high-performance system.
To configure options and paths for Tomcat:
1. In the <Tomcat_home>/bin directory, create a file called setenv.sh owned by

the user <otuser> and the group <otgroup> (if not present already).
2. Configure the following settings in the setenv.sh file.
a. Set the maximum Java heap size to at least 2 GB (-Xmx2048m).

b. Set Abstract Window Toolkit to be used “headless” (-Djava.
awt.headless=true; required by the included XML parser).
c. Set the SHARED_LIB_PATH variable to the lib directory of Archive Center.
<OT install AC> is the path to the directory into which Archive Center is
or will be installed.
CATALINA_OPTS="‑Xmx2048m ‑Djava.awt.headless=true $CATALINA_OPTS"

AR160200-00-IGU-EN-02
1.3. Setting up Apache Tomcat
SHARED_LIB_PATH=<OT install AC>/lib

LD_LIBRARY_PATH=$SHARED_LIB_PATH:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
context.xml Configure an option in the context.xml file to avoid issues with the Cookie
Processor component of Tomcat.
Note: This step is only required if Archive Center must support OpenText
Archive Center Proxy.
To configure the Cookie Processor component:
1. In the <Tomcat_home>/conf directory, open the context.xml in an editor.

2. Add the following line within the <Context> element:
<CookieProcessor className="org.apache.tomcat.util.http.
LegacyCookieProcessor" />
Example:
...
<Context>


<WatchedResource>WEB-INF/web.xml</WatchedResource>
<WatchedResource>${catalina.base}/conf/web.xml</
WatchedResource>
<CookieProcessor
className="org.apache.tomcat.util.http.LegacyCookieProcessor" />


</Context>
3. Save the context.xml file and restart Tomcat.

AR160200-00-IGU-EN-02
1.4 Setting up Directory Services

Depending on which landscape you want to use, see the corresponding item below.
See “Configuring OTDS” on page 19 for information related to all scenarios. See
“Scenario-specific settings” on page 21 for further important information for your
scenario.
• Local, new installation of OTDS
First install OTDS only. For more information, see OpenText Directory Services -
Installation and Administration Guide (OTDS-IWC).
In the OTDS web administration client, create a resource for Archive Center and
keep a note of the resource ID. For more information, see OpenText Directory
Services - Installation and Administration Guide (OTDS-IWC).
Afterwards, install Archive Center. When asked by the Archive Server setup
(Step 16), enter the OTDS credentials and the resource ID.
• Remote, new installation of OTDS
First install OTDS on the remote computer. In the OTDS web administration
client, create a resource for Archive Center and keep a note of the resource ID.
For more information, see OpenText Directory Services - Installation and
Administration Guide (OTDS-IWC).
• Local, existing installation of OTDS
(Step 16), enter the OTDS credentials and the resource ID. Do not use localhost
as the Server name but the fully-qualified name.
• Remote, existing installation of OTDS
Cluster topic: For more information, see Section 2.1 “Distributing OTDS key” in
Related Topics
• “Prerequisites for Archive Center“ on page 9

AR160200-00-IGU-EN-02
1.4. Setting up Directory Services
1.4.1 Configuring OTDS

The following settings are required to use OTDS successfully in all scenarios:
Partition, groups, and users

User information from Active Directory must be mapped to OTDS. OTDS
provides a connector to push changes of user information to Archive Center.
The connector is configured through the (synchronized) resource; see Resource
on page 19 below.
For more information, see Section 4.5 “Synchronized User Partitions” in
OpenText Directory Services - Installation and Administration Guide (OTDS-IWC).
Further, Archive Center requires the following technical partition, groups, and
users.
• A non-synchronized partition named, for example, OTInternal. This

partition must be added to the access role of Archive Center.
The technical users for the Application Layer will be added to this partition
when creating tenants, for example, ba.tenant@OTInternal.
• A user named system.cmis within the OTInternal partition. The password
should never expire. You do not need to remember the password as system.
cmis is only used as a technical user for the Application Layer (Archive
Center CMIS).
• A group called $PushConnector with an assigned user called, for example,
pushconnector.
• The access role of Archive Center requires the Include Groups from OUs
setting.
For more information, see Section 7.7 “Including/excluding groups from
organizational units” in OpenText Directory Services - Installation and
Administration Guide (OTDS-IWC).
Resource
Archive Center is represented in OTDS by a resource (a unique name and an
identifier). You can create the resource in the OTDS web client, or you can use a
wizard in OpenText Administration Client to create the resource after Archive
Center has been installed. In the latter case, select the “local user management”
option during the installation of Archive Center (Step 16).
Cluster topic: The OTDS resource must be created before the installation of the
cluster nodes. In particular, you cannot use the Administration Client wizard.
When creating the resource in the OTDS web administration client, specify the
following:
• General page
Enter any Resource name, for example: AC_server1.

AR160200-00-IGU-EN-02
• Synchronization page
Select User and group synchronization.
From the Synchronization connector list, select Archive Center.
In the This connector will area, select Create users and groups, Modify
users and groups, and Delete users and groups.
• Connection Information page
As Base URL, enter <protocol>://<server>:<port>/as_cmis/otdspc
Example: https://archive.example.com:8090/as_cmis/otdspc
As User Name, enter the user assigned to the $PushConnector group (see
Partition, groups, and users on page 19), for example: pushconnector.
Enter any Password compliant with the password policy.
For more information, see Section 6.2.2 “Creating a synchronized resource” in

Impersonation right
Directory Services requires the “impersonate user” right.
For more information, see Section 6.3 “Configuring access to your resources” in
Attribute mapping configuration

The OTDS user attribute mapping and group attribute mapping depend on the
scenario. See “Scenario-specific settings” on page 21.
For more information, see also Section 6.2.1.3 “Using resource attribute
mappings” in OpenText Directory Services - Installation and Administration Guide
(OTDS-IWC).
ACLs
The CMIS ACLs must be based on OTDS user IDs (not on the user name).
Names of users and groups are treated case-insensitive in OTDS, while CMIS
allows for case-sensitive names. If the ACLs are based on the user name it can
happen that permissions are not mapped correctly, because CMIS distinguishes
between, for example, access.default@OTInternal and access.
default@otinternal.

AR160200-00-IGU-EN-02
1.5. Further preparations
1.4.2 Scenario-specific settings

To run Archive Center scenarios, Directory Services is mandatory. In particular,
OTDS is used for the following scenarios:
FILE SHARE
Use Directory Services to let file share users be able to access their files using a
CMIS interface. File share users are mapped to Directory Services users.
Attribute mapping configuration

The oTExternalSID field must include objectSID, in the %s format.
MY ARCHIVE
Use Directory Services to let users have web access to their archived documents
through My Archive. You must allow the corresponding Directory Services
users to access Archive Center by adding them to the access role of Archive
Center.
My Archive users must be members of the OTDS group OTInternal
\<tenant>_UG, either directly or through another group membership.
1.5 Further preparations

Release Notes See the Release Notes on My Support (https://knowledge.opentext.com/knowledge/
cs.dll/Open/12331031) for further requirements to install Archive Server successfully.
Mandatory The following settings are important for a successful installation. Ensure the
settings following:
• /usr/sbin is part of the PATH for user root.
• The JDK or JRE is included in the PATH environment variable:
Enter root>> java -version
If the result is “command not found” or if the version displayed is not 1.8.0 or
later, expand the PATH variable to include the location of a valid JRE.
Test again as described.
• The umask of root is 022 (may be displayed as 0022).
To find out, use root>> umask
ksh Ensure that ksh (Korn shell) is installed, which is not available by default on certain
systems, and is required by the Archive Server setup. Use the package manager of
your system to install the ksh package.
User for Archive Center

You have to create an intended user and group before you start the installation. We
will call this user <otuser> and this group <otgroup>, for example, otxadm and group
otxsys. However, remember that the user for running the application server and the
user for starting Archive Spawner must be the same.

AR160200-00-IGU-EN-02
The password of the user can only consist of the following characters: a-z A-Z 0-9 !
§ % & / ( ) = ? { [ ] } \ * + ~ ' # <> | ; , : . - _ ^ and blank.
When you create the user (group), ensure that all partitions previously marked as
read/writable for the daemon/bin user (group) are now altered to the new OpenText
user (group). Preferably, change the owner and group of the corresponding
directories to the values chosen above: disk buffer, DP directory, cache, burn buffer,
exchange directory, and partitions for hard-disk pools.
Cluster topic: Ensure that the user and group IDs for <otuser> and <otgroup> are the
same on all nodes. Otherwise, the access to Single File (SF) storage will fail when
creating files for user with one ID and trying to modify them from another node with
another user ID. In particular, take care if you create the users manually instead of
importing them from a global system for all nodes.
Increasing file limits

Open files limit In general, the default number of files that can be opened simultaneously is too low
for Archive Center. For example, the default value on Red Hat is 1024, while the
recommend value is 15000.
File size limit The file size limit for the user running Tomcat must be at least 1 GB. If larger ISO
images are to be written, the limit will have to be accordingly higher.
To check the currently used limits:
1. On the Archive Server host, sign in as <otuser>.
2. Open a shell and run the following command:

ulimit -a
3. Check the limits as follows:
• If the shown limit of open files (open files line) is lower than 15000, consult
your system administrator to increase the value.
Note: The recommended way to increase the limit strongly depends on

the operation system.
• The shown file size limit (fsize or file size line) is given as multiple of
512 byte blocks.

AR160200-00-IGU-EN-02
Chapter 2
Setting up the database
Archive Center supports Oracle Database, PostgreSQL, and SAP HANA.
2.1 Setting up Oracle Database

You can either use an existing database or create a new database. The database can
reside on the computer on which Archive Server is installed or on a dedicated
database server.
The Oracle server or client software has to be installed beforehand. A database and a
database user must have been created. For mandatory settings of the database for
Archive Center, see “Database characteristics” on page 23.
For a detailed instruction how to install an example database for Archive Center, see
“Appendix: Setting up the database in Oracle Database“ on page 57.
2.1.1 Database characteristics

The following requirements for Archive Server database are mandatory.
• The database character set must be AL32UTF8. To verify, execute
select value from nls_database_parameters where

parameter='NLS_CHARACTERSET';
• The national character set must be AL16UTF16 – Unicode UTF-16 Universal
character set. To verify, execute
select value from nls_database_parameters where

parameter='NLS_NCHAR_CHARACTERSET';
• The ARCHIVELOG mode must be set. To verify, execute
select log_mode from v$database;

• The database must be configured to support at least 200 processes. To verify,
execute
select value from v$parameter where name = 'processes';
This value depends on the web server configuration value for the maximum
number of supported threads. For Tomcat, this is the maxThreads connector
parameter. Set the database processes parameter to maxThreads + 50.
• There must be at least two non-default tablespaces with a block size of 8 KB for
Archive Center data and index, respectively. These tablespaces must not be
named data and index. To verify, execute
select tablespace_name, block_size from dba_tablespaces;

AR160200-00-IGU-EN-02
Chapter 2 Setting up the database
• The database user provided for Archive Center must have the system and object
privileges listed in “Creating the database user” on page 60.
• The listener must be configured to support TCP/IP.
2.1.2 Remote database on Oracle RAC

If a remote database resides on an Oracle Real Application Cluster (RAC), you must
adapt the tnsnames.ora file.
To use a remote database with Oracle RAC:
1. Open the tnsnames.ora file in an editor.

2. Extend tnsnames.ora to include a TNS service name that points to the cluster
host and the SID of the cluster.
Example:
RACLINUX =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac-cluster01.example.com)
(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ORCL)
)
)
3. Before starting the Archive Server setup, ensure that at least one dedicated node
is running.
4. During the Archive Server setup, enter the following database parameters:
• Enter the TNS service name from Step 2.

• As database server, use the cluster host name, not the name of a dedicated
node.
• As Oracle SID, use the SID of the cluster, not the SID of the instance running
on a dedicated node.
2.1.3 Testing the database

To ensure that the database has all the required features, run the
StPreSchemaCreateOracle.sql check script in a command shell. You can find the
script in the Schema and Pre-upgrade checks for AC 16.zip file, which is available
on My Support (https://knowledge.opentext.com/knowledge/cs.dll/Overview/
62940896).
Process the script as follows (the example uses the default settings):
Note: The following environment variables must be set correctly:

ORACLE_HOME, TNS_ADMIN.

AR160200-00-IGU-EN-02
2.1. Setting up Oracle Database
sqlplus ecr/ecr@ecr_<db_host>
To test the characteristics of the database, enter:
@StPreSchemaCreateOracle.sql
You are prompted for the data and index tablespace name.
The script must not yield any messages beginning with FATAL:.
If you do not get any FATAL: messages, the configuration of connection and user is
correct.
Important
Ensure that the owner of the Apache Tomcat process has at least read access
on the file $ORACLE_HOME\network\admin\tnsnames.ora
2.1.4 Required database parameters

Ask your database administrator about the database parameters required by the
installation.
Table 2-1: Database parameters required by the installation
Parameter name Description Default

Database Server Database Server –
Database Port Port used for connections to the database 1521
Database User Name of the database user ecr
Database Password Password of the database user –
Oracle Service TNS service as configured by the Oracle Net ecr_<database
Configuration Assistant server>
Oracle SID System identifier of the database ECR
Data Tablespace Data tablespace ECR_DATA
Index Tablespace Index tablespace ECR_INDEX
TNS Admin Directory where the Oracle net $ORACLE_HOME/
Directory configuration files are to be found network/admin
Oracle Home Directory of the Oracle installation The directory ...
Directory
If you use Oracle server: ... of the Oracle server
installation
If you use Oracle client: ... of the Oracle client
installation.
If you use Oracle instant client: ... to which the Oracle
instant client package
was unpacked.

AR160200-00-IGU-EN-02
2.2 Setting up PostgreSQL

Version Archive Center requires PostgreSQL version 9.6.
Note: PostgreSQL 9.6 may not be available from the default package
repositories. For more information, see the PostgreSQL website (https://
www.postgresql.org/download/).
2.2.1 Installing and configuring PostgreSQL

Database server
On the computer that will host the PostgreSQL database, ensure that the
package postgresql96-server is installed.
Ensure that the latest update (9.6.1 or later) is installed. For example, run yum
update.
Archive Center server

On the computer that will host Archive Center, ensure that the packages
postgresql96-odbc (not just postgresql-odbc) and unixODBC are installed.
If the database is installed remotely, the installation of the package
postgresql96-client is optional.
Several Archive Center utilities require libraries from the PostgreSQL 9.3 ODBC
driver due to missing functionality in version 9.6. Run the following command
to install the packages:
rpm -ivh postgresql93-odbc-09.03.0400-1PGDG.rhel6.x86_64.rpm
postgresql93-libs-9.3.14-1PGDG.rhel6.x86_64.rpm
To perform manual installation steps:
1. On the database server, initialize the database by entering the following:
service postgresql-9.6 initdb

chkconfig postgresql-9.6 on
service postgresql-9.6 start
For more information, see the PostgreSQL website (http://www.postgresql.org/

download/linux/redhat).
2. On the computer(s) hosting Archive Center, open the /etc/odbcinst.ini file

in an editor and change the PostgreSQL section as follows:
a. Replace the line

Driver64 = /usr/lib64/psqlodbc.so
with
Driver64 = /usr/pgsql-9.6/lib/psqlodbc.so
b. Add the following line to the PostgreSQL section:
Threading=0
Example: Finally, the section should look like this:

AR160200-00-IGU-EN-02
2.2. Setting up PostgreSQL
[PostgreSQL]
Description = ODBC for PostgreSQL
Driver = /usr/lib/psqlodbc.so
Setup = /usr/lib/libodbcpsqlS.so
Driver64 = /usr/pgsql-9.6/lib/psqlodbc.so
Setup64 = /usr/lib64/libodbcpsqlS.so
FileUsage = 1
Threading = 0
To allow the database user access using JDBC and ODBC:
1. On the database server, navigate to the /var/lib/pgsql/9.6/data/ directory

and open the pg_hba.conf file in an editor.
2. Append a line to add a record configuring the client authentication. For more
information, see the comments in the file and the PostgreSQL documentation
(https://www.postgresql.org/docs/9.6/static/auth-pg-hba-conf.html).
3. In the /var/lib/pgsql/9.6/data/ directory, open the postgresql.conf file

in an editor and do the following:
a. Change the listen_addresses parameter such that the PostgreSQL server

also listens on interfaces other than localhost. For example, change it to
listen_addresses = '*'
b. Increase the value of the max_connection parameter. The recommended
value depends on the scenario and should roughly be number of Archive
Center nodes × number of connections.
Cluster topic: The default value (100) is too low for a cluster with three
nodes. Change it to 400.
2.2.2 Creating the database

When your PostgreSQL system is ready to be used, create the database for Archive
Center.
Important
The database must use UTF-8, which is the default encoding.
To create the database:
1. Create a directory for the tablespace. For example, enter
mkdir /software/dbdata/ecr_data
The database user must be able to access this directory. Therefore, for example,
enter
chown postgres:postgres /software/dbdata/ecr_data
2. Start the psql tool as user with database administration rights. For example,
enter

AR160200-00-IGU-EN-02
su postgres
psql
3. Create a database user for Archive Center. For example, enter:
postgres=# CREATE ROLE ecr PASSWORD 'ecr' LOGIN;
4. Create a tablespace for Archive Center. For example, enter:
postgres=# CREATE TABLESPACE ecr_data OWNER ecr LOCATION '/

software/dbdata/ecr_data';
5. Create the database for Archive Center. For example, enter:
postgres=# CREATE DATABASE ECR OWNER ecr TABLESPACE ecr_data;
The database must be owned by the user created in the previous step.
6. Define an extra function and a cast. Enter the following two commands:
postgres=# CREATE FUNCTION bigint_to_text(bigint) RETURNS text

AS 'select textin(int8out($1));' LANGUAGE SQL STRICT IMMUTABLE;
postgres=# CREATE CAST (bigint AS text) WITH FUNCTION

bigint_to_text(bigint) AS IMPLICIT;
2.3 Setting up SAP HANA

The SAP HANA database has to run on a dedicated host without any OpenText
software installed.
The SAP HANA administrator must create a user (for example, “ecr”). Doing so
creates an empty database automatically.

AR160200-00-IGU-EN-02
Chapter 3
Installing Archive Center and additional
components
System Center You can download the setup files in TAR.GZ format using OpenText™ System
Center. For more information, see “Obtaining and running the setup files using
System Center” on page 29.
Master setup Alternatively, you can install Archive Center components on many platforms by
using a master setup. It is called “OpenText Content Suite Platform Installer” and
offers a convenient way to install all required components. The general usage of the
Content Suite Platform Installer is explained in “Using the Content Suite Platform
Installer” on page 30. For more information, see also OpenText Content Suite
Platform - Installation Overview (SULC-IGD).
Related Topics
• “Prerequisites for Archive Center“ on page 9
• “Setting up the database“ on page 23
Background
• “About OpenText Archive Center“ on page v
3.1 Obtaining and running the setup files using

System Center
System Center You can use OpenText™ System Center Planner to download all mandatory and
Planner optional product components. System Center Planner can only be installed on
Windows systems. For example, use the computer on which you want to install
OpenText Administration Client. This computer must be able to connect to
OpenText My Support. You can download System Center Planner on My Support
(https://knowledge.opentext.com/knowledge/llisapi.dll/Open/56827097).
System Center The Archive Center components are available as a System Center package called
package “Archive Center 16 EP2”.
For more information, see OpenText System Center Planner - Installation and
Administration Guide (SYSCP-AGD).
Component (required/optional) Name of setup file

Archive Center (required) archive_server_16_2_0.tar.gz
Archive Monitoring Server (required) archive_monitoring_server_
16_2_0.tar.gz

AR160200-00-IGU-EN-02
Chapter 3 Installing Archive Center and additional components
Component (required/optional) Name of setup file

Document Pipeline Base (required for dp_base_16_2_0.tar.gz
Application Layer scenarios)
Document Pipeline for Archive Center dp_accmis_16_2_0.tar.gz
CMIS (required for Application Layer
scenarios)
Document Pipeline Info (optional) dp_info_16_2_0.tar.gz
Archive Cache Server (optional) archive_cache_server_16_2_0.tar.gz
Do not install on Archive Center host!
See “Setting up Archive Cache Server“
on page 51.
Solution Registry Agent (optional) solution_registry_agent_16_2_0.tar.gz
To install Archive Center components using System Center:
1. Log on as root.
Note: Ensure that the JDK or JRE is included in the PATH environment
variable. For more information, see “Further preparations” on page 21.
2. Stop Tomcat before the installation.
3. Extract the TAR.GZ file of the component on the target computer.
For example, open a command shell and change to the directory to which you
downloaded the file, and then run
tar -xzf <component>_16_2_0.tar.gz
4. In the extracted directory, run the setup.sh file.

Example:
cd archive_server
./setup.sh
5. Continue with the section for the respective component below.
3.2 Using the Content Suite Platform Installer

To install Archive Center components using Content Suite Platform Installer:
1. Download the product's ISO-9660 image from OpenText My Support and burn
a DVD from it.
Alternatively, mount the ISO image as a virtual drive. For detailed instructions,
see My Support (http://mimage.opentext.com/support/ecm/secure/software/
checksuminstructions.html).
2. Log on as root.
Note: Ensure that the JDK or JRE is included in the PATH environment
variable. For more information, see “Further preparations” on page 21.

AR160200-00-IGU-EN-02
3.2. Using the Content Suite Platform Installer
3. Mount the product's DVD or ISO image (for example, as /dvd).
Important
Stop Tomcat before the installation.
4. Change to the mounted directory and start the installation:
root>> cd /dvd
root>> ./mastersetup
5. Enter N, ENTER to get to the License agreement page.

Read the license agreement. To accept it, enter A, ENTER.
The Deployment Scenarios page is displayed.
General usage of Archive Center Installer:
Browsing pages
To browse the selection groups, press N for the next and P for the previous
page (if applicable).
Selecting components, clearing selected components

To select a component for installation or to clear a selected component, on
the appropriate selection page, press the corresponding number and press
ENTER.
Aborting the installation

At any time, you can press C, ENTER to cancel the installation.
6. Deployment Scenarios: Select the necessary deployment scenarios. The

selections depends on your planned scenario. If a scenario is selected, the
according components are pre-selected. Enter N, ENTER to continue.
7. Product Groups: Additional components can be selected to be installed. Select

additional components if necessary. Enter N, ENTER to continue.
8. Check the entries on the Global parameter page. Depending on the scenario
several parameters (for example Installation user name, Installation group
name) must be checked and adapted if necessary.
User for application server

The user for running the application server (Tomcat) and the installation
user must be the same. If the users are different, some configuration files
are not writable.
Note: This user is used for all subsequent installations. The user will run
Archive Center and will be the owner of all installation directories.
9. Press N, ENTER to continue.
10. Summary: The summary page gives an overview of all components that will be
installed. Check if all necessary components are selected. If you want to change
the selected components enter P, ENTER to change.

AR160200-00-IGU-EN-02
11. Press I, ENTER to start the installation. The installation of the selected
components is performed in the same order as shown on the summary page.
Note: Depending on the component, the setup

• is running silently, just the “Start” and “Finish” dialogues are displayed,
• or needs additional input for further configuration dialogues.
12. Continue with the next section.
3.3 Installing Archive Center

Important
• Single node
The description in this section is intended for a single installation on one
computer. For a clustered installation, see OpenText Archive Center -
Cluster Installation Guide (AR-ICLU) before continuing.
• Database ready
Before the installation of Archive Center, the database system must
already be installed and a database must already be configured (see
“Setting up the database“ on page 23).
To install Archive Center:
1. Follow the procedure in “Using the Content Suite Platform Installer” on page 30
or “Obtaining and running the setup files using System Center” on page 29 to
start the setup of Archive Center.
2. Generate SQL script to install Database schema: Press Y, ENTER to create the
script for the database schema. Press N, ENTER to skip.
Note: Only skip this step if you are installing a cluster and the database
schema is or will be installed with another cluster node.
Cluster topic: If you install a clustered environment, you must create the
database schema only once.
If you chose to generate the script in the previous step:

Execute SQL script for database schema upgrade: Press Y, ENTER to execute
the script for the database schema. Press N, ENTER to only create the script
without executing it.
Important
If you choose not to execute the schema, you will have to execute the
script manually. Otherwise, Archive Center will not work.
The script to process is located in the <OT config AC>/sql directory and named
DSSchema.sql.

AR160200-00-IGU-EN-02
3.3. Installing Archive Center
3. Archive Spawner destination directory: Enter the directory for the Archive
Spawner, for example: /opt/opentext/spawner
4. Path to the Apache Tomcat installation directory: Enter the path to the
<Tomcat_home> directory. The default for Tomcat is CATALINA_HOME.
5. Application Server HTTP Port: Enter the HTTP port of the application server;
default: 8080.
6. Application Server HTTPS Port: Enter the SSL/HTTPS port of the application
server; default: 8090.
Important
The ports must be configured in the <Tomcat_home>/conf/server.xml
configuration file. For more information, see “Configuring the connector
and securing Tomcat” on page 14.
7. Installation destination root directory: Enter the destination directory, for

example: /opt/opentext/ArchiveServerSoftware_16_2_0
8. Configuration destination root directory: Enter the directory for the

configuration information, for example: /opt/opentext/
ArchiveServerConfig_16_2_0
9. Archive logging root directory: Enter the directory for the logging information,
for example: /var/adm/opentext/log
10. JAVA home directory: Enter the path to the bin directory of the Java 1.8
installation.
11. VAR directory: Enter the directory for temporary archiving files, for example: /
var/adm/opentext
12. Database type to be used: Depending on your database system, either press O
for Oracle Database, H for SAP HANA, or P for PostgreSQL.
13. Depending on your database system, do the following:
ORACLE DATABASE
a. ORACLE_HOME directory: Enter the path to the directory of the local
Oracle software installation.
b. Hostname Database Server: Enter the name of the computer hosting
the database.
Do not enter localhost but the full server name. If the database is an
Oracle RAC, enter the abstract name for the RAC host.
c. JDBC Port: Enter the port used for connections to the database (default:
1521).
d. Database user: Enter the name for the database user, for example: ecr
e. Password of database user: Enter the password for the database user
and confirm it.

AR160200-00-IGU-EN-02
f. Oracle SID: Enter the Oracle SID, for example, ECR

If the database is an Oracle RAC, enter the abstract SID of the RAC as
specified in b on page 33.
g. TNS_ADMIN Directory: Enter the path to the directory that contains
the Oracle configuration files tnsnames.ora and sqlnet.ora. (Default
when using the Oracle configuration tools: <ORACLE_HOME>/network/
admin)
h. Service name: Enter the name of the Oracle service to be used in the
connect string, for example: ECR_<Oracle_DBserver>
Ensure that you provide the TNS service name as provided in
tnsnames.ora, including the domain. The convenience setting
DEFAULT_DOMAIN of sqlnet.ora has no effect.
i. Tablespace for index: Enter the name of the database’s index
tablespace, for example: ECR_INDEX
j. Tablespace for data: Enter the name of the database’s data tablespace,
for example: ECR_DATA
SAP HANA
a. Hostname Database Server: Enter the name of the computer hosting
the database.
Do not enter localhost but the full server name.
b. JDBC Port: Enter the port used for connections to the database (default:
30015).
c. Database user: Enter the name for the database user, for example: ecr
d. Password of database user: Enter the password for the database user
and confirm it.
POSTGRESQL
a. Hostname Database Server: Enter the name of the computer hosting
the database.
Do not enter localhost but the full server name.
b. JDBC Port: Enter the port used for connections to the database (default:
5432).
c. Database user: Enter the name for the database user, for example: ecr
d. Password of database user: Enter the password for the database user
and confirm it.
e. Database name: Enter the name of the database to be used, for example:
ECR
f. Tablespace for index: Enter the name of the database’s index
tablespace, for example: ecr_data
g. Tablespace for data: Enter the name of the database’s data tablespace,
for example: ecr_data

AR160200-00-IGU-EN-02
3.3. Installing Archive Center
14. Directory for ISO9660 trees: Enter the path to the directory for building
temporary file trees during the creation of ISO images.
Important
Ensure that the VAR directory is not a subdirectory of this directory.
Regardless of planning to use ISO images or not, you have to specify this
setting.
15. Directory where ISO9660 images are built: Enter the path to the directory for
building temporary ISO images.
Important
The CDDIR and CDIMG directories must be different.
Ensure that the VAR directory is not a subdirectory of either one of these
directories and that these directories are not a subdirectory of VAR.
Regardless of planning to use ISO images or not, you have to specify this
setting.
16. Select the user management system for Archive Center:
• If you want to use OpenText Directory Services (OTDS) and already

configured the OTDS resource, enter O to select OpenText Directory
Services (OTDS).
Cluster topic: In case of a cluster installation you already should have
configured OTDS.
For more information, see Section 1.2 “Prerequisites for the cluster
installation” in OpenText Archive Center - Cluster Installation Guide (AR-ICLU).
Enter the connection parameters to the OTDS server: HTTPS or HTTP;
Server name; and Port (default: 8443).
Enter the OTDS resource identifier that was generated during the OTDS
resource creation phase.
• If you currently have no OTDS server or resource, enter L to select Local
User management (dsadmin).
You can configure OTDS later in the Administration Client (Archive Server
> OTDS Connection).
17. A list of the provided installation parameters is displayed. Carefully check if all
parameters are correct.
If you want to change any parameter, do the following:
a. Enter Y.
b. Enter the number of the parameter you want to change.
c. Change the parameter according to the description given above.
When all parameters are set correctly, enter N to start the configuration check.

AR160200-00-IGU-EN-02
18. If the configuration check returns any errors, solve the problem and restart the
installation.
If no errors are reported, enter Y to start the installation.
Note: Detailed logging information can be found in the log file. The log file
path is displayed at the end of the setup, for example:
/opt/opentext/log/opentext_instlog/SetupArchiveServerAndJDS/
install.log
3.4 Installing Archive Monitoring Server

Archive Monitoring Server obtains status information about archives, pools, hard
disk and database space on Archive Center.
Archive Monitoring Server requires Archive Server or OpenText Document Pipeline

to be installed on the same computer.
Note: If installed, the Archive Spawner will be stopped during the installation
of Archive Monitoring Server.
To install Archive Monitoring Server:
1. On the computer to be monitored, follow the procedure in “Using the Content

Suite Platform Installer” on page 30 or “Obtaining and running the setup files
using System Center” on page 29 to start the setup of Archive Monitoring
Server.
2. Only if not specified before – Spawner directory: Enter the directory for the
Archive Spawner, default: /opt/opentext/spawner.
3. Tomcat only: Path to the Apache Tomcat installation directory: Enter the path to
the <Tomcat_home> directory. The default for Tomcat is CATALINA_HOME.
4. Installation destination root directory: Enter the destination directory,
default: /opt/opentext/ArchiveMonitoringServerPrograms_16_2_0
configuration information, default: /opt/opentext/
ArchiveMonitoringServer_16_2_0
6. Only if not specified before – Archive logging root directory: Enter the directory
for the logging information, for example: var/adm/opentext/log
7. Only if not specified before – JAVA home directory: Enter the bin/java directory
of the JRE 1.8 installation.
8. Only if not specified before – VAR directory: Enter the directory for temporary
archiving files, default: /var/adm/opentext

AR160200-00-IGU-EN-02
3.5. Installing Document Pipeline Base
a. Enter Y.
installation.
/opt/opentext/log/opentext_instlog/SetupArchiveMonitoringServer
3.5 Installing Document Pipeline Base

Document Pipeline Base is the basic package for all scenario-specific pipelines.
Cluster topic: Do not install Document Pipelines on the nodes of an Archive Center
cluster.
To install Document Pipeline Base:
start the setup of Document Pipeline Base.
2. If not specified before: Archive Spawner destination directory: Enter the directory
for the Archive Spawner, for example: /opt/opentext/spawner
3. If not specified before: VAR directory: Enter the directory for temporary archiving
files, for example: /var/adm/opentext
example: /opt/opentext/DPBASESoftware_16_2_0
configuration information, default: /opt/opentext/DPBASEConfig
6. If not specified before: Archive logging root directory: Enter the directory for the
logging information, default: /var/adm/opentext/log
7. External directory path: Enter the path to the external directory where project
pipelines are stored.
8. Directory name (DPDIR): Enter the path to the directory for temporary storage
of documents.
9. Optional Hostname Archive Server: Enter the name of the Archive Server to be
used.
10. Optional Port archive server: Enter the port the Archive Server uses. The default
port is 8080.

AR160200-00-IGU-EN-02
11. Optional Hostname Rendition Server: If OpenText™ Rendition Server is to be

used, enter the name of the computer hosting Rendition Server.
12. Optional Port Number Rendition Server: Enter the port Rendition Server uses.
The default port is 8080.
13. Optional Hostname Archive Timestamp Server: If Archive Timestamp Server is
to be used, enter the name of the Archive Timestamp Server.
14. Optional Port Number Archive Timestamp Server: Enter the port Archive
Timestamp Server uses. The default port is 32001.
a. Enter Y.
installation.
/opt/opentext/log/opentext_instlog/DPBASE/install.log
3.6 Installing Document Pipeline for Archive Center

CMIS
Document Pipeline for Archive Center CMIS provides the pipelines for the
“extended functionality” of Archive Center. Document Pipeline for Archive Center
CMIS requires Document Pipeline Base.
Cluster topic: Do not install Document Pipelines on the nodes of an Archive Center
cluster.
To install Document Pipeline for Archive Center CMIS:
start the setup of Document Pipeline for Archive Center CMIS.
example: /opt/opentext/DPAcCmis_16_2_0
3. JAVA directory for Java CMIS doctool: Enter the path to the bin directory of
the Java installation to be used by the CMIS doctool.

AR160200-00-IGU-EN-02
3.7. Installing Document Pipeline Info

a. Enter Y.
installation.
/opt/opentext/log/opentext_instlog/SetupArchiveDPAcCmis/
install.log
3.7 Installing Document Pipeline Info

Document Pipeline Info is an optional tool to monitor all Document Pipelines.
To install Document Pipeline Info:
start the setup of Document Pipeline Info.

example: /opt/opentext/DPINFOSoftware_16_2_0
3. If not specified before: Java Root Dir: Enter the path to the bin directory of the
Java installation.

a. Enter Y.
installation.

AR160200-00-IGU-EN-02
/opt/opentext/log/opentext_instlog/DPINFO/install.log
3.8 Installing Solution Registry Agent

OpenText Solution Registry can be used to provide a description of the installed
OpenText system landscape, that is, the software components (including product
name, product version, and installation directory) that are currently installed. For
more information, see OpenText Solution Registry - Configuration and Administration
Guide (LDS-AGD).
To install Solution Registry Agent:
start the setup of Solution Registry Agent.

example: /opt/opentext/SolutionRegistryAgent_16_2_0

a. Enter Y.
installation.
3.9 Concluding the installation

Configuration Optionally, configure the installed components for extended functionality. See
“Configuring for Application Layer usage ” on page 41.
Patches Install all available mandatory patches. See “Installing patches” on page 44.
Ports If you chose other ports than 8080/8090 for Tomcat, see “Adjusting non-default
ports” on page 43.
Restart See “Starting Tomcat” on page 44 and “Starting Archive Spawner” on page 44 for
information on starting the system.
Miscellaneous See “Final steps” on page 45 for further important topics.

AR160200-00-IGU-EN-02
3.9. Concluding the installation
3.9.1 Setting the ECM_VAR_DIR variable

Several jobs require the ECM_VAR_DIR variable to be set correctly.
To set the ECM_VAR_DIR variable:
1. Open the <Tomcat_home>/bin/setenv.sh file in an editor.

2. Add the following line:
ECM_VAR_DIR=<path to VAR directory>

export ECM_VAR_DIR
You specified the VAR directory in Step 11 on page 33.
3.9.2 Setting the directory for the search index

The search service requires a directory for the index, which must be configured.
Important
Depending on the scenario and usage, the index can become very big. Ensure
that you provide enough disk space.
To set the profile for the search service:
1. Open the <OT config AC>/setup/AS.Setup file in an editor and locate the
ES_DATA_DIRECTORY variable.
Cluster topic: If you install a clustered Archive Center environment, you must
edit the AS.Setup file on each node.
2. Specify the path to the directory for the search index.
3. Save the file.
3.9.3 Configuring for Application Layer usage

Before you start the system, you must change several configuration variables if you
want to use the “extended functionality” (Application Layer and web apps).
Cluster topic: For more information, see Section 1.3 “Preparing the cluster nodes” in
To configure for Application Layer usage:
1. Open the DS.Setup in an editor. You can find the file in the <OT config AC>/
setup directory.
2. Change the following variables as indicated:
MY_HOST_ALIASES
In case of an environment with multiple host names, add the fully qualified,
external host names as a comma-separated list.

AR160200-00-IGU-EN-02
MY_HOST_NAME
When working with different networks, domains, or hostnames, specify the
external Archive Server name.
STORAGE_ALLOCATION
Set to on.
The following variable must keep its value: STATISTIC (set to on),
3. Analogously, change the following variables in the AS.Setup file:
BIZ_OPERATING_MODE
Set to PublicCloud, PrivateCloud, or OnPremises, depending on your
scenario.
Note: For more information, see Section 1.2 “Operation mode” in

OpenText Archive Center - Scenario Configuration Guide (AR-CGD).
BIZ_HOST_IDENTIFIER
The host identifier will be used for archive names generated by Archive
Center Administration. Create and enter a name that fulfills the following
regular expression: [A-Z][A-Z0-9]{4} (the name must be five characters
long, it must start with an uppercase letter, followed by four uppercase
letters or numbers).
BIZ_EXPORT_DIRECTORY
Enter the path to the directory where the exports (XML files) of eDiscovery
searches are saved.
Important
Depending on the scenario and usage, the exported files can become
very big. Ensure that you provide enough disk space for the export
directory.
You can change the location again later.
4. Analogously, change the following variables in the ICS.Setup file:
ICS_SCENARIO
Set the value according to the chosen operating mode:
Operating mode Value

PublicCloud
LEAADA
PrivateCloud
OnPremises LEA
AL_PROXYPORT
Enter the HTTP port number configured for ArchiveLink connections;
default 8080. This is the external port of the Archive Server (in case of a
cluster, it is the port of the load balancer).

AR160200-00-IGU-EN-02
AL_PROXYSSLPORT
Enter the HTTPS port number configured for secure ArchiveLink
connections; default 8090. This is the external TLS/SSL port of the Archive
Server (in case of a cluster, it is the TLS/SSL port of the load balancer).
5. If you chose ports during installation that are not the default ports (that is not
8080 and 8090), see “Adjusting non-default ports” on page 43.
3.9.4 Adjusting non-default ports

Adjust If you chose ports that are not the default ports (that is not 8080 and 8090), you have
nonstandard to adjust the configured ports in two setup files.
ports
To adjust non-default ports:
1. Open the <OT config AC>/setup/ADMS.Setup file in an editor.
2. Locate the AS_HTTP_PORT variable and specify the port for HTTP connections.
Locate the AS_HTTPS_PORT variable and specify the port for HTTPS connections
(if applicable).
3. Save the file.
4. Open the <OT config AC>/setup/DS.Setup file in an editor.
5. Locate the CS2DS_DSPORT variable and specify the port for HTTP connections.
Locate the CS2DS_DSSSLPORT variable and specify the port for HTTPS
connections (if applicable).
6. Save the file.
3.9.5 Executing the schema script manually (SAP HANA only)

If you decided against executing the database schema when running the installation
(see “Installing Archive Center” on page 32), you must execute it manually as shown
below.
Location The script to process is located in <OT config AC>/sql and named DSSchema.sql.
To execute the schema script:
1. If not done already, install the SAP HANA database client software. For further
information, see the SAP HANA Database - Client Installation and Update
Guide (http://help.sap.com/hana/
SAP_HANA_Client_Installation_Update_Guide_en.pdf).
2. Execute the following command:
hdbsql -m -c //--// -n <hostname of the HANA server> ‑i <instance

ID> ‑u <user> ‑p <password> ‑I DSSchema.sql ‑o dsschema.out
where <user> is the user provided as DBLOGIN during the installation. The -o
option redirects the output to a file named dsschema.out.

AR160200-00-IGU-EN-02
3.9.6 Installing patches

OpenText releases patches for Archive Center on a regular basis. The installation of
the patches as described below is mandatory.
To install the patches:
1. After the installation, check for the latest patch collection (“Update”) for your
operating system on My Support (https://knowledge.opentext.com/knowledge/
cs.dll/Open/63027605) and, if applicable, download it.
2. Follow the instructions in OpenText Archive Center and OpenText Enterprise

Library - Update Installation Guide (UNIX/Linux) (AR-DUS).
3.9.7 Starting Apache Tomcat and Archive Spawner

Starting Tomcat
The Tomcat service is not started during the installation. To conclude the installation
and achieve a running system, you have to start Tomcat using the Installation user
given as global installation parameter.
Important
When starting Tomcat, do not run the script from within a directory that is in
the path of a volume.
Starting Archive Spawner

Load profile OpenText recommends running a script file named profile in the <OT install
AC>/bin directory (for example, /software/opentext/
ArchiveServerSoftware_16_2_0/bin).
This script updates the PATH and other environment variables and makes it easier to
start spawncmd and other Archive Center tools. After loading the profile, you can, for
example, enter spawncmd status to see the states of the archive services.
To load the profile, change to the <OT install AC>/bin directory, and then run
root>> . ./profile
Start Spawner You have to start the Archive Spawner manually as user root. For more
information, see “Appendix: Special commands and other OS-specific topics“
on page 65.
If, after starting the Spawner, Tomcat is started too late, the backup server can
terminate. To avoid this, OpenText recommends the following order:
1. Start Tomcat.
2. Start Archive Spawner.

AR160200-00-IGU-EN-02
bksrvr error If you encounter an “unable to connect to backup-service” error in the

Administration Client because the backup server (bksrvr process) terminated,
restart the bksrvr process with spawncmd start bksrvr
3.9.8 Final steps

Backup internal server certificate
The installation process generates a unique, nonrecoverable key/certificate pair,
which is used to encrypt and decrypt the server key store. If you lose this key/
certificate, you will not be able to access encrypted documents anymore! Therefore,
it is important to keep a backup copy of the corresponding <OT config AC>/setup/
as.pem file and store it in a secure place.
Enforcing protocol
In mixed IPv4/IPv6 environments it can be necessary to enforce preferred usage of
one of the protocols.
To enforce IPv4 or IPv6:
1. Open the <spawnerdir>/config/setup/profile file in an editor.
2. Add the following lines, assuming that IPv4 is to be preferred:

AS_PREF_IP=4
export AS_PREF_IP
In case IPv6 is to be preferred, add AS_PREF_IP=6 instead.
3. Repeat the previous step for the <Tomcat_home>/bin/setenv.sh file.
Log file
You find logging information for Archive Center in the as.log file in the <Tomcat
install dir>/logs directory.

AR160200-00-IGU-EN-02
Chapter 4
Configuring Archive Center
Although Archive Center is ready to be used after a successful installation, you must
perform some additional configurations. In particular, you can change passwords
for security reasons.
Cluster topic: Finish the cluster setup before you configure Archive Center.
For more information, see Section 2 “Configuring the cluster” in OpenText Archive
Center - Cluster Installation Guide (AR-ICLU).
Further configuration for the Application Layer

To use the Application Layer and the web apps of Archive Center, several additional
steps are required. For example, you must create tenants. For more information, see
OpenText Archive Center - Scenario Configuration Guide (AR-CGD).
4.1 Signing in to Archive Server in Administration

Client
To authenticate against Archive Server using Directory Services, start
Administration Client. Add your server and sign in as user otadmin@otds.admin.
For more information about using Administration Client, see the online help: Press
F1, and then expand the Shared Services node.
Note: To administer users, groups, and tenants, you use the Directory Services
web client, which is accessible under <protocol>://<host>:<port>/otds-
admin. For more information about working with OTDS, see OpenText
Directory Services - Installation and Administration Guide (OTDS-IWC).
4.2 Changing the dsadmin password

The initial password of the dsadmin superuser is not set. You must assign a
password as soon as possible.
Note: Although signing in as dsadmin into Administration Client is not

possible when OTDS is used, dsadmin is still used by other components.
To set the password of the dsadmin user:
1. Sign in to Administration Client as an OTDS user with administrator rights (for

example, otadmin@otds.admin).
2. In the console tree, open the Archive Server > System > Users and Groups
node, and in the result pane, select the Users tab.

AR160200-00-IGU-EN-02
Chapter 4 Configuring Archive Center
3. Open the Properties of the dsadmin user and change the password.
4. Restart the Apache Tomcat and Archive Spawner services for the changes to
take effect.
4.3 Changing the password of the database user

The login (DBLOGIN) and password (DBPASSWORD) of the database user are encrypted
and stored in the setup file DBS.Setup. If you change the password of the database
user, you must also change the corresponding entry as described below.
To change the DB user password:
1. Start Administration Client and sign in to Archive Server.

2. In the console tree, expand the Archive Server node.
3. Create a secure password.
Note: Characters allowed within a password are all printable ASCII

characters except: “;”, “'” and “"”.
4. Select the Configuration object in the console tree and search for the User
password of database configuration variable (internal name:
AS.DBS.DBPASSWORD).
5. Open the Properties of the User password of database configuration variable
and enter the new password.
6. Click OK.
The password is automatically stored and encrypted.
7. Change the password in the database application.
8. Restart the Apache Tomcat and Archive Spawner services for the changes to
take effect.
4.3.1 Oracle Database only: Checking the expiry date of the

password
You can check the expiry date of the user password. Run an SQL statement as
follows:
Example: sqlplus ecr/ecr@ecr_<local_host>
select username,account_status,expiry_date from user_users;
Note: With Oracle 11, the default password policy changed. Now, by default a
user password expires after 180 days.
If you do not want your password to expire, consult your local database
administrator to modify your profile accordingly.

AR160200-00-IGU-EN-02
4.4. Configuring different internal and external hostname
Further See also the Oracle information about security (http://www.oracle.com/technetwork/

information database/security/overview/index.html).
4.4 Configuring different internal and external

hostname
If in a cloud environment the internal and external name of the Archive Center host
diverge, do the following.
Cluster topic: Skip this step as a cluster requires different settings.

For more information, see Section 1.3 “Preparing the cluster nodes” in OpenText
Archive Center - Cluster Installation Guide (AR-ICLU).
To configure diverging internal and external hostnames:
1. Start Administration Client and connect to Archive Center (Archive Center).
2. Select the Configuration object in the console tree and search for my_host.
3. Open the Properties of the External Archive Server Host Name configuration
variable (internal name: AS.DS.MY_HOST_NAME).
As Value, specify the fully qualified external hostname, for example:
externalhost.domain1.example.com
4. Open the Properties of the Alias Archive Server Host Name(s) configuration
variable (internal name: AS.DS.MY_HOST_ALIASES).
As Value, specify a comma-separated list containing the internal hostname,
external hostname, and the fully qualified external hostname, for example:
internalhost,externalhost,externalhost.domain1.example.com
Note: Changes to these settings do not take effect until the application
server is restarted.
4.5 Configuring certificate authentication for Archive

Center Proxy
Before Archive Center Proxy can be installed using the Authenticate with SSL
Client Certificate option, you must change a configuration variable in Archive
Center.
To accept SSL/TLS client certificates for authentication:
1. Start OpenText Administration Client and connect to Archive Center (Archive

Center).
2. Select the Configuration object in the console tree and search for accept ssl.

AR160200-00-IGU-EN-02
Chapter 4 Configuring Archive Center
3. Open the Properties of the Accept SSL client certificates for authentication
configuration variable (internal name:
AS.AS.BIZ_ACCEPT_SSL_CLIENT_CERTIFICATE).
4. Set the Value to on, and then click OK.
Configuring Further, you must configure Tomcat to request a client certificate by setting
Tomcat clientAuth="want" for the SSL/TLS connector in the server.xml file. For more
information, see “Configuring the connector and securing Tomcat” on page 14.

AR160200-00-IGU-EN-02
Chapter 5
Setting up Archive Cache Server
OpenText Archive Cache Server is intended to reduce and speed up the data transfer
in a WAN. It is installed on its own host in a separate subnet.
Important
• If you want to use the Application Layer of Archive Center in multi-
tenant configuration, you must use Archive Center Proxy. Do not use
Archive Cache Server in this case. Archive Cache Server continues the
caching features of previous Archive Server versions (10.5.0 and before).
• Archive Cache Server and Archive Center cannot be installed together.
5.1 Prerequisites
Java, For Archive Cache Server, the same prerequisites hold as for Archive Center
application regarding Java and Apache Tomcat. For more information, see “Setting up Apache
server
Tomcat” on page 14.
Ensure that the JDK or JRE is included in the PATH environment variable. For more
information, see “Further preparations” on page 21.
User Adhere to the restrictions regarding the user for the installation as mentioned in
“User for Archive Center” on page 21.
Additionally, see the recommendations for the partition size below.
Recommendations for Archive Cache Server partitions

The following partitions should be prepared for the Archive Cache Server:
Partition for Apache Derby database

• Use a separate volume only used by the Archive Cache Server.
• The required space for the database depends on
a. the number of expected components,
b. the size of the components,
c. if stored on a write-through or write-back partition,
d. the length of different attributes as component names, content type, etc.
• Startup size (initial size plus redo logs): ca. 12 MB
• Deletion of items needs additional temporary space (calculate with 10%
additional space)

AR160200-00-IGU-EN-02
Chapter 5 Setting up Archive Cache Server
Ca. 2.7 kB (write-through) or 4.3 kB (write-back) DB space per item is

needed, but depends on size etc. (see a – d).
Example 5-1: Estimation of DB partition size

Intended capacity: 1,000,000 write-through + 100,000 write-back items
⇒ (12 * 1024 kB + 1,000,000 * 2.7 kB + 100,000 * 4.3 kB) * 1.1
= 3456516.8 kB ≈ 3.5 GB
“Write-through” partition(s)
• Use a separate volume only used by the Archive Cache Server

• The required space for write-through partitions depends on:
• Block size (may cause waste)

• Size of components
“Write-back” partition
• Use a separate volume only used by the Archive Cache Server

• Because of an increased security risk of write-back items, storage on a RAID
disk is recommended.
• The required space for write-back partitions depends on:
• Block size (may cause waste)

• Size of components
• Number of components, length of component, and the size of a set of
various document attributes, which are stored in a separate file on the idx
part of the writeback partition
• The required space for write-back partitions is divided into three directories:
1. dat – contains components
2. idx – contains meta-information for recovery in case of a database crash
3. log – contains information which documents are transferred to the

Archive Center
Note: Space given for write-back volumes is divided at a ratio of 9:1

between dat and idx.

AR160200-00-IGU-EN-02
5.2. Installing Archive Cache Server
5.2 Installing Archive Cache Server

Important
Archive Cache Server and Archive Center cannot be installed together.
To install Archive Cache Server:
1. To get the Archive Cache Server software, use OpenText™ System Center
Planner. For more information about System Center, see OpenText System Center
Planner - Installation and Administration Guide (SYSCP-AGD).
Alternatively, you can download the OpenText™ Content Suite Platform image
from My Support (https://knowledge.opentext.com/knowledge/cs.dll/Open/
17370316) and use its installer.
2. Start the setup of Archive Cache Server. For more information, see “Obtaining
and running the setup files using System Center” on page 29.
3. Read the license agreement. To accept it, enter Y.
4. Path of the Apache Tomcat home directory: Enter the path to the
<Tomcat_home> directory.
5. Application Server HTTP Port: Enter the HTTP port of Tomcat; default: 8080.
6. Application Server HTTPS Port: Enter the TLS/SSL port of Tomcat; default:
8090.
Important
The ports must be configured in the <Tomcat_home>/conf/server.xml
configuration file. For more information, see “Configuring the connector
and securing Tomcat” on page 14.

example:
/opt/opentext/archive_cache_server_16_2_0
8. User name for files and running processes: Enter the name of the user running
Tomcat.
9. Group name: Enter the name of the group of the Tomcat user.
10. Host Name Archive Server: Enter the name of the computer on which Archive
Center resides.
11. Archive Server HTTP Port: Enter the HTTP port Archive Server uses. The
default port is 8080.
12. Archive Server SSL Port: Enter the HTTPS port Archive Server uses. The
default port is 8090.
13. Dir to store database files: Enter the path to the directory in which the database
files for Archive Cache Server will be stored.

AR160200-00-IGU-EN-02
Chapter 5 Setting up Archive Cache Server
14. Write back volume path: Enter the path to the directory of the write-back
volume. Leave empty to set no write-back volume.
Caching mode
For details on the differences between “write-back” and “write-through”
caching mode, see Section 15 “Configuring Archive Cache Server” in
OpenText Archive Center - Administration Guide (AR-ACN).
15. MB size limit: Enter the size of the write-back volume in megabytes. Enter 0 to
set no write-back volume. The minimum size is 50 MB.
16. Cache Volumes Path: Enter the path to the first cache volume (more cache
volumes can be specified later).
17. MB size limit in CACHEPATH1: Enter the amount of disk space to reserve for
the first volume in megabytes. The minimum size is 20 MB.
18. Do you want to define more CACHE volumes: To add more cache volumes,
enter Y. Repeat the steps 16 and 17 accordingly for the other cache volumes.
When all cache volumes are set, enter N.
a. Enter Y.
installation.
/opt/opentext/log/opentext_instlog/SetupArchiveCacheServer/
install.log.

AR160200-00-IGU-EN-02
5.3 Concluding the installation

Starting Tomcat The Tomcat service is not started during the installation. To conclude the installation
and achieve a running system, you have to start Tomcat using the Installation user
given as global installation parameter.
Further Now that Archive Cache Server is installed, continue with the configuration. For
information more information, see Section 15 “Configuring Archive Cache Server” in OpenText
Archive Center - Administration Guide (AR-ACN).
Logfiles
To keep track of operations, Archive Cache Server logs to the as.log file in the
<Tomcat_home>/logs directory.
5.4 Enabling certificates

Archive Cache Server automatically upload its certificates to the Archive Center. The
names of this certificate can be identified by the following schema:
CS_ACS_<hostname>
If you intend to work with protected archives, this certificate must be enabled on the
Archive Center; see Section 8.5 “Certificates” in OpenText Archive Center -
Administration Guide (AR-ACN).

AR160200-00-IGU-EN-02
Chapter 6
Appendix: Setting up the database in Oracle
Database
Local database To set up a test database, you have to perform the following procedures on the
database server:
1. Install the Oracle server software and relevant patches.

2. Create the database and the Oracle listener.
3. Create the database user.
4. Configure the Oracle Listener.
5. Configure the TNS service names.
6. Optional Configure permissions and password settings.
Remote In addition, if the database is located on a different server than Archive Center, you
database have to perform the following procedures on the Archive Server computer:
1. Install the Oracle Client software and relevant patches.

2. Configure the network service names or copy the tnsnames.ora and sqlnet.
ora files from the database server to the Archive Server computer.
6.1 Setting up Oracle Database server

6.1.1 Creating the test database
Note: If the Oracle software is already installed, ensure that the Oracle
Enterprise Manager Console DB is installed before you create a new database.
Prerequisites The disks used for the database must fulfil the following prerequisites:
• The volumes of the disks must not be compressed.
• Avoid the use of RAID 5 for redo logs and archived redo logs.
The following shows how to create a test database with the Oracle 12c Database
Configuration Assistant. This very simple database will have the following
characteristics:
• All database files are located in one directory. Thus, as a prerequisite, create a
directory in which you want all database files to be created (for example, /
dbdata).
• Redo log file groups consist always of two members.

AR160200-00-IGU-EN-02
Chapter 6 Appendix: Setting up the database in Oracle Database
To create the database with Oracle 12c:
1. Configure the following:
oracle>> TERM=xterm
oracle>> export TERM
oracle>> DISPLAY=<host_xserver>:0.0
oracle>> export DISPLAY
SLES
On SUSE Linux Enterprise Server, leave <host_xserver> empty.
As root, execute the following:
root>> xhost +
2. Start the Database Configuration Assistant as user oracle:
cd <ORACLE_HOME>/bin
./dbca
3. Database Operations: Select Create Database.
4. Creation Mode: Select Advanced Mode.
5. Database Template: Select Custom Database.
6. Database Identification: Enter a Global Database Name (for example, ECR).

The SID is set automatically.
7. Management Options: Select Configure Enterprise Manager (EM) Database

Express.
8. Database Credentials: Feel free to set the passwords according to your

company standards.
9. Network Configuration: Create the Oracle Listener. Click Create a New

Listener and enter a Listener Name, for example, LISTENER. As Listener Port,
enter the standard TCP port number 1521.
10. Storage Locations: Specify the following storage options:
a. As Database files Storage Type, select File System.

b. Select Use Common Location for All Database Files and enter the
respective directory. (The directory must exist.)
c. Clear Specify Fast Recovery Area.
d. Select Enable Archiving.
e. Click Edit Archive Mode Parameters.
f. Enter one or more directories on dedicated disks as archive log
destinations.
11. Database Options: On the Database Components tab, select Oracle JVM.

AR160200-00-IGU-EN-02
6.1. Setting up Oracle Database server
Clear all other options.
12. Initialization Parameters:
a. Click Memory and select Typical.

Change the Memory Size to 750 MB.
Note: This is the minimum for a test system. A reasonable value for a
production database will be substantially larger.
Select Use Automatic Memory Management.

b. Click Sizing:
For the block size, select 8192 bytes.
For processes, select at least 300.
c. Click Character Sets and do the following:
• Database Character Set: Select Use Unicode (AL32UTF8).

• National Character Set: Select AL16UTF16 – Unicode UTF-16
Universal character set.
d. Click Connection Mode and select Dedicated Server Mode.
13. Creation Options: Select Create Database.

Click Customize Storage Locations, and then specify the following:
a. Expand the Storage tree listing.

b. Click Control Files to check that there are at least two control files.
c. Create the tablespace ECR_DATA:
i. Click Tablespaces.
ii. On the General tab, set the following:
• As Name, enter ECR_DATA, for example.

• As Type, select Permanent.
• As Block Size, select Default.
iii. To add the datafile, click the icon.

On the General tab, specify the following:
• As Name, enter ECR_DATA_1.dbf, for example.

• As File Size, enter 500 MB.
Note: This is the size for a test system. A reasonable value for
a production system will be several GB.
On the Options tab, specify the following:

AR160200-00-IGU-EN-02
• Select Automatically extend datafile when full (AUTOEXTEND).

• Set the Increment to 500 M Bytes.
• Set Maximum Size to Unlimited.
Click OK
On the Options tab, specify the following:
• Select Use Locally Managed Tablespace.

• As Allocation, select Automatic.
• Select Use Automatic Segment Space Management.
iv. Click Apply.
d. Create the tablespace ECR_INDEX. Proceed as for the tablespace ECR_DATA in
Step 13.c but enter a different name (for example, ECR_INDEX) and file name
(for example, ECR_INDEX_1.dbf).
14. Configure the redo log groups:
a. Expand the Redo Log Groups.

b. Click redo log group 1.
c. Set the File Size to 100 M Bytes.
d. Verify the directory for the first redo log member.
e. Add at least one other file to the redo log members. This file must be
located on a separate disk. If you use a SAN (Storage Area Network) or
something comparable you can omit this point.
f. Repeat the definition (steps 14.b to 14.e) for the redo log groups 2 and 3.
15. Summary: Click Finish and confirm with OK.

The database creation may take some time.
16. Database Configurations Assistant: Note the database control URL displayed,
and click Exit.
The database is now created and started.
6.1.2 Creating the database user

The following procedure shows administration privileges required for creating a
database schema.
Technical database users who run an Archive Server database on a regular basis do
not need the full scope of administration privileges that are required for creating a
database. For more information, see “Administration privileges for running a
database schema” on page 61.
To create the database user:
1. Start SQL*Plus.

AR160200-00-IGU-EN-02
oracle>> export ORACLE_SID=ECR

oracle>> sqlplus /nolog
connect / as sysdba
2. Enter the following SQL commands:
create user ecr identified by ecr;
grant create sequence to ecr;

grant create table to ecr;
grant create view to ecr;
grant create session to ecr;
grant create procedure to ecr;
grant execute on DBMS_SQL to ecr;
alter user ecr default tablespace ecr_data;

alter user ecr quota unlimited on ecr_data;
alter user ecr quota unlimited on ecr_index;
exit
Note: Using a role to grant the rights indirectly is not sufficient as stored
procedures will not have the rights.
Administration privileges for running a database schema

After successful creation of the database schema, you can reduce the set of
privileges. We assume that the same database user is used to create and to run the
database schema.
grant create session to ecr;

grant create sequence to ecr;
alter user ecr quota unlimited on ecr_data;
Notes
• The CREATE SEQUENCE privilege is required only to adjust the Archive Server
sequences.
You do not need specific privileges to delete Archive Server sequences.
However, grant create sequence to ecr; is required to create a new
Archive Server sequence.
• If you use a different user to run the database than its owner (the user who
created the database), the user running the database needs additional rights.
Assign the missing “object privileges” by running a corresponding grant
all command, for example.

AR160200-00-IGU-EN-02
6.1.3 Configuring the Oracle Listener

1. Log on as user oracle.
2. Ensure that the following is set:
oracle>> TERM=xterm
SLES
On SUSE Linux Enterprise Server, leave <host_xserver> empty.
As root, execute the following:
root>> xhost +
3. Go to the Oracle bin directory and start the Net Manager tool:
./netmgr
4. If the location of the net configuration files is the default location, the existing
configuration has been loaded.
If you use a nonstandard location, click File > Open Network Configuration to
edit the listener configuration. Enter the according name of the directory
containing the listener.ora file, and then click OK.
5. Expand Oracle Net Configuration > Local > Listeners and click the name of the
existing listener, for example, LISTENER.
Select Listening Locations. There should be at least the following two
addresses:
• TCP/IP with your host and the port (default: 1521)

• IPC with key ORACLE_SID (default ECR)
6. Select Database Services and click Add Database.
7. Enter the global database name (for example, ECR), the Oracle home directory
(for example, /software/ora102/) and the SID (for example, ECR).
8. Click File > Save Network Configuration to save the listener configuration to
the listener.ora file.
9. To make your changes effective, you have to restart the listener. Open a
command prompt and enter
lsnrctl stop
lsnrctl start
The listener is now configured and ready for use.

AR160200-00-IGU-EN-02
6.1.4 Configuring Oracle TNS Service Names

To use SQL*Plus with Net Services Names and for some components of Archive
Center, you need to configure the tnsnames.ora file.
1. Set the following:
oracle>> TERM=xterm
2. Go to the Oracle bin directory and start the Net Manager tool:
./netmgr
3. If the location of the net configuration files is the default location, the existing
configuration has been loaded.
If you use a nonstandard location, click File > Open Network Configuration to
edit the Net Service Name configuration. Enter the according name of the
directory containing the tnsnames.ora file, and then click OK.
4. Expand Oracle Net Configuration > Local and click Service Naming.
5. Click Edit and then click Create.
6. Page 1 of 5, Welcome: Enter the net service name (for example,

ECR_<localhost>) and click Next.
7. Page 2 of 5, Protocol: Select TCP/IP (Internet Protocol) and click Next.
8. Page 3 of 5, Protocol Settings: Enter the database host name and the configured
port of the Oracle listener and click Next.
9. Page 4 of 5, Service: Enter the configured service name of the database (for
example, ECR). Choose Dedicated server as the Connection Type and click
Next.
10. Page 5 of 5, Test: Click Finish.
11. Expand Oracle Net Configuration > Local and click Service Naming.
12. Select the just created service ECR_<localhost>. An address configuration is

displayed showing Address 1. Click + to add another address.
13. Select IPC as protocol and the ORACLE_SID of the database just created as Key
Name.
14. Click File > Save Network Configuration to save the Net Service Name
configuration to the tnsnames.ora file.

AR160200-00-IGU-EN-02
6.1.5 Post-installation tasks

As Oracle Database is probably installed with another file owner than the Archive
Server installation will use, the lib and bin directories and the containing files need
read and execute rights.
Important
You have to grant additional permissions manually as user root or oracle.
Change the permissions as shown below.
To change permissions of tnsnames.ora:
• Execute the following commands:
chmod a+rx $ORACLE_HOME

chmod a+rx $ORACLE_HOME/oracore
chmod a+rx $ORACLE_HOME/oracore/zoneinfo
chmod a+rx $ORACLE_HOME/rdbms
chmod a+rx $ORACLE_HOME/rdbms/mesg
chmod a+rx $ORACLE_HOME/nls
chmod a+rx $ORACLE_HOME/nls/data
chmod a+rx $ORACLE_HOME/lib
chmod a+rx $ORACLE_HOME/network
chmod a+rx $ORACLE_HOME/network/admin
chmod -R a+rx $ORACLE_HOME/lib
chmod -R a+rx $ORACLE_HOME/oracore/zoneinfo
chmod -R a+rx $ORACLE_HOME/network/admin
chmod -R a+rx $ORACLE_HOME/nls/data
chmod -R a+rx $ORACLE_HOME/rdbms/mesg
6.2 Oracle Database and Archive Spawner on one

computer
This section applies to each operating system as described in “Appendix: Special
commands and other OS-specific topics“ on page 65.
If the database and Archive Center are installed on the same computer, you have to
make sure that the Archive Spawner process is started after and shut down before the
Oracle Database instance and the Oracle TNS Listener.
For more information, see the chapter “Starting Up and Shutting Down” in the
Oracle Database Online Documentation 12c Release 1 (12.1) – Database
Administrator's Guide (https://docs.oracle.com/database/121/ADMIN/start.htm), for
example.

AR160200-00-IGU-EN-02
Chapter 7
Appendix: Special commands and other OS-
specific topics
This chapter informs about commands for starting and stopping Archive Center and
further operating system-specific topics.
7.1 Special issues of Red Hat Linux systems

See also “Oracle Database and Archive Spawner on one computer ” on page 64.
7.1.1 Stopping or starting Archive Center

Observe that a local database instance will not be started or stopped together with
the Archive Spawner.
To start Archive Spawner at boot time:
1. Log on as user root.

2. Enter the following:
chkconfig --add spawner
Note: The /etc/init.d/spawner script already has the following entries

for start/stop in the run levels 0 to 6:
spawner 0:off 1:off 2:off 3:on 4:off 5:on 6:off
Starting/ If you have run the chkconfig --add spawner command, you can use the
stopping with following service commands to start or stop the Spawner:
service
command
To stop Archive Spawner using service command:

service spawner stop
To start Archive Center using service command:

service spawner start
3. Check whether the Archive Spawner runs correctly with spawncmd status.

AR160200-00-IGU-EN-02
Chapter 7 Appendix: Special commands and other OS-specific topics
Starting/ If you did not run the chkconfig --add spawner command, you can use the
stopping following commands to start or stop the Spawner:
without service
command
To stop Archive Center:

sh /etc/init.d/spawner stop
To start Archive Center:

sh /etc/init.d/spawner start
7.1.2 Solving problem with dsh command validUser

To make the dsh command validUser (“validate user and password”) work for OS
users on Red Hat systems, you must configure the Pluggable Authentication
Modules (PAM) policy.
To configure the PAM policy:
1. In the /etc/pam.d/ directory, create a file named validuser.

2. Open the file in an editor and add the following lines:
auth include password-auth

account include password-auth
password include password-auth
3. Save the file and assign the following permissions: 644, with owner root and
group root.
7.2 Special issues of SUSE Linux systems

See also “Oracle Database and Archive Spawner on one computer ” on page 64.
Stopping or starting Archive Center

Observe that a local database instance will not be started or stopped together with
the Archive Spawner.
To stop Archive Center:


AR160200-00-IGU-EN-02
7.2. Special issues of SUSE Linux systems
sh /etc/init.d/spawner stop
To start Archive Center:
sh /etc/init.d/spawner start

AR160200-00-IGU-EN-02

OpenText Archive Center 16 2 Installation Guide For UNIX Linux English AR160200 00 IGU en 02 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

OpenText Archive Center 16 2 Installation Guide For UNIX Linux English AR160200 00 IGU en 02 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

OpenText™ Archive Center

Installation Guide for UNIX/Linux

This guide describes the setup of OpenText Archive Center 16

Further, the installation of OpenText™ Archive Cache Server is

Open Text Corporation

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

Copyright © 2017 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

PRE About OpenText Archive Center v

1 Prerequisites for Archive Center ............................................. 9

2 Setting up the database .......................................................... 23

3 Installing Archive Center and additional components ........ 29

OpenText Archive Center – Installation Guide for UNIX/Linux iii

3.8 Installing Solution Registry Agent ..................................................... 40

4 Configuring Archive Center .................................................... 47

5 Setting up Archive Cache Server ........................................... 51

6 Appendix: Setting up the database in Oracle Database ...... 57

7 Appendix: Special commands and other OS-specific

iv OpenText Archive Center – Installation Guide for UNIX/Linux

Archive Center OpenText™ Archive Center Administration is a web-based, easy-to-use client

OpenText Archive Center customers, called tenants, administrate the archiving of

Access OpenText™ Archive Center Access is a web-based, easy-to-use client included in

OpenText Archive Center – Installation Guide for UNIX/Linux v

vi OpenText Archive Center – Installation Guide for UNIX/Linux

OpenText Archive Center – Installation Guide for UNIX/Linux vii

Prerequisites for Archive Center

General Do the following to ensure a successful installation of Archive Center:

OpenText Directory Services

OpenText Archive Center – Installation Guide for UNIX/Linux 9

Administration Client can only be installed on Windows systems. Any

Conventions The following variables are conventions for this documentation:

1.1 Configuring basic settings

1.1.1 Hardware and software recommendations

Prerequisites for hard disk systems

10 OpenText Archive Center – Installation Guide for UNIX/Linux

1.1.2 Network recommendations and restrictions

To verify correct resolving of IP addresses:

1. On the Archive Center host, run

OpenText Archive Center – Installation Guide for UNIX/Linux 11

1.1.3 Testing network environment

ping <server name>

1.1.4 Checking computer name

1.1.5 Setting access rights and exporting mount points

To export the mount points:

1. Add the two following lines in the /etc/exports file:

12 OpenText Archive Center – Installation Guide for UNIX/Linux

2. Export all file systems for the current session.

Run the following command:

systemctl enable nfs-server.service

1.2 Installing Java

2. Install the JDK according to the instructions.

3. For known issues concerning the installation of Java and troubleshooting

OpenText Archive Center – Installation Guide for UNIX/Linux 13

1.3 Setting up Apache Tomcat

1.3.1 Installing Tomcat

3. Log on as this user.

4. Install the Tomcat software according to the documentation.

5. Open the $CATALINA_HOME/conf/logging.properties file in an editor.

1.3.2 Configuring the connector and securing Tomcat

14 OpenText Archive Center – Installation Guide for UNIX/Linux

To configure Tomcat for SSL/TLS:

1. From the <Tomcat_home>/conf directory, open server.xml in an editor.

3. After the line <Service name="Catalina">, define an HTTP connector port