Open Text
Open Text
10.5.0
2016-01-28
Contents
1 Introduction .................................................................................................................................... 4
2 About OpenText Content Server .................................................................................................. 4
2.1 New Features and Changes – SP1 Update 2015-12 ................................................................ 4
2.2 New Features and Changes – SP1 Update 2015-09 ................................................................ 6
2.3 New Features and Changes – SP1 Update 2015-06 ................................................................ 7
2.4 New Features and Changes – SP1 Update 2015-03 .............................................................. 10
2.5 New Features and Changes – SP1 ......................................................................................... 11
2.6 New Features and Changes – Update 2014-09 ...................................................................... 14
2.7 New Features and Changes – Update 2014-06 ...................................................................... 18
2.8 New Features and Changes – Update 2014-03 ...................................................................... 19
2.9 New Features and Changes – 10.5.0 Release ....................................................................... 22
2.10 Discontinued and Deprecated Features ................................................................................ 26
3 Packaging and Documentation .................................................................................................. 27
OpenText Content Server is the core content repository and foundational document management
technology for the OpenText Content Suite (formerly OpenText ECM Suite), as well as a broad range
of OpenText products such as the Content Suite Platform (formerly Content Lifecycle Management |
CLM), Application Governance and Archiving for SharePoint, Extended ECM for SAP Solutions,
Extended ECM for Oracle® E-Business Suite, Email Management, our family of Content Suite
Applications and other OpenText Enterprise Information Management (EIM) offerings.
Content Server provides richly-featured enterprise services based upon a unique combination of
integrated tools which include document management, workflow, and information retrieval services,
all tightly integrated into a solution that is easily customized and extended.
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. Document Conversion Server. Each DCS instance now has its own directory for temporary
files, located within the temp directory and labeled dcs_temp_xxxx (xxxx is the port number
used by that instance of DCS). The associated temporary file cleanup methods have been
improved.
4. Distributed Agents. New configuration settings that allow “fairness” to be adjusted. Fairness
is a measurement of time that should be allocated to older tasks in the queue. The task
5. 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.
6. Search Bar. A new “Location Modifier” is available that allows a “from here” search in the
search bar to be restricted to the current folder only. “Exclude Sub-Folders” is the label in the
Location Modifier field.
7. Arabic Language Support. The user interface (excluding administration pages) has been
enhanced to support “Right to left” language configuration. An Arabic language pack is
available. Note that administrators should not use Arabic language preferences.
8. Multi File Output. The Email Link button in the browse view now generates a /link/ URL. Users
following this new URL will be directed to either the Open or Properties action for the
referenced item, based on personal and system settings. Administrators can choose a default
action for the system on the Multi-File Output General Settings admin page. Users can override
the default action from the Tools -> Settings page.
9. 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.
10. Azure SQL Support. Support has been added Azure SQL for Content Server installations
running in the Azure Virtual Machine. Baseline testing regressions have been successfully
completed on a base Content Server installation in the Azure Virtual Machine (please see
Azure Virtual Machine Support statement for tested configuration information) and Azure SQL
version available as of December 2015. Although no issues are expected, full testing
regressions of all Content Suite Platform and optional modules have not been completed. For
questions about installation, sizing, storage, backup, monitoring, integration into on the premise
network, contact OpenText Professional Services.
Please note, that Microsoft Azure cloud and Microsoft Azure SQL database are updated by
Microsoft on a regular basis for which OpenText will make best efforts to test and ensure
forward compatibility.
2. Java. Java 8 update 51 replaces the prior Java 7 runtime for new installations. Utilities are
provided to upgrade an existing system based on Java 7 to Java 8.
3. Email Services. A change introduced in Content Server 2015-09 causes failure while browsing
Email Folder. Please apply Email Services 10.5.0 pat100002119 for Content Server 10 and
pat105000673 to correct this.
4. Content Web Services. The DocumentManagement service now provides the ability to get/set
Category Inheritance for categories applied to containers. New getCategoryInheritance() and
setCategoryInheritance() methods are provided for this purpose.
5. Cluster Management Tool. Now displays the total number/current progress of patches being
staged. This feature provides a transparent report of what is being executed, especially when
there are a large number of files.
6. eLink. If Email Services is installed, Email-enabled containers now support the creation of an
Email subtype (749) for inbound eLink messages. It is also now possible to enable Email
Folders for inbound eLink messages. Messages are stored in RFC 822 format as .eml files.
NOTE: Email Services patch pat105000515 is required to open ingested emails correctly.
7. Quarantined IPools. The contents of quarantined IPools can now be listed. Information about
quarantined objects can be downloaded as a spreadsheet. Quarantined IPool message
objects can be added to a collection to facilitate re-indexing.
8. Thumbnail Creation. Administrators can now request thumbnail generation for the contents of
a collection. This is a maintenance tool to facilitate repair of thumbnails, or to create
thumbnails for older objects.
9. Rendition Search Results. Renditions in search results are now identified by a simple
vertical bar marker icon to help users differentiate renditions from regular documents.
10. Extractor Configuration. There is a new control in the Extractor Configuration Administration
pages that provides the ability to disable the notification for content recovery errors.
11. Partition Map. The Partition Map Administration page has been updated for easier
understanding and to display quickly with large search grids. Distinct “percent full” values for
12. Search XML API. The search API has been extended to allow authentication using the
standard REST API authentication methods. This simplifies authentication and impersonation.
However, previous authentication methods are still supported.
13. Target Browse. Usability improved by increasing the window size and adding a scroll bar.
14. Admin Server. If the configuration in opentext.ini does not reference the current OTHOME
location, this likely indicates cross-wiring (settings copied from another location on the same
computer). Admin Server will enter safe mode.
15. Search Index TIME fields. Previously, TIME fields were ‘DROPPED”, which froze existing
values and ignored new values. The new default is REMOVE, which will eliminate existing
values and reduce the index size.
2. Queue for Indexing. This search maintenance feature has been extended to support deleting
from the index, or re-indexing metadata only. Control over the collected version versus all
versions is now also available. The underlying technology has been changed in the Extractor
to use a new Collection Iterator which reduces the impact of bulk Collection indexing on regular
indexing operations.
3. Collect Folder. A new administration control on the Collection settings page now limits the
maximum number of objects that can be handled by the Collect Folder feature.
4. Search Process Controls. The controls to stop or restart all Index Engines have been
removed from the Index Engine management pages. Similarly, the controls to stop or restart all
Search Engines have been removed from the Search Engine management pages. This
eliminates inadvertent search grid outages. The controls remain on the Update Distributor and
Search Federator admin pages, where confirmation challenges have been added.
6. Microsoft Azure virtual Machine. Microsoft Azure Virtual Machine Services offer an
Infrastructure as a Service (IaaS) platform. OpenText Content Server 10.5 Service Pack 1,
OpenText Directory Services 10.5 Service Pack 1 and OpenText Archive Server 10.5.0 (with
Azure Blob storage) are certified on Azure Virtual Machines (IaaS). Prerequisites are:
The IaaS platform allows deploying various scenarios, including hybrid deployments with
connections to the on premise customer network. For questions about installation, sizing,
storage, backup, monitoring, integration into on the premise network, contact OpenText
Professional Services.
7. Admin Server Safe Mode. Two new conditions have been added that will place the Admin
Server into “Safe Mode” of operation. Both conditions have been observed during upgrades
which are not correctly managed. The first is if an attempted Admin Server password change
fails (for example, if the disk area is write-protected). The other condition is if the hostname in
the configuration files differs from the system host name, indicating a likely misconfiguration.
8. Indexing Pattern Counting. Document Conversion Server now supports creating searchable
regions that contain counts of strings that match defined patterns. One common use for this is
identifying documents that have personally identifiable information – where content matches
patterns of phone numbers, social security numbers, or credit card numbers.
9. Indexing Pattern Extraction. Document Conversion Server now supports extracting text from
content that matches patterns, creating searchable regions of the extracted text. Common
applications could include extracting #hashtags or @userids from social media, or part
numbers / contract numbers from documents.
10. Document Conversion Process Management. DCS has two new process controls that can
help to pro-actively control unexpected resource management problems. If not busy, DCS can
now recycle processes that it manages (shutdown and restart filters, for example). The second
feature is a self-shutdown on a timed basis (typically once per day) to recover resources. The
Admin Server would then immediately restart DCS.
12. Tokenizers for Search Regions. The search engine now supports the ability to use different
tokenizers per text search region. This would allow different approaches to tokenizing that can
improve search results for regions dedicated to part numbers, phone numbers, etc.
13. Indexing Throughput Data. The Update Distributor now collects detailed information about
indexing throughput performance, and outputs it once per hour to the log file. This data can be
used to tune search indexing, especially in high-volume environments.
14. Thread Logs. Log4J can now be used with rolling log files, when per-thread logging is
configured. In addition, separate log files are retained that capture thread logs during startup,
which are useful for support and might otherwise be lost when rolling logs are configured.
15. OpenSSL Update. Open SSL has been updated to version 0.9.8zf.
16. Shell. The default shell for Solaris and Linux systems was changed to /bin/sh, since this is a
shell available by default on Linux and Solaris systems. This ensures that users do not have to
install a shell in order to run Content Server.
18. Multilingual metadata. 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.
19. Cluster Management. The “Removed Deprecated” button was added to the Staged tab of the
Cluster Management Manage Updates page, which makes it quicker and easier to remove
deprecated staged patches from the database.
20. SQL Server Always On. Content Server now supports the SQL Server 2014 Always On
solution. Follow the documentation from Microsoft to configure Always On -
https://msdn.microsoft.com/en-CA/library/ff877884.aspx . The Content Server system should
connect to the availability group listener (virtual IP). NOTE: Use of the ODBC Driver 11 for SQL
Server is currently not supported.
21. Platform Updates. Support has been added in this update for:
2. Admin Server Logging. Configuration for the Admin Server now supports rolling log files,
which is the default setting for new installations. The log locations and log level settings can
now be changed without restarting the Admin Server. Finally, logging configuration is now set
individually for each Admin Server, with the configuration settings moving from the “Configure
Debug Settings” page to the “Specific” tab on the Admin Server management page.
3. Extractor Recovery. The configuration and behavior of the Extractor Recovery iterator have
been simplified and improved. Multiple retries use successively longer retry intervals to
improve success likelihood. Unnecessary controls were removed. The Recovery iterator is
always enabled. Admins are notified if 50 or more Extractor failures occur in a single run
(indicating likely problems with a Storage Provider).
4. Indexing a Collection. The “Queue for Indexing” feature of a collection now uses the
Recovery iterator instead of DTreeNotify for the indexing operation. This ensures that large
Collection indexing operations do not starve out other indexing operations
5. Text Metadata Storage. A new “Incremental Merge” method for storing text metadata values is
now available in the search index. This new method allows higher indexing throughput and
faster startup times. This mode is set on the “Specific” tab of the Partition Map administration
page.
6. IPool Quarantine. The number of IPool messages that have been quarantined are now
displayed on the Data Flow Manager page. If SOV email notification is enabled, administrators
are advised when new IPools are quarantined.
7. Database Correction. A feature to correct Volume objects that are missing their reflexive row
in DTreeAncestors has been added.
8. Search Index Times. If the Index Tracer features are enabled, information about how current
the search index is can be displayed to admins and users with eDiscovery mode enabled. In
addition, this information will be tracked during eDiscovery search operations, and included in a
Disk Image Manifest to help describe and defend the contents of a Collection.
10. Linux 6.5 Support. Support has been added for Red Hat Linux 6.5 and Oracle Linux 6.5 as
server platforms.
11. Windows 2012 R2 with Oracle 11g R2 – 11.2.0.4 Support. Support added for Windows 2012
R2 as a server platform with Oracle 11g R2 11.2.0.4 as the Database.
3. Relative Date Search. Using the advanced search complex queries, searches are now
possible against DATE or TIMESTAMP regions using relative day, week, month, quarters and
years. For example, [qlregion “OTCreateDate”] >= “-2y” would find objects created since Jan
1, 2012 (assuming today is sometime in 2014).
4. Searching Lists of Terms. New convenience operators IN and NOT IN simplify complex
queries based on lists of terms or phrases. Example: (pollution and in (water, stream, pond,
“waste water retention”) and not in (litter, trash, “rest area”)).
5. No Full Text Comparison. The ability to perform relative comparison [ < <= => > ] has been
removed from full text search (but remains for text search in regions). User behavior has been
to construct queries such as: ( > henry and < horse ), thinking this was like: ( qlrange
“henry~horse” ). These poorly constructed queries often time out and do not return expected
results. A query construction error is now returned instead. Refer to search engine notes for
details on how to enable the prior behavior.
6. Database Repair Utilities. A number of utilities for fixing relatively safe and common
database errors are now available from the Maintain Current Database administration page.
Normally these should only be used with the advice of customer support. The available repair
utilities are:
7. DCS Log Analyzer. An updated log analyzer now ships as part of the Document Conversion
Server that provides statistic and tables summarizing DCS performance, useful to monitoring
and tuning DCS throughput. In the BIN directory, run dcslogan.exe.
8. Index Tracers. A new system exists that tracks the performance of search indexing. A new
Index Tracer volume (subtype 149) creates Tracer objects (subtype 148) every 15 minutes.
The Extractor, DCS and the Index Engines all add their time stamps when they process these
objects. Searches are used to locate these objects, and the times are tracked in a new
database table. The Tracer objects are deleted after being recorded. The
$SOVMGMT.Utils.GetIndexTracerDelay() function can be used to retrieve this data. Requires
“Ascending Extractors”, and enabling on the Extractor configuration page.
9. Search API. The XML search API has been extended to provide attribute information in results
where applicable.
10. Search Language Rules. The selection of Stemming and Thesaurus rules used during
searches is now configurable in the “Search Options” Admin page (no longer in opentext.ini),
and can also be set to dynamically select rules based on the user’s preferred language
settings.
11. Search Path Management. The administration page that allows display and edit of the file
paths used by the search system has been extended to display the search processes that rely
on each path. This change makes it easier to understand which file paths need editing.
12. Storage Provider Rules. The extended type filtering rules for Storage Providers that were
previously part of the Content Move module have been moved to become part of Content
Server. For new installations, an “Internal Storage Provider” is now mandatory, and default
storage rules will ensure that non-file Content Server objects are placed in internal storage. If
not present, an Internal Storage Provider will be created when applying SP1, although the
preferred storage rules are not applied. This change is necessary to help customers make
good choices about where configuration objects should be stored for better performance and
easier re-use of a production data in a test environment.
13. Modules. The Content Move module and the Archive Storage Provider module are no longer
separate modules; they are installed as part of Content Server. There is no need to uninstall
these modules if already present during upgrade.
15. Use existing Database. Content Server now supports the ability to create a Content Server
instance on an existing database. Any existing tables can be dropped if necessary. This
option simplifies scenarios such as deployment into a cloud where the database is provided but
empty.
16. Change Database Password. A new administration page exists that allows you to change the
database password Content Server uses to connect to the database. This improves support
for policies such as regular password rotation, or changing passwords when administrators
leave.
17. Database Ports. When selecting or creating a database, port numbers can now be provided.
With MSSQL, syntax is “hostname,port”. For Oracle, “hostname:port”.
18. Admin Server Password. The method for storing the hashed value of the Admin Server
password has been upgraded from MD5 to the PBKDF2 standard, which is much more secure.
The switchover is transparent on first usage.
19. Disk Image. Classification information can now be requested for inclusion in a collection Disk
Image. If selected, RM Classification information is also included.
20. Search Indexing. Improvements in the handling of Norwegian/Danish and Arabic characters
have been incorporated. Review the search engine release notes for possible impacts.
21. In the llserver section of the opentext.ini, the min/max thread options have been replaced with
a single option for number of threads: "number=". Please refer to the opentext.ini
documentation for details.
22. Content Server can be configured to automatically restart when the schema or configuration
changes require a full restart.
23. User dependencies are now supported by the Content Server Transport module. This allows
users from a source system to be mapped to users on a target system prior to object
deployment. This can be used to accurately transport object permission sets from one system
to another. It is also useful for setting user assignments.
Content Server Forms are now supported by the Transport system. This allows the transport of
Forms and Form Templates, and their configurations between Content Server systems.
2. 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.
3. Content Filters. New content filter settings were added that affect how Content Server behaves
when you open a new tab or window.
• Page Filter: Remember the page number you were on. If disabled, opening a new tab
or window will cause its filter results to start at the first page again by default.
• Item Filter: Remember the item type you are filtering on. If disabled, opening a new tab
or window will cause all of its item types to be displayed again by default.
• Filter by Name: Remember the name string you were filtering on. If disabled, opening a
new tab or window will cause no name filter to be applied.
4. Rights List. Performance enhancements for retrieving the Rights List information.
6. OpenSSL Library Update. The version of OpenSSL that ships with Content Server was
updated to 0.9.8za to resolve security issues.
7. CKEditor Update. The version of CKEditor was updated to support Internet Explorer 11. This
change also addresses an issue where the text box displayed as one line in IE10, which affected
editing text and html documents, adding and editing News items, adding and editing Custom
Views and Appearances and other functionality that uses the text editor.
8. Privilege Auditing. The display of audit records for changes to User Privileges has been
improved to display text descriptions of the changes rather than numerical values.
9. Disk Images. Several enhancements to Make Disk Image are incorporated that are of interest
for defensibility in litigation support and eDiscovery applications. These include:
10. Extractor. The search indexing Extractor now supports specific lightweight events for changes
to Classification values, reducing the indexing load when manual, automatic or OTAC
classification is applied to an object. Because of dependencies on the generation of the
OTLocation search region, mandatory patches are required if you are using Email Management,
Enterprise Library, Communities of Practice, Pulse, or Classifications.
11. Dataflow Monitoring. The charting of the Extractor backlog has been enhanced to differentiate
between operations pending for each of the extraction iterators: Content Recover, Re-Extract,
Targeted Updates, Add/Modify/Delete, and Initiated Workflows.
12. INI File Settings. The “Search Result Cache Expiry” time configuration is no longer managed in
the opentext.ini file. This setting is now maintained in the database and accessible on the
Search Options administration page. Two Recommender Buffer Tracking configuration settings
13. Write Checkpoints. The search index writes checkpoint files to consolidate incremental
playback metalogs. Administrators now have the ability to request checkpoint writes, generating
new checkpoints if the metalogs exceed 10% of the progress towards a natural checkpoint. This
feature is useful before a shutdown of the search grid, since startup may be much faster with
small metalog files. The feature is accessible on the Specific tab of the Update Distributor
administration page.
14. Searchable Email Domains. The search index now has the ability to create synthetic regions
comprised of email domains extracted from regions that contain email addresses. For email-
centric eDiscovery, this feature can greatly simplify the user task of finding all email messages to
or from specific email domains. For example, you can easily find all email messages sent to
recipients at opentext.com. Configuration is found on the Region Modifiers tab of the Search
Manager administration page.
15. Mandatory Search Terms. A new capability allows the administrator to enforce search
restrictions by adding search terms to queries. The restrictions are based on group
membership. The typical use case would be ensuring that users only search within their own
departments. There is a new Configure Mandatory Search Terms administration page for
managing this capability.
16. Search Agent Management. Search Agents are search queries applied during search indexing
for automatic Classification or Prospectors. With this Update, we are introducing the Manage
Search Agents administration page that allows you to review all configured search agents, and
selectively or completely disable or enable these agents. This feature is provided so that
administrators can easily address performance problems during search indexing in the event
that a user constructs expensive search agents that impact indexing throughput. There are two
new auditing interests for tracking changes to agent status, and an optional email notification to
inform users that their agents have been enabled or disabled.
17. Email Configuration. The email configuration for the System Object Volume notification has
been removed, and now uses the Configure Notification settings. This removes a redundant
configuration step. The validation of email server settings has also been improved on the
Configure Notifications administration page.
18. SysReport. Table sizes are now based on database statistics instead of the “COUNT” function.
Although not as accurate, the performance benefit is material. The table reporting now also
tolerates situations where the schema name is no longer the same as the database name.
Finally, for Microsoft SQL Server, more information about table spaces is included in the report.
20. ZIPX MIME Type. New installations of Content Server will now have the ZIPX file format
included in the mime.types file, associated with the MIME type application/zip.
21. Admin Server Functions. The admin server now has a new function,
AdminServer.SetFilewithHash(), which will include an MD5 hash value of the file in the
response. The Admin Server also has new functions to support compressing a directory:
ZipDirectory and GetZipStatus. All these functions are leveraged by the Make Disk
Image feature.
22. DCS Logging. The Document Conversion Server now supports rolling log files. The default
configuration is for up to 10 log files of 100 MB each. In [DCS] section of opentext.ini file
(or custom_dcs.ini)
LogMode=Rolling
Default rolling. (Rolling | Single | Segmented)
LogFileSizeInMB=100
Ignored for “single”
NumRollingLogFiles=10
Ignored unless Rolling
23. DCS Memory Limit. The Document Conversion server now imposes a maximum memory
usage limit on filter processes it controls. The method uses operating system features to force
exceptions if the limits are exceeded. This is intended to capture unexpected rapid memory
leaks. Default is 2 GB limit. Set to 0 to disable this feature.
[DCSworker]
x-maxmemory=2048
24. Search Garbage Collection. The frequency of Garbage Collection operations in the search
engine has been reduced, reducing CPU use and improving indexing throughput. There are two
potential side effects of note. First, the method for computing the “percent full” for a partition is
changed, and may vary slightly from previous versions. Second, it may appear that more
memory is being used but this is not necessarily true, since Java tries to use all the memory
permitted for efficiency, and with less Garbage Collection may come closer to this goal.
2. Make Disk Image. This feature has been significantly improved, with enhancements including:
The Disk Image Manifest has been improved for clarity and features, including:
The Disk Image notification email is also extended to include many of the new information
elements contained in the manifest.
3. Collections Audit. Additional details in the Collection audit records are now captured. These
details allow determination of whether objects in a collection are removed, or whether objects
referenced by the collection have been deleted from Content Server.
4. Extractor. In addition to the existing DTreeNotify table for search indexing requests, a new
DTreeAspectsNotify table is monitored by the Extractor. The DTreeAspectsNotify events are
intended to generate very specific metadata changes to the search index, allowing more efficient
search index updates. The first event supported is Object Rank updates, which are no longer
added to DTreeNotify.
6. Canceling Collection Operations. Collection operations that might run for long periods can
now be cancelled by the Admin from the “Collections General Settings” page, or by the
Collection owner from the Collection browse page. These include Make Disk Image, Queue for
Indexing, Download as Spreadsheet, and Collect all Search Results.
7. Search APIs. A new feature has been added to the XML Search API that allows a saved search
query to be run. A limited implementation of REST APIs for displaying a custom view search
form is available. This REST API is not fully implemented, and is subject to change.
8. Localhost. When 'localhost' is used in the 'OTDS Sign In' URL, the browser is redirected to the
same server name that was used in the request.
9. 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.
10. Drag and Drop. There is now Drag and Drop support for Workflow Attachments. This new
feature simplifies the Add Document and/or Add Document Version process by allowing users to
simply drag one or more documents into the Workflow Attachments folder.
2. Collections. Minor changes have been made to clarify the behavior of Collections:
a. The Collection browse interface now displays a count of selected items. This helps
users understand the interaction of the “Select All” check box, the “Entire Collection”
check box, and the type/name filters, reducing inadvertent user errors.
b. Collection features that are not applicable based on the selected items are now disabled
in the button bar and “More Actions…” menu, eliminating unnecessary error messages.
c. Operations that can delete or modify objects in Content Server now have a challenge
confirmation dialog to reduce the chance that inexperienced users will inadvertently
delete objects instead of removing them from the Collection.
3. Configuration. Two search configuration settings are now available on the “Configure Search
Options” page and stored in the KINI database table. In the past, these were in the
[SearchOptions] section of the opentext.ini file: QueryTimeoutInMS and
EnterpriseTimeToLiveInterval.
6. Database Verification. A new administration page is available to host utilities that can detect or
correct specific known database verification issues, accessed from the “Maintain Current
Database” administration page.
7. EML format support. A file format filter for text extraction (search indexing) is now available for
email messages in the .eml format, which is used by systems such as Google Mail.
9. OpenText Directory Services. When using OTDS for authentication, the Change Password
option on the Tools menu is not shown for users who are not authenticated by the embedded
LDAP directory for OTDS. This applies to OTDS 10.5 Patch 3 or OTDS 10.2.1 with Patch 16
deployed.
11. Support for WebSphere 8.5 and Oracle 11g R2 11.2.0.4 as a Server platform.
12. WebReports: WebReports code is now embedded in Content Server, and is used by OpenText
to deploy several editable reports and dashboards to enhance the user experience. However,
customers must still purchase WebReports licenses to create new WebReports objects
and functionality.
In addition:
• NODEACTION:FAVORITE
• NODEINFO:CHILDREN
• NODEINFO:PATHTOID
• USERPREFACTION
• LL_REPTAG_HTTPCOOKIE
• CAT:<category>:UPGRADEABLE
• CAT:<category>:VERSION
• NODEINFO:RELEASES
• RMACTION:FINALIZE
• USERINFO:EDITTABLE
• UNESCAPEURL
• SCUSERACTION
• LL_REPTAG_!<varname>
1. Transport. The Transport functionality allows customers to better maintain several instances of
Content Server for development, testing, acceptance and production by providing the ability to
move business objects between instances.
For the initial release of Content Server 10.5.0, the following object types are transportable:
• Document
• Folder
• Category
• Project
• URL
• Compound Document
• Revision
• Release
• Shortcut
• Custom View
• Facet
• Facet Folder
• XML DTD
• Search Form
• Custom View Search Form
• Search Slice
• Parent container
• Shortcut target
• Category
• Facet data source
2. Patch Deployment System. Content Server 10.5.0 will include a new patch deployment system
which will allow for easy patch discovery and deployment. Patch dependencies will now be
enforced along with the removal of superseded patches. All patches will be deployed on a
master instance. Once the patches are installed, the Administrator can validate them before
pushing the changes to all other instances in the cluster.
3. Workflow Designer. The Workflow Designer replaces the Workflow Painter applet. This is a
new tool for editing Workflow Maps. The tool is based on HTML5 technology, therefore a Java
runtime environment is no longer needed. The graphical representation of Workflow Maps now
4. REST API. Content Server 10.5.0 includes a new RESTful Application Interface. Access to the
REST (Representational State Transfer) API does not require any additional server components
but rather basic HTTP(S) access to the standard Content Server URL. Initially supporting
Document Management capabilities, the API will be extended to support many aspects of
Content Server functionality. The API is complemented by a detailed set of API documentation
that is included as part of the Content Server SDK. The new API makes it easy to build new and
exciting applications on top of the Content Server 10.5.0 platform.
5. Calendar Control. Content Server 10.5.0 provides a new Calendar Control. This new control is
used to simplify data entry into date fields.
6. Login Validation. Content Server 10.5.0 provides an inline error message if a user name or
password is entered incorrectly. This new functionality minimizes the number of actions a user
must make if login credentials are entered incorrectly.
7. Name Validation. Content Server 10.5.0 provides an inline error message on the Add Item page
if a duplicate name is provided by the user. This new functionality minimizes the number of
actions a user must make to correct the duplicate name.
8. Licensing. Content Server 10.5.0 will include licensing. Simple license file acquisition and
product activation will be available through an automated portal. Production licenses will
available for activation on Content Server production deployments. Non-Production licenses will
be available for deployment on supporting systems. Please review installation guide additional
information about Licensing.
9. Member Service: Content Web Services support for external users and groups has been added
to the MemberService. Two new methods were added to support creating external users and
groups, CreateExternalUser() and CreateExternalGroup(). External users and groups can be
identified by the Member.Type property. External users will have this set as "ExternalUser" and
external groups will have this set as "ExternalGroup".
In addition, the existing CreateMember() method has been deprecated. The other Create*()
methods should be used instead.
10. Text Editing. We have replaced the Java-based text editor with a new WYSIWYG (What-You-
See-Is-What-You-Get) editor. The following is a list of new features:
• New inline editing
• Advanced paste from Microsoft® Word
• Better interface usability
11. Drag and Drop. This new feature simplifies the Add Document and/or Add Document Version
process. It allows the user to simply drag one or more documents into a Content Server Browse
View.
Note: The Drag and Drop functionality will only work with Internet Explorer 10, the latest
version of Firefox ESR, the latest version of Chrome, and Safari 5.1.7+ on the Mac platform. In
addition, this feature is using standard HTML5 capabilities therefore no plug-ins or additional
software installations are required.
This allows users to quickly identify a document without having to open the document itself.
13. Region Map Management. The region map is the list of search metadata regions within the
Search Manager. The Regions page is used to review the list and modify the properties of the
search regions. A number of performance and feature improvements have been incorporated,
and the region map data is now stored in the database.
14. Extractor. The Extractor is responsible for watching events in Content Server, and formulating
appropriate changes to the search index. Content Server 10.5.0 incorporates the following
enhancements:
a. Extractor Exclusion. A number of subtypes and volumes are now excluded from
indexing by default. These can be reviewed on the Extractor General Settings
configuration page.
15. Return to Last Search Results. This consists of a link on the search bar that will return the user
to their last displayed set of search results.
16. Search Engine Scalability. A new set of features in the search engine allows text metadata to
be entirely represented on disk. This change typically allows three times the number of Content
17. Part Number and File Name Search. A set of features have been added to the Search Engine
that will improve the ability to search metadata containing common structure found in part
numbers, URLs and file names.
18. Search File Types. The Search Engine assigns file types to objects based on content analysis,
file extension, subtype, and MIME type. This file type is now used in search relevance and
search filters.
19. OpenText WebDAV 10.5.0. Now ships with Content Server 10.5.0. Separate Release Notes
exist for administrators who require more information. Please note that Content Server WebDAV
10.5.0 is compatible with Content Server 10.5.0 and Content Server 10.0.
20. OpenText Office Editor (WebEdit) 10.5.0 and Email Services Module. Now ship with Content
Server 10.5.0. Administrators who require more information can consult the Enterprise
Connect, Office Editor and Email Services 10.5.0 Release Notes document. Please note that
Office Editor 10.5.0 and Email Services module 10.5.0 are compatible with Content Server
10.5.0 and Content Server 10.0.
21. 64-bit Integers. Integer values, including Data IDs, have been changed from 32-bit values to
64-bit values. Custom applications dependent on 32-bit values may be affected.
22. Database Upgrades. The Database Upgrade Confirmation page now clarifies which module
schema is current or will be updated.
23. Search Forms. The terminology for search templates has been clarified by referring to display
templates as “Search Layouts” and query templates as “Search Forms”.
24. Initiated Workflows. These are now excluded from search indexing by default for new
installations. This can be changed on the Extractor General Settings page.
25. Connect Logs. Log levels can now be changed through the GUI without stopping or starting
Content Server services.
26. Form Regions. The region names for forms now have a standardized naming convention:
OTForm_<templateID>_<attributeID>. This change allows predictable use of forms regions in
search queries, and simplifies management of search regions.
27. Search Filter Memory. A new setting in the partition management page allows additional
memory to be allocated to search engines, nominally as space for search facets.
29. DCS IPools. The Document Conversion Service will now stop processing new data if the output
IPool area reaches 100 messages. This helps prevent runaway disk consumption if downstream
processes are halted. The limit can be adjusted in the dcs.ini file.
30. HTML Extraction. New optional settings allow any metadata in HTML files to be converted to
OTDoc<metatag> regions for indexing.
31. IPool Dataflow Distribution. This new feature allows search indexing data flows to be
distributed between up to five Document Conversion processes, providing more scalability
options for indexing and thumbnail generation.
32. Selecting Collections. The confirmation pages for selecting a Collection are now consistent for
browse and search, and offer convenient hover menus for selecting commonly used collections.
33. Retired Search Partitions. A new mode of operation for search partitions simplifies the
replacement of older partitions with newer partitions using updated settings without downtime.
34. HTML Resource Versioning. CSS and JavaScript resources used to construct HTML pages
are now versioned. This means that web pages that change these resources will display
correctly after upgrades without users needing to flush their browser cache.
35. Email Exemplars. Email objects can now be used as exemplars for Intelligent Classification.
Email can now also use the “Find Similar” feature for search.
36. Search Partition Biasing. This feature allows optimization of search indexing performance
where many partitions exist by giving preference to a limited set of partitions when growing the
search index.
37. Database Verification. Several tests to verify the integrity of ancestry data in the database
have been added.
1. Spell Check. The Spell check applet has been removed from Content Server 10.5.0. Instead,
we now rely on the spell checking functionality built into the browser.
2. LAPI. The LAPI programming interface will not be available in the next version of Content
Server. Content Server 10.5 will be the last series of Content Server that will support Livelink
API (LAPI) applications. Content Web Services or the REST API are the recommended
replacements for LAPI.
3. User Rights Threshold Setting. The User Rights Threshold setting has been removed in
Update 2014-09 as part of the Rights list optimizations. This setting was previously located on
the Server Configuration Configure Performance Settings page.
4. Recovery Iterator Administration Page. The Recovery Iterator Administration page has been
removed in Update 2015-03. The configuration and behavior of the Extractor Recovery iterator
have been simplified and improved. Unnecessary controls were removed. The Recovery
iterator is always enabled.
5. Enterprise Library Services API. The APIs in this module should not be used for new
applications. Enterprise Library Services API may not be supported for external applications in a
future version of Content Server. The Enterprise Library Search Services Search API is
deprecated and will no longer be available after Content Server 10.5.
6. NPAPI. Selected features (such as printing and Office Editor) are implemented using the NPAPI
capability in web browsers. Most major browsers are phasing out support for NPAPI. This may
cause some features to be non-functional. Solutions using alternate technologies may be made
available for some of the features, which will be communicated outside this document.
New point releases and major releases of platform components are not automatically supported.
Certified Windows 8 IE 10
Chrome1
Supported Windows 8 Firefox ESR2 • Firefox ESR 31 support added with Content
Server SP1.
Supported OSX 10.7 Safari 5 • Validated with OSX 10.7.2 and Safari 5.1.1
1
Only the latest version of Chrome is supported. Mobile platforms are not supported
2
Only the latest version of Firefox ESR is supported.
4.2.1 Client Operating System Notes
4.2.1.1 Windows
• There is an issue where special characters in filenames within a generated zip file can appear to
be garbled when the zip file is opened. Microsoft KB 2704299 outlines a resolution for this issue
- https://support.microsoft.com/en-us/kb/2704299
• 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 for us 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.
• As of Content Server 10.5 the browser spell check built into the browser should be used. The
spell check functionality has been removed from Content Server.
• The Content Server Print feature is not supported with Chrome browsers.
• Google Chrome version 42 has an issue with Drag and Drop. Please see our Knowledge Base
article: Content Server - Document Edit, Drag and Drop, and Print actions are unsuccessful after
installing Google Chrome 42. This issue is resolved in newer versions of Chrome.
4.2.2.2 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 for us 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.
• As of Content Server 10.5 the browser spell check built into the browser should be used. The
spell check functionality has been removed from Content Server.
• General
Java 7 Update 45 Java 7 Update 45 is included with the Content Server full 10.5 Release
install.
Java 8 Update 51 Java 8 Update 51 is included with the Content Server full Update 2015-09
install. Java 8 Update 51 is available as a separately
downloadable patch which can be installed along with the
Content Server Patch.
Note: Databases are supported on any Operating System platform supported by the database
vendor. It is not required that the database be on the same platform as Content Server.
Databases which have a client component must have that client supported on an Operating
System platform supported by Content Server
Supported Windows 2012 R22 SQL Server 2012 SP15 IIS 8.0/8.5 • Windows 2012 R2 support
added in Update 2014-03.
SQL Server 2012 SP25 • SQL Server SP2 support
Apache HTTP
2.4 added in Content Server
SQL Server 20145 SP1.
Tomcat 7 • Oracle 12c support added
SQL Server 2014 SP15 in Update 2015-03.
• Oracle 11g R2 – 11.2.0.4
Oracle 11g R2 – Tomcat 8
support added in Update
11.2.0.41,6 2015-03.
• SQL Server 2014 support
Oracle 12c –
added in Update 2015-03.
12.1.0.2.01,6
• Tomcat 8 support added in
Update 2015-06.
• SQL Server 2014 SP1
support added in Update
2015-09.
Certified Windows 20122 SQL Server 2012 SP15 IIS 8.0/8.5 • SQL Server SP2 support
added in Content Server
SQL Server 2012 SP25 SP1.
Supported Windows 2008 R2 SQL Server 2012 SP15 IIS 7.5/8.0 • SQL Server SP2 support
SP17 added in Content Server
SQL Server 2012 SP25 SP1.
Apache HTTP
2.4 • Oracle 11g R2 11.2.0.4
SQL Server 2008 R2 support added in Update
SP23 2014-03.
Tomcat 7
• Tomcat 8 support added in
SQL Server 2008 R2 Update 2015-06.
SP33 Tomcat 8
• SQL Server 2008 SP3
support added in Update
Oracle 11g R21,6 2015-09.
Certified Solaris 10 Oracle 11g R2 1,6 Oracle iPlanet • WebSphere 8.5 and Oracle
7 11g R2 11.2.0.4 support
added in Update 2014-03.
Tomcat 7 • Tomcat 8 support added in
Update 2015-06.
Tomcat 8
Apache HTTP
2.2
IBM
WebSphere
8.5
Certified Red Hat 6.4 Oracle 11g R2 1,6 Tomcat 7 • Oracle 11g R2 11.2.0.4
support added in Update
Oracle Linux 6.4 2014-03.
Tomcat 8
(UEK Kernel) • Tomcat 8 support added in
Update 2015-06.
Supported Red Hat 6.6 Oracle 11g R21,6 Tomcat 7 • Red Hat 6.6 and Oracle
Linux 6.6 support added in
Oracle Linux 6.64 Oracle 12c – Update 2015-06.
Tomcat 8
12.1.0.2.01,6 • Tomcat 8 support added in
Update 2015-06.
• Oracle 11g support added
with Update 2015-09.
Supported Red Hat 7.0/7.1 Oracle 12c – Tomcat 7 • Red Hat 6.6 and Oracle
12.1.0.2.01,6 Linux 6.6 support added in
Oracle Linux Update 2015-06.
Tomcat 8
7.0/7.14 • Tomcat 8 support added in
Update 2015-06.
• Red Hat 7.1 and Oracle
Linux 7.1 support added in
Update 2015-06.
Oracle iPlanet
7
1
Oracle support includes Standard, Enterprise and RAC as well as deployment on Oracle Exadata
Database Machine and Oracle SuperCluster.
2
Windows 2012 support includes Standard, Datacenter, and Hyper-V.
3
SQL Server 2008 R2 support includes Standard, Enterprise and Datacenter.
4
Covers both UEK (Unbreakable Enterprise Kernel) and Red Hat compatible Kernel.
5
SQL Server 2012 and SQL Server 2014 support includes Standard and Enterprise.
6
Oracle support includes Oracle client and Server interoperability support as provided by Oracle –
Server 12.1.x is supported with client 11.2.x and server 11.2.x is supported with Client 12.1.x.
7
Windows 2008 support includes Standard, Enterprise, and Datacenter.
• In Content Server, when you have a Content Server 10.5 instance running on Microsoft SQL
Server 2014, performance degradation may occur. Please see our knowledge base article
Content Server - "“unable to add user (X) from group (X)- error saving Group”" Message
appears and performance degradation may occur in Content Server 10.5 running SQL
Server 2014
• A software defect in MS SQL Server 2012 can occur if you have Maximum Degree of
Parallelism set to 0 and you attempt to create a clustered index on a table.
The resolution is to apply the ‘Cumulative Update Package 1’ for MS SQL Server 2012
(https://support.microsoft.com/en-us/kb/2679368 ).
4.5.2.4 Oracle 12
• A new option for Oracle Database 12c, Oracle Multitenant, allows a multitenant container
database to hold many pluggable databases. To use the pluggable database from Content
Server you must reference the pluggable database in your TNSNAMES file, and you must
connect to the pluggable database from Content Server.
• If you run Content Web Services on Microsoft Internet Information Services, you must install
.NET Framework 3.5.
Versions Notes
For details on compatibility between OpenText products, refer to the Compatibility Matrix
(https://knowledge.opentext.com/knowledge/llisapi.dll/open/15507401) in the OpenText Knowledge
Center.
Arabic AR YES NO NO
Catalan CA YES NO NO
Chinese ZH YES NO NO
Finnish FI YES NO NO
Italian IT YES NO NO
Kazakh KK YES NO NO
Portuguese PT YES NO NO
Swedish SV YES NO NO
Ukrainian UK YES NO NO
• CDR
• Word 95-2013
• Excel 95-2013
• Visio 2007-2013
• RTF
Hit Highlighting is supported for all file types, except:
• TNEF
• Inventor 2D (Windows only)
• Gerber
• CDR
• Solidworks2D (Windows only)
The following are the supported File Types and Versions for OpenText Document Filters on
Windows, Linux and Solaris:
WordPerfect EMF
Postscript
OpenText also recommends that you check the Content Server area of the OpenText Knowledge
Center (https://knowledge.opentext.com/knowledge/cs.dll/Open/16534305 ) for any documentation
updates that may have been posted after release.
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.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters
DirectoryCacheLifetime=0
FileNotFoundCacheLifetime=0
FileInfoCacheLifetime=0
6 Critical Patches
At the time of release, the following patches must be applied to Content Server 10.5.0. OpenText
recommends that you use the Cluster Management feature located in the administration pages to
identify the most up-to-date patches that have been posted after release. OpenText recommends that
you apply patches when they become available.
SP1 Update 2015-12 pat105000821 – required for Arabic support for Pulse 10.5.0
pat105000839
pat105000842 – required for Recycle Bin 10.5.0
10.5 pat105000006
Note: We recommend reviewing the deprecated patch list should a recommended patch get
rolled into an update.
7 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.
OpenText also recommends highly that you use the Cluster Management feature located in the
administration pages to identify and manage patches that have been deprecated. To do this, perform
an analysis on your master instance. Once analysis is complete, a list of deprecated patches will be
displayed.
SP1 pat105000014
pat105000049
pat105000078
pat105000101
pat105000106
pat105000129
pat105000132
pat105000135
pat105000138
pat105000174
pat105000184
pat105000185
pat105000190
pat105000196
pat105000198
pat105000200
pat105000201
pat105000206
pat105000211
pat105000213
pat105000215
pat105000216
pat105000217
pat105000218
pat105000223
pat105000224
pat105000230
pat105000233
pat105000238
pat105000239
pat105000240
pat105000245
pat105000247
pat105000251
Search Configuration Files. New versions of search configuration files are not installed when
applying an Update to an existing system because replacing these files would overwrite
customizations previously made. In this case the latest versions of the configuration files are placed
in a reference folder where you can review them and select specific edits for your configuration files:
<OTHOME>\config\config_reference.
If you are installing this update as a new install you will find these configuration files in
<OTHOME>\config.
The table below shows the Content Server Update in which each of the configuration files was last
changed. If the update is being applied to a new installation, these files should be copied to
the <OTHOME>\config directory before indexing any data.
File Change
SP1 Update 2015-12
Dcs.ini Fix for issue CMSD-5010 – “Unexpected counts reflected with File Type
Search Filter with Contract Folders and Folders”
is changed to
STMapping-81108,31108
Dcsrules.txt Fix for issue SRCH-4179. Skip thumbnail operation for PowerPoint 95 files
as they are not supported. Add exec IMPPTTHUMB.
is changed to:
exec IMPPTTHUMB
[IMPPTTHUMB]
case OTMimeTypeFormatId = "1010"
try PruneDoc
default
try IMTHUMB, PruneDoc
end
Dcsviewrules.txt Fix for SRCH-4156. Update for the Hit Highlight handling with PDF
files by adding exec Escape Tag:
case OTMimeType = "application/pdf"
try XPDF, DCSIMHH, PruneDoc
exec EscapeTag
Changed:
To the following:
OTDocModifyDate=OTDocLastSaveDate
OTDocAttachments=OTDocAttachments
OTDocInternetMessageId=OTDocInternetMessageId
OTDocMessageClass=OTDocMessageClass
OTDocConversationId=OTDocConversationId
OTDocConversationIndex=OTDocConversationIndex
OTDocDeliveryTime=OTDocDeliveryTime
OTDocAttachments
OTDocInternetMessageId
OTDocMessageClass
OTDocConversationId
OTDocConversationIndex
OTDocDeliveryTime
dcs.ini Added OTFileType for Recycle Bin Day Folders and Tempo box folders:
STMapping=1290,207
STMapping=3033,207
dcsrules.txt Add support for jp2 files:
case OTMimeType = "image/png", "image/x-bmp",
"image/gif", "image/tiff", "image/pipeg",
"image/bmp", "image/jpeg", "image/pjpeg",
"image/jp2"
dcsviewrules.txt
"image/png", "image/x-bmp", "image/pjpeg",
"image/bmp", "image/pjpeg", "image/jp2"
mime.types
image/jp2 jp2
mime.gifs Add mappings for file type eml:
eml.gif message/rfc822
# Eml message
<Error>
<Id>7237</Id>
<Name>ENAD_BadPasswordWrite_MsgID</Name>
<Value>cannot write password file</Value>
</Error>
<Error>
<Id>7238</Id>
<Name>ENAD_AuthRequired_MsgID</Name>
<Value>command %s requires
authentication</Value>
</Error>
Dcsviewrules.txt Added Visio drawing format support for view as web page and hit-
highlighting:
[View]
case OTMimeType = "application/vnd.ms-
visio.drawing"
try DCSIMAutoView, PruneDoc
[HHView]
case OTMimeType = "application/vnd.ms-
visio.drawing"
try DCSIMHH, PruneDoc
Dcsrules.txt Added Visio drawing format support for thumbnail generation and image
format support for text extraction
[Thumbnail]
case OTMimeType = "application/vnd.ms-
visio.drawing"
[Convert]
case OTMimeType = "image/tiff", "image/jpeg",
"image/pjpeg", "image/pipeg", "image/png"
try IM, PruneDoc
minMetaDataLength = 3
maxMetaDataLength = 50
[DCSmetadata]
lib=dcsmeta
#OTPAT_PHONE=((\([01]?\))?\(*[0-
9lsSoO]{1,3}\)*)*\-*\/*\.*\_*[0-9lsSoO]{3}\-
*\/*\.*\_*[0-9lsSoO]{4}(([\x58\x78])*[0-
9lsSoO]{2,3})*\s
#OTPAT_CREDIT_CARD=\b(?:3[47]\d{2}([\ \-
]?)\d{6}\1\d|(?:(?:4\d|5[1-5]|65)\d{2}|6011)([\
\-]?)\d{4}\2\d{4}\2)\d{4}\b
#OTPAT_SIN=^[0-9lsSoO]{3}(\-)*[0-9lsSoO]{3}(\-
)*[0-9lsSoO]{3}\s
#OTMETA_HASHTAG=[\s]+#([\da-zA-Z]+)
#OTMETA_USERID=[\s]+@([A-Za-z0-9]+)
#maxPatternSearchLength=50000
#maxPatternResults=1000
#maxMetadataSearchLength=1000
#maxMetadataResults=10
Dcs.ini Fix for issue SRCH-3972 – “File Types are not defined for Office 2013,
dwfx, mp3, wave, xgl, indesign,and OJT”
Fix for issue SRCH-3923 – “Unable to get image for DWG files”. Added:
Dcs.ini
DetectMapping=579,100
DetectMapping=580,100
Opentext.ini Added support for rolling Log Files. To enable add the following entry to
[general]
LogConfigPath=[OTHOME]\config\contentserver.logging.pr
operties
opentext.logfile=ON
opentext.logfile.enableconnect=ON
opentext.logfile.loglevel=TRACE
opentext.logfile.enablerollinglog=ON
opentext.logfile.maxBackupIndex=5
Update 2015-03
JavaVMOption_4=-
Djava.util.logging.config.file=`OTHome`\config\javaser
ver.logging.properties
This resolves a deadlock when using the default log4j setting (PYRO-1870)
Update 2014-12
Update 9
9 Items of Note
This section provides information about issues that have been fixed in this release.
#disable http
org.eclipse.equinox.http.jetty.http.enabled=false
#enable https
org.eclipse.equinox.http.jetty.https.enabled=true
#set port to the same as org.osgi.service.http.port setting
org.osgi.service.http.port.secure=3100
#set the keystore which was generated using Java keytool (keytool
-keystore keystore -alias jetty -genkey -keyalg RSA)
org.eclipse.equinox.http.jetty.ssl.keystore=c:/opentext/cs/keystore
org.eclipse.equinox.http.jetty.ssl.password=password
org.eclipse.equinox.http.jetty.ssl.keypassword=password
2015-06 LPAD-21894 Any multi-file output function performed on a shortcut to an item that no
longer exists gives Server did not Respond producing a trace file
2015-06 LPAD-23141 Unable to change item List, Featured, Hidden when adding via
Workflow Attachment.
2015-06 LPAD-34830 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 required to switch to the WebDAV drag
and drop view
2015-06 LPAD-35362 Users should not be allowed to move projects into sub-folders of other
projects
2015-06 LPAD-38376 Some files are unexpectedly skipped when drag and dropping max
number of files
2015-06 LPAD-40235 Webreports 10.0.1 - nodeaction:move fails on documents with Chinese
Colon in document name
2015-06 LPAD-41433 Warning Page Has Expired when paging back on Multi-Page Audit Trail
2015-06 LPAD-41537 HTTPS connection cannot be used when using Cluster Management
2015-06 LPAD-41987 Text Multiline attribute does not word wrap in IE11
2015-06 LPAD-42219 Unable to move thumbnail images via a storage provider Content Move
job
2015-06 LPAD-42349 DPS Version fails (version lost) if original file contains Category
Attribute used in a Facet
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-42493 Typo in /support/core/ajax_dhtml_util.js introduced by pat105000314
2015-06 LPAD-42617 cgihosts parameter should not be truncated on Admin page to 248
characters (?func=admin.securityvars)
2015-06 LPAD-42805 AgentSchedule may generate SQLServer deadlocks under heavy load.
2015-06 LPAD-42839 When viewing permissions on a folder, Assigned Access shows deleted
user without a "(delete)" flag next to the name.
2015-06 LPAD-42852 Database lock prevents parallel copy of documents or folders with
categories.
2015-06 LPAD-42969 The “previous” link on the audit tab does not work on some browsers.
2015-06 LPAD-42978 Unable to change item List, Featured, Hidden when adding via
Workflow Attachment
2015-06 LPAD-42982 Logging into Content Server with a Domains enabled user fails through
LAPI.
2015-06 PYRO-1862 Ensure PrgCtx cleanup occurs when used by instantiated Agents
2015-06 PYRO-1893 A copy of thread logs at DEBUG level is now captured to assist in
support activities, regardless of the log level.
2015-06 PYRO-1905 DAPI.GetNodeById() should return error if PARENTID equals DATAID
2015-06 PYRO-2037 Patch information has been added to the SysReport.
2015-06 SFWK-4111 Searching for a category of type text with a enumerated list of options
does not work if the value contains quotation marks.
LPAD-43584
2015-12 A LiveReport script could potentially halt execution and
display an error page.
LPAD-44782
2015-12 Due to browser caching, clicking the Back button in a
browser after logging out can expose the last-viewed
Content Server page. Appropriate messaging was
added to the logout page to highlight the importance of
closing the Web browser to ensure data security.
2015-12 SFWK-6816 “expat” library was updated to latest version to fix known
vulnerabilities.
PYRO-2376
PYRO-2375
LPAD-41812
2015-06 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.
LPAD-41880
2015-06 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.
LPAD-42964
2015-06 Cross-site Scripting (XSS) vulnerability in workflow.
LPAD-42349
2015-06 In some situations, when Document Property
Synchronization (DPS) added a version to a document,
and attributes associated with that document were
linked to Facets in Content Server, an error would occur,
resulting in a corrupted version being added to the
document. This occurred when the Facet system
attempted to add new data to the system when that data
already existed.
2015-06 PYRO-1982 API functions for creating a group do not check that user
has permission when creating a X-Domain group.
PYRO-2038
2015-06 Potential script crash in DAPI callbacks when requesting
too many program sessions.
2014-09 PYRO-1588 The version of OpenSSL that ships with Content Server
was updated to 0.9.8za to resolve security issues.
2014-09 LPH-740 A trace file will no longer occur when eLink agent
processes a workflow under certain conditions.
2014-06 CST-364 When using OTDS for user authentication, failed login
attempts were not being properly audited.
2014-06 LPAD-37339 Workflow audit events for form data now respect the
Workflow parameters audit trail setting "Don't include
user names". This is fixed in conjunction with Forms
10.0.0 patch 100001380.
ListNodesSettingSaved
ListNodesTablesWhiteList
ListNodesQueryBlackList
EnableListNodes
2014-03 LPAD-36216 The Audit Purge function failed when versions were
deleted as part of an eSign step.
10.5.0 WA-2165 Cluster agent fails to look up Content Server host Fixed in Update
information if MSSQL database collation is set to
2014-03
case-sensitive.
Patch pat105000006 will need to be manually
applied for customers using case sensitive MSSQL.
The Cluster Management tool can be used
subsequently.
10.5.0 WA-2048 Cluster Management pages do not work with Fixed in SP1
compatibility view turned on in IE. This happens for
both IE9 and 10. You need to turn compatibility
mode off for the site for it to work or use an
alternative browser.
10.5.0 LLWR-3556 Although WebReports manages its own scheduling Fixed in SP1
agents, some remnants of its original inclusion in
the Content Server, 5 minutes agent remains. This
results in an error message in the agent logs:
“Could not locate scheduled Agent”. This error
message can be ignored and this error has no
impact on Content Server.
10.5.0 LPAD-32419 In Internet Explorer 10's quirks mode, The CKEditor Fixed in Update
does not display correctly. Possible work around
2014-09
solutions are:
-Duser.language=en -Duser.country=US
13 Contact Information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1
Email: [email protected]
Knowledge Center: https://knowledge.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.
97