Service Pack 2

OpenText Content Server 10.0.
0 Release
Notes
2016-06-23
Contents
Contents ................................................................................................................................................ 2
1
Introduction .............................................................................................................................. 6
About OpenText Content Server 10.0.0 ................................................................................. 7
Packaging and Documentation .............................................................................................. 7
Supported Environments and Compatibility ........................................................................ 8

4.1 Supported Platforms .................................................................................................................. 8
4.1.1
Supported Server Operating Systems ............................ 9
4.1.2
Content Server Client Support ........................................ 9
4.1.3
Content Server Browser Support .................................. 10
4.1.4
Content Server Database Support ................................ 11
4.1.5
Content Server Web Server Support ............................ 13
4.1.6
Application Server Support ........................................... 13
4.1.7
Java Runtime Support .................................................. 14
4.2 General Platform Support Notes ............................................................................................. 14

5
Installation and Upgrade Notes ........................................................................................... 15

5.1 Dependencies .......................................................................................................................... 15
5.2 Critical Patches ........................................................................................................................ 15
5.3 Help Files ................................................................................................................................. 16
5.4 Language Packs ...................................................................................................................... 16
New Installation Notes .......................................................................................................... 16

6.1 Installation Notes: General ...................................................................................................... 16
6.2 Installation Notes: Database.................................................................................................... 18
6.3 Installation Notes: LiveReports ................................................................................................ 19
6.4 Installation Notes: Search........................................................................................................ 19
6.5 Installation Notes: WebDAV .................................................................................................... 19
6.6 Installation Notes: Workflow .................................................................................................... 19
Upgrade Notes ....................................................................................................................... 19
Installing Content Server 10 Updates and Service Packs ................................................. 21
Notes for Specific Updates ................................................................................................... 22

9.1 Service Pack 2 Update 2016-06 Release Notes ..................................................................... 22
Content Server 10.0.0 Release Notes

9.10
Service Pack 2 Update 2014-03 Release Notes .............................................................. 24
9.11
Service Pack 2 Update 13 Release Notes ........................................................................ 24
9.12
9.13
9.14
9.15
Service Pack 2 Update 9 Release Notes .......................................................................... 26
9.16
Service Pack 2 Release Notes ......................................................................................... 27
9.17
Update 7 Release Notes ................................................................................................... 27
9.18
9.19
9.20
9.21
9.22
10
Appendix A Critical Patches .............................................................................................. 29
11
Appendix B Deprecated Patches ...................................................................................... 32
12
Appendix C Dependencies ................................................................................................ 42
13
Appendix D Changed and Deprecated Features ............................................................. 45

13.1
Feature Changes Update 2015-12 ................................................................................ 45
13.2
13.3
13.4
13.5
13.6
13.7
13.8
13.9
Feature Changes Update 13 .......................................................................................... 47
13.10
Feature Changes Update 12
13.11
Feature Changes Update 11 .......................................................................................... 48
13.12
13.13 Feature Changes Update 9
...................................................................................... 47
...................................................................................... 49
...................................................................................... 51
13.14
Feature Changes Service Pack 2 .................................................................................. 52
13.15
...................................................................................... 53
13.16
...................................................................................... 53
13.17
...................................................................................... 53
13.18
...................................................................................... 54
13.19
...................................................................................... 54
13.20
...................................................................................... 55
13.21
...................................................................................... 56
14
Appendix E Security Fixes ................................................................................................ 57
15
Appendix F Notable Fixes.................................................................................................. 83
16
Appendix G Configuration File Changes ....................................................................... 112
17
16.1
Update 2016-06 .............................................................................................................. 112
16.2
Update 2015-12 .............................................................................................................. 113
16.3
Update 2015-06 .............................................................................................................. 113
16.4
Update 11 ........................................................................................................................ 114
16.5
Update 10 ........................................................................................................................ 114
16.6
Service Pack 2 ................................................................................................................ 114
16.7
Update 7 .......................................................................................................................... 114
16.8
Update 6 .......................................................................................................................... 115
16.9
Update 4 .......................................................................................................................... 115
16.10
Update 3
.................................................................................... 115
Appendix H New Features ............................................................................................... 118

17.1
New Features Update 2015-12 .................................................................................... 118
17.2
17.3
17.4
17.5
17.6
17.7
17.8
New Features Update 13 ............................................................................................. 119
17.9
17.10 New Features Update 11

17.11
.................................................................................... 121
.................................................................................... 124
17.13 New Features Service Pack 2 .................................................................................... 126

.................................................................................... 127
18
17.15
New Features Update 6
.................................................................................... 127
17.16
.................................................................................... 128
17.17
.................................................................................... 132
17.18
.................................................................................... 135
17.19
.................................................................................... 137
17.20
New Features Initial Release (Update 0) ..................................................................... 138
Appendix I Known Issues ................................................................................................ 142

18.1
Known Issues: General ................................................................................................... 142
18.2
Known Issues: LiveReports ............................................................................................ 146
18.3
Known Issues: Multi-File Output ..................................................................................... 146
18.4
Known Issues: Projects ................................................................................................... 147
18.5
Known Issues: Search .................................................................................................... 147
18.6
Known Issues: Workflow ................................................................................................. 147
18.7
Known Issues: Internationalization User Interface.......................................................... 148
18.8
Known Issues: EPS Integration ...................................................................................... 148
19
Appendix J Applying Updates ......................................................................................... 148
20
Contact Information ............................................................................................................ 149
1 Introduction
These Release Notes describe updates and last-minute changes in OpenText Content Server.
OpenText recommends that you read these Release Notes in conjunction with the documentation
included with the software package. If conflicts exist, the Release Notes supersede the other
documentation.
We also recommend that you check the OpenText Knowledge Center
(https://knowledge.opentext.com/) for any patches or documentation updates that may have been
posted after the initial release of Content Server 10.0.0.
The Content Server Release Notes are revised frequently to incorporate corrections, and to reflect
any changes that may occur with each Update.
The current format for Content Server 10.0.0 Release Notes was first adopted with the delivery of
Update 6 in March 2012. The information contained in the Appendices for Updates prior to Update 6
is not comprehensive.
2 About OpenText Content Server 10.0.0

OpenText Content Server 10.0.0 is the leading collaboration and Enterprise Content Management
(ECM) system for global organizations. It provides a single, comprehensive solution for managing
information and makes collaboration a part of every business process, even across organizational
and geographic boundaries. OpenText Content Server 10.0.0 brings together employees across your
organization, as well as partners.
3 Packaging and Documentation

Downloads and documentation for OpenText Content Server 10.0.0 are available in the OpenText
Knowledge Center (https://knowledge.opentext.com/).
4 Supported Environments and Compatibility

This section provides details on supported platforms and version information.
4.1
Supported Platforms
The following sections provide a reference to the supported hardware and software components
required to use OpenText Content Server. In all of the following tables there are three possible
values:
C = Certified
This platform was used for regression testing with this release of Content Server by OpenText.
Customer use is fully supported by OpenText Customer Support.
S = Supported
This platform received limited testing for this release of Content Server by OpenText. Customer use is
fully supported by OpenText Customer Support.
Not Listed = Unsupported
This received no testing by OpenText. There may or may not be known issues with this platform. Its
use is not supported by OpenText Customer Support.
4.1.1 Supported Server Operating Systems

Server Support
Platform
Support Level
SPARC Solaris 10 (64-bit)
Notes
Windows Server 2008 R2 (64-bit)
Windows Server 2008 SP2 (64-bit)
First available 3 May 2011
Windows Server 2012

Windows Server 2012 R2
S
S
First available with Update 11
Red Hat Enterprise Linux 5.0 5.9
First available with SP2

Update 2014-03
Oracle 11.2.0.4 first
available with Update 201503.
5.0 - 5.7: First available
with Update 4
5.9: First available with
Update 11
4.1.2 Content Server Client Support

Client Support
Client Platform
Windows XP SP3 (32-bit)
Support Level
Windows 7 (32-bit)
Windows 7 (64-bit)
Windows Vista (32-bit)
Windows 8 (64-bit)
Windows 8.1 (64-bit)
S
S
Windows 10 (64-bit)
Notes

Update 2014-09
Update 2016-03
4.1.3 Content Server Browser Support

Browser Support
Browser
IE 6
Support Level
Notes
IE 7 (32-bit)
IE 8 (32-bit)
IE 8 (64-bit)
IE 9 (32-bit)
IE 9 (64-bit)
IE 10 (64-bit)

Update 11
IE 10 (32-bit)

Update 11
IE 11 (32-Bit)

Update 2014-09
IE 11 (64-bit)

Update 2014-09
Firefox 3.6
Firefox ESR
Support is for the latest

version of Firefox ESR
Version 31 validated as
of SP2 Update 2014-12
Safari 5.1.x on OSX 10.7.x
Chrome

Update 10

Validated with Safari
5.1.1 on OSX 10.7.2
10
4.1.3.1
Browser Support Notes
Chrome
Chrome announced that NPAPI support will be removed from Chrome. The Content Server Print
feature is dependent on NPAPI. If you upgrade to a version of the browser where NPAPI is no
longer supported then the Print functionality will not work.
The Short Links section on the General properties page does not include options to Copy. Only
Internet Explorer allows access to the clipboard, so it is not possible to add this feature to the
other browsers. As a workaround, users can copy and paste the links that appear below the list of
options.
Firefox
Mozilla announced that Plugins, written using NPAPI, are now a legacy technology. The
Content Server Print feature is dependent on NPAPI. If you upgrade to a version of the browser
where NPAPI is no longer supported then the Print functionality will not work.
The Short Links section on the General properties page does not include options to Copy. Only
Internet Explorer allows access to the clipboard, so it is not possible to add this feature to the
other browsers. As a workaround, users can copy and paste the links that appear below the list of
options.
Internet Explorer
IE 10 - The Document Type for Content Server is DOCTYPE 3.2 which puts the browser in
quirks mode. The CKEditor does not display correctly with IE 10 in quirks mode. The work
around is to activate compatibility view.
4.1.4 Content Server Database Support

Note: Databases are supported on any operating system supported by the database vendor.
It is not required that the database be on the same platform as the Content Server.
Database Support
Database Platform
SQL Server 2008
Support Level
Notes
Includes Standard, Enterprise and

Datacenter
SQL Server 2008 R2
May 2011
Datacenter
SQL Server 2008 R2 SP1
11

Datacenter
First available with SP2 Update 201403

Datacenter
First available with SP2 Update 201509

Datacenter
SQL Server 2012 SP2
First available with CS SP2 Update 9

SQL SP2 validated as of SP2 Update
2014-12
Oracle 11G R2

RAC
Oracle 11.2.0.4 is required for
Windows 2012 and Windows 2012 R2
support
Oracle 11.2.0.4 supported with
Windows 2012 R2 as of Update 201503
Oracle RAC
4.1.4.1
Database Support Notes
Oracle 11
Oracle 11.2.0.4 is the recommended version of Oracle 11 with Content Server

Oracle 11.2.0.4 is required for Windows 2012 and Windows 2012 R2 systems. Earlier
versions of Oracle 11.x do not support Windows 2012 or Windows 2012 R2.
12
4.1.5 Content Server Web Server Support

Web Server Support
Web Server
Support
Level
Notes
Apache HTTP Server 2.2.21

(64-bit)
IIS 7.5 for Windows Server

2008 R2 (64-bit)
Validated on Windows Server 2008 RC2 (64-bit)
IIS 7.0
Validated on Windows Server 2008 SP2 (64-bit)
IIS 8.0
Validated on Windows Server 2012 (64-bit)

Validated on Red Hat Enterprise Linux 5.05.9
As of SP2 Update 11
IIS 8.5
Sun Web Server 7 for Solaris

10
Validated on SPARC Solaris 10 (64-bit)
Oracle iPlanet Web Server
First available with SP2 Update 2014-03 in

conjunction with Windows 2012 R2 support.
Validated on version 7.0.9

In 2010, Sun Java System Web Server was
renamed Oracle iPlanet Web Server.
Oracle iPlanet Web Server 7.0.9 is the
subsequent point release of Sun Java
System Web Server 7 U8.
4.1.6 Application Server Support

Application Server Support
Application Server
Tomcat 6
Support Level
Tomcat 7
IBM WebSphere 7
On SPARC Solaris 10 (64-bit)
Notes
13
4.1.7 Java Runtime Support

Java Runtime Support
Java Runtime Support
Support
Level
Notes
Oracle Java 1.6
Java included in Content Server install.
Oracle Java 1.6.x
Client-side Java versions supported.
Oracle Java 1.7.x
Client-side Java versions supported.
Special Note regarding Java Update 51:

o Java Update 51 support provided with
hotfixes for SP2 Update 2014-03 only.
See Appendix A Critical Patches.
o Support for Java Update 51 included with
SP2 Update 2014-06 and later updates
(no hotfixes are required).
Microsoft Office Support

Content Server supports storing, indexing and viewing of the files generated by the versions of
Microsoft Office in the table below. For information on integration with these versions of Office, see
the release notes for the OpenText Enterprise Connect product.
Microsoft Office Support
4.2
Versions
Notes
Office 2007
Word, Excel, and PowerPoint 2007
Office 2010
Office 2013
General Platform Support Notes
Virtualized Environments: OpenText Content Server is supported for use with the server operating
systems listed in the previous section. The supported server operating systems may be installed on
physical or virtual hosts. 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.
14
Please 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
Service Packs and Point Releases: Due to the continual release of software, there may be newer
versions of software components than those listed in these Release Notes. It is OpenTexts policy to
support service packs and minor point releases of supported software platform components that are
more recent than those listed in the Release Notes. New major releases of platform components are
not automatically supported.
Operating System Patch Level: The current set of patches recommended by your operating system
software vendor should be installed on the hardware running your Content Server.
5 Installation and Upgrade Notes

There are three basic variations of installation covered in these Release Notes a new installation, an
upgrade from a version of Content Server prior to 10.0.0, and applying an Update or Service Pack to
an existing installation of Content Server 10.0.0. This section contains information that applies to all
three of these cases.
If you are upgrading from a version of Content Server prior to 10.0.0, you must read both the New
Installation Notes section and the Upgrade Notes section.
Content Server 10.0.0 is regularly refreshed with Updates. Updates are sometimes rolled into a new
installation package, which makes new installations of the current Update simpler. For example, to
install Update 4, you could install Content Server 10.0.0 and apply Update 4, or you can install the
Content Server 10.0.0 with Update 4 package.
If you are installing a new version of Content Server 10.0.0, which includes an Update, you must read
both the New Installation Notes section and the Upgrade Notes section.
5.1
Dependencies
The minimum requirements for Content Server can change with each Update. Changes can occur in
the requirements for the operating system components, or minimum installation requirements of other
OpenText or third-party software. Review Appendix C to ensure that dependencies are met for the
Update being installed before attempting to install Content Server or apply an Update.
5.2
Critical Patches
Occasionally, changes that must be made cannot be incorporated into the Update. In this event,
OpenText will issue Critical Patches that must be applied as part of the Update. These Critical
15
Patches must be applied after installation of the files, but before using Content Server. Review
Appendix A to identify required patches.
In addition, you should review the OpenText Knowledge Center to identify other available patches that
you may need to apply.
5.3
Help Files
OpenText requires that you delete and recreate the Help Data Source Folder whenever you add or
remove language packs, or when the system default locale is modified.
The reason for the requirement is that during the creation of a help data source, Content Server
stores the set of currently installed language packs. This list is used to correctly associate a system
language with its corresponding help files within the search index. This ensures that searches within
User Help or Admin Help will only search the help files corresponding to the current users system
language of choice.
When a new language pack is installed, the Help and Admin Help data sources need to be deleted
and recreated.
If the language pack is already installed and an Update patch or Service Pack is being applied, you
only need to start the Directory Walker of the help data sources to update them.
5.4
Language Packs
A new installation and most Updates include changes to text contained in the Language Packs. If you
are using Language Packs, which are needed for language support other than English, you must
obtain and install the relevant Language Pack as part of the installation process.
6 New Installation Notes

Before you install a new instance of OpenText Content Server 10.0.0, review these installation notes
and verify related OpenText and third-party product requirements. These notes are specific to the first
release (Update 0).You should also review the Update Notes section.
6.1
Installation Notes: General
1. Some Update levels of Content Server will require installation of a Critical Patch for correct
functionality. Refer to Appendix A.
2. With IIS you may experience issues with features that use .properties files. For example you
may see an HTTP Error 404 - File or Directory not found.
16
To resolve this you should configure IIS to recognize files with the .properties extension as
application/octet-stream by performing the following steps:
a) In the IIS Microsoft Management Console (MMC), right-click the local computer name, and
then click Properties.
b) Click MIME Types.
c) Click New.
d) In the Extension box, type the .properties file extension.
e) In the MIME Type box, type application/octet-stream.
f) Apply the new settings. Restart the World Wide Web Publishing Service or wait for the worker
process to recycle for the changes to take effect.
You should also configure IIS to recognize files with the .tlx and .clx extensions by performing the
following steps:
a) Locate the virtual directory for the Enterprise Server support files in IIS.
b) Navigate to the Properties Page of the virtual directory.
c) Select the HTTP Headers tab.
d) Click Add.
e) Add the .tlx and .clx file extensions.
f) Click OK.
3. On Windows, if you are logged in as a "named" user (not the Administrator user) with
administrative privileges and you have Windows UAC (User Account Control) enabled then
you will receive the error "There is a problem with this Windows Installer package. A script
required for this install to complete could not be run. Contact your support personnel or
package vendor." during the installation. To work around this issue, you must select the
executable, bring up the context menu, and then select 'Run as Administrator' which will run
the install with elevated privileges.
4. Apache Tomcat treats URLs as case sensitive, unlike IIS or Sun ONE Web servers. For
example, with Tomcat, the following URLs are considered to be different:
https://my_host_name/path_name/cs.exe
https://my_host_name/Path_Name/cs.exe
5. Do not alter the standard permission set on the Document Undelete Volume (for Public
Access and Domain groups) to See and Add Items. If you do, the affected users will be
unable to delete documents. (1710973 and LPAD-13683)
6. When installing Content Server, you must configure your antivirus software to exclude the
Content Server installation directory and all subdirectories, as well as the directories that
contain the Content Server search index files. (1602027 and LPAD-13625)
7. Access to the Uninstall Modules page requires a Content Server login, not just an
administration login. (1963600 and LPAD-10376)
17
8. When you install one or more modules that require configuration during installation (such as
Spider, Electronic Signature) together with one or more other modules, some of the modules
may fail to install. You can go back to the Install Module page to install them. (1648347 and
LPAD-13652)
9. Administrators should review the settings for all auditable events after upgrading Content
Server as well as after installing or upgrading modules, as there may be additional available
events after the upgrade. (LPAD-14800)
10. Before installing and configuring an application server for use with Content Server in a Secure
Extranet environment, a Java development environment must be installed. A JRE (Java
Runtime Environment) is not sufficient as the application server requires the Java Compiler
(javac), which compiles JSP pages into class files. This component is a part of the Java 2
Platform, Standard Edition (Java SE). For the supported version of the Java 2 Platform, see
Supported Environments and Compatibility on page 8. (LPAD-16820)
11. When configuring Content Server to use Secure Extranet Architecture (SEA), 'filterPath=n'
(where 'n' is the path to /filters directory for the Content Server installation) must be added to
the [filters] section of the opentext.ini for the servlet to load properly. (LPAD-16852)
12. For version 10.0.0 of Content Server, My Home functionality was removed. However, My
Home still appears as a valid option for a default start page on the Server Configuration
Parameters page. (LPAD-22197)
13. It is recommended that modules be installed one at a time. Installing multiple modules at the
same time could result in a "Server Did Not Respond" error. (LPAD-22821)
14. Windows 2008 R2 installation note for non-ASCII characters. There is an issue where MultiFile output functionality does not support non-ASCII chars. All of the chars are converted to
underscore "_" when zip and download is used. This is resolved by kb 2704299 from
Microsoft - https://support.microsoft.com/en-us/kb/2704299
6.2
Installation Notes: Database
1. If you are installing Content Server with a Windows-based Oracle Server, you must create the
Oracle database with a block size of 8K. If the block size is too small, you will receive an error
"maximum key length (758) exceeded" for 2K block size "ORA-01450 maximum key length
(1578) exceeded" for 4K block size when Content Server is creating the index "GIPathIndex"
on "Recd_OperationSummary(1904158 and LPAD-13760)
2. When using an Oracle database with a UTF-8 Content Server, "ENV_NLS_LANG" under
[Lang_en_US] in the opentext.ini must be set to '.AL32UTF8' for Content Server to function
properly. (LPAD-17203)
3. When using Content Server with Microsoft SQL Server, you cannot use a SQL Server
password that contains a semicolon. Attempting to do so will result in an error "Invalid
connection string attribute" from the Microsoft ODBC SQL Server Driver. Use a password that
does not contain semicolon. (1925113 and LPAD-10116)
18
6.3
Installation Notes: LiveReports
1. If you intend to use the standard LiveReports 25 Largest Documents and Documents with
the Most Versions on very large databases, you may need to configure the TEMPDB or
SYSLOGS parameters to have sufficient space. (1465877 and LPAD-13584)
6.4
Installation Notes: Search
1. If installing Search components on Windows Server 2008 or Windows Server 2008 R2 and
using SMB2, the Cache Redirector in Windows must be disabled. Microsoft has documented
that this new feature is not compatible with applications that use file-based communication.
Per the Microsoft description here -- http://technet.microsoft.com/enus/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
6.5
Installation Notes: WebDAV
1. The OpenText WebDAV module is available as part of a basic Content Server install.
Download and read the OpenText WebDAV 10.0.0 Release Notes that contain more detail
and important information.
6.6
Installation Notes: Workflow
1. Email-enabled Workflow features require eLink to be installed and configured before they are
available for use.
7 Upgrade Notes
Before upgrading from an earlier version of Content Server (or Livelink) to Content Server 10.0.0,
review the following instructions:
1. OpenText currently supports upgrading to Content Server 10.0.0 from Content Server 9.5.0.1
(UTF-8). It is recommended that you visit Content Server 2010 Upgrade Central for
additional information about upgrading to Content Server 10.0.0.
2. When installing Content Server with an existing database, you should disable Notifications
before upgrading. (1647962 and LPAD-13656)
19
3. The Content Server database must be backed up before an upgrade is attempted. If the
database upgrade fails, the reason for the failure can be analyzed and resolved, and the
upgrade can be rolled back and started again from the beginning. OpenText does not
recommend restarting a failed database upgrade, as this will leave steps in the upgrade in an
incomplete state. (LPAD-14354)
4. The Database Upgrade Status page may incorrectly display the message, "The database
upgrade has completed successfully" when, in fact, there were errors reported. Scrolling
down the log will reveal non-fatal errors. The dbupgrade and thread logs should be reviewed
after upgrading Content Server to assess possible errors. If any errors are found, discontinue
the upgrade and contact OpenText Customer Support. (LPAD-14786)
5. When upgrading to Content Server 10.0.0, if the upgrade converts a varchar(4000) or similar
column type to a CLOB, LiveReports that use ORDER BY, UNION, GROUP BY, or any other
method of sorting or mass-comparison on the resulting CLOB (i.e. the former varchar(4000)
columns) will require type conversion using DBMS_LOB.SUBSTR(). (LPAD-24363)
6. When upgrading to Content Server 10.0.0, a manual change must be made to the
opentext.ini file before connecting to an existing database. The following lines must be
removed from the opentext.ini file:
dftConnection=databasename
HaveValidatedDBAdminServers=TRUE
Also, the following sections must also be removed:
[dbconnection:databasename]
[DBUPGRADE]
7. When upgrading to Content Server 10.0.0, the Facets Volume must be manually created after
connecting and upgrading the database. The following must be set in the opentext.ini file
[general] section before running the command:
HaveValidatedFacetsVolume=false
While logged in as the Content Server Admin user, run the following command to create the
Facets Volume:
?func=admin.AutoCreateFacets
When upgrading to Content Server 10.0.0, the Facets Volume must be manually created after
connecting and upgrading the database. The following must be set in the opentext.ini file
[general] section before running the command:
20
8 Installing Content Server 10 Updates and Service Packs

Note: To insure a successful installation OpenText recommends that you review the Content Server
10.0.0 Installation Guide before installing.
Refer to Appendix J for a summary of the procedural steps you will need to perform as part of
applying an Update.
OpenText provides cumulative Updates to Content Server 10.0.0 on a regular basis, typically every
three months. Updates generally contain some combination of performance enhancements, bug
fixes, security patches, usability improvements and new features.
The delivery of Updates has changed as of the introduction of Content Server 10.0.0. Updates to core
components are delivered as OSpaces (.oll files). These fixes previously appeared within the MMYYYY.pat file. Some optional module fixes still remain in the MM-YYYY.pat file format. The MMYYYY.pat file now resides in the /patch directory within the patch archive. It is no longer necessary to
move the MM-YYYY.pat file into the /patch directory during deployment.
The software included in each Update is cumulative. For example, if you are currently using Content
Server 10.0.0 with Update 3, you can apply Update 6 without installing Updates 4 and 5 first.
However, there may be upgrade steps associated with some Updates related to module
dependencies or configuration changes which must still be reviewed and performed.
In general, OpenText strongly recommends that you remain current with applying Updates. The
Release Notes contain a number of Appendices that will help you understand the changes included in
each Update. These include:
Security Fixes. Bug fixes and behavior changes deemed to be security improvements are
outlined in Appendix E.
Changes or Deprecated Features. Some features may be changed or deprecated in an
Update. Review Appendix D before applying the Updates to identify any potential impact for
your application.
New Features. A detailed list of new features included in each update can be found in
Appendix H.
Bug Fixes. The complete list of bug fixes and changes for an Update is contained in a
Readme file included in the patch binaries folder on the Knowledge Center. Appendix F
contains notable bug fixes.
21
9 Notes for Specific Updates

This section contains information about specific Content Server Updates. If you have skipped
Updates, then review the notes for all of the Updates you are applying. Review the Appendices for
details and additional information.
9.1
Service Pack 2 Update 2016-06 Release Notes
Content Server 10.0.0 Service Pack 2 Update 2016-06 was released June 2016. There are both
cumulative Updates and a complete installation available.
This is the last regular scheduled update for Content Server 10.0. Content Server 10.0 has reached
end of life for product support. Customers are strongly advised to upgrade to Content Server 16 at
their earliest convenience.
NOTE: If your Content Server 10.0.0 environment is currently running Update 2014-09, the hotfix
pat100001815 is required for the Update Analyzer to be able to do the analysis prior to updating to
SP2 Update 2016-03.
9.2
Content Server 10.0.0 Service Pack 2 Update 2016-03 was released March 2016. There are both
Beginning with Update 2016-03, Search Engine 16 will be included in Updates in place of Search
Engine 10.0 or Search Engine 10.5.
SP2 Update 2016-03.
9.3
Content Server 10.0.0 Service Pack 2 Update 2015-12 was released December 2015. There are
both cumulative Updates and a complete installation available.
SP2 Update 2015-12.
22
9.4
Content Server 10.0.0 Service Pack 2 Update 2015-09 was released September 2015. There are
SP2 Update 2015-09.
The Content Server Document filter functionality uses the libpng library installed on the Content
Server server machine with Content Server 10.0 and all 10.0 updates. Due to recent security updates,
OpenText recommends that the libpng library on the server machine be updated to at least libpng
version 1.2.54 on the Content Server system.
9.5
SP2 Update 2015-06.
9.6
SP2 Update 2015-03. This hotfix is not required after applying Update 2014-12.
9.7
Content Server 10.0.0 Service Pack 2 Update 2014-12 was released December 2014. There are
Content Server 10.0.0 Service Pack 2 Update 2014-12 applies changes to the database schema. For
additional details, please refer to the OpenText Content Server SDK System Schema Guide.
SP2 Update 2014-12. This hotfix is not required after applying Update 2014-12.
23
9.8
Content Server 10.0.0 Service Pack 2 Update 2014-09 was released September 2014. There are
9.9
9.10 Service Pack 2 Update 2014-03 Release Notes

9.11 Service Pack 2 Update 13 Release Notes

Content Server 10.0.0 Service Pack 2 Update 13 was released December 2013. There are both
Beginning with Update 13, Search Engine 10.5 will be included in Updates in place of Search Engine
10.0.
Content Server 10.0.0 Service Pack 2 Update 13 applies changes to the database schema. For
NOTE: The Content Server 10.0.0 Service Pack 2 Update 13 schema is identical to the 10.5 schema.
Please refer to the schema documentation that accompanies Content Server 10.5.

Content Server 10.0.0 Service Pack 2 Update 12 was released Sept 2013. There are both cumulative
Updates and a complete installation available.
Note that some settings from the opentext.ini file are moved into the database when applying this
Update. Ensure that any customizations of these settings are included in the opentext.ini file on the
instance of Content Server where the upgrade is run, or edit and review these settings in the Admin
pages once the upgrade is complete. Settings are:
truncation=x
wantResultLocationPath=TRUE
pathTruncation=80
Notable changes include the following, with details in the appendices:
24
Maximum search forms per user now in Admin interface.

Search result presentation settings now in Admin interface.
Extractor now provides explicit controls for each extraction type.
Advanced Search with MIME types and SubTypes improved.
Width of tabular search results limited.
Appearances removed from Target Browse dialog.

