OpenText Archive Center On UNIX-Linux 16.0 - Upgrading Archive Server 10.5.0 SP1 To Archive Center 16 English (AR160000-00-DUO-EN-1)

OpenText™ Archive Center on UNIX®/
Linux®
Upgrading Archive Server 10.5.0 SP1 to

Archive Center 16
This guide describes how to upgrade all components of

OpenText™ Archive Server 10.5.0 SP1 to version OpenText
Archive Center 16 on a UNIX/Linux platform with an Oracle
Database or SAP® HANA. Besides OpenText Archive Center,
this also includes administration tools and Archive Cache
Server.
AR160000-00-DUO-EN-1
OpenText™ Archive Center on UNIX®/Linux®
Upgrading Archive Server 10.5.0 SP1 to Archive Center 16
AR160000-00-DUO-EN-1
Rev.: 2016-Mar-24
This documentation has been created for software version 16.0.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text SA
40 Avenue Monterey , Luxembourg, Luxembourg L-2163
Tel: 35 2 264566 1
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: http://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2016 Open Text SA or Open Text ULC (in Canada). All Rights Reserved.
Trademarks owned by Open Text SA or Open Text ULC (in Canada).
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
Table of Contents
1 Introduction ................................................................................ 5
2 Preparing the upgrade of Archive Server 10.5.0 SP1 ............. 7

2.1 General preparations ......................................................................... 7
2.2 Prerequisites .................................................................................. 10
2.3 Preparing OpenText Directory Services ............................................ 10
2.3.1 Connecting Archive Server to Directory Services ............................... 11
2.3.2 Migrating a local Directory Services to version 16 .............................. 12
2.4 Prerequisites for Oracle Database .................................................... 13
3 Setting up Apache Tomcat 8 .................................................. 15

3.1 Installing Tomcat ............................................................................. 15
3.2 Configuring and securing Tomcat ..................................................... 16
4 Upgrading Archive Server 10.5.0 SP1 ................................... 19

4.1 Using the Installer for Archive Center for upgrading ........................... 19
4.2 Upgrading Archive Server ................................................................ 21
4.3 Upgrading Archive Monitoring Server ............................................... 22
4.4 Installing Email Cloud Archiving ....................................................... 23
4.5 Manual database update ................................................................. 24
4.6 Actions after the upgrade ................................................................. 25
4.6.1 Configuring Java options for optimal performance ............................. 25
4.6.2 Configuring paths for Tomcat ........................................................... 25
4.6.3 Installing patches ............................................................................ 26
4.6.4 Configuring OTDS ........................................................................... 26
4.6.5 Miscellaneous ................................................................................. 27
4.7 Configuring the Application Layer ..................................................... 28
5 Upgrading Archive Cache Server 10.5.0 SP1 ........................ 29

5.1 Prerequisites .................................................................................. 29
5.2 Running the setup ........................................................................... 29
5.3 Actions after the upgrade ................................................................. 30
6 Upgrading OpenText Document Pipelines 10.5.0 SP1 ......... 31

6.1 Installing Document Pipeline Perl ..................................................... 31
6.2 Upgrading Document Pipeline Base ................................................. 32
6.3 Installing Document Pipeline for Archive Center ................................ 32
7 Installing additional Windows® software .............................. 35
8 Testing the upgrade ................................................................ 37

8.1 Testing the running processes ......................................................... 37
8.2 Testing the complete archive functionality ......................................... 37
OpenText Archive Center on UNIX/Linux – Upgrading Archive Server 10.5.0 SP1 to Archive
Center 16 iii
AR160000-00-DUO-EN-1
Table of Contents
8.3 Notify OpenText about your success ................................................ 37
iv Center 16
AR160000-00-DUO-EN-1
Chapter 1
Introduction
This guide describes how to upgrade OpenText Archive Server 10.5.0 SP1 (short
term: Archive Server) to OpenText Archive Center 16 (short: Archive Center) on a
UNIX or Linux platform with Oracle Database or SAP HANA as database system.
Important
• Order of upgrades
Perform the upgrade of different components in the following order.
Depending on the scenario, not all components may be present.
1. Upgrade Archive Cache Server.
2. Upgrade remote-standby server(s).
3. Upgrade OpenText Document Pipeline server(s).
4. Upgrade original Archive Server
• Passwords of system users
Do not change the passwords of the system users archiveall, rfcuser,
user, and scan. Otherwise, archiving and viewing of documents are no
longer possible. If, for security reasons, you wish to use other passwords,
contact OpenText Customer Support.
• Upgrade of former versions
Upgrade to Archive Center 16 is only supported from version 10.5.0 SP1.
If you have an older version you must upgrade to version 10.5.0 SP1 first.
Upgrading Please note that this guide applies to other software components of Archive Center
other 16 as well. In particular, the upgrade of Archive Cache Server is described in this
components
guide.
The steps affecting the database (“Prerequisites for Oracle Database” on page 13
and “Manual database update” on page 24) are specific for the actual Archive
Center and must be skipped for other software configurations.
DPs For information about the upgrade of OpenText Document Pipeline, see OpenText
Document Pipeline - Installation and Upgrade Guide (AR-IDPDP).
Administration The administration of Archive Center, like adding logical archives, is handled
Client through a snap-in for Microsoft Management Console called OpenText
Administration Client.
Administration Client requires a Windows system.
Center 16 5
AR160000-00-DUO-EN-1
Chapter 2
Preparing the upgrade of Archive Server 10.5.0 SP1
2.1 General preparations

