Archive Center Release Notes 21.2
Archive Center Release Notes 21.2
Archive Center Release Notes 21.2
Release Notes
21.2
Contents ................................................................................................................................................ 3
1 Introduction .................................................................................................................................... 5
1.1 Release Notes revision history .................................................................................................. 5
Starting with version 16 there is only one delivery for OpenText Archive Center and Archive Server.
OpenText Archive Center consists of the known Archive Server plus the OpenText Archive Center
application layer.
Note: Customers using OpenText product bundles including the Archive Server can use the Archive
Server functionality provided by OpenText Archive Center assuming the scenario is licensed. Solution
Registry Agent for use is available as separate download from OpenText My Support.
Note: A separate license is required for usage of CMIS Interface, File Share Archiving and Archive
Center Web Application.
Archive Monitoring Server Monitoring for OpenText Archive Center and Document Pipeline
deployments
Directory Services Manages user and group identity information for OpenText
components
also available as independent download from OpenText My Support.
Note: OTDS is a prerequisite to install Archive Center. OTDS 22.2 is
tested with Archive Center 22.3
Note
Documentation that is installed with the product or packaged with the
product download is current at the time of release. Documentation
updates made after a release are available for download on OpenText
My Support (https://support.opentext.com).
If no service pack, maintenance level, patch level or similar is explicitly mentioned for a specific
software version, OpenText supports all deliverables for this version that are released by the
manufacturer, unless explicitly stated otherwise. If details of a specific service pack, patch and
maintenance level etc. is given, then this one and all subsequent ones are supported.
11
RedHat RHEL x86-64 19c - - 12 2.0 SPS 04
8.x (8.3)6 Google Cloud 2.0 SPS 05
SQL
( PostGreSQL
11, 12)
AWS RDS
(PostgreSQL
11, 12)
-
Oracle Linux x86-64 12c Release 2 - - 11
7.x6 19c 12
1 Instruction set
2 Supported editions: Standard and Enterprise Edition; 64-bit all
3 Oracle 19c: Version 19.3.0 or later (19.x) is supported
4 Oracle 12c Release 2: Bundle Patch 12.2.0.1.190416 or later
5 Only SQL databases and SQL virtual machines are supported
6 All minor versions of an OS major version are supported, the minor version in bracket was tested
12c Release 2 -
IBM AIX 7.1 Power 8 - - -
19c
• Operating system for database installed on a remote system is not relevant for OpenText Archive
Center.
• "7100-04-01-1543" should be the minimum OS level patching required on AIX to make AC 21.2
doc tools work properly
Notes
If Open JDK 11 is being used to install Archive Center 21.2 then
JAVA_HOME path needs to be set in System Environment
Variable
Instead, you can start using the HSR feature by configuring the database connection and doing a
manual switch.
• In case of a failure of the primary database, reconfigure the OpenText Archive Center connection
to the secondary database.
As it is a synchronized copy, the secondary database has the same status as the primary (before
failure).
Opentext Archive Center Supports the following variant(s) of Always On for MS SQL 2019
Note
Use of OpenJDK 11 requires Apache Tomcat 8.5.23 or later
versions
Note
Download Location: https://support.microsoft.com/en-us/topic/the-
latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-
95f26a218cc0
As OpenText may not be fully aware of all aspect of public cloud administration needs, customers are
expected to provide specific public cloud expertise to navigate such administration and configuration
responsibilities. If an issue is encountered relating to the normal operation of an OpenText product
whilst running within a virtualized environment, OpenText Customer Support is only obligated to
attempt to reproduce the issue on the same base operating system. If the issue cannot be reproduced
on the same base operating system, OpenText Customer Support will request that the issue be
referred to the vendor of the virtualization software for further investigation.
For questions about installation, sizing, storage, backup, monitoring, integration into the on-premises
network, contact OpenText Professional Services.
The Microsoft Azure cloud platform offers Microsoft Azure Virtual Machine services that offer an
Infrastructure as a Service (IaaS) platform. OpenText Archive Center supports Azure Virtual Machines
(IaaS) as well as Microsoft Kubernetes Services (AKS) for containerized deployments.
The IaaS platform allows deploying various scenarios, including hybrid deployments with connections
to the on-premises customer network.
The Amazon Web Services cloud platform offers Virtual Machine services that offer an Infrastructure
as a Service (IaaS) platform. OpenText Archive Center supports Amazon’s Virtual Machines (which
includes support for the Amazon hypervisor, AWS Nitro) as well as the Amazon Elastic Kubernetes
Service (EKS) for containerized deployments.
The IaaS platform allows deploying various scenarios, including hybrid deployments with connections
to the on-premises customer network.
The Google Cloud Platform offers Virtual Machine services that offer an Infrastructure as a Service
(IaaS) platform. OpenText Archive Center supports GCP’s Virtual Machines as well as the Google
Kubernetes Engine (GKE) for containerized deployments.
The IaaS platform allows deploying various scenarios, including hybrid deployments with connections
to the on-premises customer network.
• SAP HANA DB
Note
gzip request content encoding (http setting: compression) is not supported with ILM
• Chrome
• Firefox
• Safari
• Microsoft Edge
To achieve high availability with OpenText Archive Center (including Application Layer), there are
several options possible: Virtualization, for example VMware HA (high availability), active-passive
cluster or active-active cluster. Contact OpenText Professional Services to find the optimal approach
for your requirements.
• All nodes must run on the same operating system (OS) and OS major version
• A cluster must not be deployed in a WAN. Cluster requires low network latency
• HDSK pool and SAN storage as storage platform, except for disk buffers, are not supported
• Container storage (ISO) is not supported
• AFP feature
Note
Care has to be taken when using an active-active cluster and virtualization
technologies. Virtualization features can influence the timing behavior.
Any influence that results in a delay of the network communication must
be avoided on an Archive Center node while it is actively used in a cluster.
For more information about active-active cluster related topics, see the Cluster Installation Guide. The
marker Cluster topic is used in the Administration Guide to indicate deviations of an active-active
cluster installation.
Only the MMC mode “User mode – limited access, single window” is supported. This mode is pre-
selected by the installation.
Note: Remote Standby scenarios are not supported for archives that are used within Enterprise
Library Services, that is archives that are used to host records and are referenced within Content
Server.
Note: OpenText Archive Center only evaluates «allow» ACLs (access control lists) on the file share,
«deny» permissions are ignored.
This means: «allow» permission for everyone, and «deny» permission for a dedicated user is not
supported.
To support the configuration mentioned above, configure the «allow» permission for every single user
explicitly.
The migrate call must not be used, if the source and the target pool share the same disk
buffer. (Ref: AS-17377)
Hash algorithms supported by OpenText Archive Center: RIPEMD-160, SHA-256, SHA-512. You can
only use hash algorithms that are also supported by the timestamp provider.
exceet http://www.exceet-secure- x
solutions.de/en/
Quovadis http://www.quovadisglobal.ch/ x
Notes:
• exceet, Quovadis time stamp server are for use with Archisig only.
• exceet time stamp server is not released for use on IBM AIX.
• TS_HASHALG2 must be empty for exceet time stamp server.
• exceet time stamp server cannot be monitored through Monitor Server.
• In regards to internal used Timestamp certificates please check the KB article
https://knowledge.opentext.com/knowledge/cs.dll/kcs/kbarticle/view/KB15227934
The current configuration of the Microsoft SQL Server does not allow to recycle job numbers.
To check your current job number in use, run the following SQL statement:
All computers (servers, clients and storage systems) must use a central time server. Times returned
by OpenText Archive Center are in UTC (coordinated universal time).
IPv6 addresses in place of host names are not supported. It must be ensured that host names are
resolved to IPv6 addresses.
The component name is treated as binary data. The length is limited to 255 characters (170
characters for Oracle or SAP Hana DB). Unicode characters are supported.
Some characters are not permitted as part of component names for documents in OpenText Archive
Center. For more information, see the Knowledge Base entry “Forbidden characters for filenames” at
https://knowledge.opentext.com/go/62988621. Trailing blanks are not allowed for component names.
4.12.1.6 Retention
• ArchiveLink scenarios
• ECMPush
• AFP files
Adding new configuration variables in the Administration Client under OpenText Archive Center >
Configuration is not supported.
4.12.1.8 ArchiSig
Command line tools require loading the Archive Server environment first.
Under Windows, open a command line window, and then run <OT install AS>\bin\profile.bat.
You can specify datetime properties with custom date formats in the CMIS pipeline.
Monitoring tools are expected to be transparent for the OpenText Archive Center software. For
customers who have a support agreement, OpenText will use reasonable efforts to investigate
potential issues with OpenText software running with 3rd party monitoring tools. As part of that
investigation, OpenText may require that the issue be reproduced independently from the monitoring
products. Where issues are confirmed to be unrelated to the monitoring software, OpenText will
support its software in a manner that is consistent with support provided when that software is not
running in such an environment.
Also, at no time antivirus software must kill any of the processes belonging to a running archive server
(see “spawncmd status”). If this happens, contact your antivirus software vendor to get updated virus
signature files so the OpenText processes are not terminated by the antivirus software.
4.12.4 Multi-tenancy
Multi-tenant deployment on premises is not supported.
This does not apply to quotas imposed by the storage system itself. Storage systems with quotas
must behave like a normal disk partition.
Maximum number of volumes per single file device type (VI): 256
4.12.9 Migration via Document Import (dstools – volck) can lead to data loss
In the past, Archive Center migrations to new versions or new environments have been performed via
document import (dstools- volck) from storage systems. Migration via Document Import is no longer
supported as this method can lead to data loss. For more information, see the
https://support.opentext.com/kb?id=kb_article_view&sysparm_article=KB0811105.
Component Languages
EN DE JA FR IT ZH ES RU
Note
Deinstallation of older Archive Center components is not supported post
upgrade to AC 21.2.
Tomcat and Java versions of all products, including OT and third party
products, used with Archive Center should conform to the versions
recommended in section 4.1.6
If 100 kB documents must be ingested within 10 hours onto a NAS/CAS storage system, the
environment recommended above can be able to ingest 1 million documents per day (10 hours). Note
that the numbers can vary depending on document types, compression rates, encryption, or other
parameters.
7 Fixed issues
This section provides information about past issues that have been fixed in this release.
AS-18703 Wrong log parameters documented in GS *.setup files of archive center 16.2.2
AS-19314 BUG - issue with Oracle 19c FailOver after Archive Center 16.2.3 update
8 Known issues
The following known issues exist in this release.
AC 1781 AutoDelete does not delete CMIS folder for AFP documents.
AC 704 Archiving for Content Sever and Volume Migration cannot use Write-Thru
Pools as target.
AS 17377 The migrate call must not be used, if the source and the target pool share the
same disk buffer.
AS 17333 AutoDelete job does not work for single instance archiving (SIA).
AS 16314 Remote standby not supported for collections with retention option “Propagate
to storage”=Off.
AS 16307 Document option to allow changes by privileged users is not set by dsTools
import.
AS 15981 Cluster: Copy/Move to different pool is not released using Archive Link migrate
call.
AS 15761 Cluster: Import and export of buffer volumes is not supported for Cluster
deployments.
AS 15759 Import and export of buffer volumes is not supported for Cluster deployments.
AS 15595 Calling dshdsk with a missing volume will result in success. Nevertheless,
errors are logged.
AS 14465 Import and export of buffer volumes is not supported for Cluster deployments.
AS 13881 If encryption on the fly is set then compression on the fly must be set (if the
documents should be compressed as well).
AS 7814 After deleting a shadow pool, the application server must be restarted.
AS 7684 Delayed archiving should not be used for Archives with shadow pool.
AS 17678 dsTools and volck are able to import more data as expected if EMC Buckets
have the same PEA File. Create for each needed volume a separate Bucket
and also dedicated PEA File to solve this issue.
AS 17669 dsPurgeVol does not delete ISOs from EMC ECS even that the output is OK,
but in the log there is the error "Wrong parameter detected" mentioned. The
ISO needs to be deleted manually afterwards.
AS 18054 dsGs hangs when copying docs to different volume on same storage with 5
threads for S3/HCP/Azure. To avoid the issue make sure than number of
threads for dsGs is smaller than number of sessions.
AS 17463 Move of document by migrate to different archive or storage tier ignored if still
in diskbuffer.
AS 17377 Move of document by migrate to different storage tier ignored if both pools
share same diskbuffer.
AS 17312 With the new ability to use an S3 connection for multiple volumes, it's possible
to also create a volume referencing the actual base directory. While this
operation succeeds, the volume's root directory then includes the root directory
of any volume using the same connection with a top-level folder. This leads to
errors.
AC 3041 Cluster: utility "Reassign work to other node" can break the remaining node if
archisig is used.
AS 18256 Dinfo - different results on Windows and Unix for retention dates beyond year
3000.
AS 18998 iso9660.log and backup_proto log files are written in <tomcat> directory not into
ECM_LOG_DIR
AS 19707 AS 16.2 not able to update component when version is > 1000
AS 20222 OTCS Ticket 4656699 - document pipelines fail to send to Notification Server
through SSL
AS 23023 Free storage calculation for AWS S3/Nutanix S3: Volume size limit for Archive
Server is 8 TB
AS 20615 DocId with ‘AFP’ in the ID string is not allowed outside of the AFP scenario.
The docId with ‘AFP’ in the ID string looks like an AFP docId, which is
applicable just to correct AFP documents i.e., MDF (multi-document files), but
fails for usual documents.
AC 4230 CMIS: Upload of files that are larger than 2 GiB is not supported if the
content length is not set.
AC 1158 Web applications Access and MyArchive: export fails if documents with the
same filename exist.
AC 704 Archiving for Content Sever and Volume Migration cannot use Write-Thru
Pools as target.
AS 17387 CMIS: Selecting of a specific version including the latest version is not
supported
AC 667 ECMPush cannot be used for documents within CMIS directories with
starting blank.
AC 664 Documents ingested via the file share data source cannot be propagated to
Content Server.
AC 3043 CMIS Date filters are not working in case of internal field mappings of type
date/datetime.
The xpwd feature used for authentication of CMIS request on proxy does not
work if call is not submitted by localhost.
AS 16607 Date time search not supported for CMIS custom types.
AS 15969 MS SQL: Tagging is not possible with double byte characters in tag name.
AS 17387 If the latest version of a document is deleted, the document is still query-able
when doing a "Search all versions" but not when doing a "Search only recent
versions".
Note: Deleting a specific version or the latest version is only possible using a
dedicated client (CMIS Workbench or any other custom written client,
accessing the CMIS Api).
AS 20261 AC 20.2 - Internal Error when exporting/downloading bulk documents more than
1000 documents from CMIS UI
AS 13319 Different (mixed) settings IPv4/IPv6 for Archive Cache Server and client
using the Archive Cache Server is not supported.
AS 15370 Changing subnet address of one of the subnet definitions of a Cache Server
will reset the Cache Server mode to "Write Through".
AS 18633 List and refresh some ADMC objects failed when changing the one node to
another node in SQL 2017 Always on feature
AS 19783 OTCS Ticket 4641954 - ADMC Call of the Export to Cloud job logs passwords in
clear text in the logfiles
30