Content Server 10.0.0 Service Pack 2 Update 11 was released June 2013. There are both
Note that normally cached facet counts are used to determine whether or not to display the Facet
Panel in the sidebar for browse. If a cache entry is not available, a check determines if any facets are
available for the location in question. If facets are available, the UI will make a request to get the facet
counts; if not, the facet panel will be disabled.
Update. Ensure that custom Download Collection as Spreadsheet settings are included in the
opentext.ini file on the instance of Content Server where the upgrade is run, or edit and review these
settings in the Admin pages once the upgrade is complete. Settings are:
largestUncompressedSpreadsheetInKB
maxItemsPerSpreadsheet
maxOperationSize
The search Region Map data is moved from a file stored externally into the database.
A feature to return to the last page of search results has been added.
Multiple custom views for a folder can now be prioritized for display.
Initiated Workflows can be excluded from indexing.
Search statistics now include better differentiation of possible search sources.
TEXT metadata is now permissible in search relevance ranking adjustments.
25

Content Server 10.0.0 Service Pack 2 Update 10 was released March 2013. There are both
Update. Ensure that custom Extractor, Best Bets and Nickname settings are included in the
opentext.ini file on the instance of Content Server where the upgrade is run, or edit and review these
settings in the Admin pages once the upgrade is complete.
If you have the Remote Search module installed, it should be uninstalled before applying Update 10
or later, since this module is now included in the core code. Do not remove your remote search
processes.
Remote Search module is now installed as part of the core software.

Many settings formerly located in the opentext.ini file for Best Bets, Nicknames and the
Extractor are now managed from administration pages and stored in the database.
Custom view search forms are extended to allow selection of the search form if multiple
forms exist for a folder.
Support for document files with a size of zero bytes.

Content Server 10.0.0 Service Pack 2 Update 9 was released December 2012. There are both
Notable changes include:
A new storage mode in the Search Engine that can support 3 times as many objects in a
search partition.
User preferences are now available for the search results display style. The current default
Admin search template and default User search templates are upgraded to use this feature.
Search Engine 10 is now included in the Update, and does not need to be separately
installed.
Added support for indexing Star Office and Open Office document types.
26
9.16 Service Pack 2 Release Notes

Content Server 10.0.0 Service Pack 2 was released September 2012. There are both cumulative
Updates and a complete installation.
Content Server 10.0.0 Service Pack 2 applies changes to the database schema. For additional
details, please refer to the OpenText Content Server SDK System Schema Guide.
The Update Analyzer, shipped with Content Server 10.0.0 SP2, is an administrative tool used to
baseline a Content Server 10.0.0 deployment in order to conduct a comparative analysis against
changes included in Content Server 10.0.0 Update. The tool produces a report which advises
Administrators of differences and recommends hotfixes which can be safely removed once the
Update is applied. The tool can produce a CSV version of the Report which can be sent to Customer
Support, if requested.
Notable changes include:
The addition of search filters and removal of search themes.

Improved accuracy of cached Facet counts
Added support for View as Webpage functionality on Linux platform (formats are MS Word,
Excel, PPT and PDF)
Platform Support for Safari on OSX and Firefox ESR
9.17 Update 7 Release Notes

Content Server 10.0.0 Update 7 was released June 2012. There are both cumulative Updates and a
complete installation.
Content Server 10.0.0 Update 7 applies changes to the database schema. For additional details,
please refer to the OpenText Content Server SDK System Schema Guide.

Content Server 10.0.0 Update 6 was released March 2012. There are both cumulative Updates and a

Content Server 10.0.0 Update 5 was released December 2011. This is a cumulative Update only,
without a complete installer.
27
Update 5 does not apply any changes to the database schema.

Notable feature improvements include Virtual Folder capabilities, a Search Administration Browser,
and the ability to export a Collection as a Spreadsheet.

Content Server 10.0.0 Update 4 was released September 2011. There are both cumulative Updates
and a complete installation.

Content Server 10.0.0 Update 3 was released June 2011. There are both cumulative Updates and a

Content Server 10.0.0 Update 2 was released March 2011. This is a cumulative Update only, without
a complete installer.
28
10 Appendix A Critical Patches

A Critical Patch (or hotfix) is one that must be installed for correct operation. The need for hotfixes
generally arises when a serious defect is found during final testing and OpenText is unable to create
and test a new release candidate in a timely manner. Usually, these patches must be removed before
applying a later Update.
You should also check the OpenText Knowledge Center for the most current information about other
available patches. It is important that each hotfix be applied in numerical order.
Update
Patch
Notes
2015-06
pat100002019
Address an error during workflow item handler move.
2015-03
pat100001865
Category set does not display in the user interface when adding a
new category. Unable to add a multi-value category on the add
category page.
2014-12
pat100001810
Trace file is created when the subject is too long. Error appears
an unknown feature was specified for eLink
pat100001809
Patch for Archive Storage Provider 10.0.2 which is required for

OpenSSL Library compatibility with Content Server 10.0 2014-12.
pat100001795
Export If No Data feature does not work when using the oscriptbased reports (basic_scripted, csv_report) *LEGACY ONLY*
pat100001763
Requests from SAP fail if ""Enable Time Zone Offset"" is enabled

in Content Server.
pat10001815
Update Analyzer does not proceed if there is a version mismatch

between the update.ini and the file analysis.
pat100001696
WebReports: Allow parameter prompts to be used with the

Search Query Launch data source.
pat100001694
WebReports: Scripted report views sometimes show unwanted

pseudo-column when sorting is used.
pat100001676
Web Reports: Several fixes for INHERITATTRS:SOURCE.
pat100001657
WebReports: Several fixes to Category Update.
2014-09
29
pat100001652
Virtual Folders: inconsistent behavior when performing copy or

move in web UI.
pat100001649
LiveReports: A string input variable that mimics a parameter

identifier will be interpreted and replaced by the value of that
parameter.
pat1000001628
WebReports: SETWFFORM isn't working when running as a

SubWorkID.
pat100001267
Signed Spell Checker and Text Editor Applets required to meet

the new Java 7U51 Security requirements.
pat100001287
Signed LiveReports Applet required to meet the new Java 7U51

Security requirements.
pat100001349
Addresses issue with the result cache.
pat100001354
Open and download do not work because the REST API mapping
as the signature is incorrectly created for the content resource.
pat100001379
UserID displayed in workflow audit trail when fix for LPAD-30453

is applied.
pat100001361
Index Restore Wizard fails on systems with many partitions
pat100001393
XML Activator does not support "AddOrModify" and

"DeleteByQuery".
12
pat100001000
Corrects a problem introduced in Update 12 in the construction of

search queries.
11
pat100000866
Search Engine 10 Update 11 Release 2 fixes a problem in which

indexing may fail to resume if it pauses to accommodate high
loads, such as when an index backup is run.
11
pat100000789
Required if using Enterprise Connect 10.3.0
11
pat100000831
Required if using Content Server Pulse 10.0.0
10
pat100000718
Corrects a stack crawl in Distributed Agent when the DA worker

attempts to run a leftover task. LPAD-32707.
2014-03
30
10
pat100000731
pat100000605
pat100000608
This patch is only applicable for Linux and Solaris systems
SP2
NA
No critical patches at release time.
pat100000389
pat100000394
pat100000259
Required if using Remote Search module.
pat100000074
Content Server 10.0.0 Update 2 did not ship with a version of

llisapi.dll. A hot fix for Windows 100000074_CS64_WIN.zip is
required. LPAD-25333
pat100000015
Corrects an issue where the GetUniqueName() LLIAPI function

which would result in incorrect results being returned. LPAD23470
N/A
Content Server requires the September 2010 update for Content

Server 10.0.0 or newer. Patches are available on the Knowledge
Center.
Distributed Agent database upgrade on Oracle could take a long

time when the database contains large or fragmented tables.
LPAD-32774.
31
11 Appendix B Deprecated Patches

Many Updates will incorporate fixes that were deployed as patches for previous versions. When these
fixes are incorporated in an Update, the patch files must be removed before installing the Update to
prevent code conflict and unexpected behavior. The table below identifies patches that are known to
be deprecated, listed by Update number. For example, if installing Update 4, you must remove any
patches listed as deprecated in Update 4 or earlier before installing Update 4.
Update
Patch Numbers to be Removed
Update 2016-06
pat100002240
pat100002253
pat100002254
pat100002263
pat100002264
pat100002268
pat100002273
pat100002304
Update 2016-03
pat100002190
Update 2015-12
pat100002133
pat100002135
pat100002136
pat100002137
pat100002141
pat100002153
pat100002161
pat100002166
Update 2015-09
pat100002001
pat100002002
pat100002019
pat100002022
pat100002038
pat100002039
pat100002040
pat100002045
pat100002079
pat100002085
pat100002121
Update 2015-06
pat100001865
pat100001894
32
pat100001913
pat100001949
pat100001975
pat100002043
Update 2015-03
pat100001700
pat100001720
pat100001763
pat100001766
pat100001768
pat100001786
pat100001789
pat100001794
pat100001804
pat100001806
pat100001810
pat100001828
pat100001829
pat100001841
pat100001851
pat100001852
pat100001860
Update 2014-12
pat100001393
pat100001538
pat100001556
pat100001560
pat100001620
pat100001641
pat100001652
pat100001655
pat100001671
pat100001677
pat100001697
pat100001699
pat100001705
pat100001717
pat100001718
pat100001735
pat100001736
pat100001737
pat100001765
pat100001776
33
Update 2014-09
Update 2014-06
pat100001788
pat100001796
pat100001811
pat100001815
pat100001816
pat100001817
pat100002187
pat100002235
pat100002320
pat100001491
pat100001505
pat100001529
pat100001552
pat100001559
pat100001568
pat100001581
pat100001587
pat100001589
pat100001594
pat100001597
pat100001600
pat100001602
pat100001609
pat100001613
pat100001615
pat100001621
pat100001631
pat100001632
pat100001637
pat100001663
pat100001665
pat100001245
pat100001267
pat100001287
pat100001293
pat100001294
pat100001297
pat100001298
pat100001331
pat100001344
pat100001345
pat100001349
34
Update 2014-03
Update 13
pat100001354
pat100001361
pat100001371
pat100001378
pat100001379
pat100001409
pat100001427
pat100001428
pat100001431
pat100001478
pat100001481
pat100001488
pat100001515
pat100001551
pat100000468
pat100000497
pat100000498
pat100001093
pat100001134
pat100001149
pat100001151
pat100001156
pat100001163
pat100001176
pat100001178
pat100001183
pat100001185
pat100001195
pat100001223
pat100001224
pat100001230
pat100001246
pat100001259
pat100001272
pat100001295
pat100001323
pat100001324
pat100001351
pat100001353
pat100000781
pat100000921
pat100000931
35
Update 12
pat100000950
pat100000962
pat100000965
pat100000970
pat100000971
pat100000981
pat100000993
pat100001000
pat100001009
pat100001018
pat100001020
pat100001022
pat100001024
pat100001034
pat100001040
pat100001048
pat100001051
pat100001055
pat100001058
pat100001059
pat100001063
pat100001069
pat100001070
pat100001071
pat100001079
pat100001080
pat100001100
pat100001105
pat100001115
pat100001133
pat100001144
pat100000841
pat100000849
pat100000859
pat100000866
pat100000876
pat100000879
pat100000884
pat100000893
pat100000907
pat100000914
pat100000915
36
Update 11
pat100000917
pat100000932
pat100000951
pat100000952
pat100000953
pat100000956
pat100000964
pat100000982
pat100000667
pat100000670
pat100000675
pat100000676
pat100000683
pat100000685
pat100000691
pat100000696
pat100000704
pat100000709
pat100000711
pat100000717
pat100000718
pat100000721
pat100000728
pat100000731
pat100000736
pat100000737
pat100000738
pat100000739
pat100000741
pat100000746
pat100000747
pat100000748
pat100000750
pat100000755
pat100000762
pat100000764
pat100000777
pat100000778
pat100000779
pat100000780
pat100000787
pat100000792
37
Update 10
Update 9
pat100000793
pat100000810
pat100000815
pat100000816
pat100000823
pat100000824
pat100000830
pat100000836
pat100000848
pat100000857
pat100000860
pat100000862
pat100000870
pat100000882
pat100000582
pat100000584
pat100000588
pat100000591
pat100000592
pat100000595
pat100000603
pat100000605
pat100000607
pat100000613
pat100000619
pat100000624
pat100000625
pat100000627
pat100000631
pat100000634
pat100000642
pat100000647
pat100000648
pat100000653
pat100000655
pat100000666
pat100000669
pat100000673
pat100000678
pat100000715
pat100000452
pat100000476
38
Service Pack 2
pat100000488
pat100000489
pat100000493
pat100000494
pat100000508
pat100000512
pat100000522
pat100000528
pat100000535
pat100000536
pat100000539
pat100000541
pat100000543
pat100000545
pat100000547
pat100000548
pat100000555
pat100000558
pat100000562
pat100000563
pat100000566
pat100000569
pat100000581
pat100000587
pat100000615
pat100000314
pat100000363
pat100000367
pat100000384
pat100000389
pat100000394
pat100000395
pat100000398
pat100000407
pat100000408
pat100000413
pat100000417
pat100000418
pat100000426
pat100000428
pat100000430
pat100000432
39
Update 7
Update 6
pat100000435
pat100000437
pat100000441
pat100000446
pat100000447
pat100000448
pat100000452
pat100000455
pat100000459
pat100000529
pat100000540
pat100000277
pat100000288
pat100000290
pat100000291
pat100000295
pat100000300
pat100000301
pat100000307
pat100000320
pat100000321
pat100000323
pat100000326
pat100000330
pat100000331
pat100000332
pat100000333
pat100000337
pat100000345
pat100000357
pat100000358
pat100000385
pat100000208
pat100000213
pat100000214
pat100000215
pat100000217
pat100000220
pat100000222
pat100000223
pat100000227
pat100000229
40
Update 5
Update 4
pat100000232
pat100000233
pat100000234
pat100000237
pat100000238
pat100000241
pat100000246
pat100000251
pat100000262
pat100000264
pat100000266
pat100000278
pat100000279
pat100000281
pat100000284
pat100000286
pat000000294
pat000000297
pat000000302
pat000000304
pat000000305
pat000000362
pat000000386
pat100000123
pat100000139
pat100000156
pat100000163
pat100000164
pat100000167
pat100000171
pat100000178
pat100000181
pat100000188
pat100000201
pat100000206
pat100000097
pat100000102
pat100000104
pat100000107
pat100000112
pat100000115
pat100000118
41
Update 3
Update 2
Update 1
pat100000119
pat100000140
pat100000159
pat100000160
pat100000172
pat100000221
pat100000063
pat100000064
pat100000067
pat100000068
pat100000072
pat100000075
pat100000080
pat100000092
pat100000094
pat100000096
pat100000015
pat100000019
pat100000020
pat100000022
pat100000035
pat100000042
pat100000052
pat100000057
pat100000060
pat100000065
pat100000074
None
12 Appendix C Dependencies
This section contains information about changes in environmental dependencies. Some Updates will
require that certain modules are upgraded to a minimum version level, or that new environmental
requirements be met. As part of applying an Update, you must ensure that these module upgrades or
environmental changes are also applied.
Update
Dependency
2016-06
Search Engine 16.0.1 is included.
42
2016-03
Search Engine 16 Update 2016-03 is included.
2015-12
Search Engine 10.5 Update 2015-12 is included.
2015-09
2015-06
2015-03
2014-12
2014-09
2014-06
2014-03
13
12
Search Engine 10 Update 12 is included.
11
10
10
When Enterprise Library 10.2.2 becomes available, it must be installed

to avoid patches required for EL 10.2.1.
10
The optional Content Server Remote Search module is now included

in the core Content Server code base. An existing Remote Search
module should be uninstalled before applying Update 10. Existing
Remote Search processes will be preserved and continue to operate.
An optional ability to start a Remote Search process after creation has
also been added.
If you are using Oracle 11g, a minimum patch level of 11.2.0.3 should
be used to avoid known Oracle client performance and Oracle server
functional issues.
43
If you are using Enterprise Library, the EL 10.2.1 is the minimum

release level compatible with Update 9. Expected availability is
January 2013.
SP2
Search Engine 10 Update 8 must be installed.
SP2
If you are using Classifications, the minimum supported version is

Classifications 10.2.0.
If you are using Remote Search, you must install the latest Remote
Search patch for compatibility with Update 6 (pat100000259).
A Content Web Services security fix was made that requires Microsoft
.NET Framework 3.5 Service Pack 1 or later. Systems hosting the
.NET web services will need Microsoft .NET Framework 3.5 Service
Pack 1 or later installed. Applying this update without .NET Framework
3.5 SP1 or later installed will cause web services requests to fail.
Search Engine 10 Update 5 must be installed. Search Engine 10

Update 5 Release 2 is recommended.
Search Engine 10 Update 4 or 5 must be installed. Search Engine 10

This is the minimum Update level of Content Server to support

OpenText Spider 10.0.
This is the minimum Update level of Content Server required for use
with OpenText Federated Query Server 10.
CKEditor 3.1 was updated to CKEditor 3.5.3. CoP and Wiki modules
must be updated with the latest patches.
Search Engine 10 Update 3 or 5 must be installed. Search Engine 10

44
13 Appendix D Changed and Deprecated Features

An Update may change the behavior of existing features in Content Server for purposes of usability,
security, defect correction or compatibility with new features. In rare cases, a feature may be
deprecated or entirely removed. This section documents the known changes in behavior with each
Update that are not captured elsewhere in the release notes.
There are some Content Server 10.0 features that are known to be deprecated in future versions.
These include:
Enterprise Library Search Web Services API (replaced with Search XML API or the Search
REST API)
Filter Pack (replaced with Document Filters)
LAPI (Livelink API), replaced with Web Services or REST APIs.
Enterprise Process Suite module.
13.1 Feature Changes Update 2015-12

1. Database Correction. A new utility has been added to the Database Maintenance correction that
will identify orphaned items (those without a Parent ID) and move them into an Orphaned Item
volume. From there, they can be inspected and manually moved to a suitable location.
2. Auditing. A new auditing interest was added to control auditing the creation of attributes during
object creation. Previously, these events were always audited as attribute create/change events.
This feature was added to help manage audit record size.

1. Search API. The REST API methods for authentication and impersonation can now be used with
the XML Search API.
2. Search Results. To help differentiate renditions from other types in search results, rendition
results are now presented with a distinct marking icon.
3. Email Services. A change introduced in Content Server 2015-09 causes failure while browsing
Email Folder. Please apply Email Services 10.5.1 pat100002118 for Content Server 10 and
pat105000672 to correct this.

1. Logs. Support for rolling log files is now available with Log4J enabled. During startup, a set of
thread logs are captured and set aside that can be useful for support diagnostics.
45

1. Database Correction. A utility to add missing reflexive rows to DTreeAncestors for Volume
object types is included.

1. Search Index. Improvements to full text indexing of documents in Arabic, Danish and Norwegian
languages have been implemented. You may wish to re-index documents written in these
languages. Refer to the Search Engine release notes for details.
2. Database Correction. Several new utilities have been added that allow correction of common
errors detected by Database Verification.
3. Database Ports. Port numbers can now be specified when connecting to a database.

1. Categories. A new option was added to the category Apply to Sub-Items page. If "Replace" is
selected for a category that is to be applied to sub-items, then the values of the attributes for that
category on the parent item will be applied to that category as it exists on sub-items.

1. Search API: The XML Search API has been extended to allow executing a saved search
query.
2. Search Quotes: The construction of search queries has been relaxed to allow a wider range
of double quotes in place of the basic ASCII double quote. This allows queries created by
MS Office (which uses smart quotes) to be cut and pasted into Content Server search
dialogs.
3. Search Cache: The Search Federator can now cache search results, improving performance
for long operations such as Collect all search results.

1. LAPI: As a result of the security fix for LPAD-35969, the default settings associated with the
ListNodes SQL injection mitigation model have changed. The following configuration settings
should be deleted from the opentext.ini file if they already exist, unless they have been
manually configured by an administrator:
ListNodesSettingSaved
ListNodesTablesWhiteList
ListNodesQueryBlackList
EnableListNodes
46
If the ListNodes function is accessed, the new default settings will be automatically configured in
Content Server.

1. SysReports: No longer include information about the temp, tmp, index and logs directories in
order to reduce the likelihood of file locking conflicts.
2. Documentation: As of Content Server 10.0.0 Update 13, the Online Help and PDF Guides
are no longer updated for Content Server 10.0.0 update releases. For 10.0.0 Update 201403, please refer to the 10.5.0 Update 2014-03 documentation folder on the OpenText
Knowledge Center.
3. Extractor: Several optimizations have been implemented. Client-side cursors are no longer
used. Email objects now use the same optimizations as documents, which enables metadata
updates without obtaining and re-indexing the content of the email.
4. DCS: By default, DCS will now stop processing input IPool messages if the number of
messages in the output IPool directory exceeds 100. The objective is to reduce the likelihood
of unlimited IPools being generated if the Index Engines are stopped in a typical environment,
which can consume all disk and/or reduce indexing performance. This can be disabled by
setting the value to 0. In the dcs.ini file [DCSIpool] section:
maxoutputipoolmsgs=100

1. Search Options: Several configuration settings in the opentext.ini file for search options are
now stored in the database. A new corresponding administration page allows these values to
be managed in the admin interface. The deprecated settings in the [SearchOptions] section
of the opentext.ini file are: (SFWK-4150)
truncation=x
wantResultLocationPath=TRUE
pathTruncation=80
2. Maximum Search Templates: The maximum number of search templates that a user may
have is moved from the opentext.ini file to the database. The Reset Search Templates
administration page is renamed to Manage Search Templates and links to a new Configure
Search Templates Administration. The control for search forms and search result templates
are now independent. For new installations, the default maximum has been increased from 5
to 20. If a user encounters this limit, the Save as dialogs now prevent creating a new item
and show the reason. (SFWK-4345)
3. Ability to exclude inherited columns from a given container and all of its descendants. This is
done on the Columns Properties tab for a given container. Similarly, a container can use the
same mechanism to "re-include" an inherited column that was excluded by an ancestor
container. In addition, multiline text attributes can be used for custom columns. (LPAD-31910)
47
4. System Attributes Advanced Search: New search criteria on the Advanced Search page
are now available for MIME type and Content Type (Subtype). The default value is now
blank, which means the attribute will be omitted from the query, and is similar to Content
Server 9.7.1. Two special values are added to the options:
Any which requires the field to be defined

No Type Defined which requires that no value be defined for the field.
(SFWK-4416)
5. Tabular Search Result Width: In a tabular search result, if there is no special handling for a
column, then a new limit of 150 pixels for the column has been implemented, which prevents
the width of pages from becoming arbitrarily wide. This can be modified in the CSS file if
necessary. (SFWK-4419, SFWK-4408)
6. Search Bar without Text: In Full Text query mode only, you can now initiate a query from the
search bar without entering a value in the text field. This is equivalent to entering an asterisk
( * ) as the search term. This change allows queries to run using just the constraints in the
expanded search panel (for example, recent dates, slices, or file types). (SFWK-4326)
7. Target Browse Appearances: The appearances have been removed by default from the
Target Browse dialog. A new admin control is available on the Configure Container Options
administration page to enable appearances. (SFWK-4451)

1. Schema Change: The Dtree table was renamed to DtreeCore, and a new View called Dtree
was created. The View is based on all rows and columns in DtreeCore that have the Deleted
column marked as 0. Operations that had previously updated the fields in DtreeCore directly,
such as ExAtt1, ExAtt1 and ExtendedData, will pass through the View directly and update the
underlying table, which means no code changes are required.
2. Extractor Configuration. The Extractor iterator responsible for indexing Initiated Workflows
now has a separate configuration entry in the Extractor General Settings admin page. This
allows Initiated Workflow indexing to be paused or completely disabled. The Maximum Items
Per Extraction now applies to each type of indexing operation instead of the total of all
indexing actions. This change in behavior prevents potential starvation of indexing requests.
(SFWK-3445)
3. Search API. The facets parameter has been extended with a new possible value of user,
which applies the users enable/disable preference for including facets in the query. This
extends the existing true/false options. (SFWK-3947)
4. Collection Configuration. The settings previously stored in the opentext.ini file for
Download Collection as a Spreadsheet are now stored in the database. During the upgrade
to Update 11, the existing values from the opentext.ini file on the system running the upgrade
48
are moved to the new database location. There is a new General Settings administration
page for Collections that allows configuration of these values. (SFWK-3739). The deprecated
opentext.ini settings are:
largestUncompressedSpreadsheetInKB
maxItemsPerSpreadsheet
maxOperationSize
5. Region Settings. The search region settings (region map) storage has been moved from a
file stored in Content Server to tables in the database. This change reduces errors if the
region map file cannot be accessed, and improves performance for making updates to the
region map. During the upgrade to Update 11, the existing region settings are converted to
the database form. The region map file is not deleted; by leaving it in place, if the upgrade
needs to be re-run, it will still convert properly. (SFWK-1083)
6. Database Verification. Changes have been made to reduce the number of false positive
errors reported with ChildCounts. ChildCount checking is no longer performed on noncontainer objects. In addition, ChildCount checking is not performed on the Workflow
Volume. Internally, structure was also added to allow other modules to register themselves
for exemption to ChildCount verification. (LPAD-24283)
7. Module Upgrades. The upgrade process has been modified to reduce steps needed when
upgrades to the database schema are required by both Content Server core and optional
modules. The upgrade now applies the schema changes from both core and modules at the
same time, eliminating the need to use a dummy database in some scenarios. (LPAD-31216)
8. Search Relevance. The configuration page for adjusting search relevance now allows
spaces in values for the Object Type Rank field. This supports the new use of TEXT fields in
the search engine for relevance scoring, most valuable with OTFileType as the relevance
field. (SFWK-4101)

1. Extractor Configuration. Many of the Extractor configuration settings have been moved out
of opentext.ini into the KINI table in the database, and managed through Content Server
administration page Set Extractor General Settings. The following settings are no longer
read from the opentext.ini file:
[LivelinkExtractor]
ContentReferenceTempPathname=
enableACLExtraction=
ExcludedLocationNodes=
ExcludedLocationNodes_<n>=
ExcludedNodeTypes=
ExcludedVolumeTypes=
IndexRenditions=
49
MaxItemsInObject=
maxipoolsizeMB=
MaxItemsInTransaction=
MaxItemsPerExtraction=
MaxVersionsToExtract=
UpdateCookie=
UseContentReference=
When upgrading from previous versions of Content Server, the Extractor settings from the
opentext.ini file on the Content Server instance running the upgrade are migrated to the
database.
Current settings cannot be preserved automatically from versions prior to Livelink 9.7.1
Update 3. The settings must be entered manually on the administration pages.
Note that the current Electronic Signatures module modifies Extractor opentext.ini
settings during a new installation. These changes are ignored, and should be updated
using the admin page.
(SFWK-3689)
2. Document Management: When creating a shortcut or generation using the Make Shortcut or
Make Generation option on an object's Functions menu, the name of the new object will be
the same as the object that it is created from by default. (LPAD-28316)
3. Workflow Map Attribute Indexing. Within the Workflow Map attribute creation and edit
page, there is a setting called Show in Search. In prior versions of Content Server, all
Workflow Map attributes were indexed, and this setting affected whether the attribute could be
made searchable. Due to the large number of infrequently used metadata fields this may add
to the index, this setting has been changed. When checked, it now means add the field to
the search index, and the default for new attributes has been changed to unchecked.
These regions have the form WFAttr_xxxxxx on the Regions page of the Enterprise Search
Manager. (SFWK-3813)
4. Best Bets Configuration. The following configuration settings for tuning Best Bets and
Nicknames were moved from the opentext.ini file to the KINI table in the database, and are
now managed on the Best Bets administration page:
BestBetsMinStemLength=
BestBetsMaxTerms=
NicknameMaxTerms=
NickNameWithBestBets=
During upgrade, the existing settings from the Content Server instance on which the upgrade is
run are preserved. (SFWK-3705)
5. Multiple Custom View Search Forms. If there are multiple Custom View Search forms
defined for a single folder, Content Server will now allow the user to select from the available
search forms. (SFWK-3828)
50
6. Search Index Verifier. The OTURN field has been added to the search index verifier output
reports. (SFWK-3156)
7. Removal of Appearances in Search Dialogs. The pop-up and modal dialogs related to
search features were changed to remove Appearance information in 18 dialogs.
Appearances often allowed users to navigate away from the intended purpose of the dialog,
or consumed unexpected space in dialogs where space is limited. The Multi-Field sort
selector was converted to a modal dialog instead of a pop-up window. (SFWK-3740, SFWK3896)
8. 0-Byte Files. Content Server now allows content files with a size of zero to be added and
stored within the system.
9. Delete Performance. A number of optimizations were incorporated that improve the
performance of delete operations. Although exact benefits vary by system, in a typical
environment the delete performance is approximately doubled.

