OpenText Archive Center On Windows 16.0 - Upgrading Archive Server 10.5.0 SP1 To Archive Center 16 English (AR160000-00-DWO-En-2)

OpenText™ Archive Center on Windows®
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 OpenText Archive
Center 16 on a Windows platform with Oracle Database or
Microsoft SQL Server. Besides the current Archive Server, this
also includes pipelines, administration tools, and Archive Cache
Server.
AR160000-00-DWO-EN-2
OpenText™ Archive Center on Windows®
Upgrading Archive Server 10.5.0 SP1 to Archive Center 16
AR160000-00-DWO-EN-2
Rev.: 2016-July-29
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 .............................................................. 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
2.5 Prerequisites for Microsoft SQL Server ............................................. 14
3 Setting up Apache Tomcat 8 .................................................. 17

3.1 Installing Tomcat ............................................................................. 17
3.2 Configuring Java options ................................................................. 17
3.3 Configuring the Tomcat user ............................................................ 18
3.4 Configuring and securing Tomcat ..................................................... 18
4 Upgrading Archive Server 10.5.0 SP1 to Archive Center

16 ............................................................................................... 21
4.1 Running the Archive Center Installer ................................................ 21
4.2 Actions after the upgrade ................................................................. 22
4.2.1 Installing patches ............................................................................ 22
4.2.2 Configuring OTDS ........................................................................... 23
4.2.3 Miscellaneous ................................................................................. 23
5 Upgrading Archive Cache Server 10.5.0 SP1 to version

16 ............................................................................................... 25
5.1 Prerequisites .................................................................................. 25
5.2 Running the setup ........................................................................... 25
5.3 Actions after the upgrade ................................................................. 26
6 Upgrading OpenText Document Pipelines 10.5.0 SP1 ......... 27
7 Testing the upgrade ................................................................ 29

7.1 Testing the running processes ......................................................... 29
7.2 Testing the complete archive functionality ......................................... 29
7.3 Notify OpenText about your success ................................................ 30
OpenText Archive Center on Windows – Upgrading Archive Server 10.5.0 SP1 to Archive
Center 16 iii
AR160000-00-DWO-EN-2
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
Windows platform with an Oracle Database or Microsoft SQL Server database.
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 remote OpenText Document Pipeline server(s).
Do not upgrade local Document Pipelines before you have upgraded
Archive Server!
4. Upgrade original Archive Server.
• 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 as well. In particular, the upgrade of standalone OpenText Document Pipelines and
components
Archive Cache Server is done as described in this guide.
Center 16 5
AR160000-00-DWO-EN-2
Chapter 2
Preparing the upgrade
2.1 General preparations

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).
As its Value, enter the fully-qualified name of the computer hosting Archive
Server, for example: archiveserver.example.com
Checking disk space

Provide enough disk space for your upgrade installation.
• 250 MB on the system disk

• 20 MB in the temp folder
• 500 MB on the disk where the new software is installed (without Java and
application server)
Important
Depending on the database, the resulting transaction logs may become quite
large (several GB). Take care to reserve enough space.
If the upgrade aborts because of insufficient disk space, the database has to
be restored!
Center 16 7
AR160000-00-DWO-EN-2
Chapter 2 Preparing the upgrade
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.
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
8 Center 16
AR160000-00-DWO-EN-2
2.1. General preparations
caching mode back from write-through to write-back). See “Actions after the
upgrade” on page 22.
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).
Backing up job protocols

Existing job protocols will not be visible in the Archive Server > System > Jobs node
of Administration Client after the upgrade anymore.
The corresponding job_<job name>.log files are stored in the <OT config AC>\var
\LogDir\messages folder and will still be present after the upgrade. If you want to
keep the protocols, OpenText recommends backing them up to avoid accidental
deletion, for example, when removing the old installation files.
Disabling disk cache of hard disk