Observing global assumptions
Mandatory The following settings are important for a successful upgrade:
settings
• For AIX/HP-UX/Solaris: - Make sure that /usr/sbin is part of the PATH for user
root.
• For Linux: - Make sure that /sbin is part of the PATH.
• The umask of root is 022 (may be displayed as 0022).
To find out, use root>> umask
• root has to use a Bourne shell or compatible (ksh, msh, or bash. Do not use csh!).
To find out, use root>> echo $SHELL
Conventions The following settings are conventions for this documentation:

• The home directory of the Oracle database is <ORACLE HOME>.
• The new version of Archive Center will be installed in <OT install AC>.
• The Archive Center host is <AS host>.
• The installation image is available via the mount point <mountpoint>.
Using former installation notes

The notes that you made during the installation of the current Archive Server
version can contain important information. If such notes exist, review them before
the upgrade.
Checking MY_HOST_NAME variable

The Archive Center Installer requires the MY_HOST_NAME variable to be set to the
fully-qualified host name of the computer hosting Archive Server.
To set the MY_HOST_NAME variable:
1. Start OpenText Administration Client and sign in to Archive Server.
2. Select the Archive Server > Configuration node in the action pane, and in the
result pane, search for MY_HOST_NAME.
3. Open the Properties of the External Archive Server Host Name variable
(internal name: AS.DS.MY_HOST_NAME).
Center 16 7
AR160000-00-DUO-EN-1
Chapter 2 Preparing the upgrade of Archive Server 10.5.0 SP1
As its Value, enter the fully-qualified name of the computer hosting Archive
Server, for example: archive_server.example.com
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 Solaris 11 is 256, 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.
Informing users about downtime

Inform all users as early as possible about the scheduled downtime. Inform them
that all scanned documents must be archived before Archive Server is upgraded.
That means that no scanned documents must remain visible in Enterprise Scan and
its pipelines when the upgrade starts.
Stopping the traffic on Archive Server

In order to prevent document loss or corruption, you must stop all archiving
activities before you begin the software upgrade.
To stop traffic on Archive Server:
1. When the announced downtime has come, make sure that all document pipelines
are emptied. You can do this with the Document Pipeline Info program. See
section 5 “Using Document Pipeline Info” in OpenText Document Pipelines -
Overview and Import Interfaces (AR-CDP) for details.
2. If the document pipelines are not empty, you must wait until all documents are
archived (this may occur when the documents are very large or there are many
documents), or you may need to correct a possible error condition.
8 Center 16
AR160000-00-DUO-EN-1
2.1. General preparations
3. Make sure that OpenText client programs are not running (such as Enterprise
Scan, Administration Client, Monitor Client, Document Pipeline Info and
command-line tools such as dsClient).
4. In case of upgrading Archive Cache Server: OpenText strongly recommends

making sure that no write-back documents are pending during the upgrade of
Archive Cache Server. To ensure that no write-back documents are pending,
proceed as follows:
a. For each logical archive hosted by Archive Cache Server in write-back

mode:
i. Open the Archive Administration of the corresponding Archive

Server.
ii. In the Servers tab, locate the logical archive.
iii. In the Cache Server settings of the logical archive, locate your Archive
Cache Server and edit the Properties.
iv. Clear the Caching enabled check box.
Note: Alternatively, you can leave the caching enabled but change the
caching mode from write-back to write-through.
b. Run the “copy back” job for your Archive Cache Server on each Archive
Server using your Archive Cache Server.
Use cs2ds -count on Archive Server to check whether write-back
documents are still pending.
After the upgrade of Archive Cache Server and all Archive Servers using this
Archive Cache Server, re-enable the “Caching enabled” flag (or switch the
caching mode back from write-through to write-back). See “Actions after the
upgrade” on page 25.
Performing a complete backup