1. Search Query Enforcement. The construction and application of search queries has been
changed in two ways in Update 9 to make Content Server more compliant with litigation
support search applications. These are related to proximity and partial query correctness.
The PROX operator is valid only between basic keywords or phrases. Previously, the PROX
operations were converted to AND operations for other cases. For example, the query: Hors*
PROX[5] (grey or white) was changed to Hors* AND (grey or white). Content Server has been
changed to return a search query error for these situations. If you are currently using the PROX
operator in saved queries which would have been converted to an AND operator, these saved
queries will now fail with errors and need to be updated. A query such as Horse PROX[5] white
knight would be unaffected, since proximity searches between simple terms and phrases are
supported. (SFWK-3544,SFWK-3546, SFWK-3663).
The second change tightens rules around query correctness. In the past, if at least one
component of a search query was correctly constructed, the correct elements would be used in
the query. Now, if any of the components are incorrect, an error is returned. This change may
cause existing saved queries or search appeared to be working correctly to return errors. (SFWK3757)
2. Search Result Style Preferences. A style preference for displaying search results is now
saved in the user preferences. If My Current Style is selected in search templates, then this
preference is used. The effect from a user perspective is that changing the style from the
drop down list on the search results page is sticky, and will be used for the next search query.
Note that the upgrade process will change the default Admin search template and all default
user templates to My Current Style. Other templates with existing styles are unaffected.
3. Save as Search Form. The location of the Save as Search Form function on the search
results display page has been moved from the Select Display Style pull down list to the
Search Tools pull down list.(SFWK-3569)
51
4. Memory Constraints. It was determined that Java was allocating far more memory to the
Update Distributor and Search Federator processes than required. For new installations,
these now default to 256 MB for Enterprise Data Sources and 64 MB for other types of Data
Sources. For existing installations, we recommend adding these memory constraints as
command line options in the administration pages for these processes. (SFWK-3604)
5. Boolean Search Selection. The control for selecting a value for a Boolean field on search
forms has been modified, which is most frequently used with Categories. Previously, this was
a check box for True or False. The new implementation is a pull down menu, which covers
seven possible values (SFWK-3470):
(blank) ignore, do not include in search query
True
False
Defined must exist, may be True or False
Undefined must not exist
Not True undefined or false
Not False undefined or true
6. IPool Quarantine. The quarantine feature for unreadable IPools in DCS is now implemented
for all input IPool readers. Each IPool directory now has an _failure subdirectory, into which
bad IPools are moved. The last 100 failed IPool messages are retained on a rotating basis in
the _failure directory. This is no longer a configurable DCS feature. IPools in the _failure
directory can be used to diagnose problems in DataFlows. (SFWK-3682)
7. Extractor Improvements. The Extractor is the component of the search system that
generates search indexing operations. There are many changes to the Extractor in Update 9
to improve performance and correct defects. Some of the notable items are:
-
Optimization to reduce redundant metadata indexing operations

Reduce the likelihood of stalling on large gaps in data IDs
SQL performance optimizations
Implementation of log levels
Performance improvement at lower log levels
Administration page for setting the log level
Handle new Ntype 12 operation (Touch)
In addition, the Enterprise Library Extractor has been modified to be compatible with these
changes, and is NOT compatible with existing versions of Enterprise Library. If you are using
Enterprise Library, then you must upgrade to a minimum of Enterprise Library 10.2.1 with
the latest patches, expected January 2013.
13.14 Feature Changes Service Pack 2

1. Themes have been removed from search results, and replaced with Search Filters. Filters
provide more capabilities, but are not an exact superset of Themes. Themes are removed
52
from the display of search results, from the search option display styles, and from the Search
API.
2. Search region display names are no longer stored in saved search templates. Changes to the
name of a search region are therefore now reflected in any user interfaces that display the
region name. Existing saved templates are unaffected; the change only affects new search
templates that are saved, or existing templates that are updated. Saved search templates
include Search Forms, Custom View Search Forms, Saved Queries, etc.
3. Within the Document Conversion Server, the feature to analyze content and attach a
metadata value within the OTContentLanguage region is now enabled by default. This has a
small impact on DCS performance and the size of the index. If your environment is sensitive
to these factors, you can disable this feature in <OTHOME>/config/custom_dcs.ini file:
[LanguageID]
detectLanguage=FALSE
4. LAPI searches with an empty where clause now return an error message. In previous
releases, this was interpreted as a search for all (or *).

No feature changes for Update 7.

1. The TotalResults field in the XML Search API has been removed. There are alternate
values in the API that are more accurate and should be used instead. Contact OpenText
Customer Support for a workaround if this change impacts your applications. (SFWK-2640)
2. The EncodeCookies setting in the system configuration could be used to turn off encryption of
Content Server cookies. This functionality has been disabled. (LPAD-27523)
3. Server thread logs and System Report output now show the current Content Server Update
number, as it appears in the config/update.ini file.
4. Domains functionality has been enabled for Content Server 10.0.0.
5. Content Server will attempt to reconnect to the database after losing a database connection.
A new setting, DBConnRetries, the opentext.ini file in the [General] section allows you to
specify the number of retries. The default value is 5.

1. Temporary File Names. The following Web Service methods create temporary files before
returning the contents to the client: DocumentManagement.GetVersionContents(),
DocumentManagement.GetRenditionContents(), and XmlService.ExportXml(). The temporary
53
files that are created are changed and now use a filename that consists of a set prefix of
cws_ followed by a random string, created in the OS temp directory (LESAPI-1143)

1. RMI Deprecated. Within Search Engine 10, the ability exists to use either RMI communication or
direct socket communication between components. Starting with Update 4, Content Server will
use direct socket connections instead of RMI. The search process otrmiregistry is no longer
used. This change will reduce thread use on large search indexes. Although specific search
transactions may be slightly faster or slower, in general there is no discernible performance
difference. If upgrading from a previous version, the database upgrade process will make any
necessary configuration changes automatically.

1. Search Term Hit Highlighting. The default highlighting mechanism for the search results
page has been changed to bold characters instead of highlight characters. If highlighting
is preferred, it can be restored by adding the following to the [HitHighlight] section of the
opentext.ini file:
left2=<SPAN ID=HITBG%d CLASS=hh style=background: #C7E8F7;>
2. Search Form Lists. The behavior of pull down lists in advanced search forms has been
changed, which affects searching against regions such as dates or category attributes. The
previous behavior was a default value of any, which requires that a value in the region
exists. A blank value has been added as the new default value, which omits the region from
the query entirely. This is more consistent with text fields, where a blank value is omitted from
the search. For customers upgrading from Content Server 9.7.1, the new blank value is
functionally similar to the 9.7.1 use of the any value as the default. CS 9.7.1 does not
support the concept of the new any value (require that a value is defined in the region).
(SFWK-1452)
3. Util Function Deprecated. $WEBLL.WebUtils.GetMinificationSuffix() has been deprecated
and replaced by $WEBDSP.RequestHandlerUtils.GetMinificationSuffix(). This is to prevent a
dependency of WEBDSP on WEBLL that was problematic for OpenText Remote Cache
Server. (LPAD-25132)
4. Search Disk Retrieval Storage. If you have used the search.ini or search.ini_override files to
configure Disk Retrieval mode directly in a previous installation of Search Engine 10, you
should remove these settings and configure this mode through the partition management
pages in Content Server.
5. Forms Indexing. The indexing of forms objects has been disabled by default for new
installations of Content Server 10. This applies to object SubTypes 223, 231 and 226. The
Forms module allows creation of arbitrary region names, and it was determined that
customers are not naming regions to prevent collisions with important system metadata.
54
Enabling or disabling indexing of Forms can be done by editing the ExcludedSubtypes value
in the [LivelinkExtractor] section of the opentext.ini file.
6. Search Metadata Settings. For new installations, new default values for automatic partition
mode switching are being used. The new values are much more conservative, and better
reflect the historic metadata memory use patterns that most customers follow. Existing
customers who already have Search Engine 10 installed may want to edit their percent full
settings to the new values on the Partition Mode administration pages:
Rebalance 80%
Stop Rebalancing 77%
Update Only mode 70%
If you are making these changes and your current indexes are already above these values,
rebalancing may occur and/or adding more partitions may be necessary.

1. Admin Password. When installing Content Server 10.x, the Admin User password defaults
to livelink. During the installation process, the user is provided with a reminder that For
security reasons the Admin [User] password should be changed from the current default
value and that the default Admin User password can be changed by clicking on the
provided Admin profile page link. If the password is changed, it must conform to current
password security settings (e.g., the updated password must contain at least one [numerical]
digit).
2. Account Locking. On a new install of Content Server 10.0.0, the User Accounts Locking
setting is now turned on by default. The number of attempts is set at 5.
3. Browser Auto-Completion. On a new install of Content Server 10.0.0, browser autocompletion is switched off by default. The Administrator will now be required to turn on the
browser auto-completion should this functionality be required.
4. URL Object Creation. When installing Content Server 10.0.0, URL object creation is now
restricted by default. The setting can be turned on within the Administrator Object and Usage
Privileges page.
5. Trace Files. Trace files are now always generated upon encountering a script crash,
regardless of the Debug=# thread log setting. If the generation of trace files is not desired,
add the setting wantTrace=FALSE to the [options] section of the opentext.ini file. (PYRO-97)
6. Short Link Generation. Short links will now be generated using the nickname of the object
in the short link, unless the nickname contains high-bit UTF-8 encoded characters, in which
case the short link will use the DataID of the object. (LPAD-17992)
55

1. Domain Functionality. Domain functionality is deprecated for the Content Server 10.0.0
release.
2. Java Modules. The following Java Modules have been removed from Content Server:
My Home Java Module
Search Bar Java Module
3. LAPI. LAPI is deprecated in Content Server 10.0.0. This means that this API should be
avoided because it may be removed completely in future versions of Content Server. Content
Server 9.7.1 introduced the SOAP-based Web Services that cover the same functionality of
LAPI. Future Content Server integrations should be implemented using these Web Services.
Legacy integrations should be refactored to use the Web Services before moving to a future
version of Content Server.
56
14 Appendix E Security Fixes

OpenText has guidelines that categorize the severity of security issues. The known categorized major
security fixes that have been included in Updates are shown in the table below.
57
Fix Update
Reference
Description
2016-06
SFWK-7107
Potential CSRF vulnerability in Recommender module
2016-06
PYRO-2422
UTF8 encoding can be lost when using llisapi.dll when the system is
under load
2016-06
LPAD-46806
Potential XSS vulnerability related to permissions. This issue is now

fixed.
2016-03
LPAD-41978
Added improved Clickjacking protection.
2016-03
LPAD-43578
Secure Request Token missing from a specific function. This has

been fixed.
2016-03
LPAD-46806
Potential XSS vulnerability in permission handling. This has been

fixed.
2016-03
LPAD-46810
Update OpenSSL libraries to address known vulnerabilities. NOTE:

IMFILTER uses the OpenSSL version on the system. This version of
OpenSSL should be updated to 0.9.8zh.
2015-12
LPAD-34980
Potential information leak related to session management. This has

been fixed
2015-12
LPAD-44616
It is possible to construct a URL in such a way that can cause a

Content Server thread to abnormally halt execution and display an
error page. This has been fixed.
2015-12
LPAD-44782
Due to browser caching, clicking the Back button in a browser after

logging out can expose the last-viewed Content Server page.
Appropriate messaging has been added to the logout page to
highlight the importance of closing the web browser to ensure data
security.
2015-12
LPAD-44785
Project Templates that were created from a Project may not include
permission information for the contents of the Project when the XML
is generated. If you are creating a new Project from one of these
Project Templates, the contents of the Project will just inherit the
permissions of the Project itself.
2015-12
LPAD-45012
The document owner could potentially change when moving objects

between volumes. This has been fixed.
58
2015-12
LPAD-40138
Potential script crash related to URL construction. This has been

fixed.
2015-12
LPAD-43745
Potential script crash related to notifications. This has been fixed
2015-12
LPAD-44877
Applying Patch pat100002002 breaks 1 day Password Expire notice.
2015-12
LPAD-44979
Potential script crash related to version control.
2015-12
PYRO-1585
Parsing of socket streams hardened against possible attack vectors.
2015-12
SFWK-6788
Potential script crash in agents.
2015-12
SFWK-6860
Potential script crash in Search Index Verification.
2015-09
LPAD-43816
Potential XSS vulnerability in workflow editing.
2015-09
LPAD-42883
In some instances, a Distributed Agent may crash during execution

of a task if its input data is undefined.
2015-09
LPAD-43816
A cross-site scripting (XSS) vulnerability existed in the ll.expbuiler2

request handler.
2015-09
LPH-996
It is possible to generate a URL to Content Server eLink functionality

in such a way that arbitrary JavaScript can be executed in a user's
web browser.
2015-09
PYRO-2055
A method exists for a sysadmin to modify their login name.
2015-09
PYRO-2067
The potential exists for indefinite browser redirection for a user that
is not logged in.
2015-06
CSARC-845
OpenSSL has been updated to 0.9.8zf
2015-06
LPAD-41812
Login error messages make usernames susceptible to enumeration
59
2015-06
LPAD-41812
For security reasons, Content Server will now only tell a user that
their log-in privilege is disabled if they enter a correct username and
password combination. If their log-in is disabled and an incorrect
username and/or password is entered, the user will only be informed
that an incorrect username or password has been entered.
2015-06
LPAD-41880
Cross Site Scripting Security Vulnerability When Configuring Tabs
2015-06
LPAD-41880
It was possible to construct a URL tied to Personal Menu options in

such a way that arbitrary JavaScript could be executed in the client
web browser.
2015-06
LPAD-42551
Potential XSS when using Dynamic Views.
2015-06
LPAD-43551
It was possible to construct a Dynamic View browse URL in such a

way that arbitrary JavaScript could be executed in the client web
browser.
2015-06
LPAD-42964
Potential XSS Vulnerability with Workflow.
2015-06
PYRO-1592
If the Upload directory is not defined, users can add files from the
operating system into Content Server.
2015-06
PYRO-1982
An API feature allows X-Domain groups to be created by any user.
2015-06
PYRO-1994
An API feature can be used to create a folder even if the user only
has SeeContents permission.
2015-06
PYRO-2038
2015-03
LPAD-38418
Content Server 10.0 uses jQuery 1.3.2 which is susceptible to

Cross-Site Scripting.
2015-03
LPAD-39882
Audit events wrongly recorded for non-system admin user when

'force auditing of all events performed by system administrators' is
set.
2015-03
LPAD-40816
In some instances, it is possible for information about the Content

Server configuration to be displayed to end users when reporting a
file upload error.
Potential script crash in DAPI callbacks when requesting too many

program sessions.
60
2015-03
LPAD-41489
Cross-site Scripting Issues in Workflow have been fixed.
2015-03
LPAD-41837
Improve Admin user login audit.
2015-03
PYRO-1375
Ensure that missing providers are reported as an error during file I/O
operations.
2015-03
PYRO-1885
Content Server service crashes when it fails to open a file.
2015-03
SFWK-6228
Harden OTAdmin.BrowseDir prototype.
2014-12
LPAD-20249
It was possible to construct a URL which referenced the "LL"

request handler in such a way that could crash a Content Server
thread, which generated a trace file on the server.
2014-12
LPAD-36119
Secure request tokens that are used to prevent cross-site request

forgery (CSRF) attacks are being submitted as parameters via HTTP
get when configuring tabs for Personal Assignments. Best practice
requires these parameters to only be submitted via POST.
2014-12
LPAD-40109
Login to the Admin pages does not respect the login via GET
security setting.
2014-12
LPAD-40126
A cross-site scripting (XSS) vulnerability exists in the metadata

language Admin pages. Additionally, some error messages on this
page disclosed information that could assist with a SQL injection
attack.
2014-12
LPAD-40135
It was possible to create a URL to the ll.iconpicker request handler

that caused a Content Server thread crash, which generated a trace
file on the server.
2014-12
LPAD-40266
An error existed in the VersionReferences, EditConfig, and Outline

actions. Incomplete URLs sent to Content Server could cause a
thread to crash and generate a stack trace. This error could be used
to instigate a denial-of-service attack.
2014-12
SRCH-3759
View as Web Page for text documents has been hardened to

prevent potential XSS attacks. Some loss of formatting viewing
HTML files may occur.
61
2014-09
LPAD-38727
Potential cross-site scripting (XSS) vulnerability in Appearances.
2014-09
CST-362
After applying PAT100001294 for an SSO forms authentication issue

(CST-351), WebDAV ActiveX authentication fails.
2014-09
LPAD-39867
If the upload directory is offline or out of space, Content Server will

no longer create a zero byte file. Files are not uploaded and an
HTTP 500 error is returned.
2014-09
LPH-740
A trace file will no longer occur when eLink agent processes a

workflow under certain conditions.
2014-06
LPAD-36900
A cross-site scripting (XSS) vulnerability existed within the Content

Server Text Editor.
2014-06
LPAD-37379
It was possible for a user to access information about users in other

domains on the same Content Server system through URL
manipulation.
2014-06
LPAD-37267
Potential security issue existed when trying to execute arbitrary

JavaScript code within a client web browser.
2014-06
LPAD-36866
When creating a Project from a Project Template, if the web browser

does not send the optional HTTP_REFERER header with its
request, then Content Server will return an error and a stack trace
will occur.
2014-06
LPAD-37921

Server Project Creation Wizard.
2014-03
LPAD-35969
Potential cross-site request forgery (CSRF) in built-in ListNodes

function.
2014-03
LPAD-36364
Several cross-site scripting (XSS) issues in the Workflow and

Workflow Designer pages.
2014-03
LPAD-36318

Server browse page.
2014-03
SIESTA-445
When a Category CSNode retrieves a set-based custom attribute, a

trace file was generated.
2014-03
SIESTA-474
Potential security issue in REST API document upload.
62
2014-03
SIESTA-514
Users must have the See Contents permission on an object to

retrieve its metadata through a REST API call. If they have only the
See permission, the REST API will return an error. Previously, only
the See permission was required.
13
LPAD-36016
This feature provides added security to ensure that certain object

types cannot be deleted by a user through an API. This change also
ensures that only certain object types can be deleted by a user with
Administrative permissions through an API.
13
LPAD-35570
The parameters that are selected before the Audit Log is purged are
no longer ignored. When specific parameters are set, only the
selected items are purged from the Audit Log.
13
SFWK-4843
Potential stack trace when creating a disk image from Collections.
13
LPAD-34555
Performing some actions on a usage privilege may not get audited.
13
LPAD-33681
Security issue allows users without the user administration privilege

to modify group membership
13
LPAD34727,
LESAPI1693
Potential security issue with user password change.
12
LPAD-34758
Path traversal potential weakness in XML Export.
12
LPAD-32916
Potential cross-site request forgery (CSRF) in login page. A new

security setting has been added to the Configure Security
Parameters page to address this issue.
12
LPAD-34429
Potential XSS vulnerability in administration page.
12
LPAD-34527
XML Export may crash processing a News item.
12
SFWK-4329
Potential denial of service (script crash) in Search Administration.
12
SFWK-4347
Potential XSS vulnerability in Search API.
12
SFWK-4376
Potential XSS vulnerability in Advanced Search.
63
12
SFWK-4377
Potential XSS vulnerability in Search API.
12
SFWK-4384
Potential XSS vulnerability in Search Administration.
12
SFWK-4411
Enhance security permissions around Personal Search Templates

folder.
12
SFWK-4452
Enhance security permissions around Update Distributor and

Search Federator configuration.
12
SFWK-4502
Potential XSS vulnerability in Advanced Search.
11
CST-300
If OTDS integration is enabled and Web Server Authentication is

disabled, a successful authentication request can be made by
modifying the Content Server URL.
11
CST-302
A non-authenticated request made to Content Server through a

modified URL can result in a script crash for Content Server.
11
LPAD-30891
A script crash was generated when showing the Workflow Attributes

pages.
11
LPAD-32182
A script crash was generated when stopped Workflow instances in

high volume scenarios were deleted. This issue is resolved.
11
LPAD-32312
A cross-site scripting (XSS) vulnerability in Content Servers

Workflow pages has been addressed.
11
LPAD-32586
Potential crash in XML Import while importing very large files (over
100 MB).
11
LPAD-32856
A cross-site scripting vulnerability exists in the dialog used to edit

category data during object creation. An attacker may exploit this
vulnerability to execute arbitrary JavaScript code and compromise a
users account information.
11
LPAD-21192
When creating or updating user accounts while Content Server

Directory Services (CSDS) is installed and configured for Integrated
Windows Authentication, passwords will not be verified for
compliance with requirements as configured in the system password
settings configuration.
64
11
LPAD-32949

Expression Builder for My Workflow Settings assignments has been
addressed.
11
LPAD-32092
The Users with the can create/modify users privilege can set
password expiration on individual user accounts check box was
added to the Password Settings page. This setting allows a System
Administrator to grant users permission to change the expiration
date for passwords of individual users, which overrides the systems
password expiration policy. In previous releases, no special
privileges were required to perform this override. Also, if this setting
is enabled, the ability to make individual users passwords never
expire is restricted to User Administrators. Individual user password
expiration settings can still be configured by users with System
Administration privileges.
11
LPAD-31110
Content Server can be configured to restrict access to its Admin

account by the IP address of the request. This restriction is now
extended to the [email protected] account which is used for
administration of OpenText Directory Services (OTDS).
11
LPAD-32950

Expression Builder for My Workflow Settings assignments has been
addressed.
11
LPH-913
eLink was not correctly parsing emails that contained nested

multipart/mixed parts. This parsing was corrected. Multipart/mixed
attachments contained within a multipart/mixed attachment will now
be ingested properly.
11
SFWK-3987
A cross-site scripting (XSS) vulnerability while logged in as Admin on

an administration page has been addressed.
11
SFWK-3988
A cross-site scripting (XSS) vulnerability while logged in as Admin on

an administration page has been addressed.
11
SFWK-4045
A cross-site scripting (XSS) vulnerability on search results page has

been addressed.
11
SFWK-4068
Data source delete script crash if nodes listed in the Data Source
Folders extended data no longer exist.
65
11
SFWK-4088
A cross-site scripting (XSS) vulnerability in search result sorting has

been addressed.
11
SFWK-4091
A cross-site scripting (XSS) vulnerability in search results has been

addressed.
11
SFWK-4109
A cross-site scripting (XSS) vulnerability in Recommender has been

addressed.
11
SFWK-4140
A cross-site scripting (XSS) vulnerability in Search API has been

addressed.
11
SFWK-4141
A cross-site scripting (XSS) vulnerability in advanced search has

been addressed.
11
SFWK-4156
A cross-site scripting (XSS) vulnerability in search configuration has

been addressed.
11
SFWK-4202
A cross-site scripting (XSS) vulnerability in search results has been

addressed.
11
SFWK-4294
Increase security validation around access to several search

configuration objects.
10
JALA-319
Improper use of the DAPI.AddRendition Oscript function could

cause Content Server to crash.
10
PYRO-843
Potential buffer overrun issues were found in Kernel and LLEngine.
10
LPAD-20387
Certain error messages resulting from zipping and downloading files

included server-side file path information. This information is now
removed.
10
LPAD-30448
Potential SQL injection vulnerability.
10
LPAD-31236
It was possible to initiate a request to the Content Server

administrator login request handler with a set of parameters that will
cause a stack trace, which could cause the server to leak memory.
10
LPAD-31306
Autocomplete should not be enabled for Content Server

Administrator Log-in.
66
10
LPAD-31379
When configuring additional node attributes in Content Server

administration, a cross-site scripting (XSS) vulnerability existed on
the page used to configure valid values for a popup attribute.
10
LPAD-31380
When configuring additional node attributes in Content Server

administration, a cross-site scripting (XSS) vulnerability existed on
the page used to add a new additional node attribute.
10
LPAD-31382
A cross-site scripting (XSS) vulnerability exists in the Change Owner

request handler.
10
LPAD-31428
Permissions to browse the Facets Volume and Facet Folders were

not correctly restricted to Knowledge Managers through Target
Browse.
10
LPAD-31434
Potential script during Physical Objects module install.
10
LPAD-31620
Potential script crash in authentication
10
LPAD-31800
The admin.index page is not accessible if the encrypted form of the

admin.index password contains a /
10
LPAD-31810
A cross-site scripting (XSS) vulnerability existed in the filter when

viewing the contents of a container (for example, a Folder).
10
LPAD-31858
A Denial of Service attack vector existed within Workflow features.
10
SFWK-3593
Potential script crash looking for words using the search bar.
10
SFWK-3749
Potential script crash on Advanced Search page
10
SFWK-3899
Potential script crash with malformed Search API query
10
SFWK-3978
A cross-site scripting (XSS) vulnerability in search administration

pages
10
SFWK-3995
A cross-site scripting (XSS) vulnerability in prospector feature
10
SFWK-4015
Admin Server may core dump on Red Hat Linux.
LPAD-16620
Web administration cookie (AdminPwd) must follow cookie expiry

settings.
67
LESAPI1398
GetWorkItemDetails now returns only the forms associated with the

Workflow step, instead of all forms associated to the Workflow Map.
LPAD-30310
A potential Denial of Service attack vector related to Virtual Folders

has been mitigated.
LPAD-29684
When the Days before password expiry password setting was

updated, the database update would override any requirements to
change their password at first login.
LPAD-30420
When moving or copying with an Item Handler step that uses

Synchronize Container Contents, and one of the contents has a
single quote in the name, the following error would occur: Error
performing Workflow operation. [Error listing the children for item
item name.]
LPAD-30233
Stack crawl in Personal Assignments in ManageTabs A wrong

argument type was specified.
LPAD-23592
The set of characters that can be used for Nicknames when applied
to objects is restricted. These restrictions are only enforced in the
client, and it was possible to bypass the restrictions by sending a
special request to the server.
LPAD-30903
Potential for data loss or corruption when uploading large files

through the servlet over a slow network connection.
LPAD-30562
A change was made to the password expiration policy. Prior to

Update 9, if an administrator set a specific expiry date for a user
password, then changing the days before password expiry setting
would recalculate that expiry date. This issue is now fixed, and a
change to the days before password expiry setting does not affect
expiration dates manually set for a user by a user administrator.
LPAD-30984
Personal.Assignments delete actions should include the Secure

Request Token. To enable this feature, a system administrator must
select the check boxes on the Security Configuration administration
page.
68
LPH-888
When eLink encounters a message that exceeds the configured

maximum size, it discards the message without notifying the sender.
This issue is resolved, so that an email is sent to the originator of the
discarded message to notify them of what happened.
LPAD-30300
If the Trusted Referring Websites security setting is left blank,

validation is still attempted and may block legitimate requests.
SFWK-2987
Potential script crash with empty search results.
SFWK-3198
Delete permissions needed to return minor version in search results.
SFWK-3390
IPool log files can accumulate and consume all disk space.
SFWK-3413
ActualCount value in ListDescriptions API does not respect user

permissions.
SFWK-3673
Potential script crash in search administration.
SFWK-3729
Potential script crash downloading a Collection as a Spreadsheet.
SFWK-3733
Potential script crash in search administration.
SRCH-2646
Potential data loss with Enterprise File Store when an unexpected

exception occurs in Document Conversion Server. This problem
exists in Update 7 only.
SP2
LESAPI1340
Creating users through the Content Web Services (CWS)

MemberService.CreateMember() method did not set the new users
password expiration date. This has been fixed so that creating new
users via the CWS interface now sets the new users password
expiration date according to the password expiration policy.
SP2
LPAD-18731
In Content Server 10 the Atlas module was deprecated, however, an

Atlas cookie was still set by the application. This cookie contained
information regarding which pages had been visited in Content
Server. This cookie is no longer generated.
SP2
LPAD-24455
It was possible to construct an attribute creation request in a way

that caused a Content Server thread to terminate unexpectedly.
Additional error checking has been added to the server to prevent
this error.
69
SP2
LPAD-25036
The parameters for Content Servers checkNextURL functionality

are now case-sensitive. As of SP2, this change affects Content
Server 10.0.0.
SP2
LPAD-28504
A cross-site scripting (XSS) vulnerability in Content Servers Java

Modules framework has been addressed.
SP2
LPAD-29214
A potential memory leak involving servlet temporary file cleanup

routines has been resolved.
SP2
LPAD-29399
Potential brute force credential attack vector mitigated.
SP2
LPAD-29771
The LL.ProcessAccept request handler, which is part of the Personal

Staging module, had a cross-site scripting (XSS) vulnerability that
could be exposed through specially constructed URLs. This issue
has been addressed.
SP2
LPAD-29857
Detailed SQL error messages are now displayed only to admin

users.
SP2
LPAD-29945
A potential denial of service attack vector related to Dynamic View

was mitigated.
SP2
LPAD-29949
A cross-site scripting (XSS) vulnerability in Content Server has been

addressed.
SP2
LPAD-30235
It was possible to configure tabs used to organize Favorites,

Notification, etc. for any user in the system by editing a URL,
regardless of permissions. This was corrected so that only user
administrators can modify the tabs for users other than themselves.
SP2
LPAD-29984
It was possible to cause a Content Server thread crash by creating a

request of a certain format to the ProcessMultiAccept2 request
handler in the Personal Staging module.
SP2
LPAD-30031
Cross-site scripting (XSS) vulnerabilities in Content Server Workflow

have been addressed.
LPAD-30092
SP2
LPAD-30033
A cross-site scripting (XSS) vulnerability in Content Servers Target

Browse functionality has been addressed.
70
SP2
LPAD-30232
A cross-site scripting (XSS) vulnerability in Content Servers Copy

functionality has been addressed
SP2
LPAD-30070
An issue involving the saving of Tasks could cause Content Server

to use a large amount of system memory and system resources,
which could lead to the service becoming unavailable for use.
SP2
LPAD-30183
Additional checking has been added to the retrieval of Category

Facet and Column MetadataSources to prevent trace files from
being generated.
SP2
LPAD-30207
An issue involving the renaming of Category Attributes could cause

Content Server to use 100% of the system resources.
SP2
LPAD-30234
A reduction in the number of Personal Favorites tabs a user can

create at one time has been introduced to prevent requests that
consume resources for an inordinate amount of time.
SP2
LPAD-30290
Content Server encountered an error and generated a stack trace