To avoid loss of data, the Windows disk caching has to be disabled. Disk caching is
enabled by default and should already be disabled for the previous version. To be
sure, proceed as follows.
To disable disk caching:
1. Open Administrative Tools > Computer Management > Device Manager >
Disk Drives > Properties of the drive > Policies tab.
2. Clear the Enable write caching on the device check box.
3. Close all the applications opened before, such as Computer Management.
Center 16 9
AR160000-00-DWO-EN-2
2.2 Prerequisites
Java Archive Center 16 requires Java 8 Update 72 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 17.
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.
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, see OpenText Directory
Services - Installation and Administration Guide (OTDS-IWC) and “Connecting
Archive Server to Directory Services” on page 11.
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.
10 Center 16
AR160000-00-DWO-EN-2
2.3. Preparing OpenText Directory Services
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://otdsserver.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.
5. On the Summary page, verify your entries and click Finish. The resource is
created.
Restart Archive Server to activate the new resource.
Center 16 11
AR160000-00-DWO-EN-2
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 information about security settings, 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 folder

(default: %ProgramData%\OpenText\Directory Services 10.5.0\opendj\
config), copy the config.ldif file to a temporary folder.
2. In the <OT config>\Directory Services 10.5.0\opendj\bat folder, 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 folder 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.
2. Install Tomcat 8 as described in “Setting up Apache Tomcat 8“ on page 17.
3. Start the Apache Tomcat 8 service.
12 Center 16
AR160000-00-DWO-EN-2
2.4. Prerequisites for Oracle Database
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 folder 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. To verify that the database has all the required features, download the
StPreUpgCheckOracle.sql check script in a command window (do not use
Powershell). You can find the script in the Schema and Pre-upgrade checks for
AC 16.zip file, which is available in the Knowledge Center (https://
knowledge.opentext.com/knowledge/cs.dll/Overview/62940896).
3. Perform the following command in the folder 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-DWO-EN-2
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).
2.5 Prerequisites for Microsoft SQL Server

Archive Center 16 supports Microsoft SQL Server 2012 and 2014.
Precondition for Archive Center with remote SQL Server

database
For remote Microsoft SQL Server databases, at least the SQL Server Client Tools
must be installed on the Archive Center computer. The component “client
connectivity” is not sufficient. To check whether the client tools are installed, enter
the command sqlcmd on the command line of the Archive Center computer. If the
command is not found, you must install the SQL Server Client Tools from the SQL
Server installation image. See also section 2.1 “Setting up Microsoft SQL Server” in
OpenText Archive Center - Installation Guide for Windows (Integrated Archive Installer)
(AR-IGW).
When sqlcmd is available, proceed with the pre-upgrade check as described in
“Running the check script on SQL Server” on page 14.
Running the check script on SQL Server

Check the database schema before you start the upgrade procedure.
To check the schema:
1. To verify that the database has all the required features, download the
StPreUpgCheckMSSQL.sql check script in a command window (do not use
Powershell). You can find the script in the Schema and Pre-upgrade checks for
AC 16.zip file, which is available in the Knowledge Center (https://
knowledge.opentext.com/knowledge/cs.dll/Overview/62940896).
2. Execute the pre-upgrade check:
sqlcmd -U <user> -P <passwd> -d <database> -S <DBserver> -i

StPreUpgCheckMSSQL.sql
Example:
sqlcmd -U ecr -P <passwd> -d ECR -S <DBserver> -i

sqlcmd -U ixds -P <passwd> -d DS -S <DBserver> -i

Notes
• You can start the upgrade if you get no messages beginning with FATAL
or saying “not ok”.
14 Center 16
AR160000-00-DWO-EN-2
2.5. Prerequisites for Microsoft SQL Server
• If you get a FATAL message or a “not ok”, fix the problem before
proceeding.
• 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).
Center 16 15
AR160000-00-DWO-EN-2
Chapter 3
Setting up Apache Tomcat 8
OpenText recommends that you perform the following steps to install and configure
Tomcat:
1. Install Tomcat.
2. Configure Java options to optimize performance.
3. Configure and secure Tomcat.
3.1 Installing Tomcat