Before you begin the upgrade, you should backup the database, the disk buffer and
hard-disk partitions, and the entire software installation, including the software
itself and the configuration information. The necessary steps are described in section
19 “Backups and recovery” in OpenText Archive Center - Administration Guide (AR-
ACN).
In particular, in case the Storage Manager (STORM) is used: Make a backup of the
STORM files as described in section 19.2 “Backing up and restoring of the Storage
Manager configuration” in OpenText Archive Center - Administration Guide (AR-ACN).
Center 16 9
AR160000-00-DUO-EN-1
2.2 Prerequisites
Java Archive Center 16 requires Java 8 Update 40 or later. To verify your Java
environment, use the command java -version or go the Java Download Center at
http://java.com/en/download/index.jsp.
Application While Archive Server 10.5.0 SP1 runs on Apache Tomcat 7, Archive Center 16 runs
server on Apache Tomcat 8 only. See “Setting up Apache Tomcat 8“ on page 15.
The Tomcat 7 and Archive Spawner services must be stopped before the upgrade.
The Tomcat 8 service must be running.
No pending All documents must have been written to storage before starting the upgrade. Check
write jobs that there are no pending write jobs:
On the command line, run dscd -size
The output must be empty.
Empty buffers All disk buffer volumes must be empty before starting the upgrade. Run the
Purge_Buffer job for each volume and check its protocol.
Note: In rare cases, there may be entries in the database for components that
do not reside in a buffer. To avoid such problems, check the ds_job table.
OTDS Archive Center 16 requires OpenText™ Directory Services 16. For more information,
see “Preparing OpenText Directory Services” on page 10.
.NET 4.5.1 OpenText™ Administration Client requires .NET Framework 4.5.1. Verify that the
“.NET Framework 4.5” feature is enabled in the Windows Server Manager. The
Archive Center Installer does not check for this requirement.
2.3 Preparing OpenText Directory Services

With the “classic” Archive Server, the usage of Directory Services was optional.
Archive Center 16 requires OpenText Directory Services 16. Depending on your
current scenario, do one of the following.
No OTDS
If you run your current Archive Server without Directory Services (that is with
Archive Server’s built-in user management; “dsadmin”), you can use the
Archive Center Installer to install and configure a local instance of Directory
Services with Archive Center 16.
Alternatively, you can install Directory Services 16 on a remote server manually
and configure Archive Server to use it.
For more information about installing Directory Services remotely, see OpenText
Directory Services - Installation and Administration Guide (OTDS-IWC) and
“Connecting Archive Server to Directory Services” on page 11.
10 Center 16
AR160000-00-DUO-EN-1
2.3. Preparing OpenText Directory Services
Remote OTDS
If you use Directory Services already on a remote server, you must upgrade
Directory Services to version 16 before you can start the upgrade of Archive
Server.
For more information, see section 1.3 “Importing Data from Previous Versions of
OpenText Directory Services to 16” in OpenText Directory Services - Installation
and Administration Guide (OTDS-IWC).
Local OTDS
If you use Directory Services already on the server that also runs Archive Server,
you must migrate Directory Services to version 16 before you can start the
upgrade of Archive Server.
Important
If Directory Services is installed locally but not used by Archive Server (that
is Archive Server uses built-in user management), you must first
configure Archive Server to use Directory Services. For more
information, see “Connecting Archive Server to Directory Services”
on page 11.
Afterwards, migrate Directory Services to version 16.
For more information about migrating a local installation of Directory Services,

see “Migrating a local Directory Services to version 16” on page 12.
2.3.1 Connecting Archive Server to Directory Services

To use Directory Services with Archive Server, an OTDS resource is required. You
can set up a resource easily in OpenText Administration Client.
To connect Archive Server to Directory Services:
1. Start Administration Client, sign in to Archive Server, and select Archive Server
in the console tree.
2. In the action pane, click OTDS Connection.
The OTDS Connection wizard opens.
3. On the Connection page, enter the following:
OTDS server URL

Enter the server hosting OTDS as URL: <protocol>://<server>:<port>
For example, https://otds_server.example.com:8090
OTDS administrator
Enter the name of the OTDS administrator; default: otadmin@otds.admin
OTDS administrator password
Enter the password of the OTDS administrator.
4. On the Resource page, enter a resource name for Archive Server.
Resource names must be unique.
Center 16 11
AR160000-00-DUO-EN-1
5. On the Summary page, verify your entries and click Finish. The resource is
created.
Restart Archive Server to activate the new resource.
Important
From now on, you cannot sign in to Archive Server using dsadmin
anymore. Instead, use otadmin@otds.admin.
Note: To modify the resource, you must sign on to Directory Services.
For more information, see also section 9.9 “Connecting to Directory Services” in
OpenText Archive Center - Administration Guide (AR-ACN).
2.3.2 Migrating a local Directory Services to version 16

To migrate Directory Services, you need to export two LDIF files from version 10.5.0
SP1, which are later imported into Directory Services 16.
To export the LDIF files:
1. From the <OT config>/Directory Services 10.5.0/opendj/config directory