when loading information about Projects from Enterprise Connect.
SP2
LPAD-30292
The Project Creation Wizard had a cross-site scripting (XSS)

vulnerability in the way that error messages were reported to users.
SP2
LPAD-30639
The request handlers used to verify databases in the Database

Administration section of Content Server had cross-site scripting
vulnerabilities. It was possible to construct a server request that
allowed an attacker to gain control of sensitive user information.
SP2
LPAD-30643
The request handler used to edit users in Content Server had a

cross-site scripting vulnerability. It was possible to construct a server
request that allowed an attacker to gain control of sensitive user
information.
SP2
LPAD-30644
The request handler used to add users to groups in Content Server

had a cross-site scripting vulnerability. It was possible to construct a
server request that allowed an attacker to gain control of sensitive
user information.
SP2
LPH-867
eLink will now correctly parse multi-part MIME files whose

boundaries consist solely of hyphens.
71
SP2
PYRO-507
An issue was identified in a core engine component of Content

Server that could cause Content Server to crash.
SP2
PYRO-516
A core engine function in Content Server has been augmented to

improve handling of invalid information.
SP2
SFWK-3246
XSS vulnerability in Collections module corrected.
SFWK-3285
SP2
SFWK-3341
Potential script crash in search results corrected.
SP2
SFWK-3431
SQL injection vulnerability in search interface corrected.
CST-198
The otdsintegration.verifyconnection request was accessible to all

Content Server users. This caused a security concern because it
allowed any user to use this handler to detect whether an OTDS
server was available on the internal network at the specified URL.
This is now fixed, and only the Admin user can access this request
handler.
LPAD-17379
A new configuration setting was added to Java Module

Administration page to allow Content Server administrators to
restrict which remote addresses are allowed to connect to Content
Server RMI processes.
LPAD-21938
When Advanced Versioning for documents was used, users could

see the Attribute values assigned to Minor Versions when they only
have permissions to see the Major Versions of the document. This
issue was previously resolved in pat08361; that hotfix is now
integrated into core Content Server.
LPAD-25267
It is possible to construct a nextURL parameter which could be used

on certain requests to redirect a user to an external system.
LPAD-25716
When content was moved from one folder to another using a

Workflow, the original permissions were not maintained.
72
LPAD-26293
Users with Admin permissions that restored a document using the

Undelete functionality were given full permissions for the document,
and users in the Default Group or with Public Access enabled were
given the See and See Contents permission. This issue is now fixed
so that the restored document will no longer inherit the permissions
of the parent item, and the owner of the item and the user restoring
the item will have stripped permissions.
LPAD-26300
Possible SQL injection vulnerability is now resolved.
LPAD-26840
The admin.SysLogin request handler could be used to determine

details of the Content Server deployment.
LPAD-26994
A known XSS vulnerability in Workflow has been addressed.
LPAD-27391
When the audit trail "Don't include user names" option is cleared
from the Workflow administration pages, users were not made
aware that a server restart was required. A restart message is now
displayed.
LPAD-27682
Clean up debug code in servlet.
LPAD-27690
A code level issue that is in SMTP Transport has been fixed.
LPAD-27693
A directory traversal issue was identified in the servlet

(LLServletDcs.java) has been fixed.
LPAD-27695
A directory traversal issue was identified in the

LLServletViewRequest.java servlet is fixed.
LPAD-28733
The admin.index login dialog can now only be accessed by the listed
IPs. All other IP addresses will see receive the standard permissions
error.
LPAD-28876
A known XSS vulnerability in the Workflow handler has been

addressed.
LPAD-28898
A carefully constructed request with invalid cookie data had the

potential to cause a Server Did Not Respond error. This issue is
fixed
LPAD-28961
There was a potential DoS attack vector in Workflow Maps. This is

now fixed.
73
LPAD-29055
A potential denial-of-service attack vector related to Recommender

has been mitigated.
LPAD-29060
A potential denial-of-service attack vector related to browsing groups

has been addressed.
LPAD-29061
A potential denial-of-service attack vector related to Target Browse

has been mitigated.
LPAD-29074
A potential denial-of-service attack vector related to updating object

permissions has been addressed.
LPAD-29076
A potential denial-of-service attack vector related to Document

Overview has been mitigated.
LPO-660
A potential denial-of-service attack vector related to LAPI has been

mitigated.
LPAD-29141
A XSS vulnerability in Personal Favorites has been addressed.
LPAD-29186
An interface was added to the DBWIZAPI ospace to check whether

a database query contains SQL that is non-transactional. This
interface was added.
LPO-658
XMLImport file access is now restricted.
PYRO-437
Large files in Content Server could cause memory use issues. The
issue is fixed to catch the exception and return an error when this
occurs.
PYRO-448
A built-in function was found to be vulnerable to attack causing

memory exhaustion. This issue is fixed.
SFWK-2939
XSS vulnerability in search administration pages.
SFWK-3118
Potential spoofing of search result permissions.
TEMPO-109
Thread logs now handle passwords from OpenText Tempo clients in

a manner consistent with Content Server.
TEMPO-443
When users log in to Content Server through OpenText Tempo, the

password expiration set for external users is now enforced
74
LPAD-24440
Permissions on a Workflow are now updated correctly so only

people with the correct permissions can delete it.
LPAD-23959
Enhanced parameter validation for various Content Server URLs.
LPAD-24155
A stack crawl occurred when a user created a custom form that

used a Post for the request. This issue was only relevant to some
web servers. This issue is fixed.
LPAD-26250
The removeStylesheet parameter in XML Export is disabled due to a

security issue.
LPAD-27530
An XSS vulnerability in permissions has been addressed.
LPAD-25907
An XSS vulnerability in Categories has been addressed.
LPAD-27706
Moving a folder with sub-items resulted in wrong permissions. This

issue is now fixed so the permissions for the folder and its sub-items
are inherited from the new parent of the folder being moved.
LPAD-23636
It was possible to open a document through a URL, and the system

would not check whether an administrator disabled the document
open capability. This inconsistency is removed.
LPAD-22539
A new security setting, Allow log-in via HTTP GET request, was
added. This setting is turned off by default. When turned off, users
cannot authenticate through the ll.login request handler by HTTP
GET.
LPAD-23513
Improve error handling to prevent script crashes during workflow

initiation
LPAD-22624
A known XSS issue with URL objects in browse view has been
addressed.
LPO-601
Input via Workflows is more aggressively sanitized. This sanitization

can be removed by editing the opentext.ini file.
LPAD-26998
The GetTextContent functionality is deprecated due to a security

concern, use the Download feature instead
LPAD-28875
When an Object Usage Privilege is restricted or unrestricted, not all

Content Server instances and threads are notified of this change.
Depending on the thread and instance that serves the request, a
user may wrongfully have access or be denied access to an object
type. A workaround is to restart all Content Server instances after
making such a change
LPAD-17773
There was a possible SQL injection vulnerability. This issue is

resolved.
75
LPAD-22113
A stack crawl was generated when users view the Table of Contents
in the Online Help. This issue is resolved.
LPAD-23574
A stack crawl could occur in the temporary staging area. This issue
is resolved
LPAD-26334
When an exception happened in the Content Server servlet code,

files would not be closed, and would not be deleted. This caused the
configured temp directory to fill up. This issue is resolved.
LPAD-27059
A carefully constructed LAPI request could allow for elevation of

permissions. This issue is resolved.
LPAD-23623
A carefully crafted request could cause issues with the access

control restriction on granting access to groups only. This issue is
resolved.
LPAD-23350
work.StatusMenu request handler can stack crawl. This has been

fixed for all versions.
LPAD-20227
XSS Vulnerabilities in Workflows/Category Attributes. This issue is

resolved.
LPAD-26168
An XSS vulnerability in the wfp.SetPerformers request handler was

present. This issue is now resolved.
LPAD-26399
In certain situations, the Content Server error page could be

vulnerable to a cross-site scripting (XSS) attack. This issue is now
resolved.
LPAD-26829
The System Attribute administration pages had possible cross-site

scripting (XSS) vulnerabilities. These issues are now resolved.
LPAD-26830
An XSS vulnerability in ListAcls action. This issue is now resolved.
LPAD-27521
All updates to the System Security Parameters are logged in the

system audit log. This issue is now resolved.
LPAD-26170
The Document Overview configuration page has possible cross-site

scripting (XSS) vulnerabilities. This issue is now resolved.
LPAD-27661
The Virtual Folder Specific Properties tab was updated to make use
of a Secure Request Token to help mitigate CSRF attacks.
LPAD-23641
XSS vulnerability in workflow request handler.This issue is now

resolved.
LPH-773
The eLinkConfigure request handler had an XSS vulnerability. This

issue is now resolved.
76
LPH-641
An issue with the FetchMailAttachmentFromDoc request handler

could potentially cause the server to crash. This issue is now
resolved.
LPH-693
eLink: It was possible for users to receive emails related to objects

for which their permissions had been revoked. This issue is now
resolved.
LPH-784
XSS issue with nextURL parameter. This issue is now resolved.
SFWK-777
XSS vulnerability in Recommender module.
SFWK-1210
Potential denial of service in email notification.
SFWK-1306
Potential denial of service with Importers. A new optional INI setting

can be used to adjust this. Lower values may impact performance.
In [SearchOptions], maxImportAgentObjectsPerTransaction=10000
SFWK-1578
Inclusion of unintended information in Search API.
SFWK-1664
Potential denial of service in Prospectors.
SFWK-2026
Improve protection of potentially sensitive data in the System Object

Volume. Permissions for access to the affected locations will be
modified from See Contents to See by means of an automatic
database upgrade.
SFWK-2527
XSS vulnerability exists in some functions within the Collections

feature.
SFWK-2608
Potential information exposure in Search API.
SFWK-2628
Potential denial of service in Collections.
SFWK-2723
XSS vulnerability on an administration page.
SFWK-2792
Improve protection of configuration data in Remote Search.
SFWK-2864
Potential denial of service in Remote Search module.
77
LESAPI-671
A Content Web Services security fix was made that requires

Microsoft .NET Framework 3.5 Service Pack 1 or later. Systems
hosting the .NET web services will need Microsoft .NET Framework
3.5 Service Pack 1 or later installed. Applying this update without
.NET Framework 3.5 SP1 or later installed will cause web services
requests to fail.
LPAD-24468
The sorting of objects by name or custom columns in the Browse

view is now case-insensitive. A database upgrade is required to
replace indexes on the multilingual metadata tables to allow for
efficient sorting.
LPAD-26520
Distributed Agent task infrastructure did not select the correct user
context for execution required, in some cases, for future
functionality. Existing tasks for Facets and Columns are not affected
by this issue.
LPAD-26955
It was possible to add a Custom View to a Workflow Attachments

folder by adding a document named customview.html. Starting in
Update 5, Custom Views can only be added to Workflow
Attachments folders in the same way that they are added to any
other Folders.
LPAD27535
A potential XSS vector related to the Location column in a Dynamic

View has been mitigated.
LPAD27537
A potential XSS vector related to Facet names and values in the

Facet Panel and More dialog was mitigated.
LPH-730
Zero-byte documents emailed to Content Server 10.0.0 from eLink

caused the server to crash.
PYRO-362
Various potential buffer overflow, client privilege and numeric

truncation issues were resolved in core binaries.
SFWK-1034
Potential exposure of unintended information in Hit Highlighting.
SFWK-1857
Potential denial of service in Search Administration.
SFWK-2077
Potential denial of service in Search API.
SFWK-2139
Potential denial of service in Index Verifier.
78
SFWK-2145
Potential denial of service in Search results.
SFWK-2153
Potential denial of service saving Search Templates.
SFWK-2190
Potential denial of service in Search administration.
SFWK-2217
Insufficient parameter validation in Search API.
SFWK-2254
Potential memory leak in Advanced Search.
SFWK-2255
Potential memory leak in Search statistics.
SFWK-2284
Insufficient permission checking for access to certain Search

features.
LPAD-22898
The Number of Days Password Persists setting was not restricted to

a value range similar to other settings.
LPAD-25093
Users with User Administration privilege were able to access and

make changes on the Object Usage Privileges page. This issue is
now resolved.
LPAD-26071
4
LPAD-25837
When upgrading Categories on items or applying Categories to

items in a container (resulting in new versions of the items), there
was a possibility of the metadata for one item (for example, file
name or MIME type) being applied to another item.
LPAD-25920
When the Change Password at First Login check box is selected in

the Configure Password Settings section of the Content Server
Administration page and an Admin user resets a user password, the
user is redirected to a Change Password window at the next log in.
LPAD-26163
If a user modified the Multifile Zip and Download URL, a Server

Does Not Respond error would occur.
LPAD-26253
A stack crawl could occur when managing user permissions by

selecting a user from the User tab on the Permissions page.
SFWK-796
Potential user access to system configuration information.
SFWK-883
Potential denial of service in search results.
79
SFWK-1105
Potential denial of service performing operations on certain types of

objects.
SFWK-1635
Potential denial of service in a search request handler.
SFWK-1867
Potential denial of service in Search Bar.
SFWK-1879
XSS vulnerability in Collections.
SFWK-1898
Potential denial of service in Make Disk Image.
SFWK-1934
XSS issues on some Search admin pages.
SFWK-1946
XSS Issue in search administration.
LESAPI-729
Calling the Content Web Services WorkflowService's

CompleteWorkItem method on a work item (Workflow step) that is
unassigned or waiting resulted in a script crash. Additional checks
are now added to ensure these error cases are handled correctly
and proper error messages are returned.
SFWK-1692
Deleting a version for a non-document object (not SubType 144)

was not functioning correctly. This will leave orphaned objects in the
index, and potentially present search results for objects that do not
exist. This also prevents the Index Verification tool from deleting
orphaned objects.
WRD-159
When using the Print function, there was a potential for reflected
cross-site scripting (link injection).
WRD-160
3
WRD-158
When using the Zip & Download function, there was a potential for
reflected cross-site scripting (link injection).
WRD-150
When editing an Appearance, there was a potential for reflected

cross-site scripting (link injection).
WRD-136
When editing a Category, there was a potential for reflected crosssite scripting (link injection).
80
LPAD-23639
Various XSS Vulnerabilities in Content Server.
LPAD-23756
LPAD-24325
LPAD-24327
LPAD-24330
LPAD-24469
LPAD-24694
LPAD-24719
WRD-142
WRD-146
2
LPAD-24110
Admin user is now required to set a password upon initial

configuration.
LPAD-24123
User account locking is now on by default.
LPAD-24124
Browser auto-completion was switched on by default. The default

setting for auto-completion will now be off.
LPAD-24126
Document function Open is now disabled by default.
LPAD-24127
Default password settings have been made more secure.
LPAD-24128
Users without permission to create Item Handler workflow tasks are

no longer able to import workflows containing Item Handler steps.
This functionality has been implemented to address a security
vulnerability that would allow for the elevation of user privileges
LPAD-24130
URL object creation is unrestricted by default. The new default