To install Tomcat:
1. Download the Windows Service Installer for the Tomcat software version 8.0.30
or later from https://tomcat.apache.org/download-80.cgi.
2. Run apache-tomcat-8.0.xx.exe to install the Tomcat software.
Notes
• Do not use the ZIP file to install Tomcat.
• Do not select the Native support because the used version of OpenSSL is
incompatible with Archive Center.
Tip: In the Choose Components window of the Apache Tomcat Setup,

select a Normal type of install.
3.2 Configuring Java options

For optimal performance, change the following Java settings for Tomcat.
To configure Java options:
1. Start the Monitor Tomcat tool from Programs > Apache Tomcat > Monitor
Tomcat or by starting bin\tomcat8w.exe in the <Tomcat_home> folder.
2. Click the Java tab.
3. In the Initial memory pool box, specify at least 512 MB.
4. In the Maximum memory pool box, the value you enter should be proportional
to the number of users Directory Services will manage. OpenText recommends
entering a minimum value for Maximum memory pool as follows:
• If your number of users is 25,000 users or less, enter a minimum value of

1024 MB
Center 16 17
AR160000-00-DWO-EN-2
Chapter 3 Setting up Apache Tomcat 8
• If your number of users is 25,000 to 50,000 users, enter a minimum value of

2048 MB
• If your number of users is 50,000 to 100,000+ users, enter a minimum value
of 4096 MB
5. Click OK.
6. Open the <Tomcat_home>\conf\logging.properties file in an editor.
7. In the line starting with .handlers = ..., remove the entry java.
util.logging.ConsoleHandler and save the file.
3.3 Configuring the Tomcat user

Admin rights The user running Tomcat must be a member of the local Administrators group.
During the installation of Archive Center, Tomcat must be allowed to write to the C:
\ProgramData folder.
To add the Tomcat user to the local Administrators group:
1. Log on as a user with administrative rights and run lusrmgr.msc.

2. In the console tree, select Groups, and then open the Properties of the
Administrators group.
3. Click Add, browse for the Tomcat user, and then click OK twice.
Tomcat user You must run Tomcat with a user. Do not use the local system account.
To set the user for Tomcat:
1. Start the Monitor Tomcat tool (tomcat8w.exe).

2. Click the Log On tab and select This account.
3. Enter the name and password of the user to run the Tomcat service.
3.4 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. Automatically redirect clients that access a page with a security constraint
requiring SSL/TLS.
Important
• You must configure connectors with the same ports as used by Archive
Server 10.5. Otherwise, the Archive Center Installer will fail. By default,
the ports are 8080 for HTTP and 8090 for HTTPS.
• When enabling SSL/TLS, OpenText recommends using a server certificate
from a Certificate Authority. The root certificate must be trusted by the
18 Center 16
AR160000-00-DWO-EN-2
3.4. Configuring and securing Tomcat
JRE or JDK and correctly installed in the keystore (for example,

<JRE_HOME>\lib\security\cacerts or <JDK_HOME>\jdk8\jre\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 folder, 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"
maxThreads="150"
minSpareThreads="25"
Center 16 19
AR160000-00-DWO-EN-2
Chapter 3 Setting up Apache Tomcat 8
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
• protocol must be set to HTTP/1.1 (default).
You must not use protocol="org.apache.coyote.
http11.Http11AprProtocol".
• disableUploadTimeout must be set to true (default).
enableLookups must be set to false (default).
• 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).
20 Center 16
AR160000-00-DWO-EN-2
Chapter 4
Upgrading Archive Server 10.5.0 SP1 to Archive
Center 16
If you have fulfilled all prerequisites, you can start with the upgrade installation.
4.1 Running the Archive Center Installer

