OpenText Content Server

Release Notes
20.2

Product Released: March 2020

Release Notes Revised: May 2020

Contents
1 Introduction .................................................................................................................................... 4

2 About OpenText Content Server .................................................................................................. 4

2.1 About Release Numbers ........................................................................................................... 5
2.2 Changes – 20.2 ......................................................................................................................... 6
Administration ............................................................................................................... 6
Document Management: .............................................................................................. 8
Smart View ................................................................................................................... 8
Connected Workspaces ............................................................................................... 9
Classifications ............................................................................................................. 10
Records Management ................................................................................................ 10
Records Management WebReports 1.8 for Content Server 20.2 .............................. 10
Content Sharing with OpenText Core Share .............................................................. 10
Classic View ............................................................................................................... 11
eLink and Notifications ............................................................................................... 11
REST API.................................................................................................................... 11
Workflows ................................................................................................................... 12
DocuSign .................................................................................................................... 12
Content Suite Platform Add-On for Microsoft Office Online Server ............................ 13
Content Suite Platform Add-On for Microsoft Office Online ....................................... 13

3 Discontinued and deprecated features...................................................................................... 13

4 Packaging and documentation ................................................................................................... 14

4.1 Related documentation ............................................................................................................ 15
4.2 US Export Compliance ............................................................................................................ 15

5 Supported environments and compatibility .............................................................................. 15

5.1 Platform Compatibility .............................................................................................................. 16
5.2 Mobile Platform Matrix ............................................................................................................. 16
5.3 Enterprise Connect and Office Editor Features Support ......................................................... 16
5.4 Client Platform Support ........................................................................................................... 18
5.5 Application Server Support ...................................................................................................... 19
5.6 Content Server Java Support .................................................................................................. 19
5.7 Web Server Support ................................................................................................................ 20
Web Server Support Notes ......................................................................................... 21
5.8 Server Platform Support Matrix ............................................................................................... 22

OpenText Content Server 20.2 Release Notes

2
 Database Support Notes ............................................................................................ 24
5.9 Virtualization Support .............................................................................................................. 26
5.10 Microsoft Office Integration Support ........................................................................................ 26
5.11 Microsoft Office File Format Support ....................................................................................... 27
5.12 Document Filters Format Support ........................................................................................... 28
5.13 OpenText product compatibility ............................................................................................... 29
5.14 OpenText product compatibility ............................................................................................... 29
5.15 Language support .................................................................................................................... 30

6 Installation and upgrade notes ................................................................................................... 31

6.1 Installation notes ...................................................................................................................... 31
6.2 Installation Note: OpenText Directory Services ....................................................................... 31
6.3 Installation Note: Search file systems ..................................................................................... 31
6.4 Installation Note: Records Management, Physical Objects, Security Clearance
modules ................................................................................................................................... 32
Installation Note: Records Management WebReports 1.8 ......................................... 32
6.5 Upgrade Notes for the OpenText Email Services Module ....................................................... 32
6.6 Installation Note: Performance Improvement When Applying 16.2.4 to an Oracle
Database ................................................................................................................................. 32
6.7 My Support Review ................................................................................................................. 33
6.8 Upgrade Note: Java – OpenJDK 11.0.1 .................................................................................. 33
6.9 Installation Note: Kubernetes .................................................................................................. 34
6.10 Install Critical Patches ............................................................................................................. 34
Configuration File Changes ........................................................................................ 35

7 New features and Fixes ............................................................................................................... 40

8 Known issues ............................................................................................................................... 40

9 Contact information ..................................................................................................................... 43

OpenText Content Server 20.2 Release Notes

3
1 Introduction
These Release Notes provide an overview of OpenText Content Server 20.2, including new features,
delivery information, and supported platforms. OpenText recommends that you read these Release
Notes in conjunction with the documentation included with the software package. If any conflicts exist,
the Release Notes supersede the other documentation.