(default: ), copy the config.ldif file to a temporary directory.
2. In the <OT config OTDS>/opendj/bin directory (default: /

usr/local/OTDS/opendj/bin, run control-panel.bat.
3. In the OpenDJ Control Panel, sign in to the Local Server. The password of this
“cn=Directory Manager” account is initially set to the password of the OTDS
administrator (otadmin@otds.admin).
Note: Changing the OTDS password does not change the “cn=Directory
Manager” password as these are different accounts. You can change the
password using the otdstenant -resetpassword command. For more
information, see OpenText Directory Services - Tenant Management Guide
(OTDS-CCS).
4. In the Directory Data area, click Export LDIF.
5. On the Export LDIF page, do the following:
a. Keep Backend set to userRoot.

b. In the Export to File box, select the temporary directory from Step 1. The
name of the exported file must be otds-10.5.0.ldif!
c. Keep the Wrap Text at Column box cleared.
d. Click OK.
To install Directory Services 16:
1. Stop the Apache Tomcat 7 and Archive Spawner services.
12 Center 16
AR160000-00-DUO-EN-1
2.4. Prerequisites for Oracle Database
2. Install Tomcat 8 as described in “Setting up Apache Tomcat 8“ on page 15.
3. Start the Apache Tomcat 8 service.
4. Install Directory Services 16 according to OpenText Directory Services -

Installation and Administration Guide (OTDS-IWC).
When asked by the installer, select Import Data from OpenText Directory
Services 10.5.0 and enter the path to the temporary directory to which you
exported the LDIF files (Step 1 of the previous procedure).
2.4 Prerequisites for Oracle Database

Archive Center 16 continues to support Oracle Database 11.2 and 12.1.
Oracle Database 11.2 requires the patch level 11g Release 2 (11.2.0.4).
Running the check script on Oracle Database

Check the database schema before you start the upgrade procedure.
To check the schema:
1. Check if the TNS_ADMIN variable has the correct value.
2. Download the latest version of the pre-upgrade check SQL script

(StPreUpgCheckOracle.sql) from the Knowledge Center (https://
knowledge.opentext.com/knowledge/cs.dll/Open/15052349).
3. Perform the following command in the directory which contains

StPreUpgCheckOracle.sql:
sqlplus <otuser>/<password>@<service>
Example:
sqlplus ecr/ecr@ecr_<db_host>
4. Start the pre-upgrade check script:
SQL> @StPreUpgCheckOracle.sql
The data and index tablespace names are displayed.
Notes
• You can start the upgrade if you get no messages beginning with FATAL or
saying “not ok”.
• If you get a FATAL message or a “not ok”, fix the problem before proceeding.
• Warnings of type “additional table … found in schema” can be ignored.
Center 16 13
AR160000-00-DUO-EN-1
Important
For known problems that may be detected by the pre-upgrade check and
how to solve them, see the Knowledge Center (https://
knowledge.opentext.com/knowledge/llisapi.dll/Overview/1144682057_372).
14 Center 16
AR160000-00-DUO-EN-1
Chapter 3
Setting up Apache Tomcat 8
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.
• Install Tomcat. For more information, see “Installing Tomcat” on page 15.
HP-UX only
The Tomcat installation included in HP-UX is not supported as it is based
on Tomcat 7. You need to install Tomcat 8 as described in “Installing
Tomcat” on page 15.
• Configure SSL/TLS for Tomcat. For more information, see “Configuring and
securing Tomcat” on page 16.
3.1 Installing Tomcat

To install Tomcat:
1. Download the Apache Tomcat software version 8.0.30 (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.
Center 16 15
AR160000-00-DUO-EN-1
Chapter 3 Setting up Apache Tomcat 8
3.2 Configuring 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.
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: 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"
16 Center 16
AR160000-00-DUO-EN-1
3.2. Configuring and securing Tomcat
SSLEnabled="true"
scheme="https"
secure="true"
sslProtocol="TLS"
sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"
protocol="HTTP/1.1"
acceptCount="100"
maxHttpHeaderSize="8192"
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),
you must set clientAuth to want.
• On AIX, you must use sslProtocol="SSL" instead of
sslProtocol="TLS".
• disableUploadTimeout must be set to true (default).
enableLookups must be set to false (default).
• You must not use either of the following protocol settings in the SSL
connector:
protocol="org.apache.coyote.http11.Http11NioProtocol"
protocol="org.apache.coyote.http11.Http11AprProtocol"
• If you plan to use Tomcat for Document Pipeline Remote Interface, you
must use sslProtocol="SSL" instead of sslProtocol="TLS".
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).
Center 16 17
AR160000-00-DUO-EN-1
Chapter 4
Upgrading Archive Server 10.5.0 SP1
If you have fulfilled all prerequisites, you can start with the upgrade installation.
4.1 Using the Installer for Archive Center for

upgrading
Installer for Archive Center offers a convenient way to install or upgrade all
required components. Its general usage is explained in the following.
Important
Stop Tomcat 7 before the upgrade.
Stop all OpenText software (Archive Spawner, Content Server) before

upgrading.
To install Archive Center components:
1. Download the product's ISO-9660 image from the OpenText Knowledge Center
and burn a DVD from it.
Alternatively, mount the ISO image as a virtual drive. For detailed instructions,
see the Knowledge Center (http://mimage.opentext.com/support/ecm/secure/
software/checksuminstructions.html).
2. Log on as root.
Notes
• Settings for PATH
Make sure that 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_xx, expand the PATH variable to include the location of a valid
JDK.
Test again as described.
Alternatively, you can set the JAVA_HOME variable; for example:
root>> export JAVA_HOME=/software/java/latest/
To test the setting, use $JAVA_HOME/bin/java -version
• Make sure that /usr/sbin is included in the PATH environment variable.
3. Mount the product's DVD or ISO image (for example, as /dvd).
4. Change to the mounted directory and start the installation:
Center 16 19
AR160000-00-DUO-EN-1
Chapter 4 Upgrading Archive Server 10.5.0 SP1
root>> cd /dvd
root>> ./mastersetup
5. Enter N to get to the License agreement page.

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

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