restricts the ability to create a URL object in CS from the add item
menu. On a new install that means only the Admin user can create
it. You can then add specific users that are allowed to create URL
objects via the "Administer Object and Usage Privileges" Admin
Page
81
LPAD-24164
LPAD-24370
LPAD-24372
LPAD-24464
Failure to Sanitize CRLF Sequences in HTTP Headers ('HTTP

Response Splitting') allows for CRLF injection. Writing un-sanitized
user-supplied input into an HTTP header allows an attacker to
manipulate the HTTP response rendered by the browser, leading to
cache poisoning and cross-site scripting attacks.
Cookies can now be marked as secure for enhanced security with
Java Modules
LPAD-24373
Addresses a denial-of-service vector due to resource depletion.
LPAD-24579
Potential denial of service in XML Export feature.
LPAD-24614
Anchor tag URLs generated by WebNodeCmds are now properly

encoded for use in HTML.
PYRO-78
Addressed buffer overrun vulnerabilities in the Content Server kernel

and engine.
PYRO-79
2
SFWK-892
Potential denial of service in Search API.
SRCH-1042
Potential denial of service in Search Engines.
SFWK-1243
Potential denial of service in search functionality.
SFWK-1325
Potential denial of service in Prospectors.
SFWK-1482
XSS vulnerability in the search administration.
SFWK-1493
XSS vulnerability in search results.
WRD-43,
WRD-147
XSS vulnerability in the Object Delete functionality.
82
15 Appendix F Notable Fixes

Corrections for defects which are notable based on severity or customer reported frequency are listed
in the table below. The complete list of issues addressed with each Update can be reviewed in the
readme files provided as part of the release packages on the OpenText Knowledge Center.
Release
Reference
Description
2016-06
PYRO-2718
DB connections can be orphaned during startup.
2016-06
PYRO-2525
A number of DB correction utilities should be using DtreeCore instead

of DTree.
2016-06
PYRO-1742
Renaming a document is not functioning as expected when Metadata

language is removed
2016-06
LPAD-48406
Extra database connection is created when auditing without a PrgCtx
2016-06
LPAD-28845
Optimize purging audit events using bulk deletes from DAuditMore
2016-06
LPAD-48349
SetValue function fails due to poor error handling for memcached

values on any error from the process
2016-03
LPAD-36844
In the Target Browse dialog, sorting by clicking on table headings does

not work within Favorites or Projects folders. This has been fixed.
2016-03
LPAD-42223
Opening a help link into a new tab or new window results in an infinite
redirection loop. This has been fixed.
2016-03
LPAD-40828
Personal LiveReports do not display in the users preferred language.

This has been fixed.
2016-03
LPAD-46015
Some checkboxes on the Configure Security Parameters

administration page do not function as expected. This has been fixed.
2016-03
LPAD-46710
XML Export does not respect the LogPath setting in the [XML] section of
the opentext.ini file. This has been fixed.
2016-03
SFWK-4675
Cannot purge and re-index a data source when search partitions in

retired mode are present. This has been fixed.
2016-03
SFWK-7009
SFWK-6935
Issue with blue frames displayed around document icons in several

locations when using Internet Explorer compatibility view mode. This
has been fixed.
2015-12
LPAD-25010
Folder permissions are not retained when creating a project from a

project template or with XML Import. This has been fixed.
2015-12
LPAD-34240
Permission checking has been hardened to allow APIs to benefit from

See Contents permission checks for methods that list the contents of
containers.
2015-12
LPAD-35908
Show Group Members function fails if a pipe symbol (|) is in the group
name.
83
2015-12
LPAD-37829
Add database repair tool to handle orphaned objects (invalid ParentID).
2015-12
LPAD-42574
The &selectLabel feature in objAction=TargetBrowse is not working.

2015-12
LPAD-43906
Selecting 'Cancel' when deleting a discussion results in http 404 error.

2015-12
LPAD-44077
Optimize SQL used by IsNameUnique.
2015-12
LPAD-44142
Removed obsolete feature "Delay deletion from storage provider".
2015-12
LPAD-44591
Two new expressions are available in the Workflow Expression Builder

for the Evaluate Step:
"is empty" (empty string)

"is undefined" (undefined/null)
This allows for tighter control, especially when using a MS SQL

database where Content Server treats empty string attributes differently
than undefined values.
2015-12
LPAD-44795
Attribute Changed is not captured in Audit tab when adding version and
changing attribute value together.
2015-12
LPAD-44797
Deleting large numbers of documents may not write entries to the

DeletedDocs table when using the Document Undelete Module.
2015-12
LPAD-45233
Multi-File Print is non-functional with IE11 if compatibility mode is

disabled. This has been fixed.
2015-12
LPAD-45565
The four arrow images do not appear in Dynamic Column configuration

page on Solaris. This has been fixed.
2015-12
PYRO-2329
Added constraint to ensure that ParentID is never the same as DataID.
2015-12
SFWK-6665
Date attribute displays incorrectly when displaying region in search and

item has multiple date values in attribute. This has been fixed.
2015-12
SFWK-6707
Admin Service will not start if there is one blank line after comments at
start of opentext.ini. This has been fixed.
2015-12
SFWK-6781
[Last Results] link returns error after opening Search Result Snapshot.
2015-12
SFWK-6824
Search index backup process returns an error code too low, masking
the error in the UI. This has been fixed.
2015-09
LPAD-31655
Workflow attributes page can become blank
2015-09
LPAD-33803
My Notification Reports tab now supports multiple languages and

custom configuration
84
2015-09
LPAD-34646
When a user has Add Item but not Reserve permission on a folder, if
the Owner also lacks Reserve permission, the user will experience an
error when trying to add an object.
2015-09
LPAD-37025
Function menu requires two clicks in the Workflow Attachment area.
2015-09
LPAD-37526
Minor version information is incorrectly displayed in Facet/Column

values.
2015-09
LPAD-38048
Level 5 and 6 Database Verification does not report all objects that
could not be located in the storage provider.
2015-09
LPAD-38600
Date format in email notifications does not adhere to language settings.
2015-09
LPAD-41941
Harden sysreport against invalid objects
2015-09
LPAD-42265
Content Server email notifications can exceed the RFC 2822 limit of
988 characters per line.
2015-09
LPAD-42334
Long file names processed by Zip and Download are stored with an
incorrect extension if the file name contains multiple periods.
2015-09
LPAD-42807
Some symbols and punctuation characters do not display correctly

within the Project Wizard
2015-09
LPAD-42883
Potential script crash in Distributed Agents when an undefined task is

encountered.
2015-09
LPAD-42914
Email notifications are sent in Admin Users preferred language instead

of the recipients preferred language.
2015-09
LPAD-42930
Multi-select User Dialog does not work for Hebrew names
2015-09
LPAD-42959
Facet disappears after a category upgrade
2015-09
LPAD-42996
Optimize Facet update performance by caching parent objects
2015-09
LPAD-43459
Database Correction of Missing Reflexive Rows not working
2015-09
LPAD-43680
Facets sidebar displays even if the user has no Public Access

permissions.
2015-09
LPAD-43746
SEA servlet will now validate that the Authentication_User setting is

compatible with the settings in the opentext.ini file.
2015-09
LPAD-43891
XML Export crashes if the actual data size is shorter than expected.
2015-09
PYRO-490
The IsFeature() function returns TRUE even if the member is not a

member of the node or version
2015-09
PYRO-1966
Concurrent deletes on the same object can result in corrupted values in

database tables DTree, DTreeAncestors, or DDeletedItemsNodes
2015-09
PYRO-2005
Incorrect value in cache after a transaction rollback.
85
2015-09
PYRO-2120
Sub-folders created during document declaration do not inherit

permissions correctly when created using the method
CreateSimpleFolder.
2015-09
PYRO-2178
DAPI.CopyNode should return an error in the event a deadlock occurs
2015-09
PYRO-2188
When enabling Log4j and legacy Content Server logging, 3 connect

logs are generated
2015-09
SFWK-6422
Error generating OTSQL query for valid attribute followed by an empty

set definition.
2015-09
SFWK-6490
Renditions are now marked with a vertical bar icon in search results to
differentiate them from non-rendition results.
2015-09
SFWK-6545
Admin Server hangs if a source file is missing during a SetFile

operation
2015-09
SFWK-6586
Include hidden items in search results for admins
2015-09
SFWK-6663
Optimize performance of search results using bulk operations in

GetSearchResultsTemplateList
2015-09
SFWK-6681
Display options categories are not multi-lingual aware
2015-09
SRCH-4050
The OTFileType could be incorrectly assigned multiple values for size 0

items and items indexed immediately afterwards.
2015-06
LPAD-595
Zero (0) is now available as an option for the number of Sub-Catalog

items on the presentation tab of a folder.
2015-06
LPAD-42635
Item reference attributes that are set to Workflow attachments during

Workflow initiation no longer refer to the Workflow attachments in the
user's temporary Workflow folder. They now refer to the runtime
attachments in the Workflow attachments folder. Item handler attributes
that refer to Workflow attachments are now updated whenever a
Workflow is suspended and modified.
2015-06
PYRO-1816
Rolling log files are supported for per-thread and per-connect mode.
2015-06
LPAD-595
An additional option was added to the Presentation tab for container

objects, such as folders, which allows 0 featured sub-items to be shown
below featured items.
2015-06
LPAD-23141
2015-06
LPAD-34830
Unable to change item List, Featured, Hidden when adding via

Workflow Attachment
Facet count queries are very slow going against a facet based on a
checkbox category attribute
2015-06
LPAD-35289
Two clicks on the same icon are required to switch to the WebDAV drag
and drop view
86
2015-06
LPAD-35362
Users should not be allowed to move projects into sub-folders of other

projects
2015-06
LPAD-40235
Webreports 10.0.1 - nodeaction:move fails on documents with Chinese

Colon in document name
2015-06
LPAD-40741
Checkboxes not Recognized in IE9 for Copy, Move, Delete,

Zip&Download, etc. Buttons on Button Bar
2015-06
LPAD-42431
llnode.NodeReserve() can return success for 2 users reserving at same

time - even though only one should succeed.
2015-06
LPAD-41433
Warning Page Has Expired when paging back on Multi-Page Audit Trail
2015-06
LPAD-42805
Possible deadlock on AgentSchedule table under high load.
2015-06
LPAD-42852
DB query lock prevents parallel copy of documents and folders with

categories.
2015-06
LPAD-42969
"Previous" link on the audit tab does not work on some browsers
2015-06
LPAD-42982
Logging into Content Server with a Domains enabled user fails through
LAPI.
2015-06
LPAD-43154
Workflow tasks with roles assigned to groups generate duplicate elink

emails
2015-06
LPAD-43635
Attribute values are not updated if object specified is using Item

Reference Attribute
2015-06
PYRO-1816
Support rolling log files with per-thread and per-connect logging

enabled
2015-06
PYRO-1862
Ensure PrgCtx cleanup occurs when used by instantiated Agents
2015-06
PYRO-1905
DAPI.GetNodeById was not returning an error code if the Parent ID and

Data ID were identical, preventing Extractor operations from
completing.
2015-06
PYRO-1958
Potential stack trace during startup processing in GetPrgCtx.
2015-06
SFWK-4111
Searching for a category Text:Popup attribute that contains quotation

marks fails with an error.
2015-06
SFWK-6128
"Verify Agent terminating due to time expiration" message sent

everytime Index Verification runs over the allocated time.
2015-06
SFWK-6186
Search Filter displays User Attribute FirstName LastName regardless of

Configure User Name Display setting
2015-06
SFWK-6376
Protect the Extractor from 32 bit integer NID value overflow on Oracle
database.
2015-06
SFWK-6381
AdminService.GetDirList() stops prematurely on broken symlink entries.
2015-06
SFWK-6394
Index Verification causing trace file _DistributeCheckObjects
87
2015-06
SFWK-6411
Trace file when accessing Personal > Collections when permissions are
disabled to users personal workspace
2015-06
SFWK-6422
Error generating OTSQL query for valid attribute followed by an empty

set definition.
2015-06
SFWK-6450
One or two unexpected items may be displayed in a Collection when

sorting on custom columns.
2015-06
SFWK-6455
Incorrect translation of the text items on search results page.
2015-06
SFWK-6465
Potential crash after configuring the search bar if invalid configuration

strings are used.
2015-06
SFWK-6472
The semi-colon is now correctly stripped from file names when

generating a Joliette format Disk Image from a collection.
2015-06
SFWK-6499
Unexpected permission error in the Location component when refining

a From Here search query.
2015-06
SFWK-6548
Search terms over 255 bytes in length fail with error. Limit is now 8,000
bytes.
2015-06
SRCH-3671
Specifying a non-DATE region type for a date ranking field in the search
engine will no longer crash (logs error, ignores field).
2015-03
LESAPI1885
Setting a category attribute to NULL via Web Services affects attributes

ability to be edited in the web interface.
2015-03
LPAD-41470
Distributed Agent performance: Inserting values into

WorkerPackages_2 can take a very long time when there are many
rows in WorkerPackages and TaskPackage Map.
2015-03
LPAD-41682
The Add button in the Add Document wizard should be disabled after
the first click.
2015-03
LPAD-41761
Error 'ORA-00060: Deadlock detected while waiting for resource'

encountered when permissions are being updated.
2015-03
LPAD-41855
Support filtering by object types in virtual folders.
2015-03
LPAD-41876
Multifile upload does not work while using a Tomcat server.
2015-03
LPAD-41958
Presentation image showing as a broken link if Document Open

function not enabled.
2015-03
LPAD-42081
Transient Nodes in Enterprise Library cause stack trace in LLNotify

NodeEventProcessor.
2015-03
LPAD-42094
Folders wrongly inherit category from Project Template.
2015-03
LPAD-42097
Browse of Enterprise Workspace does not work if the Enterprise

Workspace data ID is not 2000.
2015-03
LPAD-42107
If Content Server has a container that is over 250 levels deep, the top
level cannot be deleted or moved.
88
2015-03
LPAD-42257
Custom column width restricted to 64 characters to match the size of

the custom column data.
2015-03
LPAD-42285
Sysreport and thread logs may report wrong Update Numbers in

Multilingual systems.
2015-03
LPH-1037
elink base64 encoding does not follow the RFC821 mail standard and
break the line.
2015-03
PYRO-1434
Create a new Math.RoundSignificantReal() method that honors

significant digits.
2015-03
PYRO-1720
Increased size of DDeletedItemsNodes.DeleteInfo column to eliminate

error trying to delete a column from a facet volume.
2015-03
PYRO-1746
LLServer crashes under specific conditions when executing some

DAPI.List* calls.
2015-03
SFWK-5084
Repeated Search Query executions with SearchAPIUtil.RunQuery() in

the same request may return unexpected results.
2015-03
SFWK-6050
"Error Evaluating Query" when OR operator between two categories

used.
2015-03
SFWK-6061
The Index Verifier creates versions with an invalid file size when
generating .csv report files.
2015-03
SFWK-6110
Better handling of very long file names/paths for the Make Disk Image
functionality.
2015-03
SFWK-6221
Cannot search for "fs" (unquoted).
2015-03
SFWK-6253
En dash or em dash as part of a search causes a query conversion

error.
2015-03
SFWK-6281
Admin Server resync silently creates empty partition index.
2014-12
LPAD-40693
Add checks for DTreeAncestors to DBVerification.
2014-12
LPAD-40993
Allow a port number to be included when creating a database with

MSSQL 2012.
2014-12
LPAD-41375
Relative date facet SQL causing performance issues.
2014-12
LPAD-41429
Cannot set News Player as non Admin user.
2014-12
LPH-1013
Inbound eLink emails with double-byte characters in the subject line will
result in the subject line have garbled subjects.
2014-12
LPH-1056
elink Base64 encoding change violates RFC821 Mail Server standard

(max 999 character in email body).
2014-12
SFWK-5217
Web Services Search Graph has mismatched fields and values when
null category values exist.
89
2014-12
SFWK-6001
When item name is comprised of dual-byte characters, the Email

properties share link from search results displays junk data.
2014-12
SFWK-6048
The Content Server location for items located within a project is not
correct in a collection Disk Image.
2014-12
SRCH-3765
DCS format recognition fails for some .EML email files with unusually
long values in header variables.
2014-09
LPAD-38982
Content Server would not allow the entry of attribute values longer than
65,535 characters when used with an Oracle database system. This
was due to limitations in older versions of the database library. These
limitations were removed.
2014-09
SFWK-4659
Make Disk Image configuration does not properly handle a path name
that ends with a slash character.
2014-09
SFWK-5115
Metadata language not displayed in Project Overview page.
2014-09
SFWK-5119
Location components in Advanced Search that have no value should be

excluded from the search query construction.
2014-09
SFWK-5327
Recommender Gather Agent stops processing rows from

Recd_OperationTracking due to an integer overflow.
2014-09
SFWK-5356
Collections count update does not modify the Collections Modified By

information.
2014-09
SFWK-5455
Web Services Search API does not work correctly when trying to use
the & (ampersand) character.
2014-09
SFWK-5458
Dataflow manager resynchronization does not work correctly if the

target directory exists and is empty.
2014-09
SFWK-5467
The Admin Server should ignore host names in the otadmin.cfg file
to prevent interference with processes on other servers, which can
occur if the otadmin.cfg file was improperly copied from another
system.
2014-09
SFWK-5487
A Collection Disk Image can miss items when using an Oracle

database.
2014-09
SFWK-5489
Unnecessary status check of disabled Document Conversion Server

processes removed from Admin Server.
2014-09
SRCH-3504
Improve readability of summaries generated by Document Conversion

Server when there are spaces between letters in a word.
2014-09
SRCH-3508
Search Engine update polling thread can stop, throttling the Index
Engines.
90
2014-09
SRCH-3585
Search filter values for multi-value OTFileType values are incorrect

after updating objects.
2014-06
SFWK-5083
Searching a compound document from here does not locate children

of the compound document.
2014-06
LPAD-36047
Performance improvements were made to the caching mechanisms in

Content Server. Database optimizations resulted in faster query times
when retrieving data. Additionally, values are now automatically written
to memcached, which may result in faster retrieval, and reduce impact
on the database system.
2014-06
PYRO-1522
2014-06
SFWK-5098
Modified built-in function File.Read(), so that it does not remove

carriage return if the file is a carriage return delimited file.
The Search Index Restore Wizard could fail on systems with many
partitions, resulting in an HTTP Error 404.15 query string too long.
2014-06
SFWK-5184
Count for number of items in a Collection is incorrect if the parent

location of an item in the Collection is deleted.
2014-06
SFWK-5291
Email disposition for email objects referenced by a Collection could

result in database deadlocks on the Collection table with SQL Server.
2014-06
SRCH-3195
Document Conversion Server language detection could crash with

some documents.
2014-06
SRCH-3466
Document Conversion Server could crash on startup with a PE255

error.
2014-06
SRCH-3358
Document Conversion Server could generate incorrect file names for

email attachments when using the List Attachments feature through
the direct socket API.
2014-03
LPAD-35901
In certain situations, under a heavy load, it was possible for the server
to retrieve out-of-date Category information from the database while
another server thread updated the same Category information on the
same object. This issue is now fixed.
2014-03
LPAD-36023
Attempts to retrieve permissions data on SMB2 file shares caused the

File.Stat function to fail on Windows. Various Content Server requests
that result in file operations on disk were affected. This issue is now
fixed.
2014-03
LPAD-36254
With Java 7 update 45, Oracle introduced new security features for
Java applets.
Java 7 update 51 blocks Java applets that are not compliant with the
enhanced security features.
91
For Java 7 update 51 support, Update 2014-03 and patches

pat100001267 and pat100001287 are required.
Customers running Java 7 with an update prior to 51 may find that the
applets are blocked, even if these patches are applied. This is outside
of OpenText's control.
The following client-side options will allow the applets to work:
Create a client-side Deployment Rule Set (Introduced in Java 7

update 40)
Lower the client-side Java Security slider to Medium
For information about the stricter security policies and the Deployment
Rule Set, see the following articles written by Oracle:
https://blogs.oracle.com/java-platformgroup/entry/introducing_deployment_rule_sets
https://blogs.oracle.com/java-platformgroup/entry/new_security_requirements_for_rias
2014-03
SFWK-705
Disable Collections features that do not work when "Entire Collection" is

selected.
2014-03
SFWK-4733
Index Verifier stops before checking all items in the database and lacks
error handling.
2014-03
SFWK-4810
Optimization: Download Collection as Spreadsheet is slow.
2014-03
SFWK-4811
Optimization: Improve time to create a disk image.
2014-03
SFWK-4864
Dataflow merge process occasionally truncating IPool messages.
2014-03
SFWK-4870
Continual long-running delete from Recd_OpinionSummary queries.
2014-03
SFWK-4901
Blank Edit Metadata Memory Settings page.
2014-03
SFWK-4934
Not all expected Major/Minor versions are returned in the search results
page.
2014-03
SFWK-4977
Long Extractor DB query when object has been moved.
2014-03
SFWK-4987
Add MS SQL 2012 optimizations to CollectionIteratorSubsystem to

improve performance of Collection tasks such as Browse or Make Disk
Image.
92
2014-03
SFWK-4994
SubType filtered Entire Collection bulk operations fail with SQL error.
2014-03
SFWK-4995
Optimization: Improve performance of audit record retrieval (faster

Make Disk Image).
2014-03
SFWK-4997
Refining search on date range "to" query wrongly fills out "from" value.
2014-03
SFWK-4998
SOV Notification email not sent on every Index Verification completion.
2014-03
SFWK-5029
Disk Image output incomplete when stale versions of Saved Queries

included.
2014-03
SFWK-5053
Sort by 'Name Ascending' in Tabular display options does not work

correctly.
2014-03
SFWK-5055
Cannot add a Control Rule within the Enterprise Data Source.
2014-03
SFWK-5107
Full indexing extraction is processing objects repeatedly.
13
LPAD-35158
Database Verification incorrectly reports objects missing from DTree.

Affects Updates 11 and 12 only.
13
LPAD-34596
Failed web administrator logins cause performance degradation

because of KINI cache invalidation. Updates 10, 11 and 12 only.
13
LPAD-35164
XML Export should not update the Last Modified Date.
13
LPAD-35535
Potential stack crawl in Sysreport when system is busy.
13
SFWK-4528
Incorrect results on Ratings page for People who viewed this item also
viewed field.
13
SFWK-4577
Advanced Search, using Edit the Display Options does not allow the
settings to be saved.
13
SFWK-4596
Admin Server will check for existence of ot6_eng.msg file on startup,

stop if missing with an error message.
13
SFWK-4613
Recommender not tracking people who download correctly.
13
SFWK-4616
Search Bar from here (expanded) shows an empty location on the

advanced search page.
13
SFWK-4618
Optimize performance for browsing large collections.
13
SFWK-4654
Insufficient error handling results in a trace file if search facet structure

does not match the expected region type.
13
SFWK-4669
Extractor should not populate OTDCategory with DAPINode.pCategory.
13
SFWK-4686
OTSQL errors not being trapped with Categories component of

advanced search queries.
13
SFWK-4719
Invalid search index metalog limits applied when upgrading partition

maps in Update 12.
13
SFWK-4720
Prevent line breaks from appearing in search API results between tags
and values.
93
13
SFWK-4725
Target Browse search crashes on query error.
13
SFWK-4726
Optimize gathering large sets of search results in Collections.
13
SFWK-4756
Enable optimized content extraction for Email Management /

Journaling.
12
SFWK-448
NType = -1 (Ranking update) Operations for items in the EL Volumes

are not being processed and deleted from DTreeNotify.
12
SFWK-3702
Add or adjust the indexes on columns in DTreeNotify to improve

Extractor performance.
12
SFWK-4285
Content is not extracted for indexing when moving objects out of

excluded locations to index-able locations.
12
SFWK-4310
SearchAPIUtil may return truncated locationPathMap.
12
SFWK-4315
Search Tools Menu on the Search Results Page is on top of the

Function Menu instead of behind.
12
SFWK-4319
Double slash (//) in image paths prevent icons being displayed when
security policies in place.
12
SFWK-4461
Existing Classification search agents continue to run when

Classifications are disabled.
12
SFWK-4497
Remove unused search agents and importer when Classifications are

uninstalled.
12
SFWK-4500
Temporary "View as Webpage" servlet files not deleted.
12
SFWK-4531
Enter key does not work with multiple custom view searches.
12
LPAD-33362
System Report is slow if there are long strings in the KINI table.
12
LPAD-33398
checkNextURL=true causes invalid URL message.
12
LPAD-34416
XML Export crashed exporting a News item moved while exporting.
11
LPAD-25313
Drag and Drop functionality was restored in Content Server SP2

Update 11 for Workflow attachments.
11
LPAD-31778
By default, the CGI will put a value representing how long the CGI
processes the request before it forwards the request to llserver. This
value is taken into consideration by llserver when it checks whether the
user's cookie is expired or not. If the user does not want to have this
feature, in opentext.ini, under the "Client" section, add:
AddRequestProcessDuration=FALSE
If the user wants to have this feature, we also provide encryption of this
value to make it more secure. However, using encryption degrades the
94
CGI's performance. By default, encryption is not used. To use

encryption for this value, in opentext.ini, under the "Client" section, add:
EncryptRequestProcessDuration=TRUE
To encrypt the value, a default "key" is used. To use a different key, in
opentext.ini, under the "Client" section, add:
EncryptDurationKey=mynewkey
11
LPAD-31216
Admin cannot install/upgrade modules when the Content Server

database requires an upgrade.
11
LPAD-31537
Database options set in incorrect order on creation of new database.
11
LPAD-32605
XSD file for XML Export missing GUID values.
11
LPAD-32662
Optimization: unnecessary restart eliminated on the Configure Function

Menu administration page.
11
LPAD-32760
Malformed XML generated by XML Export for Column:linkURL when

DisplayAsLink = FALSE.
11
SFWK-1355
UseContentReference can associate garbage content with items that

normally would not have indexed content.
11
SFWK-2614
Version specific metadata is not extracted for non-document, versioned,

object types.
11
SFWK-3213
DAPI error when trying to delete a Collection.
11
SFWK-3445
Provided a way to prevent indexing of Initiated Workflows.
11
SFWK-3648
Behavior of search index verifier tightened up to adhere to constraints

imposed by Extractor settings for versions.
11
SFWK-3745
The Index Verifier incorrectly deletes document versions when it locates

an orphaned Rendition of that version.
11
SFWK-3970
Extractor does not properly index version 1 of objects that were

unexpectedly created without a version.
11
SFWK-4036
Sorting on headings within the Data Flow Manager brings back 403
error.
11
SFWK-4050
Column sort does not work from Personal Display Style Template.
11
SFWK-4116
Optimization: Prospector Subscribe function menu logic run

unnecessarily with every functions menu request.
11
SFWK-4135
Search facets computed on startup to reduce chance of timeouts on

initial queries.
11
SFWK-4157
Optimization: Unneeded database load while generating search result

UI.
11
SFWK-4265
Best Bets DB upgrade fails to create index.
95
11
SFWK-4292
Unable to update a Partition, if the Index Engine and Search Engine are
hosted on different Admin Servers.
11
SFWK-4305
Index Engine "Summarize Index Log File" and "Validate Index" do not
function (Update 10 only).
11
SFWK-4310
Incomplete function menus in Enterprise Connect on search pages.
11
SRCH-2782
DCS process recycling on Windows is not reliable, generating process

errors or timeouts.
11
SRCH-2808
Potential corruption of the DCS.ini file when multiple instances are

contending for a single file.
11
SRCH-2822
Summaries generated by DCS are incorrect if images are embedded in

Word documents.
11
SRCH-2848
DCS fatal error -1 while processing an XLSX file.
10
LESAPI1437
A new SetNodeMetadata method was added to the

DocumentManagement service. This method allows you to update just
the Metadata property on a node, instead of updating a full node using
the UpdateNode method.
10
LPAD-5600
If a Workflow replacement tag was used with a Date type attribute, the
time would never be included in the output. This has been changed so
that if the "Include Time Field" option is selected in the attribute
definition, the time will be included in Workflow replacement tag output.
10
LPAD-31641
When using a large number of multi-byte characters in a multi-line

Workflow attribute field, the values can be corrupted. This has been
resolved.
10
LPAD-31691
The search feature in the Target Browse dialog has been improved by
using the OpenText search engine. The search will now accept
wildcards and results will be returned more quickly and efficiently. A
name search will now also be applied across all languages for objects
below the location being searched.
10
LPAD-31789
A new option is available on the "Configure the Operations for Copy,

Delete and Move" page called "Delay deletion from storage provider". If
this option is enabled, when an item is deleted, its content will not be
deleted right away. The "Provider Blob Deletion Failure Retry"
scheduled activity performs the content deletion instead. As a result,
the "Provider Blob Deletion Failure Retry" scheduled activity should
also be enabled on the "Configure Scheduled Activities" page if this
option is enabled.
10
SFWK-647
SOV alert emails do not have a proper To field and are therefore sent
to undisclosed participants.
10
SFWK-3077
When generations are found in search results only one item is seen in
the function menu.
10
SFWK-3177
"Search From Here" Text Remains in Default Search Bar.
10
SFWK-3441
Search and click browser Back button returns "WebPage has expired
message" under certain scenarios.
96
10
SFWK-3605
After a re-extract all non-default System Attributes are gone from the
search template.
10
SFWK-3764
Error saving Search Form when maximum number reached.
10
SFWK-3775
Windows Server 2012: Crash when creating Enterprise Data Source
10
SFWK-3789
Collections Make Disk Image mishandles slashes in item location path.
10
SFWK-3810
Windows Server 2012: Crash when creating new Classification Query

Profile
10
SFWK-3846
Search facets do not appear using Internet Explorer 10.
10
SFWK-3861
Can't save "Preferred Style" into form from Advanced Search page.
10
SFWK-3880
Paths not updated in search index when project folders moved.
10
SFWK-3885
Cookies for search filters are not compatible with IIS + Tomcat 7.
10
SFWK-3910
Missing RM and Case Management SubTypes added to OTFileType.
10
SFWK-3912
System Attribute region names shown instead of region display names.
10
SFWK-3922
Search filters do not display with Firefox 18.0.1.
10
SFWK-3980
View as Web Page fails if user does not have permission to see the
current version, if the current version is a minor version
10
SFWK-4030
Extractor IPool information pop-up is blocked by HTTP Referrer Check

using Google Chrome
10
SFWK-4056
Entries in DTreeNotify for objects deleted before extraction are not

removed from the table with Update 9.
10
SRCH-763
Process error 260 possible when reading an IPool with size of 0.
10
SRCH-2560
DCS fails when message is queued, version is deleted and

UseContentReference=TRUE.
10
SRCH-2675
LESAPI1372
Hit highlight for single Japanese character outputs XML numeric

character reference.
Two new options were added to the NodePageSpecification SDO to
allow filtering on a set of node types to include or exclude when calling
the CWS DocumentManagement Service ListNodesByPage() method.
The new options added are: IncludeTypes, which is a list of node types
to filter the results on, and ExcludeTypes, which is a list of node types
to exclude from the results.
Support was added for filtering on GenericNode node.

Note: GenericNode objects have the following form:
GenericNode:<subtype>
Support was added to update the basic node information using
the DocumentManagement.UpdateNode() method on
GenericNode node types.
97
LPAD-26388
Temporary files created during XML Import could accumulate on disk.

This issue has been fixed.
LPAD-30272
Columns have database schema associated with them, and copying

them will result in errors. To prevent these errors, copying of Columns is
not allowed.
LPAD-30312
Facets have database schema associated with them and attempting to

copy Facets will result in errors. To prevent these errors, copying of
Facets is not allowed.
LPAD-30496
A UTF-8 string might be malformed if it contains CJK characters while

the system locale is Japanese/Chinese. This issue is fixed.
LPAD-30687
In some instances, failure to upload an email to Content Server 10.0.0

from Microsoft Outlook 2007 through Enterprise Connect could produce
database inconsistencies, primarily an incorrect child count set on the
email folder. This issue was fixed
LPAD-30796
Node Exclusion settings were moved from the "Configure Notification"

page to the "Transfer Notification Events" section of the "Configure
Scheduled Activities" page.
SFWK-2664
Conversion from RMI to Socket configuration may fail during an

upgrade.
SFWK-2782
Extractor writes ContentReferenceTemp files to a single folder, which

reduces performance for large numbers of files.
SFWK-2987
Potential script crash if Search Federator returns empty values.
SFWK-3124
Display style not checked on search result page when running a saved
query.
SFWK-3277
A Date Attribute which is part of an attribute set now honors the date
string formatting configuration preferences.
SFWK-3291
Space for German localization of last modified in search bar

increased.
SFWK-3505
Extractor ignores the log level settings.
SFWK-3536
Backup Process menu displayed in wrong location.
SFWK-3604
Search Federator and Update Distributor processes need maximum

memory constraints.
SFWK-3757
Full Text search queries containing LQL errors are executed if there is
another valid search component.
SRCH-2539
The HTML format filter has been improved to recognize a number of

common variations for representing metadata in the HTML file for Title,
Subject, Description and Keywords.
98
SP2
LESAPI-1311
Searching for Content Server users from the OpenText Administration

Client can cause an infinite stream of requests sent to Content Server
when using legacy (CAP) authentication. The search request will time
out, but will continue to consume a high amount of system resources
from the RCS/CWS application server process (for example, Tomcat)
as well as from the llserver process (Content Server). This issue is fixed
so it is now possible to successfully search for Content Server users in
the OpenText Administration Client without consuming a high amount of
resources on the system.
SP2
LPAD-18335
When creating a Project from a template, the value of the Disable

Inheritance check box for Categories was ignored. This has been
addressed.
SP2
LPAD-22905
Negative real numbers are now displayed with the appropriate number
of digits of precision. For example, the value of -7.1 is displayed as -7.1
and not -7.0999999999999.
SP2
LPAD-28304
When performing NTLM authentication, the Content Server system will

now, by default, allow incoming requests from the following addresses:
"::ffff:127.0.0.1", "127.0.0.1", and "::1". These addresses are appended
to the CGIHosts setting from the opentext.ini configuration file.
SP2
LPAD-29672
Additional checking was added to the 6.0.28 database upgrade to

prevent errors when a Column has been defined for a Category
attribute that no longer exists.
SP2
PYRO-533
Web.EscapeForJS() did not output the same value as the JavaScript

escape() function for UTF-8 characters, and therefore becomes
corrupted when JavaScript's unescape() function is used to restore the
value. This has been addressed.
SP2
PYRO-676
When performing a database upgrade on Linux, two threads would

attempt to run the database upgrade at the same time, causing
database upgrade failures. This issue is now fixed.
SP2
SFWK-2741
Automated failover of search federators improved.
SP2
SFWK-3013
Admin Server could fail to take control of processes on error recovery

startup on Linux or Solaris.
SP2
SFWK-3017
If configuration of Admin Servers had been corrupted (perhaps by direct

database changes), then a new search partition could not be created.
SP2
SFWK-3193
Admin Server could leave behind otadmin.pid files with large numbers
when running on interval schedule mode.
SP2
SFWK-3208
Memory leak in processing search results in drop-in corrected.
SP2
SFWK-3211
Potential stack overflow interpreting query language in drop-in

corrected.
99
SP2
SFWK-3234
Follow Shortcuts search feature does not work with Associated

Volumes.
SP2
SFWK-3256
Search results for Workflow Task Status items that are deleted but not
yet updated in the search index generate errors.
SP2
SFWK-3341
JavaScript error in search tools drop-down list on search results page.
SP2
SFWK-3448
SP2
SRCH-2258
Executing a saved search query may generate an SQL error with

Update 7. Known to affect WebReports.
Document Conversion Server terminating with Process Error 255.
SP2
SRCH-2274
Document Conversion Server terminating with Process Error 47 when

processes are recycled.
SP2
SRCH-2318
Time to recover from a DCS processing failure is slow with multiple

DCS processes on Solaris.
CST-209
Modifying the [email protected] user from within Content Server

resulted in the otadmin account being disabled. This is fixed.
CST-244
The Content Server auditing events now include audit information for
login events when using OTDS.
CST-251
Web Server Authentication is ignored when Directory Services

Integration Administration is configured to use Web Server
authentication and OTDS Authentication.
CST-255
When OTDS authentication is used, Workflow steps that require

authentication fail.
FLEX-269
Facet framework has been updated to support object hierarchies as

facet data sources (e.g. Classifications). This functionality won't be
available until future updates to modules like Classifications
LPH-864
When replying to an email sent as a notification of a topic or reply

posted in a discussion using My Mailbox, a returned email might be
received with an Invalid eLinkAlias message.
LPAD-10407
In previous updates, if the Content Server database is created in a MS

SQL Server that is configured to use the collation
"SQL_Latin1_General_CP1_CS_AS" with the language "English",
garbled characters will be inserted into multiple Content Server tables.
LPAD-23164
When a user is assigned a Task from a Task List, that user cannot
change the status of the Task. This has been fixed in update 7.
LPAD-28340
In Update 5, a change was made to the Category upgrade user

interface. Depending on browser cache settings with Microsoft Internet
Explorer, it was possible that Category upgrades would stop after the
first batch of objects was processed. This issue is fixed in Update 7.
LPAD-28762
The Distributed Agent Controller task uses a new status for preventing
a worker from picking up a task that it will retry/cancel. It also detects if
100
LPAD-28804
a worker picked up a task before it can set this status. Tasks update the
worker time column when they are worked on, which better detects
when a task has been running for 6 hours.
When using the SEA Servlet with NTLM or LDAP authentication in
Content Server 10.0.0, document uploads would fail because the
REMOTE_USER environment variable was not conveyed to the
StreamUpload request handler. This resulted in an error message such
as "Content Server Error: Error adding new item. [File
'C:\OPENTEXT\app\temp\lluplxxx.txt' does not exist.]". This is fixed in
Update 7.
It is required that the primary instance use the same Authentication
configuration and source (in LDAP). Document uploads are
authenticated against the primary instance again, and this only
succeeds when the user who is authenticated on the SEA instance can
be successfully authenticated by the primary instance.
LPAD-28823
If the list of items presented when selecting the "more" option of

promoted functions is longer than the list of items in the browse window,
the menu draws incorrectly.
LPAD-28855
The infrastructure for Distributed Agent complex tasks (job chains) is

updated to use a new structure to aggregate the statuses of children,
instead of using the status of the task. Complex tasks in core Content
Server (PopulateFacet, PopulateColumn) are also updated to make use
of this structure. The new structure prevents Reduce tasks from
returning an error if one of the child tasks experienced an error. If the
Reduce task itself fails, it will be retried or cancelled based on the
number of attempts. For backwards compatibility, if the new structure is
not in place, an error will be returned if a child failed.
LPAD-28863
The "Host to Replace" setting was added to the Configure Rendering

Settings page. This setting is used to determine when to override the
protocol/host/port in the request for generating links. If a request comes
in that matches the host name exactly, the replacement is performed. If
it does not match, no changes are made. If there is no "Host to
Replace" set, then no replacement is performed.
LPAD-28990
LPAD-29143
Storage provider rules that referenced attribute values were not

properly evaluated when using the functionality provided by the Content
Move module. This issue is now fixed.
Category upgrades skip objects with string data that exceed the
maximum length of a string field, or values that are not valid for popup
attributes. To prevent the objects from being skipped, their data must be
upgraded to be valid with the new Category definition.
101
LPH-775
When using the eLink module to send a document in email from a UTF8 system, if that document contained accented characters in its name,
the email would not be sent, and the agent thread would halt,
preventing any further emails from being sent. This issue is fixed.
LPH-768
The eLink module incorrectly processed Content-Type MIME headers

on incoming emails with document attachments, which resulted in the
system misnaming the objects created from those attachments. This
issue is fixed.
SFWK-706
A Database Verification could incorrectly report ChildCount errors in

Collection objects.
SFWK-2678
Personal Template folders can now be deleted without Admin rights

when the user is deleted.
SFWK-2744
Documents uploaded through remote cache do not have content

indexed if the Extractor processes it first.
SFWK-2898
Standard search results do not always order by relevance.
SFWK-2936
Advanced search page has JavaScript error with Dutch Language

pack.
SFWK-3007
Save search results fails if CheckNextURL is TRUE in opentext.ini.
SFWK-3017
Cannot create a new search partition after configuration of partitions

manually in DB.
SFWK-3099
Error selecting a minor version in search results if no major version

exists.
SFWK-3110
Admin Service crashes at startup when using Microsoft Cluster

Manager with Update 6.
SFWK-3178
TEMPO-265
Search panel displays extraneous < characters when Weblingo file

comments are enabled.
A new system GUID has been added to Content Server core. This
system GUID is stored in the KIni table and will be the same across a
cluster.
LPAD-28980
The Configure Rendering Settings administration page has a new

configuration option. Although the option can be configured, the
translation of its description will not be available until a future release.
LESAPI-1198
No MIME type was set when using CWS to upload a CSV file. To fix
this issue, add the text/csv mime type to the
<OTHOME>/config/mime.types file. This addition is included in the
<OTHOME>/config/config_reference/mime.types file.
LESAPI1223
Better error handling was added for invalid values found in the
Web.Config file. The following changes were made:
If the livelink.host value is missing an error will be logged. The

default of 'localhost' will be set with a warning message logged.
102
If the livelink.port value is missing an error will be logged. The

default of '2099' will be set with a warning message logged.
If the livelink.port value cannot be parsed an error will be

logged. The default of '2099' will be set with a warning message
logged.
If the livelink.port value is invalid (valid port numbers are in the

range 1 - 65535) an error will be logged. The default of '2099'
will be set with a warning message logged.
If the livelink.encoding value is missing an error will be logged.

The default of 'UTF-8' will be set with a warning message
logged.
If the livelink.encoding value cannot be parsed an error will be

logged. The default of 'UTF-8' will be set with a warning
message logged
LPAD-26521
A new feature, X-Forwarded-For, was added. This is a standard HTTP

header used by web proxies to track the path of requests over a
network. This feature allows Content Server to include the client's IP
address in Content Server cookies for added security by examining the
request path. The administrator can now add a list of trusted proxies.
The request path is examined and the first IP not in the trusted proxy
list is designated as the client IP.
LPAD-27488
When calling DAPI.UpdateNode with the changeModifydate flag's

setting of False, the Modify Date remains unchanged.
ROEX-19
OpenText Tempo External Users

Support for OpenText Tempo External Users was added. This allows
external users to be managed and displayed in the user management
area of Content Server.
LPAD-27339
LPAD-25513
This functionality is only available for customers who installed the

OpenText Tempo 10.0 module. For more information on OpenText
Tempo, please see the OpenText Tempo 10.0 release notes on the
Knowledge Center.
If the external file store was inaccessible during a database upgrade, it
was possible for the upgrade to fail, but appear to complete
successfully. Additional error checking was added to the database
upgrade routines to prevent this situation from occurring.
Printing is now available when using Internet Explorer and Firefox.
Chrome is not currently supported. The Content Server URL must be
added to the Trusted Sites within the Internet Explorer Internet Options,
and the computer must be restarted after installing the ActiveX control
on an Internet Explorer 64-bit server.
103
SFWK-2774
The default slice selection in the Search Bar is inconsistent.
SFWK-2755
Delete operations in environments that use Major / Minor versioning

may remove the wrong version from the index during a delete operation
where minor versions exist. This defect was introduced with Update 3.
SFWK-2448
The Extractor may incorrectly process objects in a PStage folder when

required attributes are applied.
SFWK-2260
In some circumstances, if the Search Region Map is not accessible, it is

presumed that it does not exist the region map is reset and a new
region map created. This can corrupt the configuration if the
inaccessibility was due to temporary file problems. The behavior is
changed to instead display an error message under this condition
SFWK-2241
If the Purge and Re-index feature was used with partitions that are not
in Read-Write mode, they would be deleted but would not accept reindexed objects. We now prevent this with an error identifying that the
feature does not work unless in Read-Write mode.
SFWK-1223
Search processes can now be deleted even if not associated with a

correctly configured Admin Server.
SFWK-2639
The Index Verifier could incorrectly report orphaned objects in the

search index in some situations with Enterprise Library Data Sources.
SFWK-2611
Index Verification reports folder can now be safely renamed.
N/A
Category Upgrade: Content Server restarts the Category upgrade from

the point where the process was aborted. Previously, an interrupted
Category upgrade process (for example, from a user abort or system
restart) had to be restarted from the beginning.
N/A
The pop3client.dll was updated to resolve an issue where, under

certain conditions, a loop index could go out of bounds and lead to a
memory violation causing the service to crash.
LPAD-26380
Performance Improvement: Removal of items from DSuggestWords

was updated to handle deletions similar to updates to improve
performance and reduce database contention.
LPAD-26761
The MailMessage.GetMultipartContent API call incorrectly decoded

base64-encoded binary data and returned that binary data as a string.
This caused problems if the binary data contained any NULL bytes. As
of Update 5, the data is returned as a base64-encoded string.
LPAD-23926
The change in Update 5 to allow category upgrades to be restarted

replaced the CatUpgradeRefs2 WebNodeAction with a new request
handler. References to that action can be replaced with a call to the
attributes.InitUpgradeCategoryRefs request handler. The same
104
arguments will be accepted, although the UrlToPop parameter will be

ignored by the new request handler.
5
LPH-748
Attempts to send email encoded messages using an ISO-8859-1

encoding to a UTF-8 system resulted in garbled messages being
imported to Content Server. As of Update 5, the system converts
incoming messages from ISO-8859-1 to UTF-8 before creating objects
based on the messages. UTF-8 systems support incoming messages in
either ISO-8859-1 or UTF-8 encoding.
SFWK-2090
Removing an Admin Server assigned as the Disk Image Creation

server left the Make Disk Image feature non-functional.
SFWK-2248
A problem was introduced with Update 4 that could cause a redirect to

an error page when selecting User Help pages from search results.
SFWK-2260
Previously, if the Search Region Map could not be read in a timely

manner, it was reset and a new one was created, losing the settings.
The behavior has been changed to display an error message on the
Region Map page.
SFWK-2372
Performance Improvement: The search drop-in previously used two

connections in a query with Hit Highlighting. Hit Highlighting now
reuses the connection from the query, reducing the threads used in the
search engines and correcting search timeouts that may occur when
only one thread is available.
LESAPI-166
A new boolean property, FollowAliases, was added to the

ExportOptions SDO. This allows the XML Service to follow aliases
(shortcuts) when doing an export.
LESAPI-997
Trying to update a workflow's form data using the

WorkflowService.UpdateWorkItemData method would result in a script
crash. This has been fixed to properly handle these updates.
LPAD-25405
If the sort order is changed when browsing a container (for example, a

Folder or Project), and a request is made to edit the properties of an
object in that container, the sort order is retained when returned to the
Browse View.
LPAD-26373
In previous versions of Content Server, Content Server expected an

Assoc data type from the KUAF tables UserData column. If the
structure of the entry was not of Assoc type, a trace file would generate
that contained user sensitive data. This issue is now resolved and trace
files are no longer generated because of a wrong data type error.
LPAD-26516
In Content Server 10.0.0 plus Update 3, deleted files cannot be

restored after the Multilingual Metadata language is disabled. To
105
resolve this issue, you must enable the Multilingual Metadata language,
restore the file, and then disable the Multilingual Metadata language.
4
LPAD-26551
Issue in multipart/form-data forms where only the first 1Kb of data is

visible, which causes a null character to be inserted between each 1Kb
data segment.
LPAD-26893
Solaris platform only: The View as Web Page functionality is not

enabled by default for Content Server 10.0.0 Plus Update 4. To enable
the View as Web Page functionality, you must have the following
parameter in the [options] section of the opentext.ini file:
wantHTMLView=TRUE
Regions cache gets out of sync between threads / servers.
SFWK-1971
SFWK-2056
Single quotes in strings on some pages not correctly escaped, resulting

in Form submission failures.
SFWK-2092
Initial Search By Default regions cannot be set to Queryable or

Displayable.
SFWK-2128
Creating an XML Activator Consumer creates a Producer instead.
SFWK-2184
Multilingual Slice names now displayed in query forms.
SRCH-1478
ANSI files with Shift-JIS encoding are not searchable.
LESAPI-844
Content Web Services: In Content Server Update 2, a new feature was

implemented that allowed modules to add additional NodeFeatures for
different node types. The support for this feature was missing for
GenericNode objects (OScript object types without a ServiceNode
definition). This is now fixed.
LESAPI-851
Anyone who has deployed the Java web services will have to re-deploy
the les.services.war file with the updated one that is included in the
patch.
LPAD-24631
In configurations where Content Server is behind a load balancer or

proxy, the base HREF setting in a Custom View page's HTML header
may not match what is needed by the user's browser. To rectify this,
three KIni settings have been created in the [BaseHref] section of the
opentext.ini:
Protocol: The scheme section of the base HREF URL. Should be either
"HTTP" or "HTTPS"
Host: The hostname of the server to include in the base HREF URL
106
Port: The port of the Web server used in the base HREF URL
The three settings are optional. If a value is not present, it will default to
a value in the HTTP request. These values can be set on the Rendering
Settings administration page or by adding a value to the [BaseHref]
section of the opentext.ini file.
3
LPAD-26066
There are installation issues when installing eLink with Content Server
Update 3. To resolve this, follow the normal patching process to apply
the patch. From the Content Server root installation directory, move the
"elink_10_0_0" directory from "Content_Server_Home\module" to
"Content_Server_Home\staging" (where "Content_Server_Home" is the
root installation directory) and overwrite the current contents of eLink in
the "staging" directory when prompted.
SFWK-1442
It is now possible to apply Hit Highlighting for objects retrieved over

HTTPS.
SFWK-1500
For security and performance reasons, users are generally presented

with an estimate of the number of search results. The computation of
the search results has been changed with Update 3.If the total number
of raw search results is close to the number of results needed to display
the current page of results, Content Server will fetch all of the search
results and compute an exact count. The result-estimating algorithm is
adaptive. The algorithm has been changed to update probabilities once
per day instead of after every search query. This means that users
performing the same search and obtaining the same results will now
see a stable estimate of the total number of results. There are now two
configuration strings for formatting search results in the Result Count
Template portion of the Configure Search Options administration
page. The new string is used when the exact count is known.
SRCH-847
Some customers noted that incorrect HTML files that lack character
encoding statements do not index all extended characters correctly. In
some cases, updates to the dcsrules.txt file may fix this problem.
LPAD-25196
There are two performance improvements for Facets: (1) If a

memcached check fails, it does not return an error; the error is logged
the memcached check continues by getting the data from the database.
(2) Facet keys that are not found in the memcached are stored so that
the next time a memcached check is performed it does not have to
search the database. This improves performance.
LPAD-25160
Prior to Content Server 10.0.0, Update 2, Global Appearances were not

supported for XML Import. If Appearances were imported prior to
Update 2, the new memcached mechanism used to cache
107
Appearances through and XML import will generate unexpected results.

After the additional components and content are added to an
Appearance during XML Import the memcached is marked dirty, and
forces a recapture with the imported Appearance.
3
N/A
If an error resulted from attempting to retrieve column properties from

the database, that error would not be handled correctly. The value
returned from capi.exec apiError = checkVal.ApiError was changed to
apiError = checkVal. This issue is now fixed.
DCS-3051
When the UseContentReference parameter in the opentext.ini file is set

to TRUE, Open Text Document Filters skipped archived content and did
not index the content in the body of an email.
LPAD-24695
When adding a custom column, a new database column is added to the

WebNodesDisplay or WebNodesFilter table, depending on whether
sorting is permitted on the column. If a previous attempt to create the
custom column failed, it is possible that the database column was
added to the table regardless of the failed attempt. In this case, the
system will attempt to reuse the column instead of trying and failing to
add a new column with the same name.
LPAD-24841
When browsing containers (Folders, Projects, etc.) for which Facet

counts are not yet calculated and cached, the Content Filter display is
delayed on a page load. The Content Filter displays "Loading content
filter...", and the Facet counts are displayed after they are calculated.
This allows the rest of the page to load without waiting for the Content
Filter.
LESAPI-780
The Document Management Service's ListNodes and

ListNodesByPage methods did not return the same set of nodes for
node types with associated volumes (Discussions, Projects, Compound
Documents, etc). The following changes were made:
ListNodes and ListNodesByPage now return the contents of the node
ID given and if that node has an associated volume then the associated
volume contents are returned.
ListNodes and ListNodesByPage now return the children of Compound
Documents in the correct order (the order specified in the Compound
Document).
In prior versions, some node types (Compound Documents,
Discussions, Personal Workspace, etc.) would ignore page size when
using ListNodesByPage and return all nodes in the first page.
108
ListNodesByPage paging is now forced regardless of the node type's

default behaviour.
3
LPAD-20210
XML Export of Workflow Maps generated invalid export files and could
cause the Content Server service to fail due to the removal of a
serialization method required to serialize the maps upon export. This
method was added to Content Server 10.0.0 so that maps are
serialized correctly.
LPAD-24515
An upgrade step causes the Facet and Column caches to be truncated

and rebuilt. DFacetKeys and DFacetCache are truncated. This was
necessary to support the internal data structure changes that were
made to Facets for bug fixes and performance improvement.
LPAD-24581
Additional error checking is included to prevent trace files from

generating when nodes are filtered through FilterNodes() and
notifications were requested on the filtered node. Also, if the node that
has an interest identified is a container and gets filtered out in
FilterNodes(), a message is no longer generated.
LPAD-25315
If users customized their desired UI languages on the Personal Settings

page, the customized languages did not appear.
LPAD-25420
When adding a custom column, a new database column is added to the

WebNodesDisplay or WebNodesFilter table, depending on whether
sorting is permitted on the column. If a previous attempt to create the
custom column failed, the database column may have been added to
the table regardless of the failed attempt. In this case, the system will
attempt to reuse the column instead of trying and failing to add a new
column with the same name. In previous versions, adding a custom
column that previously existed could cause an error.
LPAD-25552
Incorrect items committed counts were logged in thread logs for

Workflow extractions.
LPAD-25728
Workflows that contain Item Handler steps could not be initiated by

anyone but Admin users due to ItemHandler restrictions that were set in
Update 2.
LPAD-25873
SFWK-1692
When using a Workflow Process step to copy multiple attachments and

create new versions of documents in Content Server, some of the
metadata (e.g. file name, MIME type) of one document could be applied
to another document.
Non-document objects not being deleted from Index. Index verifier can
be used to fix after Update is applied.
SFWK-1856
DeleteByQuery for full node deletes did not extract sufficient data from
the Search Index of email messages from the Email Services module,
109
and also Search Index Verification for email objects. These issues are
now fixed.
Change in behavior for the CS 10 advanced search page, ensuring that
an Exact Phrase search is performed when specifying search criteria
for category attribute pop-up types. ()
SFWK-1452
LPAD-23779
New files uploaded to the archive storage provider will now have their
file creation and modification dates set correctly in the version data.
SFWK-1516
It was found that the query used to Collect all Search Results did not
faithfully reproduce the original query during the collection. If an explicit
[region OTData] someterm statement was in the original query, this
term would be dropped during collection. This will happen if a term is
applied against content only. If you construct complex queries for
collections in this way, you may need to re-generate the collection to
get accurate results
LPAD-7034
When suspending and modifying a route of a workflow instance, the

evaluate step is getting modified when it should not.
LPAD-3991
If you perform a phonetic search (that is, sounds like) search on a

phrase, Content Server processes the query as a phonetic search on
the first largest in the phrase.
1940923
0
LPAD-10163
Generation option is available for workflows but does not work. Should
not be an option and has been removed from the list.
LPAD-16145
Assigning users by attributes are not updated after loopback.
LPAD-17250
Search bar, Global Menus, and Content Server title missing from the
workflow attachments page.
LPAD-19727
User cannot manage workflow when they are a part of a group that is
assigned management permissions.
LPAD-19791
Workflow bug with Enable Action Email option on workflow user steps.
LPAD-19895
Item Handler step does not audit changes made to category attributes.
LPAD-19993
Display attachments button code no longer works within Content

Server.
LPAD-21076
Emailing attachments to an email-enabled does not work for .msg

attachments. No failures are noted; however the .msg attachment does
not show up in the workflow attachments volume. Emailing other
attachments that are not .msg files (.doc, .txt, .pdf) works correctly and
they end up in the workflow attachment.
LPAD-21428
Workflow infrastructure does not validate IDs specified for roles when
starting a workflow.
LPAD-21528
It is possible to modify page content from the work.workflows request.
110
SFWK-477
The Metadata Integrity Checksum feature of the Index Verifier does

not reliably detect all index integrity errors.
SRCH-690
Uppercase Russian characters are not properly mapped to lowercase

characters, making search case-sensitive.
111
16 Appendix G Configuration File Changes

Some features of Content Server, DCS and Search Engine 10 are managed through configuration
files. This section outlines changes that are implemented or recommended with each Update. In
some cases, configuration files cannot be changed automatically due to the potential for conflict with
customizations to your particular site. 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 as part of an
Update, since replacing the files would overwrite any customizations previously made. The latest
versions of the configuration files are placed in a reference folder where you can review them and
consider selective replacement or edits to your installed configuration files. These files are located in
the Content Server directory <OTHOME>\config\config_reference. The table below shows the
Content Server 10.0 Update in which each of the configuration files was last changed. If the update
is being applied to a new installation, then these files should be copied to the
<OTHOME>\config directory before indexing any data.
File
dcsrules.txt
dcsviewrules.txt
dcs.ini
LLFieldDefinitions.txt
LLFieldDefinitions_EL.txt
Opentext.ini
htmlToOTTag.mapping
Windows
Update 11
Update 6
Update 2015-12
Update 3
Update 3
Update 2015-06
Update 2016-06
Solaris
Update 11
Update 6
Update 2015-12
Update 3
Update 3
Update 2015-06
Update 2016-06
Linux
Update 11
Update 6
Update 2015-12
Update 4
Update 4
Update 2015-06
Update 2016-06
16.1 Update 2016-06

1. htmlToOTTag.mapping - Fix for issue DCS-8282 DOCX - OTDocStatus region not populated
because contentStatus property is not extracted from core.xml
Add OTDocContentStatus=OTDocStatus to the #General Mapping section. For
example:
# General Mapping
OTDocCreationDate=OTDocCreateDate
OTDocCreationDateDate=OTDocCreateDate
OTDocCreationTime=OTDocCreateTime
OTDocCreationDateTime=OTDocCreateTime
OTDocAppName=OTDocNameOfCreatingApplication
OTDocCreator=OTDocNameOfCreatingApplication
OTDocProducer=OTDocNameOfCreatingApplication
OTDocCharCount=OTDocNumberOfCharacters
OTDocPageCount=OTDocNumberOfPages
OTDocPages=OTDocNumberOfPages
OTDocContentStatus=OTDocStatus
112
16.2 Update 2015-12

2. Dcs.ini - Fix for issue CMSD-5010 Unexpected counts reflected with File Type Search Filter
with Contract Folders and Folders
Remove 207 from the STMapping setting. For example:
STMapping-81108,207,31108
is changed to
STMapping-81108,31108
16.3 Update 2015-06

1. Dcs.ini - Fix for issue SRCH-3972 File Types are not defined for Office 2013, dwfx, mp3, wave,
xgl, indesign,and OJT
ID=70,Oce Job Ticket
ID=104,Autodesk Design Web Format
ID=105,AutoCAD DXF
ID=162,Software Symbolic Link
ID=336,Esri Shapefile
ID=337,Data Interchange Format
ID=338,Personal Computer Exchange
DetectMapping=569,70
2. Opentext.ini - Added support for rolling Log Files. To enable add the following entry to
[general]
LogConfigPath=[OTHOME]\config\contentserver.logging.properties
113
Modify the contentserver.logging.properties file as follows:

opentext.logfile=ON
opentext.logfile.enableconnect=ON
opentext.logfile.loglevel=TRACE
opentext.logfile.enablerollinglog=ON
opentext.logfile.maxBackupIndex=5
opentext.logfile.maxFileSize=100KB
16.4 Update 11
The dcs.ini file has been extended to add File System Archive folder types 790 and 793 to the
OTFileType definitions. Appended line exec ConvertAttachments to dcsrules.txt for the MSOffice
processing case to address SRCH-2822.
16.5 Update 10
The DCS.ini file has been extended to define a number of RM and Case Management SubTypes for
the OTFileType region.
16.6 Service Pack 2

1. The default configuration in the dcs.ini file now enables language detection.
16.7 Update 7
1. The configuration settings for DCS are now represented in a set of configuration files. Details
about this new system will be published on the Knowledge Center, accessible through the
document DCS Series Overview.pdf.
o Any configuration setting in opentext.ini used exclusively by DCS can now be placed in
the DCS.ini file. In future releases, these settings will be removed from opentext.ini.
o A new configuration file named custom_dcs.ini is now available which should be used if
you need to modify any DCS.ini settings. Future Updates may replace dcs.ini, but will not
modify your custom_dcs.ini file.
o A new configuration file named application_dcs.ini may now optionally be used by
applications that wish to modify DCS.ini settings during their installation. This file has
higher precedence than dcs.ini, but lower precedence than custom_dcs.ini.
114
16.8 Update 6
1. The dcsrules.txt had an unknown case removed.
2. The dcsviewrules.txt file has some View as Web Page corrections for Solaris and Windows, and
some hit highlighting corrections for Linux.
3. The dcs.ini file was updated to make minor corrections and improvements to file format
mappings, and added codes for the new OTContentStatus feature.
4. Linux Red Hat customers that are applying the Update 6 patch will need to make the following
changes to the opentext.ini file:
[DCS]
modx10=DCSIm
[DCSView]
modx10=DCSIm
[DCSIm]
lib=dcsim
outputoleinfo=true
dllpath=ContentServer_home/filters/image
x-timeout=30
16.9 Update 4
1. DCS Rules File. Changes in the dcsrules.txt and dcsviewrules.txt files are recommended. Before
applying these changes, review them against any customization you may have already made to
these files. For convenience, a suggested reference implementation of these files is contained in
the <OTHOME>/config/config_reference directory. You should check the dcsrules.txt and
dcsviewrules.txt files, and if the values exist, change:
IMMimeTypeFormatId to OTMimeTypeFormatId
16.10 Update 3
1. Some errors in the search index field type definitions were found. For new customers, the
LLFieldDefinitions.txt file has been updated. Upgrades (applying Update 3) do not supply an
updated LLFieldDefinitions.txt file, and hence the settings remain unchanged. For most
customers the impact is minimal. Customers with new installations since Update 0 who use
Records Management (RM) and who search on the affected RM fields may wish to address this,
and should contact Customer Support for assistance. Incorrectly typed regions and their
recommended new values in the LLFieldDefinitions.txt file are:
ENUM OTDCategory (used to be INTEGER)
ENUM rmEssential (used to be BOOLEAN)
ENUM PHYSOBJTransferID (used to be #TEXT)
INTEGER PHYSOBJMediaTypeID (used to be ENUM)
115
INTEGER rmPartID (used to be #TEXT)

#TEXT
#TEXT
#TEXT
#TEXT
#TEXT
#TEXT
#TEXT
PHYSOBJCurrentLocation (used to be ENUM)

PHYSOBJDefaultLoc (used to be ENUM)
rmSupplementalMarkings (used to be ENUM)
rmRSI (used to be ENUM)
rmXreg (used to be ENUM and also used to be misspelled rmXref)
rmClassRSI (used to be ENUM)
rmHolds (used to be ENUM)
Completely removed:
#TEXT PHYSOBJterms
#TEXT PHYSOBJTransferID
#TEXT PHYSOBJPartyName1
#TEXT PHYSOBJPartyName2
#TEXT rmPartID
Note: in the LLFieldDefinitions.txt file, there should be exactly one TAB character between the
type definition and the region name
2. Updated dcsrules.txt A new version of dcsrules.txt is installed with Update 3. If you have
customized this file or installed a module that changes this file, you should review your custom
changes and re-apply them to the new version of the file as appropriate. The most common
customizations would be the application of OpenText Filter Pack or the third-party Brava filters.
The change prevents attempts to index content from which the filters cannot extract text, which
reduces the amount of poor quality content in the index.
This was accomplished by removing the following two lines from the standard dcsrules.txt file:
case OTMimeType = "application/octet-stream"
try CharEncoding, PruneDoc
3. To support new features of DCS and indexing, an additional search region will be added to the
search index to accommodate language data. Existing installations with Update 2 or earlier
applied should edit their LLFieldDefinitions.txt files to add the following entry before starting the
index engines and indexing data:
ENUM OTContentLanguage
Failure to make this change will result in the new language data being stored as type TEXT in the
index instead of enumerated types (ENUM), which will not result in loss of functionality, but will be
less efficient in terms of memory storage. New installations of Content Server 10 including
Update 3 will have this automatically included.
116
4. The type definition for OTFileType is incorrect in the LLFieldDefinitions.txt file. This should be
changed before the search processes are started for the first time. The correct definition is:
TEXT
OTFileType
Note that exactly one tab character is required between the TEXT and OTFileType entries.
117
17 Appendix H New Features

This section outlines new features included in Content Server 10. Where Updates introduce new
features, they are detailed here.
17.1 New Features Update 2015-12

1. Database Correction. A new utility has been added to the Database Maintenance correction that
will identify orphaned items (those without a Parent ID) and move them into an Orphaned Item
volume. From there, they can be inspected and manually moved to a suitable location.
2. Auditing. A new auditing interest was added to control auditing the creation of attributes during
object creation. Previously, these events were always audited as attribute create/change events.
This feature was added to help manage audit record size.
3. Database Verification: A "Relocate Orphaned Items" option was added to the Test or Repair
Known Database Issues admin page to assist with database verification errors related to objects
with invalid ParentIDs (i.e., orphaned items). This utility will re-parent items into an Orphaned
Items Volume, where administrators can review and remove items as needed. The utility allows
for the cleanup of many SubTypes, although some SubTypes may require additional effort in
order for Content Server to allow for their deletion. Please contact OpenText Customer Support to
work through any special cases.

1. Components of an eLink email notification message that do not reflect multilingual metadata
elements are now sent to the recipient in their preferred UI language. Multilingual metadata
field values that are exposed in eLink emails (Name and Description) will be presented in the
System Default Language.

2. Windows 2012 R2 and Oracle 11g R2 11.2.0.4. Support was added for Windows 2012 R2
with Oracle 11g R2 11.2.0.4.

3. Firefox ESR Version 31 Support. Support was added for Firefox ESR Version 31.
4. SQL Server 2012 SP2 Support. Support was added for SP2 of SQL Server 2012.

5. IE 11 Support. Support was added for Internet Explorer 11.
118

1. OTDS. When a third-party Web Access Management product (e.g. CA SiteMinder, Entrust
GetAccess, etc.) is used to authenticate a user for Content Server, and the authenticated user
logs off the third-party product, their Content Server session remained active. An additional
check was added to ensure the user is still defined in the configured environment variable.
2. Workflow Volume. Paging is now supported when browsing the Workflow Volume. This
improves the response for Administrators. This setting is configured as part of the global
pagination setting in the Pagination section of the Configure Container Options page. To
access this page, click the Configure Presentation link in the Server Configuration section
of the Content Server Administration page.

1. Collection Processes: Long-running collection processes can be reviewed by Admins on the
Collections General Settings page.
2. Collection Confirmation: Users are now challenged with a dialog when performing actions
from a Collection that may delete or modify objects.
3. LQL Quotes: Additional quotation mark character types are now allowed in the construction
of search queries, such as smart quotes as used in Microsoft Office.
4. EML: A filter for extracting text from email messages in .eml format is now available for use
with search indexing.
5. Database Verification: A new page is included that can host specific detection and correction
of known database verification issues.

1. REST API. Content Server 10.5 includes a REST API. In general, the RESTful API model is
noted for simplicity of use and understanding by developers. Specifically, REST APIs are what
have become expected by developers that need to build mobile or web browser applications
that interact with a remote server application.
2. Workflow. Workflow Painter shows the task id of step in the map view and when editing step
properties. Steps with identical titles now can be distinguished.
3. Retired Partitions: Search partitions can now be marked as Retired. When used in
conjunction with new partitions, this feature allows multiple older partitions to be re-indexed
into larger Low Memory Mode partitions.
4. Dataflow Distribution: This new feature allows a dataflow to be distributed among multiple
DCS instances, providing more options for constructing high performance indexing
processes.
119
5. Search Filter Memory Allocation: New configuration setting that allows additional memory
to be allocated to Search Engines, most notably required for search facets. Default is 40 MB.
6. Extractor Statistics Gathering: Extractors now collect statistical information about their
performance, retained for 7 days. This information will be used in future reporting tools.

1. Extractor Enhancements. There are now independent controls on the Extractor General
Settings page for each extraction type. These allow you specify the number of each type of
item for every extraction run. Pause and Discard controls provide further control over the
extractor behavior. Improvements have been made to the indexes on DTreeNotify to improve
Extractor performance.
2. Document Management: The metadata language configuration interface now allows
selection of database collation for each language.
3. Reset Region Map. A new button on the Region Map page allows an administrator to set the
search region map to default values. This is a last recourse maintenance feature if the region
map is damaged.
4. Sysreport Enhanced. The SysReport now includes a user-friendly name for SubTypes and
information about the LLSystemData table. The tabular layout of KINI is also improved to
remove trailing padding and improve performance when long KINI values exist.
5. Search Configuration. New Search Engine configuration settings are exposed in the
Search Admin pages. These allow for:
control over the Update Distributor batch size

setting the trigger points for when the Index Engines should write checkpoint files
limiting parallelism for Index Engines writing checkpoint files
6. OTDS. You can now specify a different host name to redirect users for OTDS Authentication.
This is frequently required when a Content Server instance is deployed in a DMZ for Extranet
access.
7. Domains. The following methods were added to MemberService:
GetUserByLoginNameInDomain(), which allows you to retrieve a user in a domain by their

login name.
GetGroupByNameInDomain(), which allows you to retrieve a group in a domain by its group
name.
8. Custom Columns. Multi-line text attributes can be used for Custom Columns.
120
9. Sorting. Facets, with the exception of Date-type Facets, now support configuration of
different Display Modes. The Display Mode determines the order that Facet values are
displayed, and is configured on the Facet's Specific Properties tab.
The available options depend on the type of the Facet, but in general the options are "Ranked list"
(the default) to sort by the count for each value, and "Alphabetical list" to sort by the values
themselves.

1. Return to Last Search Results. A new feature of the search bar, selecting the Last Results
link will perform a search for the last query, to the last page of results. This helps users
performing search-driven functions continue from the last used search page. This feature is
enabled by default, and can be disabled on the search bar configuration page.
2. Recycle Bin and Records Management. When upgrading to Content Server SP2 Update 11
and have installed the Recycle Bin and/or Records Management modules, you must install
the Recycle Bin 10.0.1 and Records Management 10.2.0 Update 2 modules (including
Records Management, Physical Objects, Security Clearance, and Classifications). If you
attempt to use older versions of these modules, Content Server will prompt you to update to
the latest versions. For a new installation of Content Server 10.0.0 SP2 Update 11 with
Recycle Bin or Records Management, you must download Recycle Bin 10.0.1 and/or Records
Management 10.2.0 Update 2 modules (including Records Management, Physical Objects,
Security Clearance, and Classifications).
3. Deleting: A new node parameter named "fIsRecyclable " has been added LLNode object.
The purpose of this new parameter is to determine if the node can be recycled.
4. Distributed Agents. Improvements were made to Distributed Agent performance and
reliability. To apply these changes, the upgrade process must modify and migrate data
between Distributed Agent tables. Because this process can take several minutes in large
tables, you should check the amount of tasks in your Distributed Agent prior to starting the
upgrade.
The best way to verify the amount of tasks is to check the amount of records in the
WorkerPackages table. If it has more than 1 million records, you should wait for those tasks to
complete before starting the upgrade process.
5. Custom View Ordering. If there are multiple custom views or custom view search forms
defined for a single folder, this feature uses the priority field to determine the priority for
display. For custom view search forms, this also determines the default search form and the
ordering of search forms when selecting from a list. This feature is accessed through the
function menu for the folder.
6. Partition Names. The internal name used to identify a search partition is now displayed on
the Specific Properties page for the partition. This can be used in conjunction with the new
search engine feature allowing search within specific partitions. For example, with complex
query in advanced search: [qlregion OTPartitionName] server1-333455x38477x999.
121
7. Search Statistics. The Collection of search stats has been improved to capture additional
search sources, and provide better granularity for search sources. New sources include
Enterprise Connect simple search, Enterprise Connect advanced search, Enterprise Connect
Custom Search Forms, Custom View Search Forms, and executing Saved Search Queries.
8. Content Web Services. The following methods have been added to the MemberService:
CreateUserInDomain(), which allows for the creation of a new user in a Content Server
Domain, if Domain support is enabled; and CreateUser(), which allows for the creation of a
new user in Content Server and is a better alternative than the generic CreateMember()
method.
9. Content Web Services. The following methods have been added to MemberService:
CreateGroupInDomain(), which allows for the creation of a new group in a Content Server
Domain, if Domain support is enabled; and CreateGroup(), which allows for the creation of a
new group in Content Server and is a better alternative to the generic CreateMember()
method.
10. Content Web Services. A new CreateDomain() method has been added to the
MemberService. This method allows for the creation of a new Domain in Content Server if
Domain support is enabled. A new Domain SDO has also been added to represent a Domain.
The Domain SDO inherits from the Member SDO, similar to User and Group.
11. Content Web Services. A new DOMAIN option has been added to the SearchFilter enum
SDO in MemberService. This option allows you to search for only Domains when using the
SearchForMembers() method of the MemberService.
12. Auditing. If the "Disable Audit Purge" setting is enabled, users will no longer have access to
the "Purge Audit Log" functionality, either from the UI or through a URL. If the "Lock Audit
Interests" setting is enabled, the "Set Auditing Interests" page becomes read-only and users
will no longer be able to modify these settings. If the user installs a module that creates their
own event interests, they will be displayed on the page, but the user will not be able to modify
the default values.
These features are not reversible. Extreme caution should be used when deciding to enable
these features. Also, the audit log could become large, which may impact performance. New
features that are added to new/upgraded modules may not be audited if new interests are added.
13. LiveReports. A new option called "Configure LiveReports Security" was added to the
LiveReports Administration section on the Content Server Administration page.
The page provides an option to permanently disable the ability for all LiveReports to modify
the database. If enabled and saved, this action is not reversible.
If the ability to modify the database has been locked out by the admin, then the option "Allow
Database Modifications" on the create/edit LiveReports page will not be present and any preexisting values will be ignored.
14. Str.Join. A new built-in in the Str package was added, named Str.Join. It behaves in a
manner identical to Str.Catenate, except that it doesn't add the delimiter string to the end of
122
the output. E.g. Str.Catenate( {1,2,3}, "=-" ) -> "1=-2=-3=-", while Str.Join( {1,2,3}, "=-" ) ->
"1=-2=-3".

1. Additional Login Policies. For the Web Admin password, new login policy restrictions allow
a temporary lockout to be imposed and the administrator notified if too many failed password
attempts occur. For the Admin password, a new login policy can alert the Admins if too many
failed password attempts occur. (LPAD-24617)
2. FixType Utility. This utility for applying OTFileType values to existing search indices was
previously only available with a complete install, but is now also available in an Update.
3. Template ID. You can now specify the default search form to be displayed on the Advanced
Search page by setting the optional URL fragment &templateID=12345, where the number is
the node ID of the desired search form.
4. Storage Provider. By default when copying to and from the External File Store, the file buffer
size used in the copy action is 16 KB. This change allows the buffer size to be specified. It
can be set in the Configure Performance Settings of the Server Configuration administration
page and will be stored in the opentext.ini. The new default value is 500 KB and will decrease
the time to copy files.
5. Multi-file Print. The multi-file print functionality now supports the ability to print to a specific
printer. The Print to Default button will print to the default printer. The Print button will prompt
the user to select a printer and use it to print the selected documents. The ability to print a
given document type, either to the default printer or a specific one, depends on the
configuration of the client operating system for that type.
6. Configuration. By default, the CGI will put a value representing how long the CGI processes
the request before it forwards the request to llserver. This value is taken into consideration by
llserver when it checks whether the user's cookie is expired or not. If the user wants to disable
this feature, in opentext.ini, under the "Client" section, add
AddRequestProcessDuration=FALSE
If the user wants to enable this feature, we also provide encryption of this value to make it more
secure. However, using encryption degrades the CGI's performance. By default, encryption is not
used. To use encryption for this value, in opentext.ini, under the "Client" section, add
EncryptRequestProcessDuration=TRUE
To encrypt the value, a default encryption key is used. To use a different key, in opentext.ini,
under the "Client" section, add
EncryptDurationKey=mynewkey
7. Distributed Agents. Some changes have been made to Distributed Agents to improve
performance and stability. The database schema has been updated to remove unnecessary
123
table columns and update indexes for performance reasons. No changes are required to
modules that use the Distributed Agents API.
8. Workflow. The Workflow Painter Java applet is now updated to be a signed applet.
9. Workflow. The Workflow Agent now uses the Distributed Agent framework. This results in
changes in the configuration of the Workflow Agent.
If FIFO order is enabled, the Workflow Agent processes tasks in a serial way. In order to increase
the throughput, the FIFO order should be disabled in the Workflow Agent administration page.
The Workflow Agent will then use Distributed Agents for parallel processing (new behavior).

1. Search Auditing. Auditing of creation, change and execution has been added for Saved
Search Queries, Search Templates and Save Search Results. (SFWK-3322)
2. FixType Utility. A utility is included in the <OTHOME>/utilities/fixtype directory (full install
only) that allows the OTFileType metadata field to be generated or corrected for existing
indexed objects. This utility should only be used when the indexing process is disabled
(Extractor is disabled and no IPool messages are pending). OTFileType is an important
metadata value for search filters and search usability.
3. Low Memory Text Metadata Mode. A new method of storing text metadata on DISK in the
search engine is available with Update 9. The traditional DISK storage method stores the
metadata values on disk, and the metadata index in memory. The new Low Memory mode
stores both the search index and the values for text metadata on disk. Low Memory mode
typically allows more than 3 times the number of objects to be stored in a partition of a given
size. Low Memory Mode is enabled on the Specific tab of the Partition Map page, and
disabled by default for backwards compatibility. Changing the Low Memory Mode setting will
require a restart of the Index Engines, and may require several minutes per partition for
conversion of the data. Note that switching from Low Memory mode back to traditional mode
may not be possible if the number of objects in the partition exceeds the capacity of the
traditional partition size. You are strongly advised to create a backup of the search index
before first using the Low Memory Mode. (SFWK-3630).
4. Search Filters. A new control on the search filter admin page allows administrators to
suppress the display of counts beside values for users without search bypass permissions,
optionally based on the count value. Since counts are estimated, the counts can be
misleading, especially for small estimates. Labels for the common values of the OTFileType
region are now localized in search filters. (SFWK-3538)
5. Search Process Memory Limits. Investigation revealed that Java may unexpectedly
consume large amounts of heap memory if left unspecified on the command line. For new
Data Sources, default heap memory limits of 64 MB are now specified for Help data source
Search Federators and Update Distributors, and 256 MB for all other types of data sources.
For existing Data Sources, it is recommended that you set the Max Process Memory Usage
values on the Specific Information properties tab. (SFWK-3604).
124
6. DCS Variable Timeouts. A variable timeout capability has been introduced that allows DCS
to extend the time available for filters to process large files. By default, this is disabled with a
value of 0. In the DCS.INI file, the setting is: ExtraSecondsPer10MB=10 (SRCH-2539).
7. Location Depth feature has been added, in which DCS assigns the distance from the root
location as an integer. This can be used for relevance scoring. For Content Server objects,
the depth is based on the number of values in the OTLocation metadata, for crawled objects
the file path or URL are parsed. This integer is placed in the field OTLocationDepth. (SRCH2529).
8. Zero Size Files. Where files of size zero are presented for indexing, DCS will now try to
attach file type metadata for some of the most common applications based on the file name
extension.
9. Log-out and Change Password options now appear under the Tools menu of Content Server
when OTDS integration is enabled.
10. AddToCollection() and RemoveFromCollection() methods were added to the CWS Document
Management Service.
The AddToCollection() method allows you to add items to a Collection.
The RemoveFromCollection() method allows you to remove items from a Collection.
A new CollectionItem SDO has been added to represent an item in a Collection.

11. LiveReports. LiveReports can be executed using a new Web Services call, which returns the
same results as running the LiveReport through a browser.
12. The "Force auditing of all events performed by System Administrators" check box was added
to the Set Auditing Interests page. When the check box is selected, any auditable actions
performed by users with the System Administration privilege will be audited, regardless of the
other audit interest settings.
13. An additional Audit Administration setting was added, which enables the Admin user to restrict
the ability to change audit interests and purge the audit log to only the Admin, instead of any
users with the System Administration privilege. The Audit Security Settings page is accessed
from the Administer Event Auditing page, and the setting is labeled 'Limit Audit Config to
"Admin" User'. By default, this setting is "off" (which means that any user with the System
Administration privilege can access the Audit Configuration settings).
14. The Target Browse dialog, which is used to select items within Content Server, has been
enhanced with the addition of a search box. This box allows a user to search for objects at or
below the current folder level in Content Server. The search is a wildcard search against the
name of objects in the user's preferred language.
15. When copying or moving objects in Content Server, the Target Browse window used to select
the destination will, by default, browse the same location as the objects, instead of the last
location selected by Target Browse.
125
16. The English Language Pack and Language Pack Toolkit are included in the SDK 10.0.0
Release 6, and higher versions (for use with Content Server 10.0.0 Service Pack 2). These
tools can be used to help ease the creation of new language packs.
17. The DataID column was added as a fixed system column in Content Server. The DataID is
the unique numeric value that Content Server uses to identify each object. It will not be
displayed by default and you can select it by configuring Global Columns in the Facets
Volume's Control Panel.
The new column is available in the Browse View and all others features that extends this
functionality (for example, Dynamic View and Virtual Folders).
17.13 New Features Service Pack 2

1. Search Filters. Search Filters allow users to refine search results based on indexed
metadata fields defined by the administrator. Search Filters are similar in appearance to
Content Filters, and have many of the same capabilities, but only display on search result
pages. Search Filters replace Search Themes.
2. Index a Collection. This feature is intended to help administrators in diagnosis and repair of
the search index. It allows specific items in a Collection to be queued for indexing.
Historically, requesting indexing of objects could only be done with direct database
commands. This feature requires rights, and by default is limited to admins. Collection
indexing is audited.
3. Paging has been implemented for editing a group to deal with performance problems related
to large groups.
4. In order to prevent errors from occurring when content is required from a storage provider
during a database upgrade (for example, Category definitions), Content Server now verifies
that External Storage Providers can be accessed before allowing a database upgrade to
proceed. The administrator will be made aware if an error is detected and given the
opportunity to correct the error.
5. For Content Server to use JavaObjects, a Java Virtual Machine (JVM) is loaded in each
Content Server thread. The default maximum amount of memory that each JVM can
consume is 1 GB. A new configuration setting was added to Java Module Administration that
allows administrators to set the limit to a different value to improve system performance.
6. Virtual Folders created in Content Server 10.0.0, as part of the migration from Content Server
9.7.1 may exist with no selected Facets defined. Support for these types of Virtual Folders
has now been enabled. The only way Virtual Folders of this type can be created is by using
the OpenText Virtual Folder Migration Tool.
7. Prior to Service Pack 2, a language pack could not be installed over top of an existing
language pack of the same version. It is now possible to re-install the full language pack for
126
each language with each Update. OpenText will no longer distribute the language pack
patches, which simplifies the installation process for administrators.
8. The ability to exclude given node IDs and their children from Notifications has been added.
This is useful when performing bulk imports to avoid a large number of Notifications. This
assumes that Notifications is enabled and properly configured. To add node IDs for exclusion:
A. On the Content Server Administration page, click the Configure Notification link in the
Notification Administration section.
B. Select the Enable Node Exclusion check box in the Excluded Nodes section.
C. Type the node IDs that you want to exclude from Notification Events in the Excluded Nodes
field. Separate multiple node IDs with commas. You can use the node IDs of Folders and the
items inside of the folder will also be excluded from Notification Events.

1. Search Location Modifiers. For developers, a new framework is available that allows
location elements of search queries to be modified. The Search API has also been
enhanced to support this capability.
2. Search Folder Shortcuts. Using the location modifier framework, a new search feature is
available that can search for objects within folders that are reference by a shortcut from the
current folder.
3. Audit Saved Queries. Supporting Records Management applications, Content Server can
now audit the creation, modification and execution of Saved Search Queries.
4. DCS Configuration Files. There is now a hierarchy of dcs.ini configuration files that is
expected to reduce collision between uses of the file. Refer to the Configuration File
appendix for more information.
5. DCS Configuration Logging. When DCS starts, it will now include dcs.ini settings in the log
file if this is the first log file or the dcs.ini file(s) have changed. This configuration information
will be of assistance when resolving support tickets.
6. Multi-Volume Provider Storage. The Multi-Volume Provider Storage rule functionality was
previously distributed as a separate module for Content Server 9.7.1. As of Update 7, it is
included in core Content Server 10.0.0.

1. Nickname Column. Knowledge Managers can now create a Column to display the
Nicknames of items in Content Server.
127
2. DB Verification. An additional check has been added to the database verification system that
will look for cyclical references in the DTree database table. This check is part of the Level 2
verification.
3. Project Wizard. The Project Wizard was updated to allow other modules to request
additional information at the time a Project is created. This feature was specifically added to
allow users to select Classifications to apply to Projects when they are created.
4. DB Verification. There are changes to the database verification for SQL storage. If SQL
storage is used, Level 5 and Level 6 database verification now verifies the existence and size
of the stored objects.
5. DB Verification. A new database verification level has been added. Level 6 verification will
verify the existence and size of document and email objects, and compare data from the
storage provider against the system database. Level 5 database verification has been
modified to exclude these object types, leaving only system configuration objects, which will
improve the performance of Level 5 database verification.
6. Add to Favorites. In Standard search results layout, the Add to Favorites link now displays
Adding when selected, then disappears when complete.
7. Search Bar. Now wider to display more keywords. Width is configurable in Search Bar Edit
administration page.
8. Save Search Result Templates. New dialog clarifies behavior, allows updating of an
existing template.
9. Admin Menu Rights. The Admin Menu added in Update 5 now requires a user privilege in
addition to Bypass permissions. Default is enabled for all users with Bypass permissions.
10. OTContentStatus. DCS now populates the OTContentStatus metadata region with worst
content quality code. This feature works in conjunction with a similar capability within the
index engines to characterize the quality of indexed data.
11. CSV Files. A new format filter has been added for indexing Comma Separated Value files.
Files must have the extension CSV for this feature to function. Feature can be disabled in the
dcsrules.txt file:
[CharEncoding]
module QDF
param Operation "ConvertToUTF8"
param ConvertCSV "True"

1. Virtual Folders. Virtual Folder functionality is available in Update 5 and extends the existing
facet framework to provide the capability to create and manage folders that contain dynamic
128
content in Content Server 10.0.0. A Virtual Folder is an object in Content Server which
defines both a selection of facets and a location within Content Server to which that selection
will be applied.
The creation of Virtual Folders is restricted by default. Users must be granted the privilege to
create Virtual Folder objects through the Administer Object and Usage Privileges in the System
Administration section of the Content Server Administration page.
2. Download Collection as Spreadsheet. A new tool within Collections supports the download
of metadata about an entire Collection or a filtered or selected subset of a Collection as a
spreadsheet, in CSV (Comma Separated Value) format. Large Collections are broken into
multiple CSV files. Multiple CSV files or large CSV files are compressed into a ZIP file before
downloading. A progress bar provides feedback on preparation of the download file. This is
a lightweight implementation the objects are not downloaded, and the spreadsheet is not
retained within Content Server. There are User Rights for accessing this feature, and the
feature is audited. There are configuration limits within the opentext.ini file:
[CollectionsDownloadAsSpreadsheet]
maxOperationSize=250000
Upper limit on number of items that can be downloaded. Use -1 for unlimited.
largestUncompressedSpreadsheetInKB=5120
If spreadsheet larger than this, then it is converted to a ZIP file. Default 5
Mbytes. -1 for no limit.
maxItemsPerSpreadsheet=30000
If more rows than this, the output is broken into multiple spreadsheets and
zipped into a single file.
3. Admin Menu. A new main menu (Admin) is now displayed for administrators. The menu has
links to the main Administration page and the new Search Administration browser.
4. Search Administration Browser. A new tool is available that helps administrators locate and
understand Search Administration features. This is accessible through the Admin menu.
5. Advanced Search. The Advanced Search form has been updated with a number of usability
improvements. The templates within Advanced Search are now referred to as Search
Forms. You now select a Search Form on a pull-down list instead of a separate tab sheet.
The Revert to Default button is now an item in the Form Selection list. The extended Save
features are moved from the bottom to a panel on the left to reduce confusion for the common
search case. The behavior of the Query Components panel on the left is modified to clarify
that selecting these objects moves them into the Search Form as components. The Scope
component is now labeled Slices for consistency with other uses within the product. Other
locations that display this form are updated to remain consistent, such as properties for
Saved Queries. On search Forms, the term Template is replaced with Search Form in
select areas.
129
6. Save as Search Form this feature of Advanced Search was previously labeled Save as
Template. The pop-up save dialog is updated to clarify the options of creating a new form
versus overwriting an existing form, and is now presented as a dialog instead of a new
browser window.
7. Search Activity Indicator. When a search query is issued, a small JavaScript inset is now
presented to the user indicating that the query was accepted and is being processed. This
applies to the search bar, advanced search page and custom view search.
8. Search from Query Properties. A Search button is added to the Properties page for a
Saved Query, allowing a search to be initiated directly from this page.
9. Multilingual Names for Search Forms. You can now edit the properties for a Search Form
(a.k.a. Template) to create multilingual names and descriptions.
10. Rename Search Templates. You can now rename Search Templates. This feature is
accessible through the Function menu on Search Template objects. Internally, Search
Templates are now referenced by ID instead of name.
11. Save as Slice. This feature is now explicitly available as a Save option on the Advanced
Search page and is available only to administrators. In previous releases, you had to save as
template and navigate to the slice folder.
12. Process Scheduling. A minor enhancement was made to the interface for scheduling
processes which now uses radio buttons to clarify the available modes. For processes that
have the ability to manage their own scheduling, such as the Document Conversion and Two
Way Tee processes, a new Persistent Scheduling option is now available.
13. Extractor Optimization. Content Server will now inject specific delete operations into the
DTreeNotify database table instead of generic update operations when objects are deleted.
This allows the Extractor to make smarter decisions and reduce the load on the Search
indexing system.
14. DCS Character Encoding. DCS can now convert text or HTML encoded as BIG5 or
ISO-8859-8 (Hebrew) to UTF-8 for indexing.
15. Document Conversion IPool Error Handling. If the Document Conversion Process (DCP)
cannot process an Interchange Pool (IPool) message and terminates with an exception, the
IPool message will be moved to a quarantine folder after two attempts and DCP will continue
processing the next IPool message. This is intended to prevent ingestion from stopping
completely when errors occur. Problematic IPool messages will be moved to the _failures
folder within the IPool folders. DCP must be restarted (manually or automatically) for this
feature to work, and you may want to set the Maximum Bad Error Code value higher to best
use this feature. In the opentext.ini file in the [ipools] section, the setting:
MaxIPoolQuarantine=10 controls how many bad IPools are retained. Set to 0 to disable this
feature.
130
16. DCS Socket Connections. DCS will now perform up to 3 retries with 1 second intervals
when attempting to open socket connections to the admin server. This change is to
accommodate customers who are unable to resolve intermittent third-party socket conflicts.
17. File Type. The new File Type identification system introduced in earlier updates is enhanced
for coverage of more cases. Note that the system does not correctly identify all data types for
objects that have been stored in Enterprise Library, since Enterprise Library introduces
different mechanisms for reporting object types.
18. Default Regions. The behavior of the &dspregionN= parameter in the XML Search API is
changed. In the past, if this parameter was present, it replaced the default list of regions
returned in the query. This parameter is now used to supplement the default list, adding the
specified region to the results.
19. Level 5 database verification storage providers. The Level 5 database verification now
supports additional storage providers other than External File Storage. The Database
Verification Settings page lists all of the storage providers that will be verified.
20. Storage provider verification framework. A new storage provider verification framework
has been created; this framework will allow additional storage providers beyond External
Document Storage to be verified.
21. Updated errors returned from EFS. The set of errors that can be returned from External File
Storage verification has been altered. The following verification errors can now appear: "The
file size in DVersData table does not correspond to the file size in the storage provider.",
"Document could not be located in the storage provider.", "Errors occurred accessing storage
providers", and "Errors occurred while verifying storage provider data".
22. Web Services: Returned node limit. The following configuration parameter is available in
the opentext.ini file that limits the number of nodes that are returned by a Web Service call
(LESAPI-425):
[WebServices]
MaxNodes=1000
This limit reduces memory use for Web Service calls that can potentially return thousands of
nodes at once. Setting this limit will impact the following Web Service methods:
DocumentManagement.ListNodes() - The maximum number of nodes that will be
returned will be equal to the MaxNodes limit,
DocumentManagement.ListNodesByPage() - The maximum page size that can be
used will be equal to the MaxNodes limit
DocumentManagement.GetNodesInContainer() - The maximum MaxResults option
that can be used will be equal to the MaxNodes limit.
131
Note: This is an optional configuration item and will not appear in the opentext.ini file unless
added explicitly.
23. Web Services: Workflow Service accepts process instance ID. The Workflow Service
GetProcessDefinition method was extended to allow you to pass in a process instance ID to
return the process definition of a running process instance. (LESAPI-173)
24. Web Services: New GetMetadataLanguages method. The GetMetadataLanguages()
method was added to the Document Management service, which returns a list of the enabled
metadata languages on the system. (LESAPI-1098)
25. OTDS Authentication. The Content Server OTDS Integration now supports Web server
authentication (for example, Integrated Windows Authentication (IWA)), in addition to
standard Content Server and OTDS authentication methods.

1. Support for Red Hat Enterprise Linux 5.05.7
Support has been added for Red Hat Enterprise Linux 5.05.7 as a server operating system
for Content Server 10.0.0 + Update 4 and subsequent versions.
The following are known issues that presently exist with Content Server 10 plus Update 4:
The Document Conversion Service (DCS) File Format identification feature

OTFileTypedoes not function.
Content Server will only index certain document file formats. This includes, but may not
be limited to, text, HTML, XML, Microsoft Office, OpenOffice, and PDF.
During the indexing process, if the file format for a document is not recognized, the
document will not be indexed. If the same scenario occurs on a Windows or Solaris
platform, the document metadata is indexed while the actual content of the document is
not.
Not all variations of Microsoft Office will be supported. The text extracted from Microsoft
Office documents will be different than the text extracted from the same documents on a
Windows or Solaris platform. Documents created in Microsoft Office 20032010 will have
their data indexed as XML. The additional XML information will have subtle impacts on
search relevance (for example, proximity may not function as expected).
Note: With the release of Update 4, tools to create and configure an OpenText Spider
data source are now included in the Search administration pages. Installation of
OpenText Spider is required to use these features. However, Spider 10.0.0 is not
available for Linux. In addition, the OpenText Filter Pack and Federated Query Server
10.0.0 will not be available for the Red Hat Linux Enterprise operating systems supported
by OpenText Content Server 10.0.0.
132
2. Support for Internet Explorer 9. Support has been added for Internet Explorer 9 as a web
browser for Content Server 10.0.0 + Update 4 and subsequent versions. Support is limited to
the 32-bit version of Internet Explorer 9 on Windows 7.
3. Object Move Throttle (Limit). The new move throttle allows a system administrator to
configure the maximum number of items that can be moved in one operation. An additional
configuration page allows you to enable this setting and set the limit. (WRD-191)
4. Prospector Limiting. A new feature is available that allows an administrator to limit the
complexity of Prospectors that may be created. This feature can help ensure that
Prospectors have limited impact where high volume search indexing requirements exist.
5. RMI Deprecated. Within Search Engine 10, the ability exists to use either RMI
communication or direct socket communication between components. Starting with Update
4, Content Server will use direct socket connections instead of RMI. The search process
otrmiregistry is no longer used. This change will reduce thread use on large search indexes.
Although specific search transactions may be slightly faster or slower, in general there is no
discernible performance difference. If upgrading from a previous version, the database
upgrade process will make any necessary configuration changes automatically.
6. Collections. There are new features for Collections. The name and object type filters
available in the browse user interface are now also available for use when browsing a
collection. The check box for Entire Collection will now also honor these filter settings.
7. Admin Page Refresh. A feature to automatically refresh certain Search Administrator pages
has been added. These pages display the status of search processes. Using the refresh
feature is useful for Admins that are monitoring search processes during startup or
conversion. The refresh feature is available for: Admin Server page, Data Source Folder
browse, Search Manager browse, Update Distributor Index Engines tab, Search Federator
Search Engines tab and Partition Map page.
8. Back Button Compatibility. Pages that display results from search form submissions have
been modified to allow use of the Back button with certain browsers. Browsers such as
Microsoft Internet Explorer challenge the user with a Form Resubmission dialog when using
the Back button. The change is implemented by using a browser redirect from the form
POST to a GET operation.
An optimization for using a GET operation directly from the search bar has also been
implemented, which skips the redirect if the size of the submission string is not long.
In more security-conscious environments, using a form POST instead of GET may be desired.
The behavior can be changed to force the use of form POST for search queries in the opentext.ini
file:
[SearchOptions]
redirectPost=false
133
9. Spider 10.0 Integration. Beginning with Update 4, tools to create and configure an OpenText
Spider data source are now included in the search administration pages. Installation of
OpenText Spider is required to use these features. Spider is a separate product that allows
web sites, ftp sites and other data locations to be crawled and indexed within Content Server
search.
10. Admin Server Resynchronization. The presentation of output results from Admin Server
Resynchronization has had formatting changes to improve readability. In addition, a new
section highlights any orphaned or unknown processes that may require additional
investigation.
11. DCS Character Encoding. Document Conversion can now identify and convert to UTF-8
more character encodings for text files that do not have explicit encoding information (typically
text or HTML). New encodings supported are GB18030, EUC-JP, EUC-KR, ISO-8859-1,
ISO-8859-2, ISO-8859-5, ISO-8859-6, ISO-8859-7, ISO-8859-9, Windows-1251, Windows1256, and KOI8-R.
12. DCS Format Identification. Document Conversion now has a new file format identification
system, which generates a file type in the search index in metadata region OTFileType. This
new system uses a blend of data that includes the Content Server OTSubType, the output
from a format analysis tool, file format extensions and MIME types. The configuration is
controlled using a new configuration file: dcs.ini.
13. Workflow Error Recipients. There is a new option called "Set Recipient for Workflow Error
E-mails" on the Workflow administration page that allows an admin user to decide who
receives an email when a Workflow error occurs. The previous behavior was to send an email
to all managers of a Workflow. ( LPAD-14276)
14. File Identification on Upload 1. The opentext.ini file contains the following new optional
entry in the [Client] section: UseDCS, which indicates whether DCS should be used. The
default is False. A value of false uses the browser settings to determine the file MIME type, a
value of true will sent the document to DCS for analysis, which is more accurate but slower.
(LPAD-15200)
15. File Identification on Upload 2. A new feature is added that gives administrators the ability
to explicitly define what methods are used, and in what order, to determine the MIME type of
a document when it is uploaded to the system. (LPAD-8564)
16. Object Move Throttle (Limit). The new move throttle allows a system administrator to
configure the maximum number of items that can be moved in one operation. An additional
configuration page allows you to enable this setting and set the limit. This new feature
requires a change to the database schema. See the Installation Notes for the database
upgrade steps. (WRD-191)
17. Permissions for Content Web Services. Added permissions support for Owner, Owner
Group, and Public Access rights. This affects the following API methods:
DocumentManagement.AddNodeRight: Owner, Owner Group, and Public Access rights

for a node can be restored if they were removed.
134
DocumentManagement.GetNodeRight: if a node's Owner, Owner Group, or Public

Access right was removed, the corresponding NodeRight object in the returned NodeRights
object is null.
DocumentManagement.RemoveNodeRight: Owner, Owner Group, and Public Access
rights for a node can be removed.
DocumentManagement.SetNodeRights: Owner, Owner Group, and Public Access rights
for a node can be added, removed, or updated.
DocumentManagement.UpdateNodeRight: Owner, Owner Group, and Public Access
rights for a node can be added or updated.

1. DCS File Type Identification. The Document Conversion Server now has a new mechanism
for establishing object types. This implementation examines the OTSubType, the results from
the Document Filter format detection, the file name extension within OTFileName, and the
Content Server MIME Type. This new type system is more user-friendly than MIME types for
searching. This applies only to new objects added to the search index. The type is stored in
the search region OTFileType. The format detection system can be customized, and the
configuration settings are contained in a new configuration file called DCS.INI.
2. Search Results GUI Update. A number of changes have been made to the presentation of
Search results. These include:
The title of the Search results page will change to identify Custom View Search results and
Advanced Search results.
When using the Search Bar, the title of the Search Results page will now include the source
folder name and the search query to clarify the result for users. The title will be along the
lines of:
Search Results in My Folder Name for: keyword1 keyword2
When using the Search Bar, if searching within a folder, a link will be displayed as a
convenience that will perform the same search on the Enterprise slice, along these lines:
Results 1 to 10 of about 100 sorted by Relevance, did you mean to search Enterprise?
The grey buttons for search tools along the top of the results page have been replaced. The
Refine Your Search button is now a link to Advanced Search. The More Results button is
deprecated in favor of the navigation links at the bottom of the page. Any remaining buttons
are now moved into a pull-down action menu labeled Search Tools.
The link to Edit the Display Options has been replaced with a pull-down menu labeled
Select Display Style. This menu now contains the Edit the Display Options function, the
save search template function, and a quick picker to change the current search layout.
135
The controls at the bottom of the search results have been updated to use the standard
Content Server controls for page navigation and the number of results to display to improve
overall product consistency.
3. Standard Search Result Layout. A new search layout has been added to the list of
available search presentation styles, labeled Standard. This layout differs significantly from
the other search layouts in a number of ways.
The Standard presentation is specifically targeted at casual search users who are looking for
objects to open and share. The layout is simplified, removing much of the complexity in the
interest of meeting this particular need. This layout deliberately provides different information
and features.
The presentation is visually very different, modeled on common public web search engines in
order to provide a familiar interface to search users.
The interface provides quick links to the most common activities that a search user performs:
open a document, share it, add to favorites, add to a collection, or view the properties page.
If you have requirements in which certain fields or search presentation features MUST be
presented, you may want to prevent users from accessing this interface. To do this, BEFORE
allowing users to access the feature, you can delete the new layout from the KIni table with SQL
like this:
delete from KIni where IniSection = 'ResultLayouts' and IniValue like '%.Standard>%'
4. Unpermissioned Search Result Privileges. A new user privilege is available that allows a
user to see the total number of raw search hit counts in a Search Query. Note that this does
not allow them to access the results (which are still trimmed), just the total number of Search
results.
This feature is managed in the Content Server Object Usage and Privileges administration
page, with a Usage Type of Search, and the Usage Name See Unpermissioned Result Counts.
The default is off meaning that users will by default have their result counts permission-trimmed
(estimated), which is the existing Content Server behavior.
5. Audit Hit Highlighting. Auditing of Hit Highlighting is now available but is disabled by
default. To enable this, check the Hit Highlight event on the Set Auditing Interests
administration page within Content Server (SFWK-1662)
6. Search Performance Logging. There is now logging available that can capture timing at
specific points in the Search process within the thread logs. This data is for detailed
investigation when Search performance analysis is required. The data created is intended for
use by OpenText support and development staff, and is not structured for customer use, and
may be changed in the future. This feature is enabled in the [SearchOptions] section of the
opentext.ini file by adding the value WantCheckpointLogs=TRUE.
136
7. Extended Node Rights API. Content Web Services: The AddReplace value was added to
the RightOperation enum. Using this with the UpdateNodeRightsContext method will add the
ACL entry for the user if one does not already exist; or if one does exist, it will replace or
update it.(LESAPI-873)
8. Improved Error Logging. Content Web Services: In Livelink 9.7.1, (in Oscript) if an error
code is passed into the SetError script without a prefix, the script automatically prefixes the
error code with the service's namespace. This functionality exists in Content Server 10.0.0.
(LESAPI-877.
9. Add Partition Wizard. The Add Partition wizard has been upgraded to perform more error
checking at each step of the wizard, improve the default settings, check port availability, add
comments for clarification, and clean up (back out changes) if the wizard is cancelled or
cannot complete.
10. Add Federator Wizard. The Add Search Federator wizard has been upgraded to perform
more error checking at each step of the wizard, improve the default settings, check port
availability, add comments for clarification, and clean up (back out changes) if the wizard is
cancelled or cannot complete.
11. Search Storage Only Mode. The Search engine supports a text metadata storage mode
known as Disk Retrieval. This storage mode keeps the metadata values on disk, and does
not build an index for the values. Hence, these values may be retrieved from the index, but
not searched. The Content Server administration pages now expose this feature in the
Enterprise Partition Map pages. Disk Retrieval should be considered for OTSummary and
OTHP regions, which can consume up to 25% of the metadata RAM in the search engine. If
making this change, ensure that OTSummary and OTHP are removed from your default
search regions list and are not used in the Search Rankings.
12. Fetch Request Handler. In the fetch request handler, a new subsystem and registration
object were created with to allow external editors to register, and open and manipulate
content from Content Server instead of the traditional Content Server document streaming.
By default, the standard 'Open' functionality is used. There are no user interface changes for
this update. (SAPRM-1887)

1. SLD Registration. Content Server 10.0.0 has automated the SLD registration at the SAP
Solution Manager. The Administrator can now create the SLD file for Content Server 10.0.0
as well as uninstall the file from the Administrative area.
2. View as Web Page. Users can now view a document version as a web page and have
access to the page footer. Previous to this fix, the user could not access the footer when
viewing a document version as a web page.
3. Secure Attribute for Cookies. Added an Enable Secure Attribute for Cookies option in Java
Modules Admin Page. Setting the secure attribute on an HTTP cookie instructs the web
browser to send it only over a secure channel, such as an SSL connection.
137
4. Advanced Search Blanks. Date fields in advanced search have a new value in the pull down
list, blank, which is the default. If blank is selected, the term is omitted from the query
entirely. This is analogous to the CS 9.7.1 default of Any. In CS10, the Any setting is
interpreted as including the term in the query and searching for * in the field, which requires
that a value is present. (SFWK-1540)
5. Best Bets Tuning. The test for Nicknames and Best Bets in CS10 is now tunable to reduce
the number of matches. (SFWK-1382)
Support has been added for four new opentext.ini settings in the [SearchOptions] section to allow
for tuning:
BestBetsMinStemLength: Minimum number of characters a search term using stemming,
left/right truncation, * wildcards, or regex must be to in order to be translated into a like SQL
clause for Best Bets lookup. Defaults to 4 if not present.
NicknameMinStemLength: Number of terms to be used in Best Bets generation (the first N
terms of the query are used). Defaults to 4 if not present.
BestBetsMaxTerms: Minimum number of characters a search term using stemming, left/right
truncation, * wildcards, or regex must be to in order to be translated into a like SQL clause for
Nickname lookup. Defaults to 3 if not present, use -1 for unlimited.
NicknameMaxTerms: Number of terms to be used in nickname generation (the first N terms of
the query are used). Defaults to 3 if not present, use -1 for unlimited.
6. Search API. The XML Search API has been extended to allow regions to be retrieved that are
not marked as Displayable. (SFWK-440)
7. Search API. The XML Search API has been extended to allow specification of language rules
that apply to Thesaurus and Stemming. (SFWK-45)
17.20 New Features Initial Release (Update 0)

Faceted Browsing Content Filtering. The Faceted Browsing functionality provides metadatadriven content filtering across the Enterprise. The filter panels appear in the new sidebar user
interface component and show applicable values within the folder and containers. After selecting a
value in a filter panel, the user sees the new "Dynamic View" mode, which filters the content based on
the selection. The Dynamic View shows all content available to the user at the current location and
within containers. Multiple filter panels can be applied at one time to enable flexible filter
combinations. This makes browsing for content significantly faster and more intuitive.
Content Server 10.0.0 comes preconfigured with four system-data based filters:
Modification Date
Owner
138
Item Type (for example, Folder)

Document Type (for example, MS Word)
The new Knowledge Manager role can configure Categories and Attributes to be used as Facets,
which can then be deployed as part of the content filter functionality. Content Filter panels can be
configured for global, role-based, or location-based use.
URL support means users can share configured views.
Faceted Browsing Custom Columns. The Custom Columns functionality allows the display of
additional columns of metadata in the main browse view of Content Server. Users can see the
metadata values in the columns as part of the browse view. Content Server provides sample columns,
such as version number and date. This capability reduces the need to manually look up attribute
values for items in the system.
The new Knowledge Manager role can configure Categories and Attributes to be used as columns,
which can then be deployed as part of the Content Filter functionality. Columns can be configured for
global, role-based, or location-based use. Users can specify columns they want to see for any
location.
Internationalization User Interface. OpenText Content Server 10.0.0 introduces Language Pack
functionality.
A single instance of OpenText Content Server 10.0.0 can have language packs installed that
enable multiple localized user interfaces.
All instances begin as English-only and then become localized as language packs are installed.
This allows all users of a multilingual system to use the same URL to access Content Server.
Language packs can be installed for Content Server 10.0.0 and optional modules.
In an instance with multiple language packs installed, users can now specify and save their
preferred UI language.
Multilingual Metadata. The Multilingual Metadata functionality in Content Server provides the ability
to assign multiple language values to items Name and Description fields. When Content Server is
configured to use two or more languages, users can specify the language of choice and see the
appropriate values in the main browse view. This makes finding content easier for users who work in
an environment where more than one language is spoken.
139
Users can edit or view additional language values for name and description fields. Users can specify
a language of choice, and when that language is available, they will see the relevant value, otherwise
the initial value is used. Multilingual metadata is supported for all object types that ship as part of the
base Content Server configuration, including Documents, Folders, Projects, and others. Multilingual
metadata is also supported in Search.
Workflow Single Page View. The Workflow Single Page View is a UI Option that allows the
Workflow Designer to control the Workflow packages displayed to the Task Assignee. The Single
Page View condenses the UI into a single page and minimizes user navigation and the number of
mouse clicks.
The Single Page View UI is not a replacement of the current double frame UI, but an optional UI view
that can be applied to default 'User' Task types. This means that Workflow Designer can use either
the default double frame UI or the single frame UI in a Workflow.
Workflow Designers have the option to pick active packages that they want the Task Assignee to
have access to for a specific Task. Package display order is determined by the Workflow Designed at
design time. Packages that can be used in the Single Page view are:
Comments
Attachments
General Information
Forms (link to Form only; Form itself will open in a new window)
Attributes
Improved Performance. The broad goals to improve server performance and functionality are
represented by:
Modification of the server to take advantage of multi-processor and multi-core servers

Elimination of software bottlenecks caused by the use of outdated techniques
Porting of the server to a native 64-bit application
Integration the Hoard memory manager
Increasing of the real and perceived download speed
Search Engine 10.0. The existing OT7 search engine has been improved and rebranded as Search
Engine 10. Key enhancements include:
Extractor - improved performance, especially for deletes or operations on versioned objects
Index Verifier - new features, better error coverage and correction
Support for text metadata with multiple attributes - support for multilingual metadata
64-bit deployment that allows for fewer, larger partitions (simpler management and higher
search performance)
New memory-efficient disk-storage mode for metadata that is retrievable but not searchable
New standard and synthetic metadata that supports analysis of index quality
Document Conversion Service (DCS)
New / improved HTML filter
140
New standard document filters based on technology from Spicer acquisition

Automatic identification of content of language. This is disabled by default.
EPS Integration. Enterprise Process Services work items can be displayed in the My Assignments
page in Content Server
The Enterprise Process Services inbox appears in the My Assignments page of Content
Server. This allows users to find and track assignments from both EPS and Content Server
Workflows in a single location. The selection of an EPS task from the My Assignment page
leads directly to the Forms views of the selected task embedded in the Content Server UI.
Alternatively, the end user can open the EPS Inbox in Process Workplace and process work
items from here. In this inbox, only the BPM assignments are listed.
Users can add an EPS Process Shortcut to a folder in Content Server. From there, users who
have access can initiate the EPS process from within the folder by clicking on the EPS
Process shortcut.
Users that have permission to view or edit an active EPS Process can simply go to the
Workflow Status area. Active instances of EPS Processes that are associated with Content
Server are available on the Workflow Status page.
Search and add and view Content Server objects in EPS work items. Document, Folder, and
Project objects are supported as attachments. The attachments can be loaded into Content
Server from the EPS Process, or added to the Process from Content Server. The attachments
are handled as links, which means the metadata from the underlying object is shared, and
Process flow can be dependent on it. Also, any changes in the underlying object are
automatically reflected in the Process attachment. Standard document management features
such as Reserve, Versioning, and adding Categories and Attributes is fully supported.
EPS supports Single Sign On. The Single Sign On feature between Content Server and EPS
provides transparent access for the end user between the two systems. For example, a user
can access the Inbox section or the Work Items view of Enterprise Process Services from
Content Server without authenticating again.
Refreshed Interface. The updated user interface in Content Server has a modern look and feel with
less visual distractions. The UI makes use of commonly used widescreen monitors. Content Server
now includes a new Sidebar component that provides the ability to filter content in the browse view
based on metadata. The header and Enterprise menu are streamlined and the interface now
incorporates visual feedback when the mouse is placed over clickable items such as menus and
function icons. The breadcrumb trail is simplified and the toolbar items now collapse into a menu if
the screen is resized. The Add Item functionality is moved closer to the main browse area. The
header is simplified to facilitate rebranding and moving the date and user name to the simplified footer
area.
All of these changes contribute to an overall clean look which in turn addresses user adoption and
training issues.
141
18 Appendix I Known Issues

This section should be reviewed to determine if workarounds or limitations exist for configurations or
features that may of particular interest in your application.
18.1 Known Issues: General

1. A 32-bit Java Runtime Environment is required for eLink Server to be installed. Once
installed, either a 32-bit or 64-bit version of the Java Runtime Environment can be used to run
eLink Server. (LPH-700)
2. When the Report Fields parameter is used in a LiveReport, the SQL statement cannot make
use of an alias for the DTree view, otherwise the report will result in an ODBC or ORA error
similar to "The multi-part identifier 'DTree.DataID' could not be bound" (LPAD-23765).
3. On Windows, if you are logged in as a "named" user (not the Administrator user) with
administrative privileges and you have Windows UAC (User Account Control) enabled then
you will receive the error "There is a problem with this Windows Installer package. A script
required for this install to complete could not be run. Contact your support personnel or
package vendor." during the installation. To work around this issue, you must select the
executable, bring up the context menu, and then select 'Run as Administrator' which will run
the install with elevated privileges.(LPAD-40377) [Fixed in Update 2014-12]
4. An error will occur when the resulting zip file created by the Zip and Download function is
greater than 2 GB. (LPAD-36198)
5. After configuring a new Storage Provider and Storage Rules for that provider, it was possible
to lose subsequent additions of version data to Content Server objects. In order to prevent the
loss data, the Content Server services should be restarted after changes are made to the
Storage Provider configuration. (LPAD-37436) [Fixed in Update 2014-06]
6. It was possible to create dependency cycles in the Document Class definitions that are used
to build Facets. This caused an error indicating that the maximum recursion limit was
exceeded. To fix this issue, the following changes were made:
The recursion through these Document Class definitions has now been changed to be
mindful of such cycles and avoid getting stuck in the loop.
The UI will check for such cycles when the Document Class definitions are edited and roll
back all changes if it detects one, providing an error message to user.
A new Admin function called Identify Document Class Cycles is now available in the Test or
Repair Known Database Issues section of the Maintain Current Database page.
(LPAD-34407) [Fixed in Update 2014-06]

7. Printing using Multi-File Output does not always print when selecting a new Print (with the
Printer Selection dialog). The "Print" and "PrintTo" Shell commands use the Windows
142
Registry on the client machine to determine the proper command. In the registry, each file
type has a Shell section where the supported commands are registered. When documents do
not print, it is because the appropriate Shell command has not been registered for that file
type on that client machine.
Workaround:
Below is the general procedure for determining the configuration of the printto verb for a given
type of file. This procedure describes the process for TIF files, but it applies for any extension.
Open Regedit
Navigate to HKEY_CLASSES_ROOT
Locate the ".tif" entry beneath HKEY_CLASSES_ROOT and determine its (default) value this provides the underlying document type name. For TIF, this is normally
TIFImage.Document
Locate the document type name beneath HKEY_CLASSES_ROOT - e.g.

HKEY_CLASSES_ROOT\TIFImage.Document
Beneath that key, is a sub-key for shell
Beneath the shell sub-key is a key for each registered verb for that type of file
Confirm that there is a printto verb registered. For example:

HKEY_CLASSES_ROOT\TIFImage.Document\shell\printto
NOTE: The workaround for this issue involves advanced administrative tasks, such as editing the
registry. You should contact your IT support personnel before editing the registry.
If there is no printto verb present, you must create it to solve the non-print issue. Sometimes you
can view another computer's registry and copy the value from there. Other times, you are
required to install software that supports the printto verb. Occasionally, other applications have
changed the document type for the file extension (for example, .tif file extensions might be set to
something besides "TIFImage.Document").
Example:
The default value of the HKEY_CLASSES_ROOT\TIFImage.Document\shell\printto\command
key on a Windows 7 workstation is:
"%SystemRoot%\System32\rundll32.exe"
"%SystemRoot%\System32\shimgvw.dll",ImageView_PrintTo /pt "%1" "%2" "%3" "%4"
8. The eLink module uses an artificial email address called "devnull" when processing emails.
This address serves as a "no reply" address. (LPH-909)
9. In order for the Content Server REST API to correctly handle PUT and DELETE requests via
IIS, the Application for Content Server needs to be configured to disable WebDAV. The
WebDAV Module should be removed as well as the handler mapping for WebDAV. Since the
Content Server WebDAV module uses a different IIS Application than that for Content Server
itself, this will not cause a problem for that functionality. (SIESTA-505)
143
10. In Content Server 10.0 Update 11, if you delete a row from the DVersData table, a row is not
added in the NotifyEvents table even if Notifications are enabled. When this happens,
"Delete" notifications are not created. This issue only applies when an Oracle Database is
used. (LPAD-35644) [Fixed in Update 2014-03]
11. The Content Server text document Java applet is not currently signed by an OpenText
security certificate. If a web browser prompts with a security message, the Java applet should
be allowed to run. (LPAD-34559) [Fixed in Update 12]
12. The Database Upgrade step during an upgrade may report that the Admin server is not ready
or in safe mode. In some cases, this can occur because the upgrade started before the
Admin server has completed its startup process. In this case, waiting a minute and trying the
upgrade step again may resolve the problem. (SFWK-3514) [Fixed in Update 9]
13. Installing E-Mail Services 10.2.1 on Content Server 10 SP2 will generate an error during the
installation process. To resolve this issue, you will need to install patch pat100000526.
(CSEM-187) [Fixed with E-mail Services 10.2.2]
14. When painting a Workflow and trying to use expressions on the Assignee tab of a user step, it
is not possible to add, remove, or edit expressions in some browsers. Firefox and Internet
Explorer work as expected. However, when using Chrome, the radio button moves from
"Expression" to "Assignee from Prior Step" and the following error appears: [You must select
a step to choose assignee from.]
15. WebDAV (WebEdit) and Office Editor are not supported with Chrome. To use these features,
you must use supported Internet Explorer or Firefox web browsers.
16. When adding a Text Document using the Safari browser, the Spell Check Utility does not
appear. (LPAD-30682)
17. A new configuration option has been added to the Java Module administration page for
Update 7. Proper configuration of this setting may be required for any Java RMI clients,
including SEA Servlet.
The "Client IP Addresses" setting needs to include the addresses of the Content Server. Any RMI
requests from clients not in this list and not originating from the same server as Content Server
will result in the Java Server logging a security exception and denying the connection attempt. For
SEA Servlet, the client list should match the CGI Hosts setting for Content Server. (LPAD-30675)
18. WebDAV is not currently supported using the Safari browser. (LPAS-727)
19. When exporting and importing via a Project Template, if you have a Workflow Map with an
Item Handler step that has a mapping of a Category to Workflow attribute, the settings are not
maintained. (1912622)
20. If Content Web Services (CWS) is being deployed in OpenText Runtime and Core Services
(RCS), it should be updated with each Content Server cumulative update or service pack. To
update RCS with the latest CWS package:
Stop Tomcat.
144
Place the latest version of les-services.car and les-services.war from the Content Server
cumulative update (<OTHOME>\webservices\java\core-services) into <RCS
workspace>/modules/install (overwrite if exists).
Restart Tomcat.
21. When the LiveReports module is uninstalled, the database schema is not cleaned up. The
server will not work until the module is reinstalled or the schema is manually adjusted.
(1597425 and LPAD-77)
22. In a LiveReport with a Click-thru SubReport, the "DETAILS" action will not display if the report
format is set to "LiveReport". (1602075 and LPAD-72)
23. Some dynamic links generated by Content Server are "absolute" rather than "relative" and,
therefore, can cause problems with some proxy servers, cluster servers, and authentication
tools. Known areas include highlighting, Workflow painting, Project menu items, News
Channels, and Task Lists. (1806673 and LPAD-823)
24. If a system report is aborted before it is allowed to complete, it can become difficult to run
another system report. Contact OpenText Customer Support to resolve this issue. (LPAD12821)
25. When performing an XML Export, if the transform parameter is used for style sheets that
contain the XSL document() function, an error is returned. (LPAD-16217)
26. User Interface never updated to show that func=admin.xmlimportstatus has completed and
import logs not generated with [general] logpath change. (LPAD-19520)
27. Renditions not copied when minor version is promoted to major and Renditions module is not
installed (LPAD-22634)
28. Expression Builder sometimes cannot display added rows properly (LPAD-22700)
29. When a user is assigned a Task from a Task List, that user cannot change the status of the
Task. (LPAD-23164) [Fixed in Update 7]
30. When Text Documents that contain extended ASCII characters that are created through the
Content Server interface on a UTF-8 installation are opened, the browser encoding is
incorrect. To properly view these Documents, the browser encoding must be manually set to
UTF-8. (LPAD-4525)
31. Memcached Folder (SOV) is not automatically created during upgrade from Livelink 9.7.1
(UTF-8) to Content Server 10.0.0. The Memcached folder and 3 processes should be created
along with the facets and columns upgrade during the upgrade. (LPAD-22657)
32. Content Server Administration. When you install Content Server 10 on Windows Server
2012, the "Content Server Administration" start page shortcut cannot be launched by the
Admin because Microsoft does not permit the Admin user to use the IE10 Metro app.
145
Workaround: Launch an IE10 browser and type in the URL manually. For example:
<http://localhost/OTCS/livelink.exe?func=admin.index>
33. The URL with livelink.exe (or livelink) functions properly; but cs.exe (or cs) does not when
using appropriate Tomcat 6 xml mappings for Content Server 10.0.0. The web.xml file (the
default location is: content_server/application/WEB-INF/) should contain a cs and a cs.exe
filter-mapping and servlet-mapping. (LPAD-25322)
The following filter-mapping sections and servlet-mapping sections need to be added to the
OTHome/application/WEB-INF/web.xml file:
<filter-mapping>
<filter-name>compressionFilter</filter-name>
<url-pattern>/cs/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>compressionFilter</filter-name>
<url-pattern>/cs.exe/*</url-pattern>
</filter-mapping>
<servlet-mapping>
<servlet-name>LLServletClient</servlet-name>
<url-pattern>/cs/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>LLServletClient</servlet-name>
<url-pattern>/cs.exe/*</url-pattern>
</servlet-mapping>
18.2 Known Issues: LiveReports

1. When users click the Report Format drop-down menu and select either bar, pie, or line chart,
the function will tie up a thread in Content Server and use memory for the browser by creating
frames in the pop up window. Each call will create a frame inside the previous frame. (LPAD23320)
18.3 Known Issues: Multi-File Output

1. In certain instances the Help for this page feature may direct the user to the wrong page.
(LPAD-14564)
2. When Multi-File Output is installed and you right-click on a supported container or Document
in Content Server Explorer, the menu items say Zip Download and/or Zip Email instead of
Zip & Download or Zip & Email (the ampersands are missing). (LPAD-17083)
146
18.4 Known Issues: Projects

1. An error occurs when using The Create From command to create a Project from a Project
Template that has been imported. As a workaround, all Project Templates should be exported
using the CONTENT parameter to specify base64 encoding in the export URL. For
example:
func=ll&objID=xxxx&objAction=xmlexport&nodeinfo&permissions&attributeinfo&scope=sub&v
ersioninfo=all&content=base64. (1960191 and LPAD-5359) 2
2. If a Sub-Project within a Project is configured to display within Featured Items, the SubProject will not be displayed. (LPAD-16729) [Fixed in Update 7]
18.5 Known Issues: Search

1. When Java detects Turkish regional settings, the Index Engines are unable to recognize the
Integer data type. SRCH-801. Workaround is to add the following parameters to the Java
command line in the Additional Arguments field of the Search JVM Configuration admin page:
-Duser.language=en -Duser.country=US
18.6 Known Issues: Workflow

1. When modifying the route of an active Workflow, ownership of the attachments within the new
Workflow will change to the user who is enforcing the modifications. (1840172 and LPAD1055)
2. If a user makes another user a Proxy for their Workflow Assignments and that user also has
set a Proxy, the first users assignments show up only in the Assignments page of the direct
Proxy and not in that of the Proxy of the direct Proxy. (1647861 and LPAD-286)
3. HttpOnlyCookies option breaks save of WorkflowMap (with IE). (LPAD-12777)
4. Possible IPv4/IPv6 Issues in Workflow Painter. If a user authenticates through their browser
under an IPv6 connection, under some circumstances the WFP applet will still try to
communicate with the server under IPv4. If Content Server is configured to compare the IP
originating the TCP connection with the IP stored in the user's LLCookie (via the "Client IP
Address" setting under "Cookie Authentication Information" on the Configure Security
Parameters admin page), the IPv4 IP reported by the TCP connection will not match with the
IPv6 IP expected by the cookie. To avoid this issue, adjust setting to Do no use IP address
for authentication. (LPAD-22057)
5. In a multilingual environment, subworkflows will not support document sharing with a user
from a different language the original language. Workaround for this issue is changing the
sub-workflow step attachment setting to All instead of Selected Items. (LPAD-21341)
6. Users editing a form in Workflow can always see the storage mechanism. Users can always
see the currently selected storage mechanism even if they dont have permissions to it
(LPAD-20252)
147
7. Workflow Expression Builder cannot handle special characters such as . (LPAD-22699)
18.7 Known Issues: Internationalization User Interface

1. Changing multilingual default language does not correctly display new default language in
browse.(LPAD-22759)
18.8 Known Issues: EPS Integration

1. With the latest patch for Content Server, the ListObjects method in LAPI is disabled by
default. With one of the latest patch for Livelink 9.7.1 (PAT08100) the ListObjects LAPI
method is disabled by default. This method is necessary for the Livelink SPI for BPM (not the
new Content Server SPI). The Administrator will be able to turn it on by setting a flag
EnableListObjects=TRUE in LAPi section of opentext.ini (BLI-348)
19 Appendix J Applying Updates

The procedures for applying an Update to Content Server are summarized here for convenience.
Summaries are provided for the following 3 scenarios:
Installing a new instance of Content Server and immediately applying Updates.

Applying an Update to an existing instance of Content Server.
Applying an Update to a Content Server cluster.
OpenText may also provide more detailed resources on the Knowledge Center that can assist you
with correctly installing and Updating Content Server. You are strongly encouraged to review the
available documentation and use it to supplement the procedures provided here.
Sample documentation on the Knowledge Center includes:
Best Practices Applying Update 11 to OpenText Content Server 10
Best Practices Applying Update 2014-03 to OpenText Content Server 10
Best Practices - Applying Update 2015-06 to OpenText Content Server 10
148
20 Contact Information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1
Email: [email protected]
Knowledge Center: https://knowledge.opentext.com
For more information, visit www.opentext.com
Copyright 2015 Open Text Corporation. Visit online.opentext.com. OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not exhaustive of other
trademarks, registered trademarks, product names, company names, brands and service names mentioned herein are property of Open Text SA or other respective owners
149

Service Pack 2

Uploaded by

Copyright:

Available Formats

Service Pack 2

Uploaded by

Document Information

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

Service Pack 2

Uploaded by

Copyright:

Available Formats

What are the main components of Content Server 10.0.0?

What are the main components of Content Server 10.0.0?

What are some of the supported environments and platforms for Content Server 10.0.0?

What are some of the supported environments and platforms for Content Server 10.0.0?

OpenText Content Server 10.0.

About OpenText Content Server 10.0.0 ................................................................................. 7

Packaging and Documentation .............................................................................................. 7

Supported Environments and Compatibility ........................................................................ 8

Supported Server Operating Systems ............................ 9

Content Server Client Support ........................................ 9

Content Server Browser Support .................................. 10

Content Server Database Support ................................ 11

Content Server Web Server Support ............................ 13

Application Server Support ........................................... 13

Java Runtime Support .................................................. 14

4.2 General Platform Support Notes ............................................................................................. 14

Installation and Upgrade Notes ........................................................................................... 15

New Installation Notes .......................................................................................................... 16

Upgrade Notes ....................................................................................................................... 19

Installing Content Server 10 Updates and Service Packs ................................................. 21

Notes for Specific Updates ................................................................................................... 22

Content Server 10.0.0 Release Notes

9.4 Service Pack 2 Update 2015-09 Release Notes ..................................................................... 23

Service Pack 2 Update 2014-03 Release Notes .............................................................. 24

Service Pack 2 Update 13 Release Notes ........................................................................ 24

Service Pack 2 Update 12 Release Notes ........................................................................ 24

Service Pack 2 Update 11 Release Notes ........................................................................ 25

Service Pack 2 Update 10 Release Notes ........................................................................ 26

Service Pack 2 Update 9 Release Notes .......................................................................... 26

Service Pack 2 Release Notes ......................................................................................... 27

Update 7 Release Notes ................................................................................................... 27

Update 6 Release Notes ................................................................................................... 27

Update 5 Release Notes ................................................................................................... 27

Update 4 Release Notes ................................................................................................... 28

Update 3 Release Notes ................................................................................................... 28

Update 2 Release Notes ................................................................................................... 28

Appendix A Critical Patches .............................................................................................. 29

Appendix B Deprecated Patches ...................................................................................... 32

Appendix C Dependencies ................................................................................................ 42

Appendix D Changed and Deprecated Features ............................................................. 45

Feature Changes Update 2015-12 ................................................................................ 45

Feature Changes Update 2015-09 ................................................................................ 45

Feature Changes Update 2015-06 ................................................................................ 45

Feature Changes Update 2015-03 ................................................................................ 46

Feature Changes Update 2014-12 ................................................................................ 46

Feature Changes Update 2014-09 ................................................................................ 46

Feature Changes Update 2014-06 ................................................................................ 46

Feature Changes Update 2014-03 ................................................................................ 46

Feature Changes Update 13 .......................................................................................... 47

Feature Changes Update 12

Feature Changes Update 11 .......................................................................................... 48

Feature Changes Update 10

13.13 Feature Changes Update 9

Content Server 10.0.0 Release Notes

Feature Changes Service Pack 2 .................................................................................. 52

Feature Changes Update 7

Feature Changes Update 6

Feature Changes Update 5

Feature Changes Update 4

Feature Changes Update 3