We also recommend that you check OpenText My Support (https://support.opentext.com) for any
patches or documentation updates that may have been posted after the initial release of this product.

2 About OpenText Content Server

This section provides an overview of OpenText Content Server 20.2.

OpenText Content Server forms the document management cornerstone of the OpenText Content
Suite and provides secure, enterprise-wide control over any type of content - from contracts to
engineering drawings, system reports, email messages, images rich media and much more.

OpenText Content Server is designed with user productivity in mind, offering a simple, responsive
UI, with role-based views to enterprise, project-oriented, and personal workspaces. Users access
the information they need fast, with powerful content navigation through full text and metadata
search filters.

Social interaction is directly in-line with content to improve collaboration and enrich search
through activity feeds, in-line commenting, and user profile management.

OpenText Content Server features fundamental tools such as workflow, offline editing, version
control, taxonomy, multilingual metadata categorization, and reporting, and is easily customized
and extended with REST API and a Widget Framework that can be use d to expose Content
Server.

OpenText Content Server is the central content management foundation for the OpenText Content
Suite Platform, as well as a broad range of OpenText products including the OpenText™ Extended
ECM for Microsoft® SharePoint®, OpenText Extended ECM for SAP® Solutions, OpenText Extended
ECM for Oracle® E-Business Suite, OpenText™ Extended ECM for Salesforce®, and other
OpenText offerings.

OpenText Content Server 20.2 Release Notes

4
2.1 About Release Numbers
OpenText issues cumulative updates to Content Server on a quarterly basis. These updates
incorporate new features, security fixes and enhancements, performance optimizations and defect
corrections. The marketing release of Content Suite Platform Cloud Edition is generally about 1
month after Content Server is available. Content Server 20.2 is the cumulative update following
16.2.11 – there is no 16.2.12. Note that Content Suite Platform may be comprised of products with
various version numbers.

Scheduled Content
16.0 16.2+
Date Suite
2016 March 16.0 16
2016 June 16.0.1 16
2016 September 16.0.2 16
2016 December 16.0.3 16
2017 March 16.0.4 16.2.0 16 EP2
2017 June 16.0.5 16.2.1 16 EP2
2017 September 16.0.6 16.2.2 16 EP2
2017 December 16.0.7 16.2.3 16 EP2
2018 March 16.0.8 16.2.4 16 EP4
2018 June 16.0.9 16.2.5 16 EP4
2018 September 16.0.10 16.2.6 16 EP5
2018 December 16.0.11 16.2.7 16 EP5
2019 March 16.0.12 16.2.8 16 EP6
2019 June 16.0.13 16.2.9 16 EP6
2019 September 16.0.14 16.2.10 16 EP7
2019 December 16.0.15 16.2.11 16 EP7
2020 March 16.0.16 20.2 CE 20.2

OpenText Content Server 20.2 Release Notes

5
2.2 Changes – 20.2
Administration
Perspectives and Rules: A completely new Perspective and Rule storage and management
model has been introduced to improve performance, administrative control, and
transportability of Rules, Perspectives, and their underlying widget options.

• Perspectives and Rules are now their own SubType and can be controlled through
specific object privileges and individual permissions. These new objects are stored by
default in the Perspectives Volume and are directly editable. Rules are stored as a
child item of their parent Perspective.
• Perspectives and Rules are recyclable by default.
• Perspectives: Global usage privilege introduced to control creating and editing of
global Perspectives.
• New pages available to manage priority order of global Perspectives (through
administration pages) and local container Perspectives (through container Properties
pages).
• Systems with old ActiveView Perspectives will require conversion to the new model
through the Convert ActiveView Perspectives Administration page to take advantage
of new features. The most recent version of each Perspective will be used for
conversion and original permissions, location, and priority order will be retained.
Users/groups with ActiveView object creation privilege + Perspectives Tab usage
privilege will be automatically granted Perspective + Rule object privileges and
Perspectives: Global usage privilege. Perspectives making use of unsupported
features, as identified by the tool, will need to be modified prior to conversion. Refer
to the help pages for more information.
• Code Editor and Tag View as seen in the Perspective Manager have been removed.
• New Transport framework allows widget developers to clearly describe their
dependencies for use in Transport scenarios. The Transport Overview page has been
updated to better describe widget and rule dependencies.
• Perspective information is now available in System Report output.

NOTE: Perspectives containing widgets that now offer new Transport support (e.g.,
Connected Workspaces) must be re-saved in the Perspective Manager for Transport to
detect newly described dependencies.

Transport exact matching: A new experimental feature has been added to allow for precise
matching of node dependencies. Enabling the feature from the Core System – Server
Configuration > Features > Deprecated and Experimental Features administration page will
preserve node GUIDs during transport operations and will use the GUIDs to perform exact
matching. Once the feature is enabled, imported objects become unique and can only be
deployed to one location. The Transport Overview page will indicate exact matches (where
possible) and “fuzzy” (approximate) matches using Name + SubType where GUID matching
was not successful.

Transport Package drag and drop: Transport Packages can now be easily brought into a
destination system using drag and drop into the Transport Packages container of the
Transport Warehouse.

OpenText Content Server 20.2 Release Notes

6
 Transport custom mapping reversion: Custom dependency mappings can now be deleted
from the Transport Overview page for a given item. Deleting the custom mapping will revert to
automatic scanning (exact or fuzzy matching).

Large Document Partitions: Search Index Partitions can now be reserved for objects that
have large full text size, typically several MB. For customers that need all the text of very
large documents indexed, this feature allows a significant cost savings since only the
reserved partitions require additional memory.

Admin Server logging: Worker processes managed by the Admin Server may write output
to stderr and stdout, which is not captured. With this update, setting the Admin Server log
level to maximum (3) will result in these worker process logging messages being captured in
the Admin Server logs.

SOV Agent: The System Object Volume agent must only run on 1 instance at a time within a
cluster. With this update, the SOV Agent will not run if another SOV Agent is already active.
Each SOV Agent records execution information in the database and goes back to sleep if
another has run recently. If the active SOV Agent is removed from the system, another SOV
Agent (if configured to run) will begin executing within approximately 10 minutes.

Configuration Scripting: Additional administration pages have been converted to enable

export, import and scripting of configuration settings. The new integrated pages are: Manage
Tags and Subtags, Configure System for Security Clearance Levels and/or Supplemental
Marking, Enable and Configure Records Management.

Business Administration: On startup, Business Administration privileges are now checked

to verify if they are restricted, and if not, restriction is enforced.

Administration Security Parameters page: The About Page Requires Login field on the
Configure Server Parameters page in previous versions was set to false by default. The
setting is now true by default for enhanced security purposes.

Configure Server Parameters: As part of the security by default theme within

Content Server the Configure Server parameters - About Page Requires Login value
is now enabled. In previous versions of Content Server this value was disabled by
default.

The SameSite Attribute addition to the Admin Security page: Google released Chrome
80 which introduced a fundamental cookie behavioral change with the use of the SameSite
Attribute. The SameSite Attribute is intended to mitigate cross-site request forgery (CSRF).

A detailed description of the SameSite attribute can accessed at the following Chromium
Project link.

The SameSite attribute of a cookie specifies whether the cookie should be restricted to a first-
party or same-site context. There are three possible values: (by default Chrome 80 and above
is set to SameSite=Lax)

1. A cookie with SameSite=Strict will only be sent with a same-site request.

OpenText Content Server 20.2 Release Notes

7
 2. A cookie with SameSite=Lax will be sent with a same-site request, or a cross-site top-
level navigation with a "safe" HTTP method.
3. A cookie with SameSite=None will be sent with both same-site and cross-site
requests.

Content Server has accommodated the change made by Google in Chrome and potentially
with other browser vendors with the introduction, enablement and disablement of the
SameSite Attribute on the Configure Security Parameters page. Customers can now easily
set the SameSite cookie attribute to either Strict, Lax, or None where some solutions and
environments may require a non-default value. The SameSite Attribute value by default in
Content Server is disabled.

Hebrew language: New modern Hebrew language codes have been added to align with the
ISO-639-1 standard – Hebrew [he] and Hebrew (Israel) [he_IL].

Upload filtering re-label: The Version Blocked audit event has been re-labeled to Content
Blocked.

Document Management:
Renditions Server now supports the loading and publishing of MicroStation DGN and
AutoCAD DWG external references or XREF files in either PDF and PDF/A-1b or TIFF.

Smart View
Personalized Landing Pages: users can customize Landing Pages according to their
personal needs:

• Hide widgets: widgets that are not needed can be hidden.

• Widget order: the order of the widgets on the page can be changed (with drag &
drop).
• Shortcut groups: new shortcut groups can be created to provide quick access to
items frequently needed. Shortcut groups created by an administrator on the original
Landing Page can be hidden but they cannot be changed.

For each user an “Edit page” command is available in the user menu of the Smart View page
header. With “Edit page” the Landing Page is switched into edit mode and the user can
customize the page.

OpenText Content Server 20.2 Release Notes

8
 Note
A prerequisite for the personalization of Landing Pages is that one of the
following steps was done:

• The Smart View Landing Pages were migrated to the

new perspective management model, please see
Administration.
• The original Landing Page was edited at least once with
the “Edit page” command by a user who has the
permission to edit the Landing Page for everyone.

Advanced versioning: Major/minor versioning is now supported in Smart View:

• A version control setting was introduced that allows major/minor versioning for
folders and subfolders
• When major/minor versioning is enabled, documents that are uploaded to the folder
are added as minor versions.
• When a user adds a new version to a document, the user can decide if the new
version should be added as minor or major version.
• In the version history, minor versions can be promoted to a major version.

Note
In Smart View, major/minor versioning can be enabled on a folder level,
but not for individual documents.

Document default action: when you enable the “Enable Document Overview pages” option
in the Server configuration > Presentation > Configure Document Functions Administration
page, the Smart View Document Overview page opens when a user clicks on the name of a
document, for example in Browse View.

Progress bar enhancements: with long-running operations Smart View displays a progress
bar in the page header, which was enhanced in the following ways:

• Multiple document uploads: when a user starts a new document upload without
waiting for a previous upload to finish, the progress is updated with information about
the new document upload.
• Minimized the progress bar: a progress bar can be minimized to an icon that
displays progress. Clicking on the icon maximizes the progress bar again.

Nickname search: when a user does a search by using a nickname as a search term, the
result with the nickname is displayed as a promoted item on top of the search result list.

Connected Workspaces
Document Templates in Smart View: Creating documents based on a Document Template
can now be performed using a list and grid view selection in the recently introduced Smart
View side panel.

OpenText Content Server 20.2 Release Notes

9
 Transport of Smart View Workspace Perspectives: The new feature enables users to
transport Smart View Workspace perspectives including Connected Workspaces Widgets
(Team, Metadata) based on the new Workspace perspective node type. The action can be
performed via the Content Server Transport Warehouse.

Classifications
Smart View Classification Workspace: The Classifications Workspace is now available in
the Smart View. To access the Classifications Workspace is the Smart View, create a Favorite
or Shortcut widget to add to user Perspectives who require access to the workspace.
Standard Classification Trees and standard Classifications can be created and updated from
the Smart View Classifications Workspace.

Note
Creating RM Classifications and viewing classified objects from the new
Smart View Classification Workspace is planned for future.

Records Management
Multiple RM Classifications in Smart View: For multiple RM Classifications on an item,
add, remove, designating the primary RM Classification and applying changes to sub-items
from an item’s Properties page is now available in the Smart View provided multiple RM
Classifications are enabled.
RM Disposition and Accession Search Item Types: Any object type can now be selected
as the Container option when defining Disposition or Accession search criteria.
Reject RM Disposition Review Comments Required: When changing the review decision
for item(s) listed in the Disposition Review Search results, a new system setting is available to
make Comments required when Reject is selected as a review decision.
REST API: Updated an existing REST API for creating a Hold to return the new HoldID to
more efficiently facilitate follow-up processing.
Records Management WebReports 1.8: Records Management WebReports
(OTRMReports) are upgraded to 1.8 as noted in the installation notes.

Records Management WebReports 1.8 for Content Server 20.2

Any modifications to the Records Management WebReports (OTRMReports) shipped with
previous releases will not be maintained on upgrade. You may wish to copy the report you
have modified prior to upgrade.

Content Sharing with OpenText Core Share

Share Ownership: Set the Core Share Tenant Service User Account as the default owner of
content shared from Content Server.

Share Details: Display share details in the Smart View Properties page when users click on
the Share icon.

OpenText Content Server 20.2 Release Notes

10
 Core Share Operations: Synchronize content back to Content Server when Core Share
items are moved within folders.

Classic View
Drag and drop from Outlook: Email messages can now be dragged directly from Outlook
into the Classic View using Chrome or Edge browsers.

Preferred start page: Smart View and Favorites can now be selected as a preferred start
page. Administrators can choose these options as the default for all users on the Configure
Server Parameters Administration page.

eLink and Notifications

eLink Outbound inline images: Images included in a Discussion or Forum Post directly in
the body of the message will now be preserved in outbound subscription emails.

Increased default eLink Maximum Outbound Size: The default has been increased from
1024KB to 5120KB. Any inline images causing the overall message size to exceed this
setting will be replaced with placeholder text.

Enabling Notifications without email: Notifications can now be enabled without requiring
mail server settings to be populated.

REST API
Renditions: Support for listing, creating by upload, replacing by upload, retrieval, and
deletion of Renditions is now available. Endpoints are:
/api/v2/nodes/{node_id}/versions/renditions and
/api/v2/nodes/{node_id}/versions/{version_id}/renditions.

Languages: List of available display and metadata languages is accessible through

/api/v1/serverinfo. A user’s preferred display language can be modified through the
display_language property of a member.

Permissions pagination: ACL for a node can now be retrieved in paginated form through
/nodes/{id}/permissions or /nodes/{id}/nodes/permissions. The first three items of page #1 will
always be Owner, Owner Group, and Public Access. Page and Limit parameters control page
number and page size, respectively.

Additional Node Attributes form: Create and Update forms for nodes now include
information about Additional Node Attributes (a.k.a. System Attributes) under the role named
systemattributes.

Advanced Versioning enhancements:

• /api/v1/serverinfo includes flags for Advanced Versioning system configuration. The

advanced_versioning and enhanced_advanced_versioning flags indicate if

OpenText Content Server 20.2 Release Notes

11
 Advanced Versioning is in use and whether Enhanced Advanced Versioning is
enabled.
• Control whether newly added items are added to a given container with advanced
versioning (major/minor) using the versions_control_advanced flag for the
container node. The optional apply_to parameter applies a one-time change to the
specified item (0), subitem (1), or the specified item and subitems (2).
• Node action list now includes the ability to modify Version Control and Promote to
Major.

Additional business administration volume support: Volume retrieval for Facet Volume
(901) and Transport Warehouse (525) using /api/v2/volumes has been added. Permissions
support for Facet Folders (905) has been added.

HEAD requests: Calls returning content now support the HEAD method.
These include /api/v*/nodes/{node_id}/content/*,
/api/v*/nodes/{node_id}/versions/{version_id}/content/*,
/api/v1/nodes/{node_id}/thumbnails/{size}/content,
/api/v1/nodes/{node_id}/versions/{version_id}/thumbnails/{size}/content, and
/api/v2/nodes/{node_id}/versions/{version_id}/renditions/content.

Workflows
Transferring Category Attributes on initiation: On initiating a Workflow from an object,
Workflow Maps can now be configured to map Category Attributes with Workflow Attributes. If
configured, values from Category Attributes are automatically transferred to the Workflow
Instance and could be used there to automatically fill out Workflow Forms. This prevents
users from manually entering information into a Workflow Form, which might already be
available as Category information on the document.

“Display at initiation” for Smart View: The Start Step includes a setting to avoid displaying
itself during the initiation of the Workflow. This setting was only working in Classic View and
has been implemented for Smart View. This allows Workflow designers to skip showing any
interaction with the “Start Step” to users.

DocuSign
Added support for Anchor Tags: DocuSign Anchor tags offer a way to place keywords
within a document, which will then automatically be replaced with DocuSign tabs during the
transfer. Requesters will no longer be required to place signing fields by hand. The anchor
tags can easily be configured in the Content Server administration pages and do not require
any DocuSign configuration changes.

Real name requirement added: Due to compliance reasons with some regulations,
requesters are now required to give the full name of the signers and their email address.

Signing order definition: The DocuSign step now allows a requester to define a signing
order for signing users. This order can easily be changed using drag & drop within the
DocuSign step. This supports further automation of signing documents including DocuSign
anchor tags.

OpenText Content Server 20.2 Release Notes

12
 Progress tracking: The DocuSign Workflow Agent handling the transfer of documents and
checking the status of envelopes created on DocuSign side, can now be monitored within the
Workflow by all participants and the Workflow Tracking widget in Smart View. All status
messages produced by the agent are displayed in a newly added tab within these areas.

Content Suite Platform Add-On for Microsoft Office Online Server

The Content Suite Platform Add-On for Microsoft Office Online Server enables Content
Server users to do the following:

• Use Office Online applications, including Microsoft® Word Online, Microsoft® Excel
Online, and Microsoft® PowerPoint Online to edit and open documents directly in the
browser while connected to Content Server, without requiring Office to be installed on
the desktop.
• Co-author documents with other Content Server users. Multiple users can make
changes to the same document at the same time.

This optional add-on is for the integration between Content Server and the Office Online
Server. Microsoft Office Online Server is downloaded and installed on a customer’s premises
and is not to be confused with Office Online Service which is hosted by Microsoft. Integrating
with the Office Online Server requires downloading and installing the Office Online Broker
from OpenText.

Contact your OpenText representative for additional information on this add-on.

Content Suite Platform Add-On for Microsoft Office Online

The Content Suite Platform Add-On for Microsoft Office Online enables Content Server users
to do the following:

• Use Office Online applications, including Microsoft® Word Online, Microsoft® Excel
Online, and Microsoft® PowerPoint Online to edit and open documents directly in the
browser while connected to Content Server, without requiring Office to be installed on
the desktop.
• Co-author documents with other Content Server users. Multiple users can make
changes to the same document at the same time.

This optional add-on is for the integration between Content Server and the Office Online
Service. The Office Online Service is hosted by Microsoft. The Office Online Broker is
deployed in the OpenText cloud and maintained by OpenText.

Contact your OpenText representative for additional information on this add-on.

3 Discontinued and deprecated features

3.1 Discontinued Features
The following features are discontinued:

OpenText Content Server 20.2 Release Notes

13
 Caution

In Content Server 10.5 Update 2015-03, changes were made to the storage
format of OScript code that make up modules (OLL files). Backwards
compatibility for the old format was provided as a transition for solutions. As
of the June 2020 (20.3) update, the old format is no longer be supported. For
solutions that are not transitioned at that time, the solution vendor will need
to provide an update.

• Remote Search has been deprecated in release 20.2. The value of Remote Search has
diminished in favor of newer OpenText offerings such as InfoFusion, File Intelligence and
Federated Compliance. For now, Remote Search can be enabled on the Deprecated and
Experimental Features administration page to facilitate a transition to alternative technologies.

• ActiveView Wizard is discontinued in 20.2. Authoring of ActiveViews must be performed

through the ActiveView editor.

• REST API /api/v1/perspectives collection has been deprecated due to the new Perspective
and Rules model introduced in 20.2.

• Content Server 16.2.4 was the last Content Server version that supported WebDAV.
Enhanced functionality in Content Server, Enterprise Connect and Office Editor have been
added to replace much of the similar use cases supported by WebDAV. For more
information check this KB article KB11778113

3.2 Deprecated Features

The following features are deprecated. They are likely to be eliminated in a future update, and you
should consider implementing alternatives.

• Native authentication with Content Server using IWA (Integrated Windows Authentication) is
deprecated, and will be removed in a future update. All authentication should be gated by
OpenText Directory Services (OTDS), which offers authentication endpoints that support IWA.

• Support for Microsoft SQL Server 2012 and Microsoft SQL Server 2014 tentatively scheduled
to be dropped in the 21.1 update (Q1 2021).

4 Packaging and documentation

Downloads and documentation for OpenText Content Server are available on OpenText My Support
(https://support.opentext.com).

OpenText Content Server 20.2 Release Notes

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

ISO packages containing the entire Content Suite are no longer available. System Center is the
preferred method for downloading necessary software in traditional deployments, and containers are
an alternative path for cloud / Kubernetes deployment.

4.1 Related documentation

For additional information about OpenText Content Server, or for supplemental information about
related products, refer to the following documents, which are available on OpenText My Support
(https://support.opentext.com).

4.2 US Export Compliance

OpenText products are assessed for compliance with United States export control regulations. Per
ECCN guidelines, Content Server is self-classified as 5D002 ENC.

5 Supported environments and compatibility

This section provides details about supported platforms, systems, and versions.

OpenText Content Server 20.2 Release Notes

15
5.1 Platform Compatibility

Caution
Operating systems, databases, browsers and other platforms
advance on independent schedules. OpenText identifies the
version tested where applicable, and if a version is not identified,
testing is typically performed on the platform software available
approximately one month before the release date of Content
Server.

OpenText relies on the platform vendor to maintain backwards

compatibility. If the platform vendor makes a change that affects
compatibility, there may be period of time where the platform is not
fully functional while OpenText makes appropriate
changes. Depending on the severity of the changes, an update to
the latest or next quarterly update of Content Server may be
required.

Platforms that may be subject to these constraints are marked with a

† symbol.

5.2 Mobile Platform Matrix

Content Server functionality is supported on the following mobile platforms:

Device Mobile OS Mobile Browser Note

iPad or iPad Mini capable iOS, latest Safari, latest Only supported with Content
of running the latest iOS version version Server Smart View which is
version tested with the latest iOS
version. If you run into a
problem that exists only in a
previous iOS version please
upgrade to the latest version.

5.3 Enterprise Connect and Office Editor Features Support

These are Content Server features that require a specific version of Enterprise Connect or Office
Editor:

Feature Client Browser Support Notes

OpenText Content Server 20.2 Release Notes

16
 Enterprise Connect • Firefox ESR / Quantum Requires Enterprise Connect
From Here • Google Chrome 16.2.8 to be installed on the
• Microsoft Edge desktop
• IE11
• Microsoft Chromium Edge Requires Enterprise Connect
20.2 to be installed on the
desktop
Edit / Open using • Firefox ESR / Quantum Requires Office Editor 16.x.x to
Office Editor • Google Chrome be installed on the desktop
• Microsoft Edge
• IE11
• Microsoft Chromium Edge Requires Office Editor 20.2 to be
installed on the desktop

Print • Firefox ESR / Quantum Requires Enterprise Connect

• Google Chrome 16.2.8 to be installed on the
• Microsoft Edge desktop
• IE11
• Microsoft Chromium Edge Requires Enterprise Connect
20.2 to be installed on the
desktop

Send to mail as • Firefox ESR / Quantum Requires Enterprise Connect

attachment • Google Chrome 20.2 to be installed on the
• Microsoft Chromium Edge desktop
• Microsoft Edge

Send to my working • Firefox ESR / Quantum Requires Enterprise Connect

documents list • Google Chrome 20.2 to be installed on the
• Microsoft Chromium Edge desktop
• Microsoft Edge

OpenText Content Server 20.2 Release Notes

17
 Caution
If you install Enterprise Connect or Office Editor 20.2 client on a system
with the latest ESR or Quantum version of Firefox, the browser extension
for Firefox is not installed. To install the extension after the client is
installed, do the following:
1. In Firefox, click Open Menu , and then click Add-ons.
2. Click Tools for all add-ons , and then click Install add-on from File.
3. Navigate to one of the following locations:
• C:\Users\<username>\AppData\Local\Mozilla Firefox (for user
installations)
• C:\Program Files\Mozilla Firefox\browser\extensions (for 64-bit
system installations)
• C:\Program Files (x86)\Mozilla Firefox\browser\extensions (for
32-bit system installations)
4. Double-click [email protected].
5. In the Add Content Server Browser Web Extension? box, click Add.

5.4 Client Platform Support

Content Server functionality is supported on all browser/client OS combinations with the exceptions
specified in the Support Notes below. The table below does not cover the Enterprise Connect and
Office Editor Features. Please see 5.3 Enterprise Connect and Office Editor Features Support for
information on client platform support for Enterprise Connect/Office Editor.

Client OS Client Browser Support Notes

Windows IE 10 and older Not supported.

IE 11 Enterprise Mode

Windows IE 11

Windows Firefox ESR † • The Short Links section on the General

Firefox Quantum † properties page does not include options to
Firefox † Copy.
Chrome † • Chrome version 42 does not support Drag and
Drop. This issue is resolved with versions of
Chrome newer than version 42.
• Chrome version 80 includes changes to
Samesite cookie behavior. See Section 2.2.1 -
Administration for details on this change in
Chrome and Content Server 20.2.

OpenText Content Server 20.2 Release Notes

18
 Non- Firefox ESR † • The Short Links section on the General
Windows Firefox Quantum † properties page does not include options to
Safari Copy.
Chrome †
Firefox †

† See Section Supported environments and compatibility5 - Supported environments and

compatibility.

5.5 Application Server Support

The following chart describes the application servers/JAVA versions that are supported.

Supported Application JAVA supported on Notes

Server Application Server

Tomcat 8.5.x OpenJDK 11.0.5 Validated with Tomcat 8.5.51 and earlier.
Tomcat 9.0.x Validated with Tomcat 9.0.31 and earlier.

5.6 Content Server Java Support

The following chart describes the version of Java that is included in Content Server. OpenText
recommends that you use the associated Java and Content Server versions listed below:

OpenText Content Server 20.2 Release Notes

19
 Java Version Notes Content
Server

Java 8 Update 112 Java 8 Update 112 is included with the Content Server full 16.2.0
install.

Java 8 Update 121 Java 8 Update 121 is included with the Content Server full 16.2.1
install.

Java 8 Update 131 Java 8 Update 131 is included with the Content Server full 16.2.2
install.

Java 8 Update 144 Java 8 Update 144 is included with the Content Server full 16.2.3
install.

Java 8 Update 152 Java 8 Update 152 is included with the Content Server full 16.2.4
install.

Java 8 Update 162 Java 8 Update 162 is included with the Content Server full 16.2.5
install.

Java 8 Update 181 Java 8 Update 181 is included with the Content Server full 16.2.6
install.

Java 8 Update 192 Java 8 Update 192 is included with the Content Server full 16.2.7
install.

OpenJDK 11.0.1 OpenJDK 11.0.1 is included with the Content Server install 16.2.8
and upgrade packages.

OpenJDK 11.0.2 OpenJDK 11.0.2 is included with the Content Server install 16.2.9
and upgrade packages.

OpenJDK 11.0.3 OpenJDK 11.0.3 (version distributed by the AdoptOpenJDK 16.2.10

organization) is included with the Content Server install and
upgrade packages.

OpenJDK 11.0.5 OpenJDK 11.0.5 (version distributed by the AdoptOpenJDK 16.2.11

organization) is included with the Content Server install and
upgrade packages.

5.7 Web Server Support

The following chart describes the Web Servers that are supported.

OpenText Content Server 20.2 Release Notes

20
 Supported Web Server Version Notes

Tomcat 8.5.x Validated with Tomcat 8.5.51 and earlier.

9.0.x Validated with Tomcat 9.0.31 and earlier.
IIS 8.5, 10.0 IIS 10 supported on Windows 2016 as of 16.2.2

Apache HTTP Server 2.4.x Validated with 2.4.29 and earlier on Windows.

Oracle iPlanet 7.x

Web Server Support Notes

• HTTP/2 is not supported. Ensure you disable HTTP/2 in your web browser.

OpenText Content Server 20.2 Release Notes

21
5.8 Server Platform Support Matrix
The following chart describes the server OS and server database versions supported by Content
Server.

Note
Please review the specific support notes in the sections immediately
following this chart.

Content Server OS Database Note

Windows 2019 2 SQL Server 2019 SQL 2019 added

with 20.2.
SQL Server 2017
SQL 2017 added
Oracle 19c 19.x with 16.2.9.

Oracle 19.x
added with
16.2.10

Windows 2016 2 SQL Server 2016 Windows 2016

added with 16.2.2
SQL Server 2016 SP1
Oracle 12.2 and
SQL Server 2016 SP2 Azure SQL added
with 16.2.4
Azure SQL †
SQL Server 2016
Oracle 12c 12.2.0.1 SP2 added with
16.2.6
Oracle 19c 19.x
Hana 2.0 added
HANA 2.0 † with 16.2.8

Oracle 19c added

with 20.2

Windows 2012 R2 1 SQL Server 2016 SQL Server 2016

SP1 support
SQL Server 2016 SP1 added with 16.2.2

SQL Server 2016 SP2 SQL Server 2016

SP2 support
SQL Server 2014 added with 16.2.6
SQL Server 2014 SP1

SQL Server 2014 SP2

OpenText Content Server 20.2 Release Notes

22
 SQL Server 2014 SP3 Oracle 12.2
support added
Azure SQL † with 16.2.4

Oracle 11g R2 11.2.0.4 Hana 2.0 support

added with 16.2.7.
Oracle 12c 12.1.0.2
SQL Server 2014
Oracle 12c 12.2.0.1 SP3 support
added with 16.2.8
HANA 2.0 †

Red Hat 7.0 - 7.54 Oracle 11g R2 11.2.0.4 Linux 7.2 support
added with 16.2.1
Oracle 12c 12.1.0.2 Linux 7.3 support
added with 16.2.3
Oracle Linux 7.0 - 7.5 3,4 Oracle 12c 12.2.0.1
Linux 7.5 support
added with 16.2.6
Oracle 12.2
support added
with 16.2.4

Red Hat Linux 7.1 - 7.54 PostgreSQL 10.3+ Linux 7.2 support
added with 16.2.1.
Oracle Linux 7.1 - 7.5 3,4
Linux 7.3 support
added with 16.2.3
Linux 7.5 support
added with 16.2.6
PostgreSQL 10
support added
with 16.2.6

Red Hat Linux 7.1 – 7.54 HANA 2.0 † Hana 2.0 support
added with 16.2.7
Linux 7.6 support
added with 16.2.8

Red Hat Linux 7.6 Oracle 11g R2 11.2.0.4 Linux 7.6 support
added with 16.2.8
Oracle Linux 7.6 Oracle 12c 12.1.0.2 Oracle 19.x added
with 16.2.10
Oracle 12c 12.2.0.1
PostGreSQL 11.4
Oracle 19c 19.x added with
16.2.10
HANA 2.0 †

OpenText Content Server 20.2 Release Notes

23
 PostGreSQL 11.4

1
Windows 2012 R2 support includes Standard, Datacenter, and Hyper-V.
2
Windows 2016 support includes Standard and Datacenter.
3
Covers both UEK (Unbreakable Enterprise Kernel) and Red Hat compatible Kernel.
4
Linux is supported on x86_64 architecture.

† See Section Supported environments and compatibility5 - Supported environments and

compatibility.

Database Support Notes

5.8.1.1 General

Databases are supported on any Operating System platform supported by the database vendor. It is
not required that the database be on the same platform as Content Server. Databases which have a
client component must have that client supported on an Operating System platform supported by
Content Server.

5.8.1.2 Azure SQL

• Compatibility Mode. Due to the known issue CSARC-861 you must set the compatibility
level to SQL 2012 (110).
• Adding and Connecting to an Azure SQL DB. You must create the Content Server
database in Azure SQL and then use Content Server to create the tables. Please refer to the
Content Server Installation Guide for additional details.
• Database Maintenance. If your Content Server database is a SQL Server database
deployed on Microsoft Azure, you cannot use any of the tasks on the Microsoft SQL Server
Maintenance page. Use other tools (for example, SQL Server Management Studio) to
perform these tasks.

5.8.1.3 Microsoft SQL Server 2019

• SQL Server 2019 support includes Standard and Enterprise.

• Compatibility Mode. Due to the known issue CSARC-861 you must set the compatibility
level to SQL 2012 (110).

5.8.1.4 Microsoft SQL Server 2017

• SQL Server 2017 support includes Standard and Enterprise.

• Compatibility Mode. Due to the known issue CSARC-861 you must set the compatibility
level to SQL 2012 (110).

5.8.1.5 Microsoft SQL Server 2016

• SQL Server 2016 support includes Standard and Enterprise.

• Compatibility Mode. Due to the known issue CSARC-861 you must set the compatibility
level to SQL 2012 (110).

OpenText Content Server 20.2 Release Notes

24
 • SQL Server Always On. Content Server supports SQL Server 2016 Always On. Follow the
documentation from Microsoft to configure Always On -
https://social.technet.microsoft.com/wiki/contents/articles/36143.sql-server-2016-step-by-
step-creating-alwayson-availability-group.aspx .

5.8.1.6 Microsoft SQL Server 2014

• Performance. In Content Server, when you have a Content Server instance running on
Microsoft SQL Server 2014, performance degradation may occur. Please see our knowledge
base article Content Server - "“unable to add user (X) from group (X)- error saving Group”"
Message appears and performance degradation may occur in Content Server 10.5 running
SQL Server 2014
• SQL Server Always On. Content Server supports the SQL Server 2014 Always On solution
with the ODBC Driver 11 for SQL Server. Follow the documentation from Microsoft to
configure Always On - https://msdn.microsoft.com/en-CA/library/ff877884.aspx . The Content
Server system should connect to the availability group listener (virtual IP).
• Compatibility Mode. Due to the known issue CSARC-861 you must set the compatibility
level to SQL 2012 (110).
• SQL Server 2014 support includes Standard and Enterprise Editions.

5.8.1.7 Oracle 11g

• Oracle 11.2.0.4 is the recommended version of Oracle 11 with Content Server.

• Oracle support includes Standard, Enterprise and RAC as well as deployment on Oracle
Exadata Database Machine and Oracle SuperCluster.
• Content Server Oracle support includes Oracle client and Server interoperability support as
certified by Oracle where the minimum supported Database version for Content Server is
11.2.0.4.

5.8.1.8 Oracle 12c

• Oracle support includes Standard, Enterprise and RAC as well as deployment on Oracle
Exadata Database Machine, Oracle DataGuard, and Oracle SuperCluster.
• Oracle Multitenant. The Oracle Multitenant option for Oracle Database 12c allows a
multitenant container database to hold pluggable databases. To use the pluggable database
from Content Server you must reference the pluggable database in your TNSNAMES file, and
you must connect to the pluggable database from Content Server.
• Content Server Oracle support includes Oracle client and Server interoperability support as
certified by Oracle where the minimum supported Database version for Content Server is
11.2.0.4.

5.8.1.9 Oracle 19c

• Oracle support includes Standard, Enterprise and RAC as well as deployment on Oracle
Exadata Database Machine, Oracle DataGuard, and Oracle SuperCluster as supported by
Oracle.
• Content Server Oracle support includes Oracle client and Server interoperability support as
certified by Oracle.

OpenText Content Server 20.2 Release Notes

25
5.9 Virtualization Support
OpenText Content Server is supported for use with the server operating systems listed in the previous
sections. The supported server operating systems may be installed on physical or virtual hosts,
including cloud environments such as Google Cloud, Amazon Web Service and Microsoft Azure.
Customers that choose to use a virtual environment are encouraged to select a virtualization
platform intended for production systems and known to be fully supported by the server operating
system vendor.

Microsoft Azure is a supported virtualization environment. †

Note that Content Server is a resource intensive application and will require at least the same amount
of resources in a virtual environment as it would in a physical environment. Therefore, additional
resource scaling may be required to maintain the same level of performance in a virtual environment
as observed in physical environment. Static or committed resources within a Virtual Environment are
typically needed for performance sensitive scenarios.

5.10 Microsoft Office Integration Support

For information on integration with these versions of Office, please see the release notes for the
OpenText Enterprise Connect and Office Editor products.

OpenText Content Server 20.2 Release Notes

26
5.11 Microsoft Office File Format Support
Content Server supports storing, indexing, viewing, and thumbnail generation of the files generated
by the versions of Microsoft Office in the table below. For information on support for these versions of
Office, please see the release notes for the OpenText Enterprise Connect product.

Version Releases Notes

Office 95 Only text indexing and hit highlighting

Word, MS Project, and Excel 95
are supported with MS Project.

Office 97 Word, Excel, MS Project, and Only text indexing and hit highlighting
PowerPoint 97 are supported with MS Project.

Office 2000 Word, Excel, MS Project, and Only text indexing and hit highlighting
PowerPoint 2000 are supported with MS Project.

Office 2003 Word, Excel, MS Project, and Only text indexing and hit highlighting
PowerPoint 2003 are supported with MS Project.

Office 2007 Word, Excel, MS Project, and Only text indexing and hit highlighting
PowerPoint 2007 are supported with MS Project.

Office 2010 Word, Excel, and PowerPoint 2010

Office 2013 Word, Excel, Visio, and PowerPoint

2013

Office 2016 Word, Excel, Visio, and PowerPoint

2016

Office 2019 Word, Excel, Visio, and PowerPoint

2019

OpenText Content Server 20.2 Release Notes

27
5.12 Document Filters Format Support
The file types and versions the OpenText Document Filters support by default are listed here. All file
types are supported on Windows, Linux, and Solaris, except where indicated.

MIME type extraction is supported for all file types, except CDR.

On Linux and Solaris operating systems, only Western languages are supported for View as Web
Page and Thumbnails.

For details about format support, please refer to section 28.5.11 OpenText Document Filters of the
Content Server: Admin Online Help.

Text Indexing, View as Web Metadata

File Types
Hit Highlighting Page, Thumbnails Extraction

Word 95-2019 ✓ ✓ ✓
Excel 95-2019
Email – MSG
WordPerfect
RTF
CALS

PowerPoint 97-2019 ✓ ✓ ✓
Visio 2013, 2016
PDF
Postscript

OpenOffice Writer, Calc, Impress, ✓ ✓

Draw, Math

MS Project 95-2007 ✓
TAR, LZH, RDL, ZIP
Mail RFC822
IGES (Windows only)

DWG (up to AutoCAD 2016), ✓ ✓

DWF, DWFx, DXF, DGN
CADRA (Windows only)
Calcomp, HPGL, CGM
EMF, WMF
ME10 (binary ME10 compressed
format not supported)

JPEG, BMP, PNG, GIF, TIF ✓ ✓

Gerber ✓ Windows only

OpenText Content Server 20.2 Release Notes

28
5.13 OpenText product compatibility
The section provides details about which versions of other OpenText products are compatible with this
release of OpenText Content Server 20.2.

Important
For the latest compatibility information for OpenText products, refer to the
Compatibility Matrix (https://knowledge.opentext.com/go/matrix) on
OpenText My Support.

5.14 OpenText product compatibility

The section provides details about which versions of other OpenText products are compatible with this
release of OpenText Content Server 20.2.

OpenText Content Server Version Notes

Administration Client
Archive Center
Brava! for Content Suite 16 EP7 Requires license key to enable
Blazon for Content Suite 16 EP7 Requires license key to enable
Content Server Syndication Included, requires license key to enable
Document Pipelines
Enterprise Connect
Enterprise Library Services Deprecated
Imaging Review and Notes
Imaging Enterprise Scan
Imaging Windows Viewer and DesktopLink
Monitoring Agent
Object Importer Included, requires license key to enable
Office Editor
Content Suite PlOffice Online Add-
Open Text Directory Services
Solution Registry Agent
XML Workflow Extensions
XML Workflow Interchange
WebReports Included, requires license key to enable
WebReports Extensions for Workflow Included, licensed separately

OpenText Content Server 20.2 Release Notes

29
5.15 Language support
OpenText Content Server is currently localized in the following languages. Additional languages may
be available in future releases.

Component Languages

EN FR DE JA ES RU KO TW AR CA ZH NL FI IT KK PT SV UK

Smart View X X X X X X X X X X X X X X X X X X

Smart View X X X X X X X
User Help

Classic UI X X X X X X X X X X X X X X X X X X

Classic X X X X X X X

UI User Help

Administration X X X X X X X X X X X X X X X X X X

Administration X X X X

Help

OpenText Content Server 20.2 Release Notes

30
6 Installation and upgrade notes
This section provides additional installation and upgrade information, including related or third-party
product information and any required critical patches.

6.1 Installation notes

Before you install OpenText Content Server, review these additional installation notes and verify
related product or third-party product requirements.

6.2 Installation Note: OpenText Directory Services

If you update the Admin user properties, you may be prompted to update the password after logging
in the next time. You can work around this using the following procedure:

1. Go through with the password change and set a temporary password

2. Login to OTDS administration (e.g. http://localhost:8002/otds-admin)
3. Go to Partitions->Global Settings (at the top) ->Password Policy
4. Set 'Number of unique passwords before an old password can be reused' to 0 so that you can
reuse the desired password.
5. Press Save
6. Go to Partitions->otds.admin->Actions->View Members
7. otadmin->Actions->Properties->Account
8. Select 'Do not require password change on reset' and 'Password never expires'
9. Save
Login to CS and change the password for Admin as you did in the first place to the desired
value

If you are applying the 16.2.7 or 16.0.11 update to an existing Content Server that uses an Internal
OTDS server, you must go to Directory Services Integration Settings -> Configure Integration Settings
(?func=otdsintegration.settings) and click “Save” settings in order for Content Server to have
administrative rights in the Internal OTDS.

6.3 Installation Note: Search file systems

The search system components require accurate file locking to function correctly. Some NFS
systems do not properly propagate file attributes when configured for high availability and may require
the NFS noac configuration flag to be set.

Distributed File Systems are not suitable for storing the Search Index. Microsoft DFS is known to fail
for search. Likewise, on Microsoft Windows Servers, SMB2 and SMB3 Cache Redirector features
must be disabled. Microsoft has documented that this feature is not compatible with applications that
use file-based communication. Per the Microsoft description (http://technet.microsoft.com/en-
us/library/ff686200(WS.10).aspx), set or create the following registry keys of type REG_DWORD to
ZERO:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters
DirectoryCacheLifetime=0
FileNotFoundCacheLifetime=0
FileInfoCacheLifetime=0

OpenText Content Server 20.2 Release Notes

31
6.4 Installation Note: Records Management, Physical Objects,
Security Clearance modules
The Classifications, Records Management, Physical Objects and Security Clearance modules
are installed with Content Server. For new installations or upgrades, where Records
Management, Physical Objects or Security Clearance is not previously installed, the
administrator will need to enable the modules by going to the Content Server Administration>
Records Management Administration> Enable and Configure Records Management page to
confirm licensing. A license key is not required.

The latest version of the Physical Objects label control file is available for download on My
Support.

Installation Note: Records Management WebReports 1.8

Any modifications to the Records Management WebReports (OTRMReports) shipped with
previous releases will not be maintained on upgrade. You may wish to copy the report you
have modified prior to upgrade.

Caution
The release of Records Management OTRMReports 1.8 will need to be
manually upgraded by going to Content Server Applications
Administration > Applications Management.

OTPOReports 1.7 and OTRMSECReports 1.7 have not been upgraded.

6.5 Upgrade Notes for the OpenText Email Services Module

Caution

Never attempt to upgrade the Email Services module by uninstalling and

reinstalling it. Always follow the correct process for upgrading Content
Server modules.

Upgrading to Email Services 16.2 (included with Content Server 16) from
Email Services 10.5.1 or earlier requires a schema change. Depending on
the number of emails in Content Server, the upgrade might take some time
to complete.

6.6 Installation Note: Performance Improvement When Applying

16.2.4 to an Oracle Database
For Oracle upgrades only:
Pre-checks cannot be done as the tasks below require DBA (or SYSTEM) access to the database.
DBA should perform the following tasks to improve performance on Oracle upgrades. The setting of

OpenText Content Server 20.2 Release Notes

32
the Parallel parameters will ensure that statements with parallelism will be run as parallel.
1. Make sure Parallel parameters have been updated from the defaults.
2. Before running the upgrade:
ALTER SYSTEM SET parallel_degree_policy = AUTO;
ALTER SESSION ENABLE PARALLEL DML;
ALTER SYSTEM RECYLEBIN = OFF;
3. Calibrate the IO
sample:
--number of physical disks = phys_disk
--param max_latency = max_lat
SET SERVEROUTPUT ON
DECLARE
lat INTEGER;
iops INTEGER;
mbps INTEGER;
BEGIN
-- DBMS_RESOURCE_MANAGER.CALIBRATE_IO (<DISKS>, <MAX_LATENCY>, iops, mbps, lat);
DBMS_RESOURCE_MANAGER.CALIBRATE_IO (phys_disk, max_lat, iops, mbps, lat);
DBMS_OUTPUT.PUT_LINE ('max_iops = ' || iops);
DBMS_OUTPUT.PUT_LINE ('latency = ' || lat);
DBMS_OUTPUT.PUT_LINE ('max_mbps = ' || mbps);
END;

6.7 My Support Review

Documentation and resources for Content Server 20.2 are available on OpenText My Support and
linked from the Content Server landing page.

OpenText also recommends that you check the Content Server area of the OpenText My Support
(https://knowledge.opentext.com/go/16534305) for any documentation updates that may have been
posted after release.

6.8 Upgrade Note: Java – OpenJDK 11.0.1

As of version 16.2.8 Content Server now uses OpenJDK 11 instead of Java 8. There are no changes
in customer licensing or our support of products with this switch. OpenJDK and selected Java classes
are included in the install and upgrade packages.

Java 8 includes a number of Java classes that are not part of the standard OpenJDK distribution. If
you have custom or 3rd party extensions to Content Server written in Java, you should review the use
of Java classes by your application, and you may need to separately install any that are missing.

Within Content Server 16.2.8, Content Suite Viewer, available using the additional Brava! Server
Components install, did not support OpenJDK 11. Administrators could not install Brava! Server
Components onto a Content Server system running OpenJDK 11. Content Server 16.2.9 resolved
this incompatibility.

OpenText Content Server 20.2 Release Notes

33
6.9 Installation Note: Kubernetes
Content Server is also available as a Docker Container to be deployed in Kubernetes – a container-
orchestration system. For further information, please refer to the Content Suite Platform Release
Notes document.

6.10 Install Critical Patches

OpenText recommends that you use the OpenText System Center to keep your Content Server up
to date with all the applicable latest patches.

OpenText Content Server 20.2 Release Notes

34
 Configuration File Changes
Some features of Content Server, DCS and Search Engine are managed through configuration files.
This section outlines changes that are implemented or recommended with each Update. In some
cases, configuration files cannot be overwritten or updated automatically due to the potential for
conflict with customized settings. You should review the suggested changes and apply those which
can be safely made for your system.

Search Configuration Files. New versions of search configuration files are not installed when
applying an Update to an existing system because replacing these files would overwrite
customizations previously made. In this case the latest versions of the configuration files are placed
in a reference folder where you can review them and select specific edits for your configuration files:
<OTHOME>\config\config_reference.

If you are installing this update as a new install you will find these configuration files in
<OTHOME>\config.

The table below shows the Content Server Update in which each of the configuration files was last
changed. If the update is being applied to a new installation, these files should be copied to
the <OTHOME>\config directory before indexing any data.

File Change
16.2.11

In the \Config\licensemetering\ Update for LPAD-77295 – “License Metering: License Report PDF
folder Export”

• default2fo.xsl Business Administrators have the ability to generate a PDF export

• fop.xconf
of the license report for all registered ecosystems. The PDF
• header_opetentext.png
licensereport2fo.xsl export of the license report is basically taken from the Extended
•
ECM Platform.

The Business Administrator will have access to a web page

displaying the license report for all registered ecosystems. The
report will be based on calendar year, and will summarize not only
the license usage but, will provide a list of all users with their
assigned license as well as a list of users without licenses.

Currently, the License Metering framework is only used by

Extended ECM and therefore the license report shows only data
for Extended ECM products. The report can be accessed only
from the Extended ECM configuration volume.

16.2.9

In the Config\antisamy\ folder Update for LPAD-74495 – “Update Antisamy third party library”
• clean-customized.html • There are several changes in these files
• clean-loose.html

OpenText Content Server 20.2 Release Notes

35
 • clean-standard.html • Copy files from the config_reference\antisamy folder to
• clean-strict.html support the updated Antisamy library

Windows and Linux Update for FMT-1685 – “Filter configuration files must be moved
after upgrade.”
• Config\filters\image.ini
• These are new files
Linux only • Copy files from the config_reference\filers folder.
In the Config/filters/ folder

• /startXVFB.sh

• /shutdownXVFB.sh

Config\LLFieldDefinitions.txt \ Update for SRCH-5434 – “OTTracerExtratorID should be Long not

LLFieldDefinitions_EL.txt Integer”
In the #Index Tracer section of the file change the following:
INTEGER OTTracerExtractorID
To the following:
LONG OTTracerExtractorID

16.2.7

Config\application_dcs.ini Update for SRCH-5240 – “Provide default patterns for full text
matching”
Pattern detection and normalization for search indexing is enabled
by default on new installations for credit cards, social security
numbers, and US 10 digit phone numbers.
Add the following text:
[Patterns]
#
meta_sin=name:SIN pattern:regex_SIN op
eration:count,insert delim:zqsin
# regex_SIN=(^|\n|(?<=\D)[\s:])\d{3}([ -
])\d{3}\g2\d{3}(?=([\n\r]|[\s,\.;]\D))

meta_ssn=name:SSN pattern:regex_SSN op
eration:count,insert delim:zqssn
regex_SSN=(^|\n|(?<=\D)[\s:])\d{3}([ -
])\d{2}\g2\d{4}(?=([\n\r]|[,\.;\s]\D))

meta_credit=name:CreditCard pattern:rege
x_credit operation:count,insert delim:
zqcc
regex_credit=(^|\n|(?<=(\D[\s:])))[\d]{4}(
[ -
]?)[\d]{4}\g3[\d]{4}\g3[\d]{4}(?=([\n\r]|[
\s,\.;]\D))

meta_phone_na=name:PhoneNumber pattern:r
egex_phone_na operation:count,insert d
elim:zqph
regex_phone_na=(^|\n|(?<=(\+\d|\s\d|\D\D))
[\s:])(\()?\d{3}(?(3)(\))[ ]|[ \.-

OpenText Content Server 20.2 Release Notes

36
 ])\d{3}(?(3)[ -]|[ -
\.])\d{4}(?=(\s\D|[ex]|[\r\n]|[\.,;]\s))

Opentext.ini The following settings were moved from opentext.ini file to the
database:
• Configure Attribute Value Requirements
o [AttrRequiredValue]
• Configure Status Page for Multi Select Options
o [General\multiSelectProgressNumber]
16.2.6

config\antisamy\clean- Fix for LPAD-68499 – “Update Antisamy Version to support

standard.xml updated HTML controls”

Add the text in bold italics:

<tag name="a" action="validate">

<!-- onInvalid="filterTag" has been
removed as per suggestion at OWASP SJ 2007
- just "name" is valid -->
<attribute name="href"/>
<attribute name="onFocus"/>
<attribute name="onBlur"/>
<attribute name="nohref">
<regexp-list>
<regexp name="anything"/>
</regexp-list>
</attribute>
<attribute name="rel">
<literal-list>
<literal value="nofollow"/>
</literal-list>
</attribute>
<attribute name="name"/>
<attribute name="target">
<literal-list>
<literal value="_blank"/>
</literal-list>
</attribute>
</tag>
16.2.5

dcs.ini New configuration settings for pattern matching and injecting

normalize numeric values. Sample below:

[Patterns]
Meta=name:SSN pattern:Regex_SSN
operation:count,match,insert
delim:ssn,ssn_x
Regex_SSN=\b[0-9]{3}[-][0-9]{2}[-][0-9]{4}\b

OpenText Content Server 20.2 Release Notes

37
 Opentext.ini Update for Pyro-4090 “Add support for parallel for Oracle
database when upgrading”. This setting is only available in an
upgrade on a Content Server system using Oracle. Parallel is
enabled by default with the installer and disabled with the patch.

[DBUPGRADE]
EnableParallel=false (or true, depending
on what the user chooses)

Opentext.ini Fix for CAR-704 “Adjust configuration to adhere to naming

conventions”.
Settings to turn logging on and off have changed from

[contentmove_logs]
entryLogEnabled=true|false
To
[spchange]
enforceEntryLog=true|false

htmlToOTTag/mapping Fix for FMT-885 “Add AddrSender and DisplaySender”

#MSG Meta data Mapping
…
OTDocDisplaySender=OTDocDisplaySender
OTDocAddrSender=OTDocAddrSender

16.2.3

Opentext.ini Fix for CSEM-982 “Email Services objects prompt for required
attributes when dragged and dropped into a container”
A new entry is added as follows:
[PSTAGE]
AdditionalSupportedContainers={751}

16.2.2

Search.ini Fix for SRCH-4879 “Provide administration controls for configuring

exact substring search regions”
A new directory was created in the config folder called “tokenizers”
to allow the administrator to pick from a list.

16.2.1

Dcsrules.txt Fix for DCS-8271 “Update dcsrules.txt to remove unsupported

formats.”

OpenText Content Server 20.2 Release Notes

38
 Remove the following in [Thumbnail]

case OTMimeType = "application/iges",

"model/iges"
try IMTHUMB, PruneDoc

Dcsrules.txt Fix for SRCH-2701. “QDFBranch should by removed from the try
line of Office 2010/2007 formats in the DCSRules.txt file.”

Remove the following in [Convert]

"application/vnd.openxmlformats-
officedocument.wordprocessingml.document"
try IM, QDFBranch,PruneDoc
exec ConvertAttachments

Add the following in [Convert]

"application/vnd.openxmlformats-
officedocument.wordprocessingml.document"
try IM, PruneDoc

exec ConvertAttachments

Search_xmp_api.dtd Fix for SFWK-7064 “Support facets in search REST API.”

Remove the following in [Convert]

<!ELEMENT FacetItem EMPTY>

<!ATTLIST FacetItem
Count CDATA #IMPLIED
Value CDATA #REQUIRED>
Add the following:

<!ELEMENT FacetItem EMPTY>

<!ATTLIST FacetItem
Count CDATA #IMPLIED
DisplayName CDATA #REQUIRED
Value CDATA #REQUIRED>

Opentext.ini Fix for PYRO-3323 “Increase default size of SQL Connects and
Threads logs to 250 MB.”

In [thread_logs] AND [connect-logs] sections, update:

maxBackupIndex=10
maxFileSize=50

To

maxBackupIndex=4
maxFileSize=250

OpenText Content Server 20.2 Release Notes

39
7 New features and Fixes
Important
Security Fixes, Fixes of Note and New Features can be reviewed in the
OpenText Content Server 16 Release Notes List in OpenText My
Support.

8 Known issues
The following known issues exist in this release.

OpenText Content Server 20.2 Release Notes

40
Component Issue number Description

Physical LPU-10042 When a label is generated on item creation, some Records Detail fields do
Objects not display on the label. Once the Physical Object is created, regenerating
the label displays the Records Detail fields.

Records LPU-2635 For a User Hold to be applied to Text Documents (sub-type 145), the
Management Managed Objects page must have the Document sub-type (144) checked
for User Hold.

When RM metadata fields are required on the Add Item page and the
LPAD-35560,
items are dragged and dropped in the Classic View of Content Server, the
LPU-5344
user is not prompted to fill in the RM required fields. The content will be
uploaded, and the next time the user accesses the Records Detail tab, the
user will be prompted to fill in the required fields.

LPAD-47804, Deleted Category information of purged children is not captured.

LPU-7335 Category\Attribute information in the Audit Deletion Logs was added in
Records Management 16.0. However, when items are sent to the
Recycle Bin and later purged, the purged children’s Category\Attribute
information is not captured.

LPU-9960 The Disposition Search Results Export creates an HTML page that allows
it to be displayed in Excel with an .xls extension so that it is recognized as
a spreadsheet. The Document Conversion process fails to process the file
when using View as Webpage as the file is not a true .xls mime type. The
Document Conversion process fails to process the file as the format is
incorrect.

When opening this exported file in MS Office, an error occurs. However

the file can be opened in Excel and the converted file saved to Excel.

LPU-9257 When a Disposition Review Assignment from the Advanced Review

Workflow Assignment is reassigned, the RM Disposition Review link
displays in the Workflow Assignment. However, no search results are
displayed when accessing the RM Disposition Review snapshot.

Retention Schedules using Category Attributes as time or event-based

criteria may seem to export and import to other systems, but they will not
be recognized in the destination system. Schedules using Category
Attributes as criteria need to be manually edited after import.

The option on Dispositions to auto-process search results will only be

successful if Notifications are configured correctly.

Content EFSC-374 External file sharing using OpenText Core can be impacted whenever the
Sharing with Trusted Referrer settings in Content Server are not blank.
OpenText
Core
EFSC-892 The Content Sharing integration with OpenText Core needs to be re-
enabled after a patch upgrade of Content Server 20.2

OpenText Content Server 20.2 Release Notes

41
OpenText Content Server 20.2 Release Notes
42
9 Contact information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1

OpenText My Support: https://support.opentext.com

For more information, visit www.opentext.com

Copyright © 2020 Open Text. All Rights Reserved.

Trademarks owned by Open Text. One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
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.

43