At any time, you can enter C to cancel the upgrade.
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 to continue.
7. Product Groups: Additional components can be selected to be installed. Select

additional components if necessary. Enter N to continue.
All components with status “upgradeable” must be selected.
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 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 the Document Pipelines and will be the owner of all
installation directories.
9. Enter N to continue.
10. Enter I 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 silent, just the “Start” and “Finish” dialogues are displayed
20 Center 16
AR160000-00-DUO-EN-1
4.2. Upgrading Archive Server
• needs additional input for further configuration dialogues

11. When all setups have finished, the Installer exits automatically.
Note: Depending on the scenario to be upgraded, some of the installation steps

described in the subsequent sections will not show up.
4.2 Upgrading Archive Server

To upgrade Archive Server:
1. Follow the procedure in “Using the Installer for Archive Center for upgrading”
on page 19 to start the setup of Archive Center.
2. Upgrade installation: Enter Y to start the upgrade.
3. Execute SQL scripts for Oracle database schema upgrade: Enter Y to create
and execute the script for the database configuration. Enter N to only create the
script without executing it.
Important
OpenText recommends executing the script. However, if you choose not
to execute the schema, you will have to execute the script manually.
Otherwise, Archive Center will not work.
For more information, see “Manual database update” on page 24.

4. A list of installation parameters is displayed. Next, the missing and invalid
parameters will be collected.
5. Tomcat directory: Enter the path to Tomcat 8, for example: /
software/opentext/tomcat/latest8
6. Installation destination root directory: Enter the path to the new installation
directory, default: /opt/opentext/ArchiveServerSoftware_16_0_0
The installation directory must be empty.
7. Configuration destination root directory: Enter the path to the new
configuration directory, default: /
opt/opentext/ArchiveServerConfig_16_0_0
The configuration directory must be empty.
8. User management system: Select the user management system for Archive
Center: OpenText Directory Services (OTDS) or built-in user management
(dsadmin).
Note: You can change the user management settings at any time after
upgrade in the Administration Client.
If OTDS is used, do the following:
a. OTDS protocol: Type the protocol (HTTP or HTTPS) for OTDS.
Center 16 21
AR160000-00-DUO-EN-1
b. OTDS server name: Type the name of used OTDS server.

c. OTDS port: Type the port for OTDS.
d. OTDS resource: Type the resource ID of the OTDS resource that is
assigned to this Archive Center.
9. 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.
10. 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
4.3 Upgrading 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 upgrade Archive Monitoring Server:
1. On the computer to be monitored, follow the procedure in “Using the Installer

for Archive Center for upgrading” on page 19 to start the setup of Archive
Monitoring Server.
3. A list of installation parameters is displayed. Next, the missing and invalid

4. Tomcat only: Path to the Apache Tomcat installation directory: Enter the path to
the <Tomcat home> directory. The default for Tomcat is CATALINA_HOME.
5. Installation destination root directory: Enter the destination directory,

default: /opt/opentext/ArchiveMonitoringServer_16_0_0
22 Center 16
AR160000-00-DUO-EN-1
4.4. Installing Email Cloud Archiving
6. Configuration destination root directory: Enter the directory for the

configuration information, default: /
opt/opentext/ArchiveMonitoringServerConfig_16_0_0

a. Enter Y.
installation.
/opt/opentext/log/opentext_instlog/SetupArchiveMonitoringServer
4.4 Installing Email Cloud Archiving

Archive Center Email Cloud Archiving is required for the connection to Archive
Center Proxy, regardless of the supported scenarios.
To install Email Cloud Archiving:
on page 19 to start the setup of Email Cloud Archiving.
2. Installation destination root directory: Enter the destination directory,

default: /opt/opentext/EmailArchivingSoftware_16_0_0
3. Configuration destination root directory: Enter the directory for the

configuration information, default: /
opt/opentext/EmailArchivingConfig_16_0_0
4. Email directory (also called email root directory): Enter the directory for the
SMTP relay server to save emails temporarily.
Important
If archiving of an email fails, it is kept in a subdirectory of this directory
and is not deleted automatically. Depending on the number and size of
the failed emails, the directory can grow very quickly. Therefore,
OpenText recommends placing it on a dedicated hard disk that is large
enough to hold as many emails as are expected to arrive within one
week.
Center 16 23
AR160000-00-DUO-EN-1
You can also change the directory location later using the Root folder for
buffering emails configuration variable (internal name:
EC.ECA.configuration.emailsystem.rootfolder).

a. Enter Y.
installation.
/
opt/opentext/log/opentext_instlog/SetupEmailArchiving/install.lo
g
4.5 Manual database update

Important
This applies only if you have chosen to process the SQL script manually
during the installation.
To update the database manually:
1. Change the default permissions of the file.

2. Enter the following command to start the update of the respective schema of the
Oracle Database:
sqlplus <user>/<passwd>@<service> @ <configuration root