The Archive Center Installer can perform an in-place upgrade of Archive Server
10.5.0 SP1 to Archive Center 16.
The following components will be upgraded if present or installed if not yet
available:
• Archive Server
• Archive Monitoring Server
• Administration Client
• Document Pipeline Base
Important
If there are other Document Pipelines installed, do no upgrade them
before you have upgraded Document Pipeline Base using the Archive
Center Installer. If you upgrade Document Pipeline Base using another
master setup, you cannot use Archive Center Installer anymore to
upgrade to Archive Center.
• Document Pipeline Info
• New features of Archive Center 16:
• File Share
• Email Capture (previously called “Email Archiving”)
• Document Pipeline for Archive Center CMIS
The following components will not be upgraded:

• Directory Services
Directory Services will be installed if not available. For more information, see
“Preparing OpenText Directory Services” on page 10.
Important
• If Archive Server uses a local installation of Directory Services 10.5, you
must first upgrade Directory Services to version 16. For more
information, see “Migrating a local Directory Services to version 16”
on page 12.
Center 16 21
AR160000-00-DWO-EN-2
Chapter 4 Upgrading Archive Server 10.5.0 SP1 to Archive Center 16
• 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.
• Solution Registry Agent
To upgrade Archive Server:
1. Download the Archive Center Installer 16.exe file from the OpenText
Knowledge Center (https://knowledge.opentext.com/knowledge/llisapi.dll/
Open/52699338).
2. Run the ArchiveCenterInstaller16.exe file as a user with local

administration rights.
3. Accept the License Agreement and on the Prerequisites page, verify that no
errors have occurred.
4. On the Application Server page, enter the password of the user running the
Apache Tomcat service.
5. On the Directory Services page, enter the name and password of the Directory
Services administrator (default name: otadmin@otds.admin).
6. Verify the default installation and configuration paths. If required, adapt them
to your needs.
Click Install to start the upgrade process.
Note: You can find detailed logging information in %TEMP%\opentext and

%ECM_LOG_DIR%.
4.2 Actions after the upgrade

4.2.1 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/llisapi.dll/Open/63027605).
2. Install the latest Update according to the documentation. For more information,
see OpenText Archive Center and OpenText Enterprise Library - Update Installation
Guide (Windows) (AR-DWS).
22 Center 16
AR160000-00-DWO-EN-2
4.2. Actions after the upgrade
4.2.2 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 “Including/excluding groups from

organizational units” in OpenText Directory Services - Installation and Administration
Guide (OTDS-IWC).
4.2.3 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.
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).
Center 16 23
AR160000-00-DWO-EN-2
Chapter 5
Upgrading Archive Cache Server 10.5.0 SP1 to
version 16
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 17.
5.2 Running the setup

To upgrade Archive Cache Server:
1. Start the setup of Archive Cache Server.
2. Log on to the server as a user with administrator rights.
Remote setup
If you want to run the installer using Microsoft Remote Desktop
(Terminal Service Client), you must use the /admin option when
establishing the remote session.
3. Run archive_cache_server_16.0.0.msi.
4. Read the License Agreement. To accept it, select the I accept the terms in the
License Agreement check box.
5. On the Apache Tomcat Parameters page, choose the Tomcat service to be used.
6. On the Ports Web Application Server page, enter the HTTP and HTTP/SSL
ports of Tomcat.
These ports must be configured in the server.xml configuration file of Tomcat.
For more information, see “Configuring and securing Tomcat” on page 18.
7. On the Archive Host page, enter the name of the computer on which Archive
Server resides.
Center 16 25
AR160000-00-DWO-EN-2
Chapter 5 Upgrading Archive Cache Server 10.5.0 SP1 to version 16
In the HTTP Port of the Archive Server field, enter the HTTP port that Archive
Server uses; default: 8080.
In the HTTPS/SSL Port of the Archive Server field, enter the HTTPS port that
Archive Server uses; default: 8090.
8. Click Install to start the installation.
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).
26 Center 16
AR160000-00-DWO-EN-2
Chapter 6
Upgrading OpenText Document Pipelines 10.5.0
SP1
The Archive Center Installer also upgrades the Document Pipelines required for the
“extended functionality” of Archive Center (Application Layer and web apps):
Document Pipeline Base, File Share, and Document Pipeline Info.
Important
If there are other Document Pipelines installed, do no upgrade them before
you have upgraded Document Pipeline Base using the Archive Center
Installer. If you upgrade Document Pipeline Base using another master
setup, you cannot use Archive Center Installer anymore to upgrade to
Archive Center.
For more information about the upgrade of other Document Pipelines, see OpenText
Document Pipeline - Installation and Upgrade Guide (AR-IDPDP).
Configuring protocol and port

The Archive Center Installer sets the protocol and port of the CMIS connection to the
default values (HTTP and 8080, respectively). If you want to use TLS/SSL for the
CMIS connection, you have to edit the corresponding configuration variables.
To configure protocol and port of the CMIS connection for TLS/SSL:
1. Start Administration Client and sign in to Archive Center.
2. Expand the Archive Server> Configuration node and select Document

Pipeline> Specific settings for FSA Document Pipelines.
3. Open the properties of the Archive / CMIS server: communication protocol

variable (internal name: DP.FSA.CMIS_PROTOCOL)and select HTTPS.
4. Open the properties of the Archive / CMIS Server: communication port

variable (internal name: DP.FSA.CMIS_PORT) and set its value to the HTTPS
port (default: 8090).
5. Restart the Apache Tomcat and Archive Spawner services.
Center 16 27
AR160000-00-DWO-EN-2
Chapter 7
Testing the upgrade
7.1 Testing the running processes

After the upgrade, test if all required processes are running.
To test for required processes:
1. In a command window, type spawncmd status and confirm with RETURN to

check the Archive Spawner status.
2. Check whether the processes chkw, db, dsstockist, and stockist are
terminated (T), as they run only in certain intervals.
All other processes must be running (R). Otherwise, check the corresponding
log file in the <OT install>\var\log folder or contact OpenText Global
Technical Services.
For Document Pipelines: Doctools not in use by any pipeline configuration can
also be terminated (for example, Chkpout, timestampdt).
7.2 Testing the complete archive functionality

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, have a look at the corresponding troubleshooting folder in the

Knowledge Center (https://knowledge.opentext.com) or contact OpenText Global
Technical Services.
Center 16 29
AR160000-00-DWO-EN-2
Chapter 7 Testing the upgrade
7.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.
30 Center 16
AR160000-00-DWO-EN-2

OpenText Archive Center On Windows 16.0 - Upgrading Archive Server 10.5.0 SP1 To Archive Center 16 English (AR160000-00-DWO-En-2)

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 Windows 16.0 - Upgrading Archive Server 10.5.0 SP1 To Archive Center 16 English (AR160000-00-DWO-En-2)

Uploaded by

Copyright:

Available Formats

OpenText™ Archive Center on Windows®

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

3 Setting up Apache Tomcat 8 .................................................. 17

4 Upgrading Archive Server 10.5.0 SP1 to Archive Center

5 Upgrading Archive Cache Server 10.5.0 SP1 to version

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

7 Testing the upgrade ................................................................ 29

Preparing the upgrade

2.1 General preparations

Checking MY_HOST_NAME variable

To set the MY_HOST_NAME variable:

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

Checking disk space

• 250 MB on the system disk

Informing users about downtime

Stopping the traffic on Archive Server

To stop traffic on Archive Server:

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

Backing up job protocols

Disabling disk cache of hard disk

To disable disk caching:

2. Clear the Enable write caching on the device check box.

3. Close all the applications opened before, such as Computer Management.

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 folder

2. In the <OT config>\Directory Services 10.5.0\opendj\bat folder, run

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

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.

3. Perform the following command in the folder which contains

4. Start the pre-upgrade check script:

The data and index tablespace names are displayed.

2.5 Prerequisites for Microsoft SQL Server

Precondition for Archive Center with remote SQL Server

Running the check script on SQL Server

To check the schema:

sqlcmd -U <user> -P <passwd> -d <database> -S <DBserver> -i

sqlcmd -U ecr -P <passwd> -d ECR -S <DBserver> -i

sqlcmd -U ixds -P <passwd> -d DS -S <DBserver> -i