directory>/config/sql/DSSchema.sql
24 Center 16
AR160000-00-DUO-EN-1
4.6. Actions after the upgrade
4.6 Actions after the upgrade

4.6.1 Configuring Java options for optimal performance
To configure Java options 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. Add (or edit) the following Java options to optimize memory pool and heap size
for your operating system:
CATALINA_OPTS="-XX:MaxPermSize=256m -Xmx1024m $CATALINA_OPTS"
3. For Solaris, include ‑d64 in CATALINA_OPTS in the setenv.sh file.
CATALINA_OPTS="-XX:MaxPermSize=256m -Xmx1024M -d64

$CATALINA_OPTS"
4. For HP-UX, add the following to the setenv.sh file:
CATALINA_OPTS="-Xss1m -XX:MaxPermSize=256m -Xmx1024M -d64

$CATALINA_OPTS"
5. Make the <Tomcat home>/bin/setenv.sh executable, for example, by running:

root>> chmod 750 setenv.sh
6. Restart Tomcat.
4.6.2 Configuring paths for Tomcat

The SHARED_LIB_PATH variable must be set to the lib directory of Archive Center:
Verify the following path settings in the <Tomcat home>/bin/setenv.sh file. If it
does not exist yet create a new file owned by the user <otuser> and the group
<otgroup>:
AIX
SHARED_LIB_PATH=<OT install AC>/lib

LIBPATH=$SHARED_LIB_PATH:$LIBPATH
export LIBPATH
Linux, Solaris

LD_LIBRARY_PATH=$SHARED_LIB_PATH:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
HP-UX

SHLIB_PATH=$SHARED_LIB_PATH:$SHLIB_PATH
export SHLIB_PATH
Center 16 25
AR160000-00-DUO-EN-1
4.6.3 Installing patches

The installation of the latest patch collection is mandatory.
To install the patches:
1. Check for the latest Update (“Patch Collection”) in the Knowledge Center
(https://knowledge.opentext.com/knowledge/cs.dll/Open/32919421).
2. Install the latest Update according to the documentation. For more information,
see OpenText Archive Server and OpenText Enterprise Library - Update Installation
Guide (UNIX/Linux) (AR-DUG).
4.6.4 Configuring OTDS

Adding administrators in OTDS
If you did not use Directory Services with Archive Server 10.5.0 SP1 before, and if
you created administrative users within the built-in user management, you need to
create corresponding users for Archive Center in Directory Services again. Add the
users to the otasadmins group (administrators for Archive Center) or otadmins
group (administrators for all OpenText products).
Do not delete the old users of the built-in user management as they still can be
required internally.
For more information, see section 8.3 “Configuring Groups” in OpenText Directory
Services - Installation and Administration Guide (OTDS-IWC).
Configuring the access role for Archive Center

In the OTDS web admin client, enable the Include Groups from OUs setting for the
access role of Archive Center. This setting is required by the synchronization
connector and is not set during the upgrade.
For more information, see section 7.7 “To Include/Exclude Groups From
Organizational Units” in OpenText Directory Services - Installation and Administration
Guide (OTDS-IWC).
26 Center 16
AR160000-00-DUO-EN-1
4.6. Actions after the upgrade
4.6.5 Miscellaneous
Important
Do not remove files from the installation folder left over from the old
Archive Server, as some configuration files might have been put there
manually (like Centera.pea, TSM.opt) or timestamp certificates might still
reside there.
IBM Tivoli DR550

If IBM Tivoli DR550 is used as storage, update your TSM client API to version 5.4 or
later.
As Archive and Storage Services 10.5.0 SP1 runs on 64-bit systems, you have to use
the 64-bit version of the TSM client API (tivoli.tsm.client.api.64bit).
Changed location of dsm.sys
The 64-bit version of the TSM client API uses a different location for the
dsm.sys configuration file. Copy, move, or link your existing dsm.sys file
from <TSM install dir>/api/bin to <TSM install dir>/api/bin64.
Attribute migration
From version 10.5.0 SP1 on, all metadata information of a document’s ATTRIB.ATR
file is stored in the database. The database schema has been changed accordingly.
The schema migration of the database must be finished before shadow pools can be
used. Further, local volume migration is not possible unless all documents have
been migrated to the new schema!
For more information, see section 28 “Attribute migration” in OpenText Archive

Center - Administration Guide (AR-ACN).
Enforcing protocol
In mixed IPv4/IPv6 environments it can be necessary to enforce preferred usage of
one of the protocols. If you had enforced the protocol in Archive Server 10.5.0 SP1,
this setting should still be active after the upgrade. Check whether your Spawner
profile contains the AS_PREF_IP=4 line.
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.
Center 16 27
AR160000-00-DUO-EN-1
4.7 Configuring the Application Layer

If you want to use the Application Layer and the web apps of Archive Center,
several additional steps are required. For example, you must create tenants and
enable transaction logs.
For more information, see OpenText Archive Center - Scenario Configuration Guide (AR-
CGD).
28 Center 16
AR160000-00-DUO-EN-1
Chapter 5
Upgrading Archive Cache Server 10.5.0 SP1
The Archive Cache Server setup is not included in the Archive Center Installer. 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 the Knowledge Center (https://knowledge.opentext.com/knowledge/cs.dll/
Open/17370316) and use its installer.
5.1 Prerequisites
For Archive Cache Server, the same prerequisites hold as for Archive Center
regarding Java and Apache Tomcat. For more information, see “Setting up Apache
Tomcat 8“ on page 15.
5.2 Running the setup

To upgrade Archive Cache Server:
1. Start the setup of Archive Cache Server.

A list of installation parameters is displayed. Next, the missing and invalid
3. Tomcat directory: Enter the path to Tomcat 8, for example: /
software/opentext/tomcat/latest8
4. HTTP port: Enter the HTTP port for Archive Cache Server (default: 8080).
5. SSL port: Enter the HTTPS port for Archive Cache Server (default: 8090).
Important
• The ports must be configured in the server.xml configuration file of
Tomcat. For more information, see “Configuring and securing
Tomcat” on page 16.
• If you use other ports with Tomcat 8 than you have used with
Tomcat 7, you must also change the port setting of the Archive Cache
Server in the Administration Client (Archive Server > Environment
> Cache Servers).
6. Installation destination root directory: Enter the path to the new installation
directory.
Center 16 29
AR160000-00-DUO-EN-1
Chapter 5 Upgrading Archive Cache Server 10.5.0 SP1
Note: The installation directory must be empty.

a. Enter Y.
installation.
/tmp/opentext_instlog/SetupArchiveCacheServer/install.log.
5.3 Actions after the upgrade

Certificate/key For internal secure communication between Archive Cache Server and Archive
pairs Center, Archive Cache Server uses a dedicated certificate/key pair. The certificate
has been imported into Archive Center and presumably been enabled before
upgrade as a global certificate named CS_ACS_<Archive Cache Server host name>.
During the upgrade, this key/certificate pair is migrated to the new Archive Cache
Server configuration and used by Archive Cache Server. Make sure that the
certificate is enabled.
Write-back If you had to disable caching for some logical archive in write-back mode, or if you
mode had to switch the caching mode from write-back to write-through (see “Stopping the
traffic on Archive Server” on page 8) you can now re-enable caching for these logical
archives (or switch back from write-through to write-back).
30 Center 16
AR160000-00-DUO-EN-1
Chapter 6
Upgrading OpenText Document Pipelines 10.5.0

SP1
The Installer for Archive Center also upgrades (or installs, if not present) the
Document Pipeline components required for the “extended functionality” of
Archive Center (Application Layer and web apps): Document Pipeline Base, File
Archiving, and Document Pipeline Info.
For information about the upgrade of other Document Pipeline components, see
OpenText Document Pipeline - Installation and Upgrade Guide (AR-IDPDP).
6.1 Installing Document Pipeline Perl

To install Document Pipeline Perl:
1. Start the setup of Document Pipeline Perl.
2. Installation destination root directory: Enter the path to the destination

directory, for example: /opentextsw/DPPerl16_0_0
Note: All other parameters are taken over from the previous setup.

a. Enter Y.
installation.
/opt/opentext/log/opentext_instlog/DPPERL/install.log.
Center 16 31
AR160000-00-DUO-EN-1
Chapter 6 Upgrading OpenText Document Pipelines 10.5.0 SP1
6.2 Upgrading Document Pipeline Base

To upgrade Document Pipeline Base:
1. Start the setup of Document Pipeline Base.

2. Upgrade installation: Enter Y.
3. Installation destination root directory: Enter the destination directory, for
example: /opentext/DPBaseSoftware_16.0.0
a. Enter Y.
installation.
/opt/opentext/log/opentext_instlog/DPBASE/install.log.
6.3 Installing Document Pipeline for Archive Center

Document Pipeline for Archive Center provides the pipelines for the “extended
functionality” of Archive Center. Document Pipeline for Archive Center requires
Document Pipeline Base.
To install Document Pipeline for Archive Center:
on page 19 to start the setup of Document Pipeline Base.
2. Installation destination root directory: Enter the destination directory, for
example: /opt/opentext/DPAcCmis_16_0_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.
a. Enter Y.
32 Center 16
AR160000-00-DUO-EN-1
6.3. Installing Document Pipeline for Archive Center

installation.
/
opt/opentext/log/opentext_instlog/SetupArchiveDPAcCmis/install.l
og
Center 16 33
AR160000-00-DUO-EN-1
Chapter 7
Installing additional Windows® software
OpenText Administration Client is Windows software and must be installed on

separate computer.
Prerequisites Administration Client is a snap-in for Microsoft Management Console (MMC) and
for Administra- can only be installed on Windows systems. Administration Client requires the
tion Client
Microsoft products .NET Framework 4.5.1, and MMC 3.0 installed on the same
computer. On Windows Server 2008 and Windows Server 2012, check whether these
features are activated.
To install Administration Client:
1. On the computer on which to install Administration Client, either
• insert the DVD you created in “Using the Installer for Archive Center for
upgrading” on page 19 or
• “mount” the ISO image you downloaded as a virtual drive. For details, see
the Knowledge Center (http://mimage.opentext.com/support/ecm/secure/
software/checksuminstructions.html).
2. From the <DVD ROM>:\administration_clients\administration_client

directory, run the administration_client-16.0.0.msi file and follow the
instructions.
Center 16 35
AR160000-00-DUO-EN-1
Chapter 8
Testing the upgrade
8.1 Testing the running processes

After the upgrade, test if all needed processes are running:
1. To check the status of the Archive Spawner, enter spawncmd status and
confirm with RETURN.
2. Check whether the processes chkw and db are terminated (T), as they run only in
certain intervals, but all other processes must be running (R). Otherwise, check
the corresponding log file in the /tmp/opentext_instlog/<service>
directories or contact OpenText Global Technical Services.
8.2 Testing the complete archive functionality

In order to make sure that the upgrade installation was successful, perform the
following tests for all scenarios you are using:
1. Display documents that are archived before the upgrade was done.
2. Archive new documents.
3. Display the new documents.
4. Append notes to old archived documents and display them again.
5. In case you use Storage Manager: Back up the STORM files as soon as possible;
see section 19.2 “Backing up and restoring of the Storage Manager
configuration” in OpenText Archive Center - Administration Guide (AR-ACN).
If problems occur, see the corresponding troubleshooting folder in the Knowledge

Center (https://knowledge.opentext.com) or contact OpenText Global Technical
Services.
8.3 Notify OpenText about your success

When you have successfully completed all tests, update your system information in
the Customer Self Service portal (https://css.opentext.com). With this information,
we can keep our customer installation database up-to-date, which helps us
providing faster technical support for you. Thank you for your cooperation.
Center 16 37
AR160000-00-DUO-EN-1

OpenText Archive Center On UNIX-Linux 16.0 - Upgrading Archive Server 10.5.0 SP1 To Archive Center 16 English (AR160000-00-DUO-EN-1)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Archive Center On UNIX-Linux 16.0 - Upgrading Archive Server 10.5.0 SP1 To Archive Center 16 English (AR160000-00-DUO-EN-1)

Uploaded by

Copyright:

Available Formats

OpenText™ Archive Center on UNIX®/

Upgrading Archive Server 10.5.0 SP1 to

This guide describes how to upgrade all components of

40 Avenue Monterey , Luxembourg, Luxembourg L-2163

Open Text Corporation

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

No Warranties and Limitation of Liability

2 Preparing the upgrade of Archive Server 10.5.0 SP1 ............. 7

3 Setting up Apache Tomcat 8 .................................................. 15

4 Upgrading Archive Server 10.5.0 SP1 ................................... 19

5 Upgrading Archive Cache Server 10.5.0 SP1 ........................ 29

6 Upgrading OpenText Document Pipelines 10.5.0 SP1 ......... 31

7 Installing additional Windows® software .............................. 35

8 Testing the upgrade ................................................................ 37

8.3 Notify OpenText about your success ................................................ 37

Administration Client requires a Windows system.

2.1 General preparations

Conventions The following settings are conventions for this documentation:

Using former installation notes

Checking MY_HOST_NAME variable

To set the MY_HOST_NAME variable:

1. Start OpenText Administration Client and sign in to Archive Server.

Increasing file limits

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:

3. Check the limits as follows:

Note: The recommended way to increase the limit strongly depends on

Informing users about downtime

Stopping the traffic on Archive Server

To stop traffic on Archive Server:

4. In case of upgrading Archive Cache Server: OpenText strongly recommends

a. For each logical archive hosted by Archive Cache Server in write-back

i. Open the Archive Administration of the corresponding Archive

Performing a complete backup

2.3 Preparing OpenText Directory Services

For more information about migrating a local installation of Directory Services,

2.3.1 Connecting Archive Server to Directory Services

To connect Archive Server to Directory Services:

OTDS server URL

Note: To modify the resource, you must sign on to Directory Services.

2.3.2 Migrating a local Directory Services to version 16

To export the LDIF files:

1. From the <OT config>/Directory Services 10.5.0/opendj/config directory

2. In the <OT config OTDS>/opendj/bin directory (default: /

4. In the Directory Data area, click Export LDIF.

5. On the Export LDIF page, do the following:

a. Keep Backend set to userRoot.

To install Directory Services 16:

1. Stop the Apache Tomcat 7 and Archive Spawner services.

2. Install Tomcat 8 as described in “Setting up Apache Tomcat 8“ on page 15.

3. Start the Apache Tomcat 8 service.

4. Install Directory Services 16 according to OpenText Directory Services -

2.4 Prerequisites for Oracle Database

Running the check script on Oracle Database

To check the schema:

1. Check if the TNS_ADMIN variable has the correct value.

2. Download the latest version of the pre-upgrade check SQL script

3. Perform the following command in the directory which contains

4. Start the pre-upgrade check script:

The data and index tablespace names are displayed.

3.1 Installing Tomcat

3. Log on as this user.